chris clepper said this at Thu, 6 Mar 2003 14:38:13 -0600:
I looked at the source and guessed about [pix_videodarwin 720 480], and although it created the object and rendered, it was far too pixelated to be showing full resolution. But I'll experiment some more.
i found the flag to set for high_quality and added that to the code. there are several other modes and i will look into adding those as well.
Thanks. So that others don't take this performance hit, would you consider dedicating a couple commands (messages to the [pix_videoDarwin] object) for this? I dunno how you're handling this.
That would be helpful, as I noticed that S-Video out on my machine has a minimum resolution of 800x600, which causes a bit of a crash.
s-video has a resolution of 640x480, in fact it has to in order to support NTSC (it's actually the _only resolution for NTSC). the OSX monitor panel doesn't show it by default for some reason, but if you uncheck 'Show modes recommended by display' it will allow 640x480.
I'm actually in PAL-land, but the TV will handle NTSC as well. What you suggest sounds like it. I'll try it as soon as I can get a turn on the telly.
what sort of crash occurs? what's the hardware?
Just Pd falling over. Nothing serious. HW is a PB12", so the NVidia Go 420.
Any chance of putting a titlebar on the non-external display window?
sure, at some point. that requires an event loop for the window, which could be tricky. also, another event loop is exactly what pd+GEM does not need at this point.
Right. Good point. But I'm blown away by the performance right now.
Cheers, adam