-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Magic key" during Inquiry #4
Comments
"What exactly happened when you tried to send SYSEX messages before the "activate MIDI" message?"I got stuck :-)fun...The device hangs and has to be resetted.As i remember a simple power off/ power on got it running again.If it had bricked my THR iwould have ceased experimenting for sure.Interesting approach with the CRC of the symbol table, will try this.Perhaps there is a way to read out the table before activating, but i do not know.The Yamaha software does not read the table at all, as i know.
-------- Ursprüngliche Nachricht --------Von: MDJRosenau ***@***.***> Datum: 10.03.24 20:29 (GMT+01:00) An: martinzw/THRII-direct-USB-pedalboard ***@***.***> Cc: martinzw ***@***.***>, Assign ***@***.***> Betreff: [martinzw/THRII-direct-USB-pedalboard] "Magic key" during Inquiry (Issue #4)
Hello Martin
I'm interested in the protocol because the Yamaha app does not run on the operating system I am using.
I have a question about the "magic key" in the "activate MIDI" message:
In the Windows app, there are three binary files which are obviously symbol tables of different firmware versions.
I found out that the CRC-32 values of three of these files are identical to three of the "magic keys" listed in your PDF.
For this reason, I think that the "activate MIDI" message is actually there to ensure that the app uses the correct symbol table if it does not read this table from the device.
If this is the case, the "magic key " of future firmware versions could be calculated by calculating the CRC-32 of the symbol table.
MY QUESTION:
... this would require reading the symbol table before sending the "activate MIDI" message.
In your PDF you write: "Do not send any commands to the THRII before successful MIDI activation- or you get stuck!"
What exactly happened when you tried to send SYSEX messages before the "activate MIDI" message?
Did you brick your amplifier or did you just have to do a power-on/off reset to get the amplifier working again?
I don't like to try reading out the symbol table before sending the "activate MIDI" message if I know that sending SYSEX messages before the "activate MIDI" message bricks the device...
Thanks for your Answer
Martin
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were assigned.Message ID: ***@***.***>
|
I just tested with my THR-10-II, firmware 1.44.0a: |
Great news! That solves the riddle about the "Magic key".Thanks a lot.
-------- Ursprüngliche Nachricht --------Von: MDJRosenau ***@***.***> Datum: 11.03.24 21:35 (GMT+01:00) An: martinzw/THRII-direct-USB-pedalboard ***@***.***> Cc: martinzw ***@***.***>, Assign ***@***.***> Betreff: Re: [martinzw/THRII-direct-USB-pedalboard] "Magic key" during Inquiry (Issue #4)
I just tested with my THR-10-II, firmware 1.44.0a:
Reading the symbol table works before sending the "activate MIDI" message.
... and the CRC-32 of the symbol table matches the key.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were assigned.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello Martin
I'm interested in the protocol because the Yamaha app does not run on the operating system I am using.
I have a question about the "magic key" in the "activate MIDI" message:
In the Windows app, there are three binary files which are obviously symbol tables of different firmware versions.
I found out that the CRC-32 values of three of these files are identical to three of the "magic keys" listed in your PDF.
For this reason, I think that the "activate MIDI" message is actually there to ensure that the app uses the correct symbol table if it does not read this table from the device.
If this is the case, the "magic key " of future firmware versions could be calculated by calculating the CRC-32 of the symbol table.
MY QUESTION:
... this would require reading the symbol table before sending the "activate MIDI" message.
In your PDF you write: "Do not send any commands to the THRII before successful MIDI activation- or you get stuck!"
What exactly happened when you tried to send SYSEX messages before the "activate MIDI" message?
Did you brick your amplifier or did you just have to do a power-on/off reset to get the amplifier working again?
I don't like to try reading out the symbol table before sending the "activate MIDI" message if I know that sending SYSEX messages before the "activate MIDI" message bricks the device...
Thanks for your Answer
Martin
The text was updated successfully, but these errors were encountered: