BlueARP VST Arpeggiator development - let's discuss! (Apple M1 ready, 4K)
-
- KVRer
- 4 posts since 16 Sep, 2022
Hey Gray Wolf! Was wondering if its possible for the Drum Sequencer to make it disregard the DAW transport playback/recording and only respond to incoming MIDI? Every time I start the transport in my DAW the Drum Sequencer also starts, but would like for the Drum Sequencer to only respond to MIDI input instead. Thanks!
- KVRian
- Topic Starter
- 807 posts since 15 Apr, 2012
Yep, if you change 'restart on' to 'key', it should behave exactly like you say. Also you can adjust input range if needed and 'in quantize', so arp start moment will still be aligned with the grid.rdw456 wrote: Mon Jun 08, 2026 5:13 am Hey Gray Wolf! Was wondering if its possible for the Drum Sequencer to make it disregard the DAW transport playback/recording and only respond to incoming MIDI? Every time I start the transport in my DAW the Drum Sequencer also starts, but would like for the Drum Sequencer to only respond to MIDI input instead. Thanks!
- KVRian
- Topic Starter
- 807 posts since 15 Apr, 2012
BlueARP v2.8.8. update on my website
https://omg-instruments.com/wp/?page_id=46
Mostly a bugfix release, hopefully I fixed some issues with Ableton/VST3, and also bug when switching operation mode.
Change log:
1. BugFix. When changing values of some parameters in Ableton 12 / VST3 BlueARP (like operation mode, transpose oct.),
value jumps to the wrong value right after change.
2. BugFix. Automating polyphonic parameters (like KEY SELECT and OCTAVE lane on polyphonic mode) forces values to mono
(instead of producing weird random values). Fix for both VST2 and VST3
3. Minor GUI issue, in Ableton 12 / VST3, automated values with % showed like '12 % %' (double % sign)
4. BugFix. Switching operation mode from 'arp' to 'guitar' and back didn't work in some DAWs
https://omg-instruments.com/wp/?page_id=46
Mostly a bugfix release, hopefully I fixed some issues with Ableton/VST3, and also bug when switching operation mode.
Change log:
1. BugFix. When changing values of some parameters in Ableton 12 / VST3 BlueARP (like operation mode, transpose oct.),
value jumps to the wrong value right after change.
2. BugFix. Automating polyphonic parameters (like KEY SELECT and OCTAVE lane on polyphonic mode) forces values to mono
(instead of producing weird random values). Fix for both VST2 and VST3
3. Minor GUI issue, in Ableton 12 / VST3, automated values with % showed like '12 % %' (double % sign)
4. BugFix. Switching operation mode from 'arp' to 'guitar' and back didn't work in some DAWs
- KVRAF
- 7114 posts since 19 Apr, 2002 from Utah
How are things looking with the Linux port?graywolf2004 wrote: Tue Jun 23, 2026 7:35 pm BlueARP v2.8.8. update on my website
https://omg-instruments.com/wp/?page_id=46
Mostly a bugfix release, hopefully I fixed some issues with Ableton/VST3, and also bug when switching operation mode.
Change log:
1. BugFix. When changing values of some parameters in Ableton 12 / VST3 BlueARP (like operation mode, transpose oct.),
value jumps to the wrong value right after change.
2. BugFix. Automating polyphonic parameters (like KEY SELECT and OCTAVE lane on polyphonic mode) forces values to mono
(instead of producing weird random values). Fix for both VST2 and VST3
3. Minor GUI issue, in Ableton 12 / VST3, automated values with % showed like '12 % %' (double % sign)
4. BugFix. Switching operation mode from 'arp' to 'guitar' and back didn't work in some DAWs
Vendor‑Dependent Copy Protection: Customers lose. Pirates win.
(Also: I'm Accused of lying about Linux—it boots, runs my pro audio workflow, stays stable, updates--though yearly dismissed as “niche”. Yet I'm the deluded one.)
(Also: I'm Accused of lying about Linux—it boots, runs my pro audio workflow, stays stable, updates--though yearly dismissed as “niche”. Yet I'm the deluded one.)
