KVR Audio

robert_p · Post by **robert_p** » Sun Apr 12, 2026 9:30 pm

graywolf2004 wrote: Sun Apr 12, 2026 9:17 pm There's v2.8.7g on my website
(...)
This is the tutorial on how to use BlueARP guitar mode in Unify2

Thanks for the update and very useful tutorial!

g1ul10 · Post by **g1ul10** » Mon Apr 13, 2026 1:09 pm

Hi Grey Wolf, I’ve just created a skin for BlueArp that I’d like to share with you. You’re welcome to include it in future versions of the VST if you like.

1UP

Giulio Quattrocchi

Giulio Quattrocchi GQ STYLE SKIN for BlueARP.rar

Giulio Quattrocchi GQ STYLE SKIN for BlueARP.png

graywolf2004 · Post by **graywolf2004** » Sun Apr 19, 2026 4:31 am

g1ul10 wrote: Mon Apr 13, 2026 1:09 pm Hi Grey Wolf, I’ve just created a skin for BlueArp that I’d like to share with you. You’re welcome to include it in future versions of the VST if you like.

Sure, thanks for sharing!

mabian · Post by **mabian** » Sun Apr 19, 2026 8:35 am

Can we consider 2.8.7g stable?

Thanks,
Mario

audiojunkie · Post by **audiojunkie** » Mon Apr 20, 2026 12:13 am

This looks so useful! Are we getting any closer to a Linux version?

digitalboytn · Post by **digitalboytn** » Mon Apr 20, 2026 1:11 am

Thanks for this great arpeggiator...

Really useful and really appreciated

hamlen · Post by **hamlen** » Mon Apr 20, 2026 4:13 am

graywolf2004 wrote: Sun Mar 22, 2026 3:46 pm Just added this thing, it is called 'clock offset', didn't yet do deep testing yet, so please let me know, if this works for you.

Affirmative test results: I just played my first gig using the new clock-offset feature today, and I can confirm that it works exactly as expected (tested on 2.8.7b). Great work! With sample-accuracy turned on and clock-offset adjusted to about +10 or +20 (depending on patch attack speed), my arps sound so much more precise. I'll definitely be using this feature a lot for live performance. Thank you!

Refinement idea for future development: Setting clock offset to +n has the predictable drawback of requiring a live performer to play notes n ms early. An even better implementation could fix this by allowing a different clock offset for the input buffer than the output buffer. With such a feature, setting the input clock offset to +0 and the output clock offset to +20 would interpret incoming midi events as arriving on-time (allowing performers to play normally), but generate output midi events 20 ms before each beat (to compensate for sound attack-time). Setting input-offset to -20 would even grant performers a "forgiveness" factor---notes played within 20 ms after downbeats would be arpeggiated as if they had been played at/before the downbeat, supporting human performers who are ... less perfect than BlueARP.

hebex · Post by **hebex** » Sat Apr 25, 2026 10:04 am

delete

graywolf2004 · Post by **graywolf2004** » Sun Apr 26, 2026 8:51 am

mabian wrote: Sun Apr 19, 2026 8:35 am Can we consider 2.8.7g stable?

I hope so, it has been 2 weeks and I gut just one complaint on YouTube about Ableton 12, but later he replied he figured it out with Chat GPT, but maybe he will give further details here.

graywolf2004 · Post by **graywolf2004** » Sun Apr 26, 2026 9:01 am

audiojunkie wrote: Mon Apr 20, 2026 12:13 am This looks so useful! Are we getting any closer to a Linux version?

Yes, step by step, but still a long way to go. Currently I'm migrating to iPlug2 and I'm gradually rebuilding the GUI, about 30% done now. Hope to finish it this Fall, and then the next step will be to to compile it under Linux. iPlug2 dev says that Linux support is still beta GUI-wise, but I have hopes that it will improve by the time I start it on Linux.

audiojunkie · Post by **audiojunkie** » Sun Apr 26, 2026 1:36 pm

Sounds good! Thank you for the update!

Almondo · Post by **Almondo** » Mon May 04, 2026 10:02 pm

Got a weird bug in BlueARP (VST3). When I mouse scroll/click on Key Select either in the value lane or the editor the selected value jumps around and flickers between values. Using Ableton Live 12. Anyone else seen this?

Edit: Just tried previous versions, same behaviour for all previous versions until 2.5.0, and then the behaviour is reversed (jumps to value below the mouse pointer).

Edit2: Latest VST2 version working, will stick with that for now.

kavvvv · Post by **kavvvv** » Tue May 05, 2026 7:46 am

Can anyone help me to get
scale step working with polyphonic notes please ?

Almondo · Post by **Almondo** » Sun May 10, 2026 11:25 pm

Step Type names are very confusing, wouldn't this make more sense?

'Off' renamed to 'Rest'
'Rest' renamed to 'Tie'
'Tie' renamed to 'Glide'

graywolf2004 · Post by **graywolf2004** » Wed May 27, 2026 8:22 pm

Almondo wrote: Mon May 04, 2026 10:02 pm Got a weird bug in BlueARP (VST3). When I mouse scroll/click on Key Select either in the value lane or the editor the selected value jumps around and flickers between values. Using Ableton Live 12. Anyone else seen this?

Edit: Just tried previous versions, same behaviour for all previous versions until 2.5.0, and then the behaviour is reversed (jumps to value below the mouse pointer).

Edit2: Latest VST2 version working, will stick with that for now.

Thanks for the report, especially for checking both VST2 and VST3. I installed Ableton 12.3.5 on my system and manager to reproduce the error with VST3 version, will look further (no such issue in FL which is my main DAW that's why I overlooked it)
PS. I found the reason, though don't yet know how to fix it. The thing is that after BlueARP VST3 reports changed parameter to the host (calling performEdit), host immediately calls the plugin back with setParamNormalized and there the value is messed up. Something about range conversion. FL Studio doesn't make this setParamNormalized call and there this problem doesn't show up.
Update: I fixed it, just not sure I will post the update this weekend. Anyway, if you have an option to use VST2, I recommend VST2 over VST3 version, VST2 is more reliable because of its simplicity.

BlueARP VST Arpeggiator development - let's discuss! (Apple M1 ready, 4K)