If everything is wired correctly and all your device settings are correct (MIDI Thru is on etc), then clicking on the Send Sysex button will get you this:
Before changing any parameters, I tested the MIDI Thru Check, and it worked — but Nixie 2 still didn’t connect.
Then, I applied all the suggested settings and performed the troubleshooting steps. The MIDI Thru Check worked again, and all MIDI messages like clock, preset changes, etc., are being sent and received correctly.
However, Nixie 2 still doesn’t recognize the Timeline , no matter what I try.
I’ve double-checked, and the Strymon Timeline and BigSky MX are configured correctly according to the official MIDI guide.
I couldn’t find any documentation indicating that the Quad Cortex blocks or limits large SysEx messages , but just to be safe, I ran all of James’s tests both with and without the QC in the chain — and in both scenarios, the MIDI Thru Check worked perfectly .
Still, Nixie 2 doesn’t detect the Timeline at all, even though everything else (preset changes, clock messages, etc.) is working fine.
At this point, I’m wondering if there’s something specific about how Nixie handles SysEx communication that might be causing the issue.
If Windows, there is this thing where if a software (like the morningstar editor) is connect to the MIDI port, then other softwares cannot access that same MIDI port. Try closing the browser for the editor (and other MIDI software) and see if you can get that to work.
The Timeline appears in Nixie2 when the MIDI cables are connected between the MC6 PRO and Timeline. In this instance, the MC6 PRO is just acting as a USB MIDI interface between Nixie2 and the Timeline.
Is your Timeline firmware updated? Here’s what I’m using:
