Hi!
I'm working on 'custom' footswitch to control my whole DIY rig. I stuck on MIDI part which I will use to control G-Major. I write whole program in C. Could anyone tell me how sending part should look (commands and order)? I mean:
1. Note on/off
2. CC
3. channel
or something different?
Thanks in advance for help!
This is a pretty good explanation of the format of MIDI messages:
https://www.songstuff.com/recording/article/midi_message_format/
The basics are that you send one status byte, followed by either one or two data bytes (depending on the message).
There are a couple of exceptions: (1) the MIDI "system realtime" messages are a single byte and can appear anywhere, and (2) "running status" can be used to reduce the number of bytes sent when sending large numbers of notes (basically, if the status byte you're about to send is the same as the last one you sent, you don't have to bother. The receiving device will assume the status).
hope that helps,
Tom
Thanks for help!
It helps a lot but I can't control G-Major thru midi still. "MIDI-IN" is blinking when I push the button but "learn" mode don't catch anything. Commands should be bin, hex or dec values?
Are you sending Program Changes (PC) or Control Changes (CC) ? G-Major's "Learn" mode only reacts to Control Change values. Check the manual, page 22:
https://toneprints.com/media/666860/tcelectronic-gmajor-sw-1-27-_manual-english.pdf
To send a program change, it's enough to send just 0xCn 0xPP where c is the channel number and PP is the program to switch to.
The G-Major has a cool thing where you can configure it to send the tuner data back to the pedal (through a second cable). Then during a gig you don't have to look at the rack, just press Tune on your pedal and look at the pedal. A couple of years ago I reverse engineered the protocol, it's SysEx messages as follows:
F0 00 20 1F 00 48 70 NN XX F7
Where NN is the note: C=0, C#=1, etc. and XX is the tuning, from 10 - 17 - 1F.
(1)7 is "in tune", lower and higher tells how much out of tune. 0 is most flat and f is most sharp: 0 1 2 3 4 5 6 7 8 9 a b c d e f
For that you'll have to build a MIDI-in on your pedal, though.
Quote from: swisher on November 25, 2019, 02:35:45 PM
Commands should be bin, hex or dec values?
MIDI is mostly quoted in hex (like pruttelherrie just did) but it doesn't really mae any odds, since they're all the same thing really. What MIDI *sends* and what is *received* is "a byte", but whether that byte is to be interpreted in binary, hex or decimal really depends on what's convenient for the context.
So what's the context? What are you using to send bytes to this G-Major, and do you know that it sends MIDI data correctly?
I struggled for ages with MIDI send until I got a MIDI monitor application on my computer so I could see what I was sending. It turned out it wasn't at all what I thought I was sending. I'd got some setting wrong in the UART used for sending MIDI bytes, and things were getting scrambled. Once I fixed that, everything sprang to life.
Thanks a lot! :icon_eek:
Finally I have some reactions in G-major but I think there is a problem with soft uart. When I send CC code (0xB1, 0x08, 0x7F) I get address=11, CC=55 and "MOD (055)" with first press and "MOD (056)" with next press (it's toggling - 055/056). If I use PC code (0xC1, 0x08) G-major doesn't receive MIDI signal.
EDIT:
I run footswitch code thru Proteus and in terminal I reiceive 0xFD, 0xF5, 0xFB instead of 0xB1, 0x08, 0x7F
Is your midi transmission inverted by any chance?
Quote from: anotherjim on November 27, 2019, 01:37:24 PM
Is your midi transmission inverted by any chance?
That was my first thought too.
Sounds like you're nearly there though - keep fiddling with it and you'll get it. And as soon as you've done it once, you've got known-good code you can use for the future.
I cleaned up my code a little and there is a progress. I can send simple values but there is always "3" before any number. When I'm sending "1" or "0x01" I get in terminal "31", if it's "127" I get "31 32 37". There is a mistake somewhere in code but I can't find it. Anyway, thanks a loooot for help!
30 hex is ASCII code for 0
https://www.ascii-code.com/
On the other side, I have never been able to simulate in Proteus correctly so that I can see in the terminal the MIDI data transferred....
What I did some time ago to be able to debug midi in Proteus, was creating a virtual serial port in the PC connected to Proteus serial output, and then use a serial-to-midi software (like Hariless midi-serial bridge) and a MIDI virtual cable.....
I know this sounds complex, but once it's configured, you can use MIDOX or similar to monitor
I'm testing uart with lower speed (9600) - I can't set 31250 baud in Proteus.
potul: Maybe I'll try this ;)
Quote from: Digital Larry on November 28, 2019, 12:53:03 AM
30 hex is ASCII code for 0
https://www.ascii-code.com/
I think Larry is on to something:
Quote from: swisher on November 27, 2019, 06:14:18 PM
I can send simple values but there is always "3" before any number. (snip) if it's "127" I get "31 32 37".
It looks like you're not sending a byte with value 127, but the 3 characters that make up "127".
Can you post the snippet of code where you actually send values to the serial port?
Quote from: pruttelherrie on November 29, 2019, 06:09:17 PM
It looks like you're not sending a byte with value 127, but the 3 characters that make up "127".
Yeah, well spotted! 31, 32, 37 makes sense like that. The compiler is treating it like a string not a byte.
Right, that's what i found in ASCII table.
Two functions for sending:
C file:
void suart_puts( char * str ) {
while( *str ) sputchar( *str++ );
}
void suart_putint( int val ) {
char buf[9];
itoa( val, buf, 10 );
suart_puts( buf );
}
H file:
void sputchar( char zn );
void suart_puts( char * str );
void suart_putint( int val );
I've got assembler file also (soft uart). I don't understand anything from assembler so I didn't change anything.
Ok, instead of suart_putint(value); use sputchar(value); and make sure value is a byte, not an int. (Note: 'char' is also a byte!)
sputchar(192);
sputchar(6);
(for example) should be a Program Change to 6.
Of course, sputchar(0xC0); sputchar(0x06); should be the same.
Damn... it works! :icon_surprised: Thanks a lot! Now I can test it with G-major ::)
Quote from: swisher on November 28, 2019, 12:01:16 PM
I'm testing uart with lower speed (9600) - I can't set 31250 baud in Proteus.
potul: Maybe I'll try this ;)
Yep,.. I faced this issue as well. That's one of the reasons I used serial-to-MIDI conversion.
Glad to see you have it working now.
on the other hand, what kind of microcontroller are you using for the project?
For footswitch controller I'm using Atmega328. I didn't know anything about MIDI so I didn't know it works through UART. If I will know it I will use Atmega164 probably.
There are some MIDI libraries ready to use for Arduino. You could easily use them in your Atmega328