Stig Olsen
Forum Replies Created
-
Hi,
Umult makes the rest of the graphic about 5-10% transparent.
Stig
-
Yup, I just think it strange that AE cant deal with it.
Stig
-
Let Juan use his money on new machines everytime he runs into a problem.
I suggest you Modify the QualifiedGpuBoards.txt file in Avid, by opening it in texteditor/notepad and change driver number next to “NVIDIA Corporation–Quadro 2000/PCI/SSE2 : NVIDIA : 2000”
Stig
-
Hi Michael,
What you imply is not correct. DNx36 can not utilize the full potential of the GoPro material. You should transcode to DNx120.
Stig
-
Hi Mikee,
AMA is resource hungry and drive speed dependent, and will not work properly for some.
MXF is way faster and the most reliable way of dealing with material in Avid, and is trusted in most professional facilities,
I recommend that you only use AMA to select clips, and transcode/cosolidate to MXF.But hey, whatever works for you.
Stig
-
Hi William,
You should never use AMA to import material to Avid!
If you do, you have a graphic/video-level source editor in the bin.Since Avid works in video levels internally, you need to set the monitor options in Resolve to normal and export MXF directly to the AvidMediaFiles/MXF/1,2,3 etc – folder.
The white and black levels will match up perfectly between 16-235.Do NOT apply a broadcast safe, as it does not remap but clip your levels and chroma.
The
-
Hi Bill,
Did you notice this on QT wrapped files only (same as source)?
Stig
-
Job ter Burg, you are a genious. I think QT sometimes doesnt understand the tag created in the “same as source” file. I will be using DNxHD from now on. I want control over the black level in all players.
-
The thing here is that the two files follow the same route but one of them (same as source) is confusing the players (0-255 or/and 16-235) and the other one (dnXhd) keep the levels constant at 0-255.
-
That is the reason I remap to RGB when exporting.