Re: [PD] sysex messages

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>> >>>>&

Re: [PD] sysex messages

ensi...@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 con

Re: [PD] sysex messages

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.buoninf

Re: [PD] sysex messages

<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 &l

Re: [PD] sysex messages

t; > 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.localdo

Re: [PD] sysex messages

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

Re: [PD] sysex messages

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,

Re: [PD] sysex messages

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

Re: [PD] sysex messages

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

Re: [PD] sysex messages

> 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

Re: [PD] sysex messages

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

Re: [PD] sysex messages

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

Re: [PD] sysex messages

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

Re: [PD] 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

[PD] sysex messages

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

Re: [PD] sysex messages

s 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" &

Re: [PD] sysex messages

rse 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 mes

Re: [PD] sysex messages

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 buoninfante&

Re: [PD] sysex messages

I *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 wi

Re: [PD] sysex messages

" <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 kn

Re: [PD] sysex messages

.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/

Re: [PD] sysex messages

on: "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 wo

Re: [PD] sysex messages

.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/

Re: [PD] sysex messages

ario.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

Re: [PD] sysex messages

"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

Re: [PD] sysex messages

: "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 d

Re: [PD] sysex messages

: 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

Re: [PD] sysex messages

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

Re: [PD] sysex messages

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

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

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

Re: [PD] sysex messages

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

Re: [PD] sysex messages

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>

[PD] sysex messages

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 ___