On 12/12/05, Jay R. Ashworth <[EMAIL PROTECTED]> wrote: > On Mon, Dec 12, 2005 at 04:56:28AM -0700, William Ferrell wrote: > > On 12/11/05, Kelvin Lawson <[EMAIL PROTECTED]> wrote: > > > 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. :-)
You're right; I paid more attention to how it performed at native resolution (non-full screen, no scaling) at 30 FPS versus 60 FPS and there's no discernable difference. 30 FPS is fine, even at 1024x768 this machine can handle it with only about 35% CPU usage. I'd recommend changing the default to 30 instead of 60 :) Thanks for the reminder, Jay :) I forgot TVs do that 2 fields trick. > > > 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. Interesting thought; my only concern with using Xvnc is speed -- certainly OpenGL hardware acceleration isn't available via Xvnc, so the spiffy visualizations I run wouldn't work properly, nor would video playback (unless I've missed something major in VNC development :). However, I'm curious if anyone here knows how to snag the right-hand "half" of my two-screen-wide X server desktop and create a "preview" of what it's showing in a small window on the left side. Enlightenment can do something similar with its "pager" feature but that's horribly slow and too small to be useful. > > 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. See if 30 FPS is any better. > Can "fullscreen" mode change the scan rate of the X server? Set it to > 640x480x8, and the problem would likely evaporate. Yes, full screen mode will switch your display resolution if it can match a mode to your options; try this: pycdg.py -w 640 -h 480 -f -s 30 file.cdg That'll run it at full screen, 640x480, at 30FPS. You should even be able to get 60 FPS out of it, not that I can now see much difference between 30 and 60 :) ------------------------------------------------------- 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_idv37&alloc_id865&op=click _______________________________________________ Pykaraoke-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pykaraoke-discuss
