Floh Peters
Forum Replies Created
-
[Jaeson Koszarsky] “If I test the waters of OSX 10.5 with Media100HD 11.5.1 and it doesn’t work, what’s the quickest/easiest method for reverting OSX to it’s the early 10.4.11?”
I would get a 2nd internal HD for, I don´t know, maybe $40, and then clone your boot drive onto it via Carbon Copy Cloner. Then boot from the copy to make sure it is okay, and then do the 10.5 upgrade onto this drive. This way you can switch back to your 10.4.x installation immediately if something goes wrong there. I always recommend having a 2nd, working startup partition in case some installation damages your main boot drive somehow and makes your system unusable otherwise anyway.
-
[Robin Hamilton] “All the clips look different and have different reported datarates.”
The datarate in the Bin is just an average calculation, so it is not really an issue you should worry about. As you probably have seen e.g. during acquire, that even for the ProRes codecs there is a dynamic range of datarate, and not a fixed data rate. So the codec simply did a little bit different compression on each pass.
Regarding the different looks: When you do a file import into Media 100, it currently expects non-native Media 100 clips to be in the 16-235 colorrange. So if you e.g. import a file that you have exported as a by reference clip from a ProRes timeline, the re-imported clip will be too contrasty. Currently there are only some workarounds for this if you use the File->Import dialog. The Scale out of Range RGB values checkbox is no solution, unfortunately.
The AVCHD Import “knows” that the incoming files are in 0-255 RGB colorspace, so it interprets them correctly on import. The resulting clips should be as they were intended to be.
-
[Jaeson Koszarsky] “In the RENDERED MEDIA folder within the project’s MEDIA folder, there are files ending in .HAL and .RTI, is one of these a BorisRed project file? “
No, the “project” file is integrated in the Media 100 timeline file. So you cannot access your Red projects that you have created in Media 100 from the standalone Red application, as long as you did not save them as projects from within Red (when accessing it from Media 100). You could save your project and then modify it from within the Red standalone app, but you would need to put them back into your timeline again since there is no linking between standalone Red projects and the one within your Media 100 timeline.
-
[Peter DeArmond] “Yes, it’s there, but it’s grayed out. Always.”
The full ProRes Codec is part of FinalCutStudio. The ProRes decoder for Playback is part of QuickTime. So I am guessing you don´t have the full ProRes codec installed on your system.
-
[Doug Calhoun] ” So if, like Peter, I simply import the footage without selecting “Import Media to the Media Standard and Codec” it simply imports as Media100 HD?”
No, it uses whatever codec you have selected in the Media Settings. 30% sounds more like ProRes or probably even DVCProHD than Media 100 HD codec; Media 100 HD codec is uncompressed, which probably is ~15 times bigger (1500%) than your original files. If you want great quality at low data rates you should use ProRes.
-
Media 100 does not support XDCam files natively (they are a flavor of MPEG2 interframe compression, and currently Media 100 does not support any interframe compressed material). So it is normal that the file get converted on import into a codec of your choice. If you send the XML back to FCP, you either can send your media files with it (making it easier in case you have to get it back again); or the FCP operator could try relinking to the original XDCam files (not sure if this will work 100% reliable, though).
-
For AVCHD the import is a 2 step process. First the clips get rewrapped from MXF into QickTime, then the QuickTime gets imported into Media 100 as whatever codec you chose. Sounds like your clips should be ProRes in the end. Not really sure what your problem is; is it the fact that the clips via ClipWrap look different than before??
-
[David Jones] “I shot test footage with the camera set for 720P and then set up my Media 100 to acquire 720P footage. The problem appears to be the JVC flavor of 720P is 30 fps while Media 100 Producer’s (version 13.0.1 for PPC) idea of 720P is 59.94 fps or 60 fps except that the 60 choice is not active – it is grayed out.
“Hmmm, the 720p formats are usually 59.94, even if it is called 30p in the camera. Have you tried acquiring via the 59.94p setting? Have you checked if there maybe is a downconverter for FireWire turned on in the camera? I guess you try to acquire via FireWire…
-
How does it fail? Any error message?
-
The camera records in MPEG2@35MBit. MPEG2 editing currently is not supported natively in Media 100, therefore the transcode to e.g. ProRes. ProRes is a pretty good editing codec, so you should get a brilliant image quality at relatively low data rates.