Bill Ravens
Forum Replies Created
-
wow!
While DNxHD is a free source decoder, not all venues know enough to have the DNxHD playback decoder installed on their system. Without knowing, for sure, I’d opt for H.264, AKA AVCHD. This is a pretty widely accepted playback format, these days. -
TmpGenc video masteroing works
or
Cineform(available thru GoPro) -
Shane has explained this at least once before, but, I think his point was missed, so I’ll reiterate what he said.
Let’s say you have 60 minutes of native footage in AVCHD. Now, let’s say that when you’re done editting, you’ll only be using 20 minutes of that native footage.
So, if you import all 60 minutes to DNxHD, it will take Avid some time to import/transcode all 60 minutes.
Now, if you AMA link to the 60 minutes of native AVCHD footage, put it on your timeline and cut out everything but the 20 minutes you need, now you can transcode it to DNxHD, and the transcode time will be much shorter because it’s only 20 minutes of footage instead of the original 60 minutes.With the transcoded 20 minutes of .new footage, you can now edit and export to your hearts content.
Edit: Here’s a new wrinkle. Avid is reporting that their algorithms are different depending on whether the workflow is AMA Link>Transcode or straight Import. There is a reported quality loss when Importing. Transcoding from AMA is also faster than a straight import. -
In my workflow, I routinely output my edit session to Quicktime Reference files for use in a third party authoring or distribution application. AMA links will not export with QTRef. They must be transcoded before they can be exported via QTRef, so, there’s no avoiding the transcoding process, anyway, with my workflow.
-
I have encountered the same problem. The “workaround” is to borrow that second monitor again. Once you see the missing scopes on the second monitor, drag them back to the primary monitor. Now you can disconnect the second monitor and still see the scopes when you start with a single monitor.
-
I reported this to BMD months and months ago. I believe there is a color space flag set incorrectly within the Quicktime codec that is used to playback the footage. All the data is there, nothing has been lost, however, if you look at your footage on a waveform monitor, you will see the RGB values are something like 32-216. You can work around this by color correcting the footage back to 16-235.
To date, BMD has not acknowledged or admitted this is an error.
-
It’s already here:
ASUS P8Z77-V PRO/THUNDERBOLT -
Thunderbolt was developed by Intel and brought to market with technical collaboration from Apple. It was introduced commercially on Apple’s updated MacBook Pro lineup on February 24, 2011, using the same connector as Mini DisplayPort. Though the Thunderbolt trademark was registered by Apple, full rights belong to Intel which subsequently led to the transfer of the registration from Apple to Intel.[3]
-
supposedly, it’s coming, Intel was recently granted a license from Mac to incorporate Tbolt on their motherboards.
-
yes, sorry for the typo