By DuckonQuak
Fri Aug 21, 2020 10:51 pm
So I've been using the Force for about 8 months now and its been working really well in my hybrid hardware/software setup. But I've encountered an issue with clips and working with Ableton Live and VST synths.
The short explanation... is that it's like when changing clips on the Force that there is some type of "ALL OFF" message sent across MIDI. Which causes it to cut the audio completely of a playing synth (even if it's just the decaying tail and no actual MIDI note).
The long explanation... So I've got an instance of Analog Lab and an instance of Pigments running on my computer. I have them triggering from individual MIDI tracks from the Force, on their own channels. When the 8bar clips are just looping there is no issue in audio playback. But when I trigger a different clip on the Analog Lab (it's running a Jupiter 8 pad sound), it immediately stops the audio playback from Ableton on that track, causing an audio buffer noise (and spikes the CPU to 50%). Even when hitting a blank clip area on the Force it stops the audio playback.
I've tested this with other soft synths and pad sounds and the same thing happens. I even recorded the midi information into Ableton and triggered the clips to test and it does not cut the audio like it does when using Force clips.
So what information is the Force sending out that I can't see? I've even gone in to check the clips on the MIDI tracks and all it has is the note information (no All notes off or anything like that). I'm at a loss for what to do as it seems like it's not a computer power or buffer issue, which is what I initially thought, but rather a Force sending some MIDI message issue that I have zero control over.
Thanks for any help in advance.
Oh, and just to note, all my MIDI runs through a MOTU Midi Express.
The short explanation... is that it's like when changing clips on the Force that there is some type of "ALL OFF" message sent across MIDI. Which causes it to cut the audio completely of a playing synth (even if it's just the decaying tail and no actual MIDI note).
The long explanation... So I've got an instance of Analog Lab and an instance of Pigments running on my computer. I have them triggering from individual MIDI tracks from the Force, on their own channels. When the 8bar clips are just looping there is no issue in audio playback. But when I trigger a different clip on the Analog Lab (it's running a Jupiter 8 pad sound), it immediately stops the audio playback from Ableton on that track, causing an audio buffer noise (and spikes the CPU to 50%). Even when hitting a blank clip area on the Force it stops the audio playback.
I've tested this with other soft synths and pad sounds and the same thing happens. I even recorded the midi information into Ableton and triggered the clips to test and it does not cut the audio like it does when using Force clips.
So what information is the Force sending out that I can't see? I've even gone in to check the clips on the MIDI tracks and all it has is the note information (no All notes off or anything like that). I'm at a loss for what to do as it seems like it's not a computer power or buffer issue, which is what I initially thought, but rather a Force sending some MIDI message issue that I have zero control over.
Thanks for any help in advance.
Oh, and just to note, all my MIDI runs through a MOTU Midi Express.
Duck on Quak
Akai Force / Roland TR8S / Deepmind 12 / Roli Rise25 / Model D / CAT / WASP / Motu Midi Express / Dell XPS 9570 i7 / Presonus 1824c
Akai Force / Roland TR8S / Deepmind 12 / Roli Rise25 / Model D / CAT / WASP / Motu Midi Express / Dell XPS 9570 i7 / Presonus 1824c