I have the same problem on my machine. It took about 1 second per file to build the song list. I could see it load each file in turn (I guess it had to load the file to see the file info), and so just do the math when trying to create a songlist of thousands of songs.

It would seem to me that the process should just be able to read the information from byte offsets in the file (since PGMusic knows the file structure), and shouldn't require loading each song to just find out standard information about each file. But that does not seem to be the way it does it.

I rebuilt the song list of all the MGU files I have downloaded from the internet over time, so that's about 30,000 files (after eliminating all the exact duplicates). It took all night to rebuild the list.

My machine is an i5 with 7200 RPM drives that normally works pretty quickly on everything else. Everything is installed to the hard drive.

I haven't tried rebuilding it, though, because I don't want to tie up my machine for that long.

John

Laptop-HP Omen I7 Win11Pro 32GB 2x2TB, 1x4TB SSD
Desktop-ASUS-I7 Win10Pro 32GB 2x1.5TB, 2x2TB, 1x4TB SATA

BB2025/UMC404HD/Casios/Cakewalk/Reaper/Studio One/MixBus/Notion/Finale/Dorico/Noteworthy/NI/Halion/IK

http://www.sus4chord.com