i did not want to mark any of this as a BUG yet, because it could be user error.
I understand what these mean at face value, but they do not perform as expected in use.
Tracker+ OUT connected to Synth IN via MIDI Jack Tracker+ set to: Clock out and Transport out over both USB + MIDI (been this way since my OG tracker and have never had an issue) Synth: Clock In set to Midi In Jack; Transport in set to OFF; pads locked
Hit play on the Tracker, the Synth starts playing but i can’t tell if they are properly synced. They definitely are not starting on STEP 1 (consistently).
Tracker+ set to: Clock out and Transport out over both USB + MIDI (been this way since my OG tracker and have never had an issue) Synth: Clock In and Transport in set to Midi In Jack; pads locked
Hit play on the Tracker, the Synth does not start playing. I can see the locked pads lit, yet the do not play. In order to have the sequence/arp start on STEP 1, I have to hit SHIFT+PAD. Sometimes it starts without re-triggering the already lit pads, sometimes it doesn’t.
I have glanced at the manual, but none of this makes sense intuitively, to me. I have a studio full of boxes with their own sequencers and syncing, none of this happens.
Lastly, the same pads stay lit when i change SCENES. Why? Sometimes I leave my studio on for 12-24 hours. Would this cause this machine to act oddly?
I only received it a few days abo and for the first time am considering returning something so quickly. It also froze twice now in two days just browsing presets (had to power cycle) PLUS I’ve overloaded the CPU multiple times using the effects.
I even choked the entire sound output to where it stopped producing sounds completely, bc I was using an LFO to modulate a filter (LFO1 was sent to 3 destinations, one was filter cutoff, i dont remember the engine).
Video of the pads staying lit when i switch scenes. Unsure if this is a feature? I thought I read scenes save SEQ/ARP data per scene. This seems odd then?
Hey there @quone.sw, would love to help you but i‘m slightly confused by a couple things. Sadly i don‘t seem to be able to access the video either that you posted?
A video of your setup and what is happening would definitely help to see what‘s going on.
I’m having the most success by setting midi clock to the input jack and wait for start on, but keeping the transport OFF. This just doesn’t seem right to me and if it is it needs to be properly outlined in the manual. Because I don’t know why we would have transport in and then wait for start external transport in.
But I still can’t get it to sync up every single time I start the transport externally.
Hey @quone.sw , sorry for the delayed reply. I’ve been off for a couple days. Thank you for reuploading the videos. I’ve had a look and tried this myself and can confirm what you are seeing. It does indeed behave weirdly/incorrectly.
Just for confirmation. It looks like you are trying to play the arps/sequences directly on the Synth by latching the notes, correct? As in: you don’t want to sequence them on the tracker.
The Transport In option is purely for choosing which transport the Synth should be listening for: either MIDI In Jack or MIDI In USB.
Wait For Start is the more confusing one, but makes sense with a bit of context. Some devices (and DAWs) send constant Clock, not just when Play is pressed. So hence Wait For Start ensures that the arps/sequences are only triggered once a MIDI Start event is received.
The Tracker for example does not send constant clock messages (unlike the Play), so in that case it may appear confusing and uneccessary. But essentially the correct MIDI Settings, in your case would be:
Clock In: MIDI In Jack
Transport in: MIDI In Jack
Wait for start: On.
Now - with that said, there appears to be a bug, that the arp/sequences are not restarted correctly. Currently the only way to get them to trigger again, is to unlatch the notes and latch them again on the synth. Or to sequence the notes externally.
I’m gonna go ahead and update this topic to become a bug report with all the necessary parts and send it on to the team.
Thank you for all the details and videos and sorry for the inconvenience this caused you.
Thank you for taking the time to check this out! I’m sure this might not be an issue for some, but the way I jam, it is indeed confusing me.
Correct!
This is clear, and I now understand. I am also going to try and use the Tracker’s MIDI tracks and ping a single note out to the Synth, to see if this provides expected the behavior. I have since realized the Synth is, well, in fact as SYNTH first and foremost, and the arp/sequencer functionality is a bonus.
I also posted a request to change the behavior of the SHIFT button when the unit is in ARP/SEQ mode. The request would change SHIFT x2 to PLAY/PAUSE and SHIFT x3 would be KILL ALL LATCHED NOTES.
