Endless Loop

[jakarhill]

I have stumbled on a problem where jajuk cycles through
every song in my directory. This seems to happen where
there is an error in accessing the audio device. For a
breif second, I see a audio error in the footer of
Jajuk and then it goes to the next song. It just keeps
going and going and going. IT tries to play every song.
I have to Kill Jajuk to stop it. It may take many efforts.

CHeers

Randy

[bflorat]

Logged In: YES 
user_id=363565

In all cases, a stop ( at the top with play, pause...
command panel ) should stop the loop.
Jajuk assumes that all tracks are available as it knows them
in its collection. If the read fails because the track no
more exists ( removed from file system ) or for any other
reason like sound device access, it display an error message
and follow the options you set : if there is more tracks you
selected or the continue mode ( in command panel ) is set or
the repeat mode is enabled, it will continue to try playing
these files.
If you still feel it's a bug, please explain the exact use
case  and please give your <home directory>/.jajuk/jajuk.log
file.

[jakarhill]

Logged In: YES 
user_id=1030800

I have attached my log file. I am using XP. I cannot always
get the bug to appear. I am looking for a consistent use
case now. I think this is a bug of some kind. If audio
driver is not available, the application should not go crazy
looping.

[bflorat]

Logged In: YES 
user_id=363565

I don't see your jajuk.log file, please attach it to this
bug or send it to bertrand@florat.net.
I tried to reproduce your pbm ( another sound appli runs )
and jajuk starts every track with an error and lauch next
one... A stop stops the loop ( is it your case ? ) . It's
for me a normal behavior.

[bflorat]

Logged In: YES 
user_id=363565

Appart from the "cannot create device" pbm, i saw you need a
refresh ( file not found" errors. Don't forget to refresh
your devices from times to times because Jajuk only knowns
its database collection, not the real file system. 
I've not seen anything strange in you log file. Please send
me a use-case if you reproduce something other than normal
behavior as described before.