[Wickham Strub]

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]

Yes, and so is QT 7.6

[Wickham Strub]

The official response to this is that we never tested anything prior to v12.5 under Leopard.

The installer for v12.1 didn’t “know” about Leopard when it (v12.1) was created so… M100 will likely install and try to run but… you’re on you own.

My suggestion would be to this:

– Set up a separate Leopard install (if you don’t already have one) so that your current system is kept safe and secure

– Try running v12.1 on Leopard with all new media and projects so as not to risk anything you can’t afford to lose.

-If it doesn’t work, give the Try and Buy of v13 a go.

[Wickham Strub]

sorry about that

[Wickham Strub]

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

[Wickham Strub]

Hi Mike,

The QT 7.6 should have the same positive effect on Producer that it does on the hardware-based systems. In fact, it’s not really about the M100 applications at all. It’s always been about the MJPEG codec that’s built into QuickTime and our Media 100 i codec that feeds off the MJPEG codec to do its magic.

RE: your other question… my car is getting better gas mileage, my kids are treating me with more respect and my waistband is shrinking. But that MUST be unrelated, right?

[Wickham Strub]

Hmmm…off the top of my head…

I’d say you should cut them up as you wish in M100 then export the clips one at a time. Then, bring the multiple audio clips to whatever burning software you’re using. You should end up with separate tracks that way.

[Wickham Strub]

https://www.media100.com/support/downloads.php

At this page you will find a link to two versions of the M100 codec(s). One is for PowerPC (G5,G4) Macs and one is for the new Intel-based machines.

~Wick

[Wickham Strub]

I’ll check with the big brains on this one to be sure, but I’m thinking that once you choose the “Other” option, it’s out of our hands.

~Wick

[Wickham Strub]

I agree with Floh’s ideas about settings. I’ve done this myself in the past, archiving old “comedy” tapes my friends and I had made in idle days of youth.

While you certainly don’t NEED a full-blown NLE to pull something like this off, a real junction box makes this a lot easier.