Software Support > DOS/WinCab
wincab breaking down ?
jp:
hello , hope anybody can help me
i got wincab set up working fine,
set "maxque" to 5 ,and randomplay to true, no duplicates.
now on startup randomplay works everything is ok,
after selcting 5 songs , wincab ads for every played song one song in the upcomming list (the same song)
and after playing the last selected song is crashes.
set maxque to 4 it does the same except for the adding of songs in upcomming list,(it crashes)
Chris:
This is a bug; it only occurs when MaxQueue is set to a really low number. I haven't found the cause of it, but this report will definately help me narrow it down... thank you!
--Chris
jp:
first i like to thank you for this great program,
when i found it it was just right for my purpose (a true jukebox)
did a lot of surching for it
problem:
did some more testing:
removed the strict album message's (put a "#" in front of it)
maxque stil 4 ,
it plays the 4 selected songs but fills "upcoming" with a (random selected ) song (4 times the same)
and plays this song (over and over ) until i select another song (or more ) which is placed on top of "upcoming" and are normaly played ("upcoming" list stil getting filled with the same song)
hope this helps
jp
jp:
and more testing
set maxque to 100 (you said it happened when maxque is set to "a really low number" , (100 songs more than 6 hours of music))
it still fils maxque with a song (after restarting this song is the first "random "song)
put strictalbums back in (maxque still 100)
it does not fill maxque with a song but after the last song it exits (quits)
jp
Chris:
--- Quote from: jp on February 20, 2006, 02:36:16 pm ---and more testing
set maxque to 100 (you said it happened when maxque is set to "a really low number" , (100 songs more than 6 hours of music))
it still fils maxque with a song (after restarting this song is the first "random "song)
put strictalbums back in (maxque still 100)
it does not fill maxque with a song but after the last song it exits (quits)
--- End quote ---
Hmm... very interesting. This probably isn't the problem I thought it was, then; it's more likely to be a buffer overflow or something.
This is very helpful... thank you!
Navigation
[0] Message Index
[#] Next page
Go to full version