[Wickham Strub]

Sacha,

I know this suggestion will only get you deeper into the problem you’re facing but…

You COULD install the trial version of 13 on the other system and use that.

~Wick

[Wickham Strub]

Hey Elliott,

How have you been?

The best you can do to solve a “dueling color spaces” problem like this is to try to match up the codecs. I’m guessing that you cannot re-capture the FCP media, so try to re-acquire the M100 media to the same codec as the FCP stuff.

As always, do a couple of short tests before diving all the way in.

~Wick

[Wickham Strub]

Hi Paul,

First off, I’m a little unclear why exactly you’re unsyncing the audio tracks. Perhaps that’s not part of the puzzle, so let’s ignore it for now.

I haven’t actually heard of THIS specific problem, but…

It sounds like it ‘could’ be related to a bug that we’re working on where attempting to re-acquire audio that has been “remapped” in the timeline results in the audio simply NOT relinking. Based on the workaround we’ve developed for that , try the following for your case:

– If you’ve got a clip you want remap the audio for, double-click on that clip in a bin (it MUST come from a bin) to load it into the Edit Suite.

– Click the Track Remapping button and make the changes there (small tip: you don’t have to close this window for the change to take effect).

– Bring the clip from the Edit Suite to the Program.

Now, do whatever it is that you’ve been doing that causes the crash and see if it still happens. We’ll all be away till Monday for the holiday so I can’t test this myself till then. I’m hoping that the fix we’re working on for the re-acquire problem will also “fix” your problem too.

Let us know how it goes.

~Wick

[Wickham Strub]

“Our top story tonight: Generalissimo Francisco Franco is still dead.”
Oh, funny Chevy Chase, how we miss you. But I digress….

Yes, QT 7.5.5 still “breaks” the M100i and MJPEG-B codecs.

There have been reports of a fix coming in a future release of QT:
https://www.macrumors.com/2008/10/22/apple-seeds-quicktime-7-6-to-developers-no-h-264-acceleration-yet/

These are rumors I can neither confirm nor deny.

~Wick

[Wickham Strub]

Hi Mike,

That 12.7 link points to the 12.7.1 disk image.

~Wick

[Wickham Strub]

Hi Marc,

Bringing AVIs into M100 (or anything else on the Mac, really) can be tricky. Having said that, what version of M100 are you using? We did recently have a problem importing some movies that weren’t exactly 720×486, but that problem was with the horizontal scaling. That shouldn’t be the issue with the footage you’re describing. I would shy away from AVIs and try MOVs instead.

In regards to your original question, I would definitely request 720×486.

Where the codec is concerned the general rule is that if QuickTime can play it, M100 can import it. Some codecs, like the ones available in M100’s Media Settings (as well as a few others such as Animation) can be “quick imported”. Bringing them into the bin almost instantly.

The most important concern is that you are aware of the color space of the codecs to import vs. the color space of the media in your timeline. Media 100 can mix and match YUV and RGB color spaces in real-time just fine out to a deck or an external monitor. However, if you need to export the program, there can be only One (color space, that is). If you export a timeline with both color spaces in it, one of them will either look washed out or crushed.

The only way to be sure this won’t be an issue is to do a quick workflow test with a short, sample Program. It’s best to import files that already match the color space of your existing media, but you can also switch the color space in M100’s Import dialog if need be.

[Wickham Strub]

It sounds like Dean is all set now but I just want to throw in one more tidbit for the lurkers out there.

Last week I spoke to someone with odd behavior after backing up his QT. We noticed that, although the M100i codec was working again, his QT still reported as v7.5.5.

It took some investigating on his end, but finally the user realized that he had used the QT v7.5 installer for the wrong OS. (Chris did this early on and his Mac wouldn’t even boot).

So…be careful when choosing the QT v7.5 installer for the Pacifist procedure described here: https://forums.creativecow.net/readpost/4/862351

[Wickham Strub]

It’s definitely NOT about the junction box. Media 100 i will work just fine without one.

I like Floh’s idea about the DV Option “daughter card”. It’s the small, square card that says Sony on it with a long cable running to the FireWire port on the P6000.

Try ensuring that the card is seated properly or, if you don’t need DV, just try removing the daughter card altogether.

[Wickham Strub]

Yeah, well… Floh was quick on that one ’cause he’s the one that found the bug for us. It’s actually a bug that’s been lurking in the code for some time now. Strange how something can be out there like that for a while and then, all of a sudden, a bunch of people stumble onto it at the same time.

A permanent fix for it should be rolled into an update sometime soon.

~Wick

[Wickham Strub]

Hi Jeremy,

**The following assumes you are using at least v12.6 of Media 100 with the “retail” driver from AJA**

The only way to control this that I know of is with the AJA Control Panel (in the Applications folder). Under the “Control” tab you can make choices about what the card puts out when it’s not being used.

~Wick