Re: [PD] Problems going fullscreen on external projector

2011-03-23 Thread Antonio Roberts
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 ma...@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
#N canvas 424 82 679 315 10;
#X obj 142 22 openpanel;
#X msg 142 46 open \$1;
#X obj 142 4 bng 15 250 50 0 empty empty empty 17 7 0 10 -262144 -1
-1;
#X obj 52 24 metro 33.333;
#X obj 52 4 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 1 1
;
#X msg 26 114 1;
#X msg 26 137 2;
#X msg 26 160 3;
#X obj 279 22 openpanel;
#X msg 279 46 open \$1;
#X obj 279 4 bng 15 250 50 0 empty empty empty 17 7 0 10 -262144 -1
-1;
#X obj 399 22 openpanel;
#X msg 399 46 open \$1;
#X obj 399 4 bng 15 250 50 0 empty empty empty 17 7 0 10 -262144 -1
-1;
#X msg 26 181 4;
#X obj 537 21 openpanel;
#X msg 537 45 open \$1;
#X obj 537 3 bng 15 250 50 0 empty empty empty 17 7 0 10 -262144 -1
-1;
#X obj 64 141 switch 4;
#X obj 143 70 #in;
#X obj 279 70 #in;
#X obj 399 70 #in;
#X obj 537 70 #in;
#X obj 142 90 #downscale_by 8;
#X obj 278 90 #downscale_by 8;
#X obj 399 90 #downscale_by 8;
#X obj 537 89 #downscale_by 8;
#X obj 142 113 #see;
#X obj 279 113 #see;
#X obj 399 113 #see;
#X obj 537 112 #see;
#X obj 150 204 #to_pdp;
#X obj 150 225 pdp_xv;
#X msg 204 204 create;
#X obj 64 205 #out window;
#X obj 64 226 fps;
#X floatatom 64 249 5 0 0 0 - - -;
#X connect 0 0 1 0;
#X connect 1 0 19 0;
#X connect 2 0 0 0;
#X connect 3 0 19 0;
#X connect 3 0 22 0;
#X connect 3 0 20 0;
#X connect 3 0 21 0;
#X connect 4 0 3 0;
#X connect 5 0 18 0;
#X connect 6 0 18 0;
#X connect 7 0 18 0;
#X connect 8 0 9 0;
#X connect 9 0 20 0;
#X connect 10 0 8 0;
#X connect 11 0 12 0;
#X connect 12 0 21 0;
#X connect 13 0 11 0;
#X connect 14 0 18 0;
#X connect 15 0 16 0;
#X connect 16 0 22 0;
#X connect 17 0 15 0;
#X connect 18 0 34 0;
#X connect 18 0 31 0;
#X connect 19 0 18 1;
#X connect 19 0 23 0;
#X connect 20 0 18 2;
#X connect 20 0 24 0;
#X connect 21 0 18 3;
#X connect 21 0 25 0;
#X connect 22 0 18 4;
#X connect 22 0 26 0;
#X connect 23 0 27 0;
#X connect 24 0 28 0;
#X connect 25 0 29 0;
#X connect 26 0 30 0;
#X connect 31 0 32 0;
#X connect 33 0 32 0;
#X connect 34 0 35 0;
#X connect 35 0 36 0;
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] Problems going fullscreen on external projector

2011-03-19 Thread Mathieu Bouchard

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___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] Problems going fullscreen on external projector

2011-03-15 Thread Antonio Roberts
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 ma...@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

___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] Problems going fullscreen on external projector

2011-03-15 Thread Husk 00
On Tue, Mar 15, 2011 at 1:50 PM, Antonio Roberts
anto...@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

-- 
when Art become pratical
we call it technology.

When Technology become useless
we call it Art

www.estereotips.net

___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] Problems going fullscreen on external projector

2011-03-14 Thread Mathieu Bouchard

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___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list