The only way I can think of to understand what's going on would be to share the captured file here on the forum and/or with CL tech support. There have been various reports of issues like this over the years and typically PD has trouble working with some aspect of the recorded files.

If you're willing to share a recorded clip, people here can see what happens on their systems and possibly narrow down the issue or find a workaround.

You can upload the produced clip to OneDrive or Google Drive and paste a publicly shareable link to it here. See this FAQ for more details.

You should also update PD365 to the latest version, which is 20.3.2714.0

Quote The only way I can think of to understand what's going on would be to share the captured file here on the forum and/or with CL tech support. There have been various reports of issues like this over the years and typically PD has trouble working with some aspect of the recorded files.

If you're willing to share a recorded clip, people here can see what happens on their systems and possibly narrow down the issue or find a workaround.

You can upload the produced clip to OneDrive or Google Drive and paste a publicly shareable link to it here. See this FAQ for more details.

You should also update PD365 to the latest version, which is 20.3.2714.0

-----

Thanks very much for the reply; sorry it took me a couple of days to check back here.

I have now upgraded to the newer version, but haven't had a chance to check if that changed this issue or not.

Here's a Google Drive link to the files. https://drive.google.com/drive/folders/1FOhZ9eCdGLUms0BRQB_t6tcc7wDt2MXb?usp=sharing

Old horrible-quality (and boring) corporate training video from the 1980s. Checking at roughly the 8:00 mark makes the sync apparent.

The wmv is the original capture (to Windows Movie Maker) - That's in sync, though unedited.

Produce.mp4 is the produced version by PowerDirector - (only the simplest of editing - removing the blank spaces). Note that it starts in sync, but at the 8:00 mark, way out of sync.

Produce.m2ts was another PD producing attempt (following up a solution from years ago that I found elsewhere on this board to try the different format). - Still out of sync.

The other mp4 is a test using the free version of NCH's VideoPad - for whatever reason, that one stays acceptably in sync. (I had also succeeded earlier with simple editing of other videos through WMM itself; that stayed in sync, too, so it's only PD that makes it go out of sync.)

Thanks for any help or suggestions! -- Randy

Thanks very much for the source clip and for all the additional information👍

The first thing I noticed is that for some reason, MovieMaker captured this at a 3:2 aspect ratio when it should have been at 4:3. I don't know if you'd want to re-do the capture but PD doesn't have a 3:2 producing option so you'll end up with black bars along one or both pairs of edges unless you take additional steps as listed in this discussion and this one.

As to producing with PD365, I have no problems with audio if I produce to WMV (I upscaled it to 720x480). I took out the blank section and produced the total 12:00 of content, and it took 2:20 on my very fast PC. Hardware encoding isn't available for the WMV format so your producing speed will entirely depend on how powerful your CPU is.

I then tried an MPG version (352x240). That only took 34 seconds to produce, but the video is lower quality. No sound sync issue here, either.

Next I used hardware encoding to produce to AVC/H.264 MP4 (640x480). That took 3:43 to produce and the file size is more than 3x larger than the other two versions, but the sound stays in sync the entire time.

I've shared my produced clips in this OneDrive folder.

In short, all my attempts resulted in synced A/V thoughout the produced clip, which seems to be the exact opposite of your experience. I only used default profiles and didn't make any customizations, so maybe try the WindowsMedia and/or MPEG-2 formats and see if you have any better luck.

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

Quote Thanks very much for the source clip and for all the additional information👍

The first thing I noticed is that for some reason, MovieMaker captured this at a 3:2 aspect ratio when it should have been at 4:3. I don't know if you'd want to re-do the capture but PD doesn't have a 3:2 producing option so you'll end up with black bars along one or both pairs of edges unless you take additional steps as listed in this discussion and this one.

As to producing with PD365, I have no problems with audio if I produce to WMV (I upscaled it to 720x480). I took out the blank section and produced the total 12:00 of content, and it took 2:20 on my very fast PC. Hardware encoding isn't available for the WMV format so your producing speed will entirely depend on how powerful your CPU is.

I then tried an MPG version (352x240). That only took 34 seconds to produce, but the video is lower quality. No sound sync issue here, either.

Next I used hardware encoding to produce to AVC/H.264 MP4 (640x480). That took 3:43 to produce and the file size is more than 3x larger than the other two versions, but the sound stays in sync the entire time.

I've shared my produced clips in this OneDrive folder.

In short, all my attempts resulted in synced A/V thoughout the produced clip, which seems to be the exact opposite of your experience. I only used default profiles and didn't make any customizations, so maybe try the WindowsMedia and/or MPEG-2 formats and see if you have any better luck.

Again, apologies for my delay in responding; a lot going on!

Thank you very much for all the help with this. Somewhat mysterious how your results were so different than mine. But since this particular cip is so short, I'll continue using it to experiment with all of the various things you suggested - seeing if I can get the different ratio - the upscaling and producing to wmv, etc., and see what I come up with.

Many thanks again! -- Randy