![]() I found out that the audio, as i think you mentioned was messing with the sync, so i messed with it, but never got it to work all the way to perfection. So how would i fix that sync issue? if its the fault of the recording device.just get a better device.? and i apologize to all for the long time responding.i got wrapped up in something else. The format supports lots of weird timing that wouldn't be legal in other types of media file, and OpenShot probably just reproduces that when encoding to MOV, but isn't making the necessary conversions properly when it encodes to some other format. You mentioned in #1290 that the sync issues didn't occur when exporting to MOV, which makes me even more convinced about the nature of these sync issues because MOV files are notorious for causing all kinds of sync issues in various players. Sometimes even just skipping forward or backwards during playback will cause it to lose sync.) (But the same issue can show up in video players too, where the file plays fine if you start it from the beginning, but when you try to start playing from the middle it'll be out of sync. Obviously that can be a problem for editing. ![]() ![]() But correct sync is almost a side-effect, really, and that's where trouble starts because it's often only possible play the file in sync if you start at the beginning. Instead of providing the necessary information to properly sync up the files they output, they just leave weird gaps at the beginning of the file that happen to have the effect of syncing up the contents. (It's usually the audio that gets adjusted relative to the video.) Players are able to pick up on those notations and make the necessary adjustments.Īnd then there are other devices, and whatever created your source files most likely falls into this category, that aren't as well-behaved. Others know the data will be out-of-sync, so they insert the appropriate metadata into the output file that says, "delay audio by XXX milliseconds" or "shift audio forward by YYY ms" or whatever. The really good ones do the work of syncing up the streams before encoding, and still generate a correctly-synchronized output file. Plus, like I said, it's not the real framerate anyway, it's just the average across the file - meaning there's a chunk of weirdly-timed data (right at the beginning of the file, probably), followed by a normal 29.97 fps video.Ī lot of real-time recording devices (cameras, stream recorders, etc.) capture their video and audio inputs out of sync, and they deal with it in different ways. That may very well be the source of the sync problems.Įxporting at 29.20 fps wouldn't fix the sync issues, and would just create a file with a weird framerate that would probably break lots of other things. Most likely that means the input video framerate is 29.97, but there's a time adjustment somewhere that causes it to average out differently. There is no option to export at that framerate? Also, if i look at the videos that i added info, it say 29.20 framerate.
0 Comments
Leave a Reply. |