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

[robert_p]

If I make it, it will only require to adjust your projects one time.

It may not be as simple as it sounds - I remember creating a preset for Unify 3 years ago (not sure which version of BlueARP I was using at the time) - and today (after several BlueARP updates) that preset is completely broken (and it's not easy to investigate as the preset contains several instances of BlueARP inside the comboboxes etc.)

[dhemery]

… if I just wanted to tweak the preset patterns, what are the most important parameters to adjust to achieve an evolving effect (over the span of say 4 or 8 bars) that is still loosely recognized as some sort of pattern?

One fun technique is to set the matrix to a length that does not match the length of the bar. For example, if you set the matrix to 5 steps, and each step is a 16th note, then the pattern will not fall on the same place in the bar until after 5 bars. So each of the five bars feels a little different, but clearly the same pattern.

[graywolf2004]

BlueARP v2.5.4, yet only Windows update, will try to compile OSX one as well this weekend
https://omg-instruments.com/wp/?page_id=46

This is a bugfix release only, but I found a lot of minor issues and fixed them. Please be careful and check it with your important projects, I still didn't test all I wanted and since I'm working on a new cool operation mode (which I will reveal soon), I might introduce some new issues. Though, I tested it with a few of my projects and it seems fine. Patch format didn't change, should be compatible with the older projects (except the 'fixed sequence' issue mentioned before)

Change log:
1. BugFix: In steps=1 (quantized thru mode) it was retriggering the note, the bug was introduced in the recent versions
2. BugFix: When switching programs while holding input keys, they should be re-triggered
3. BugFix: When switching between auto/off and auto/thru states, latched keys weren't correctly re-triggered
4. For 'descending' order algorithms, I removed the k1..k5 visual flip in the matrix editor, it was too counter-intuitive. But the value flipping when the algorithm changes is still there, so the pattern will stay the same when you switch from 'ascending' to 'descending' and vice versa
5. GUI minor fix: more accurate value change when mouse-dragging horizontally across the matrix editor
6. BugFix: 'current chain' went above the 'number of chains' value
7. BugFix: 'notes off' button didn't cut the input notes when latch is on
8. Removed 'output note velocity' param from the Drum mode (ARP block), it doesn't work in drum mode anyway
9. Added 'notes off' button in drum mode
10. BugFix: some 'stuck notes' in special mode with steps=0 (simple thru)
11. BugFix: for rootles chords with sort algo = "chord, normalized" root wasn't included into post-filter key list
12. BugFix: KEY SELECT k1..k5 values didn't flip when switching from 'desc' algo to 'chord normalized' or 'chord as played'
13. BugFix: When KEY SELECT = Root and in 'fake playback' (DAW playback stopped), sometimes the arp generated the lowest notes (midi note 0) after all input keys just released
14. BugFix: Input quantize didn't work for chords as designed, now it will show something like 'Am > Am7', meaning that the current chord is Am, but currently detected is Am7, will switch to Am7 on next quantization step

[graywolf2004]

BlueARP v2.5.4, OSX update
https://omg-instruments.com/wp/?page_id=46

Change log is the same, plus fixed one minor issue on Mac - by default mouse wheel on mac scrolls 3 lines at a time, so in BlueARP it also adjusted values by +/-3, changed that to +/-1.

[sdp6000]

Currently I thing p.4 is the most elegant, but also the most labour intensive as well. Which ont to prefer? Maybe some other ideas?

It is important that version 2.5.3 is compatible with projects created with v.2.3.9 (by default, it should play fixed notes when the project is loaded and transport runs). I think, there is no need for changes in hardware version (hardware settings are "project non-dependent"). As for the software - I would place this in "settings" tab:

Play Fixed Note:
- Always (default)
- Input Required
---
Play Fixed Note.jpg

Sorry I've been away and just catching up on this conversation now.

+1 from me on option 1 and robert_p's comment. I appreciate that you need to be very careful about adding too many new elements to the settings page but as this is one of the few changes that can prevent old patterns from sending any MIDI (and requiring significant changes to every DAW track to get fixed note patterns working again) I think it's worth adding globally and avoiding need to change all individual patterns.

Re. the separate plugin IDs, also appreciate this might be a pain to implement. Is there any other 'hacky' workaround that could be used by the few of us users that might get caught by needing to roll back? There are so many features (which I'm grateful for!) that often issues aren't apparent until using a new version for a while, by which time projects have been updated and would need to have all BlueArp instances replaced to be able to load them again.

I'm ok with sticking with 2.3.9 for now as well but will keep an eye out in case this is something you're able to fix without it being too much of a hassle to implement!

[graywolf2004]

Hi, a quick important note for the Mac users. When you install the plugin, you have to copy just the Bluearp.component to the Components folder, not the whole BlueARP_MFX folder. Otherwise, Logic Pro will not see the plug-in.
The included fxb factory bank is not actually needed, it is there from the older versions. I will remove it later. Now it is hard coded into the plugin.
PS. Readme.txt file is a bit inaccurate, I'll correct it later when I'm back from the vacation.

[christianwn]

Thanks for Bluearp, fantastic arp/seq.

I have tested it on linux via Yabridge and Carla plugin host. Yabridge has sync issues, like the beat is not steady. Carla can not send midi out. Host used is Reaper native linux.

It would be fantastic with a native linux version. Clap is the new format that is open source for all platforms.

There are many people who will not ever use windows 11, because of different concerns. And windows 10 is fading out. It is also nice to not be forced to use Win or Mac for music creation. Linux can be optimized for audio way beyond windows or mac if you put in some effort, it is a great platform for audio. The stability compared to windows... I usual have to reinstall windows at least once a year.

If you made a donation button for linux, but let everybody join, from 1€ to 100€, I am sure you would get some donations.

[phreaque]

If you made a donation button for linux, but let everybody join, from 1€ to 100€, I am sure you would get some donations.

Thanks on behalf of Graywolf

The donation page is here

[graywolf2004]

Thanks for Bluearp, fantastic arp/seq.

I have tested it on linux via Yabridge and Carla plugin host. Yabridge has sync issues, like the beat is not steady. Carla can not send midi out. Host used is Reaper native linux.

It would be fantastic with a native linux version. Clap is the new format that is open source for all platforms.

There are many people who will not ever use windows 11, because of different concerns. And windows 10 is fading out. It is also nice to not be forced to use Win or Mac for music creation. Linux can be optimized for audio way beyond windows or mac if you put in some effort, it is a great platform for audio. The stability compared to windows... I usual have to reinstall windows at least once a year.

If you made a donation button for linux, but let everybody join, from 1€ to 100€, I am sure you would get some donations.

I have 'making the Linux version' as a low priority task for a while already, but now it is getting a bit higher since I feel this trend of moving away from Windows. But I can't promise it soon, depends on too many things and too much stuff I have in plans. But somewhere late 2025 or 2026 - this might happen. The main stop factor is that in the framework I use there's no Linux support and I have to do a lot of dirty work myself.

[graywolf2004]

ANNOUNCEMENT
I started a separate Instagram channel for BlueARP project, please subscribe for upcoming short video demos and tutorials.
https://www.instagram.com/omg_instruments/

omg_instruments_qr2.png

[graywolf2004]

(...) I can compile an un-official version working that way.

There's no point in doing that - only a few users will use it and the potential bugs may not be detected or reported. Furthermore, releasing an update for two versions would require more work. I'll stay with ver.2.3.9

Can you please check this one:
https://drive.google.com/file/d/1gR4xdr ... MZ1AfqQ1UK
It is not the whole package, just VST2 & VST3 dlls, replace them.
The main thing is that it has an option to behave like v2.3.9 - playing fixed key sequence when no input keys pressed. To enable this, go to BlueARP.ini (MENU -> Debug -> Open BlueARP.ini location), there you should add line "fixed_key_always_play=1", restart your DAW afterwards.

Code: Select all

[SETTINGS]
skin_index=0
gui_size=0
octave_numbering=0
fixed_key_always_play=1
[PATH]
last_path=D:\_PLUG\BlueARP_FactoryBank\Program1.fxp

By default, it is 0, and it is fine since 99% of the users won't care about it, but hopefully it will help you to migrate from v2.3.9. I'm trying to keep the backwards compatibility, basically it still opens programs\banks saved with v1.15b3 (the latest version made in Delphi, and the earliest one I try to support).

[graywolf2004]

That makes sense, many thanks for testing and confirming.
Having to send notes to activate fixed-note patterns (which don't get passed thru the plugin) won't work with the way I use it in my setup so I'll go back to the previous version and hope that it's something that's changed in a future update. Glad we discovered that before I got too attached to the new features!

Please check the previous post, you seem to have the same issue as robert_p.

[mjolnir]

looks pretty cool i ought to try it.

[glokraw]

In AVLinux distro, with linux Reaper, I've been recording BlueArp playing three instances of Synth1 tonight, no issues I can hear or point to. But I'm not doing anything complex, and might not notice things more demanding users could identify. Thanks Greywolf for a video manual, maybe this winter I can study properly!
Cheers

[sdp6000]

That makes sense, many thanks for testing and confirming.
Having to send notes to activate fixed-note patterns (which don't get passed thru the plugin) won't work with the way I use it in my setup so I'll go back to the previous version and hope that it's something that's changed in a future update. Glad we discovered that before I got too attached to the new features!

Please check the previous post, you seem to have the same issue as robert_p.

Thanks! That seems to work as required on a first test, fixed patterns are playing ok without needing a MIDI input.

One issue that I had was that all instances of BlueArp in my project (Reaper win11) lost their arp programs/presets. Everything was reset to the default program bank. I'd just copied the .dll into the old version's plugin folder so I'm not sure if that's a factor?