BlueARP VST Arpeggiator development - let's discuss! (Apple M1 ready, 4K)
- KVRian
- Topic Starter
- 696 posts since 15 Apr, 2012 from Moscow, Russia
BlueARP plugin v2.5.3 released, along with the firmware update for the BlueARP DM.
Get it here:
https://omg-instruments.com/wp/?page_id=46
Mostly a bugfix release and aligning with BlueARP DM development, but also new cool mode 'latch + sustain' which works nice for guitar picking arpeggios.
Changelog:
1. BugFix: chain variations don't switch reliably for input condition 'input keys' or 'input notes'
2. When 'page lock' is on, changing pattern page doesn't reset the lock as it was (this way it is easier
to edit long pattern page-by-page while keeping 'page lock' on)
3. Pattern page buttons replaced with typical 'dragBox' control, with the added right-click menu to copy/paste
pattern pages (the menu duplicates the one available via MENU button)
4. 'arp state' and 'operation mode' swapped on the GUI to make it consistent with the hardware GUI
5. 'arp. latch' checkbox replaced with dragbox, new value 'latch+sustain' - latches input chord and sustains
generated notes, works great for guitar picking patterns
6. BugFix: crashes when order algo = 'chord, normalized'
7. BugFix: aftertouch condition for chain variations didn't work reliably
8. BugFix: crashes or freezes with order algorithm = 'chord, normalized'
Get it here:
https://omg-instruments.com/wp/?page_id=46
Mostly a bugfix release and aligning with BlueARP DM development, but also new cool mode 'latch + sustain' which works nice for guitar picking arpeggios.
Changelog:
1. BugFix: chain variations don't switch reliably for input condition 'input keys' or 'input notes'
2. When 'page lock' is on, changing pattern page doesn't reset the lock as it was (this way it is easier
to edit long pattern page-by-page while keeping 'page lock' on)
3. Pattern page buttons replaced with typical 'dragBox' control, with the added right-click menu to copy/paste
pattern pages (the menu duplicates the one available via MENU button)
4. 'arp state' and 'operation mode' swapped on the GUI to make it consistent with the hardware GUI
5. 'arp. latch' checkbox replaced with dragbox, new value 'latch+sustain' - latches input chord and sustains
generated notes, works great for guitar picking patterns
6. BugFix: crashes when order algo = 'chord, normalized'
7. BugFix: aftertouch condition for chain variations didn't work reliably
8. BugFix: crashes or freezes with order algorithm = 'chord, normalized'
- KVRian
- Topic Starter
- 696 posts since 15 Apr, 2012 from Moscow, Russia
I still have some stuff in mind and it needs a bit more debugging, but next few months I won't have much time for BlueARP and it is good and stable enough already I believe. It everything goes ok, late 2024 I'm going do some minor improvements and concentrate on making tutorial videos for BlueARP, I have lots of ideas of making content with BlueARP (both plugin and DM)
-
- KVRer
- 20 posts since 30 Jun, 2023
Big thanks for these updates!
I'm about to check it out but my current setup relies a lot on the old version with a load of VST param references etc. Do you know if there'd be likely to be problems running this version and the previous one side by side? (I'm running on Reaper Win10 if that's relevant).
I'm about to check it out but my current setup relies a lot on the old version with a load of VST param references etc. Do you know if there'd be likely to be problems running this version and the previous one side by side? (I'm running on Reaper Win10 if that's relevant).
-
- KVRist
- 223 posts since 4 Feb, 2015
Thanks for the update, Oleg! ![Thumbs Up! :tu:](./images/smilies/icon_thumbsup.gif)
![Thumbs Up! :tu:](./images/smilies/icon_thumbsup.gif)
- KVRian
- 1380 posts since 17 Jul, 2007 from Riversland Valhalla
Thanks for the supportive feedbacksdp6000 wrote: ↑Tue Apr 23, 2024 6:11 pm Big thanks for these updates!
I'm about to check it out but my current setup relies a lot on the old version with a load of VST param references etc. Do you know if there'd be likely to be problems running this version and the previous one side by side? (I'm running on Reaper Win10 if that's relevant).
![Smile :)](./images/smilies/icon_smile.gif)
For me, all previous saved projects & presets are working fine in the new version without a problem (testing in FL Studio, Unify & Live 12).
- KVRian
- Topic Starter
- 696 posts since 15 Apr, 2012 from Moscow, Russia
If I didn't miss anything, if should pick up older projects fine. Regarding arp functionality, nothing changed in the core, except the addition of chain variations. Which should not affect existing projects. There are mostly GUI improvements.sdp6000 wrote: ↑Tue Apr 23, 2024 6:11 pm Big thanks for these updates!
I'm about to check it out but my current setup relies a lot on the old version with a load of VST param references etc. Do you know if there'd be likely to be problems running this version and the previous one side by side? (I'm running on Reaper Win10 if that's relevant).
- KVRist
- 499 posts since 1 Dec, 2021
My setup also relies a lot on the old version and I found the new version doesn't work as expected:graywolf2004 wrote: ↑Fri Apr 26, 2024 10:18 pmIf I didn't miss anything, if should pick up older projects fine. Regarding arp functionality, nothing changed in the core, except the addition of chain variations. Which should not affect existing projects. There are mostly GUI improvements.sdp6000 wrote: ↑Tue Apr 23, 2024 6:11 pm Big thanks for these updates!
I'm about to check it out but my current setup relies a lot on the old version with a load of VST param references etc. Do you know if there'd be likely to be problems running this version and the previous one side by side? (I'm running on Reaper Win10 if that's relevant).
In the old version, switching between 2 programs ("Silent dummy" and "MIDI thru dummy" when a key on my MIDI keyboard is pressed and held) "mutes and resumes" the MIDI note. In the new version when I switch the program to "MIDI thru dummy", the MIDI note doesn't "resume".
Also, the number of velocity steps has been reduced in the new version (no fine adjustments) - this can be a problem when BlueARP is used with MIDI Converter plugins (e.g. Velocity to MIDI CC Converter).
EDIT: I just found that in the new version we still have 128 velocity steps, so it's ok
![Very Happy :D](./images/smilies/icon_biggrin.gif)
-
- KVRist
- 118 posts since 2 Mar, 2016 from Paris France
Hello.
Would there be a way to randomise octaves?
For the moment, I set all 16 steps to random and set each step to a different Octave, but you can still hear some kind of repeating pattern in the Octave change. I would like Octaves to be totally random as well if possible.
Maybe a feature requests for next version? Unless it's already possible of course.
Kind regards,
Jean-Philippe
Would there be a way to randomise octaves?
For the moment, I set all 16 steps to random and set each step to a different Octave, but you can still hear some kind of repeating pattern in the Octave change. I would like Octaves to be totally random as well if possible.
Maybe a feature requests for next version? Unless it's already possible of course.
Kind regards,
Jean-Philippe
- KVRian
- Topic Starter
- 696 posts since 15 Apr, 2012 from Moscow, Russia
Looks like I introduced some bug in 2.5.3, MIDI Thru dummy doesn't work as expected. Can you please check this fixed versionrobert_p wrote: ↑Mon Apr 29, 2024 2:12 amMy setup also relies a lot on the old version and I found the new version doesn't work as expected:graywolf2004 wrote: ↑Fri Apr 26, 2024 10:18 pmIf I didn't miss anything, if should pick up older projects fine. Regarding arp functionality, nothing changed in the core, except the addition of chain variations. Which should not affect existing projects. There are mostly GUI improvements.sdp6000 wrote: ↑Tue Apr 23, 2024 6:11 pm Big thanks for these updates!
I'm about to check it out but my current setup relies a lot on the old version with a load of VST param references etc. Do you know if there'd be likely to be problems running this version and the previous one side by side? (I'm running on Reaper Win10 if that's relevant).
In the old version, switching between 2 programs ("Silent dummy" and "MIDI thru dummy" when a key on my MIDI keyboard is pressed and held) "mutes and resumes" the MIDI note. In the new version when I switch the program to "MIDI thru dummy", the MIDI note doesn't "resume".
Also, the number of velocity steps has been reduced in the new version (no fine adjustments) - this can be a problem when BlueARP is used with MIDI Converter plugins (e.g. Velocity to MIDI CC Converter).
EDIT: I just found that in the new version we still have 128 velocity steps, so it's ok![]()
https://drive.google.com/file/d/1SNQzrH ... DUB4kjlzgX
Regarding veloocity steps - yep, it is only 128 steps now, cause hardly anyone used coarse velocity
- KVRist
- 499 posts since 1 Dec, 2021
Thanks for the update, I checked the fixed version and it works fine now!graywolf2004 wrote: ↑Mon Jul 22, 2024 6:37 pm Looks like I introduced some bug in 2.5.3, MIDI Thru dummy doesn't work as expected. Can you please check this fixed version (...)
-
- KVRer
- 20 posts since 30 Jun, 2023
Just tried out the new version (I was waiting for a fix of the thru notes bug robert_p reported as I use it to mute/unmute sustaining notes).
The additions look great (and thanks for adding the longer bar settings!) but I'm having problems with any patterns that use fixed notes. I can't get them to output any MIDI, all the patterns that are translating incoming notes are working fine but nothing is coming from the fixed note patterns.
The problem occurred with all of the drum patterns that were working ok in the previous version and on a simple new pattern I created with fixed notes. Let me know if I can provide any more info (or if it's likely I'm missing anything obvious that might have changed).
Apart from that the new version seems to be working well with my existing crazy parameter mapping/control setup. The only thing that needed tweaking were the VST parameter values for the slower sync settings (obviously changed to fit the handy new ones in!) but that's a quick fix![Smile :)](./images/smilies/icon_smile.gif)
The additions look great (and thanks for adding the longer bar settings!) but I'm having problems with any patterns that use fixed notes. I can't get them to output any MIDI, all the patterns that are translating incoming notes are working fine but nothing is coming from the fixed note patterns.
The problem occurred with all of the drum patterns that were working ok in the previous version and on a simple new pattern I created with fixed notes. Let me know if I can provide any more info (or if it's likely I'm missing anything obvious that might have changed).
Apart from that the new version seems to be working well with my existing crazy parameter mapping/control setup. The only thing that needed tweaking were the VST parameter values for the slower sync settings (obviously changed to fit the handy new ones in!) but that's a quick fix
![Smile :)](./images/smilies/icon_smile.gif)
- KVRist
- 499 posts since 1 Dec, 2021
Hi, make sure the "Output Note Velocity" is set to "Velocity Lane" - other options won't produce any output for fixed notes.
---
You do not have the required permissions to view the files attached to this post.
-
- KVRer
- 20 posts since 30 Jun, 2023
Thanks for the quick response
It's set to velocity lane already.
Here's a screenshot of one of the patterns that was playing fine before the update.
![Smile :)](./images/smilies/icon_smile.gif)
Here's a screenshot of one of the patterns that was playing fine before the update.
You do not have the required permissions to view the files attached to this post.
-
- KVRer
- 20 posts since 30 Jun, 2023
A bit more info in case it's helpful - I'm using Reaper 7.18 on Windows 11. Tried with the last official v2.53 and the bug fix from this week. Big project with about 30 Bluearp instances, every one is playing fine apart from the drum plugins which are the only ones that use fixed notes. MIDI monitor placed after Bluearp shows no MIDI data.
Copying back the old version of Bluearp to the same project file (saved just before the update) and they all play fine.
EDIT - problem also occurs with a new instance of Bluearp in an empty project. Sending fixed C1 notes on a new pattern doesn't send any MIDI but switching to the Drum mode sends C1 fine.
Copying back the old version of Bluearp to the same project file (saved just before the update) and they all play fine.
EDIT - problem also occurs with a new instance of Bluearp in an empty project. Sending fixed C1 notes on a new pattern doesn't send any MIDI but switching to the Drum mode sends C1 fine.
- KVRist
- 499 posts since 1 Dec, 2021
You're right - I just found that ver. 2.5.3 requires an input note for "fixed key" type, while ver. 2.3.9 generate "fixed notes" when host transport runs (no input note required). I see on your screenshot that the "Input Range Filter" is set to (C -2 / C -2) - changing it to (C -2 / G8) would allow you to play fixed notes by sending any sustained note to the BlueArp input - otherwise, we'll have to wait for another update from the developer.