Quote Hi fellows

Does anyone have a problem with loading mp3 files in bitrate over 256 kb/s into the timeline?
They load only as a vertical line and not as timeline files
Any suggestions?

greetings
Irek

That seems like it might be a problem with a specific clip or type of encoding that was used. I don't have PD16, but in PD14 and PD17 (screenshot below), a 320kbps MP3 behaves normally:



Could you upload one of the MP3s that's been giving you trouble to a cloud folder and post the link to it here? Maybe other people can confirm what you're seeing, or help narrow down what the problem might be.

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°

The test files are in the Dropbox link

Can anyone with PD16 confirm that the problem exists?

https://www.dropbox.com/sh/75sin7gus5r37e8/AADo3RBZBFiW72fqnLTU6W6va?dl=0

regards
Irek Win10Pro64, Ryzen 7 1800X, GTX1070Ti8GB STRIX, 16 GB RAM, 4 x M.2 Samsung 960Pro 500GB, 6 x SSD Samsung 256GB, ASUS PRIME X-370 PRO,2xA160AEJ,1xUX180,3xA6300,3xA6000, 2xD4S,1xD850,man and woman without skills...

Quote The test files are in the Dropbox link

Can anyone with PD16 confirm that the problem exists?

Yes, the problem exists with that specific clip in PD14 and PD17. MediaInfo reports the correct details about the clip, but PD sees it as only having a duration of 13 frames at 60 fps (or 0.216 seconds):



If I edit that timeline clip with AudioDirector9, it shows the waveform for the full clip. If I make any changes and send it back to PD17, the .WAV file shows correctly.

I then opened the clip directly in AD9 and produced it without making any changes to a 320kbps .MP3 file. That clip works correctly in PD14 and 17 on my computer, so the problem would seem to be with the LAME3.100 encoding library that was used, not the high bitrate.



You can download my re-produced clip from here and see if it works properly in PD16.

If it does, you should report this issue to Cyberlink using this contact form, and be sure to copy the URL of this forum thread in your message. Then post the ticket number (it will start with CS) back here to close the loop.

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°

Yes, I know the method for changing the file format by any program, but this problem did not occur before.
And I am not sure if the problem occurred before the last update... Win10Pro64, Ryzen 7 1800X, GTX1070Ti8GB STRIX, 16 GB RAM, 4 x M.2 Samsung 960Pro 500GB, 6 x SSD Samsung 256GB, ASUS PRIME X-370 PRO,2xA160AEJ,1xUX180,3xA6300,3xA6000, 2xD4S,1xD850,man and woman without skills...

Quote Yes, I know the method for changing the file format by any program, but this problem did not occur before.
And I am not sure if the problem occurred before the last update...

I am certain this issue was present before the latest PD16 update, as PD13, 14 and 17 all show the same problem. I'm glad you know that there's a workaround by converting the clip, but I think Cyberlink should be informed of this issue so they can at least patch PD16 and 17 (15 and older are no longer actively supported).

I'm happy to report it to them if you don't want to do it.

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°

already reported... Win10Pro64, Ryzen 7 1800X, GTX1070Ti8GB STRIX, 16 GB RAM, 4 x M.2 Samsung 960Pro 500GB, 6 x SSD Samsung 256GB, ASUS PRIME X-370 PRO,2xA160AEJ,1xUX180,3xA6300,3xA6000, 2xD4S,1xD850,man and woman without skills...

This is answer from Cyberlink Support:
"
With regards to your previous concern, upon further checking, we are able to reproduce the issue in our lab when trying to edit the 2 specific MP3.
After checking, the issue relates to Windows MP3 filter, which PowerDirector laverages it to edit MP3 audio. It doesn't relate to the audio codec. Due to this filter is a system module so we are not able to check the root cause of the error.
It is suggested to convert the specific MP3 as the workaround solution."

OptoData, can You help them with this problem?

regards
Irek Win10Pro64, Ryzen 7 1800X, GTX1070Ti8GB STRIX, 16 GB RAM, 4 x M.2 Samsung 960Pro 500GB, 6 x SSD Samsung 256GB, ASUS PRIME X-370 PRO,2xA160AEJ,1xUX180,3xA6300,3xA6000, 2xD4S,1xD850,man and woman without skills...

Quote OptoData, can You help them with this problem?

regards
Irek

I'm happy to

You already know that you can convert the audio clip to another format and/or bitrate, and the new clip should work fine as long as the app you're using has a different codec library.

Since the problem seems to be with how the media libraries are set up on your machine, one thing to try if you want to change that is to download and install the K-Lite codec pack from here. Be alert for unwanted apps when you install, but you should be able to opt-out of installing everything but the codecs. You can try the Basic or Standard versions and the comparison chart is here.

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°

I have noticed that my music mp3 files are sampled at the 44.1 Khz. Rate as was your 128kbps lame encoded one. Your 320kbps one here has a sampling rate of 48 Khz. Could not find any ripped cd music at that sampling rate. I encoded a 320kbps audio sampled at 48 Khz using an older version of lame and it worked properly in PD17.

You may want to encode that audio using lame at 44.1 Khz and let us know if that was the problem with your lame encoder (latest version).