Floh Peters
Forum Replies Created
-
No, currently not.
-
[Tom Masters] “for real? that would be pretty impressive.
Is there a specific version I need? (Media 100 suite v.2? or Media 100 i ?)
Can I use a demo to open & export these?”
Yeah. Get the Suite 2 trial version and you will be able to use it for 14 days (assuming you have a Intel Mac). And if you like it; there is a promo running right now where you can save $400 on the price of the app.
-
Hmmm, sounds more like you have a bad audio file somewhere. As far as I understand copying the audio clips to the SD timeline did work, right? Then I am not sure why it should not export if not for a bad audio clip or some other sort of problem. What happens when it fails? Crash? Or an error message?
-
Sounds like you have a damaged media file somewhere. Try opening Media 100 with the “Shift” key pressed. This way you should be able to create a new project. Does this work? If yes, look into the media folder of the non-working project to see if there is a bad media file.
-
Yes, the current codec and the current application will read these files.
-
Hey Dave,
thanks a lot for letting us know. Looking forward to a Lion-compatible version.
-
[Andy Taplin] “not that that should make a difference?”
No.
Just get over it and export via QuickTime.
-
yeah, I bet it render in something different. Locate the rendered file in your Rendered Media directory, and open it in QuickTime Player. Command-I to get the clips infos, and there you should see the used codec.
Make sure your render settings are correct, and try to rerender.
-
That´s the joy of QuickTime. Media 100 i codec uses a different RGB colorspace than Apple codecs. So if you render something in ProRes, it looks different, at least in QuickTime player. The solution is to do a QuickTime export into the codec of your choice (not as by ref or self contained), or to stay within a single codec on your timeline.
-
If you have installed 10.6.8 (see in the Apple Menu->About your Mac), then you will experience problems with the MJPEG-B-based Media 100 i codec. Apple broke this once again with this update (they tend to do that from time to time), and it is up to them to fix it again. But I guess the chances are pretty low that we will see a 10.6.9 update, since Lion is around the corner. So if you need to get some work done, you should downgrade to 10.6.7 again (reinstall 10.6.x and update only to 10.6.7 if you find a download version of it). Or if you have a backup of your system (Time Machine or Carbon Copy Cloner are your friends!!!), you can revert to a state before you installed the update.
Unfortunately there is nothing Media 100 can do about this issue, except filing a bug report with Apple, what they have done already as far as I know.