Floh Peters
Forum Replies Created
-
What codec are you rendering into? I would suggest ProRes if you have them installed
-
If these are AVC Intra the Sony XDCam Transfer won´t help. You either need the calibrated tools to work natively in AVC Intra, or of course you could use some other application (e.g. if you have FCP) to convert them to QuickTime and a codec of your choice.
-
The problem is that you cannot debayer (decompress) 4k material in realtime, it simply is not possible on todays CPUs. Therefore Media 100 opted to do a draft decompression for realtime playback. If you want to see your image in full quality, you can use the Catch Frame window. And there is a quality setting for Red decode in the Preferences if you want to render your footage (e.g. into a HD timeline, for Export,…)
-
I guess you cannot import without audio. But you can select the clips you want in your bin, and then press Command-ALT-U to unsync/remove the audio before editing the clips into the timeline…
-
Did you change anything within your setup? The whole AFP for video media always was suspicious for me; not really sure if there is anything that changed within Media 100 to break this workflow.
-
Either your footage is DVCPro or Animation codec; maybe it is both if you exported as self-contained and you mixed different formats and resolutions in your timeline…
Best thing probably would be to export your Timeline to QuickTime, with a full-raster codec like ProRes or Animation. What resolution is your timeline? 720p? 1080i?
-
Another (easy) approach is to load your clip into Red (select the clip in the Timeline, CMD-Shift-E), and apply the “BCC Film Damage” filter to it. There are various presets including black&white ones which should give you a pretty good start; including scratches, dirt, Flicker, Grain and everything else you could want to destroy your image 😉
-
When doing a slow-import into your selected format QuickTime does a frame rate conversion. Unfortunately the QuickTime conversion is not that great.
Since these days most of the cameras shoot both in 50 as well as 59.94 frame rates, you would be much better off with another camera that shoots 25p or 50i, at least if your final delivery will be 50/25. Otherwise the quality will suffer. -
[Jaeson Koszarsky] “I have noticed that the new QuickTime player (10.1) isn’t as solid as the old QuickTimePro 7.6.6. Some MOVs playback with random glitches in 10 than never appear when using Pro7. I wonder if that explains some random glitches I continue to see in M100 title track renders. “
No, definitely not. The reason for having a QuickTime X and QuickTime 7 player is that there are 2 different foundations on which there are built on. The “old” QuickTime foundation used in QuickTime 7 player, Media 100, Final Cut Pro 7 and other applications, and the new “AV Foundation”, which is more or less the base for iOS media playback, which got ported back into MacOS X, which is very capable in terms of “new” formats like H.264 and others, but does not support all the legacy things the old QuickTime foundation does provide (e.g. playback of a wide range of QuickTime codec files, export,…). QuickTime X falls back to the old QuickTime foundation if it needs to access these kind of features (codecs) or simply does not allow some tasks the old QuickTime Player (Pro) did provide
-
No, you cannot trick Media 100 into relinking to different files, since it writes a special header to each of its media files to be able to identify it always. This is very helpful in case you have several media files with the same name (Media 100 relinks always to the right one), but somewhat limiting in your situation.
What you can do is to replace the clips with the “Replace” command (Command-Drag the clip on top of the one you want to replace in the timeline), but of course you have to do this with each clip instance of the media file in your timeline.