Ole Kristiansen
Forum Replies Created
-
-
Hi Michael
For 4K timelines, Resolve 12 officially requires at least 8GB of GPU memory – so 3GB is not great !
Make sure you have plenty of free space on your OS disk for a swap file the size of your system memory that should be larger than your GPU memory….
Try increase the Pre-allocated System Memory value in Resolve Preferences
Try reducing the timeline resolution
Best,
Ole -
Hi
I’m talking about your macbook hdmi output settings – ReFresh Rate !
Best,
Ole -
Ole Kristiansen
October 2, 2017 at 6:05 pm in reply to: Converting GH5 10bit for use in PremierePro ?Hi Nicolas
You can convert to DNxHR – or maybe try set your GH5 Luminance level to (64-940) and see if this is better in Premiere !
Best,
Ole -
Last time I did it is was perfect – I got a Intensity Pro 4K Blackmagic card ! It was in Resolve 12.5 maybe something wrong in 14 ? I can try after work !
Here is another video !
https://www.youtube.com/watch?v=ugfcvfXNsqc
-
Hi Matt
“Am I needing to connect my reference monitor to my PC first and create the 3D Lut that way?”
No
I just follow the video made by Aram K and it seems perfect !
best,
Olehttps://www.youtube.com/watch?v=37yvL98nFa8
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
History of changes
Neat Video v3 plug-in for OFX hosts (Linux)
Version 4.6
Added support for DaVinci Resolve 14https://www.neatvideo.com/features/version-history/nv3ofxl?os-tab=linux
-
-
Up
-
Hi Ulrik
Understanding render options in Adobe Premiere Pro
https://www.digitalrebellion.com/blog/posts/understanding_render_options_in_adobe_premiere_pro
Use Previews
This results in reduced export times because your sequence render files are used instead of having to re-render the sequence. This is of course assuming that you have a significant amount of your timeline already rendered, which may not be the case if you have a fast computer or your sequence is simple enough to be played back without rendering.
Generally you should not use this option because it is likely to result in reduced image quality, particularly when outputting to a different format from your sequence and also because it will bypass the quality options detailed above. It should only be used where processing time is more important than image quality, such as previews or rough cuts for example, although these are likely to be simple enough that this option doesn’t significantly affect processing times.

