BlueARP VST Arpeggiator development - let's discuss! (Apple M1 ready, 4K)
-
- KVRist
- 355 posts since 10 Mar, 2026
Thanks for keeping BluArp alive Oleg, your hard work is appreciated. Its a plugin that always finds its way on my computer after a fresh install. Cheers.
Beware of the gatekeepers and attack dogs and stay safe.
-
- KVRer
- 6 posts since 9 Mar, 2026
Any chance of also releasing BlueARP as a standalone app? Combined with Linux support it will allow e.g. Raspberry Pi + cheap 1024x600 screen + some kind of midi interface to be used as a small and convenient arp device (EDIT: by the folks for who BlueARP Desktop Module is out of the budget)graywolf2004 wrote: Fri Mar 13, 2026 6:47 am Yep, I only hope that on Linux it won't be as much PITA as on OSX. I'm not a fan of Windows either, but regarding backwards compatibility I have no questions - even Windows 11 can still run 32 bit apps.
Last edited by andywt765 on Mon Mar 23, 2026 1:26 pm, edited 1 time in total.
- KVRian
- Topic Starter
- 805 posts since 15 Apr, 2012
Please respect my time, I can't work with bug reports like this, since I have no time to play the guessing game and test every possible combination. At least you could tell: OSX version, Intel or Silicon, which Logic version. And ideally give some details - whether it crashed of the plugin is not listed. If crashed - OSX gives you crash report which may give me way more clues than just "it doesn't work"
PS. Also there's un-official update earlier in the thread which fixed some crashes on OSX
https://drive.google.com/file/d/1fHu2_1 ... dJ_nOsP6X1
Last edited by graywolf2004 on Sun Mar 22, 2026 5:58 pm, edited 1 time in total.
- KVRian
- Topic Starter
- 805 posts since 15 Apr, 2012
BlueARP update v2.8.7 (+ new firmware for the BlueARP DM)
https://omg-instruments.com/wp/?page_id=46
Change log:
1. GUI now is freely scalable, supporting scales from 50% to 200%, grip the bottom-right border of the app to resize, if you set the non-standard scale (not from the list of pre-defined values like 100%, 125%, 150%, etc.), it will memorize it. The default 'system' setting reads your Windows display scale and follows it. On OSX it keeps 100%, but the app is hiRes aware
2. New parameter 'sample-accurate' (SETTINGS tab), when On, BlueARP will delay it's note output by 1 buffer and add mOffset - note offset in samples within a frame. On by default, but for FL studio it is safe to turn it off, since FL splits the buffer at the measure boundaries
3. New parameter 'clock offset, ms' - offsets song position BlueARP receives from the host by the number of milliseconds. Experimental, use with care. Note that setting negative values will requite offsetting input keys accordingly, otherwise, they will be delayed due to input quantization.
4. Fixed OSX compatibility, this version should work for OSX 10.13 High Sierra and higher (2.8.6 only supports OSX 11+)
5. Fixed some validation issues on OSX with pluginval and auvaltool (AU version only, VST and VST3 was fine).
6. Fixed issue with 'press midi key...' input for midi-key related params (it captured a value with offset, like C#3 instead of C3)
7. Added parameter group names (clumps) for AU MIDI-FX version, for more convenient automation setup in Logic / MainStage.
8. BugFix: dragboxes related to drum and guitar modes didn't show P/B marks (indicating param level - program or bank)
9. Minor GUI fix: right-click menus for drag boxes always have values in ascending order top-down, like -3, -2, -1, 0, 1, 2, 3 (before, the list was inverted if the range had negative values)
10. 'sync' param: re-ordered the list by note length (for the existing projects, values will be re-mapped on load), added '1/3' and '3/4 values
11. 'in. quantize' and 'chain quantize' params: re-ordered the list by note length, also added '3/16' and '1/3' values
12. Guitar mode related parameter 'chuck mode', 'chuck value', 'palm mute', 'palm mute ch.' were changed from program-level to bank-level. This was a hard decision but this way it is more convenient in 99% use cases, you don't need them to be different per-program, in rare cases you do - you can have 2 instances if BlueARP for that. For the older saved projects, conversion routine will take the value from the current program, so, unless you had these settings deliberately different for different programs, your older project will load fine.
13. GATE per step lane now has fine scale (again, for the older projects conversion will take care of remapping to new values). It still has 128 steps in total, but it gives finer adjustments than the previous one.
14. 'Duplicate' function (when right-clicking on the program name) adds ' 2' to the name or increases the number if it ends with a number (to avoid the second program having exact same name)
Many words here, but the main things are:
1. GUI-wise - BlueARP now resizable and by default it will use system dpi, so it shouldn't be small on high resolution displays. If you resize it manually, it will keep this size system-wide
2. TIMING / CLOCK - BlueARP is now sample accurate, adding mOffset in samples to each output note. At least REAPER supports it, I tested. Not that important for FL though, it splits frames at measure boundaries. And the clock offset, yet experimental, but adds offset to BlueARP's internal clock derived from host song position
3. Project format had elevated, so be careful here, projects saved with this one won't load with the earlier version, better back up all your important projects
4. Last but not least - updated the manual
PS. All this stuff is a big 'clean up' and 'tidy up' with my current BlueARP project before I start another big activity of migrating to the current iPlug2, which should enable CLAP support and Linux. So I decided to add some features that were sitting in my ToDo list for quite a while.
Sadly couldn't make an explanation video today, maybe next weekend
Now I added and fixed all the stuff I was going to do for a while, so for the next few months I'm going to concentrate on iPlug2 migration, but this may take longer due to my summer-time activities.
https://omg-instruments.com/wp/?page_id=46
Change log:
1. GUI now is freely scalable, supporting scales from 50% to 200%, grip the bottom-right border of the app to resize, if you set the non-standard scale (not from the list of pre-defined values like 100%, 125%, 150%, etc.), it will memorize it. The default 'system' setting reads your Windows display scale and follows it. On OSX it keeps 100%, but the app is hiRes aware
2. New parameter 'sample-accurate' (SETTINGS tab), when On, BlueARP will delay it's note output by 1 buffer and add mOffset - note offset in samples within a frame. On by default, but for FL studio it is safe to turn it off, since FL splits the buffer at the measure boundaries
3. New parameter 'clock offset, ms' - offsets song position BlueARP receives from the host by the number of milliseconds. Experimental, use with care. Note that setting negative values will requite offsetting input keys accordingly, otherwise, they will be delayed due to input quantization.
4. Fixed OSX compatibility, this version should work for OSX 10.13 High Sierra and higher (2.8.6 only supports OSX 11+)
5. Fixed some validation issues on OSX with pluginval and auvaltool (AU version only, VST and VST3 was fine).
6. Fixed issue with 'press midi key...' input for midi-key related params (it captured a value with offset, like C#3 instead of C3)
7. Added parameter group names (clumps) for AU MIDI-FX version, for more convenient automation setup in Logic / MainStage.
8. BugFix: dragboxes related to drum and guitar modes didn't show P/B marks (indicating param level - program or bank)
9. Minor GUI fix: right-click menus for drag boxes always have values in ascending order top-down, like -3, -2, -1, 0, 1, 2, 3 (before, the list was inverted if the range had negative values)
10. 'sync' param: re-ordered the list by note length (for the existing projects, values will be re-mapped on load), added '1/3' and '3/4 values
11. 'in. quantize' and 'chain quantize' params: re-ordered the list by note length, also added '3/16' and '1/3' values
12. Guitar mode related parameter 'chuck mode', 'chuck value', 'palm mute', 'palm mute ch.' were changed from program-level to bank-level. This was a hard decision but this way it is more convenient in 99% use cases, you don't need them to be different per-program, in rare cases you do - you can have 2 instances if BlueARP for that. For the older saved projects, conversion routine will take the value from the current program, so, unless you had these settings deliberately different for different programs, your older project will load fine.
13. GATE per step lane now has fine scale (again, for the older projects conversion will take care of remapping to new values). It still has 128 steps in total, but it gives finer adjustments than the previous one.
14. 'Duplicate' function (when right-clicking on the program name) adds ' 2' to the name or increases the number if it ends with a number (to avoid the second program having exact same name)
Many words here, but the main things are:
1. GUI-wise - BlueARP now resizable and by default it will use system dpi, so it shouldn't be small on high resolution displays. If you resize it manually, it will keep this size system-wide
2. TIMING / CLOCK - BlueARP is now sample accurate, adding mOffset in samples to each output note. At least REAPER supports it, I tested. Not that important for FL though, it splits frames at measure boundaries. And the clock offset, yet experimental, but adds offset to BlueARP's internal clock derived from host song position
3. Project format had elevated, so be careful here, projects saved with this one won't load with the earlier version, better back up all your important projects
4. Last but not least - updated the manual
PS. All this stuff is a big 'clean up' and 'tidy up' with my current BlueARP project before I start another big activity of migrating to the current iPlug2, which should enable CLAP support and Linux. So I decided to add some features that were sitting in my ToDo list for quite a while.
Sadly couldn't make an explanation video today, maybe next weekend
Now I added and fixed all the stuff I was going to do for a while, so for the next few months I'm going to concentrate on iPlug2 migration, but this may take longer due to my summer-time activities.
Last edited by graywolf2004 on Mon Mar 23, 2026 4:56 pm, edited 6 times in total.
- KVRian
- Topic Starter
- 805 posts since 15 Apr, 2012
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.hamlen wrote: Sat Jan 24, 2026 7:50 pm I love BlueARP and have used it for years, but it lacks one critical feature that I long for every time I use it: delay compensation.
...
- KVRian
- Topic Starter
- 805 posts since 15 Apr, 2012
A video tutorial for the BlueARP v2.8.7 update
Just for fun, this is how I managed to do the sample-precise math correctly, when after 2 hours of trying I realized I can't solve it in my head and have to put it on paper:
Just for fun, this is how I managed to do the sample-precise math correctly, when after 2 hours of trying I realized I can't solve it in my head and have to put it on paper:
You do not have the required permissions to view the files attached to this post.
Last edited by graywolf2004 on Sun Mar 29, 2026 9:52 pm, edited 8 times in total.
-
- KVRist
- 282 posts since 4 Feb, 2015
Oleg, I just have to say it again: You are amazing!
Thanks so much for another update!
Having watched the video to the end, I was a little concerned to learn about your pelvis fracture. It sounds like you've had a very tough few months, so I’m happy to hear that your recovery is making such good progress.
I wish you all the best for the rest of your recovery – keep it up!
Thanks so much for another update!
Having watched the video to the end, I was a little concerned to learn about your pelvis fracture. It sounds like you've had a very tough few months, so I’m happy to hear that your recovery is making such good progress.
I wish you all the best for the rest of your recovery – keep it up!
- KVRian
- Topic Starter
- 805 posts since 15 Apr, 2012
Thanks mate, I hope it will be good now and I didn't waste that time anyway )e-musician wrote: Sun Mar 29, 2026 5:00 pm Oleg, I just have to say it again: You are amazing!
Thanks so much for another update!
Having watched the video to the end, I was a little concerned to learn about your pelvis fracture. It sounds like you've had a very tough few months, so I’m happy to hear that your recovery is making such good progress.
I wish you all the best for the rest of your recovery – keep it up!
- KVRAF
- 7019 posts since 19 Apr, 2002 from Utah
graywolf2004 wrote: Sun Mar 22, 2026 3:30 pm BlueARP update v2.8.7 (+ new firmware for the BlueARP DM)
https://omg-instruments.com/wp/?page_id=46
PS. All this stuff is a big 'clean up' and 'tidy up' with my current BlueARP project before I start another big activity of migrating to the current iPlug2, which should enable CLAP support and Linux. So I decided to add some features that were sitting in my ToDo list for quite a while.
Sadly couldn't make an explanation video today, maybe next weekend...
...
Now I added and fixed all the stuff I was going to do for a while, so for the next few months I'm going to concentrate on iPlug2 migration, but this may take longer due to my summer-time activities.
I'm excitedly waiting for the Linux support.
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.)
-
- KVRist
- 282 posts since 4 Feb, 2015
Hm, I *might* have come across a bug, but I am not sure ...
It is related to the new feature of resizing BlueArp by dragging the bottom right corner of the window.
To reproduce:
1) Open BlueArp; resizing works as expected.
2) Switch to a different skin.
3) Drag-to-resize is no longer possible (it only works via the settings).
Happens in both the VST2 and VST3 versions.
OS: W11
Host: Unify 2
It is related to the new feature of resizing BlueArp by dragging the bottom right corner of the window.
To reproduce:
1) Open BlueArp; resizing works as expected.
2) Switch to a different skin.
3) Drag-to-resize is no longer possible (it only works via the settings).
Happens in both the VST2 and VST3 versions.
OS: W11
Host: Unify 2
- KVRian
- Topic Starter
- 805 posts since 15 Apr, 2012
Yep, there's a minor bug. I already fixed it, but need to check some other things and hope to upload a fix later today or tomorrowe-musician wrote: Fri Apr 03, 2026 3:02 pm Hm, I *might* have come across a bug, but I am not sure ...
It is related to the new feature of resizing BlueArp by dragging the bottom right corner of the window.
...
- KVRian
- Topic Starter
- 805 posts since 15 Apr, 2012
Minor bugfix release BlueARP v2.8.7b
https://omg-instruments.com/wp/?page_id=46
Change log:
1. Minor GUI fix: small mouse offsets for the Gate per step lane.
2. Backward compatibility issue: didn't load .fxp (program) files savled with versions v2.2.4 and earlier
3. Sample-precise timing: improved for noteOff messages
4. Bug fix: after resizing the window manually, it didn't resize it second time
5. Bug fix: when you have multiple instances of BlueARP and resize one (or change skin), other will pick
up that change immediately (or on the next window open)
The main thing GUI-related - if you have several BlueARPs in a project and change the scale for one, others go weird, until you reload the project. Now when you change skin or scale for one BlueARP, others should update right away.
I have a thought - maybe store the selected skin with a project, not as a system-wide setting? Might be useful to have BlueARPs of different colors for different type of tracks (bass, sequence, arp, pads, etc.)
PS. Regarding backwards compatibility - I'm doing by best to keep it, just found my old project from 2015 (Lazerhawk "So close" cover), which was made with BlueARP v2.17, loaded fine, I will keep it to test further versions for backwards compatibility.
https://omg-instruments.com/wp/?page_id=46
Change log:
1. Minor GUI fix: small mouse offsets for the Gate per step lane.
2. Backward compatibility issue: didn't load .fxp (program) files savled with versions v2.2.4 and earlier
3. Sample-precise timing: improved for noteOff messages
4. Bug fix: after resizing the window manually, it didn't resize it second time
5. Bug fix: when you have multiple instances of BlueARP and resize one (or change skin), other will pick
up that change immediately (or on the next window open)
The main thing GUI-related - if you have several BlueARPs in a project and change the scale for one, others go weird, until you reload the project. Now when you change skin or scale for one BlueARP, others should update right away.
I have a thought - maybe store the selected skin with a project, not as a system-wide setting? Might be useful to have BlueARPs of different colors for different type of tracks (bass, sequence, arp, pads, etc.)
PS. Regarding backwards compatibility - I'm doing by best to keep it, just found my old project from 2015 (Lazerhawk "So close" cover), which was made with BlueARP v2.17, loaded fine, I will keep it to test further versions for backwards compatibility.
-
- KVRist
- 282 posts since 4 Feb, 2015
Thanks for the quick fix!
This only seems to be fixed in the VST2 version. In the VST3 version, however, drag-to-resize still only works once.graywolf2004 wrote: Sat Apr 04, 2026 9:11 pm 4. Bug fix: after resizing the window manually, it didn't resize it second time
- KVRian
- Topic Starter
- 805 posts since 15 Apr, 2012
I can't reproduce it in FL, VST3 works as expected. In Unify2 symptoms are the same - you resize, change the skin and then resize doesn't work? Also pls double-check that you have the updated vst3, it should show version 2.8.7b on the top panel.e-musician wrote: Sun Apr 05, 2026 1:37 pm Thanks for the quick fix!![]()
This only seems to be fixed in the VST2 version. In the VST3 version, however, drag-to-resize still only works once.graywolf2004 wrote: Sat Apr 04, 2026 9:11 pm 4. Bug fix: after resizing the window manually, it didn't resize it second time
