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
- 809 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
- 809 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
- 7224 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.)
-
- KVRian
- Topic Starter
- 809 posts since 15 Apr, 2012
Not much actually, want to get back to my iPlug2/CLAP project in this fall. It is yet a lot of quite boring work to do, but the 'proof of the concept' thing is already there. Now only have time to fix some remaining bugs since I want the current version of BlueARP to be stable and polished before I switch to the new one.
-
- KVRian
- Topic Starter
- 809 posts since 15 Apr, 2012
BlueARP v2.8.8c update, mostly GUI fixes
https://omg-instruments.com/wp/?page_id=46
Change log:
1. BugFix. When num. chains set to 1, couldn't switch to chain '---' (no chain) via automation
2. BugFix. When current chain is automated and you switch it, sometimes parts of the GUI disappear, this was to wrong critical section logic.
When reopening the window, it was always there so just a GUI bug. In FL at almost never happened, but quite apparent in BitWig.
Now, hopefully fixed
3. BugFix. VST3 version now reports to the host it is DPI aware. FL didn't care about this, but in BitWig now it bacame crisp on hiRes monitors,
rather than being blurry because of bitmap scaling
4. BugFix for OSX. When editing program or chain name, text appeared 2x bigger on hiRes displays
5. BugFix for OSX. When editing program or chain name and clicking away afterwards, the cursor stayed I-beam
6. Included new skin 'Giulio Quattrocchi GQ STYLE', suggested by KVR thread member
The main thing here is this 'flickering' GUI bug and rare occasions when parts of the GUI disappear. Was due to my wrong and overengineered locking/critical section logic in the code. Now hopefully fixed.
https://omg-instruments.com/wp/?page_id=46
Change log:
1. BugFix. When num. chains set to 1, couldn't switch to chain '---' (no chain) via automation
2. BugFix. When current chain is automated and you switch it, sometimes parts of the GUI disappear, this was to wrong critical section logic.
When reopening the window, it was always there so just a GUI bug. In FL at almost never happened, but quite apparent in BitWig.
Now, hopefully fixed
3. BugFix. VST3 version now reports to the host it is DPI aware. FL didn't care about this, but in BitWig now it bacame crisp on hiRes monitors,
rather than being blurry because of bitmap scaling
4. BugFix for OSX. When editing program or chain name, text appeared 2x bigger on hiRes displays
5. BugFix for OSX. When editing program or chain name and clicking away afterwards, the cursor stayed I-beam
6. Included new skin 'Giulio Quattrocchi GQ STYLE', suggested by KVR thread member
The main thing here is this 'flickering' GUI bug and rare occasions when parts of the GUI disappear. Was due to my wrong and overengineered locking/critical section logic in the code. Now hopefully fixed.
-
- KVRAF
- 2051 posts since 13 May, 2004 from Germany
Thank you very much!