My DT2 is set up to send midi on track 8/channel 2 to my 0-coast and on track 7/channel 3 to my TD3. It works all fine, but when I want to play for example E3 on both tracks, the 0-coast doesn’t play any more. Any other note than the one the TD3 uses is ok, but never the same one.
I have setup midi channel 2 on my 0-coast and channel 3 on my TD3 correctly, but I miss something and don’t know why. Any ideas? I tried different things in the DT in the midi settings, but no chance. Plz help! Thanks
What MIDI connections have you made between the three instruments (DT2, 0-Coast, and TD3)?
Its the CME MIDI Thru5 WC
Assuming that everything else is correct, I’d suspect that the problem is here, within the CME midi thru.
To test this, you could try sending midi from the digitakt into the TD3 and then using the TD3 midi thru port to pass the data on to the 0-coast with a DIN cable.
If the behavior still exists connected in the daisy chain like this, then the problem is probably with 1 of the 3 devices (digitakt or 2 synths).
If the problem stops when passing thru the TD3, then the issue is probably that your midi thru device can’t properly separate thru messages on different channels simultaneously when the midi note being sent on both channels has the same midi note number.
If the behavior indicates that the CME product is the problem, I’d see if the firmware can be updated and start there. If it is not a device where you can update the firmware, I’d contact the manufacturer.
I always dislike when the answer is to buy a new thing but you could buy a new thing 
I have a distrust of midi thru!
Ok this is interesting: I tried Midi out from DT directly into the TD3 and its midi thru into the 0-coast and it does exact the same thing. So the midi thru box is not the problem… damn
Super weird. Can you show a picture of your midi settings from the digitakt gear wheel menu? Maybe something will jump out but the behavior of the 0-coast doesn’t really make sense.
Are you monitoring with speakers? Is it possible that the 0 coast is playing the note but the level is below the other synth and so it’s getting cancelled out or something? If you did not already, maybe try turning the td3 vo.ume all the way down just to confirm.
It happens with all notes or only with E3? It plays E3 normally if the TD3 is not present?
I am also suspicious of maybe some relationship to the way elektron sends a note-on message but uses velocity zero instead of note off. I would think that separate midi channels would mitigate this but with them sending at the same time and same step, it feels like the second note-on message is not being sent or not interpreted correctly.
Something small is missing from the picture right now which is obscuring our view but and maybe we can figure out what it is.
Did you try sending different note lengths? Maybe lengthen the note length on the source page as a test? If possible use a midi monitor program and confirm that the digitakt is sending 2 individual note-on messages for the same note, one for each channel and track.
You could set up test tracks with only 1 note sent from the same step on each in order to make the data easier to read.
You could also try micro-timing the problem note ahead or behind by a tick. Or you could launch it from the next or previous step, but microtimed all the way towards the desired step and see if that change of timing impacts anything. Even though the distance is very small, perhaps due to the serial protocol it will make a difference.
So it is on every note, not just E3. And I did some test now and found out that when the note length on the 0-coast is above 16 it plays the note. So with 17 it works. I tracked it all with a midi monitor and took a screenshot, so maybe you can see what the problem here is?!
I have tried all of the midi settings in the DT gear menu, checked out every variation, but it seems like it is setup all correct. I asked GPT for the problemt and it said that there are some monophonic synths that are very sensible for very short note on/off messages. So can it maybe be the point that when they are both play the same note, the gap between note on/off is too short for the 0-coast?
This is the only reasonable explanation. We can look for other instances online where this is mentioned for the no coast specifically and if we find someone else with the same synth and similar issue I would take that as confirmation.
The midi monitor confirms both notes are sent by dt with the same time stamp and that they’re going to the correct channels.
Try the thing I mentioned about setting the same note on a different step and micro timing it forward. So if it’s step 5 for the td3, try setting the 0 coast note on step 4 and then micro time that note all the way forward by holding the trig down and using the right arrow key to push it forward all the way, just to see what happens when the 0-coast data is sent first but with essentially the same timing. Use the 16th note since that is the source of the issue.
I’ll try and google the 0 coast behavior with 16th notes.
The more I read, the more likely it seems that the internal midi to cv conversion that is going on inside the 0 coast is somehow not able to keep up when the same short notes are sent on different midi channels but I’m not sure how to prove it. The data for all channels is sent at once and it’s the synth which picks out the data from the channel it’s listening for, but it’s exposed to all data for all channels.
It looks like (from the midi monitor) for some reason channel 3 is always sent first, even the note off (velocity 0) appears for channel 3 first. I might try switching which device is on which channel and see if there’s any impact on the behavior. Basically testing the behavior of the 0 coast when it’s on ch3 and the td3 is on ch2.
Thanks for your intensive help 
I tried some more things:
So I now come to an end and just set the 0-coast note lenght to 17 and regulate it via the 0-coast envelope. That works. Its not solving the problem but it works for me 
