Floh Peters
Forum Replies Created
-
1080/24p is not supported via FireWire currently. The only option would be to use e.g. the analog or SDI inputs.
-
No, you can´t go back. The only thing you could do is to look through your backup folders if you have a old version that was not opened in V13. Or of course you could upgrade your systems to V13 😉
-
[Ben Strasser] “it would not let me upload saying that (despite the fact I believed I had deleted QT 7.5.5.) I already had a later version installed???”
Yeah, that´s why you need Pacifist.
-
Ben,
some users have reported problems with the QuickTime 7.5.5 to 7.5 downgrade under OS X 10.4.11. I only did it on 10.5.x, where it worked as expected. I am not sure if what you are seeing is part of the 10.4.11 downgrade problem. One thing you should make sure, though, is that you downloaded the correct QuickTime 7.5 version for your OS. There is one for 10.4.11 and one for 10.5.x
If you still get these pink frames, I would suggest trying the QuickTime downgrade again by carefully following this post. -
[Jim McLean] “Can we buy a key that will unlock the old P6000 to run in the G5 with version 8.2.2? Thanks for your help. Jim”
Yes you can. But not from me. 😉
You should get in touch with Media 100 sales, they can sell you an unlock key for 8.2.3 for your P6000 board. -
You have a codec mismatch on your timeline. You have acquired your video material in one codec (e.g. DV, ProRes,…), and you have rendered into a different codec (e.g. Media 100 i, Media 100 HD). The Media 100 codecs use a different colorspace when watched in RGB (QuickTime) than the Apple codecs, although they look identical when watched in their source YCrCb format via Media 100. If you have mixed codecs in your timeline you should do a full QuickTime export into a codec of your choice. Or make sure that you render into the same codec as you acquired.
Note, that you also can get into a field order mismatch. E.g. DV PAL is Lower field first, while most of the other PAL codecs are upper field first. If you export a timeline by reference with e.g. DV and ProRes clips you will have either the one or other clips with a wrong field order. Media 100 does handle all this in the background when working inside the app. -
[Jim McLean] “I have put an older p6000 card into G5 Media 100i system. I have the serial number and activation key and when I enter the activation key I’m told the number is invalid. What do I need to do to make the system work with this p6000 card. (That I know works from another system).”
The activation key is related to a software version; e.g. there is a key for V8.0 to 8.1.x, a key for 8.2,… I guess you simply use the wrong software for the key; most likely V8.2.3a when your key is only for 8.1.x
-
[Eric Nicastro] “Is there a way to transfer Media 100 projects into Final Cut Pro? We are on Media 100 version 8.2.3”
You can do it from V13, via XML export from Media 100. It will export an XML file (sort of a “Meta-EDL”), which can be read by FCP. FCP then will link to the Media 100 media files. And you also can export XMLs from FCP and import them with the media files into Media 100.
-
[Paul Friedli] “I’m testing the XML export function to move from FCP to M100 and back. The one thing I don’t understand is why it needs to render the audio and video files. I’m using the same codec/settings in FCP than in M100. It takes forever.Could the files not just relink to the existing medias? I’m using ProRes 422 (HQ)”
Media 100 does need to render the audio files in a FCP XML transfer, since it expects all audio in a timeline to be as SD2 individual mono files. So if you get a timeline from FCP with e.g. audio embedded into the video QuickTime files, or if you get stereo aiff files, Media 100 needs to create its own audio files for this. This should be relatively quick, though.
The video files should not get recreated, but still Media 100 needs to do some optimization on the file structure to play them back. This again should not take very long, but of course if you have a very long or complex timeline it can take some minutes to import the whole XML.
If you look at the source files of your Media 100 timeline, are the video files actually the same files as used in FCP, or does Media 100 really create new video files? If you really are getting new video files on import It could be that there is either a bug on the XML import path causing this, or that you are working in a size, codec or framerate not supported by Media 100, and that the files need to be converted because of this. -
[Michael Slowe] “Paul, I will I’m sure be corrected, but I understood that Media 100 do not support Pro Res. It’s an Apple codec and they haven’t been all that helpful to Media 100.”
Media 100 does support ProRes, but it does not ship the codec. It is part of the FCS2 package, though, and works nicely in Media 100. Plus, there is even a free ProRes decoder for playback only available as a free download, so if you get ProRes material you will be able to use it in Media 100 even if you do not have the FinalCut Studio package.