Rohit Gupta
Forum Replies Created
-
The Resolve scopes show the full range signal. The scaling to video levels is done on the Decklink output when you are monitoring, or laying off to a tape.
The only way to see video levels on the Resolve scopes would be to use a 1-D Display LUT which would do full range to video level scaling. If you are using such a LUT, please make sure you set Decklink monitoring to full range.
Of course, if you are using Ultrascope for external video monitoring, you would see video levels since it will look at the Decklink output.
-
You should be able to add the Avid MediaFiles folder in the Resolve Preferences, and then add MXF files to the media pool. If you need to read or write DNxHD files, then you will need the license. Uncompressed MXF files do not require the license.
-
We’ve seen this problem on a few installations where the database does not install properly when you install resolve. Perhaps you are running into the same issue.
To solve this problem, please use the following steps:
1. Open a Terminal
2. sudo mv /Library/PostgreSQL /Library/PostgreSQL_old (enter password when prompted)
3. Re-install Resolve -
In the video monitoring section in the config page, you can choose whether to monitor in full range or video range. Same setting is available for Deck I/O.
-
Also, in the Config page, Project tab, enable “Assist using reel number from the”, and then “Embedding in source clip file”.
It is recommended to set this to before starting your project and adding any clips to the Media Pool.
-
Add all the R3Ds in the media pool, and then load the EDL to conform the media.
You should also enable reel number support to avoid any conflicts in case there are two clips with overlapping source timecode.
Resolve supports reading the full reel/tape number written out by FCP in the comments field of the EDL.
-
Hi Aless,
6 GB RAM is sufficient to run Resolve.
The 285 is much faster than the 4800 as this point of time.
Regards,
Rohit Gupta
Blackmagic Design