Super SLOW mp3 import bug is back in 2022.9 and 2022.10

[akproductions1]

A few versions ago we had a bug where importing mp3 files were painfully slow. They fixed it but it came back with tons of other bugs in 2022.9. Now, 2022.10 is here with the same slow mp3 import bug. The same mp3 files that takes less than a second to import in 2022.7 takes 30 seconds plus in 2022.9 and 2022.10.

[jamesburlander]

I am also seeing this issue.

Running a Mac Studio M1 Pro processor, 16gb RAM.

[jamesburlander]

A 30 minute mp3 file just took about 8 minutes to import (I dragged file from Finder into edit view).

[JimaSound]

I am having this same issue with PT22022.9 and then PT2022.10. MBP M1 Max (macOS 12.6)

[mtmusic]

I'm getting this issue again too since 2022.9...

[moogboy100]

Confirmed this IS an issue. Like a major problem. AVID, please fix ASAP!!!!!

[DigiTechSupt]

Originally Posted by akproductions1

A few versions ago we had a bug where importing mp3 files were painfully slow. They fixed it but it came back with tons of other bugs in 2022.9. Now, 2022.10 is here with the same slow mp3 import bug. The same mp3 files that takes less than a second to import in 2022.7 takes 30 seconds plus in 2022.9 and 2022.10.

Hi! Community Support here, have you started a case for this issue? Thanks!

[moogboy100]

Originally Posted by DigiTechSupt

Hi! Community Support here, have you started a case for this issue? Thanks!

I just opened a case.

[changareth]

has this been solved? T.T totally experiencing this with my new mac book pro

[nednednerb]

Originally Posted by changareth

has this been solved? T.T totally experiencing this with my new mac book pro

Did you happen to read the last two messages about opening a case? They indicate very very clearly that Avid is collecting information, not "been solved"... That isn't totally clear? As I said, did you read the thread?

You should also open a case if you want it to be fixed faster. Your question is a slow and ineffective approach to solving your problem, compared to opening another case and letting devs know many different systems are experiencing the issue.