Re: Issue receiving sysex dump from DX7

--bI5HHT2QUyeJtxvLCS9z
Content-Type: multipart/alternative; boundary="000000000000db364305979fa4e8"

--000000000000db364305979fa4e8
Content-Type: text/plain; charset="UTF-8"

I was just playing around with an SPX-updated DX7Mk1 in my studio. The 0xb0
appears to come  keypresses as I trigger the bulk dump from the interface.
The dump itself looks normal on my box, though.

The flickering light, btw, is just the active sensing and is totally
(annoying, but) normal on Yamaha keyboards.

Jb

AllTheRest <[email protected]> schrieb am Mo., 18. Nov. 2019, 00:38:

> Hi Jeremy,
>
> On 17/11/2019 21:11, Jeremy Bernstein via Groups.Io wrote:
> > 0xF2 could be Song Position Pointer, but clearly that data is looking a
> little odd. Is your DX7 E!-upgraded or similar? I wonder if it's sending
> some (corrupt) sequencer-related info.
>
> No, it's absolutely vanilla, no expansion boards, all chips are
> original. So the Song Pointer doesn't make any sense. The superfluous F2
> is only in a part of the sysex, in other places it's B0 and other dirt
> as well, nothing that makes sense here.
>
> Cheers, Florian
>
>
>

--000000000000db364305979fa4e8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">I was just playing around with an SPX-updated DX7Mk1 in m=
y studio. The 0xb0 appears to come=C2=A0 keypresses as I trigger the bulk d=
ump from the interface. The dump itself looks normal on my box, though.<div=
 dir=3D"auto"><br></div><div dir=3D"auto">The flickering light, btw, is jus=
t the active sensing and is totally (annoying, but) normal on Yamaha keyboa=
rds.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Jb</div></div><br><=
div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">AllTheRest =
&lt;<a href=3D"mailto:[email protected]">[email protected]</a>&=
gt; schrieb am Mo., 18. Nov. 2019, 00:38:<br></div><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">Hi Jeremy,<br>
<br>
On 17/11/2019 21:11, Jeremy Bernstein via Groups.Io wrote:<br>
&gt; 0xF2 could be Song Position Pointer, but clearly that data is looking =
a little odd. Is your DX7 E!-upgraded or similar? I wonder if it&#39;s send=
ing some (corrupt) sequencer-related info.<br>
<br>
No, it&#39;s absolutely vanilla, no expansion boards, all chips are <br>
original. So the Song Pointer doesn&#39;t make any sense. The superfluous F=
2 <br>
is only in a part of the sysex, in other places it&#39;s B0 and other dirt =
<br>
as well, nothing that makes sense here.<br>
<br>
Cheers, Florian<br>
<br>
<br>
</blockquote></div>

--000000000000db364305979fa4e8--

--bI5HHT2QUyeJtxvLCS9z
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 (#20431): https://groups.io/g/YamahaDX/message/20431
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-

--bI5HHT2QUyeJtxvLCS9z--