[Jeff Carbonneau]

Thanks Todd! I don’t have a CRT. Just LED. Also, just to clarify, this might be an intentional mistake on my part but I do in fact upload MPEG2 progressive to the stations and they’ve been accepting it for years now. My steps are the following…. shoot 23.98 Prores HQ, edit 23.98 Prores HQ, render out self-contained movie, bring it into compressor, choose mpeg2, 1920×1080, 35mbps, 29.97, when I jog the render through frame by frame the pattern is that is duplicates every fourth frame on the fifth and so one… This looks the best to me and I’ve never had a station question it. I just did do the interlace test and saw the pattern even on the LED. I see what you’re talking about. Embarassed to say I should’ve seen this years ago. To the eye the progressive render always looked better so I always sent that. It’s weird that I’ve never been called on it. Anyways, thanks for your help Todd.

[Jeff Carbonneau]

Thanks for the insight Todd. thats exactly the method I do with one exeception. I make my 24p master, bring a self contained movie into compressor or ame and do a 1080 mpeg 2 around 40mbps. so I’m in the process of switching from compressor to ame for my compressing duties as my tests yield faster better results. When I had my mpeg2 setting in compressor I could’ve sworn it was set to progressive on the 3:2 pull down 24 to 30. When did my test today in ame progressive looked much better the interlaced upper. I did 2 tests one with progressive and one with interlaced upper. Progressive didn’t have the weird frame blending that the interlaced version had. Is it possible that the stations have been receiving progessive and converting it? Maybe the compressor version was interlaced I’ll have to check. Anyways, I do have to say any sort of frame blending looks too blurry and takes sharpness from any moving images. Quick thoughts on that and thanks again.

[Jeff Carbonneau]

i’ve repaired the permissions… haven’t trashed the prefs yet… but could it be as simple as that… i’ll try it , but i never changed the prefs to begin with

[Jeff Carbonneau]

Wow… the clarity is much better on the VLC player and more like it looks natively, but it still very stroby… i’m mean i shot it in 24F on my XLH1, but then made my sequence 29.97… i mean it’s stroby (because of the 24) in playback on FCP, but the MPEG seems to really stroby, like there’s a frame rate issue… this wouldn’t have anything to do with how i shot it right? because the canon doesn’t shoot native 24, it still shoot 60 fields a second to make it look like 24… i don’t know, i just seems like it’s stuttering with the frames on playback in VLC, although the clarity is where i want it… any thoughts on the stuttering problem, and do you have reccommendation on the bit rate and field dominance?

[Jeff Carbonneau]

My mac: 2x3GHz Dual-Core Intel…. and 4GB of RAM
Quicktime Version 7.6.4

I’ll see if VLC is available for MAC download

[Jeff Carbonneau]

none that i can find

[Jeff Carbonneau]

sure… it’s connected via Blackmagic Multibridge Pro HDMI out

[Jeff Carbonneau]

i think it must be how FCP and quicktime view the camera strictly as a hdv connection and doesn’t recognize it as dv also… what i’ve had to do is take the tape that i shot 4:3 ntsc xlh1a and load it in through my xl2. what a pain… hopefully this is a bug that gets worked out, because loading sd footage from the xlh1a is necessary when doing strictly sd projects… i guess the alternative would be to shoot it all in hd, bring it in prores and downconvert in final output…