Floh Peters
Forum Replies Created
-
If you click on the oval button on the right upper corner of a bin you get the bin view settings (as you get with timelines and projects windows)
-
The deferred HDV acquire is explained on media100.com under Tutorials. It is a way to reduce the processor load during acquire.
-
[Gregg Michaels] “Just so I’m understanding this, Media100 is capturing everything in “studio rgb”. So when I export either by reference or self-contained, I’m still in the 16-235 color range. And when you import a quicktime, any quicktime, Media100 is assuming that your importing computer rgb- 0 to 255.”
It is more or less the opposite. Media 100 does capture into YCrCb colorspace (for all codecs), since this is the “natural” video space. Therefore you don´t have a problem mixing different codecs in the timeline.
The “Apple” codecs like ProRes and DVCProHD are RGB0-255, so if you export a by-ref file from a ProRes timeline, you still are in RGB0-255 (although the actual video data still is the original YCrCb file). Now if you import a by-ref file into Media 100, the system sees that it is not a format that is playable in realtime and therefore does a “slow import” into your selected codec. While importing it assumes that the incoming file is in RGB16-235 colorspace and therefore creates a file that has too much contrast. -
Due to the RGB level differences between different codecs, I would suggest doing exports always as QuickTime files (and not as by reference or self-contained files). I would export as e.g. ProRes, with the colorspace set to Computer (0-255) and with the correct field order for your format. The resulting file will fast-import and have the correct colorspace.
Unfortunately due to the fact that we tend to mix different codecs in a timeline the by-ref export way usually ends up with some sort of level jumps. It definitely was easier (but of course a lot less flexible) when we only could edit in a single codec.
-
This somewhat sounds like the deck/device does not work in the correct frame rate; but it is just a guess.
One thing I would try is to prepare the disc; write colorbars and black to the beginning of the disc using the “Master to Tape” Record Mode (let´s say to TC 00:58:30:00 with 1 minute of colorbars), and then try to assemble from 09:59:30:00 with 30 seconds of black as a Leader, and your record start TC set to 01:00:00:00. If your frame rate is set correctly both on your deck and your system, you should be good to go.
-
This most likely means that a part of the file (the resource fork) is missing. PC formatted drives tend not to write resource forks, but since these are an important part of the data they are needed for Media 100 (and QuickTime).
How were the files transferred to the drive? Via Network? Or via a special software, allowing Windows drives to be read and written on OSX? Maybe you should try to recreate this setup to see if there is a chance to get the files back… -
The problem was actually with QuickTime 7.6.2. The freshly released 7.6.4 still has the same problem with 13.0.3, but *should* be fine with Media 100 13.0.4 and Media 100 Suite. But you are still on your own risk…
-
This is a problem caused by QuickTime 7.6.2 and should be fixed in Media 100 V13.0.4
-
Not sure if I understand your question correctly. You want to move media files from Media 100 to FCP? Which codecs are the Media 100 files in? Media 100 i? If yes, the FCP system needs the Media 100 codecs installed. You can download them from Media 100 support. If you try to do something else, please try to explain what you want to achieve…
-
They are not supported with Media 100 Suite yet. But as Wick said, they expect to have something on this soon.