Not absolutely certain, as there is a "random" element that means unknown or hard to produce trigger, but switching from the generic VESA driver to i965 chipset driver seems to have stopped the interface lockup. Odd, as overall the display is fine, all windows except mixxx are perfect. It's got to be a library function write-to-window-something deadlocking. That's a relief. I'll continue trying to tune this.
There is still a very noticable and repeatable pause in audio output when hitting CUE while a player is playing, eg. jumping back to a set cue point. The delay seems congruous with the waveform display generation -- a large jump in time requires a full erase/rewrite. It's quite repeatable, if I hit CUE... CUE... CUE... once per second or so, there's an audio pause/gap and full waveform rewrite every time. It's a 2.4GHz dual core intel with 4gb of 1066MHz RAM, running only mixxx and an xterm or two. ALSA driver from mixxx, not jackd. This makes cue while playing unusable. I have to stop, jog to the cue point and use PLAY to start. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
