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

[cvi]

thanks Graywolf!

[ENV1]

Restart on key option is still buggy.

Confirmed.

Still, what you did so far isnt bad at all. On the contrary, if one doesnt restart too often in the middle of the sequence its pretty usable already.

Thanks for implementing this.

[guppi]

Swing works great, thank you! I will trigger some drumsets with it now

[graywolf2004]

Restart on key option is still buggy.

Confirmed.
Still, what you did so far isnt bad at all. On the contrary, if one doesnt restart too often in the middle of the sequence its pretty usable already.
Thanks for implementing this.

OK, before the next weekend let's clarify the logic, how "restart on key" should interfere with "input quantize".
Now my idea is:
- with inp.quzntize = none, arp is triggered right when you press 1st key, an goes on while you hold at least 1 key. It won't quantize to the beat, so if you want it to start say on next kick, you have to press it exactly then;
- with inp.quantize = 1 step (say sync = 16th), arp will start on the next 16th note after you press 1st key, so you have to press it a little beforehead;

Novation Nova's arp has 4 input quantization modes which are not all clear to me. But another idea I got there is that with inp.quantize = 1 step in some of that modes it can "forgive" if you press 1st key slightly later (say during first half of 16th note), then it will trigger it anyway, but step 1 will be shorter, thereby step 2 will align to the beat and so on.

[phreaque]

Привет другу

Just wanted to thank you once again for taking huge update & consider to manage the crash of multiple instance.

Just have an idea:

You have a simple arp sequence of 4 "keys : fingers" and holding chords on my controllers, can you make the first key "Key 1 - from Key select matrix" to be transposed in octave?

i.e. whenever I press a Cmin chord, the C note will be octaved down, that will save me from spreading my hand all over the midi controller or using two hands.

It's just like playing with an auto accompaniment "arranger" keyboard...

спасибо большое

[Crackbaby]

Phreaque, there's oct and seminote per step at the bottom of the ui. If that is what you meant ...

[phreaque]

Phreaque, there's oct and seminote per step at the bottom of the ui. If that is what you meant ...

Yeah true, I've just found it & was about to delete my previous post
That dude GrayWolf is a true God-send

[graywolf2004]

You have a simple arp sequence of 4 "keys : fingers" and holding chords on my controllers, can you make the first key "Key 1 - from Key select matrix" to be transposed in octave?

Yes, you can transpose individual steps up/down 1 octave. For better result check that only steps with key 1 are transposed down, and key 1 should be root key of your chord. But you can't configure it like say "transpose all the steps with key 1 down 1 octave, whereever they are", and it's not supposed to be so - it would be too complicated.

But you directed me into one idea. I was thinking how to to bring in some features from arrangers to bluearp withiot ruining usability.
And what I have in mind - it's possible to implement basic chord recognition and add new key select option "root key".
Then, say you press a C-major chord, C-E-G, sort order - by pitch, so your keylist is k1=C, k2=E, k3=G.
When you press inverted chord like G(-1)-C-E, your keylist will be k1=G(-1), k2=C, k2=E.
Then, BlueARP will detect the chord and determine the root key - C in both cases. So, if you set certain steps Key_select to root, it will be C in both cases, while k1\k2\k3 will be different. What do you think? Or maybe it's too complicated? I have to think more of it, will it be useful with real arpeggios...

PS. По-русски можно пообщаться в привате

[phreaque]

A request:

"Order Algorithm" There should be a Pitch detector for lower notes. The inverted version of "by pitch, desc." parameter...

This will help to make something like "Bass inversion" function on Korg Pa arrangers...

Thanks

[Crackbaby]

chord recognition would be the frost of the icing of the cake

[graywolf2004]

Well, anyway all this ideas about chord recognition are quite abstract at this point. More important is to implement patch load\save and to fix existing bugs. Afterwards, if this chord recognition feature will be musically useful and won't complicate GUI too much, I'll likely implement it. What I definitely don't want to do is to load the app with features which are musically useless or too complicated.

[Crackbaby]

Sounds good For the record, i haven't noticed any bugs so far!

[ENV1]

OK, before the next weekend let's clarify the logic, how "restart on key" should interfere with "input quantize".

Retrig on next note probably makes the most sense.

Will give it some more thought...

[bronswerk]

Well, anyway all this ideas about chord recognition are quite abstract at this point. More important is to implement patch load\save and to fix existing bugs. Afterwards, if this chord recognition feature will be musically useful and won't complicate GUI too much, I'll likely implement it. What I definitely don't want to do is to load the app with features which are musically useless or too complicated.

Musically useless? Absolutely not. Too complicated? From a programmer point of view it probably is. Let me explain, I've wrote a program that uses arps and does chord recognition too. The way I implemented it was that the chords used for chord recognition are independent from the chords used for the arps. So the fundamental pattern an arp plays was not affected by the chord input used for the chord recognition part. This is especially useful when multiple arps are playing at the same time. It does work, but programming chord recognition does open up a whole other can of worms, be warned.

[sinkmusic]

Do you have any plan to add various colorschemes (i'm not a huge fan of the blue, i'd be glad to be able to set it to gray for instance ).