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

[graywolf2004]

...
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?

Hm... Doesn't look like the expected behaviour, it should pick up projects saved with the older BlueARP versions just fine. Your copied .dll over the old one correctly, so for REAPER it should work instead of the old one.
You used BlueARP v2.3.9, right? I just did a quick test with FL Studio, saved a project with BlueARP v2.3.9 and re-opened it with v2.5.9 from the link above, looks fine.
Can you send me one of your Reaper projects, or make some test one with the older BlueARP and attach it here, if I manage to re-produce it on my PC, I will fix it. Also which version of Reaper?
I'm on Win10, but don't think this is the reason here, more likely something Reaper-specific.

[graywolf2004]

Just did another quick test (thankfully, REAPER demo version allows you to save projects). Installed the current REAPER 7.27 win64 version, created a dummy project with BlueARP v2.3.9, saved it, replaced BlueARP with v2.5.9 from the link above, opened that project, looks fine, all my changes are there. So would be great if you can give me some test REAPER project to reproduce the issue.
PS. Cause I'm doing my best to make it backwards compatible, BlueARP still loads banks saved with version 1.15b3 from 2014, I check this periodically.

[colico]

Hi there, Oleg.
So many thanks for this fantastic arp/seq and your incredible commitment with the project!!

I use REAPER as DAW.
Is it possible to somehow bypass the velocity and gate values per note of BlueArp?
I basically want to control those parameters dynamically (for instance, with a knob in a controller).

Many thanks.

[graywolf2004]

Working on the BlueARP update, GATE STEP lane gets a new mode 'CHANCE', trigger chance per step, will release the BlueARP update in a few days. This is a musical demo:
https://www.youtube.com/watch?v=ukz-F1f6Bd0

[graywolf2004]

Hi there, Oleg.
So many thanks for this fantastic arp/seq and your incredible commitment with the project!!

I use REAPER as DAW.
Is it possible to somehow bypass the velocity and gate values per note of BlueArp?
I basically want to control those parameters dynamically (for instance, with a knob in a controller).

Many thanks.

I have 'dynamics' value for the drum mode already, so I will think of it, makes sense for the arp mode as well. It will basically amplify / attenuate velocity values from the lane, as it works for the drums already. Not in the nearest release, but makes sense. As for the gate, you can already do this by automating 'gate' parameter.

[mabian]

Hi there, Oleg.
So many thanks for this fantastic arp/seq and your incredible commitment with the project!!

I use REAPER as DAW.
Is it possible to somehow bypass the velocity and gate values per note of BlueArp?
I basically want to control those parameters dynamically (for instance, with a knob in a controller).

Many thanks.

About velocity, you can leave BlueArp output fixed velocity, or with its "fixed" velocity patterns.
Then put a velocity changer JSFX after it in the FX Chain and automate the velocity of the JSFX. Done
About gate, I think Oleg already answered. REAPER rules on things like these

- Mario

[colico]

Many thanks to both of you (graywolf2004 and mabian) for your quick answers!!

• Gate.
Perfect. Didn´t know it was that easy.

• Velocity.
Yes, would be great if it could be as easily automated as the gate parameter.
But indeed, it was easy enough to put a velocity plugin (JS: Velocity MIDI Control) between Blue Arp and the synth instrument and control it from there. So, no big deal, really.

Many thanks!
You rock!

[mabian]

Many thanks to both of you (graywolf2004 and mabian) for your quick answers!!

• Gate.
Perfect. Didn´t know it was that easy.

• Velocity.
Yes, would be great if it could be as easily automated as the gate parameter.
But indeed, it was easy enough to put a velocity plugin (JS: Velocity MIDI Control) between Blue Arp and the synth instrument and control it from there. So, no big deal, really.

Many thanks!
You rock!

Glad to help

[graywolf2004]

BlueARP v2.5.9 update, yet Windows only, OSX version will follow shortly
https://omg-instruments.com/wp/?page_id=46

Change log:
1. GATE TIME lane got new mode 'CHANCE'. Defines note trigger chance on a pre-step basis.
For 'Nrm' steps, decreasing the chance will attract the step to 'Off'; for 'Rst' - to 'Nrm',
for 'Tie' - to 'Rst'; for other step types - to 'Off'.
2. Reworked chord recognition engine. Now BlueARP creates 'pressed keys footprint' from input
keys, wrapped into 1 octave and scans it against pre-defined table. This algorithm is much
faster that the previous one and has a lot of potential for flexibility
(i.e. user-defined chord detection tables)
3. BugFix: chord detection algorithm re-scans input keys on each key press\release,
but chord changes are quantized the same way as the keys, for more consistent root note
detection; also for 'chord, normalized' and 'chord, as played' key ordering options.
4. Added new ordering option 'chord norm, low root' - works as 'chord, normalized', but the
detected root will always be lower than all of the pressed keys
5. BugFix: selected page allowing to select non-relevant page numbers (like 16 steps,
pages 1-3 should be disabled)
6. Removed 'min out vel' and 'amplitude' params for the drum mode (amplitude didn't work
anyway, I overcomplicated things a bit), logic for 'dynamics' and 'base value' changed a bit,
check the manual.
7. "probability" param for drum mode renamed into "chance" or "trigger chance"
8. "fixed key" param removed from drum mode, it doesn't work there anyway
9. "dynamics" param in drum mode renamed into "velo amp" (velocity amplify), to make it
consistent the with other modes. The value now shows real amplification factor value
(from 0.00 to 2.00, 1.00 is the default 'neutral' value)
10. Change to 'restart on key' option, the sequence will restart when a key pressed after
all keys were released, even if the gap is shorter than the step time
(if you don't want that, use 'restart on 1st key')
11. Added the ability to play 'fixed key' steps without the note input (version 2.3.9 worked
this way, then it was removed).
To make it work like v2.3.9 in this respect, go to BlueARP.ini
(MENU -> Debug -> Open BlueARP.ini location),
there you should have the line "fixed_key_always_play=0",
change the value to 1 and restart your DAW afterwards.

Video explanation of my pervious performance 'Signal from space', how to use 'CHANCE per step' feature
https://youtu.be/Zy2vLonNQY8

[robert_p]

...
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?

Hm... Doesn't look like the expected behaviour, it should pick up projects saved with the older BlueARP versions just fine. Your copied .dll over the old one correctly, so for REAPER it should work instead of the old one.

I have the same problem with BlueArp in Studio One 7 and MuLab9. Projects saved with ver 2.3.9 or ver.2.5.3 and opened with ver.2.5.9 have the bank reset to default.
---
Studio One 7 - Project saved with ver.2.5.3 (vst2)

v253SO7.jpg

---
Studio One 7 - Project opened with ver.2.5.9 (vst2)

v259SO7.jpg

---
I attached Studio One 7 Test Project - it contains one empty track saved with BlueArp 2.5.3 vst2 .
---

SO7-BlueArp.zip

[graywolf2004]

Thanks a heap, I will check it in a few hours when I'm back home from work. Hope it will help to reproduce the issue.

[graywolf2004]

...
I have the same problem with BlueArp in Studio One 7 and MuLab9. Projects saved with ver 2.3.9 or ver.2.5.3 and opened with ver.2.5.9 have the bank reset to default.
---
Studio One 7 - Project saved with ver.2.5.3 (vst2)
v253SO7.jpg
---
Studio One 7 - Project opened with ver.2.5.9 (vst2)
v259SO7.jpg
---
I attached Studio One 7 Test Project - it contains one empty track saved with BlueArp 2.5.3 vst2 .
---
SO7-BlueArp.zip

Thanks a lot, your projects helped me to nail down the problem pretty quickly. This was kind of unitialized memory error, which randomly pops up only on some hosts / systems
PS. Unfortunatelly now matter how hard you try it is not always possible to find these king of bugs. But hopefully next big release (which I may call BlueARP Christmas update )) will go flawless.

[graywolf2004]

BlueARP v2.6.0 quick fix
Fixing backwards compatibility issues found in v2.5.9 (sometimes won't load BlueARP state and starts with the default bank).
https://omg-instruments.com/wp/?page_id=46

Change log:
1. BugFix: due to memory leak in some DAWs projects saved with the BlueARP versions up to v2.5.3 didn't load
correctly (it started with the default bank)
2. BugFix: some possible project loading problems for VST3 version due to memory leak

Hope the compatibility with the older projects will be fine now

[graywolf2004]

I have the same problem with BlueArp in Studio One 7 and MuLab9. Projects saved with ver 2.3.9 or ver.2.5.3 and opened with ver.2.5.9 have the bank reset to default.
...

Did the previous patch fix your compatibility problem?

PS. A question for all - I'm currently working on some GUI improvements. This is a dark color scheme for the FL Studio, based on the colors of FLEX. Any requests about which another colors do you want BlueARP to have?

BlueARP_Dark.JPG

(this scheme looks to me like it has some gradient, while it doesn't)

The "studio" skins it has embedded for years are good, but recently I added more color params and variables (like corner radiuses, draw outline for boxes or not). Also made box captions a bit smaller, I think is is better now, they don't 'compete' with the values too much, and it is a bit less cluttered.

[rasmusklump]

Looks great.