[Michael Costa]

Thanks – I’ll try that and see how it goes.

Pardon this stupid question but why is this an issue? The same card is capturing both parts into the same software app at the same time so why is keeping them in sync a problem?

Michael

[Michael Costa]

Solved problem. It was a 0.1% pull up/down issue, exacerbated by the fact that I’m a Pro Tools expert but still have my plates on for FCP. Too much PAL work and not enough mixed PAL/NTSC work in my resume!
I’ll NEVER make this mistake again!

[Michael Costa]

Thanks for the try Nick.
What’s interesting is that knowing I’ve got to get a paying job done, I downloaded demos of two expensive compression programs to see how they handle it. One of them also spat out a 320 x 240 file, but thankfully Compression Master gave me the file size I wanted.

I’m just a little worried about paying $499 for this power (even though it does so many other cool things). If its MPEG2 powers were much better than Compressor’s, then I’d buy it in a second, but all reports I’ve read don’t rate it particularly better at all.

Aside from solving my MPEG1 problem, does anyone have anything positive to say about Compression Master? Those flashing ads to the left of every Cow screen get a little hypnotic!!

[Michael Costa]

The only thing in the MPEG1 encoding box that seems to imply PAL or NTSC is the Frame Rate. Obviously I had that set to 25. The bit that’s obviously a bug is that in the summary window of Compressor where it tells you what all the settings are, it says that I’m going to get a 352 x 288 outcome, but then doesn’t give it to me.

The only thing I don’t have an answer to is that it says (in this summary window) that the pixel aspect ratio is 0.917. I assume the ratio of the MPEG1 at the end is 1. So, does this scaling account for anything?

Either way, it’s telling me I’m getting one thing, and then delivers something else.

[Michael Costa]

As I mentioned: For me it was only a monitoring thing, albeit a damn annoying one! This was because I transcoded the timeline to MPEG2. Had I been outputing the timeline to DigiBeta, I don’t know if the problem would have gone with it. I haven’t tested that yet. If it does, then we got a bad problem here – Aja?

[Michael Costa]

Absolutely confirmed here. I was about to post the same problem. Of course, it doesn’t affect your final output – it’s a dsiplay issue only but it should be fixed.