Re: [PD] Getting Sysex output to work on Linux

2008-05-31 Thread PSPunch

Does anyone have any opinion on the specs suggested by Martin?
Should [sysexout] behave in this manner, or would it be more suitable to 
make this a new object rather than over write the conventional object 
for compatibility?

I have no idea if I will be skilled to fix this in the near future, but 
I really would love to see some of my MIDI controllers in action.

--
David Shimamoto


 PSPunch wrote:
 Martin,


 I'm looking at the source code in svn, assuming you use [midiout] to 
 send sysex.
 The midiout object has one method, for floats : midiout_float(), in 
 x_midi.c, line 681.
 It just calls outmidi_byte() in s_midi.c, line 239. If Pd was 
 compiled with USEAPI_ALSA defined, then outmidi_byte calls 
 sys_alsa_putmidibyte() in s_midi_alsa.c line 234, otherwise it calls 
 sys_putmidibyte() in s_midi_oss.c line 182.

 Do you mean that theoretically, Pd + ALSA MIDI should be working?
 hmmm...
 
 Well it looks like it should but I just tried with a scope on the cable 
 and got messages using [noteout] but nothing using [midiout] with alsa 
 midi and jack. I tried sending bytes singly and in comma-separated 
 messages as well as just lists. Nothing comes out.
 


 According to IOhannes,

 the problem is rather, that ALSA sequencer does not support MIDI in a
 way Pd would like it, mainly: no raw midi.

 
 Yes, it looks like the ALSA function  being called expects a complete 
 sysex message but instead it's getting one byte at a time. I guess Pd 
 should buffer the message until it gets an F7 (End of Exclusive) and 
 then send the whole thing as one packet. Not too difficult except for 
 anticipating what the the maximum message size is going to be. Maybe a 
 [sysexout] object that takes lists of bytes (and inserts the F0 and F7) 
 is in order...
 

 Also I think one of the recent posts which I cannot locate now,
 mentioned that it was just a matter of Pd using a function in ALSA API
 other than what is used at the moment.

 
 Well I think it's better to send a complete sysex packet, otherwise it 
 could be trashed by a noteout or similar that occurs before the F7 goes 
 out. Really Pd should buffer the packet and only then send it to ALSA.
 
 Martin
 


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


Re: [PD] netpd broken?

2008-05-31 Thread Enrique Erne



i can open netpd, log in, chat... but as soon as i open creator i get
error: pd-cr.singletons: no such object
and a empty windows pops up: pd cr.singletons (no dash)
netloading a netpd patch doens't work



now i got it to. just tried it with:
Pd-0.40.3-extended-20080531-macosx105-i386

it seems that some dynamic patching tricks are broken. attached example 
isn't working anymore :(. it creates the container subpatches but can't 
create the abstraction inside. could somebody confirm that?


eni
#N canvas 386 22 527 592 10;
#N canvas 17 28 355 263 sub 0;
#N canvas 0 22 450 300 1-subsub 0;
#X restore 10 20 pd 1-subsub;
#N canvas 0 22 450 300 2-subsub 0;
#X restore 10 40 pd 2-subsub;
#N canvas 0 22 450 300 3-subsub 0;
#X restore 10 60 pd 3-subsub;
#N canvas 0 22 450 300 11-subsub 0;
#X restore 10 220 pd 11-subsub;
#N canvas 0 22 450 300 15-subsub 0;
#X restore 10 300 pd 15-subsub;
#N canvas 0 22 450 300 19-subsub 0;
#X restore 10 380 pd 19-subsub;
#N canvas 0 22 450 300 24-subsub 0;
#X restore 10 480 pd 24-subsub;
#N canvas 0 22 450 300 25-subsub 0;
#X restore 10 500 pd 25-subsub;
#N canvas 0 22 450 300 29-subsub 0;
#X restore 10 580 pd 29-subsub;
#N canvas 0 22 450 300 32-subsub 0;
#X restore 10 640 pd 32-subsub;
#N canvas 0 22 450 300 33-subsub 0;
#X restore 10 660 pd 33-subsub;
#N canvas 0 22 450 300 34-subsub 0;
#X restore 10 680 pd 34-subsub;
#N canvas 0 22 450 300 40-subsub 0;
#X restore 10 800 pd 40-subsub;
#N canvas 0 22 450 300 51-subsub 0;
#X restore 10 1020 pd 51-subsub;
#N canvas 0 22 450 300 1-subsub 0;
#X restore 10 20 pd 1-subsub;
#X restore 21 22 pd sub;
#X msg 24 392 \; pd-sub clear;
#X msg 24 233 \; pd-sub loadbang;
#X floatatom 24 79 5 0 0 0 - - -;
#X obj 52 136 * 20;
#X obj 24 96 t f f f;
#X obj 24 116 makefilename pd-%d-subsub;
#X obj 24 156 pack s f f;
#X obj 24 325 makefilename pd-%d-subsub;
#X msg 24 347 \; \$1 clear;
#X floatatom 24 306 5 0 0 0 - - -;
#X text 79 22 add and remove abstractions;
#X msg 21 53 1;
#X msg 61 53 2;
#X msg 97 53 3;
#X text 149 53 a) create some subsubpatches and abstractions;
#X text 148 237 b) if your abstractions use loadbang you have to do
that manually;
#X msg 24 283 1;
#X msg 64 283 2;
#X msg 100 283 3;
#X text 142 398 (clear pd-sub before saving this patch);
#X text 145 282 c) clear subsubpatch where your abstractions are;
#X text 23 506 e) if your abstraction does signal processing you need
to rebuild the dsptree. you could do so by either turn off/on [pd dsp
0 \, pd dsp 1( or dynamically create an other ~-object in a subpatch
and clear it again.;
#X text 25 439 d) if your abstraction has a gui inside that you want
to open sepparately \, use either namecanvas or put the gui in an subpatch
[pd \$1-something] and use an arguemnt as id to refenrence the subpatch.
;
#X msg 24 176 \; pd-sub obj 10 \$2 pd \$3-subsub \; \$1 obj 10 10 my-abstraction
\$3;
#X connect 3 0 5 0;
#X connect 4 0 7 1;
#X connect 5 0 6 0;
#X connect 5 1 4 0;
#X connect 5 2 7 2;
#X connect 6 0 7 0;
#X connect 7 0 24 0;
#X connect 8 0 9 0;
#X connect 10 0 8 0;
#X connect 12 0 3 0;
#X connect 13 0 3 0;
#X connect 14 0 3 0;
#X connect 17 0 10 0;
#X connect 18 0 10 0;
#X connect 19 0 10 0;
___
PD-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


[PD] HID and OS X

2008-05-31 Thread Phil Stone
Hi Hans, and list,

Is [gemmouse] currently the only option available for access to mouse 
(or trackball, in my case) data via HID on OS X?  [gemmouse] works 
great, but I can't get anything else to work...[mouse] (or [darwinhid], 
for that matter) won't instantiate, and [hidio] sees the trackball, but 
doesn't output any data from it.

I searched the archives, but I can't get a clear picture of whether this 
is an OS X problem, or if I've just not configured something properly.  
I'm on Pd version 0.40.3-extended-20071204 for MacIntel.


Phil Stone
www.pkstonemusic.com

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


Re: [PD] pix_resize

2008-05-31 Thread Nicolas Montgermont
Hi list,

I've got he same problem here. It works well with pictures in the 
pix_resize-help patch, but when I'm trying to resize video, I've got the 
error outputted.
For example pix_resize doesn't work when inserted after the pix_video 
object in the pix_video-help patch.
Is there any solution to resize this kind of images?

Thanks,

Nicolas

marius schebella a écrit :
 hi,
 I am getting an error with pix_resize on osx, anybody knows where that 
 is coming from?
 [pix_resize]: gluError 100900: unable to resize image
 pdX latest autobuild.
 marius.

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

   


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


Re: [PD] Getting Sysex output to work on Linux

2008-05-31 Thread Miller Puckette
I'm still curious why the raw MIDI doesn't work for you.  I need to 
find someone with a similar USB MIDI device to try to figure this out.
I did recently find out that the raw interface has a bug that prevents it from
opening /dev/midi for reading only and for writing only; the only operation
that works is for both reading and writing.  I've got a fix for that
(s_midi_oss.c; change two occurrences of devno == 1 to devno == 0).

But this wouldn't help if, as I read your letter, you simply don't see any
input or output devices at all, for instance in the midi settings dialog.
That sounds like a different problem from the one I was having.

cheers
Miller

On Mon, May 26, 2008 at 10:11:53PM +0900, PSPunch wrote:
 
 Ken,
 
  OSS has, IIRC, been deprecated for many years now.
  
  ALSA should be the correct one to use on Linux.
 
 Deprecated in terms of people abandoning it, or is it literally not 
 functioning any more?
 
 
 To be specific, what I am trying to get working is a Korg padKontrol 
 which is basically a USB-MIDI device. As soon at it is connected to my 
 Ubuntu box, it is recognized as an Alsa-MIDI device. When routing this 
 to Pd, only Sysex messages are dropped. (No response when routing 
 directly to kmidimon either)
 
 
 Since Miller had suggested its usage, I was hoping OSS to work but not 
 quite yet.
 I understand that this classic API takes a different approach from ALSA 
 and expects applications to route directly to each other. The list of 
 MIDI devices that Pd offers to connect to is simply blank.
 Is there such thing as a wrapper that lets Alsa-MIDI devices be 
 recognized as OSS devices?
 
 
 --
 David Shimamoto
 
 
  
  And, also, for the past year or so there's been a new JACK MIDI API which 
  is a lot cleaner (and strongly-timed) than ALSA, although it of course uses 
  ALSA for transmission to actual MIDI devices.
  
  -ken
  
 
 
 ___
 PD-list@iem.at mailing list
 UNSUBSCRIBE and account-management - 
 http://lists.puredata.info/listinfo/pd-list

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


Re: [PD] Getting Sysex output to work on Linux

2008-05-31 Thread PSPunch

Hi, Miller,


Yes, it is a USB-MIDI device which currently appears only under the list 
of ALSA-MIDI devices.

However, the same behaviors I've seen apply also to the application 
kmidimon.
I think that if there is a way to get kmidimon to appear as an OSS MIDI 
device, theoretically the same procedure should work with my hardware.

Does anyone know of methods, or perhaps wrappers that may get this going?

--
David Shimamoto


 I'm still curious why the raw MIDI doesn't work for you.  I need to 
 find someone with a similar USB MIDI device to try to figure this out.
 I did recently find out that the raw interface has a bug that prevents it from
 opening /dev/midi for reading only and for writing only; the only operation
 that works is for both reading and writing.  I've got a fix for that
 (s_midi_oss.c; change two occurrences of devno == 1 to devno == 0).
 
 But this wouldn't help if, as I read your letter, you simply don't see any
 input or output devices at all, for instance in the midi settings dialog.
 That sounds like a different problem from the one I was having.
 
 cheers
 Miller
 
 On Mon, May 26, 2008 at 10:11:53PM +0900, PSPunch wrote:
 Ken,

 OSS has, IIRC, been deprecated for many years now.

 ALSA should be the correct one to use on Linux.
 Deprecated in terms of people abandoning it, or is it literally not 
 functioning any more?


 To be specific, what I am trying to get working is a Korg padKontrol 
 which is basically a USB-MIDI device. As soon at it is connected to my 
 Ubuntu box, it is recognized as an Alsa-MIDI device. When routing this 
 to Pd, only Sysex messages are dropped. (No response when routing 
 directly to kmidimon either)


 Since Miller had suggested its usage, I was hoping OSS to work but not 
 quite yet.
 I understand that this classic API takes a different approach from ALSA 
 and expects applications to route directly to each other. The list of 
 MIDI devices that Pd offers to connect to is simply blank.
 Is there such thing as a wrapper that lets Alsa-MIDI devices be 
 recognized as OSS devices?


 --
 David Shimamoto


 And, also, for the past year or so there's been a new JACK MIDI API which 
 is a lot cleaner (and strongly-timed) than ALSA, although it of course uses 
 ALSA for transmission to actual MIDI devices.

 -ken


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


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


[PD] [PD-announce] Pdmtl#27

2008-05-31 Thread Mathieu Bouchard


The PureData users group of Montréal met for the 27th time on May 27th, 
2008. This meeting was an initiative of Marc Fournel. 14 people came this 
time.


The wiki page of the meeting is in French, but even if you don't speak 
French you may find the links to be interesting.


  http://wiki.dataflow.ws/PdMtl/27

(note: this page doesn't have photos of the meeting yet.)

 _ _ __ ___ _  _ _ ...
| Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec___
PD-announce mailing list
[EMAIL PROTECTED]
http://lists.puredata.info/listinfo/pd-announce
___
PD-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


[PD] [PD-announce] GridFlow 0.9.2

2008-05-31 Thread Mathieu Bouchard


I had skipped this announcement. This was released (in 
http://gridflow.ca/download) a month ago, during the GridFlow workshop 
that was held in São Paulo at the time of the Brasilian Pd Convention of 
2008.


ChangeLog for version 0.9.2 (2008.05.02):

 * removed libruby dependency

 _ _ __ ___ _  _ _ ...
| Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada___
PD-announce mailing list
[EMAIL PROTECTED]
http://lists.puredata.info/listinfo/pd-announce
___
PD-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list