Ripchord original notes still playing when connected to LibreArp and then a Synth
-
- KVRist
- 47 posts since 30 Oct, 2019
Good day. I connected Ripchord to LibreArp and then to a synth but when I play a note, the notes in Ripchord are playing at the beginning, in addition to the LibreArp pattern. I only want the LibreArp pattern to play. Is there a module or something I can add, to prevent these original Ripchord notes from playing?
-
- KVRist
- Topic Starter
- 47 posts since 30 Oct, 2019
Hi Michael. Thanks for the reply but I need a solution that uses Ripchord and LibreArp, since all my patterns are already created in LibreArp. I don't get this issue when using Unify by Pluginguru or Tracktion Waveform Pro but much prefer the mulab interface, as you can customize it like you want.
-
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
-
- KVRist
- Topic Starter
- 47 posts since 30 Oct, 2019
Hi Joe. I have attached an image of my setup. I'm thinking that the Event Input 1 in the INSTRUMENT and DRUM Composers are accepting notes from my MIDI controller, even though I want the route of my MIDI Controller Input to be:
VST MIDI Input ===> Unify Multi ===>
(these are my MIDI Apps Only)
CHORDS Rack ===> a. SEQ/ARP Rack | b. BASS Rack | c. Drum Rack
(there are my INSTRUMENT/DRUM Apps Only)
MIDI from a and b above must go to ===> INSTRUMENT Composer
MIDI from c must go to ===> DRUM Composer
I don't want my MIDI controller to control anything in the INSTRUMENT and DRUM Composer - these Composers must solely be controlled from the MIDI coming from: a. SEQ/ARP Rack | b. BASS Rack | c. Drum Rack
I hope that this makes sense and an easy solution is possible. MuLab is still a bit of a challenge for me but with so much flexibility, it would be impossible to make it very simple, like a conventional DAW, so that is totally fine with me.
VST MIDI Input ===> Unify Multi ===>
(these are my MIDI Apps Only)
CHORDS Rack ===> a. SEQ/ARP Rack | b. BASS Rack | c. Drum Rack
(there are my INSTRUMENT/DRUM Apps Only)
MIDI from a and b above must go to ===> INSTRUMENT Composer
MIDI from c must go to ===> DRUM Composer
I don't want my MIDI controller to control anything in the INSTRUMENT and DRUM Composer - these Composers must solely be controlled from the MIDI coming from: a. SEQ/ARP Rack | b. BASS Rack | c. Drum Rack
I hope that this makes sense and an easy solution is possible. MuLab is still a bit of a challenge for me but with so much flexibility, it would be impossible to make it very simple, like a conventional DAW, so that is totally fine with me.
You do not have the required permissions to view the files attached to this post.
-
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
Unfortunately i can't easily evaluate the MIDI event flow from that picture.
In fact best that you diagnose it yourself, eg by using a Event Monitor module and inserting it at various points and see if events flow as you expect.
What you could also do is to replace the VSTs by MuLab internal modules, as Michael suggested, just to test the signal flow and to diagnose the issue.
In fact best that you diagnose it yourself, eg by using a Event Monitor module and inserting it at various points and see if events flow as you expect.
What you could also do is to replace the VSTs by MuLab internal modules, as Michael suggested, just to test the signal flow and to diagnose the issue.
-
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
Also this: Make sure Project menu -> MIDI Input Channel Routing is setup so that all 16 input channels are mapped to the Project MUX chans 1-16. If not you can do so via the Options in that dialog.