Re: Issue receiving sysex dump from DX7
"Florian Heer" <[email protected]> Sun, 17 Nov 2019 21:19:04 +0100
| Newsgroups | gmane.music.equipment.yamaha-dx |
|---|---|
| Message-ID | <[email protected]> |
--SCD5YdbsgjM0Kx4k9QjX
Content-Type: multipart/alternative;
boundary="------------78D6292CA403C46E159B5289"
Content-Language: en-US
--------------78D6292CA403C46E159B5289
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Hi Florian (it's like talking to myself, just better),
On 17/11/2019 20:28, Florian Anwander wrote:
> 1.) no-name USB-MIDI have only one feature: they increase the income
> of some chinese factory manager. They don't provide the feature to
> transfer MIDI (at least they reach the end of their abilities with
> sysex). So: put it to the dumpster.
Yeah, well... most of the time that one does its job, quite some
programming work with a YS200 showed no issues (when relayed through the
MOTU), also sending and receiving full dumps to/from an M1 worked out.
Also I already have filled their pockets, as long as there is no
pressing need, I won't fill the garbage can with it . Anyway, that's why
I used the FCA1616 in parallel to test. And also the cheap cable uses
class drivers, and the Behringer has its own, different drivers.
> 2.) what software do you use? for receiving / analysing / sending the
> sysex data?
Usually / mainly something I have written myself using the WebMidiApi in
Chrome. Also DX Manager 5 - I installed that to verify my suspicions, no
experience with that, except that I successfully tested if it could talk
to my TX7 - and also MIDI-Ox, SoundDiver and "MIDI Sysex file transfer
utility". But except for the first, I'm no expert in any of these. I
only know that with the cheap USB cable, I can't send bigger sysex with
MIDI-Ox (that's why I installed the "MIDI Sysex file transfer utility").
I would usually believe that my own code would be the best source of
truth for me, as I know what happens there. But then again, I don't know
if the web midi api might already filter out stuff that it doesn't
understand, and also of course I don't know if the Windows drivers might
hide 'dirty' data.
I have not tried using Linux or a Mac yet - if there is a realistic
chance that Windows is to blame, I'll give it shot.
Cheers, Florian
--------------78D6292CA403C46E159B5289
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-text-flowed" style="font-family: -moz-fixed;
font-size: 14px;" lang="x-unicode">Hi Florian (it's like talking
to myself, just better),
<br>
<br>
On 17/11/2019 20:28, Florian Anwander wrote:
<br>
<blockquote type="cite" style="color: #000000;">1.) no-name
USB-MIDI have only one feature: they increase the income of some
chinese factory manager. They don't provide the feature to
transfer MIDI (at least they reach the end of their abilities
with sysex). So: put it to the dumpster.
<br>
</blockquote>
<br>
Yeah, well... most of the time that one does its job, quite some
programming work with a YS200 showed no issues (when relayed
through the MOTU), also sending and receiving full dumps to/from
an M1 worked out. Also I already have filled their pockets, as
long as there is no pressing need, I won't fill the garbage can
with it <span class="moz-smiley-s1" title=":-)"></span>. Anyway,
that's why I used the FCA1616 in parallel to test. And also the
cheap cable uses class drivers, and the Behringer has its own,
different drivers.
<br>
<br>
<blockquote type="cite" style="color: #000000;">2.) what software
do you use? for receiving / analysing / sending the sysex data?
<br>
</blockquote>
<br>
Usually / mainly something I have written myself using the
WebMidiApi in Chrome. Also DX Manager 5 - I installed that to
verify my suspicions, no experience with that, except that I
successfully tested if it could talk to my TX7 - and also MIDI-Ox,
SoundDiver and "MIDI Sysex file transfer utility". But except for
the first, I'm no expert in any of these. I only know that with
the cheap USB cable, I can't send bigger sysex with MIDI-Ox
(that's why I installed the "MIDI Sysex file transfer utility").
<br>
<br>
I would usually believe that my own code would be the best source
of truth for me, as I know what happens there. But then again, I
don't know if the web midi api might already filter out stuff that
it doesn't understand, and also of course I don't know if the
Windows drivers might hide 'dirty' data.
<br>
<br>
I have not tried using Linux or a Mac yet - if there is a
realistic chance that Windows is to blame, I'll give it shot.
<br>
<br>
Cheers, Florian
<br>
<br>
</div>
</body>
</html>
--------------78D6292CA403C46E159B5289--
--SCD5YdbsgjM0Kx4k9QjX
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#20427): https://groups.io/g/YamahaDX/message/20427
Mute This Topic: https://groups.io/mt/59988412/2509863
Group Owner: [email protected]
Unsubscribe: https://groups.io/g/YamahaDX/unsub [[email protected]]
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
--SCD5YdbsgjM0Kx4k9QjX--