Quantcast
Channel: KVR Audio
Viewing all articles
Browse latest Browse all 5068

Bitwig • Re: Kinda sick of talking to NI about maschine2 + Bitwig routing

$
0
0
Im not sure how to capture all routing visually. Ill upload the template. I can upload a maschine template also if it is useful.

Its the simplest maschine-only BWS template. I have attached this 5.1.3 template to this post. When loaded, this project causes BWS to claim there is a loop and that I should contact support. I did so and am waiting to hear back.

-This is a blank template with the maschine plugin loaded into 1 instrument track, and that track has no input device set. The main plugin midi config is ALL/1.
-The other 3 tracks are tracks for connecting maschine groups (A1, B1, C1) to the corresponding midi channels (6, 7, 8), which are also configured in maschine's routing.
-These 3 tracks(A1, B1, C1) have input settings connected back to the main plugin(either way doesnt work - "maschine mk3 midi" or "maschine(device)". Bitwig output setting is "notes to tracks/maschine(device)" for each group.

Machine's routing is also standard for use inside a DAW, and is the EXACT WAY I had configured it before when this all worked. I can configure all this in Cubase 12 in 30 seconds, with as many maschine groups as I want, and everything works. Tested this last night. Bitwig seems to have the most trouble.

My maschine--group A1 (all groups are the same except midi):

-group/midi INPUT settings are manual, host, ALL channels (the plugin must receive notes on all channels to allow multiple groups to send notes to it)
-sound/midi INPUT settings are default, on channel 6
-sound/midi OUTPUT settings are host, channel 6

This works on cubase, and it worked on earlier versions of BWS without any loops.

Statistics: Posted by Milkman — Sun Feb 25, 2024 6:45 pm



Viewing all articles
Browse latest Browse all 5068

Trending Articles