It sounds like they are saying Avid cannot produce renders or mixdowns that are 10-bit if the target codec is ProRes, only if it is DNxHD###X.
If true, this would be a limitation inside Avid, since the ProRes codecs all support 10-bits (or more).
At this point, I wouldn't trust any 10-bit pathway in or out of Avid without testing it.
Cheers,
--Michael Brockington
I heard back from Avid support regarding the thread. Marianna had passed my initial questions on to support. I don't quite understand everything in the response especially regarding the part that say ProRes is always 8 bit. I don't quite understand if that's just in certain Avid cases or what. I render my 4K to ProResHQ to facilitate delivery of a ProResHQ to QC. I didn't think Avid was rendering that as 8 bit ProResHQ. I've asked for some clarification about this. Here's the Avid Support Response:
Hi All, Timeline Video Quality Settings DOES NOT affect file export. However, it does affect the Output on Digital Cut. So whatever is set on the Video Quality Menu on the Timeline, that will apply to the Output of the material on the Digital Cut. With some output modes, you can also use the Bit Depth menu to select either 8-bit or 10-bit effects processing. If this option is not available, the Bit Depth menu is either grayed out or does not appear (see page 889 of the document below). http://resources.avid.com/SupportFiles/attach/Media_Composer_Editing_Guide_2018.2.pdf Mixdowns, Renders, etc. can be set to 10 bit only if we do it on a "DNxHD X" format.. We only have the option of 10 bit for Playback both on Source and Record Monitor/Timeline. Though you have the option to export the file as 8 or 10 bit by doing a "Custom Quicktime Movie Export" as "Avid DNxHD Codec". On the other hand, all Apple Prores are 8 bit. You can use "Media Info" application which is a free software for Mac and Windows Os to determine the bit depth of the material. Regards, Kris Avid Video Editors
---In Avid-L2@yahoogroups.com, <bigfish@...> wrote :
Type on the 15 minute clip should have said 15 second clip.
---In Avid-L2@yahoogroups.com, <bigfish@...> wrote :
With all the questions regarding Timeline Quality Settings impact on renders etc... today I'm doing some stabilizing in 4K which is time consuming to say the least. I got to wondering if Timeline Quality Settings would have any effect on the fluidstabilizer tracking on the stabilize effect. I took a 15 minute clip and applied the stabilize to a 15 second clip while in Yellow/Green timeline quality and it took 11 minutes even. Doing the same thing in 10 bit Green Timeline Quality took 11:14. So not much different in processing time.
I've found that the stabilize tracker seems to look through all the monitored tracks to do it's tracking. For example if I have a shaky shot on V1 and I cover that shot with a still on an upper track and monitor the upper track when I apply the stabilize to the V1 shot in my monitor I see the fluidstabilizer dots dancing over the still. If I move the monitor track down to V1 the fluidstabilizer dots are dancing on the V1 shaky shot as intended. From this is seems to me that the Stabilize Fluid Tracker is using the timeline monitor as it's input. Would this mean that if I'm in Yellow Green mode that the Stabilze Tracker is processing a less detailed image than if I did it in 10 bit Green mode? The time difference from the aforementioned time test I did doesn't really show a significant change in processing time but I don't know if that is a valid way to access if it's better to be in 10bit green mode for Stabilze effect.
The reason I'm curious is I can't get real time playback in 10 bit green without a render so I have to keep toggling back to Yellow/Green mode to playback the stabilize effect to see if it worked acceptably. Curious what others think or have experienced in this regard.John Moore Barking Trout Productions Studio City, CA bigfish@...
Posted by: Michael Brockington <mbrock321@gmail.com>
Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (4) |
No comments:
Post a Comment