I've made a simple video mixer in Gridflow (9.13) and I want to send the output to an external projector. I've set up my computer so that I can drag windows to the second screen, but when I attempt to go full screen using [#out sdl] and then pressing Esc it goes fullscreen on both screens. If I use an [#out window] object, which I believe is an x11 window, there's no way (that I can find) to go full screen, so I'm stuck at with an 800x600 window on a 1366x768 screen. I did attempt to use a [#scale_to (768 1366)] object to emulate being full screen but the scaling causes a massive drop in framerate.
Can anyone suggest how to go fullscreen on only one screen, how to go fullscreen using an x11 window or some other way to do this?
I'm using Gridflow 9.13 with Pd-extended 0.42.5 on a Dell Studio 1555 using the ATI Radeon 4555 proprietary driver running Ubuntu 10.10.
Thanks,
Antonio
On Thu, 10 Mar 2011, Antonio Roberts wrote:
I've made a simple video mixer in Gridflow (9.13) and I want to send the output to an external projector. I've set up my computer so that I can drag windows to the second screen, but when I attempt to go full screen using [#out sdl] and then pressing Esc it goes fullscreen on both screens.
Sounds like the kind of problem that can't be solved in GridFlow. It's a SDL issue.
If I use an [#out window] object, which I believe is an x11 window, there's no way (that I can find) to go full screen, so I'm stuck at with an 800x600 window on a 1366x768 screen. I did attempt to use a [#scale_to (768 1366)] object to emulate being full screen but the scaling causes a massive drop in framerate.
Changing the screen resolution is a sure way to avoid even having to scale.
[#scale_to] is a simple abstraction not meant to be fast or fancy. It would be a good thing to make a much better software scaler for GridFlow (interpolating and faster), but it wouldn't be as fast as a hardware-accelerated scaler, or simply changing the screen resolution.
Changing screen resolution also gives you the best image quality when using a CRT, whereas on a LCD it just means you're getting the LCD monitor to do the scaling for you.
Can anyone suggest how to go fullscreen on only one screen, how to go fullscreen using an x11 window or some other way to do this?
There is the "border" method for removing the border, the "move" method to put a window wherever you want (compute window coordinates to match the way the mouse travels from one screen to the other).
I say that again in an email, because most people don't read the chat.
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
Thanks for the advice! I've sent it to the pure data forum as well.
As GEM crashed often for me (using an ATI card) I instead used:
[#to_pdp] | [pdp_xv]
I can't remove the window border but I at least can resize the window to fit the size of the screen
Ant
On 14 March 2011 15:17, Mathieu Bouchard matju@artengine.ca wrote:
On Thu, 10 Mar 2011, Antonio Roberts wrote:
I've made a simple video mixer in Gridflow (9.13) and I want to send the output to an external projector. I've set up my computer so that I can drag windows to the second screen, but when I attempt to go full screen using [#out sdl] and then pressing Esc it goes fullscreen on both screens.
Sounds like the kind of problem that can't be solved in GridFlow. It's a SDL issue.
If I use an [#out window] object, which I believe is an x11 window, there's no way (that I can find) to go full screen, so I'm stuck at with an 800x600 window on a 1366x768 screen. I did attempt to use a [#scale_to (768 1366)] object to emulate being full screen but the scaling causes a massive drop in framerate.
Changing the screen resolution is a sure way to avoid even having to scale.
[#scale_to] is a simple abstraction not meant to be fast or fancy. It would be a good thing to make a much better software scaler for GridFlow (interpolating and faster), but it wouldn't be as fast as a hardware-accelerated scaler, or simply changing the screen resolution.
Changing screen resolution also gives you the best image quality when using a CRT, whereas on a LCD it just means you're getting the LCD monitor to do the scaling for you.
Can anyone suggest how to go fullscreen on only one screen, how to go fullscreen using an x11 window or some other way to do this?
There is the "border" method for removing the border, the "move" method to put a window wherever you want (compute window coordinates to match the way the mouse travels from one screen to the other).
I say that again in an email, because most people don't read the chat.
_______________________________________________________________________ | Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
On Tue, Mar 15, 2011 at 1:50 PM, Antonio Roberts antonio@hellocatfood.com wrote:
Thanks for the advice! I've sent it to the pure data forum as well.
As GEM crashed often for me (using an ATI card) I instead used:
[#to_pdp] | [pdp_xv]
I can't remove the window border but I at least can resize the window to fit the size of the screen
To remove the border from a pdp window you can set a gnome shortcut for send windows to fullscreen. Or using devilspie. cheers husk
On Tue, 15 Mar 2011, Antonio Roberts wrote:
Thanks for the advice! I've sent it to the pure data forum as well. As GEM crashed often for me (using an ATI card) I instead used:
[#to_pdp]
Btw someone (buzz) reported that [#to_pdp] would only produce a single frame, as it would get stuck with the same packet over and over. I tried it and [#to_pdp] would receive the same pointer over and over, pointing to the same data as the first frame. Did you experience this problem yet ? If so, with which pdp object classes does it happen, and do you know a workaround, or any other hint that might allow me to fix the problem directly in [#to_pdp] ?
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
I'm not really sure what you mean. I used [#to_pdp] and [#pdp_xv] and everything worked fine. I've attached the patch that I used (On Ubuntu 10.10)
Ant
On 19 March 2011 21:06, Mathieu Bouchard matju@artengine.ca wrote:
On Tue, 15 Mar 2011, Antonio Roberts wrote:
Thanks for the advice! I've sent it to the pure data forum as well. As GEM crashed often for me (using an ATI card) I instead used:
[#to_pdp]
Btw someone (buzz) reported that [#to_pdp] would only produce a single frame, as it would get stuck with the same packet over and over. I tried it and [#to_pdp] would receive the same pointer over and over, pointing to the same data as the first frame. Did you experience this problem yet ? If so, with which pdp object classes does it happen, and do you know a workaround, or any other hint that might allow me to fix the problem directly in [#to_pdp] ?
_______________________________________________________________________ | Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
-
Antonio Roberts -
Husk 00 -
Mathieu Bouchard