[Michael Trenton]

Have you rendered the AE comps in the Premiere timeline?

[Michael Trenton]

Yes Bandicam was indeed set to record at a fixed framerate so I don’t expect that to be the issue here, particularly not when both Final Cut Pro 7, Compressor and Squeeze were all able to handle the footage.

I think the really weird thing is that even when I converted the footage to DNxHD through Media Encoder then Premiere was still not able to play back the correct sound. So even when I put a converted DNxHD clip in the timeline, unlinked the audio and video and manually synced up a part of the audio with the clip then Premiere would still not allow that part of the audio to ‘remain’ there, but rather play back some different part of the audio instead (hope that explanation made sense).
So to me it seems the problems Premiere is having is with the audio. Premiere seems to just play back random parts of the audio. What really baffles me this can still happen even after converting to DNxHD (and again, converting the same clip to ProRes through Compressor or DNxHD through Squeeze – no problems whatsoever).

It would be interesting to know is whether Adobe in general isn’t capable of editing and converting MotionJPEG correctly or whether Adobe only has a problem with the MotionJPEG coming out of Bandicam. I think I’ll do a test on this by exporting some MotionJPEG from a different program and see how Premiere handles that.

[Michael Trenton]

I’ll look into it and see if that is the case that Bandicam is recording with variable bitrate, but it’s not just that the audio is out of sync it’s a matter of Premiere playing back audio from a completely different part of the clip, So let’s say if I’ve dropped a 30 minute clip into my timeline and play back the beginning then the audio that Premiere plays back is from the end of the clip or some other random part of the clip.

And since both Apple Compressor and Sorenson Squeeze are capable of handling and converting the footage correctly it’s still weird that Adobe can’t even if a variable bitrate should somehow be the cause of this.