better way for get track to track midi-in, than with the note-reciever?

[kukident-youth]

Well in live i just route my source-midi-track into another mid-track and if i on/off the ARM the destination track gets this input or not. (for booth: hearing/monitoring and for record/"resample").
Afaik, in BWS i need a note-reciever for hearing/playback the source midi-track and i need a similar live-routing for record/get in clip... the source-midi-in.
This extra-routing has a lot of steps to do / compliactions i never had in live.
This is not an academic problem.... In live i build up my (midi) chords/bass/melodies.... first with my Reaktor/PhrasendrescherZwo Plug-IN from the same one (source) track and record the different settings/doings in this Plug step by step to different tracks... just by ARM the current track i want this notes+++ from the (source) plug. Thats all! In BWS i can do "the same"... but!!!! ... But with BWS and the necassary?????? note-reciever there a lot of irritations /extra-steps i have keep in mind/ allways to widewindowed fix... SO is there any way the simple/efficent live midi-track-to-another track behavior to get in BWS... this easy midi-mixer-routing source/destiantions and arm on/off if i wish and i get access to hear/monitor/record if i wish and MUTE this input if i not wish, just by arm on/off?

[sth]

Yes, just change the Note Input of the Track you want to receive, and set it to the Note Output of the Track you want to send. The dropdowns aren't _always_ visible, but you can see them on the Inspector if you click on any Track.

[kukident-youth]

Yeah, so far thanks, but not really....: or maybe i miss/missundertood something????? Your answer works for ONE "reciev" track" with the opposite of recieve/send.... But its not my point: I want a FLEXIBLE/ current (if wished) route/in/out ("activated")...possibility ........ Is absolut "possbily" that i dont get your point (sry, my englsih is not got enough to understand "details" in ABSTRACT technically explanations....) .... so please explain it a little bit deeper, like for child of 6 years, if i missunderstood your point... .... Thank you!!!!!!!! ... Sooooo, its just the inverted "solution" by a reversed problem....
My point/wish is: I want to ADRESS different tracks by "routing", but ONLY the currents /selected/ armed.... Track get the info/trigger.... If i want.... e.g. by just armed...... !

1000 Thanks!

[pdxindy]

My point/wish is: I want to ADRESS different tracks by "routing", but ONLY the currents /selected/ armed.... Track get the info/trigger.... If i want.... e.g. by just armed...... !

1000 Thanks!

You mentioned Live, but in Live you cannot just arm a track. You also have to change the send track to go to the track you want to arm.

[ReleaseCandidate]

My point/wish is: I want to ADRESS different tracks by "routing", but ONLY the currents /selected/ armed.... Track get the info/trigger.... If i want.... e.g. by just armed...... !

1000 Thanks!

You mentioned Live, but in Live you cannot just arm a track. You also have to change the send track to go to the track you want to arm.

No, you don't. You can change the output _or_ the input with Live.

I didn't find a way to easily do the routing kukident-youth wants in Bitwig, sorry.

[Dionysos]

It's a bit of a pet peeve of mine, too. The way this works in Bitwig is just slightly too unwieldy for me to use plugins like Scaler 2 comfortably, or at least without ending up with a big knot in my brain.

EDIT: When I say "in Bitwig", I don't mean "in Bitwig as opposed to Live or some other sequencer", I don't actually know whether this is much easier in other DAWs.

[pdxindy]

My point/wish is: I want to ADRESS different tracks by "routing", but ONLY the currents /selected/ armed.... Track get the info/trigger.... If i want.... e.g. by just armed...... !

1000 Thanks!

You mentioned Live, but in Live you cannot just arm a track. You also have to change the send track to go to the track you want to arm.

No, you don't. You can change the output _or_ the input with Live.

I didn't find a way to easily do the routing kukident-youth wants in Bitwig, sorry.

Yeah... track routing in Bitwig is confusing. It doesn't work as one would expect and is IMO unnecessarily convoluted. Of course in Live you cannot simply put an arpeggiator in front of a synth. You need to use 2 tracks to do it.

In Bitwig, arming or not arming a track does nothing to affect playback, only recording.

One can set Track 1 (sending track) to output midi to Track 2. Set Track 2 to receive midi from Track 1. Then it can both play and record midi without a Note Receiver. One can use this method to record the arpeggiator and/or other midi device chains from another track. You do this with multiple receiving tracks and only the one selected in the sending track will play/record.

[sth]

Yeah, I really don't understand the question more after the extra explanations. I know of two ways to push Notes around, the MIDI Receiver Device and changing the Track's Input; I use both methods and it seemed like you didn't know about the 2nd and wanted something similar to it. I'm not 100% on the specific arming behaviors so maybe that's where I went wrong.

I imagine I have a similar setup to what Dionysos was describing:

1. A single "Global" MIDI Track that would handle 80%+ of my MIDI, with notes separated into MIDI Channels by "spectrum." For example, Ch1 for Sub notes, Ch2 for Bassline notes, Ch3 for Pads, etc. These are very "high level" and contain mostly the chords in legato lengths, like 2 or 4+ bars long.
2. For that same Track, generally I have a Note Pitch Shifter for transposition and sometimes Scalar 2 to identify what I already have or look for possible changes.
3. Most of my other Instrument Tracks receive MIDI From that Track, either by changing the Input of the Track or using a Note Receiver (if I'd rather _also_ play some Notes myself). They would also Channel Filter to select their specific "spectrum."
4. Those Tracks almost always have some sort of "Note Sequencer" that would arpeggiate or otherwise play the Notes differently than the original Chords were played; longer sections for Pads, a defined rhythm for Chords, tons of Notes for Arps, etc.

I don't see any part of that as "excessive" or "unwieldy" but quite the opposite. With a single MIDI Controller and some Zones across the octaves, I can play into one Track and control almost every instruments' Notes/Chords very simply, and it really makes "sketching" the songs very easy.

I guess I have one problem with my workflow that I still need to solve, and that's the lack of a "bounce MIDI in-place." Given that each Track also has a Sequencer, I cannot simply used the Armed Recording to capture the Notes for that Track, since it'd just be grabbing the "Global" Notes again. Late in the Project if I want to "flatten" everything for some more-specific tweaks, I basically need extra Tracks the listen to the Instruments' Tracks and Record _those_, then move that back onto the Instruments and disable their beginning Chain.

[kukident-youth]

3. Most of my other Instrument Tracks receive MIDI From that Track, either by changing the Input of the Track or using a Note Receiver (if I'd rather _also_ play some Notes myself). They would also Channel Filter to select their specific "spectrum."

My problem starts always here: I dont get midi from the "master-source-midi-chanel" just by changing the input of the destination track. At least not for mornitoring, for reording the midi-data from the source-midi-track get recievedm but for just hearing the "master-midi" in this track, i need a note-reciever too! Thats my main-prob.

[pdxindy]

3. Most of my other Instrument Tracks receive MIDI From that Track, either by changing the Input of the Track or using a Note Receiver (if I'd rather _also_ play some Notes myself). They would also Channel Filter to select their specific "spectrum."

My problem starts always here: I dont get midi from the "master-source-midi-chanel" just by changing the input of the destination track. At least not for mornitoring, for reording the midi-data from the source-midi-track get recievedm but for just hearing the "master-midi" in this track, i need a note-reciever too! Thats my main-prob.

Yeah... changing destination of the input track to the sending track doesn't do anything by itself. It doesn't play or record notes. It makes so little sense that sometimes I think it must be buggy. I'm curious what Bitwig's thinking is about it.

If you want to hear the midi, you can either send midi from the source track or use a Note Receiver.
If you want to record midi you can either send from source and receive from source, or receive from source and use a Note Receiver.

Don't know if it could be more confusing for the new user. Once I figured it out (it is not explained in the manual that I found), I find it quick enough to suit my needs that it is not a frustration for me. But I'm sure every new user tries to set a track to receive midi from another track and is puzzled that nothing happens.

[sth]

3. Most of my other Instrument Tracks receive MIDI From that Track, either by changing the Input of the Track or using a Note Receiver (if I'd rather _also_ play some Notes myself). They would also Channel Filter to select their specific "spectrum."

My problem starts always here: I dont get midi from the "master-source-midi-chanel" just by changing the input of the destination track. At least not for mornitoring, for reording the midi-data from the source-midi-track get recievedm but for just hearing the "master-midi" in this track, i need a note-reciever too! Thats my main-prob.

Yeah... changing destination of the input track to the sending track doesn't do anything by itself. It doesn't play or record notes. It makes so little sense that sometimes I think it must be buggy. I'm curious what Bitwig's thinking is about it.

If you want to hear the midi, you can either send midi from the source track or use a Note Receiver.
If you want to record midi you can either send from source and receive from source, or receive from source and use a Note Receiver.

OK, just verified, and I see what you mean here, but my experience is still a little different and much simpler than you described.

Simply changing the Input MIDI to another Track/Device _does not play_ those notes, but it _does record_ them (i.e. no need to alter the Source's Output, or bring in a Note Receiver).

Simply using the Note Receiver basically does the opposite, letting you _play_ but _not record_.

I use all of this just fine, Note Receivers etc. on most Tracks, and I don't see the big issue since it does what I want it to. This boils down in my mind to "How can I do X, and I know that Y will do X, but I don't want to do Y, so I how can I do X without the usual Y" and I don't see the same problems with Y that you all do. What is wrong with the Note Receiver?

[antic604]

What is wrong with the Note Receiver?

I don't think there's anything wrong with it and it actually works as expected - since it's a track device, then it's obvious the notes won't be recorded to the timeline, but can be received by further devices.

The only thing that's "wrong" with MIDI routing in Bitwig is that you can't monitor notes that come via track's input or are sent to it using "Send notes to..." from other track. Having to insert Note Receiver to compensate for that is redundant and unnecessary (and unlogical, too).

EDIT: actually the notes sent via "Send notes to..." are both monitored & recorded.

[kukident-youth]

I use all of this just fine, Note Receivers etc. on most Tracks, and I don't see the big issue since it does what I want it to.

I use this stuff, too. And i also dont see a BIG issue by bitwigs-behavior of handle this question. BUT Its just a question of workflow and wide-windowed: if i eg. just record a clip from source to destination track and ´´m in edit-view i dont see the devices and playing taht clip now get booth-ins from the clip and my source-midi... i fisrt have to switch to device-view, disable the recive and have to go back to edit-view.... And if i need another clip i have to do it viceversa, than record the clip from source, than do the steps above again.... Of course, there a bigger problems in the world, bit this is un-elegant/wide-windowed... but this issue could solved very easy: Either i could see the reciever in the track-mix/input view an disable it there or why not an option Ableton-behavior by routing midi to midi????

EDIT: By using the mixer-view its more easy to handle. Here i can de/activate the reciever AND and edit the clips in sidebyside-view

[sth]

I use all of this just fine, Note Receivers etc. on most Tracks, and I don't see the big issue since it does what I want it to.

I use this stuff, too. And i also dont see a BIG issue by bitwigs-behavior of handle this question. BUT Its just a question of workflow and wide-windowed: if i eg. just record a clip from source to destination track and ´´m in edit-view i dont see the devices and playing taht clip now get booth-ins from the clip and my source-midi... i fisrt have to switch to device-view, disable the recive and have to go back to edit-view.... And if i need another clip i have to do it viceversa, than record the clip from source, than do the steps above again.... Of course, there a bigger problems in the world, bit this is un-elegant/wide-windowed... but this issue could solved very easy: Either i could see the reciever in the track-mix/input view an disable it there or why not an option Ableton-behavior by routing midi to midi????

EDIT: By using the mixer-view its more easy to handle. Here i can de/activate the reciever AND and edit the clips in sidebyside-view

I gotcha. I've definitely been using almost all of the views recently since they're all good in their own way. I've never done the back/forth you're talking about, so the "swap once then record" workflow for me is less painful.

[horizon7]

I wish if there’s also a “send to” device
for midi & audio.

This is useful eg. in a song that has dub step beats or break beats which you want the kick & snare to be used as side chain but each has different effects. in other words this is useful for summing a bunch of midi channels or tracks at certain position in the chain to one track. unlike the track’s send.

It can be used also to control several tracks at one time in case on note fx.

I’m not whether it might consumes CPU or not.