The only thing that makes sense is a cache problem, but I don't know why it would come back unless you keep using Render Preview (or might have the preview screen resolution set to Ultra UHD and PD is automatically pre-rendering to give you smooth playback).

Either way you'll see a thin green line directly above the timeline when that's occurred. You may have to create a new project, delete all the cached files then close PD to get rid of them all. Double check that they're all gone when you reopen the current project.

As a test for what might be happening, don't split any clips when you need to mute a section. Hold down the Ctrl key and click on the clip's volume level (horizontal very thin green line that runs the horizontal length of each clip) to add 4 keyframes starting where you want to mute the audio. Next drag the two middle ones to the bottom edge of the clip to mute just that section.

I assume that would work normally whereas splitting the clip is what seems to trigger the issue.

Quote Power Director 365 19.3
Win 10
file was originally created in 14 but has since been resaved.
I have encountered this is the past but just worked through it as best I could but I'm looking for fix, not a workaround like I have already. Though this is the first time in 365.

I'm working on this one video where something's happened to the audio. I did a bit of sarching on it, but I'm not exactly sure how to describe the symptoms accurately enough to find appropriate answers:

If I split out a small section to mute. When muted, and I go back to check if I got it all, it will still play the audio even though it shows as muted.
Secondly, if I split and delete portions of the video, the audio of the remaining clip starts at the point of the clip I just deleted. basically putting the audio out of sync by the duration of the clip I just cut out.

If I close and open the program and reload the file, everything gets sorted properly again without me doing anything.
I thought maybe the cache files were corrupted so I deleted them and then reopend the file and let the cache files be built again, but its still the same problem.

any ideas? tia

I've seen the same/similar issues with highly variable framerate and/or bitrate files. Basically, the split points are not correct. If that describes your source video file, I'd convert to a more conventional constant framerate file with typical audio in HandBrake or potentially even PD if you make no edits and produce to a new format and use this new produced file for editing.

Jeff

Quote
As a test for what might be happening, don't split any clips when you need to mute a section. Hold down the Ctrl key and click on the clip's volume level (horizontal very thin green line that runs the horizontal length of each clip) to add 4 keyframes starting where you want to mute the audio. Next drag the two middle ones to the bottom edge of the clip to mute just that section.
.

To be clear, I'm just splitting a video clicp and muting the audio. I noprmally split because sometimes I decide to go back and try to edit the audio if the mute makes things overly awkward. I followed the instructions and used keyframes and muted a section of audio. The problem still occurred. I had to close the program and reopen for the audio to be muted.

Quote

I've seen the same/similar issues with highly variable framerate and/or bitrate files. Basically, the split points are not correct. If that describes your source video file, I'd convert to a more conventional constant framerate file with typical audio in HandBrake or potentially even PD if you make no edits and produce to a new format and use this new produced file for editing.

Jeff

I hadn't thought of this. The project is based off a series of 45mbps 2500x1600 60fps MP4 files recorded from Nvidia Shadowplay with a stereo 48hz 192kps AAC audio track. I have been using a video of TV static with sound for a couple of transtions and looking now it's 2.4mbps 1280x720 30fps with 44khz 128kps audio. I would have thoughta video editor would bbe able to make that leap, and maybe it can....

So I decided to try copying the entire project from the original file into a new file (ctrl c, ctrl v), and boy did all hell break loose. I couldn't watch the video in the preview video most of the time. Some parts of video I deleted showed up. Some part of the video were completely missing audio even being shown at all. When I saved it and tried to reopen it I got some error about incorrect something or other that I only ever recieved once (I didn't record the exact words). It had stripped out further sections of the video / audio....

I'm going to consider this file cursed (corrupted) and start over from scratch and pay closer attention to the bitrates and such for all supporting videos I use like this static one. I've just recently edited four other video from the same timeframe and not had any of these issues. For all I know this might have bee a file where I originally encountered the problem back when I was using version 14.

I'll start over and post back if I encounter the issue again...

Nvidia Shadowplay captures can be very challenging for many editors, especially with maintaining proper audio. You say 60 fps, but Shadowplay uses a highly variable frame rate during capture. It's not unusual to see 3-4fps to 60fps in the same file depending on what was being recorded. That's what I implied in my original post, files with highly variable frame rates. Furthermore, not all files are the same because of this capture technique so some may edit fine, while others have trouble.

If you still have issues with a file going forward, I'd convert one with HandBrake and see if you have any better editing luck. PD editing is not real accommodating of these highly variable fps files, it works best with basic old school near constant fps files which HandBrake can create.

Jeff

So I spent the time and redid the video from the basic template I use for all my videos. I used the same source files and I didn't encounter the problem. Not sure what caused it but it seems the file is indeed cursed. thanks for your help trying to figure out what the problem was.

At least I learned the shadowplay does that "variable framerate" thing. I was unaware of variable framerates at all. Are Shadowplay files the only place you'd encounter them? Is there any way to tell if a file actually has a variable rate in it? I assume the variable framerate occurs when the game itself experiences a drop in framerate? If thats the case I probably dont encounter it very much with my videos I'm working on because the game I was recording came out in 2002 and I was playing it in 2017 so even at max settings my latest gaming rig had no issues rendering it.