XYplorer Beta Club

Hi,
I have a large library of MP3 under different directories. The default installation of XYplorer does not have a length column. I need to see the length of each MP3 files. I added a column and selected the property "Length". Now I see the length of each MP3, which is great, but if a directory has more than 50 MP3, it takes a while for the length to show up. Once it shows up it is fine, but if switch between directories, there is a delay "hour glass" until it loads. Is there an indexing that I need to do in order for the contents of the directory show up immediately? If I delete the column "Length" everything is fast and normal, but it really slows the refresh when I add a custom column. is there a solution for this?

Thanks.

Welcome to the forum.

Use the custom column "Length" instead. After that you can configure it's trigger and choose:
"List" instead of "Browse". In that case the data is only fetched when items are actually displayed (e.g. while scrolling).
Another method is possible: Tagging all the files with their length and display such a custom column afterwards.

But if the first version is ok for you, I'd go with that

Thank you very much for your reply.
I have done exactly as you recommended Changed to list from browse, but I still have a lag on the directories with a lot of MP3 files. It is better than before, but it is not instantaneous. Without the custom column it is instantaneous.
It is mostly for the folders with a lot of MP3 files. If there is less than 50 files, it is normal.
Any other suggesstions?
Thanks,
Paul.

It needs to read the length attribute from all currently visible files. Ofc this takes a little moment. Apart from tagging I'm not aware of any faster method

I have a Custom Column configured to calculate file hashes - which can also be rather slow and disruptive when browsing.
What I do is configure it to trigger on Click and then when I need the hashes I right click the column header and select Refresh Column which calculates it for all listed items.

This keeps browsing snappy and while hashes are not always available they are not too far away.

My only complaint with this approach is they are not cached so occasionally when comparing hashes and jumping around I end up having to "Refresh Column" multiple times.