Well, I spent 3 weeks learning Bitwig 4 on a trial license, then bought the full license 4 days ago.Tj Shredder wrote: Wed Jun 21, 2023 2:46 pmDid you setup an extra script for the arp Midi port?Milkman wrote: Sun Jun 04, 2023 6:00 pm My only trouble with Vector today is that I cant seem to get Bitwig 4 to read the arp output from the Vector, which has its own output channel. In Cubase the vector works fine in/out, but Im struggling to get Bitwig to even see the arp midi.
I spent a few hours on 3rd party scripts, including the Driven by Moss scripts, and I really found them to be super maximal for the minimal config I am trying to build.
So I built it my own way, with 1 instrument track for the Vector MIDI in/out and a second instrument track for Vector MIDI arp input only. This is identical to how it works inside Cubase 12 -- 1 track for MIDI in/out, second track to grab incoming MIDI arp. Bitwig does not see the incoming MIDI Arp data from Vector no matter how Vector or Bitwig are configured. All my other HW and soft synths send their MIDI Arp data to Bitwig, Cubase, etc, without any trouble. The issue may be in how the Vector sends that data. I tried Note FX and MIDI channel mapping stuff in Bitwig, but it didnt see the MIDI arp.
Is there some sort of script to do this a different way? Maybe, but I am looking for minimal configuration so that I can continue to build and route the way I like to, per my own philosophy. *To start*. Later I can get more into 3rd party scripts if I can find a use for them. I switch back and forth between Cubase and Bitwig for now.
Edit: I should also add, I've not been able to get Maschine and my MK3 working perfectly inside Bitwig 4, either. Without scripts by Moss or whomever, getting Maschine to read/write MIDI data to/from Bitwig is also a pain, unless you are using a single "group" inside Maschine. If you only use one group, that's easy to read/write to Bitwig. As soon as you try to add multiple maschine groups and assign MIDI routing to/from them in Bitwig, you get problems. From everything I've read, you need 3rd party scripts to use Maschine(properly) as a plugin inside Bitwig. For now I use a single Maschine group, or I just do it all in Cubase and send WAVs to Bitwig.
Im looking forward to future Bitwig updates that perhaps fix these baffling integration issues. These things all work fine inside Cuabse 12, without any 3rd party nonsense or even specific integration support.
