<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>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.<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 02/22/2018 10:37 PM, Alex wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAOGs2RBTX_6J0Gw+kqOd-LX7dGL7BE5t14t-6eLvCMpepE6V+Q@mail.gmail.com">
      <div dir="ltr">
        <div>Oh okay, I get it.<br>
        </div>
        I'm not sure. Are you sending SYSEX from your Circuit as well?<br>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Thu, Feb 22, 2018 at 2:31 PM, mario
          buoninfante <span dir="ltr"><<a
              href="mailto:mario.buoninfante@gmail.com" target="_blank"
              moz-do-not-send="true">mario.buoninfante@gmail.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">yap, this
            makes sense. I imagined Gmidimonitor does that. but why is
            not parsing midi from Pd?<br>
            <br>
            sorry, maybe I'm just missing the point, but I'm really
            trying to get my head around with that ;)<br>
            <br>
            <br>
            cheers
            <div class="HOEnZb">
              <div class="h5"><br>
                <br>
                <br>
                On 02/22/2018 10:29 PM, Christof Ressi wrote:<br>
                <blockquote class="gmail_quote" style="margin:0 0 0
                  .8ex;border-left:1px #ccc solid;padding-left:1ex">
                  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*.<br>
                  <br>
                  <br>
                  Gesendet: Donnerstag, 22. Februar 2018 um 23:05 Uhr<br>
                  Von: "mario buoninfante" <<a
                    href="mailto:mario.buoninfante@gmail.com"
                    target="_blank" moz-do-not-send="true">mario.buoninfante@gmail.com</a>><br>
                  An: Alex <<a href="mailto:x37v.alex@gmail.com"
                    target="_blank" moz-do-not-send="true">x37v.alex@gmail.com</a>><br>
                  Cc: <a href="mailto:pd-list@lists.iem.at"
                    target="_blank" moz-do-not-send="true">pd-list@lists.iem.at</a><br>
                  Betreff: Re: [PD] sysex messages<br>
                  <br>
                  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).<br>
                  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.<br>
                  now my question would be, how is this possible?<br>
                  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.<br>
                    cheers,<br>
                  Mario<br>
                    On 02/22/2018 09:58 PM, Alex wrote:<br>
                  <br>
                  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..<br>
                  PD's object let you do bytes at a time instead of
                  individual bits :)<br>
                    On Thu, Feb 22, 2018 at 1:47 PM, mario buoninfante
                  <<a href="mailto:mario.buoninfante@gmail.com"
                    target="_blank" moz-do-not-send="true">mario.buoninfante@gmail.com</a>[m<wbr>ailto:<a
                    href="mailto:mario.buoninfante@gmail.com"
                    target="_blank" moz-do-not-send="true">mario.buoninfante@gmail.<wbr>com</a>]>
                  wrote:<br>
                  Hi Alex,<br>
                    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).<br>
                  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.<br>
                  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.<br>
                    cheers,<br>
                  Mario<br>
                  <br>
                    <br>
                  On 02/22/2018 09:34 PM, Alex wrote:<br>
                  <br>
                  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: <a
href="https://github.com/x37v/pure_data%5Bhttps://github.com/x37v/pure_data%5D"
                    rel="noreferrer" target="_blank"
                    moz-do-not-send="true">https://github.com/x37v/pure_d<wbr>ata[https://github.com/x37v/pu<wbr>re_data]</a><br>
                    midi is a byte oriented protocol..<br>
                    On Thu, Feb 22, 2018 at 1:24 PM, mario buoninfante
                  <<a href="mailto:mario.buoninfante@gmail.com"
                    target="_blank" moz-do-not-send="true">mario.buoninfante@gmail.com</a>[m<wbr>ailto:<a
                    href="mailto:mario.buoninfante@gmail.com"
                    target="_blank" moz-do-not-send="true">mario.buoninfante@gmail.<wbr>com</a>]>
                  wrote:Hi,<br>
                  <br>
                  <br>
                  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?<br>
                  <br>
                  if not, do you know if there's a particular reason why
                  it's not possible?<br>
                  <br>
                  <br>
                  cheers,<br>
                  <br>
                  Mario<br>
                  <br>
                  <br>
                  ______________________________<wbr>_________________<br>
                  <a href="mailto:Pd-list@lists.iem.at" target="_blank"
                    moz-do-not-send="true">Pd-list@lists.iem.at</a>[mailto:<a
                    href="mailto:Pd-list@lists.iem.at" target="_blank"
                    moz-do-not-send="true">Pd<wbr>-list@lists.iem.at</a>]
                  mailing list<br>
                  UNSUBSCRIBE and account-management -> <a
href="https://lists.puredata.info/listinfo/pd-list%5Bhttps://lists.puredata.info/listinfo/pd-list%5D"
                    rel="noreferrer" target="_blank"
                    moz-do-not-send="true">https://lists.puredata.info/li<wbr>stinfo/pd-list[https://lists.<wbr>puredata.info/listinfo/pd-<wbr>list]</a><br>
                  ______________________________<wbr>_________________ <a
                    href="mailto:Pd-list@lists.iem.at" target="_blank"
                    moz-do-not-send="true">Pd-list@lists.iem.at</a>
                  mailing list UNSUBSCRIBE and account-management ->
                  <a
href="https://lists.puredata.info/listinfo/pd-list%5Bhttps://lists.puredata.info/listinfo/pd-list%5D"
                    rel="noreferrer" target="_blank"
                    moz-do-not-send="true">https://lists.puredata.info/li<wbr>stinfo/pd-list[https://lists.<wbr>puredata.info/listinfo/pd-<wbr>list]</a><br>
                </blockquote>
                <br>
                <br>
                ______________________________<wbr>_________________<br>
                <a href="mailto:Pd-list@lists.iem.at" target="_blank"
                  moz-do-not-send="true">Pd-list@lists.iem.at</a>
                mailing list<br>
                UNSUBSCRIBE and account-management -> <a
                  href="https://lists.puredata.info/listinfo/pd-list"
                  rel="noreferrer" target="_blank"
                  moz-do-not-send="true">https://lists.puredata.info/li<wbr>stinfo/pd-list</a><br>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>