Floh Peters
Forum Replies Created
-
[J Valentine LAHEY] “Found out in 2003 that, despite being the sole remaining owner of that system, I was unable to upgrade without their official title of ownership EVEN if I traded the boards in.”
Believe me, a lot has changed between 2003 and now.
-
Yes, V12.7.1 currently only works with the V5.1 drivers
-
It would be good to see these flickers. It sounds like a digital dropout, which could be caused either by your P6000 Media 100 board or by your deck or tape. If you post a short example clip somewhere we could have a look at it and maybe by viewing the problem see what it causes it.
-
[J Valentine LAHEY] “If I’m wrong about this, and am allowed to upgrade w/o an official title to the Media 100 that I own, please let me know.”
Why don´t you simply get in touch with Media 100 sales and ask them about the possibility to upgrade? They are the ones who really should know how to proceed there.
-
[J Valentine LAHEY] “Seems like special considerations for Media 100 are colliding with demands of basic functionality for Mac; would be nice if Media 100 got a little more on it with patches/support responding to Quicktime development.”
Um, I am not really sure if you have noticed it, but Media 100 i has been replaced by Media 100 HD some years ago (somewhere in 2004, with the Media 100 V10.0 software), and still there were some updates done for Media 100 i V8 after that. Plus, usually Media 100 is the company who supports Apples newest OS releases and QuickTime versions much quicker than e.g. Apple with FCP and Avid.
You definitely should not hold your breath for a patch for Media 100 i and QuickTime 7.5.5. QuickTime 7.5 could work, but as I said it is up to you to try it. Still, since iTunes 8 does require QuickTime 7.5.5 I am not sure how much you would gain from 7.5. Maybe it is time to upgrade to Media 100 V12.7 or the newly announced V13 sooner or later? -
If you are using V8.2, you definitely should upgrade to V8.2.3a, which is downloadable from Media 100. As you can read some threads below in a post from Wick, Media 100 V8.2.3a only has been officially tested up to OSX 10.4.4 or something; we use (and still use occasionally) one V8.2.3a system on 10.4.11 as an ingest station, which seems to work fine, but we are not doing heavy editing on it. I think at this point you do have to do some tests regarding Quicktime and compatability. One thing you should do is to clone your startup HD (e.g. via Carbon Copy Cloner) as a backup, and then install whatever you want to try on the startup drive. This way you can easily revert back to your old and working configuration in case something breaks with an update.
You definitely don´t want to install QuickTime 7.5.5, since this currently breaks the Media 100 i codec. You could test QuickTime 7.5, though. But before doing work with a tight deadline make sure you have enough time to test this configuration.
And ask yourself what you will gain from the QuickTime upgrades. If there is a software that needs the newer version of QuickTime this would be a good reason to try it out, but if you don´t have a good reason you have to decide if it is worth the hassle.
-
[David Issko] “Export new movie as PR422HQ and import back into M100. New clip plays back with what I can best describe as frames with alternating 10% rise in black level then back to ‘normal’ then up again & back, resulting in a ‘strobe like’ visual effect.
“As far as I know ProRes HQ still has some issues, especially with AE. Try rendering back into ProRes 422, or try rendering into e.g. MJPEGB to see if it is a Codec problem.
-
Jack,
you are running into the usual 0-255 vs 16-235 RGB luma level range. Media 100 i codec uses a 16-235 luma range when being converted to RGB via QuickTime, DVCPro does use 0-255. Both are perfectly legal ways of handling luma ranges, and both have advantages and disadvantages. One thing you should not do for a by-reference or self-contained export is to mix formats. If you mix formats for whatever reason in your timeline, make sure to use the QuickTime export to a codec of your choice, and choose your target range depending what you want to do with the resulting file. E.g. if you want to use the files in Compressor, use 0-255. If you e.g. want to use them in AE and render back into Media 100 i codec, use 16-235. Some apps (like BitVice for example) do support both luma ranges. In BitVice the 16-235 range is called “StudioRGB” vs. FullRGb for the 0-255 range.
-
[Greg Snyder] “Help! “
Like reminding you not to upgrade QuickTime?
Go to Apples QickTime Support Page and locate the QuickTime version you want to install. In your case most likely QuickTime 7.5 for Panther. Download it.
Go to YourHardDrive->Library->Receipts and delete the Receipts for QuickTime 7.5 and 7.5.5.
Go to Macupdate.com and search for “Pacifist”. Download it
Use Pacifist to Install the downloaded QuickTime 7.5 installer package.
You should be good to g. -
V13 will work on HDx and PPC