tte mailto:m...@ucsd.edu>>
To: mario buoninfante <mailto:mario.buoninfa...@gmail.com>>
Cc: Simon Iten <mailto:itensi...@gmail.com>>, pd list <mailto:pd-l...@iem.at>>
Subject: Re: [PD] sysex messages
Message-ID: <20180314222113.GL7620@elroy.localdomain
<mailto:20180314222
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:
>>>>>
>
<mailto:pd-list-requ...@lists.iem.at> wrote:
From: Miller Puckette mailto:m...@ucsd.edu>>
To: mario buoninfante <mailto:mario.buoninfa...@gmail.com>>
Cc: Simon Iten mailto:itensi...@gmail.com>>,
pd list mailto:pd-l...@iem.at>>
Subject: Re: [PD] sysex messages
Message
at
>>> <mailto:pd-list-requ...@lists.iem.at> wrote:
>>>
>>> From: Miller Puckette mailto:m...@ucsd.edu>>
>>> To: mario buoninfante >> <mailto:mario.buoninfa...@gmail.com>>
>>> Cc: Simon Iten mailto:itensi...@gm
...@gmail.com>>
Cc: Simon Iten mailto:itensi...@gmail.com>>, pd
list 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
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 mailto:m...@ucsd.edu>>
> To: mario buoninfante <mailto:mario.buoninfa...@gmail.com>>
> Cc: Simon Iten mailto:itensi...@gmail.com>&g
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
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,
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
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 do
> 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 pas
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 ALS
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
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
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 w
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
>&g
to parse the message.
Gesendet: Freitag, 23. Februar 2018 um 15:03 Uhr
Von: "Mario Buoninfante"
An: Alex
Cc: "Christof Ressi" , pd-list
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 easi
ich
>>> 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 b
n] 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"
An: "Christof Ressi" , pd-list
Betreff: Re: Aw: Re: [PD] sysex mess
te" mailto:mario.buoninfa...@gmail.com>>
An: Alex 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
ysexin] 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"
An: "Christof Ressi" , pd-list
Betreff: Re: Aw: Re: [PD] s
gt;> 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 20
se [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"
An: "Christof Ressi" , pd-list
Betreff: Re: Aw: Re: [
e"
An: Alex
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
Von: "mario buoninfante"
> An: "Christof Ressi" , pd-list
> 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,
018 um 23:05 Uhr
Von: "mario buoninfante"
An: Alex
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 (
Gesendet: Donnerstag, 22. Februar 2018 um 23:05 Uhr
Von: "mario buoninfante"
An: Alex
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 dif
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 a
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,
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
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
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 by
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
33 matches
Mail list logo
