Dave Mccarthy
Forum Replies Created
-
What is the codec, frame size and frame rate of the file you’re importing? QuickTime Player’s info window can show you this.
-
If you have a program in ProRes, a self-contained export will be very close to a QuickTime export, and arguably better quality because we avoid a decompress/compress step. Color clips (or empty sections of the program) don’t exist in ProRes, so self-contained export has to create a placeholder, and for that we use a 2×2 frame in the Animation codec. (Some older applications have trouble understanding those clips, which is sometimes a reason to use the QuickTime export.) So I can’t say the files will be identical, but they should be indistinguishable when played.
-
Self-contained will export without a decompression step, so you will get the frame data as it is stored in the media (or rendered media). So this is the best way to avoid any generation loss. But if you have mixed codecs in your program, so will the export. It also can’t do the options available with QuickTime, such as changing the color space or adding timecode burnin.
h.264 is a great codec for network delivery but it’s not so good as a backup medium unless it’s your last resort. It takes a long time to encode, and it’s pretty lossy. And of course Media 100 Suite would have to transcode it back into an edit codec if you need to use that backup.
Just in case you haven’t thought of this, using an export as backup will compress all the video layers in your program to a single video track. That makes it impossible to edit transitions, alpha titles, color keys, or just about anything else an editor does.
-
Any export to QuickTime is going to incur a decompress/compress action. Most modern codecs can handle this without significant generational loss.
-
I think your use of “Mastering” is confusing us. If you want to archive the project, including its original source media, use the Collect Files feature in the Files menu. There is no need to export anything.
There was a bug in the audio export options that was fixed in v1.7.1
-
I don’t know Sony’s stance on Lion support for XDCam Transfer, but it worked fine for us when we tested it in August. We have not qualified the new XDCam Browser application.
-
We did a lot of work to improve the quality. It’s much better than before. Is it good enough? Too many variables to answer that. Maybe others can offer their opinions.
-
See my other post. 10.7.2 fixes the codec issue.
Media 100 Suite 2.1 is the only release compatible with Lion.
-
The scaler code was written in OpenGL so it can be accelerated by hardware, but the current release executes the scaler on the CPU because there were problems with Apple’s (or the graphics cards’) implementation.
-
The old “Conform” scaler used QuickTime, which was reasonably fast but not great quality. The Suite 2.0 motion editor uses a completely new scaler which has optimized code for up and down conversions. It has a realtime preview mode but it must be rendered for final quality.