Announcement
Collapse
No announcement yet.
Midi thru?
Collapse
This topic has been answered.
X
X
-
I hit the same snag myself, glad to hear it solved it for you as well! -
There is a known potential bug on 2.2.9
Please check the following setting in the settings.tml file found on your micro sd card:
midithrumodetype=“1"
This value is likely 0, once set to 1 save the file. MIDI Thru should now work.
- Selected Answer
Leave a comment:
-
Same problem here? My whole set is dependend on midi out?? Im on 2.2.9.
Anybody?Leave a comment:
-
This explains so much. I ended up re soldering a bunch of cables because I figured it was something on my end. I was sure it worked before and then I couldn’t get it to work for love nor money.
Glad it’s on the radar.Leave a comment:
-
MIDI appears to be broken on 2.2.7 - nothing is passed through and it also spews out MIDI clock. Reported to 1010 a few weeks ago but no response.
https://forum.1010music.com/forum/pr...-clock-out-bug👍 1Leave a comment:
-
MIDI appears to be broken on 2.2.7 - nothing is passed through and it also spews out MIDI clock. Reported to 1010 a few weeks ago but no response.
Hi 1010, I've just updated from 2.2.3 to 2.2.7 and the micro now continuously sends MIDI clock. It stops sending after recording a multisample (New Multi) but starts again after a powering up/restarting. I see that there are other MIDI issues with 2.2.7 so could you please add this to your fix list. Thanks! GrumLeave a comment:
-
Midi thru?
I can't tell if I've just gone mad or something isn't set up correctly. Previously I used to have my Beatstep Pro -> Bitbox Micro -> Rample -> mmMidi. This worked great and I was able to trigger everything from the Beatstep pro. Now it seems the note information gets lost? mmMidi still picks up the clock and start/stop messages. However, it doesn't register any note information coming from the Beatstep pro.
Did I reset a setting somewhere?
Firmware 2.2.7.Tags: None
Leave a comment: