Anyone seen this issue before?

[Dosx]

I have a video at 30fps I'm cutting audio to in Pro Tools

When I export the audio (not bounced) it adds exactly one frame.

The audio and video are perfectly aligned in Pro Tools
the extra frame is only there in Premiere Pro.

Any one experienced this before?

Thanks,
D

[BScout]

h264 encoding of picture. The problem with them is interpreting interframe compression codecs like that one. How a DAW or NLE wants to make them as "objects" leaves them +- 1 frame.

(Which is why I don't ask/request them from editors and if delivered, first thing is they must get converted to an intraframe codec and there must be both 2pop and tailpop sync references)

It's fine for final delivery (as long as you don't care for absolute accuracy like we do in feature and broadcast) but garbage as an editing medium.

[Dosx]

Originally Posted by BScout

h264 encoding of picture. The problem with them is interpreting interframe compression codecs like that one. How a DAW or NLE wants to make them as "objects" leaves them +- 1 frame.

(Which is why I don't ask/request them from editors and if delivered, first thing is they must get converted to an intraframe codec and there must be both 2pop and tailpop sync references)

It's fine for final delivery (as long as you don't care for absolute accuracy like we do in feature and broadcast) but garbage as an editing medium.

Thanks for your help.

I do care about absolute accuracy, especially in this case as I'm trying to make a perfectly seamless loop.

I don't work much with video though so I'm not sure what an interframe codec is, can you recommend a good format to convert to?

Thanks

[BScout]

Choose Apple ProRes or Avid DNxHD or Avid DNxHR to convert to.

Unless you need the highest resolution (which you probably don't seeing as you are starting with an mp4 which already degraded quality), Apple ProRes Proxy or Apple ProRes LT will be high enough quality (indiscernible from the original media).

On the Avid side, for DNxHD, you'll want DNxHD 36 or DNxHD/DNxHR LB. The file sizes will be manageable. (If you go to higher settings, the file sizes can grow to be massive because they are encoding for things like 10bit colour)

Interframe codecs, in simple terms, is each frame is decoded/encoded by using data from frames before and after the frame you are on.
Intraframe codecs are where each frame is decoded/encoded only from the content in the frame you are on.

So with Intraframe, you can think of each frame of video as a picture that was then compressed.

With Interframe, think of taking the first frame of video and then the second frame is created by figuring out which pixels have changed from the first frame (and only that info is stored), and the third frame is figured out from what changed from that second frame (which means knowing what changed from the first frame because that's how the second frame is figured out.) You can get higher compression that way (smaller file sizes). But this is a simplification because the compression is actually figured out from frames that happened before the one you are on and frames that happen after the one you are on.

[Dosx]

Originally Posted by BScout

Choose Apple ProRes or Avid DNxHD or Avid DNxHR to convert to.

Unless you need the highest resolution (which you probably don't seeing as you are starting with an mp4 which already degraded quality), Apple ProRes Proxy or Apple ProRes LT will be high enough quality (indiscernible from the original media).

On the Avid side, for DNxHD, you'll want DNxHD 36 or DNxHD/DNxHR LB. The file sizes will be manageable. (If you go to higher settings, the file sizes can grow to be massive because they are encoding for things like 10bit colour)

Interframe codecs, in simple terms, is each frame is decoded/encoded by using data from frames before and after the frame you are on.
Intraframe codecs are where each frame is decoded/encoded only from the content in the frame you are on.

So with Intraframe, you can think of each frame of video as a picture that was then compressed.

With Interframe, think of taking the first frame of video and then the second frame is created by figuring out which pixels have changed from the first frame (and only that info is stored), and the third frame is figured out from what changed from that second frame (which means knowing what changed from the first frame because that's how the second frame is figured out.) You can get higher compression that way (smaller file sizes). But this is a simplification because the compression is actually figured out from frames that happened before the one you are on and frames that happen after the one you are on.

Amazing info! Much appreciated.
Thank you!!