[Guy Smith]

Interestingly enough, I ran across this post after I did a little experiment converting m2t files (from HDV files created by my Z1U) using Cineform NeoScene and noted an offset of about 2 frames in the converted files (audio precedes the video). For the record, the audio on the original m2t files was in sync with the video.

I thought that I would try using NeoScene on the AVCHD files from my 7D and see what NeoScene would do with them, but noted that even before I did a conversion, there was already an offset on the captures direct from the 7D using the Canon EOS utility.

Bottom line is I guess I’m going to have to start using a clapboard on all my shoots! And I thought I’d solved my sync problems with Plural Eyes!

[Guy Smith]

I also ran into the sync problem using NeoScene converting HDV footage. The audio of the cineform converted footage is ahead of the video by 2-3 frames. In contrast, the captured m2t file has its audio and video in sync.

I’ve tested this out using some HDV footage (captured shot of a standard film clapboard using a Z1U) and have put the m2t files and the converted files on the Vegas timeline. There is definitely an offset.

I didn’t change frame rates either. The m2t file was at 29.97fps and the conversion was left at the same rate.

[Guy Smith]

Don’t get too hasty on dismissing this. I also ran across the audio offset effect from NeoScene. I recently took captured HDV footage (with a Sony Z1U) and processed it in NeoScene and discovered a 2-3 frame offset (audio ahead of video).

I took some test footage (shot of a standard film clapboard) and imported in into my PC as straight m2t files. Putting them on the Vegas timeline, the audio “clap” on the m2t file was in perfect sync with the visual frame showing the clapboard coming together. After converting to Cineform however, the video frame appears 2-3 frames after the audio.

It is a subtle difference, but one that, embarassingly, a client noticed on a tight closeup on an interview. With over 20 years of video editing experience, I didn’t notice it, primarily because I believed it was in sync (after all, no pink offset in Vegas).

I’d be interested in others trying testing Neoscene and it’s conversion capability to see if they have this issue also. I’ve tried it on 2 PCs now with the same results (Neoscene 5.5.1 build 323).

I’m currently swapping emails with support at Cineform related to this issue.