mov, since PP has an easier time with them for some reason), the video would not open at all exiting with an error: a bad public movie atom was found in the movie. Also trying to play the video with QuickTime (was changing to. though got an error along the lines of The file duration is too long for timebase. | Adobe Communityīefore searching here for issues regarding such problem, I was trouble shooting Premiere Pro (PP), in the process I tried converting, copying etc. More Out Of Sync Audio with 59.94 source files. I will use this issue in the future to link similar issues and requests to As you described TL process of combing clips, it sounds very similar to person I found on the adobe forums as they describe this issue of audio dsync occurring, when they combined (grouped) multiple 'chapters' (clips) with the audio. In this case Vegas interpolates the whole project and it works very smoothly without any desync. Now the whole project has 58.76 FPS and then I export it as 60 FPS.

I personally use Sony (or now Magix) Vegas Pro and it asks me to set the project FPS to the FPS of the very first imported video file. But then again the problem is that some consumer products like Camtasia cannot set the FPS to odd values like 58.76 FPS or something like that. The solution is to set the project FPS to exactly the same FPS of the Twitch video. So the longer the video is, the more desync there will be. Basically what happens is that it stretches the video to 30 FPS but leaves the audio stream alone resulting in A/V desync over time. Now shit gets real when Camtasia interprets the 29.97 FPS video as 30 FPS. That video has 29.97 or 58.76 FPS (and that is sometimes the case, don't ask me why). Now you import the downloaded video from Twitch. Let's say you open up a new Camtasia project and you choose either 30 or 60 FPS for your project. The most common problem is that projects of various video editing softwares run at a certain FPS.

Twitch leecher 1.4.2 vod audio desync