[PD] Pd-list Digest, Vol 52, Issue 19
michael green
mikegreen_london at yahoo.co.uk
Wed Jul 8 08:51:59 CEST 2009
http://www.mnml.nl/phpBB2/viewtopic.php?t=49126
michael green
---------------------
m: 010 4910 2282
w: http://soundcloud.com/greenbuddha
________________________________
From: "pd-list-request at iem.at" <pd-list-request at iem.at>
To: pd-list at iem.at
Sent: Wednesday, 8 July, 2009 13:17:39
Subject: Pd-list Digest, Vol 52, Issue 19
Send Pd-list mailing list submissions to
pd-list at iem.at
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.puredata.info/listinfo/pd-list
or, via email, send a message with subject or body 'help' to
pd-list-request at iem.at
You can reach the person managing the list at
pd-list-owner at iem.at
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Pd-list digest..."
Today's Topics:
1. Re: Sysex out problems (linux only) (Alex)
2. Re: Sysex out problems (linux only) (Andr?s Mur?nyi)
3. Re: Sysex out problems (linux only) (Alex)
4. Re: Sysex out problems (linux only) (Andr?s Mur?nyi)
5. Re: Sysex out problems (linux only) (Martin Peach)
6. Re: workshop in Boston August 1st (ydegoyon at gmail.com)
----------------------------------------------------------------------
Message: 1
Date: Tue, 7 Jul 2009 17:08:13 -0700
From: Alex <x37v.alex at gmail.com>
Subject: Re: [PD] Sysex out problems (linux only)
To: Andr?s Mur?nyi <muranyia at gmail.com>
Cc: pd-list at iem.at
Message-ID:
<c5e6c7e30907071708t2737b929gcad15b983ca0b377 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
I haven't actually tested sysex out limits, but sysex in is limited to
something like 24 byte messages..
here is a thread where i talk about it:
http://lists.puredata.info/pipermail/pd-list/2009-01/067372.html
It is hard coded into the source. You can modify the source to change
the hard coded limit.. i have a diff on that thread which shows how i
did it.
It would be nice if this limit was either totally removed or
dynamically growable.. as it would be really nice to be able to write
real sysex editors in PD.
I have been creating my own physical devices with sysex and I use pd
to edit the sysex data but i have to make my sysex packets short
because of PD's limitations.
-Alex
2009/7/7 Andr?s Mur?nyi <muranyia at gmail.com>:
> Dear Sirs,
>
> I just have never been successful with sysex in Pd and I'm asking for your
> kind advice.
> Attached is an example for a long sysex message which goes out on [midiout]
> (linux only, afaik).
> The problems I have:
> - sysex gets fragmented (also when nothing is sent out meanwhile by other
> objects).. It is always properly terminated with '247' but the content is
> often truncated. Is this a bug/feature...? What is your best recommendation
> knowing that my patch is full of sysex outs (+envelopes on some of them!)
> - sysex just magically does not work on the target machine ;o) I have no
> clue why except for this thing with being truncated but it *never* works
> even if the message seems to go out intact. Even more interesting that the
> machine shows me that it is recieving sysex! Tried with the mpu-401 of an
> Audigy and with a MOTU 828 mkII through Jack and a2jmidid (jack-alsa midi
> bridge). Sysex is
>
> Thanks a Lot!
>
> --
> Muranyi Andras
>
> _______________________________________________
> Pd-list at iem.at mailing list
> UNSUBSCRIBE and account-management ->
> http://lists.puredata.info/listinfo/pd-list
>
>
------------------------------
Message: 2
Date: Wed, 8 Jul 2009 02:23:00 +0200
From: Andr?s Mur?nyi <muranyia at gmail.com>
Subject: Re: [PD] Sysex out problems (linux only)
To: pd-list at iem.at
Message-ID:
<23cdbfeb0907071723t75a155d0p824b42bf4879e13f at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
2009/7/8 Alex <x37v.alex at gmail.com>
> > - sysex gets fragmented (also when nothing is sent out meanwhile by other
> > objects). It is always properly terminated with '247' but the content is
> > often truncated. Is this a bug/feature...? What is your best
> recommendation
> > knowing that my patch is full of sysex outs (+envelopes on some of them!)
> > - sysex just magically does not work on the target machine ;o) I have no
> > clue why except for this thing with being truncated but it *never* works
> > even if the message seems to go out intact. Even more interesting that
> the
> > machine shows me that it is recieving sysex! Tried with the mpu-401 of an
> > Audigy and with a MOTU 828 mkII through Jack and a2jmidid (jack-alsa midi
> > bridge).
>
>
I haven't actually tested sysex out limits, but sysex in is limited to
> something like 24 byte messages..
>
> here is a thread where i talk about it:
> http://lists.puredata.info/pipermail/pd-list/2009-01/067372..html
>
> It is hard coded into the source. You can modify the source to change
> the hard coded limit.. i have a diff on that thread which shows how i
> did it.
>
Thanks Alex, it's an important thing to know.
My sysex is shorter than 24B it's just broken.
What we shall see repeating is 240 67 16 73 8 16 19 (knobvalue) 247
Instead I'm having this grinded mess coming back on physical loopback:
print: 240
print: 67
print: 16
print: 247
print: 240
print: 67
print: 247
print: 240
print: 67
print: 16
print: 247
print: 240
print: 67
print: 16
print: 73
print: 247
print: 240
print: 67
print: 16
print: 73
print: 8
print: 247
print: 240
print: 67
print: 16
print: 73
print: 247
print: 240
print: 67
print: 16
print: 247
print: 240
print: 67
print: 16
print: 247
print: 240
print: 67
print: 16
print: 73
print: 8
print: 247
print: 240
print: 67
print: 16
print: 247
print: 240
print: 67
print: 16
print: 73
print: 247
print: 240
print: 67
print: 16
print: 73
print: 247
print: 240
print: 67
print: 16
print: 73
print: 247
This makes me think I'm trying to send too much data in too short
intervals...? Is there a handy way to limit the density of my output? (i
think its not not [drip] as it has to stay realtime)
I'm not very experienced, sorry if this traces back to something very
obvious!
--
Muranyi Andras
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20090708/b5e63f36/attachment-0001.htm>
------------------------------
Message: 3
Date: Tue, 7 Jul 2009 17:32:04 -0700
From: Alex <x37v.alex at gmail.com>
Subject: Re: [PD] Sysex out problems (linux only)
To: Andr?s Mur?nyi <muranyia at gmail.com>
Cc: pd-list at iem.at
Message-ID:
<c5e6c7e30907071732h57728befp5e6088c87e89f0e5 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
It looks like you may experiencing another thing that i've complained
about... pd's alsa midi connects to all MIDI inputs and outputs that
it can.. this includes alsa's MIDI through.. so everything that you
send out gets echoed back into the input.. SUPER annoying.
run aconnect [or easier, though not great, aconnectgui] and see if
that is the case for you.. disconnect pd from the alsa through port.
-Alex
2009/7/7 Andr?s Mur?nyi <muranyia at gmail.com>:
>
> 2009/7/8 Alex <x37v.alex at gmail.com>
>>
>> > - sysex gets fragmented (also when nothing is sent out meanwhile by
>> > other
>> > objects). It is always properly terminated with '247' but the content is
>> > often truncated. Is this a bug/feature...? What is your best
>> > recommendation
>> > knowing that my patch is full of sysex outs (+envelopes on some of
>> > them!)
>> > - sysex just magically does not work on the target machine ;o) I have no
>> > clue why except for this thing with being truncated but it *never* works
>> > even if the message seems to go out intact. Even more interesting that
>> > the
>> > machine shows me that it is recieving sysex! Tried with the mpu-401 of
>> > an
>> > Audigy and with a MOTU 828 mkII through Jack and a2jmidid (jack-alsa
>> > midi
>> > bridge).
>>
>>
>>
>> I haven't actually tested sysex out limits, but sysex in is limited to
>> something like 24 byte messages..
>>
>> here is a thread where i talk about it:
>> http://lists.puredata.info/pipermail/pd-list/2009-01/067372.html
>>
>> It is hard coded into the source. You can modify the source to change
>> the hard coded limit.. i have a diff on that thread which shows how i
>> did it.
>
> Thanks Alex, it's an important thing to know.
> My sysex is shorter than 24B it's just broken.
> What we shall see repeating is 240 67 16 73 8 16 19 (knobvalue) 247
>
> Instead I'm having this grinded mess coming back on physical loopback:
>
> print: 240
> print: 67
> print: 16
> print: 247
> print: 240
> print: 67
> print: 247
> print: 240
> print: 67
> print: 16
> print: 247
> print: 240
> print: 67
> print: 16
> print: 73
> print: 247
> print: 240
> print: 67
> print: 16
> print: 73
> print: 8
> print: 247
> print: 240
> print: 67
> print: 16
> print: 73
> print: 247
> print: 240
> print: 67
> print: 16
> print: 247
> print: 240
> print: 67
> print: 16
> print: 247
> print: 240
> print: 67
> print: 16
> print: 73
> print: 8
> print: 247
> print: 240
> print: 67
> print: 16
> print: 247
> print: 240
> print: 67
> print: 16
> print: 73
> print: 247
> print: 240
> print: 67
> print: 16
> print: 73
> print: 247
> print: 240
> print: 67
> print: 16
> print: 73
> print: 247
>
> This makes me think I'm trying to send too much data in too short
> intervals...? Is there a handy way to limit the density of my output? (i
> think its not not [drip] as it has to stay realtime)
> I'm not very experienced, sorry if this traces back to something very
> obvious!
>
> --
> Muranyi Andras
>
> _______________________________________________
> Pd-list at iem.at mailing list
> UNSUBSCRIBE and account-management ->
> http://lists.puredata.info/listinfo/pd-list
>
>
------------------------------
Message: 4
Date: Wed, 8 Jul 2009 02:59:34 +0200
From: Andr?s Mur?nyi <muranyia at gmail.com>
Subject: Re: [PD] Sysex out problems (linux only)
To: pd-list at iem.at
Message-ID:
<23cdbfeb0907071759k448d0362uc104e9973c1d48ca at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
2009/7/8 Alex <x37v.alex at gmail.com>
> It looks like you may experiencing another thing that i've complained
> about... pd's alsa midi connects to all MIDI inputs and outputs that
> it can.. this includes alsa's MIDI through.. so everything that you
> send out gets echoed back into the input.. SUPER annoying.
>
> run aconnect [or easier, though not great, aconnectgui] and see if
> that is the case for you.. disconnect pd from the alsa through port.
>
I've checked and it's ok. Right now have the output looped back with a cable
but it only comes back once.
> > This makes me think I'm trying to send too much data in too short
> > intervals...? Is there a handy way to limit the density of my output? (i
> > think its not not [drip] as it has to stay realtime)
>
What about dropping some data before making up / sending out the sysex? My
best guess was storing into [float] and firing it with [metro] or [pulse] at
a constant, decent rate.
--
Muranyi Andras
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists..puredata.info/pipermail/pd-list/attachments/20090708/2ef7e441/attachment-0001.htm>
------------------------------
Message: 5
Date: Tue, 07 Jul 2009 23:00:10 -0400
From: Martin Peach <martin.peach at sympatico.ca>
Subject: Re: [PD] Sysex out problems (linux only)
To: Andr?s Mur?nyi <muranyia at gmail.com>
Cc: pd-list at iem.at
Message-ID: <BLU0-SMTP70D9EFA8A05F5DD2BD52C2ED290 at phx.gbl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Andr?s Mur?nyi wrote:
> Dear Sirs,
>
> I just have never been successful with sysex in Pd and I'm asking for
> your kind advice.
> Attached is an example for a long sysex message which goes out on
> [midiout] (linux only, afaik).
> The problems I have:
> - sysex gets fragmented (also when nothing is sent out meanwhile by
> other objects). It is always properly terminated with '247' but the
> content is often truncated. Is this a bug/feature...? What is your best
> recommendation knowing that my patch is full of sysex outs (+envelopes
> on some of them!)
in the patch you posted, the message you send to [midiout] is
[240,67,16,73,8,$2,19,$1,247(
, which Pd takes as 9 separate messages because of the comma in between
each item.
Probably [240 67 16 73 8 $2 19 $1 247( would work better.
Martin
------------------------------
Message: 6
Date: Wed, 08 Jul 2009 06:18:10 +0200
From: "ydegoyon at gmail.com" <ydegoyon at gmail.com>
Subject: Re: [PD] workshop in Boston August 1st
To: chris clepper <cgclepper at gmail.com>
Cc: PD list <pd-list at iem.at>
Message-ID: <4A541E02.5020608 at gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
perfect you don't answer,
40 dollars and forbidden to use linux?
no thank you, man
ydegoyon at gmail.com wrote:
> Laptops running Linux cannot be used. !!
>
> i'd like to know why?
> something missing on linux?
>
> chris clepper wrote:
>> I am doing a basic Pd workshop in the Boston area on August 1st at
>> Axiom Gallery. I will be covering simple patching, audio and GEM.
>> The optional first hour will be dedicated to setting up the
>> participant's laptops with Pd and getting audio and MIDI working.
>> Space is limited to 12 and you must register online.
>>
>> Details on this page:
>> http://www.axiomart.org/events.php
>>
>> I hope to do a more advanced video/GEM workshop in the coming months
>> as well.
>>
>> Chris
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Pd-list at iem.at mailing list
>> UNSUBSCRIBE and account-management ->
>> http://lists.puredata.info/listinfo/pd-list
>>
>
>
------------------------------
_______________________________________________
Pd-list mailing list
Pd-list at iem.at
to manage your subscription (including un-subscription) see
http://lists.puredata.info/listinfo/pd-list
End of Pd-list Digest, Vol 52, Issue 19
***************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20090707/543a67e8/attachment.htm>
More information about the Pd-list
mailing list