Hey Tom, Thanks for doing all of this testing for us, it's good to know that we're making some sort of progress. :)
Regarding the Ubuntu 8.04 QtOpenGL compile error, do you recommend that we remove the --silence-errors line from the pkg-config calls? If not, any ideas how we could improve the error reporting? Thanks, Albert On Wed, 2008-07-02 at 23:25 -0700, Tom Jennings wrote: > Hi all, well I'm a fan but a weak helper-outer it turns out, between > work and school I'm useless here. But here's a few small items. > > > 0) All my interface crashing woes ended with patches dating back a few > months now. Late news, but I fogured I'd say thanks for the work. > > > 1) Was unable to compile a recent version on ubuntu 8.04. To make a long > story short --silence-errors in pkg-config QtOpenGl invokation hid the > error; manually invoked w/o --silence-errors revealed that it could not > find libqt4-opengl-dev. apt-get install that, scons compiled fine, and > versions since. I had been compiling just fine before that. Sorry, no > rev number(s) to report. > > > 2) I've been unable for some time to reduce latency to anything really > useful; the best I could achieve was 49mS (!); less than that got the > usual pops and gapping. Turning waveform to simple helped somewhat. > This, on a machine designed for low-latency music (dual core 2.4GHz, 4GB > of very fast RAM, etc). > > Poking around on a related problem found a thread involving RT latency > and cpufreqd. So at a mere whim I apt-get purge'd it, and install cpudyn > instead. Voila! I could run latency down to 2 (two!) mS with occasional > pops; 4mS no pops (but read on). With waveform on, two tracks mixing > centered fader, etc. > > Before I posted I figured I'd do some regression, so I purge'd cpudyn, > reinstalled cpufreqd, expecting... still works at 4mS. So much for that > theory. I assume that soemthing like a bad install/upgrade/etc crossed > up the daemon, and now I'll never know. > > --> If you can't drop latency on a fast machine, try > purging/reinstalling cpufreqd and/or cpudyn. There does seem to be some > issue with frequency scaling in Hardy. > > > 3) "Latency leak" -- confounded w/previous results, I thought I'd set > latency to 4mS, put two tracks on, and leave it running. After a day or > two -- mild pops. Then adjusted latency to 6mS, problem went away, and > after another 24 hours of continuous play, did not pop. I repeated this > twice (took a week, that's how busy I've been :-). So 6mS is more than > acceptable, but there is something funny in there. > > > No complaints here, it's working just great. > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Mixxx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mixxx-devel ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
