Re: [Pykaraoke-discuss] FINALLY -- ghod I hate SuSE
On 12/11/05, Kelvin Lawson [EMAIL PROTECTED] wrote: Hi Jay, 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. The only problem with this is that the FPS is actually somewhat important; 15 fps is a bare minimum (from the testing on different tracks I've tried it with) for usable singing (it seems jumpy even at 15 FPS, though it's servicable). 30 FPS is definitely better, and 60 FPS is what the hardware players I've worked with produce. 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. It's enabled by default in CVS but it doesn't actually seem to help at all (that I can detect). It may just not be working or I may have set something up incorrectly. Having more pairs of eyes looking that over would be helpful :) What speed CPU are you using by the way? The notebook I now use for shows is an AMD Sempron 1.6GHz. 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. Don't forget about xinerama-style support -- one desktop stretched across two physical display devices. This is what I use now (the notebook display is used for my stuff during a show, then the VGA-to-NTSC adapter showing the other half of the desktop is used for the who's up cards, video clips, etc. pycdg.py plays along just fine by specifying the correct geometry and position, too. I can routinely squeeze 50 FPS out of it at 800x600. If I try for 60 FPS, it loses sync with the audio and isn't usable. --- 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_idv37alloc_id865op=click ___ Pykaraoke-discuss mailing list Pykaraoke-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pykaraoke-discuss
Re: [Pykaraoke-discuss] FINALLY -- ghod I hate SuSE
On Mon, Dec 12, 2005 at 04:56:28AM -0700, William Ferrell wrote: On 12/11/05, Kelvin Lawson [EMAIL PROTECTED] wrote: 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. The only problem with this is that the FPS is actually somewhat important; 15 fps is a bare minimum (from the testing on different tracks I've tried it with) for usable singing (it seems jumpy even at 15 FPS, though it's servicable). 30 FPS is definitely better, and 60 FPS is what the hardware players I've worked with produce. Well, only in that they do 2 fields per frame. :-) Apologies, BTW, guys; my last 2 replies were inadvertantly off list; feel free to reply them back on. 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. It's enabled by default in CVS but it doesn't actually seem to help at all (that I can detect). It may just not be working or I may have set something up incorrectly. Having more pairs of eyes looking that over would be helpful :) Hmmm... 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. Don't forget about xinerama-style support -- one desktop stretched across two physical display devices. This is what I use now (the notebook display is used for my stuff during a show, then the VGA-to-NTSC adapter showing the other half of the desktop is used for the who's up cards, video clips, etc. I don't know that I'll have Xinerama support on the Tritton USB VGA dongles I'll need to use; I plan to have 3 or 4 channels of video going simultaneously. I *may* get by with one X server; I may not. Optimally, I'd like to have 4 Xvnc servers and 4 real ones; if one gets locked up mid show, it's more likely to be a hardware server; that wasy i could restart it without breaking the show. I don't know that I'll be doing that on an laptop, of course. pycdg.py plays along just fine by specifying the correct geometry and position, too. I can routinely squeeze 50 FPS out of it at 800x600. If I try for 60 FPS, it loses sync with the audio and isn't usable. Mine is much less happy than that, but, of course, that's at 1280x1024. Can fullscreen mode change the scan rate of the X server? Set it to 640x480x8, and the problem would likely evaporate. Cheers, -- jra -- Jay R. Ashworth[EMAIL PROTECTED] Designer Baylink RFC 2100 Ashworth AssociatesThe Things I Think'87 e24 St Petersburg FL USA http://baylink.pitas.com +1 727 647 1274 Space is called 'space' because there's so much *space* there. - John Walker, of Fourmilab, on Trek's End --- 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=7637alloc_id=16865op=click ___ Pykaraoke-discuss mailing list Pykaraoke-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pykaraoke-discuss
Re: [Pykaraoke-discuss] FINALLY -- ghod I hate SuSE
Hi Jay, Mine is much less happy than that, but, of course, that's at 1280x1024. Can fullscreen mode change the scan rate of the X server? Set it to 640x480x8, and the problem would likely evaporate. I've just spotted the following in the pygame docs: It is usually best to not pass the depth argument. It will default to the best and fastest color depth for the system. If your game requires a specific color format you can control the depth with this argument. Pygame will emulate an unavailable color depth which can be slow. Could you try setting DISPLAY_DEPTH=0 in pycdg.py, see if that helps. 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=7637alloc_id=16865op=click ___ Pykaraoke-discuss mailing list Pykaraoke-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pykaraoke-discuss
