[Wickham Strub]

Hi Eric,

You’re not doing anything wrong, it turned out to be an issue that the folks at AJA need to solve. They’ve told us that they’re on it and the fix should be in their next driver update.

[Wickham Strub]

One last thing…

What versions of M100 and Mac OS are you using? I know you’ve shared this before but it’s hard for me to find it now as we’ve hijacked this thread.

[Wickham Strub]

Thanks Rich,

I’m confused ’cause I’m SURE that was the the same group you pointed out some time ago and I’m just as sure that we fixed it.

You’re idea about it being config specific is a good one but I wouldn’t expect it on Snow Leopard ’cause I’m in SL almost exclusively these days.

Either way, I’ll take a look first thing Friday.

~Wick

[Wickham Strub]

Hey Rich,

I really thought we had covered this one a while ago.

Could you share with the rest of us which one’s aren’t working for you?

Just point me in the right direction and I’ll take it from there.

~Wick

[Wickham Strub]

Mac OS: Leopard 10.5.8 or Snow Leopard 10.6.2
As for QT, the easiest thing to do is simply run Software Update and take whatever it offers.

See the Media 100 Suite v1.1.2 Release Notes for full details.

[Wickham Strub]

It’s important to understand that although Media 100 can use hardware from AJA, Blackmagic and Matrox, we currently only have the sort of tight integration Floh is describing with AJA. We are able to take full advantage of the the AJA drivers and thus the Media 100 software “drives” the card as if it were our own custom hardware.

With Blackmagic and Matrox you will have to tweak their respective Control Panels to fit the needs of the particular projects you’re working on, same as you do with any hardware (even AJA) when using FCP.

[Wickham Strub]

Hi Mark,

Without getting into too much detail, you’ve found a bug. It appears (since you’re using ‘older’ software from both M100 and AJA) that it’s been lurking for some time now.

Our engineers working closely with AJA’s engineers to solve the problem. I will post back as soon as it’s resolved to let you know as well as anyone else following along.

~Wick

[Wickham Strub]

We try to offer any format that the hardware supports.

[Wickham Strub]

Okay… forget that last question.

I was just able to sit down and replicate your scenario and I think I may be seeing the same thing.

I am able to trim the clips out to fill the gap, at which time they play as expected. Can you do this also?

I am going to run this by Engineering now to see what they think about it.

~Wick

[Wickham Strub]

I think Floh’s right on with the ripple problem.

I can offer a bit more on the “what frame rate am I really shooting?” question.

With P2 especially, it pays to follow the media all the way down the chain to see how the camera menu relates to the frame rate of the media created and how both those details relate to the name that QuickTime uses for the codec.

I’ve got a Panasonic AG-HVX200P here on my desk. When I go through the process here’s what I find.

– The camera menu calls it “720P/60P”

– The CLIP xml for the shot on the P2 volume lists the codec as “DV100_720/59.94p” and the framerate as “59.94p”.

– After importing, Media 100 shows the codec as “DVCPRO HD 720p60” (the same name that QuickTime Pro uses. Try exporting from QTPro to see the codec names).