Given how much processor there is in a cdg player, I can't imagine it's
much.
Yeah they're probably very low spec but their software isn't running on
top of Python/Pygame/SDL/X etc :-)
I'd bet *cash* it's in the scale-up algorithm inside pygame. Assuming
that's who's scaling to size.
I think you're right. Here's an idea: divide the screen up into several
segments, and only scale those segments that have actually been updated.
At the moment we scale up the entire frame at every update, whereas in
actual fact only a small portion of the screen is likely to have changed
between any two updates. If it's possible to scale up only part of the
surface, we could save a lot of horsepower there.
3) add OK buttons to the prefs and search dialogs.
So you're doing that? Or I am? :-)
I'll race you :-)
-------------------------------------------------------
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
