Typically you may see a lag when editing as your system might struggle to preview the timeline smoothly with certain edits, but none of that lag should end up in a produced version.

Try taking a careful look at your timeline and see if you can locate the content when you first notice the A/V sync issue. Is it with a specific clip, or maybe a specific kind of edit or FX that was applied there?

You can also try producing without using any GPU hardware. That means unchecking the Fast video rendering technology: box on the Export page. You should also uncheck the Hardware decoding option from Preferences | Hardware Acceleration. Note that it will take longer to produce the video.

If you'd like more assistance, please follow the steps in the Read Me Before Posting guide and attach the DxDiag test results so we can see the exact technical details of your system.

Quote First off my hardware:

i9 12900HK
32GB of Ram
3070ti GB

I have had zero issues rendering 4K files with this laptopfor the past year through multiple versions of PD ( some issues with the Nvidia AI denoise algorithim but those worked themsleves out in a subsiquent update) fast forward to my current issue...

I editied together a 42 min video (output files were in 4K24 from my A7iii as they always have been) when editing things together on the timeline i would lose AV synch. (the audio would be about a second ahead of the video after about a min or so) pausing the video and hitting play would automatically fix the problem while editing ( until the issue would perodically creep up again depending on the length of the clip i was working on) I know in the past sometimes weird things like this would happen but they would always work themselves out in the render... not so this time. I tried outputting in h.264, h.265, and at various resoloutions to no avail. this was never an issue until the update just before the July 26th one..

can anyone shed some light on what might be going on? NOTHING on the laptop has changed... I would gladly roll back to a previous version of PD if someone could guide me as to how ( I dont think thats an option... the Application manager sees to it...) I have tried reinstalling my GPU drivers, running all my system updates, etc. I was also able to duplicate the issue on my office PC (running an i5 8500, and a quadro p600) which leads me to believe something happened im the software... Also there used to be an option to optimise the GPU settings that is now gone...

Can anyone PLEASE shed some light on this issue? I have some time sensitive projects that NEED to get done, and If i cant get this figured out I guess it's time to start learning Premiere Pro... I can help but feel like a beta tester for Cyberlink after this last update.... any help would be much appreciated!

You never indicated if your office computer replicated on the exact same project or just the same source video.

Since produced sync issue occurred on both platforms, my guess your source A7iii video might be different than prior. Any chance you maybe had the shutter set to auto, which maybe you didn't do with other video, or maybe the scenes were rather different, if so, it's likely it is a VFR video. If source is highly VFR, it's likely PD21 can't handle it. Try to convert with HandBrake or similar utility while retaining similar resolution, similar bitrate but use a CFR and see if you have issue with this converted video in PD21.

Jeff

Hey there!

thanks for the responses. yes the same issue happened on both machines at the same timeframes in the clips. ( i also played the clips outside of PowerDriector and they don't exhibit any issues at all. It's only when edit them in the timeline, or render them that i get the issue. I will try to produce a render just using the CPU alone. and see what happens, thanks for that advice. FYI, I have not changed the settings on the A7iii. I am recording at 4K@24FPS with a 100Mbit rate...

Optodata, i used to run PD on a microsoft surface, and while i would bring it to it's knees in the timeline view, the renders always turned out perfect. Hope this info helps folks.

I'll report back after trying. thanks! Also, is there specific info from DXDiag you need?

Quote I'll report back after trying. thanks! Also, is there specific info from DXDiag you need?

The entirety is useful. FYI there's nothing personal in there other than possibly a name you've given your PC right near the top.

so 6 hours later the render finished without any hardware acceleration... I would normally experience an AV sync issue about 30- 40 seconds in and wasnt there! however the issue crept up shortly thereafter and the problem still persists...... please see the attached DxDiag file. I appreciate any insight you can offer me.

I recorded more footage for a project today, and it is experienceing the same exact issue... I was able to dust off my Microsoft Surface that had been sitting for the past year ( running an older version of PD 365) I was able to load the clips onto there, and i am able to edit them without issue... So i think i've narrowed it down to being the latest PD update?

I appreciate your input.

Quote so 6 hours later the render finished without any hardware acceleration... I would normally experience an AV sync issue about 30- 40 seconds in and wasnt there! however the issue crept up shortly thereafter and the problem still persists...... please see the attached DxDiag file. I appreciate any insight you can offer me.

I recorded more footage for a project today, and it is experienceing the same exact issue... I was able to dust off my Microsoft Surface that had been sitting for the past year ( running an older version of PD 365) I was able to load the clips onto there, and i am able to edit them without issue... So i think i've narrowed it down to being the latest PD update?

I appreciate your input.

There will always be something noticed in a dxdiag, from BIOS being outdated, recent crashes and need to run system file checker. But, since replicated on another machine and not seen on a third with a different PD version, I rather doubt something specific to your Raider laptop.

As the issue you describe sounds a lot like VFR and/or VBR issues, and if a PD365 issue, highly unlikely it would be addressed in a reasonable amount of time. I'd probably try the workaround of converting a file with HandBrake to constant 24 fps, same resolution, constant and similar or better bitrate and see if that at least can get you to an edited produced output with P365 without the glitch.

It may help to attach the text file from MediaInfo or the online version https://mediaarea.net/MediaInfoOnline of your source video file and the converted file in its entirety.

Jeff

Jeff, I assume you are referring to Variable Frame Rate or Variable Bit Rate? for the files coming from the A7iii? I have not changed any settings in the camera and to my knowledge this is not something that the A7iii can do, although i could be entirely wrong!

I have attached screenshots of the properties from the A7iii file, as well as the PD output file im struggling with. Please let me knwo what additional info you may need.

Because I was able to duplicate the issue on a seperate but less powerful system, and the fact that PD 20.4.2812.0 Is working on a significantly less powerful machine with these files, to me at least anyway would indicate an issue with the PD update.

A short term fix for me would be if i could roll back the last 2 updates, (the one from July 26th, and the one a week or 2 prior to that. that would have me back to a version where all of my hardware rendering worked, as well as my nvidia AI denoise, etc... does anyone have any idea if this is possible?

I have also started a trouble ticket with Cyberlink, but if the feedback from the forum is any indication, it sounds like the wheels move slow...

Anyway I appreciate any continued support or advice you can offer!

Thanks!

Reg

Quote

There will always be something noticed in a dxdiag, from BIOS being outdated, recent crashes and need to run system file checker. But, since replicated on another machine and not seen on a third with a different PD version, I rather doubt something specific to your Raider laptop.

As the issue you describe sounds a lot like VFR and/or VBR issues, and if a PD365 issue, highly unlikely it would be addressed in a reasonable amount of time. I'd probably try the workaround of converting a file with HandBrake to constant 24 fps, same resolution, constant and similar or better bitrate and see if that at least can get you to an edited produced output with P365 without the glitch.

It may help to attach the text file from MediaInfo or the online version https://mediaarea.net/MediaInfoOnline of your source video file and the converted file in its entirety.

Jeff

Quote Jeff, I assume you are referring to Variable Frame Rate or Variable Bit Rate? for the files coming from the A7iii? I have not changed any settings in the camera and to my knowledge this is not something that the A7iii can do, although i could be entirely wrong!

I have attached screenshots of the properties from the A7iii file, as well as the PD output file im struggling with. Please let me knwo what additional info you may need.

Because I was able to duplicate the issue on a seperate but less powerful system, and the fact that PD 20.4.2812.0 Is working on a significantly less powerful machine with these files, to me at least anyway would indicate an issue with the PD update.

A short term fix for me would be if i could roll back the last 2 updates, (the one from July 26th, and the one a week or 2 prior to that. that would have me back to a version where all of my hardware rendering worked, as well as my nvidia AI denoise, etc... does anyone have any idea if this is possible?

I have also started a trouble ticket with Cyberlink, but if the feedback from the forum is any indication, it sounds like the wheels move slow...

Anyway I appreciate any continued support or advice you can offer!

Thanks!

Reg

Yes, VFR and/or VBR. The issue occurs randomly with PD for years and I'm not implying one changed any camera settings. As mentioned prior, scene changes can often trigger, conversion a simple workaround.

Those windows properties are not real useful for video, suggested use of MediaInfo of source and HandBrake files provides many more relevant details.

Jeff

Thanks for the feedback Jeff. indeed you are correct the file from the Sony is indeed VBR:

General
Complete name : C0204.MP4
Format : XAVC
Codec ID : XAVC (XAVC/mp42/iso2)
File size : 7.98 GiB
Duration : 11 min 43 s
Overall bit rate mode : Variable
Overall bit rate : 97.5 Mb/s
Frame rate : 23.976 FPS
Encoded date : 2023-07-16 03:10:44 UTC
Tagged date : 2023-07-16 03:10:44 UTC
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L5.1
Format settings : CABAC / 2 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 2 frames
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 11 min 43 s
Bit rate mode : Variable
Bit rate : 95.7 Mb/s
Maximum bit rate : 100.0 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.481
Stream size : 7.84 GiB (98%)
Encoded date : 2023-07-16 03:10:44 UTC
Tagged date : 2023-07-16 03:10:44 UTC
Color range : Limited
Color primaries : BT.709
Transfer characteristics : xvYCC
Matrix coefficients : BT.709
Metas : 3
Codec configuration box : avcC
Audio
ID : 2
Format : PCM
Format settings : Big / Signed
Codec ID : twos
Duration : 11 min 43 s
Bit rate mode : Constant
Bit rate : 1 536 kb/s
Channel(s) : 2 channels
Sampling rate : 48.0 kHz
Bit depth : 16 bits
Stream size : 129 MiB (2%)
Encoded date : 2023-07-16 03:10:44 UTC
Tagged date : 2023-07-16 03:10:44 UTC
Other
ID : 3
Type : meta
Format : rtmd
Codec ID : rtmd
Duration : 11 min 43 s
Bit rate mode : Constant
Encoded date : 2023-07-16 03:10:44 UTC
Tagged date : 2023-07-16 03:10:44 UTC


Here is the output file:

General
Complete name : Hot Tub Heater Repair_2.mp4
Format : MPEG-4
Format profile : Base Media / Version 2
Codec ID : mp42 (MSNV/isom/mp42)
File size : 27.4 GiB
Duration : 42 min 53 s
Overall bit rate : 91.4 Mb/s
Frame rate : 23.976 FPS
Encoded date : 2023-08-02 05:11:15 UTC
Tagged date : 2023-08-02 05:11:15 UTC
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main@L5.1@High
Codec ID : hvc1
Codec ID/Info : High Efficiency Video Coding
Duration : 42 min 53 s
Source duration : 42 min 53 s
Bit rate : 91.2 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Variable
Frame rate : 23.976 (24000/1001) FPS
Minimum frame rate : 23.962 FPS
Maximum frame rate : 23.981 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Bits/(Pixel*Frame) : 0.459
Stream size : 27.3 GiB (100%)
Source stream size : 27.3 GiB (100%)
Language : English
Encoded date : 2023-08-02 05:11:15 UTC
Tagged date : 2023-08-02 05:11:15 UTC
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
mdhd_Duration : 2573485
Codec configuration box : hvcC
Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : 2 / 40 / mp4a-40-2
Duration : 42 min 53 s
Source duration : 42 min 53 s
Bit rate mode : Constant
Bit rate : 205 kb/s
Nominal bit rate : 192 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 46.875 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 62.8 MiB (0%)
Source stream size : 62.8 MiB (0%)
Language : English
Encoded date : 2023-08-02 05:11:15 UTC
Tagged date : 2023-08-02 05:11:15 UTC
mdhd_Duration : 2573479


I think i know the answer to this, but i assume that I can't take the file that PD outpu, run it through handbrake, and expect the AV sync issue to be resolved? I dont want to have to run 30+ clips through handbrake just so I can retain functionality in PD that was already there....

Thanks for the speedy feedback, I have been losing sleep over this for the past week trying to get this figured out...

Thanks!

Reg

Quote

Yes, VFR and/or VBR. The issue occurs randomly with PD for years and I'm not implying one changed any camera settings. As mentioned prior, scene changes can often trigger, conversion a simple workaround.

Those windows properties are not real useful for video, suggested use of MediaInfo of source and HandBrake files provides many more relevant details.

Jeff

Quote Thanks for the feedback Jeff. indeed you are correct the file from the Sony is indeed VBR:

I think i know the answer to this, but i assume that I can't take the file that PD outpu, run it through handbrake, and expect the AV sync issue to be resolved? I dont want to have to run 30+ clips through handbrake just so I can retain functionality in PD that was already there....

Thanks for the speedy feedback, I have been losing sleep over this for the past week trying to get this figured out...

Thanks!

Reg

You might try attaching the output in the future as was suggested.

HandBrake can't fix the jittery output file, yes, one would process the input files.

You might also try to use PD's "Profile Analyzer" to create similar AAC (H.264) output profile for your input streams vs your transcode conversion to HEVC (H.265). This output may not have the glitch. I know, you shouldn't have to, but with PD sometimes you have to do things to get glitch free output.

Jeff

I did use the profile analyzer, but alas, no dice. I will give Handbrake a shot for a clip or 2 tonight and see if that helps. I genuineley hope i can roll back to a version from a few weeks ago so I can get these projects completed on time.

Any suggestion of what settings i need to use in handbrake given the file from the a7iii?

Thank you again for all of your suggestions!

Reg

Quote

You might try attaching the output in the future as was suggested.

HandBrake can't fix the jittery output file, yes, one would process the input files.

You might also try to use PD's "Profile Analyzer" to create similar AAC (H.264) output profile for your input streams vs your transcode conversion to HEVC (H.265). This output may not have the glitch. I know, you shouldn't have to, but with PD sometimes you have to do things to get glitch free output.

Jeff

Quote I did use the profile analyzer, but alas, no dice. I will give Handbrake a shot for a clip or 2 tonight and see if that helps. I genuineley hope i can roll back to a version from a few weeks ago so I can get these projects completed on time.

Any suggestion of what settings i need to use in handbrake given the file from the a7iii?

Thank you again for all of your suggestions!

Reg

You can use about anything just as a test to see if sync issue is corrected to see if conversion is worth pursuing. But specifics of your source video to replicate for similarity to source are:
Dimensions: 3840 x 2160
Video Encoder: H.264 or H.264 (NVEnc) to use your Nvidia GPU for faster encode
Framerate FPS: 23.976 and Constant Framerate
Avg Bitrate (kbps): 100000

Always judge sync issue based on produced output file with playback in any accepted media player vs PD timeline playback.

Many cases of issues after a version push, but it has not been very common for CL to provide access to an old version with 365 subscription key. CL really washes hands if you read the EULA which you accepted to use the software, "You agree that CyberLink may change the version of the SOFTWARE provided to you at any time without liability to you."

Jeff

So i took your advice, installed handbrake and rendered the video given your parameters. The video plays flawlessly in media player but once I load it into PD, even after letting a shadow file generate i expereince some random choppiness however the audio and video stay in sync! i tested it against the original file and the original plays smoothly in PD however after 45 seconds i got the sync issue. (that is resolved by hitting play then pause) I havent attempted a render yet, but I think this might be a viable workaround. Thank you so much for all your help Jeff! I'll keep the forum posted once i attempt to render the handbrake files. for the heck of it i'll run the OG output file through handbrake and see what happens...

Thanks Again!

Quote

You can use about anything just as a test to see if sync issue is corrected to see if conversion is worth pursuing. But specifics of your source video to replicate for similarity to source are:
Dimensions: 3840 x 2160
Video Encoder: H.264 or H.264 (NVEnc) to use your Nvidia GPU for faster encode
Framerate FPS: 23.976 and Constant Framerate
Avg Bitrate (kbps): 100000

Always judge sync issue based on produced output file with playback in any accepted media player vs PD timeline playback.

Many cases of issues after a version push, but it has not been very common for CL to provide access to an old version with 365 subscription key. CL really washes hands if you read the EULA which you accepted to use the software, "You agree that CyberLink may change the version of the SOFTWARE provided to you at any time without liability to you."

Jeff