Thanks for the input guys.
Well, I only have 256MB of ram, 400MHz RAMBUS stuff. mAirList chugs along nicely at about 120MB mem usage all up with windows. I tried to load the whole audio to ram, but it seems to go to the hard drive as a swap file rather than the available system ram come down. I don’t really see why it would help as the start is still instantaneous to me on wave files, appart from the 10ms jitter or whatever its exact amount is now and then when starting. I realise it’s quicker starting from ram, but it’s not a hard drive problem, or it would happen with any other player.
I just replaced the bass.dll with the latest. Still happens. It doesn’t appear to happen when you load mAirList for the first time, and start the song the first time. It’s like there’s 5-10ms of audio left in a buffer somewhere next time it goes to start the file from stop/idle. It doesn’t always happen, but it’s still enough to be annoying.
More about my setup. It’s a P4 1.5GHz, 256MB of 400MHz RAM which I never use more than 160MB unless audio editing. It’s an Intel board/processor/rambus etc… Simple 32MB video card. A couple of western digital drives, the audio drive being on the second IDE by its self (D:). DMA all ultra mode 5 etc… the audio drive is partitioned in large allocation size for audio files, no indexing (service disabled), fixed swap file size on C: of 768MB (to avoid delays with dynamic swap file sizes) which I never used more than 160MB physical ram unless audio editing etc…
This machine does it’s job just fine, doesn’t run out of RAM, doesn’t hesitate when playing back audio, especially as I’m using uncompressed linear PCM files which the sound card handles without the need for CPU decoding etc…
Audition runs on this PC fine for editing and playback of multiple tracks at once without the jitter on start.
The CPU hits maybe 30% when I start 1-3 players in mAirList. About 5% if I start it in media player or just the cart player in mAirList.
Since I use wave files, everything’s in metadata files as far as additional information goes.
I use short file names (7 characters) so less long file name look up conversions etc… all those sort of tweaks you could think of.
I just tried playing a quiet -70dB tone in a cart player, while starting the song I know it jitters at the start quite often on in another cart player. Perfect, no jitter on start and re-starting it over and over. Yet, as soon as I use the players, there’s a 50/50 chance almost it’ll jitter a split second of audio and a real quick split second before it starts. Almost like the tinest error on a scratched CD.
So why would it do this in the players with hardware mixing, yet it’s fine in the cart player with other audio running at the same time etc…?
I don’t have any onbeforeplayerstart scripts loaded at the moment either.
It’s just a little anoying. Perhaps everyone else uses mp3’s with the inherent 30-40ms codec delay and my files are to tightly edited for mAirList? Usually there’s 5-15ms on the start of the audio files and they all start at infinity, not part way through a sine wave etc…
I could always email a 2 seconds of the wave file for someone else to load 10 times or so in a playlist and stop/start it in the players to check on their mAirList?
Gav.