Rick - Thanks for the tip on the multi tag editor. I don't use genres at all..I guess I should start. That makes the most sense of all..
As far as the hiccup...I'm guessing VDJ, like others loads the track to memory?
Randy...This is a newly formatted PC...the usual processes are running. No issues when I try to browse another sub folder, only when I recurse the folder that contains ther track that is playing...The hiccup occurs right at the very end...without fail. I will try it on another machine.....to see if I can reproduce it. I use the onboard sound on this PC; that may be the culprit as well....
VDJ and others, usually load the whole track by default, or have an option as to how much to keep in memory.
Rockit is streaming by nature (more on that later), so it reads chunks of the file at a time. That means that if you happen to browse through My Computer, to the same file that is playing, and Rockit happens to be reading a chunk at the same exact time, you can get a burp.
Hence, why we use the library
There are reasons I keep the decoder working that way, and if you look in Task Manager, you will see that playing audio, Rockit uses almost no CPU time, and very little memory. Take a look at some of the others, and see how much resources they use. The worst I've seen to date, is the newly released DEX thingy from my "buds" in Florida (repackaged DJDecks). It uses memory sooo fast, I can't keep up with tracking it :sqerr:
Rockit does have the ability to pre-load the entire track, and also do all that wiki-wiki, scratch type stuff and tempo, but it is disabled in V4.0, because it didn't meet my release stability requirements for this version.
I usually cannot duplicate what Steve is running into, but it could also be due to something caching things differently on his system. For example, if you have the option for fast indexing turned on, system restore, things like that, your cache is constantly being refreshed in Windows, hence a lot more chance of something like that occurring...