Software Support > DOS/WinCab

DWJukebox 3.4.1 skipping?

<< < (2/3) > >>

Dermbrian:
You might try this program....

http://www.thesycon.de/deu/latency_check.shtml

FYI, my MSI all-in-one doesn't skip.  The latency check program shows occasional red spikes quite frequently in the 2000usec to 4000usec range.  If I start and stop my wi-fi, the spikes are much bigger during that time.  But just idling:  2000-4000usec.  I wonder what kind of latency yours might show.

Brian

JustMichael:
I really doubt "latency" is the problem.  Any latency would also effect every other mp3 players as well.  I just went and installed "Arcade Jukebox 8" and I had it, Windows Media Player and WinAmp (all 3 at the same time) play an mp3 file.  All of them played the mp3 file just fine without skipping.  When other mp3 players play the mp3s just fine I get the feeling that the machine isn't the problem but that DWjukebox is the problem.

Dermbrian:

--- Quote from: JustMichael on September 08, 2010, 08:14:01 pm --- When other mp3 players play the mp3s just fine I get the feeling that the machine isn't the problem but that DWjukebox is the problem.

--- End quote ---

I hear you.  Too bad Arcade Jukebox 8, Winamp, and Windows Media player can't do the same job of emulating an electromechanical jukebox that DWJukebox can. When it works well, it's a truly unique program with an incredible level of user customization available. But there does seem to be different performance on various newer processors and peripherals than you'd expect there to be. 

My netbook with its single core Atom processor can't really run it well.  My all-in-one with its slightly faster dual core Atom can.  My newest MSI all-in-one with its Pentium R dual core runs it just fine...just as well as a five year old Pentium would :-\.  Your dual core Athlon 64 apparently can't run it in its current configuration of hardware/software/peripherals/drivers.  Hard to blame the program itself, but not hard to blame the particular Allegro game programming library that underlies it or the hardware manufacturers that apparently aren't all that compatible with the way they run that library.


Brian

Chris:
It's not Allegro so much as the underlying mpg123 library.  I need to figure out how to write a wrapper so I can use the Windows Media Player functions and not rely on mpg123.

There is no reason why on any modern system the buffer should not get updated for 23 ticks unless I have a bug somewhere, so I am also perfectly willing to blame my own code.  3.4.1 had a lot of optimizations that fixed many skipping issues as I found holes in my code, but obviously there are more to find.

Michael, are you using an album skin or a classic skin?  There are big differences in memory allocation betwen the two systems.  A lot of the bugs I fouund before were specific to one or the other, some even to specific skins.

--Chris

JustMichael:
A classic type skin I think.  The kind of skin were you see up to 100 songs at once.

Navigation

[0] Message Index

[#] Next page

[*] Previous page