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

[aquilyzer]

Found a small bug. Not sure why this happens, but when you’re in pass-thru mute arp mode and then switch to another mode, the arpeggio can sometimes get stuck in mute. I made a short video showing it here:

[e-musician]

Found a small bug. Not sure why this happens, but when you’re in pass-thru mute arp mode and then switch to another mode, the arpeggio can sometimes get stuck in mute. I made a short video showing it here:

What version of Unify are you using?

[aquilyzer]

What version of Unify are you using?

It's Unify 2.00.0: https://www.pluginguru.com/products/unify2/

[e-musician]

What version of Unify are you using?

It's Unify 2.00.0: https://www.pluginguru.com/products/unify2/

Okay. Meanwhile, Unify 2 has been updated to 2.01.3 (as of Jan 30).
Please download the latest version from your account. It *might* be that this solves the issue you have with BlueARP. Not sure, though, but it's worth a try.

[aquilyzer]

Okay. Meanwhile, Unify 2 has been updated to 2.01.3 (as of Jan 30).
Please download the latest version from your account. It *might* be that this solves the issue you have with BlueARP. Not sure, though, but it's worth a try.

Also happens with Spire 1.5. So it’s not Unify related. You just need to switch between the different input range modes during playback till the bug gets triggered. It’s quite easy to reproduce.

[graywolf2004]

Found a small bug. Not sure why this happens, but when you’re in pass-thru mute arp mode and then switch to another mode, the arpeggio can sometimes get stuck in mute. I made a short video
...

Thanks for the video, it always makes things much more clear. I'll check it in a few days, didn't make it to this release, I have my hands full for a few nights with the stuff that comes in the next post. And I tweaked the logic for this new 'pass thru + mute arp' setting so when restart on - key, it mutes the arp and restarts the sequence. Man this feature is so cool. I was playing for at least an hour, you can play so many songs in this space-trancey style (I have NordLead emulation called NodalRed and a supersaw like patch with a good low end and tempo synced delay). I think I'll make a music demo, this is so cool. Thanks for giving me this idea.

[graywolf2004]

BlueARP update v2.8.6
https://omg-instruments.com/wp/?page_id=84
1. 'input range mode' renamed to 'out of range keys' to make it more self explanatory (values are 'truncate', 'pass thru' and 'pass thru + mute arp')
2. Guitar mode: when 'chuck mode' = 'velocity', chuck value <= 63 means that the chuck strumming range it from 0 to chuck value, chuck value >= 64 - from this value to 127. With BlueARP it is better to have low velocity range for chucks, cause with the regular patches it doesn't get as wrong as when you have loud short strums instead of chucks
3. Bugfixes for the Guitar mode regarding chuck mode = velocity, is should stay within normal or chuck velocity zone regardless of velocity amplify and velocity randomization setting.
4. Small change to new input range mode / out of range keys setting. With 'pass thru + mute arp' option, when restart on = 'key', pressing outside-the-range key will also retrigger the arp from step 0.

One of the reasons for this update was that I was fine tuning Guitar mode logic while I designed 2 free sampled guitar instruments for DecentSampler. You can get the libraries here:
https://omg-instruments.com/wp/?page_id=685

And here's the demo video and some explanations:

DecentSampler is super cool, even though it lacks some features I wanted (the biggest one is to modulate sample start time by velocity, which AKAI samplers were doing decades ago), but the overall idea is fantastic - you can build your own sample library, customize the UI and expose the sound controls you want.
I believe now I have a good answer to the question "which guitar to use with BlueARP", at least in the Acoustic Guitar department.

[Cuauhtli]

Awesome. Works well with the Kontakt Sessions guitars (transposing it up an octave) with the normal strums. The chuck thing probably won't work with the session instruments as that stuff is key mapped.

[aquilyzer]

... Man this feature is so cool. I was playing for at least an hour, you can play so many songs in this space-trancey style (I have NordLead emulation called NodalRed and a supersaw like patch with a good low end and tempo synced delay) ...

Yeah, I think it’s super powerful, and it’s also a feature that other arp plugins don’t have. Arp melodies in “easy mode”

And I tweaked the logic for this new 'pass thru + mute arp' setting so when restart on - key, it mutes the arp and restarts the sequence.

Yeah, that already helps to make the arp play more consistently between the melody notes. Not sure if it would still be possible to only restart when an "out of range" key is released. Right now, in the "restart on key" mode with a 16th-note melody, the first note of the 16th-note arp sequence gets skipped. Ideally, the sequence should restart right after releasing the "out of range" key. I can make a video if needed.

[SigmaSynth]

Latest version today. If i do chain variation, fi change to var1, when play note b , and use sustain (pedal) , if i switch back to original variation. Does not work. Sustain keeps hanging.

[graywolf2004]

Latest version today. If i do chain variation, fi change to var1, when play note b , and use sustain (pedal) , if i switch back to original variation. Does not work. Sustain keeps hanging.

First I wanted to ask you for clarifications, but after some playing and guessing game I think I found the exact bug. By default BlueARP links input sustain pedal message to 'arp. latch' parameter and sets it to 'latch' so when you have a chain variation (say velocity-driven), you hit the key hard, it switched to chainVar1 and you hold the pedal, then you release the key and release the pedal, chainVar should switch back to main, but it doesn't. I fixed it, check v2.8.6b, the next post.

[graywolf2004]

...
Yeah, that already helps to make the arp play more consistently between the melody notes. Not sure if it would still be possible to only restart when an "out of range" key is released. Right now, in the "restart on key" mode with a 16th-note melody, the first note of the 16th-note arp sequence gets skipped. Ideally, the sequence should restart right after releasing the "out of range" key. I can make a video if needed.

I think I will keep it the way it is - restarting in the keyOn, not KeyOff, it is more consistent with other logic in BlueARP and sonically more clear, I think. I mean when you hit the left key, it restarts, when you hit the right key, it restarts as well. You can work this around by shifting you right-hand sequence to the right, so whatever step you want after your right-hand input key, will be step 2. I guess you are already doing that.

[graywolf2004]

Update: BlueARP v2.8.6b
https://omg-instruments.com/wp/?page_id=46

This update is mostly about this new feature: 'pass thru + mute arp', initially proposed by aquilyzer. Is was already there in v2.8.6, but I did some more refinements and testing, also check the demo video, I think it is cool and worth a separate tutorial / demo.

Change log:
1. 'input range mode' / 'out of range keys' behavior refinement, for out of range keys octave transposition
('transp. oct' param in OUTPUT FULTER section) doesn't apply, only the semitone one.
Octave transposition works only for inside-the-range keys.
2. Some other minor tweaks to 'out of range keys' = 'pass thru + mute arp' mode, mostly regarding
real time input quantization
3. BugFix. When arp.latch is assigned to sustain pedal message (as by default), you have a chain variation, it fires,
(for example, by velocity), then you release the key, release the sustain, but chain variation doesn't switch back

PS. I'm a bit too frequent with the updates lately, this one has only new things for this 'pass thru + mute arp' mode. So you you're not going to use it, no need to update.

[aquilyzer]

I think I will keep it the way it is - restarting in the keyOn, not KeyOff, it is more consistent with other logic in BlueARP and sonically more clear, I think. I mean when you hit the left key, it restarts, when you hit the right key, it restarts as well. You can work this around by shifting you right-hand sequence to the right, so whatever step you want after your right-hand input key, will be step 2. I guess you are already doing that.

Alright, thanks! It’s definitely awesome that you integrated this feature into BlueArp! Love it!

[Nug Wrangler]

Update: BlueARP v2.8.6b
https://omg-instruments.com/wp/?page_id=46

This update is mostly about this new feature: 'pass thru + mute arp', initially proposed by aquilyzer. Is was already there in v2.8.6, but I did some more refinements and testing, also check the demo video, I think it is cool and worth a separate tutorial / demo.

Change log:
1. 'input range mode' / 'out of range keys' behavior refinement, for out of range keys octave transposition
('transp. oct' param in OUTPUT FULTER section) doesn't apply, only the semitone one.
Octave transposition works only for inside-the-range keys.
2. Some other minor tweaks to 'out of range keys' = 'pass thru + mute arp' mode, mostly regarding
real time input quantization
3. BugFix. When arp.latch is assigned to sustain pedal message (as by default), you have a chain variation, it fires,
(for example, by velocity), then you release the key, release the sustain, but chain variation doesn't switch back

PS. I'm a bit too frequent with the updates lately, this one has only new things for this 'pass thru + mute arp' mode. So you you're not going to use it, no need to update.

This is so cool!