-
QuickTime 7.6 Resolves Issue with Media 100 i and MJPEG B Codecs
I got this in an Email from M100 just now
QuickTime 7.6 Resolves Issue with Media 100 i and MJPEG B Codecs
QuickTime 7.6 is now available and we are pleased to announce that it resolves the QuickTime 7.5.5 “bad video frame” issue with the Media 100 i and MJPEG B codecs. Go here to download QuickTime 7.6.
Olof Ekbergh
-
17 Replies
-
And I’m talking REALLY legacy, as in 8.2.3 running on a G4 under 10.4.11 I know, believe me if I could talk “management” into an upgrade I would be ecstatic. But I’ve been trying for years and now… well, we all know where budgets are right now.
Anyway I don’t seem to be getting the BVF errors, but all the clips in my bins are little pink rectangles. No visual reference at all. Back to 7.5 I’m afraid.
-
Are you sure you upgraded to 7.6, and not to 7.5.5? I haven´t tried it on 10.4.11, but as far as I know 7.6 should fix the problems on 10.4.11 as well as on 10.5.x
-
Yes, after the upgrade I checked in the QT prefs and it read 7.6. The pink rectangles were happening under 7.5.5 too, but I was also getting the BVF errors.
-
Olof,
Try creating a new project and bringing the bin(s) into the new project. This will force the creation of new keyframes. If they’re still pink after that, then there’s something else going on.
Let us know either way. I can dust of my M100i system and try to reproduce it here.
~Wick
-
sorry about that
-
Thanks Wick, I’ll try that when I get a chance. Right now I’m finishing a current project on it. Legacy though it may be, we still use it almost every day.
-
I’m interested to hear the results here because I have the exact same set up (M100 8.2.3 on a G4 running Mac OS 10.4.11) and am seeing the exact same problem with the pink keyframes. No other errors, but it would be nice to be able to visually identify your clips. We use our system almost daily as well- we’re a small Community Television station, and it still works really well, so it would be nice to know if I need to revert back to 7.5 again. Thanks!
Danielle DeLucia
Grafton Commmunity Television
Grafton, MA -
Danielle, for now we have backslushed to QT 7.5. As time allows I will try the “Create new project” solution suggested above, but that seems like a tedious way to handle it. I’ll post back when I have some results.
-
Hey Marty,
Don’t bother, stick with QT 7.5
I have tried EVERYTHING I can think of and I’m seeing the same thing.
What it boils down to is this…
Although the new-generations of HD-capable Media 100 systems support legacy projects and media, they are FAR from the old Media 100 i systems. It appears that QT 7.5 broke M100i in a different way than it did the new systems. It sure looked like the same thing to everybody (including us) but, obviously, there’s more to it. Sadly, I think I can safely say that it’s NEVER going to get “fixed”.
It’s frankly a miracle that it took THIS long for the QuickTime updates to “break” the old Media 100i systems.
The last QT version that we could officially vouch for, QT v7.0.4, was released in January of 2006. It took 15 more updates to QuickTime before Media 100 i was shaken. That’s nearly THREE years without changing a single line of Media 100 i code. To the engineers both current and past who still lurk on this forum (you know who you are), you should feel proud… or lucky… or both.
The good new is, as you noted, M100i still works like a champ with QT 7.5 under it. So all is not completely lost.
-
[Wickham Strub] “Although the new-generations of HD-capable Media 100 systems support legacy projects and media, they are FAR from the old Media 100 i systems. It appears that QT 7.5 broke M100i in a different way than it did the new systems. It sure looked like the same thing to everybody (including us) but, obviously, there’s more to it. Sadly, I think I can safely say that it’s NEVER going to get “fixed”. “
I think the main question is: is the MJPEG B problem fixed only in QuickTime 7.6 for Leopard/10.5, or also in QuickTime 7.6 for Tiger/10.5. Since the Media 100 i systems are running Tiger, it could be the case that the MJPEG B problem still exists for Media 100 V12.x systems, which run under OSX 10.4.11, and that the problem was only fixed for systems running on OSX 10.5?!?
Reply to this Discussion! Login or Sign Up