Hi Jay,
I had to build SDL from tarball source -- the RPM wouldn't even
./configure, much less build a binary (which was my preferred
approach).
Building it required installing slang-devel and smpeg-devel, both of
which were in the SuSE 9.3 collection, and, I don't *think*, anything
else.
Quite a few people have had the same problem on FC and SuSE. There are
some instructions on the installation page of the website but it doesn't
mention slang-devel. Note to self.
I note that it doesn't handle full-screen well (1280x1024), speedwise;
is there something I should be doing there?
The CPU horsepower is heavily affected by the display update rate, I
think v0.4 went out with a default 60 frames per second. I've lowered
this to 10fps in CVS. To lower it in your installation, search for "fps"
in pycdg.py.
Will also committed a mod in CVS to use hardware acceleration if
available in full-screen mode - sounds like it would be worth giving
that a go as well.
What speed CPU are you using by the way?
My production environment will be a little tiny window on my KJ
display, and probably 640x480x8 on the playback monitor (are we doing
dual-monitor yet? Or will I have to do an X-splice somehow?); will
that be fast enough to keep up?
I made a development version that allows you to send to another X
display, but not dual-display yet. Dual-display is going to need some
architectural changes... something like a single audio playback and
syncing module that sends the display data to other display processes.
There's no built-in support in pygame for selecting X displays so it
would mean running a new python process with DISPLAY= in front.
And, finally, I note that my rip was kinda messy. Will cdparanoia
properly extract the subcode? Is there error correction *on* the
subcode? Or am I going to have to preview all 4000 tracks before I
turn them lose?
cdrdao defaults to the highest read speed, which I've found can
introduce errors. One of the recent versions introduced something like a
--read-speed option so you can get better quality rips.
Let me know how you get on with the lower update rate. If that helps
I'll put out a new release pronto. There have been a few other bugfixes
that I'd like to get released as well, plus the new release could be
distro-package-manager-ready. Then we can move on to the small matter of
pitch-shifting etc.
Cheers,
Kelvin.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Pykaraoke-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pykaraoke-discuss
