Digitakt 2 turn off midi tx per track

Elektron Gear Digitakt
1

Hello, new user here. I am trying to sequence my Jupiter X with my Digitakt 2 with the midi out to the midi in of my Jupiter X (physical din plug). The problem I’m facing is if I want to use the I-ARP in my Jupiter X, I must turn on remote keyboard in the Jupiter X. At that point it responds to EVERY midi channel the same. Is there a way to turn off the midi transmit on the digitakt 2 on a per track basis?

If I turn remote keyboard off in my Jupiter X, it then behaves as other devices and only responds to individual midi channels and whatever scene/part I assign them to, but I loose the function of using the I-arp triggered by the digitakt.

2

I tried to google this, I think the JX is the problem, in iarp it seems to enter omni mode as you found and receive on all channels but this reddit post showed a couple suggestions that you might try out. The OP later stated:

“If I set the “Remote Kbd” to “MIDI IN” in the global settings, it plays every part on every channel and the iArp is working. If I set it to “USB Com” or “USB MEM”, I can play each part individually on each single channel BUT the iArp is deactivated. Completely gone.”

Behavior sounds too similar to be a coincidence. So as far as turning off the midi on a per track basis, muting the midi track should have the effect that it stops sending any midi data. Have you tried using a mute?

Also, the midi can be turned off on a per track basis in the settings menu, or also from the midi source page you can turn it from the channel you selected back to the X, but I’m pretty sure unless we’re not on the same page that muting any midi tracks you do not want note data being sent from should do the trick.

1 Like
3

Yes that is exactly my problem. I did see that redit that you quoted and same thing with on usb com. Weird issue. I wonder if enough people report to Roland they will write an updated FW lol. Thank you for the other suggestion on midi mute, I am going to try that tomorrow and report back

1 Like
4

Ok let me know and if it doesn’t work and I’ll see if I can figure something else out. Are you only trying to sequence the JX from your digitakt or do you have stuff on other midi tracks as well? I just want to make sure that I understand where the midi data you’re trying to avoid is coming from. I’m assuming you must have more than one midi track set up to have note data coming from multiple channels at once but just want to confirm.

1 Like
5

Yes only on JX. I realize it would never be possible with 2 or more external devices if my JX is listening to ALL midi channels. Unless I want them to play the same note lol. I tried this before a while ago with my Korg EMX and ESX. But you can’t turn off midi tx on the EMX/ESX per track. You can change the channel but not off, I wasn’t sure any device can do this, as it’s an odd request.

So basic hypothetical senecio, I want 15 tracks locally playing on the digitakt, and 1 track to send some stuff to the JX, all while the digitakt is only outputting midi only for the one JX track.

6

Sure, when you assign a midi machine to your 1 midi track, from the source page you would select and confirm the channel you want that track to send data on and it will only send on that channel. In the midi source page you’ll also be able to set any bank change or program change messages but that’s only if you need to use those features.

Because dtII can assign any track as an audio or midi, 15 audio and one midi is no problem. My only confusion right now is were you initially talking about the jx behavior as it acted with the korg as master? Or did you already try sequencing it from the digitakt and still had an issue? Unless you have multiple multiple midi tracks with different sequences on different channels, the Jupiter should only hear whatever midi channel you’re sending on.

Even with that weird omni mode type behavior on the roland I don’t think you should be having an issue. Also, as I was saying previously, even if you had like 4 midi tracks, as soon as you mute the other 3 they’ll stop sending note data so no problem there.

7

I just got the dtII today and tried it briefly with same result as EMX so I just figured I’d ask here since it’s such an active responsive group

Both sequencers work as expected when JX is just in regular midi mode, but no arp trigger. With JX in remote keyboard mode arp triggers but so does 15 other things at once on it, because it’s listening to ALL channels in that mode.

Normally I wouldn’t care and just work around, but the I-arp on this synth is really cool to me.

I’ll give what you said a try tomorrow. But it doesn’t sound like you can actually turn the midi tx off per channel on dtii. Some of the older MPCs allowed this I remember. But at the time I didn’t know why you would need to do that.

1 Like
8

Ok so maybe what I’m understanding is wrong, the problem is then that the arp sequence or the sequence intended for the arp is triggering all tracks on the jupiter? Meaning that you send on one midi channel which is supposed to only engage the arpeggiator, but that one channel triggers all tracks plus the arp so it’s madness?

If that (what I just said) is the way it’s happening, I don’t think anything you can do with the digitakt will change the way the jupiter is “wired” or in this case programmed is probably more accurate. That is an extremely strange behavior for them to build into the firmware.

Um, ok omni mode or all channels like I was talking about is when a device is set to listen on all channels. That’s like a very general protocol that dumbs down the midi experience for the user and is like 5 levels below auto-channel, it’s intended to make a midi device listen to whatever channel is trying to talk to it, even if it’s multiple channels at once, it will try and play them all up to the limits of it’s polyphony.

So if it’s not that, and the issue is jupiter triggering 16 tracks at once despite only receiving data on 1 channel, I don’t think any setting on the master device is going to impact the way the peripheral interprets and distributes data.

There was another post on that reddit page, where a different dude says:

"make sure the correct parts are on and off indicated by the blue lights for quick reference part selection is numbers 6-10 on front panel under 6-10 you will see part/osc on 1-R these are the 5 sounds with R being the 5th track 5th track only carries rhythm and drum kits on the jupiter

FIX*** on jupiter xm click scene then click page arrow twice to right

screen should now be on scene part edit menu stroll menu to bottom to find RX CH this is where you will select the midi output CH for each sound to play back your midi parts in fl studio or daw of choice

tap the part/osc/ 1- 5 on front of jupiter xm to change setting of each part

My RX channel for sound 2 was set to 1 which made nothing play on midi 2 channel instead midi channel 1 played both sound 1 & 2 hope this helps"

So that indicates there should be some way to mute parts directly from the jupiter, have you tried this already, what he’s talking about? It sounds a little fiddly but if you aren’t using those other tracks immediately before the arp it might be doable. Although as I have no JX to test it on, I can only tell you how it reads as opposed to whether it actually works.

2 Likes
9

Sounds like I need a midi solutions big box and filter out some channels.

10

The issue unfortunately doesn’t sound like it can be filtered due to the nature of the problem. If you’re only sending on (example) midi channel 1, then the sequencer data should only be pointed at the track or part for which midi channel 1 is the destination, in this case the arp. Let’s say you filter out channels 2 through 16 and you’re only sending on 1, but when it hits the jupiter it sounds as if all “parts” are responding to the one trigger, and only in the remote kbd mode described, because like you said it’s otherwise working as expected.

I just don’t want you to go spending money on something to fix this because filtering the midi isn’t going to change the way they wrote that weird behavior into firmware. It almost sounds too much like a bug to believe they intended for it to be that way man, I just can’t imagine any situation where you would want to trigger everything at once.

The only time you really see that, is on (for example) synths with unison mode, where all voices play at once for like a thick mono synth sound, but you wouldn’t usually use that with rhythm parts or anything so since it has a drum part it would be weird to want to layer that with the others. I mean I’m just guessing as to their intentions but I can’t help but feel like it’s a bug rather than a feature, you know?

Also, unison mode would be something you had to turn on, and it shouldn’t change based on the keyboard setting. I can try and look at the manual though and see if it says anything about unison.

eidt: Ok so I just watched this video and if it’s the same keyboard shown here, it does have a unison mode but it’s saying that it automatically detunes the oscillators as opposed to stacking voices. I’d still make sure this button isn’t lit but I don’t think this is going to fix it, it’s just something to try.

Just looking at other posts on other forums and this stacking of the tracks seems to be happening to more than just a few people when trying to trigger the iArp from external. It’s definitely not just yours with an issue.

1 Like
11

Yes I can control all 5 JX tracks from any sequencer fine, but if I want to trigger I-arp, the JX has to be in remote mode and receives all notes from any sequencer therefore playing ALL midi channels it receive

Edit. It’s the I-Arp. They are blocking it somewhere in software. Just to work on a dedicated midi channel would be easy.

1 Like
12

Ok. I got it. No wonder I was confusing, I feel like an idiot now. So I just got the digitakt II second hand. I see there are some weird things programmed on this. I factory reseted it. I think it was set to send midi on all tracks or something. This is the way EMX/ESX always are and you can’t turn it off, so that’s why I thought it was like that. I just tested it from a factory default, plugged in the midi out and turned the JX to remote keyboard. Hit play and no sounds being triggered! Then I just changed one track to a midi track and set to channel 1. Triggers perfectly and I-arp works while playing other 15 tracks in DTII! Thank You!

1 Like
13

What a wild ride lol

1 Like
14

Lesson learned, always factory default used gear, especially if you are trying to learn it from scratch. It had some good patterns when I got it so I was hesitant. Come to find out it was just the factory ones all modified doing weird stuff.