hldj.org

I've looked everywhere for this (including http://www.hldj.org/forums/viewtopic.ph ... 60&start=0) and I've found nothing.

Sometimes HLDJ gets stuck when selecting a file, and pressing hldj_next or hldj_previous just keeps showing the same filename and doesn't go anywhere. This problem usually goes away if I wait several seconds (after which pressing next/previous ACTUALLY changes the selected file). Also, filenames displayed not matching the actual file playing happens frequently too alongside this.

I had this problem back in 1.4.5, although it's improved since 1.5.0 was released. Also, I've noticed this happens more often the bigger the individual filesizes are in the current folder. In a folder where all the wav files are a few dozen KB each, even if there's hundreds of them, HLDJ responds quickly and this problem rarely occurs (and when it does, the time I need to wait is less than a second). But in a folder with several files ranging about 4 or 6 MB, even if there's only a few files, it gets stuck frequently (sometimes I have to wait 10 seconds or more).

Showing the current directory and changing directories works perfectly, and this problem happens whether I'm in an online game or single player.
I should also mention I'm using "+developer 2" on Left 4 Dead to display the last 6 lines of console at the top of the screen, I'm on Windows 7 64-bit (although I've seen this problem happen even when I had XP Pro SP3 32-bit), and my Audio folder for HLDJ is about 1.69 GB. Any ideas?

This is normal: HLDJ copies the selected file to the appropriate location, so larger files take longer to copy, especially depending on your system specs. In 1.5 I improved the parsing algorithms and added multithreading which is why you probably notice an improvement.

With this in mind, use discretion when quickly advancing through files. I've tested next/prev to the point that nothing should "stick" or break even if you issue many commands consecutively, but you may notice that the current audio text is not being updating quickly enough.

I'm currently exploring the possibility of using hardlinks instead of copying the file, which should be many times faster, but they are not without their own drawbacks. In the meantime, if you're noticing considerable delay, make sure your system is running up to par, with no unnecessary programs running in the background. Also obvious things such as loading songs from a USB harddrive or network share will slow down transfers. Other than that, check back every so often to see if I've got hardlinks implemented.

Well that explains it. Thanks.