In the past i routed my internal midi like this:
But since 130 the midi will be recorded, but there is no monitor-signal anymore as you can see here
BWS says the HW-Ins was never devoloped for making internal routings. Ok, but the IAC isnt realy internal, is it?
And why worked it in the past in not yet?
And what is an alternativly way now? Without midi-stunts like this, BWS is quite useless for me.
how to route INTERNAL midi now?
-
DJ-Superherpes DJ-Superherpes https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=333433 - KVRist
- 217 posts since 29 Jun, 2014
-
- KVRAF
- 5144 posts since 3 Oct, 2013
it should be sticky or whatever seems everybody struggle with it, my way is currently >
general steps> create a group track for every instrument (layer) group
- all the instruments go to instrument layers
- all the effects go to fx layers beside the affected instrument (so macros gonna work per instrument group based because always there is a top instrument container which contains all the instruments and fxs, till you not have to use some modulation container
which can f* the whole nice structure, but it's an other story, anyway try to use the modulation devices somewhere at bottom of the device hierarchy, they should be transparent(currently they are black boxes) I've requested it many times ... currently I'm using the internal LFOs of the VSTinstrument/devices instead of the Bitwig's one just because of this)
this is a group track >
- if u have multi-in instruments should create an empty group track for every channel and route them directly to the VSTis
should put the MIDI track(s, can use more if u want to use lanes) into it and route them to the channel group (it will sum the MIDIs and gonna send them to the VSTi using the given channel)
if u put an arp/MIDI generator device into one of the MIDI tracks and want to record its out, should set the "in" of the channel group track to it and press record (F9, as in the video)
- if u have non-multi in instrument(s) don't have to use inner groups just simply should
create a group track for the instruments(layers) and the fxs(layers)
then create MIDI track for it (or more if need lanes as on the picture) as u can see the mixer view is quite useful there are per instrument columns with the affected fxs and all the MIDI tracks (all of them are toggleable so they can hide the MIDI tracks if u close the given group, can hide and fxs if u close the fx layer with the small arrow etc.)
this is the fully open state:
as u can see Nexus uses parallel fx signal chains
as u can see on the arrangement pictures above all the instrument groups use only one per group automation lane so the arrangement view is quite clean (as on the video), all the per group automations can be switched off using just an empty clip on the given group track (launcher view)
- case three> instrument containers like drum machine normally they can be used
this way so instruments to cells and fxs into fx layers beside them, mixer view also will be quite nice (instruments and fx will be in different columns)
because we used group tracks for instruments can change between them with the group selector
bounce in place gonna work directly on the group tracks (as in the video)
general steps> create a group track for every instrument (layer) group
- all the instruments go to instrument layers
- all the effects go to fx layers beside the affected instrument (so macros gonna work per instrument group based because always there is a top instrument container which contains all the instruments and fxs, till you not have to use some modulation container
which can f* the whole nice structure, but it's an other story, anyway try to use the modulation devices somewhere at bottom of the device hierarchy, they should be transparent(currently they are black boxes) I've requested it many times ... currently I'm using the internal LFOs of the VSTinstrument/devices instead of the Bitwig's one just because of this)this is a group track >
- if u have multi-in instruments should create an empty group track for every channel and route them directly to the VSTis
should put the MIDI track(s, can use more if u want to use lanes) into it and route them to the channel group (it will sum the MIDIs and gonna send them to the VSTi using the given channel)
if u put an arp/MIDI generator device into one of the MIDI tracks and want to record its out, should set the "in" of the channel group track to it and press record (F9, as in the video)
- if u have non-multi in instrument(s) don't have to use inner groups just simply should
create a group track for the instruments(layers) and the fxs(layers)
then create MIDI track for it (or more if need lanes as on the picture) as u can see the mixer view is quite useful there are per instrument columns with the affected fxs and all the MIDI tracks (all of them are toggleable so they can hide the MIDI tracks if u close the given group, can hide and fxs if u close the fx layer with the small arrow etc.)
this is the fully open state:
as u can see Nexus uses parallel fx signal chains
as u can see on the arrangement pictures above all the instrument groups use only one per group automation lane so the arrangement view is quite clean (as on the video), all the per group automations can be switched off using just an empty clip on the given group track (launcher view)
- case three> instrument containers like drum machine normally they can be used
this way so instruments to cells and fxs into fx layers beside them, mixer view also will be quite nice (instruments and fx will be in different columns)
because we used group tracks for instruments can change between them with the group selector
bounce in place gonna work directly on the group tracks (as in the video)
Last edited by xbitz on Sat Dec 19, 2015 4:14 pm, edited 15 times in total.
"Where we're workarounding, we don't NEED features." - powermat
-
- KVRAF
- 5144 posts since 3 Oct, 2013
and another video about the generators using the method above
need a group track and the inner MIDI one with the generator in it, the group in is set the inner one ... done , can record MIDI and can use bounce in place, both from the group track
need a group track and the inner MIDI one with the generator in it, the group in is set the inner one ... done , can record MIDI and can use bounce in place, both from the group track
"Where we're workarounding, we don't NEED features." - powermat
-
- KVRAF
- 5144 posts since 3 Oct, 2013
...and forgot to mention but there is another good reason for using this type of routing(instruments on group) currently this is the only way to set the dry/wet levels together from a common macro, this is especially important if there are different send levels on the instrument layers
so the problem is the following> the dry and wet/send signals go to different ways to the master ergo if the dry is set to zero the wet one is still can be heard
currently the only solution is assigning the a common macro(key is the bipolar mode, which can change the levels relativly to plus/minus range) and changing/automating that one
so the problem is the following> the dry and wet/send signals go to different ways to the master ergo if the dry is set to zero the wet one is still can be heard
currently the only solution is assigning the a common macro(key is the bipolar mode, which can change the levels relativly to plus/minus range) and changing/automating that one
"Where we're workarounding, we don't NEED features." - powermat
-
- KVRAF
- 4803 posts since 21 Jan, 2008 from oO
nice, maybe post a link to this thread in the tips and tricks thread, would be cool for later reference. 
JamWide - a cross-platform Ninjam client for DAWs
-
- KVRist
- 365 posts since 23 Jul, 2013 from Bay Area, San Francisco
+1Suloo wrote:nice, maybe post a link to this thread in the tips and tricks thread, would be cool for later reference.
And please let us know where you found Prasendrescher! Been looking for it for months now
