subject:"\[PD\] sysex messages"

Re: [PD] sysex messages

2018-03-14 Thread Dan Wilcox

Active sense messages come through now. ALL MIDI messages do.

> On Mar 15, 2018, at 12:07 AM, mario buoninfante <mario.buoninfa...@gmail.com> 
> wrote:
> 
> but still if I'm not wrong we don't deal with Active Sensing. am I wrong?
> 
> On 14/03/18 23:06, Dan Wilcox wrote:
>> It's probably not the changes to the alsa code but more likely those to the 
>> general MIDI parser in s_midi.c. It now handles all message types as well as 
>> realtime bytes within other messages and running status messages.
>> 
>>> On Mar 15, 2018, at 12:00 AM, mario buoninfante 
>>> <mario.buoninfa...@gmail.com <mailto:mario.buoninfa...@gmail.com>> wrote:
>>> 
>>> it looks like your guess definitely worked :D
>>> 
>>> 
>>> thanks,
>>> 
>>> Mario
>>> 
>>> On 14/03/18 22:32, Dan Wilcox wrote:
>>>> I essentially overhauled the MIDI handling so all message types can be 
>>>> sent/received, but I only made a "pretty good guess" with the ALSA 
>>>> interface as I didn't personally test on Linux. Relevant info is here: 
>>>> https://github.com/pure-data/pure-data/pull/214 
>>>> <https://github.com/pure-data/pure-data/pull/214>
>>>> 
>>>>> On Mar 14, 2018, at 11:21 PM, pd-list-requ...@lists.iem.at 
>>>>> <mailto:pd-list-requ...@lists.iem.at> wrote:
>>>>> 
>>>>> From: Miller Puckette <m...@ucsd.edu <mailto:m...@ucsd.edu>>
>>>>> To: mario buoninfante <mario.buoninfa...@gmail.com 
>>>>> <mailto:mario.buoninfa...@gmail.com>>
>>>>> Cc: Simon Iten <itensi...@gmail.com <mailto:itensi...@gmail.com>>, pd 
>>>>> list <pd-l...@iem.at <mailto:pd-l...@iem.at>>
>>>>> Subject: Re: [PD] sysex messages
>>>>> Message-ID: <20180314222113.GL7620@elroy.localdomain 
>>>>> <mailto:20180314222113.GL7620@elroy.localdomain>>
>>>>> Content-Type: text/plain; charset=utf-8
>>>>> 
>>>>> Aha!  Yes, Dan Wilcox contributed a whole raft of changes to s_midi_alsa.c
>>>>> August 2017.  So it looks like we're in the clear after all...
>>>>> 
>>>>> cheers
>>>>> Miller
>>>> 
>>>> 
>>>> Dan Wilcox
>>>> @danomatika <http://twitter.com/danomatika>
>>>> danomatika.com <http://danomatika.com/>
>>>> robotcowboy.com <http://robotcowboy.com/>
>>>> 
>>>> 
>>>> 
>>> 
>> 
>> 
>> Dan Wilcox
>> @danomatika <http://twitter.com/danomatika>
>> danomatika.com <http://danomatika.com/>
>> robotcowboy.com <http://robotcowboy.com/>
>> 
>> 
>> 
> 


Dan Wilcox
@danomatika <http://twitter.com/danomatika>
danomatika.com <http://danomatika.com/>
robotcowboy.com <http://robotcowboy.com/>



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

Re: [PD] sysex messages

2018-03-14 Thread mario buoninfante


but still if I'm not wrong we don't deal with Active Sensing. am I wrong?


On 14/03/18 23:06, Dan Wilcox wrote:
It's probably not the changes to the alsa code but more likely those 
to the general MIDI parser in s_midi.c. It now handles all message 
types as well as realtime bytes within other messages and running 
status messages.


On Mar 15, 2018, at 12:00 AM, mario buoninfante 
<mario.buoninfa...@gmail.com <mailto:mario.buoninfa...@gmail.com>> wrote:


it looks like your guess definitely worked :D


thanks,

Mario


On 14/03/18 22:32, Dan Wilcox wrote:
I essentially overhauled the MIDI handling so all message types can 
be sent/received, but I only made a "pretty good guess" with the 
ALSA interface as I didn't personally test on Linux. Relevant info 
is here: https://github.com/pure-data/pure-data/pull/214


On Mar 14, 2018, at 11:21 PM, pd-list-requ...@lists.iem.at 
<mailto:pd-list-requ...@lists.iem.at> wrote:


From: Miller Puckette <m...@ucsd.edu <mailto:m...@ucsd.edu>>
To: mario buoninfante <mario.buoninfa...@gmail.com 
<mailto:mario.buoninfa...@gmail.com>>
Cc: Simon Iten <itensi...@gmail.com <mailto:itensi...@gmail.com>>, 
pd list <pd-l...@iem.at <mailto:pd-l...@iem.at>>

Subject: Re: [PD] sysex messages
Message-ID: <20180314222113.GL7620@elroy.localdomain 
<mailto:20180314222113.GL7620@elroy.localdomain>>

Content-Type: text/plain; charset=utf-8

Aha!  Yes, Dan Wilcox contributed a whole raft of changes to 
s_midi_alsa.c

August 2017.  So it looks like we're in the clear after all...

cheers
Miller



Dan Wilcox
@danomatika <http://twitter.com/danomatika>
danomatika.com <http://danomatika.com/>
robotcowboy.com <http://robotcowboy.com/>








Dan Wilcox
@danomatika <http://twitter.com/danomatika>
danomatika.com <http://danomatika.com>
robotcowboy.com <http://robotcowboy.com>





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

Re: [PD] sysex messages

2018-03-14 Thread Dan Wilcox

It's probably not the changes to the alsa code but more likely those to the 
general MIDI parser in s_midi.c. It now handles all message types as well as 
realtime bytes within other messages and running status messages.

> On Mar 15, 2018, at 12:00 AM, mario buoninfante <mario.buoninfa...@gmail.com> 
> wrote:
> 
> it looks like your guess definitely worked :D
> 
> 
> thanks,
> 
> Mario
> 
> On 14/03/18 22:32, Dan Wilcox wrote:
>> I essentially overhauled the MIDI handling so all message types can be 
>> sent/received, but I only made a "pretty good guess" with the ALSA interface 
>> as I didn't personally test on Linux. Relevant info is here: 
>> https://github.com/pure-data/pure-data/pull/214 
>> <https://github.com/pure-data/pure-data/pull/214>
>> 
>>> On Mar 14, 2018, at 11:21 PM, pd-list-requ...@lists.iem.at 
>>> <mailto:pd-list-requ...@lists.iem.at> wrote:
>>> 
>>> From: Miller Puckette <m...@ucsd.edu <mailto:m...@ucsd.edu>>
>>> To: mario buoninfante <mario.buoninfa...@gmail.com 
>>> <mailto:mario.buoninfa...@gmail.com>>
>>> Cc: Simon Iten <itensi...@gmail.com <mailto:itensi...@gmail.com>>, pd list 
>>> <pd-l...@iem.at <mailto:pd-l...@iem.at>>
>>> Subject: Re: [PD] sysex messages
>>> Message-ID: <20180314222113.GL7620@elroy.localdomain 
>>> <mailto:20180314222113.GL7620@elroy.localdomain>>
>>> Content-Type: text/plain; charset=utf-8
>>> 
>>> Aha!  Yes, Dan Wilcox contributed a whole raft of changes to s_midi_alsa.c
>>> August 2017.  So it looks like we're in the clear after all...
>>> 
>>> cheers
>>> Miller
>> 
>> 
>> Dan Wilcox
>> @danomatika <http://twitter.com/danomatika>
>> danomatika.com <http://danomatika.com/>
>> robotcowboy.com <http://robotcowboy.com/>
>> 
>> 
>> 
> 


Dan Wilcox
@danomatika <http://twitter.com/danomatika>
danomatika.com <http://danomatika.com/>
robotcowboy.com <http://robotcowboy.com/>



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

Re: [PD] sysex messages

2018-03-14 Thread mario buoninfante


it looks like your guess definitely worked :D


thanks,

Mario


On 14/03/18 22:32, Dan Wilcox wrote:
I essentially overhauled the MIDI handling so all message types can be 
sent/received, but I only made a "pretty good guess" with the ALSA 
interface as I didn't personally test on Linux. Relevant info is here: 
https://github.com/pure-data/pure-data/pull/214


On Mar 14, 2018, at 11:21 PM, pd-list-requ...@lists.iem.at 
<mailto:pd-list-requ...@lists.iem.at> wrote:


From: Miller Puckette <m...@ucsd.edu <mailto:m...@ucsd.edu>>
To: mario buoninfante <mario.buoninfa...@gmail.com 
<mailto:mario.buoninfa...@gmail.com>>
Cc: Simon Iten <itensi...@gmail.com <mailto:itensi...@gmail.com>>, pd 
list <pd-l...@iem.at <mailto:pd-l...@iem.at>>

Subject: Re: [PD] sysex messages
Message-ID: <20180314222113.GL7620@elroy.localdomain 
<mailto:20180314222113.GL7620@elroy.localdomain>>

Content-Type: text/plain; charset=utf-8

Aha!  Yes, Dan Wilcox contributed a whole raft of changes to 
s_midi_alsa.c

August 2017.  So it looks like we're in the clear after all...

cheers
Miller



Dan Wilcox
@danomatika <http://twitter.com/danomatika>
danomatika.com <http://danomatika.com>
robotcowboy.com <http://robotcowboy.com>





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

Re: [PD] sysex messages

2018-03-14 Thread Dan Wilcox

I essentially overhauled the MIDI handling so all message types can be 
sent/received, but I only made a "pretty good guess" with the ALSA interface as 
I didn't personally test on Linux. Relevant info is here: 
https://github.com/pure-data/pure-data/pull/214 
<https://github.com/pure-data/pure-data/pull/214>

> On Mar 14, 2018, at 11:21 PM, pd-list-requ...@lists.iem.at wrote:
> 
> From: Miller Puckette <m...@ucsd.edu <mailto:m...@ucsd.edu>>
> To: mario buoninfante <mario.buoninfa...@gmail.com 
> <mailto:mario.buoninfa...@gmail.com>>
> Cc: Simon Iten <itensi...@gmail.com <mailto:itensi...@gmail.com>>, pd list 
> <pd-l...@iem.at <mailto:pd-l...@iem.at>>
> Subject: Re: [PD] sysex messages
> Message-ID: <20180314222113.GL7620@elroy.localdomain 
> <mailto:20180314222113.GL7620@elroy.localdomain>>
> Content-Type: text/plain; charset=utf-8
> 
> Aha!  Yes, Dan Wilcox contributed a whole raft of changes to s_midi_alsa.c
> August 2017.  So it looks like we're in the clear after all...
> 
> cheers
> Miller


Dan Wilcox
@danomatika <http://twitter.com/danomatika>
danomatika.com <http://danomatika.com/>
robotcowboy.com <http://robotcowboy.com/>



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

Re: [PD] sysex messages

2018-03-14 Thread mario buoninfante

amazing, this makes sense. now I'm just curious to have a look at the 
code and compare it with the latest version.


thanks for your help :D


cheers,

Mario


On 14/03/18 22:21, Miller Puckette wrote:

Aha!  Yes, Dan Wilcox contributed a whole raft of changes to s_midi_alsa.c
August 2017.  So it looks like we're in the clear after all...

cheers
Miller

On Wed, Mar 14, 2018 at 10:06:10PM +, mario buoninfante wrote:

Hi Simon,

yes the message is received and understood by other devices, so at the end
of the day it's not a problem, mine is more curiosity :D

btw I've got a little update, after chatting with another Pd user, I figured
it out that the problem doesn't occur on Pd 0.48.0 and 0.48.1 . but it does
occur on Pd 0.46.1, the version I was using when I discovered this.
so my suspect is that something changed in the code. I'll have a look at
github. does anyone know anything about that>


cheers,
Mario

On 14/03/18 21:49, Simon Iten wrote:

hi there,

i have sent sysex with puredata for some years now, and i never had any
problems, even with large chunks.
i have used attached abstraction to send sysex, maybe it helps?

midi IS a serial protocol, so it is perfectly valid to send one byte at
a time at least over din midi. in fact i am doing that with arduinos all
the time.  (usb midi is a different beast)

do the “special” midiout noteon and noteoff messages work when a
synthmodule or similar is connected?





On 14 Mar 2018, at 21:28, mario buoninfante
>
wrote:

Hi Miller,

yap I'm using ALSA.

btw, I had a look at the source code (I want to clarify I'm not a C
programmer :) ) and from what I found in x_midi.c and s_midi.c, it
kind of make sense that [midiout] returns 1 byte at time.

it seems to me we're missing a way to detect outgoing sysex messages
(maybe having a dedicated object could help), so there's no way to
collect a sysex and send it out in one go (ie having an array to
return). I apologize for my trivial description of the "problem",
but this is what I think is causing this behaviour.


cheers,

Mario


On 13/03/18 04:37, Miller Puckette wrote:

Hi Mario -

Perhaps you said this in the previous message which I missed... are you
using ALSA MIDI system or OSS?

MIDI support has always been a problem in Pd... largely because I don't have
a lot of experience with it.

cheers
Miller

On Tue, Mar 13, 2018 at 12:04:00AM +, mario buoninfante wrote:

Hi,


I ran few more tests on Linux trying to understand what's going on with
[midiout] and sysex messages.

I discovered that it's not just about sysex. I'm monitoring MIDI from Pd
with /KMidimon /and /GMIDImonitor/, and I noticed that also sending Note On
messages with [midiout] seems to be in some way different then sending the
same message using [noteout].

when Note On is sent using [midiout], this will spit single bytes that are
recognized as single byte sysex messages by the MIDI monitors!

has anyone ever experienced the same?


cheers,

Mario


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

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

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



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

Re: [PD] sysex messages

2018-03-14 Thread Miller Puckette

Aha!  Yes, Dan Wilcox contributed a whole raft of changes to s_midi_alsa.c
August 2017.  So it looks like we're in the clear after all...

cheers
Miller

On Wed, Mar 14, 2018 at 10:06:10PM +, mario buoninfante wrote:
> Hi Simon,
> 
> yes the message is received and understood by other devices, so at the end
> of the day it's not a problem, mine is more curiosity :D
> 
> btw I've got a little update, after chatting with another Pd user, I figured
> it out that the problem doesn't occur on Pd 0.48.0 and 0.48.1 . but it does 
> occur on Pd 0.46.1, the version I was using when I discovered this.
> so my suspect is that something changed in the code. I'll have a look at
> github. does anyone know anything about that>
> 
> 
> cheers,
> Mario
> 
> On 14/03/18 21:49, Simon Iten wrote:
> > hi there,
> > 
> > i have sent sysex with puredata for some years now, and i never had any
> > problems, even with large chunks.
> > i have used attached abstraction to send sysex, maybe it helps?
> > 
> > midi IS a serial protocol, so it is perfectly valid to send one byte at
> > a time at least over din midi. in fact i am doing that with arduinos all
> > the time.  (usb midi is a different beast)
> > 
> > do the “special” midiout noteon and noteoff messages work when a
> > synthmodule or similar is connected?
> > 
> > 
> > 
> > 
> > > On 14 Mar 2018, at 21:28, mario buoninfante
> > > >
> > > wrote:
> > > 
> > > Hi Miller,
> > > 
> > > yap I'm using ALSA.
> > > 
> > > btw, I had a look at the source code (I want to clarify I'm not a C
> > > programmer :) ) and from what I found in x_midi.c and s_midi.c, it
> > > kind of make sense that [midiout] returns 1 byte at time.
> > > 
> > > it seems to me we're missing a way to detect outgoing sysex messages
> > > (maybe having a dedicated object could help), so there's no way to
> > > collect a sysex and send it out in one go (ie having an array to
> > > return). I apologize for my trivial description of the "problem",
> > > but this is what I think is causing this behaviour.
> > > 
> > > 
> > > cheers,
> > > 
> > > Mario
> > > 
> > > 
> > > On 13/03/18 04:37, Miller Puckette wrote:
> > > > Hi Mario -
> > > > 
> > > > Perhaps you said this in the previous message which I missed... are you
> > > > using ALSA MIDI system or OSS?
> > > > 
> > > > MIDI support has always been a problem in Pd... largely because I don't 
> > > > have
> > > > a lot of experience with it.
> > > > 
> > > > cheers
> > > > Miller
> > > > 
> > > > On Tue, Mar 13, 2018 at 12:04:00AM +, mario buoninfante wrote:
> > > > > Hi,
> > > > > 
> > > > > 
> > > > > I ran few more tests on Linux trying to understand what's going on 
> > > > > with
> > > > > [midiout] and sysex messages.
> > > > > 
> > > > > I discovered that it's not just about sysex. I'm monitoring MIDI from 
> > > > > Pd
> > > > > with /KMidimon /and /GMIDImonitor/, and I noticed that also sending 
> > > > > Note On
> > > > > messages with [midiout] seems to be in some way different then 
> > > > > sending the
> > > > > same message using [noteout].
> > > > > 
> > > > > when Note On is sent using [midiout], this will spit single bytes 
> > > > > that are
> > > > > recognized as single byte sysex messages by the MIDI monitors!
> > > > > 
> > > > > has anyone ever experienced the same?
> > > > > 
> > > > > 
> > > > > cheers,
> > > > > 
> > > > > Mario
> > > > > 
> > > > > 
> > > > > ___
> > > > > Pd-list@lists.iem.at  mailing list
> > > > > UNSUBSCRIBE and account-management 
> > > > > ->https://lists.puredata.info/listinfo/pd-list
> > > 
> > > ___
> > > Pd-list@lists.iem.at  mailing list
> > > UNSUBSCRIBE and account-management ->
> > > https://lists.puredata.info/listinfo/pd-list
> > 
> 

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


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

Re: [PD] sysex messages

2018-03-14 Thread mario buoninfante

yap I start thinking the same. also because I had a chat with a 
colleague who's a programmer, who told me that for example on MacOS 
there is a process called something like MIDI Manager which sits in the 
middle and buffers up all the messages, forwarding them to applications 
that are listening to the ports.


so probably this is what is missing (or simply working differently) on 
Linux with ALSA.



cheers,

Mario


On 14/03/18 21:53, Miller Puckette wrote:

This seems to be a specific problem with sysex-handling using linux/ALSA...
if you're using 'OSS' MIDI back end it should work fine.

Incidentally, I think the best fix would be to start using portmidi to address
linux/ALSA.

(An easier one would be to just use OSS but there are features in the ALSA
driver such as loopback that I think you can't get in OSS emulation, so
some MIDI users on linux are forced into the ALSA API.

cheers
Miller

On Wed, Mar 14, 2018 at 10:49:28PM +0100, Simon Iten wrote:

hi there,

i have sent sysex with puredata for some years now, and i never had any 
problems, even with large chunks.
i have used attached abstraction to send sysex, maybe it helps?

midi IS a serial protocol, so it is perfectly valid to send one byte at a time 
at least over din midi. in fact i am doing that with arduinos all the time.  
(usb midi is a different beast)

do the “special” midiout noteon and noteoff messages work when a synthmodule or 
similar is connected?



On 14 Mar 2018, at 21:28, mario buoninfante  wrote:

Hi Miller,

yap I'm using ALSA.
btw, I had a look at the source code (I want to clarify I'm not a C programmer 
:) ) and from what I found in x_midi.c and s_midi.c, it kind of make sense that 
[midiout] returns 1 byte at time.

it seems to me we're missing a way to detect outgoing sysex messages (maybe having a 
dedicated object could help), so there's no way to collect a sysex and send it out in one 
go (ie having an array to return). I apologize for my trivial description of the 
"problem", but this is what I think is causing this behaviour.



cheers,

Mario


On 13/03/18 04:37, Miller Puckette wrote:

Hi Mario -

Perhaps you said this in the previous message which I missed... are you
using ALSA MIDI system or OSS?

MIDI support has always been a problem in Pd... largely because I don't have
a lot of experience with it.

cheers
Miller

On Tue, Mar 13, 2018 at 12:04:00AM +, mario buoninfante wrote:

Hi,


I ran few more tests on Linux trying to understand what's going on with
[midiout] and sysex messages.

I discovered that it's not just about sysex. I'm monitoring MIDI from Pd
with /KMidimon /and /GMIDImonitor/, and I noticed that also sending Note On
messages with [midiout] seems to be in some way different then sending the
same message using [noteout].

when Note On is sent using [midiout], this will spit single bytes that are
recognized as single byte sysex messages by the MIDI monitors!

has anyone ever experienced the same?


cheers,

Mario


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


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

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



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

Re: [PD] sysex messages

2018-03-14 Thread mario buoninfante


Hi Simon,

yes the message is received and understood by other devices, so at the 
end of the day it's not a problem, mine is more curiosity :D


btw I've got a little update, after chatting with another Pd user, I 
figured it out that the problem doesn't occur on Pd 0.48.0 and 0.48.1 . 
but it does  occur on Pd 0.46.1, the version I was using when I 
discovered this.
so my suspect is that something changed in the code. I'll have a look at 
github. does anyone know anything about that>



cheers,
Mario

On 14/03/18 21:49, Simon Iten wrote:

hi there,

i have sent sysex with puredata for some years now, and i never had 
any problems, even with large chunks.

i have used attached abstraction to send sysex, maybe it helps?

midi IS a serial protocol, so it is perfectly valid to send one byte 
at a time at least over din midi. in fact i am doing that with 
arduinos all the time.  (usb midi is a different beast)


do the “special” midiout noteon and noteoff messages work when a 
synthmodule or similar is connected?





On 14 Mar 2018, at 21:28, mario buoninfante 
> wrote:


Hi Miller,

yap I'm using ALSA.

btw, I had a look at the source code (I want to clarify I'm not a C 
programmer :) ) and from what I found in x_midi.c and s_midi.c, it 
kind of make sense that [midiout] returns 1 byte at time.


it seems to me we're missing a way to detect outgoing sysex messages 
(maybe having a dedicated object could help), so there's no way to 
collect a sysex and send it out in one go (ie having an array to 
return). I apologize for my trivial description of the "problem", but 
this is what I think is causing this behaviour.



cheers,

Mario


On 13/03/18 04:37, Miller Puckette wrote:

Hi Mario -

Perhaps you said this in the previous message which I missed... are you
using ALSA MIDI system or OSS?

MIDI support has always been a problem in Pd... largely because I don't have
a lot of experience with it.

cheers
Miller

On Tue, Mar 13, 2018 at 12:04:00AM +, mario buoninfante wrote:

Hi,


I ran few more tests on Linux trying to understand what's going on with
[midiout] and sysex messages.

I discovered that it's not just about sysex. I'm monitoring MIDI from Pd
with /KMidimon /and /GMIDImonitor/, and I noticed that also sending Note On
messages with [midiout] seems to be in some way different then sending the
same message using [noteout].

when Note On is sent using [midiout], this will spit single bytes that are
recognized as single byte sysex messages by the MIDI monitors!

has anyone ever experienced the same?


cheers,

Mario


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


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




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

Re: [PD] sysex messages

2018-03-14 Thread Simon Iten

> On 14 Mar 2018, at 22:53, Miller Puckette  wrote:
> 
> Incidentally, I think the best fix would be to start using portmidi to address
> linux/ALSA.

ahh ok, sorry! funny you should mention that. i use hatari with a synth 
programmer that sends sysex exclusively and i had many problems in the past.
as soon as the hatari code got updated to use portmidi it all started working 
properly, no dropouts or lost bytes anymore. so maybe you can have a peek there?

https://hatari.tuxfamily.org/download.html 

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

Re: [PD] sysex messages

2018-03-14 Thread Miller Puckette

This seems to be a specific problem with sysex-handling using linux/ALSA...
if you're using 'OSS' MIDI back end it should work fine.

Incidentally, I think the best fix would be to start using portmidi to address
linux/ALSA.

(An easier one would be to just use OSS but there are features in the ALSA
driver such as loopback that I think you can't get in OSS emulation, so
some MIDI users on linux are forced into the ALSA API.

cheers
Miller

On Wed, Mar 14, 2018 at 10:49:28PM +0100, Simon Iten wrote:
> hi there,
> 
> i have sent sysex with puredata for some years now, and i never had any 
> problems, even with large chunks.
> i have used attached abstraction to send sysex, maybe it helps?
> 
> midi IS a serial protocol, so it is perfectly valid to send one byte at a 
> time at least over din midi. in fact i am doing that with arduinos all the 
> time.  (usb midi is a different beast) 
> 
> do the “special” midiout noteon and noteoff messages work when a synthmodule 
> or similar is connected?
> 
> 
> > On 14 Mar 2018, at 21:28, mario buoninfante  
> > wrote:
> > 
> > Hi Miller,
> > 
> > yap I'm using ALSA. 
> > btw, I had a look at the source code (I want to clarify I'm not a C 
> > programmer :) ) and from what I found in x_midi.c and s_midi.c, it kind of 
> > make sense that [midiout] returns 1 byte at time.
> > 
> > it seems to me we're missing a way to detect outgoing sysex messages (maybe 
> > having a dedicated object could help), so there's no way to collect a sysex 
> > and send it out in one go (ie having an array to return). I apologize for 
> > my trivial description of the "problem", but this is what I think is 
> > causing this behaviour.
> > 
> > 
> > 
> > cheers,
> > 
> > Mario
> > 
> > 
> > On 13/03/18 04:37, Miller Puckette wrote:
> >> Hi Mario -
> >> 
> >> Perhaps you said this in the previous message which I missed... are you
> >> using ALSA MIDI system or OSS?
> >> 
> >> MIDI support has always been a problem in Pd... largely because I don't 
> >> have
> >> a lot of experience with it.
> >> 
> >> cheers
> >> Miller
> >> 
> >> On Tue, Mar 13, 2018 at 12:04:00AM +, mario buoninfante wrote:
> >>> Hi,
> >>> 
> >>> 
> >>> I ran few more tests on Linux trying to understand what's going on with
> >>> [midiout] and sysex messages.
> >>> 
> >>> I discovered that it's not just about sysex. I'm monitoring MIDI from Pd
> >>> with /KMidimon /and /GMIDImonitor/, and I noticed that also sending Note 
> >>> On
> >>> messages with [midiout] seems to be in some way different then sending the
> >>> same message using [noteout].
> >>> 
> >>> when Note On is sent using [midiout], this will spit single bytes that are
> >>> recognized as single byte sysex messages by the MIDI monitors!
> >>> 
> >>> has anyone ever experienced the same?
> >>> 
> >>> 
> >>> cheers,
> >>> 
> >>> Mario
> >>> 
> >>> 
> >> 
> >>> ___
> >>> Pd-list@lists.iem.at  mailing list
> >>> UNSUBSCRIBE and account-management -> 
> >>> https://lists.puredata.info/listinfo/pd-list 
> >>> 
> > 
> > ___
> > Pd-list@lists.iem.at mailing list
> > UNSUBSCRIBE and account-management -> 
> > https://lists.puredata.info/listinfo/pd-list
> 

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


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

Re: [PD] sysex messages

2018-03-14 Thread Simon Iten

hi there,i have sent sysex with puredata for some years now, and i never had any problems, even with large chunks.i have used attached abstraction to send sysex, maybe it helps?midi IS a serial protocol, so it is perfectly valid to send one byte at a time at least over din midi. in fact i am doing that with arduinos all the time.  (usb midi is a different beast) do the “special” midiout noteon and noteoff messages work when a synthmodule or similar is connected?

sysexout.pd
Description: Binary data
On 14 Mar 2018, at 21:28, mario buoninfante  wrote:
  

  
  Hi Miller,yap I'm using ALSA. 
btw, I had a look at the source code (I want to clarify I'm not a
  C programmer :) ) and from what I found in x_midi.c and s_midi.c,
  it kind of make sense that [midiout] returns 1 byte at time.it seems to me we're missing a way to detect outgoing sysex
  messages (maybe having a dedicated object could help), so there's
  no way to collect a sysex and send it out in one go (ie having an
  array to return). I apologize for my trivial description of
  the "problem", but this is what I think is causing this
  behaviour.

cheers,Mario


On 13/03/18 04:37, Miller Puckette
  wrote:


  Hi Mario -

Perhaps you said this in the previous message which I missed... are you
using ALSA MIDI system or OSS?

MIDI support has always been a problem in Pd... largely because I don't have
a lot of experience with it.

cheers
Miller

On Tue, Mar 13, 2018 at 12:04:00AM +, mario buoninfante wrote:

  
Hi,


I ran few more tests on Linux trying to understand what's going on with
[midiout] and sysex messages.

I discovered that it's not just about sysex. I'm monitoring MIDI from Pd
with /KMidimon /and /GMIDImonitor/, and I noticed that also sending Note On
messages with [midiout] seems to be in some way different then sending the
same message using [noteout].

when Note On is sent using [midiout], this will spit single bytes that are
recognized as single byte sysex messages by the MIDI monitors!

has anyone ever experienced the same?


cheers,

Mario



  
  

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

  
  


  

___Pd-list@lists.iem.at mailing listUNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] sysex messages

2018-03-14 Thread mario buoninfante


Hi Miller,

yap I'm using ALSA.

btw, I had a look at the source code (I want to clarify I'm not a C 
programmer :) ) and from what I found in x_midi.c and s_midi.c, it kind 
of make sense that [midiout] returns 1 byte at time.


it seems to me we're missing a way to detect outgoing sysex messages 
(maybe having a dedicated object could help), so there's no way to 
collect a sysex and send it out in one go (ie having an array to 
return). I apologize for my trivial description of the "problem", but 
this is what I think is causing this behaviour.



cheers,

Mario


On 13/03/18 04:37, Miller Puckette wrote:

Hi Mario -

Perhaps you said this in the previous message which I missed... are you
using ALSA MIDI system or OSS?

MIDI support has always been a problem in Pd... largely because I don't have
a lot of experience with it.

cheers
Miller

On Tue, Mar 13, 2018 at 12:04:00AM +, mario buoninfante wrote:

Hi,


I ran few more tests on Linux trying to understand what's going on with
[midiout] and sysex messages.

I discovered that it's not just about sysex. I'm monitoring MIDI from Pd
with /KMidimon /and /GMIDImonitor/, and I noticed that also sending Note On
messages with [midiout] seems to be in some way different then sending the
same message using [noteout].

when Note On is sent using [midiout], this will spit single bytes that are
recognized as single byte sysex messages by the MIDI monitors!

has anyone ever experienced the same?


cheers,

Mario





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


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

Re: [PD] sysex messages

2018-03-12 Thread Miller Puckette

Hi Mario -

Perhaps you said this in the previous message which I missed... are you
using ALSA MIDI system or OSS?

MIDI support has always been a problem in Pd... largely because I don't have
a lot of experience with it.

cheers
Miller

On Tue, Mar 13, 2018 at 12:04:00AM +, mario buoninfante wrote:
> Hi,
> 
> 
> I ran few more tests on Linux trying to understand what's going on with
> [midiout] and sysex messages.
> 
> I discovered that it's not just about sysex. I'm monitoring MIDI from Pd
> with /KMidimon /and /GMIDImonitor/, and I noticed that also sending Note On
> messages with [midiout] seems to be in some way different then sending the
> same message using [noteout].
> 
> when Note On is sent using [midiout], this will spit single bytes that are
> recognized as single byte sysex messages by the MIDI monitors!
> 
> has anyone ever experienced the same?
> 
> 
> cheers,
> 
> Mario
> 
> 


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


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

[PD] sysex messages

2018-03-12 Thread mario buoninfante


Hi,


I ran few more tests on Linux trying to understand what's going on with 
[midiout] and sysex messages.


I discovered that it's not just about sysex. I'm monitoring MIDI from Pd 
with /KMidimon /and /GMIDImonitor/, and I noticed that also sending Note 
On messages with [midiout] seems to be in some way different then 
sending the same message using [noteout].


when Note On is sent using [midiout], this will spit single bytes that 
are recognized as single byte sysex messages by the MIDI monitors!


has anyone ever experienced the same?


cheers,

Mario


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

Re: [PD] sysex messages

2018-02-23 Thread Alex

yeah, so a lot of objects in pd except lists and then fan them out to the
inputs so you can do |list 1 2( -> [+ ] -> 3 but [midiout] has a 2nd input
to indicate the port number so doing that wouldn't map to what people are
used to in most contexts.

Really, an abstraction that works how you want it to is the way to go here.
[mario_sysex].
For instance, I almost always want midi CC to come as channel, cc number,
cc val but [ctlin] is the opposite, so I use an abstraction that changes
the order for me.
I'd say, make an abstraction, likely just copy mine and have it contain the
[midiout] instead of [outlet] and maybe take an argument for port number,
and then use and share that!

It is curious that your midi monitor groups a sysex message from one source
differently than from another, I can only speculate there but as long as
the bytes are interpreted properly it shouldn't matter :)

On Fri, Feb 23, 2018 at 6:03 AM, Mario Buoninfante <
mario.buoninfa...@gmail.com> wrote:

> Hi Marco,
>
> I just wanna point out that I haven't got issues with Pd, no problem at
> all. I can easily work with Sysex in various way and of course also the way
> you described. mine was more a let's call it curiosity. also because I
> think that the possibility to directly send a list to [midiout], and let Pd
> deal with parsing, would be a faster process.
>
> cheers,
> Mario
>
> 2018-02-22 22:40 GMT+00:00 mario buoninfante <mario.buoninfa...@gmail.com>
> :
>
>> yap I'm sending sysex from Circuit. I'm using Components a Novation
>> website that allows you to store patches and session from Circuit. and the
>> way that Circuit sends these info is why sysex. so I'm just dumping data
>> and monitoring.
>>
>> On 02/22/2018 10:37 PM, Alex wrote:
>>
>> Oh okay, I get it.
>> I'm not sure. Are you sending SYSEX from your Circuit as well?
>>
>> On Thu, Feb 22, 2018 at 2:31 PM, mario buoninfante <
>> mario.buoninfa...@gmail.com> wrote:
>>
>>> yap, this makes sense. I imagined Gmidimonitor does that. but why is not
>>> parsing midi from Pd?
>>>
>>> sorry, maybe I'm just missing the point, but I'm really trying to get my
>>> head around with that ;)
>>>
>>>
>>> cheers
>>>
>>>
>>>
>>> On 02/22/2018 10:29 PM, Christof Ressi wrote:
>>>
>>>> don't confuse MIDI messages with the individual bytes which make up the
>>>> message. Gmidimonitor parses the byte stream so it can tell you which
>>>> messages it gets. [midiout] is only responsible for sending raw *bytes* to
>>>> a MIDI device. it's your job to assemble your MIDI *messages*.
>>>>
>>>>
>>>> Gesendet: Donnerstag, 22. Februar 2018 um 23:05 Uhr
>>>> Von: "mario buoninfante" <mario.buoninfa...@gmail.com>
>>>> An: Alex <x37v.a...@gmail.com>
>>>> Cc: pd-list@lists.iem.at
>>>> Betreff: Re: [PD] sysex messages
>>>>
>>>> yap, I know that at the end of the day MIDI is dealing with 1 byte at
>>>> time. I was wondering why there's a difference between 2 different piece of
>>>> code that generates MIDI (Pd and Hardware synth).
>>>> for example I just monitored (via USB) my Novation Circuit (a
>>>> groovebox) and Gmidimonitor receives messages 81 bytes long. with Pd as I
>>>> said is always 1 byte.
>>>> now my question would be, how is this possible?
>>>> I'm sure Circuit sends sysex 81 bytes long, so I know that this is
>>>> correct, but still I don't know why Pd doesn't allow something like that.
>>>>   cheers,
>>>> Mario
>>>>   On 02/22/2018 09:58 PM, Alex wrote:
>>>>
>>>> MIDI is a serial protocol, individual bits running down a single line,
>>>> we now also have USB midi which is a little bit different than that but
>>>> usually that is abstracted for you.The software monitor you're using likely
>>>> groups these for you but in reality you simply have a stream of individual
>>>> bits on the hardware line..
>>>> PD's object let you do bytes at a time instead of individual bits :)
>>>>   On Thu, Feb 22, 2018 at 1:47 PM, mario buoninfante <
>>>> mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]> wrote:
>>>> Hi Alex,
>>>>   thanks for your reply. I think that also using your abstraction Pd
>>>> will spit out 1 byte per time (I didn't check it, but I assume that cause
>>>> it's not an external in C).
>>>> about MIDI if I'm not wrong, bytes are grouped in acc

Re: [PD] sysex messages

2018-02-23 Thread Christof Ressi

> I think that the possibility to directly send a list to [midiout],
 
I'd also like [midiout] to accept a list of numbers and serialize them 
automatically, similar to [send 0 1 2 3 4 ...( with [netsend].
but what should [midiout] parse? it just transmits bytes, the receiving device 
has to parse the message.
 

Gesendet: Freitag, 23. Februar 2018 um 15:03 Uhr
Von: "Mario Buoninfante" <mario.buoninfa...@gmail.com>
An: Alex <x37v.a...@gmail.com>
Cc: "Christof Ressi" <christof.re...@gmx.at>, pd-list <pd-l...@iem.at>
Betreff: Re: [PD] sysex messages

Hi Marco,
 I just wanna point out that I haven't got issues with Pd, no problem at all. I 
can easily work with Sysex in various way and of course also the way you 
described. mine was more a let's call it curiosity. also because I think that 
the possibility to directly send a list to [midiout], and let Pd deal with 
parsing, would be a faster process.
 cheers,Mario
 
2018-02-22 22:40 GMT+00:00 mario buoninfante 
<mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]>:
yap I'm sending sysex from Circuit. I'm using Components a Novation website 
that allows you to store patches and session from Circuit. and the way that 
Circuit sends these info is why sysex. so I'm just dumping data and monitoring.

 
On 02/22/2018 10:37 PM, Alex wrote:

Oh okay, I get it.I'm not sure. Are you sending SYSEX from your Circuit as well?
 
On Thu, Feb 22, 2018 at 2:31 PM, mario buoninfante 
<mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]> wrote:yap, 
this makes sense. I imagined Gmidimonitor does that. but why is not parsing 
midi from Pd?

sorry, maybe I'm just missing the point, but I'm really trying to get my head 
around with that ;)


cheers


On 02/22/2018 10:29 PM, Christof Ressi wrote:don't confuse MIDI messages with 
the individual bytes which make up the message. Gmidimonitor parses the byte 
stream so it can tell you which messages it gets. [midiout] is only responsible 
for sending raw *bytes* to a MIDI device. it's your job to assemble your MIDI 
*messages*.


Gesendet: Donnerstag, 22. Februar 2018 um 23:05 Uhr
Von: "mario buoninfante" 
<mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]>
An: Alex <x37v.a...@gmail.com[mailto:x37v.a...@gmail.com]>
Cc: pd-list@lists.iem.at[mailto:pd-list@lists.iem.at]
Betreff: Re: [PD] sysex messages

yap, I know that at the end of the day MIDI is dealing with 1 byte at time. I 
was wondering why there's a difference between 2 different piece of code that 
generates MIDI (Pd and Hardware synth).
for example I just monitored (via USB) my Novation Circuit (a groovebox) and 
Gmidimonitor receives messages 81 bytes long. with Pd as I said is always 1 
byte.
now my question would be, how is this possible?
I'm sure Circuit sends sysex 81 bytes long, so I know that this is correct, but 
still I don't know why Pd doesn't allow something like that.
  cheers,
Mario
  On 02/22/2018 09:58 PM, Alex wrote:

MIDI is a serial protocol, individual bits running down a single line, we now 
also have USB midi which is a little bit different than that but usually that 
is abstracted for you.The software monitor you're using likely groups these for 
you but in reality you simply have a stream of individual bits on the hardware 
line..
PD's object let you do bytes at a time instead of individual bits :)
  On Thu, Feb 22, 2018 at 1:47 PM, mario buoninfante 
<mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com][mailto:mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]]>
 wrote:
Hi Alex,
  thanks for your reply. I think that also using your abstraction Pd will spit 
out 1 byte per time (I didn't check it, but I assume that cause it's not an 
external in C).
about MIDI if I'm not wrong, bytes are grouped in accord with the type of 
message, ie Note on/off and CC are 3 bytes messages, channel pressure and 
program change are 2 bytes, sysex have variable length and so on. and I presume 
they're sent out in group.
in fact when I monitor MIDI messages coming for certain applications (I'm on 
Linux and I'm using Gmidimonitor) the console tells me the sysex size in bytes. 
so, with Pd the size is always 1 byte, but with other programming languages and 
softwares is variable and goes in accord with the sysex I generated.
  cheers,
Mario

 
On 02/22/2018 09:34 PM, Alex wrote:

I haven't tested in a while but I wrote an abstraction to take a list, wrap it 
in the sysex start and end and output it as individual bytes: 
https://github.com/x37v/pure_data[https://github.com/x37v/pure_data][https://github.com/x37v/pure_data%5Bhttps://github.com/x37v/pure_data%5D]
  midi is a byte oriented protocol..
  On Thu, Feb 22, 2018 at 1:24 PM, mario buoninfante 
<mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com][mailto:mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]]>
 wrote:Hi,


do you guys know if t

Re: [PD] sysex messages

2018-02-23 Thread Mario Buoninfante

Hi Marco,

I just wanna point out that I haven't got issues with Pd, no problem at
all. I can easily work with Sysex in various way and of course also the way
you described. mine was more a let's call it curiosity. also because I
think that the possibility to directly send a list to [midiout], and let Pd
deal with parsing, would be a faster process.

cheers,
Mario

2018-02-22 22:40 GMT+00:00 mario buoninfante <mario.buoninfa...@gmail.com>:

> yap I'm sending sysex from Circuit. I'm using Components a Novation
> website that allows you to store patches and session from Circuit. and the
> way that Circuit sends these info is why sysex. so I'm just dumping data
> and monitoring.
>
> On 02/22/2018 10:37 PM, Alex wrote:
>
> Oh okay, I get it.
> I'm not sure. Are you sending SYSEX from your Circuit as well?
>
> On Thu, Feb 22, 2018 at 2:31 PM, mario buoninfante <
> mario.buoninfa...@gmail.com> wrote:
>
>> yap, this makes sense. I imagined Gmidimonitor does that. but why is not
>> parsing midi from Pd?
>>
>> sorry, maybe I'm just missing the point, but I'm really trying to get my
>> head around with that ;)
>>
>>
>> cheers
>>
>>
>>
>> On 02/22/2018 10:29 PM, Christof Ressi wrote:
>>
>>> don't confuse MIDI messages with the individual bytes which make up the
>>> message. Gmidimonitor parses the byte stream so it can tell you which
>>> messages it gets. [midiout] is only responsible for sending raw *bytes* to
>>> a MIDI device. it's your job to assemble your MIDI *messages*.
>>>
>>>
>>> Gesendet: Donnerstag, 22. Februar 2018 um 23:05 Uhr
>>> Von: "mario buoninfante" <mario.buoninfa...@gmail.com>
>>> An: Alex <x37v.a...@gmail.com>
>>> Cc: pd-list@lists.iem.at
>>> Betreff: Re: [PD] sysex messages
>>>
>>> yap, I know that at the end of the day MIDI is dealing with 1 byte at
>>> time. I was wondering why there's a difference between 2 different piece of
>>> code that generates MIDI (Pd and Hardware synth).
>>> for example I just monitored (via USB) my Novation Circuit (a groovebox)
>>> and Gmidimonitor receives messages 81 bytes long. with Pd as I said is
>>> always 1 byte.
>>> now my question would be, how is this possible?
>>> I'm sure Circuit sends sysex 81 bytes long, so I know that this is
>>> correct, but still I don't know why Pd doesn't allow something like that.
>>>   cheers,
>>> Mario
>>>   On 02/22/2018 09:58 PM, Alex wrote:
>>>
>>> MIDI is a serial protocol, individual bits running down a single line,
>>> we now also have USB midi which is a little bit different than that but
>>> usually that is abstracted for you.The software monitor you're using likely
>>> groups these for you but in reality you simply have a stream of individual
>>> bits on the hardware line..
>>> PD's object let you do bytes at a time instead of individual bits :)
>>>   On Thu, Feb 22, 2018 at 1:47 PM, mario buoninfante <
>>> mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]> wrote:
>>> Hi Alex,
>>>   thanks for your reply. I think that also using your abstraction Pd
>>> will spit out 1 byte per time (I didn't check it, but I assume that cause
>>> it's not an external in C).
>>> about MIDI if I'm not wrong, bytes are grouped in accord with the type
>>> of message, ie Note on/off and CC are 3 bytes messages, channel pressure
>>> and program change are 2 bytes, sysex have variable length and so on. and I
>>> presume they're sent out in group.
>>> in fact when I monitor MIDI messages coming for certain applications
>>> (I'm on Linux and I'm using Gmidimonitor) the console tells me the sysex
>>> size in bytes. so, with Pd the size is always 1 byte, but with other
>>> programming languages and softwares is variable and goes in accord with the
>>> sysex I generated.
>>>   cheers,
>>> Mario
>>>
>>>
>>> On 02/22/2018 09:34 PM, Alex wrote:
>>>
>>> I haven't tested in a while but I wrote an abstraction to take a list,
>>> wrap it in the sysex start and end and output it as individual bytes:
>>> https://github.com/x37v/pure_data[https://github.com/x37v/pure_data]
>>>   midi is a byte oriented protocol..
>>>   On Thu, Feb 22, 2018 at 1:24 PM, mario buoninfante <
>>> mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]>
>>> wrote:Hi,
>>>
>>>
>>> do you guys know if there's a way

Re: [PD] sysex messages

2018-02-22 Thread Marco Hugo Schretter


hi mario,

for me the following works without issues from every point
to every point with sysex-to-midi-to-osc-to-midi-to-sysex
from every point in the line to every point with pd-vanilla
(bcf<->yamaha_dm2000<->osc<->hammerfall<->ableton)

parse your desired message in the other way round (so
that the end-msg is the first and start-msg ist last)
and use the right-to-left handling of the unpack object
for the output to the midiout in the right order:

example (volume-fader-ctl):
dm2000 sysex has 14 values
so when i talk to dm2000 i say



[1 69 1(<-- this example sets ch1-volume for hi+lo-bits
|
[247 $2 $3 0 0 $1 0 28 1 127 62 16 67 240(
|
unpack 0 0 0 0 0 0 0 0 0 0 0 0 0 0
|/
_
midiout

===

check the right order of sysex after unpack with print

liebe grüße
marco

Am 22.02.18 um 23:38 schrieb mario buoninfante:

the way I'm generating sysex in Pd is the following:

[list of bytes which starts with 240 and ends with 247(

|

|

[cyclone/iter 1]

|

|

[midiout 1]


On 02/22/2018 10:35 PM, Christof Ressi wrote:
are you sure you're correctly assembling your sysex messages in Pd? 
you could use [sysexin] to get the raw sysex messages from your 
Novation circuit, pass them straight to [midiout] and then have a look 
at Gmidimonitor.



Gesendet: Donnerstag, 22. Februar 2018 um 23:31 Uhr
Von: "mario buoninfante" <mario.buoninfa...@gmail.com>
An: "Christof Ressi" <christof.re...@gmx.at>, pd-list <pd-l...@iem.at>
Betreff: Re: Aw: Re: [PD] sysex messages

yap, this makes sense. I imagined Gmidimonitor does that. but why is not
parsing midi from Pd?

sorry, maybe I'm just missing the point, but I'm really trying to get my
head around with that ;)


cheers


On 02/22/2018 10:29 PM, Christof Ressi wrote:
don't confuse MIDI messages with the individual bytes which make up 
the message. Gmidimonitor parses the byte stream so it can tell you 
which messages it gets. [midiout] is only responsible for sending 
raw *bytes* to a MIDI device. it's your job to assemble your MIDI 
*messages*.



Gesendet: Donnerstag, 22. Februar 2018 um 23:05 Uhr
Von: "mario buoninfante" <mario.buoninfa...@gmail.com>
An: Alex <x37v.a...@gmail.com>
Cc: pd-list@lists.iem.at
Betreff: Re: [PD] sysex messages

yap, I know that at the end of the day MIDI is dealing with 1 byte 
at time. I was wondering why there's a difference between 2 
different piece of code that generates MIDI (Pd and Hardware synth).
for example I just monitored (via USB) my Novation Circuit (a 
groovebox) and Gmidimonitor receives messages 81 bytes long. with Pd 
as I said is always 1 byte.

now my question would be, how is this possible?
I'm sure Circuit sends sysex 81 bytes long, so I know that this is 
correct, but still I don't know why Pd doesn't allow something like 
that.

cheers,
Mario
On 02/22/2018 09:58 PM, Alex wrote:

MIDI is a serial protocol, individual bits running down a single 
line, we now also have USB midi which is a little bit different than 
that but usually that is abstracted for you.The software monitor 
you're using likely groups these for you but in reality you simply 
have a stream of individual bits on the hardware line..

PD's object let you do bytes at a time instead of individual bits :)
On Thu, Feb 22, 2018 at 1:47 PM, mario buoninfante 
<mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]> 
wrote:

Hi Alex,
thanks for your reply. I think that also using your abstraction Pd 
will spit out 1 byte per time (I didn't check it, but I assume that 
cause it's not an external in C).
about MIDI if I'm not wrong, bytes are grouped in accord with the 
type of message, ie Note on/off and CC are 3 bytes messages, channel 
pressure and program change are 2 bytes, sysex have variable length 
and so on. and I presume they're sent out in group.
in fact when I monitor MIDI messages coming for certain applications 
(I'm on Linux and I'm using Gmidimonitor) the console tells me the 
sysex size in bytes. so, with Pd the size is always 1 byte, but with 
other programming languages and softwares is variable and goes in 
accord with the sysex I generated.

cheers,
Mario


On 02/22/2018 09:34 PM, Alex wrote:

I haven't tested in a while but I wrote an abstraction to take a 
list, wrap it in the sysex start and end and output it as individual 
bytes: 
https://github.com/x37v/pure_data[https://github.com/x37v/pure_data]

   midi is a byte oriented protocol..
On Thu, Feb 22, 2018 at 1:24 PM, mario buoninfante 
<mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]> 
wrote:Hi,



do you guys know if there's a way to send a list of sysex messages 
(or 1 complete message, let's say 8 bytes long) rather then 1 byte 
per time?


if not, do you know if there's a particular reason why it's not 
possible?



cheers,

Mario


___
Pd-list@lists.iem.at[mailto:Pd-list@lists.iem.a

Re: [PD] sysex messages

2018-02-22 Thread mario buoninfante

yap I'm sending sysex from Circuit. I'm using Components a Novation 
website that allows you to store patches and session from Circuit. and 
the way that Circuit sends these info is why sysex. so I'm just dumping 
data and monitoring.



On 02/22/2018 10:37 PM, Alex wrote:

Oh okay, I get it.
I'm not sure. Are you sending SYSEX from your Circuit as well?

On Thu, Feb 22, 2018 at 2:31 PM, mario buoninfante 
<mario.buoninfa...@gmail.com <mailto:mario.buoninfa...@gmail.com>> wrote:


yap, this makes sense. I imagined Gmidimonitor does that. but why
is not parsing midi from Pd?

sorry, maybe I'm just missing the point, but I'm really trying to
get my head around with that ;)


cheers



On 02/22/2018 10:29 PM, Christof Ressi wrote:

don't confuse MIDI messages with the individual bytes which
make up the message. Gmidimonitor parses the byte stream so it
can tell you which messages it gets. [midiout] is only
responsible for sending raw *bytes* to a MIDI device. it's
your job to assemble your MIDI *messages*.


Gesendet: Donnerstag, 22. Februar 2018 um 23:05 Uhr
Von: "mario buoninfante" <mario.buoninfa...@gmail.com
<mailto:mario.buoninfa...@gmail.com>>
An: Alex <x37v.a...@gmail.com <mailto:x37v.a...@gmail.com>>
Cc: pd-list@lists.iem.at <mailto:pd-list@lists.iem.at>
Betreff: Re: [PD] sysex messages

yap, I know that at the end of the day MIDI is dealing with 1
byte at time. I was wondering why there's a difference between
2 different piece of code that generates MIDI (Pd and Hardware
synth).
for example I just monitored (via USB) my Novation Circuit (a
groovebox) and Gmidimonitor receives messages 81 bytes long.
with Pd as I said is always 1 byte.
now my question would be, how is this possible?
I'm sure Circuit sends sysex 81 bytes long, so I know that
this is correct, but still I don't know why Pd doesn't allow
something like that.
  cheers,
Mario
  On 02/22/2018 09:58 PM, Alex wrote:

MIDI is a serial protocol, individual bits running down a
single line, we now also have USB midi which is a little bit
different than that but usually that is abstracted for you.The
software monitor you're using likely groups these for you but
in reality you simply have a stream of individual bits on the
hardware line..
PD's object let you do bytes at a time instead of individual
bits :)
  On Thu, Feb 22, 2018 at 1:47 PM, mario buoninfante
<mario.buoninfa...@gmail.com
<mailto:mario.buoninfa...@gmail.com>[mailto:mario.buoninfa...@gmail.com
<mailto:mario.buoninfa...@gmail.com>]> wrote:
Hi Alex,
  thanks for your reply. I think that also using your
abstraction Pd will spit out 1 byte per time (I didn't check
it, but I assume that cause it's not an external in C).
about MIDI if I'm not wrong, bytes are grouped in accord with
the type of message, ie Note on/off and CC are 3 bytes
messages, channel pressure and program change are 2 bytes,
sysex have variable length and so on. and I presume they're
sent out in group.
in fact when I monitor MIDI messages coming for certain
applications (I'm on Linux and I'm using Gmidimonitor) the
console tells me the sysex size in bytes. so, with Pd the size
is always 1 byte, but with other programming languages and
softwares is variable and goes in accord with the sysex I
generated.
  cheers,
Mario


On 02/22/2018 09:34 PM, Alex wrote:

I haven't tested in a while but I wrote an abstraction to take
a list, wrap it in the sysex start and end and output it as
individual bytes:
https://github.com/x37v/pure_data[https://github.com/x37v/pure_data]

<https://github.com/x37v/pure_data%5Bhttps://github.com/x37v/pure_data%5D>
  midi is a byte oriented protocol..
  On Thu, Feb 22, 2018 at 1:24 PM, mario buoninfante
<mario.buoninfa...@gmail.com
<mailto:mario.buoninfa...@gmail.com>[mailto:mario.buoninfa...@gmail.com
<mailto:mario.buoninfa...@gmail.com>]> wrote:Hi,


do you guys know if there's a way to send a list of sysex
messages (or 1 complete message, let's say 8 bytes long)
rather then 1 byte per time?

if not, do you know if there's a particular reason why it's
not possible?


cheers,

Mario


___
Pd-list@lists.iem.at
<mailto:Pd-list@lists.iem.at>[mailto:Pd-list@lists.iem.at
<mailto:Pd-list@lists.iem.at>] mailing list
UNSUBSCRIBE a

Re: [PD] sysex messages

2018-02-22 Thread mario buoninfante

the way I'm generating sysex in Pd is the following:

[list of bytes which starts with 240 and ends with 247(

[cyclone/iter 1]

[midiout 1]

On 02/22/2018 10:35 PM, Christof Ressi wrote:

are you sure you're correctly assembling your sysex messages in Pd? you could
use [sysexin] to get the raw sysex messages from your Novation circuit, pass
them straight to [midiout] and then have a look at Gmidimonitor.

Gesendet: Donnerstag, 22. Februar 2018 um 23:31 Uhr
Von: "mario buoninfante" <mario.buoninfa...@gmail.com>
An: "Christof Ressi" <christof.re...@gmx.at>, pd-list <pd-l...@iem.at>
Betreff: Re: Aw: Re: [PD] sysex messages

yap, this makes sense. I imagined Gmidimonitor does that. but why is not
parsing midi from Pd?

sorry, maybe I'm just missing the point, but I'm really trying to get my
head around with that ;)

cheers

On 02/22/2018 10:29 PM, Christof Ressi wrote:

don't confuse MIDI messages with the individual bytes which make up the
message. Gmidimonitor parses the byte stream so it can tell you which messages
it gets. [midiout] is only responsible for sending raw *bytes* to a MIDI
device. it's your job to assemble your MIDI *messages*.

Gesendet: Donnerstag, 22. Februar 2018 um 23:05 Uhr
Von: "mario buoninfante" <mario.buoninfa...@gmail.com>
An: Alex <x37v.a...@gmail.com>
Cc: pd-list@lists.iem.at
Betreff: Re: [PD] sysex messages

yap, I know that at the end of the day MIDI is dealing with 1 byte at time. I
was wondering why there's a difference between 2 different piece of code that
generates MIDI (Pd and Hardware synth).
for example I just monitored (via USB) my Novation Circuit (a groovebox) and
Gmidimonitor receives messages 81 bytes long. with Pd as I said is always 1
byte.
now my question would be, how is this possible?
I'm sure Circuit sends sysex 81 bytes long, so I know that this is correct, but
still I don't know why Pd doesn't allow something like that.

cheers,

Mario

On 02/22/2018 09:58 PM, Alex wrote:

On Thu, Feb 22, 2018 at 1:47 PM, mario buoninfante <mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]> wrote:

Hi Alex,

thanks for your reply. I think that also using your abstraction Pd will spit out 1 byte per time (I didn't check it, but I assume that cause it's not an external in C).

about MIDI if I'm not wrong, bytes are grouped in accord with the type of
message, ie Note on/off and CC are 3 bytes messages, channel pressure and
program change are 2 bytes, sysex have variable length and so on. and I presume
they're sent out in group.
in fact when I monitor MIDI messages coming for certain applications (I'm on
Linux and I'm using Gmidimonitor) the console tells me the sysex size in bytes.
so, with Pd the size is always 1 byte, but with other programming languages and
softwares is variable and goes in accord with the sysex I generated.

cheers,

Mario

On 02/22/2018 09:34 PM, Alex wrote:

On Thu, Feb 22, 2018 at 1:24 PM, mario buoninfante <mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]> wrote:Hi,

do you guys know if there's a way to send a list of sysex messages (or 1
complete message, let's say 8 bytes long) rather then 1 byte per time?

if not, do you know if there's a particular reason why it's not possible?

cheers,

Mario

___
Pd-list@lists.iem.at[mailto:Pd-list@lists.iem.at] mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list[https://lists.puredata.info/listinfo/pd-list]
___ Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list[https://lists.puredata.info/listinfo/pd-list]

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

Re: [PD] sysex messages

2018-02-22 Thread Alex

Oh okay, I get it.
I'm not sure. Are you sending SYSEX from your Circuit as well?

On Thu, Feb 22, 2018 at 2:31 PM, mario buoninfante <
mario.buoninfa...@gmail.com> wrote:

> yap, this makes sense. I imagined Gmidimonitor does that. but why is not
> parsing midi from Pd?
>
> sorry, maybe I'm just missing the point, but I'm really trying to get my
> head around with that ;)
>
>
> cheers
>
>
>
> On 02/22/2018 10:29 PM, Christof Ressi wrote:
>
>> don't confuse MIDI messages with the individual bytes which make up the
>> message. Gmidimonitor parses the byte stream so it can tell you which
>> messages it gets. [midiout] is only responsible for sending raw *bytes* to
>> a MIDI device. it's your job to assemble your MIDI *messages*.
>>
>>
>> Gesendet: Donnerstag, 22. Februar 2018 um 23:05 Uhr
>> Von: "mario buoninfante" <mario.buoninfa...@gmail.com>
>> An: Alex <x37v.a...@gmail.com>
>> Cc: pd-list@lists.iem.at
>> Betreff: Re: [PD] sysex messages
>>
>> yap, I know that at the end of the day MIDI is dealing with 1 byte at
>> time. I was wondering why there's a difference between 2 different piece of
>> code that generates MIDI (Pd and Hardware synth).
>> for example I just monitored (via USB) my Novation Circuit (a groovebox)
>> and Gmidimonitor receives messages 81 bytes long. with Pd as I said is
>> always 1 byte.
>> now my question would be, how is this possible?
>> I'm sure Circuit sends sysex 81 bytes long, so I know that this is
>> correct, but still I don't know why Pd doesn't allow something like that.
>>   cheers,
>> Mario
>>   On 02/22/2018 09:58 PM, Alex wrote:
>>
>> MIDI is a serial protocol, individual bits running down a single line, we
>> now also have USB midi which is a little bit different than that but
>> usually that is abstracted for you.The software monitor you're using likely
>> groups these for you but in reality you simply have a stream of individual
>> bits on the hardware line..
>> PD's object let you do bytes at a time instead of individual bits :)
>>   On Thu, Feb 22, 2018 at 1:47 PM, mario buoninfante <
>> mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]> wrote:
>> Hi Alex,
>>   thanks for your reply. I think that also using your abstraction Pd will
>> spit out 1 byte per time (I didn't check it, but I assume that cause it's
>> not an external in C).
>> about MIDI if I'm not wrong, bytes are grouped in accord with the type of
>> message, ie Note on/off and CC are 3 bytes messages, channel pressure and
>> program change are 2 bytes, sysex have variable length and so on. and I
>> presume they're sent out in group.
>> in fact when I monitor MIDI messages coming for certain applications (I'm
>> on Linux and I'm using Gmidimonitor) the console tells me the sysex size in
>> bytes. so, with Pd the size is always 1 byte, but with other programming
>> languages and softwares is variable and goes in accord with the sysex I
>> generated.
>>   cheers,
>> Mario
>>
>>
>> On 02/22/2018 09:34 PM, Alex wrote:
>>
>> I haven't tested in a while but I wrote an abstraction to take a list,
>> wrap it in the sysex start and end and output it as individual bytes:
>> https://github.com/x37v/pure_data[https://github.com/x37v/pure_data]
>>   midi is a byte oriented protocol..
>>   On Thu, Feb 22, 2018 at 1:24 PM, mario buoninfante <
>> mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]>
>> wrote:Hi,
>>
>>
>> do you guys know if there's a way to send a list of sysex messages (or 1
>> complete message, let's say 8 bytes long) rather then 1 byte per time?
>>
>> if not, do you know if there's a particular reason why it's not possible?
>>
>>
>> cheers,
>>
>> Mario
>>
>>
>> ___
>> Pd-list@lists.iem.at[mailto:Pd-list@lists.iem.at] mailing list
>> UNSUBSCRIBE and account-management -> https://lists.puredata.info/li
>> stinfo/pd-list[https://lists.puredata.info/listinfo/pd-list]
>> ___ Pd-list@lists.iem.at
>> mailing list UNSUBSCRIBE and account-management ->
>> https://lists.puredata.info/listinfo/pd-list[https://lists.
>> puredata.info/listinfo/pd-list]
>>
>
>
> ___
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> https://lists.puredata.info/li
> stinfo/pd-list
>
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] sysex messages

2018-02-22 Thread mario buoninfante

yes I'm sure, and I also monitored my Circuit on Mac with Midi Monitor,
everything is fine. then I'm sure that [sysexin] will spit out 1 byte at
time.

On 02/22/2018 10:35 PM, Christof Ressi wrote:

yap, this makes sense. I imagined Gmidimonitor does that. but why is not
parsing midi from Pd?

sorry, maybe I'm just missing the point, but I'm really trying to get my
head around with that ;)

cheers

On 02/22/2018 10:29 PM, Christof Ressi wrote:

Gesendet: Donnerstag, 22. Februar 2018 um 23:05 Uhr
Von: "mario buoninfante" <mario.buoninfa...@gmail.com>
An: Alex <x37v.a...@gmail.com>
Cc: pd-list@lists.iem.at
Betreff: Re: [PD] sysex messages

cheers,

Mario

On 02/22/2018 09:58 PM, Alex wrote:

On Thu, Feb 22, 2018 at 1:47 PM, mario buoninfante <mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]> wrote:

Hi Alex,

thanks for your reply. I think that also using your abstraction Pd will spit out 1 byte per time (I didn't check it, but I assume that cause it's not an external in C).

cheers,

Mario

On 02/22/2018 09:34 PM, Alex wrote:

On Thu, Feb 22, 2018 at 1:24 PM, mario buoninfante <mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]> wrote:Hi,

do you guys know if there's a way to send a list of sysex messages (or 1
complete message, let's say 8 bytes long) rather then 1 byte per time?

if not, do you know if there's a particular reason why it's not possible?

cheers,

Mario

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

Re: [PD] sysex messages

2018-02-22 Thread mario buoninfante

funny thing I created a new patch with only a numberbox connected to 
[midiout 1], every value I typed will generate a sysex msg??


I don't entirely understand that


On 02/22/2018 10:29 PM, Christof Ressi wrote:

don't confuse MIDI messages with the individual bytes which make up the 
message. Gmidimonitor parses the byte stream so it can tell you which messages 
it gets. [midiout] is only responsible for sending raw *bytes* to a MIDI 
device. it's your job to assemble your MIDI *messages*.


Gesendet: Donnerstag, 22. Februar 2018 um 23:05 Uhr
Von: "mario buoninfante" <mario.buoninfa...@gmail.com>
An: Alex <x37v.a...@gmail.com>
Cc: pd-list@lists.iem.at
Betreff: Re: [PD] sysex messages

yap, I know that at the end of the day MIDI is dealing with 1 byte at time. I 
was wondering why there's a difference between 2 different piece of code that 
generates MIDI (Pd and Hardware synth).
for example I just monitored (via USB) my Novation Circuit (a groovebox) and 
Gmidimonitor receives messages 81 bytes long. with Pd as I said is always 1 
byte.
now my question would be, how is this possible?
I'm sure Circuit sends sysex 81 bytes long, so I know that this is correct, but 
still I don't know why Pd doesn't allow something like that.
  
cheers,

Mario
  
On 02/22/2018 09:58 PM, Alex wrote:


MIDI is a serial protocol, individual bits running down a single line, we now 
also have USB midi which is a little bit different than that but usually that 
is abstracted for you.The software monitor you're using likely groups these for 
you but in reality you simply have a stream of individual bits on the hardware 
line..
PD's object let you do bytes at a time instead of individual bits :)
  
On Thu, Feb 22, 2018 at 1:47 PM, mario buoninfante <mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]> wrote:

Hi Alex,
  
thanks for your reply. I think that also using your abstraction Pd will spit out 1 byte per time (I didn't check it, but I assume that cause it's not an external in C).

about MIDI if I'm not wrong, bytes are grouped in accord with the type of 
message, ie Note on/off and CC are 3 bytes messages, channel pressure and 
program change are 2 bytes, sysex have variable length and so on. and I presume 
they're sent out in group.
in fact when I monitor MIDI messages coming for certain applications (I'm on 
Linux and I'm using Gmidimonitor) the console tells me the sysex size in bytes. 
so, with Pd the size is always 1 byte, but with other programming languages and 
softwares is variable and goes in accord with the sysex I generated.
  
cheers,

Mario

  


On 02/22/2018 09:34 PM, Alex wrote:

I haven't tested in a while but I wrote an abstraction to take a list, wrap it 
in the sysex start and end and output it as individual bytes: 
https://github.com/x37v/pure_data[https://github.com/x37v/pure_data]
  midi is a byte oriented protocol..
  
On Thu, Feb 22, 2018 at 1:24 PM, mario buoninfante <mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]> wrote:Hi,



do you guys know if there's a way to send a list of sysex messages (or 1 
complete message, let's say 8 bytes long) rather then 1 byte per time?

if not, do you know if there's a particular reason why it's not possible?


cheers,

Mario


___
Pd-list@lists.iem.at[mailto:Pd-list@lists.iem.at] mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list[https://lists.puredata.info/listinfo/pd-list]
___ Pd-list@lists.iem.at mailing list 
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list[https://lists.puredata.info/listinfo/pd-list]



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

Re: [PD] sysex messages

2018-02-22 Thread Christof Ressi

are you sure you're correctly assembling your sysex messages in Pd? you could 
use [sysexin] to get the raw sysex messages from your Novation circuit, pass 
them straight to [midiout] and then have a look at Gmidimonitor.

> Gesendet: Donnerstag, 22. Februar 2018 um 23:31 Uhr
> Von: "mario buoninfante" <mario.buoninfa...@gmail.com>
> An: "Christof Ressi" <christof.re...@gmx.at>, pd-list <pd-l...@iem.at>
> Betreff: Re: Aw: Re: [PD] sysex messages
>
> yap, this makes sense. I imagined Gmidimonitor does that. but why is not 
> parsing midi from Pd?
> 
> sorry, maybe I'm just missing the point, but I'm really trying to get my 
> head around with that ;)
> 
> 
> cheers
> 
> 
> On 02/22/2018 10:29 PM, Christof Ressi wrote:
> > don't confuse MIDI messages with the individual bytes which make up the 
> > message. Gmidimonitor parses the byte stream so it can tell you which 
> > messages it gets. [midiout] is only responsible for sending raw *bytes* to 
> > a MIDI device. it's your job to assemble your MIDI *messages*.
> >
> >
> > Gesendet: Donnerstag, 22. Februar 2018 um 23:05 Uhr
> > Von: "mario buoninfante" <mario.buoninfa...@gmail.com>
> > An: Alex <x37v.a...@gmail.com>
> > Cc: pd-list@lists.iem.at
> > Betreff: Re: [PD] sysex messages
> >
> > yap, I know that at the end of the day MIDI is dealing with 1 byte at time. 
> > I was wondering why there's a difference between 2 different piece of code 
> > that generates MIDI (Pd and Hardware synth).
> > for example I just monitored (via USB) my Novation Circuit (a groovebox) 
> > and Gmidimonitor receives messages 81 bytes long. with Pd as I said is 
> > always 1 byte.
> > now my question would be, how is this possible?
> > I'm sure Circuit sends sysex 81 bytes long, so I know that this is correct, 
> > but still I don't know why Pd doesn't allow something like that.
> >   
> > cheers,
> > Mario
> >   
> > On 02/22/2018 09:58 PM, Alex wrote:
> >
> > MIDI is a serial protocol, individual bits running down a single line, we 
> > now also have USB midi which is a little bit different than that but 
> > usually that is abstracted for you.The software monitor you're using likely 
> > groups these for you but in reality you simply have a stream of individual 
> > bits on the hardware line..
> > PD's object let you do bytes at a time instead of individual bits :)
> >   
> > On Thu, Feb 22, 2018 at 1:47 PM, mario buoninfante 
> > <mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]> wrote:
> > Hi Alex,
> >   
> > thanks for your reply. I think that also using your abstraction Pd will 
> > spit out 1 byte per time (I didn't check it, but I assume that cause it's 
> > not an external in C).
> > about MIDI if I'm not wrong, bytes are grouped in accord with the type of 
> > message, ie Note on/off and CC are 3 bytes messages, channel pressure and 
> > program change are 2 bytes, sysex have variable length and so on. and I 
> > presume they're sent out in group.
> > in fact when I monitor MIDI messages coming for certain applications (I'm 
> > on Linux and I'm using Gmidimonitor) the console tells me the sysex size in 
> > bytes. so, with Pd the size is always 1 byte, but with other programming 
> > languages and softwares is variable and goes in accord with the sysex I 
> > generated.
> >   
> > cheers,
> > Mario
> >
> >   
> >
> > On 02/22/2018 09:34 PM, Alex wrote:
> >
> > I haven't tested in a while but I wrote an abstraction to take a list, wrap 
> > it in the sysex start and end and output it as individual bytes: 
> > https://github.com/x37v/pure_data[https://github.com/x37v/pure_data]
> >   midi is a byte oriented protocol..
> >   
> > On Thu, Feb 22, 2018 at 1:24 PM, mario buoninfante 
> > <mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]> wrote:Hi,
> >
> >
> > do you guys know if there's a way to send a list of sysex messages (or 1 
> > complete message, let's say 8 bytes long) rather then 1 byte per time?
> >
> > if not, do you know if there's a particular reason why it's not possible?
> >
> >
> > cheers,
> >
> > Mario
> >
> >
> > ___
> > Pd-list@lists.iem.at[mailto:Pd-list@lists.iem.at] mailing list
> > UNSUBSCRIBE and account-management -> 
> > https://lists.puredata.info/listinfo/pd-list[https://lists.puredata.info/listinfo/pd-list]
> > ___ Pd-list@lists.iem.at 
> > mailing list UNSUBSCRIBE and account-management -> 
> > https://lists.puredata.info/listinfo/pd-list[https://lists.puredata.info/listinfo/pd-list]
> 
>

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

Re: [PD] sysex messages

2018-02-22 Thread mario buoninfante

yap, this makes sense. I imagined Gmidimonitor does that. but why is not
parsing midi from Pd?

sorry, maybe I'm just missing the point, but I'm really trying to get my
head around with that ;)

cheers

On 02/22/2018 10:29 PM, Christof Ressi wrote:

Gesendet: Donnerstag, 22. Februar 2018 um 23:05 Uhr
Von: "mario buoninfante" <mario.buoninfa...@gmail.com>
An: Alex <x37v.a...@gmail.com>
Cc: pd-list@lists.iem.at
Betreff: Re: [PD] sysex messages

cheers,

Mario

On 02/22/2018 09:58 PM, Alex wrote:

On Thu, Feb 22, 2018 at 1:47 PM, mario buoninfante <mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]> wrote:

Hi Alex,

thanks for your reply. I think that also using your abstraction Pd will spit out 1 byte per time (I didn't check it, but I assume that cause it's not an external in C).

cheers,

Mario

On 02/22/2018 09:34 PM, Alex wrote:

On Thu, Feb 22, 2018 at 1:24 PM, mario buoninfante <mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]> wrote:Hi,

do you guys know if there's a way to send a list of sysex messages (or 1
complete message, let's say 8 bytes long) rather then 1 byte per time?

if not, do you know if there's a particular reason why it's not possible?

cheers,

Mario

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

Re: [PD] sysex messages

2018-02-22 Thread Christof Ressi

Gesendet: Donnerstag, 22. Februar 2018 um 23:05 Uhr
Von: "mario buoninfante" <mario.buoninfa...@gmail.com>
An: Alex <x37v.a...@gmail.com>
Cc: pd-list@lists.iem.at
Betreff: Re: [PD] sysex messages

MIDI is a serial protocol, individual bits running down a single line, we now
also have USB midi which is a little bit different than that but usually that
is abstracted for you.The software monitor you're using likely groups these for
you but in reality you simply have a stream of individual bits on the hardware
line..
PD's object let you do bytes at a time instead of individual bits :)
On Thu, Feb 22, 2018 at 1:47 PM, mario buoninfante
<mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]> wrote:
Hi Alex,
thanks for your reply. I think that also using your abstraction Pd will spit
out 1 byte per time (I didn't check it, but I assume that cause it's not an
external in C).
about MIDI if I'm not wrong, bytes are grouped in accord with the type of
message, ie Note on/off and CC are 3 bytes messages, channel pressure and
program change are 2 bytes, sysex have variable length and so on. and I presume
they're sent out in group.
in fact when I monitor MIDI messages coming for certain applications (I'm on
Linux and I'm using Gmidimonitor) the console tells me the sysex size in bytes.
so, with Pd the size is always 1 byte, but with other programming languages and
softwares is variable and goes in accord with the sysex I generated.
cheers,
Mario

On 02/22/2018 09:34 PM, Alex wrote:

I haven't tested in a while but I wrote an abstraction to take a list, wrap it
in the sysex start and end and output it as individual bytes:
https://github.com/x37v/pure_data[https://github.com/x37v/pure_data]
midi is a byte oriented protocol..
On Thu, Feb 22, 2018 at 1:24 PM, mario buoninfante
<mario.buoninfa...@gmail.com[mailto:mario.buoninfa...@gmail.com]> wrote:Hi,

do you guys know if there's a way to send a list of sysex messages (or 1
complete message, let's say 8 bytes long) rather then 1 byte per time?

if not, do you know if there's a particular reason why it's not possible?

cheers,

Mario

___
Pd-list@lists.iem.at[mailto:Pd-list@lists.iem.at] mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list[https://lists.puredata.info/listinfo/pd-list]
___ Pd-list@lists.iem.at mailing
list UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list[https://lists.puredata.info/listinfo/pd-list]

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

Re: [PD] sysex messages

2018-02-22 Thread mario buoninfante


Hi Ryan,


Circuit is sending MIDI via USB, while I'm routing Pd via Jack on Linux.


cheers


On 02/22/2018 10:25 PM, Ryan Smith wrote:

Are you using the hardware midi ports on the Circuit or all through
USB? The USB midi specs are slightly different when it comes to sysex
messages if I recall and maybe the Circuit is using that style while
Pd doesn't so the interface just sees the messages as bytes instead of
grouping it.

On Thu, Feb 22, 2018 at 2:05 PM, mario buoninfante
 wrote:

yap, I know that at the end of the day MIDI is dealing with 1 byte at time.
I was wondering why there's a difference between 2 different piece of code
that generates MIDI (Pd and Hardware synth).

for example I just monitored (via USB) my Novation Circuit (a groovebox) and
Gmidimonitor receives messages 81 bytes long. with Pd as I said is always 1
byte.

now my question would be, how is this possible?

I'm sure Circuit sends sysex 81 bytes long, so I know that this is correct,
but still I don't know why Pd doesn't allow something like that.


cheers,

Mario


On 02/22/2018 09:58 PM, Alex wrote:

MIDI is a serial protocol, individual bits running down a single line, we
now also have USB midi which is a little bit different than that but usually
that is abstracted for you.
The software monitor you're using likely groups these for you but in reality
you simply have a stream of individual bits on the hardware line..
PD's object let you do bytes at a time instead of individual bits :)

On Thu, Feb 22, 2018 at 1:47 PM, mario buoninfante
 wrote:

Hi Alex,


thanks for your reply. I think that also using your abstraction Pd will
spit out 1 byte per time (I didn't check it, but I assume that cause it's
not an external in C).

about MIDI if I'm not wrong, bytes are grouped in accord with the type of
message, ie Note on/off and CC are 3 bytes messages, channel pressure and
program change are 2 bytes, sysex have variable length and so on. and I
presume they're sent out in group.

in fact when I monitor MIDI messages coming for certain applications (I'm
on Linux and I'm using Gmidimonitor) the console tells me the sysex size in
bytes. so, with Pd the size is always 1 byte, but with other programming
languages and softwares is variable and goes in accord with the sysex I
generated.


cheers,

Mario


On 02/22/2018 09:34 PM, Alex wrote:

I haven't tested in a while but I wrote an abstraction to take a list,
wrap it in the sysex start and end and output it as individual bytes:
https://github.com/x37v/pure_data

midi is a byte oriented protocol..

On Thu, Feb 22, 2018 at 1:24 PM, mario buoninfante
 wrote:

Hi,


do you guys know if there's a way to send a list of sysex messages (or 1
complete message, let's say 8 bytes long) rather then 1 byte per time?

if not, do you know if there's a particular reason why it's not possible?


cheers,

Mario


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






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




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

Re: [PD] sysex messages

2018-02-22 Thread Ryan Smith

Are you using the hardware midi ports on the Circuit or all through
USB? The USB midi specs are slightly different when it comes to sysex
messages if I recall and maybe the Circuit is using that style while
Pd doesn't so the interface just sees the messages as bytes instead of
grouping it.

On Thu, Feb 22, 2018 at 2:05 PM, mario buoninfante
 wrote:
> yap, I know that at the end of the day MIDI is dealing with 1 byte at time.
> I was wondering why there's a difference between 2 different piece of code
> that generates MIDI (Pd and Hardware synth).
>
> for example I just monitored (via USB) my Novation Circuit (a groovebox) and
> Gmidimonitor receives messages 81 bytes long. with Pd as I said is always 1
> byte.
>
> now my question would be, how is this possible?
>
> I'm sure Circuit sends sysex 81 bytes long, so I know that this is correct,
> but still I don't know why Pd doesn't allow something like that.
>
>
> cheers,
>
> Mario
>
>
> On 02/22/2018 09:58 PM, Alex wrote:
>
> MIDI is a serial protocol, individual bits running down a single line, we
> now also have USB midi which is a little bit different than that but usually
> that is abstracted for you.
> The software monitor you're using likely groups these for you but in reality
> you simply have a stream of individual bits on the hardware line..
> PD's object let you do bytes at a time instead of individual bits :)
>
> On Thu, Feb 22, 2018 at 1:47 PM, mario buoninfante
>  wrote:
>>
>> Hi Alex,
>>
>>
>> thanks for your reply. I think that also using your abstraction Pd will
>> spit out 1 byte per time (I didn't check it, but I assume that cause it's
>> not an external in C).
>>
>> about MIDI if I'm not wrong, bytes are grouped in accord with the type of
>> message, ie Note on/off and CC are 3 bytes messages, channel pressure and
>> program change are 2 bytes, sysex have variable length and so on. and I
>> presume they're sent out in group.
>>
>> in fact when I monitor MIDI messages coming for certain applications (I'm
>> on Linux and I'm using Gmidimonitor) the console tells me the sysex size in
>> bytes. so, with Pd the size is always 1 byte, but with other programming
>> languages and softwares is variable and goes in accord with the sysex I
>> generated.
>>
>>
>> cheers,
>>
>> Mario
>>
>>
>> On 02/22/2018 09:34 PM, Alex wrote:
>>
>> I haven't tested in a while but I wrote an abstraction to take a list,
>> wrap it in the sysex start and end and output it as individual bytes:
>> https://github.com/x37v/pure_data
>>
>> midi is a byte oriented protocol..
>>
>> On Thu, Feb 22, 2018 at 1:24 PM, mario buoninfante
>>  wrote:
>>>
>>> Hi,
>>>
>>>
>>> do you guys know if there's a way to send a list of sysex messages (or 1
>>> complete message, let's say 8 bytes long) rather then 1 byte per time?
>>>
>>> if not, do you know if there's a particular reason why it's not possible?
>>>
>>>
>>> cheers,
>>>
>>> Mario
>>>
>>>
>>> ___
>>> Pd-list@lists.iem.at mailing list
>>> UNSUBSCRIBE and account-management ->
>>> https://lists.puredata.info/listinfo/pd-list
>>
>>
>>
>
>
>
> ___
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management ->
> https://lists.puredata.info/listinfo/pd-list
>

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

Re: [PD] sysex messages

2018-02-22 Thread mario buoninfante

yap, I know that at the end of the day MIDI is dealing with 1 byte at 
time. I was wondering why there's a difference between 2 different piece 
of code that generates MIDI (Pd and Hardware synth).

for example I just monitored (via USB) my Novation Circuit (a groovebox) 
and Gmidimonitor receives messages 81 bytes long. with Pd as I said is 
always 1 byte.

now my question would be, how is this possible?

I'm sure Circuit sends sysex 81 bytes long, so I know that this is 
correct, but still I don't know why Pd doesn't allow something like that.

cheers,

Mario

On 02/22/2018 09:58 PM, Alex wrote:
MIDI is a serial protocol, individual bits running down a single line, 
we now also have USB midi which is a little bit different than that 
but usually that is abstracted for you.
The software monitor you're using likely groups these for you but in 
reality you simply have a stream of individual bits on the hardware 
line..

PD's object let you do bytes at a time instead of individual bits :)

On Thu, Feb 22, 2018 at 1:47 PM, mario buoninfante 
> wrote:

Hi Alex,

thanks for your reply. I think that also using your abstraction Pd
will spit out 1 byte per time (I didn't check it, but I assume
that cause it's not an external in C).

about MIDI if I'm not wrong, bytes are grouped in accord with the
type of message, ie Note on/off and CC are 3 bytes messages,
channel pressure and program change are 2 bytes, sysex have
variable length and so on. and I presume they're sent out in group.

in fact when I monitor MIDI messages coming for certain
applications (I'm on Linux and I'm using Gmidimonitor) the console
tells me the sysex size in bytes. so, with Pd the size is always 1
byte, but with other programming languages and softwares is
variable and goes in accord with the sysex I generated.

cheers,

Mario

On 02/22/2018 09:34 PM, Alex wrote:

I haven't tested in a while but I wrote an abstraction to take a
list, wrap it in the sysex start and end and output it as
individual bytes: https://github.com/x37v/pure_data

midi is a byte oriented protocol..

On Thu, Feb 22, 2018 at 1:24 PM, mario buoninfante
> wrote:

Hi,

do you guys know if there's a way to send a list of sysex
messages (or 1 complete message, let's say 8 bytes long)
rather then 1 byte per time?

if not, do you know if there's a particular reason why it's
not possible?

cheers,

Mario

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

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

Re: [PD] sysex messages

2018-02-22 Thread Alex

MIDI is a serial protocol, individual bits running down a single line, we
now also have USB midi which is a little bit different than that but
usually that is abstracted for you.
The software monitor you're using likely groups these for you but in
reality you simply have a stream of individual bits on the hardware line..
PD's object let you do bytes at a time instead of individual bits :)

On Thu, Feb 22, 2018 at 1:47 PM, mario buoninfante <
mario.buoninfa...@gmail.com> wrote:

> Hi Alex,
>
>
> thanks for your reply. I think that also using your abstraction Pd will
> spit out 1 byte per time (I didn't check it, but I assume that cause it's
> not an external in C).
>
> about MIDI if I'm not wrong, bytes are grouped in accord with the type of
> message, ie Note on/off and CC are 3 bytes messages, channel pressure and
> program change are 2 bytes, sysex have variable length and so on. and I
> presume they're sent out in group.
>
> in fact when I monitor MIDI messages coming for certain applications (I'm
> on Linux and I'm using Gmidimonitor) the console tells me the sysex size in
> bytes. so, with Pd the size is always 1 byte, but with other programming
> languages and softwares is variable and goes in accord with the sysex I
> generated.
>
>
> cheers,
>
> Mario
>
>
> On 02/22/2018 09:34 PM, Alex wrote:
>
> I haven't tested in a while but I wrote an abstraction to take a list,
> wrap it in the sysex start and end and output it as individual bytes:
> https://github.com/x37v/pure_data
>
> midi is a byte oriented protocol..
>
> On Thu, Feb 22, 2018 at 1:24 PM, mario buoninfante <
> mario.buoninfa...@gmail.com> wrote:
>
>> Hi,
>>
>>
>> do you guys know if there's a way to send a list of sysex messages (or 1
>> complete message, let's say 8 bytes long) rather then 1 byte per time?
>>
>> if not, do you know if there's a particular reason why it's not possible?
>>
>>
>> cheers,
>>
>> Mario
>>
>>
>> ___
>> Pd-list@lists.iem.at mailing list
>> UNSUBSCRIBE and account-management -> https://lists.puredata.info/li
>> stinfo/pd-list
>>
>
>
>
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] sysex messages

2018-02-22 Thread mario buoninfante


Hi Alex,


thanks for your reply. I think that also using your abstraction Pd will 
spit out 1 byte per time (I didn't check it, but I assume that cause 
it's not an external in C).


about MIDI if I'm not wrong, bytes are grouped in accord with the type 
of message, ie Note on/off and CC are 3 bytes messages, channel pressure 
and program change are 2 bytes, sysex have variable length and so on. 
and I presume they're sent out in group.


in fact when I monitor MIDI messages coming for certain applications 
(I'm on Linux and I'm using Gmidimonitor) the console tells me the sysex 
size in bytes. so, with Pd the size is always 1 byte, but with other 
programming languages and softwares is variable and goes in accord with 
the sysex I generated.



cheers,

Mario


On 02/22/2018 09:34 PM, Alex wrote:
I haven't tested in a while but I wrote an abstraction to take a list, 
wrap it in the sysex start and end and output it as individual bytes: 
https://github.com/x37v/pure_data


midi is a byte oriented protocol..

On Thu, Feb 22, 2018 at 1:24 PM, mario buoninfante 
> wrote:


Hi,


do you guys know if there's a way to send a list of sysex messages
(or 1 complete message, let's say 8 bytes long) rather then 1 byte
per time?

if not, do you know if there's a particular reason why it's not
possible?


cheers,

Mario


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





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

Re: [PD] sysex messages

2018-02-22 Thread Alex

I haven't tested in a while but I wrote an abstraction to take a list, wrap
it in the sysex start and end and output it as individual bytes:
https://github.com/x37v/pure_data

midi is a byte oriented protocol..

On Thu, Feb 22, 2018 at 1:24 PM, mario buoninfante <
mario.buoninfa...@gmail.com> wrote:

> Hi,
>
>
> do you guys know if there's a way to send a list of sysex messages (or 1
> complete message, let's say 8 bytes long) rather then 1 byte per time?
>
> if not, do you know if there's a particular reason why it's not possible?
>
>
> cheers,
>
> Mario
>
>
> ___
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> https://lists.puredata.info/li
> stinfo/pd-list
>
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

[PD] sysex messages

2018-02-22 Thread mario buoninfante


Hi,


do you guys know if there's a way to send a list of sysex messages (or 1 
complete message, let's say 8 bytes long) rather then 1 byte per time?


if not, do you know if there's a particular reason why it's not possible?


cheers,

Mario


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

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

[PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

Re: [PD] sysex messages

[PD] sysex messages

34 matches

Site Navigation

Mail list logo

Footer information