Board Logo

[FIXED in v3.0] eJ stops playing in Random/Shuffle mode
stsirois - 3-24-2003 at 05:55 AM

Not sure if this is a bug or a feature...After my selected playlist has finished, songs will randomly play, which is the way I prefer. However, after a bunch of songs have beed played, eJ does not queue up any more songs to play & it stops. I don't know how many songs it plays before it stops, but it seems like it takes an hour or two before eJ stops playing. I would like it if it played until almost all my songs have been played, which would take some time since I have over 7000 songs.

Thanks,
Steve


Audiosoft - 3-24-2003 at 06:01 AM

The random playback is most likely stopping because one of your MP3 files is corrupted and is not able to play all the way through.

To correct this problem open eJukebox's control panel, click the "Sound" tab at the top. Then check the option "Prevent Playback Stoppage".

This will make eJukebox start playing another song automatically when this happens.


stsirois - 3-26-2003 at 01:45 PM

Hmm...I have never had Winamp 2.x (by itself, no eJ) stop playing on me when I had my entire MP3 collection queued up in shuffle mode. Yet, so far with eJ, every time I leave it running for a number of hours, it stops playing at some point. I'll have to do perform some experiments so that I can get you some concrete data to work with. eJ wouldn't happen to have a feature that outputs a list of songs that it has played along with maybe a date/time stamp?

Thanks,
Steve


Audiosoft - 3-26-2003 at 09:48 PM

Does it still stop playing after a few hours when you have the "Prevent Playback Stoppage" option checked?


bosh - 3-26-2003 at 11:46 PM

I can confirm this behaviour; with 'Prevent Playback Stoppage' checked, I'll still have the music grind to a halt from time to time. I can never be sure what is triggering it though. However, there are never any songs in the playlist when it happens. I'm just running in the popularity mode.


Audiosoft - 4-2-2003 at 03:18 PM

We have isolated and fixed this problem in v3.0.