[Paul Dougherty]

Thanks James, I get the gist of what you’re saying but that is not what I’m seeing for the (Pro CC 7.2.1) dissolve Effects Control panel. I see a kf under the mid point of the diss however I can’t move or extend it

also one would expect to see 2 ifs – one for the outgoing and one for the incoming – only see one

Paul

[Paul Dougherty]

Thanks Shane! Michael I did the upgrade to 8.3 and changed the frame rate setting for the clip and it seems the weirdness has subsided. Don’t want to pop champagne yet but the ‘point” release feature really seems to make a difference

Paul

[Paul Dougherty]

As to why I would get such a crazy mix of frame-rates, Ht Davis suggested this in my original Premiere post…

You have fallen into the OIS trap.

This type of image stabilizer is on by default on some cameras and will either speed up the frame rate or slow it down to stabilize an image. If you are on a rig or tripod, turn this off and make damned sure you check that before shooting. After shooting, if you are experiencing frame rate problems, the missing frames will be marked and the frame rate change will be as well, but only in the bitstream, not in the header. SO…. …You’ll have to transcode to a useable format. Find the base frame rate for the cameras, looks like a 25p on the 24.03, and a 24p setting on the 23.xx (25 frames and 23.9x in media encoder). You should transcode them with “USE FRAME BLENDING” so that the frame rates are filled in. This will fix any problems with the videos themselves.

Next, you’ll have to import those into premiere. I also advise you to right click the clip in project panel and Interpret the Footage to your sequence frame rate. This will flag it and play it as if at that frame rate, but conforming it to seconds instead of frames. WARNING: you may drop some frames (though not many, and usually not enough to degrade the quality unless in areas of high motion).

[Paul Dougherty]

Hi Michael,

Can’t beat getting a frame rate answer from you! 🙂 I’m on MC 8.2 and don’t see the ability to select project rate in “source settings” I can upgrade to 8.3 and try again. Since this is 720 size I will make a 23.97 proj (instead of 24)

Shane I had mentioned this job is for computer playback only (mobile app). The is no good reason for the dopey frame rate of the file I was given but you say “I’m not sure HOW a frame rate can be a decimal” aren’t these standards also 29.97 or 23.98 decimal?

Finally once I have been supplied with the original with the strange frame rate, that is meant for computer playback only (on a mobile app) doing the content edit and giving it back in the native frame rate seems like a good practice or “insurance”, not to introduce any unnecessary frame rate artifacts. But I’m guessing you guys don’t think this is a winning argument.

Paul

[Paul Dougherty]

Thanks Ht, in VLC I don’t see an “Inspector” in the window Media Information (same deal I guess) it does mention one frame being dropped.

[Paul Dougherty]

Thanks Ht,

It’s probably asking for a lot but I wish I understood why I get such different sync results with different frame rates (sources) in Premiere (just playing back and in seq with matching frame rates.. no conversion)

Again in Avid playback of the same worst case h.264 Qt file it will keep sync, though it hangs-up on a freeze a lot, releases & plays, hangs-up on a freeze a lot, repeat.

Is irregular performance something about h.264? I’m just not used to it

It occurred to me that (maybe I’m slow on the uptake) that the “peed up the frame rate or slow it down” is happening on the fly, yes? In other words do you think the frame rate is constantly changing throughout the mov? Is there a way to analyze that (monitor with metrics)? This is not a academic question as it would help explain to the client why this is taking so long to sort out.

Paul

[Paul Dougherty]

It’s strange to me that Adobe Media Encoder (in the Broadcast options) doesn’t over Quicktime. The next best alternative seemed to be mxf. I ran a test to covert the funny file to 24fpf (w frame blending) and the result was out of sync. I turned to Apple Compressor 3.5 and converted to 24fps ProRes (don’t think frame blending is an option) and it looked ok. (This is a talking head). I’ve lost so much time troubleshooting today, I think I’ll just go with Compressor.

Thanks!

[Paul Dougherty]

Wow, sounds like you’ve nailed it. I’ll try it and get back to you. Would you mind if I posted your reply to the Avid-L where I asked a variation on this question? I will credit you as “Ht Davis” or any way you’d like.

Thanks,

Paul

[Paul Dougherty]

I just verified that of two source clips with similar frames – one will play in Premiere just a little rubbery, the other about 15 frames (or more) out of sync – yet play perfectly well in the Qt player (OS 10.8.5) what gives? Then when it’s time to export the problem one’s seq from the TL – the sync problem is very much there.

Premiere says the two clips have this frame rate 24.02, however the Qt player says the problem one is 24.33 while the decent one is 23.99. (I’ve yet to get an answer why these were shot at different rates – I’m not holding my breath)

I just double checked that Avid MC 8.2 will play the problem clip in sync, however is freezes up constantly and then plays ok for a few seconds

Paul

[Paul Dougherty]

“Play side” = Source

thx