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

[Dumpster Fire]

Is there any way in BlueARP to force the "algorithm" to quickly detect the order of notes I play in a chord and start the pattern based on the pitch of the notes in the chord as opposed to the order in which I play/input the notes?

For instance, if I play a simple C Major triad but am a bit sloppy in my playing so that I play the E third in the chord ever-so-slightly before the C root note, that BlueARP will wait a few milliseconds and detect that I have played a C Major triad and start the arpeggiation pattern on the C root note rather than the E major third in the chord?

I hope my question makes sense.

[graywolf2004]

Is there any way in BlueARP to force the "algorithm" to quickly detect the order of notes I play in a chord and start the pattern based on the pitch of the notes in the chord as opposed to the order in which I play/input the notes?

For instance, if I play a simple C Major triad but am a bit sloppy in my playing so that I play the E third in the chord ever-so-slightly before the C root note, that BlueARP will wait a few milliseconds and detect that I have played a C Major triad and start the arpeggiation pattern on the C root note rather than the E major third in the chord?

I hope my question makes sense.

Input quantize should help here, try to set it to 1/4 (whole beats). This way BlueARP will 'capture' input keys for a pattern only on the start of each beat, according to input quantize. Of course you need to press keys a bit before-hand, cause it doesn't have a time machine and can't know what will you press next. And order algorithm 'chord, normalized' may also help here if you want your key list to be a normalized chord steps.

[graywolf2004]

I love this arp! Only rivaled by Stepic.
The main issue I'd like to see fixed is the clutter on the main panel. All of the left/right arrows could be hidden until you hover and that alone would clean up the interface A LOT. It's great to have the option but the right click menu on each field helps to get you there quickly so thanks for that

The new skins help by omitting the box around the arrows, but would be great to at least have an option to turn them on or off
An option to show/hide the letter boxes (B,P, G etc) would help clear it up as well.

Keep up the fantastic work!

This is actually a great idea, I like it. Even with this basic GUI library I can implement these arrows to appear only on mouse over. It is even possible to add a flag in skins.ini so it will only work for some skins. I will definitely try it out, thx for this suggestion.

[graywolf2004]

Speaking of fixed patterns and 'dummy note input' requirement. After I 'slept on this', I have several ideas on how to make it
1. Additional parameter 'sequencer mode' in settings tab, I halfway implemented this already.
But the problem here - I don't know where to place in on the GUI for the BlueARP DM. And I think like additional parameter for this is a bit exxessive
2. Additional 'order algorithm' or 'missing keys subst', when selected, input key list will always be some dummy chord
3. Check the pattern, if all steps are fixed, then generate the output even if the input keys are empty
(when fixed and normal steps are mixed, I want it to be idle when there are no input keys, this was the source of confusion before(
4. Add special operation mode 'sequencer', where input filter block will change a bit - no ordering, ranges, or substitution,
instead - params to define up to 5 input keys (like in drum mode), so you can for example set it to pentatonic scale or some chord, and then create even poly patterns on it, with no need for dummy note input

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

[Dumpster Fire]

Is there any way in BlueARP to force the "algorithm" to quickly detect the order of notes I play in a chord and start the pattern based on the pitch of the notes in the chord as opposed to the order in which I play/input the notes?

For instance, if I play a simple C Major triad but am a bit sloppy in my playing so that I play the E third in the chord ever-so-slightly before the C root note, that BlueARP will wait a few milliseconds and detect that I have played a C Major triad and start the arpeggiation pattern on the C root note rather than the E major third in the chord?

I hope my question makes sense.

Input quantize should help here, try to set it to 1/4 (whole beats). This way BlueARP will 'capture' input keys for a pattern only on the start of each beat, according to input quantize. Of course you need to press keys a bit before-hand, cause it doesn't have a time machine and can't know what will you press next. And order algorithm 'chord, normalized' may also help here if you want your key list to be a normalized chord steps.

Thanks for your help. But what about simply playing in a chord without actually engaging my DAW sequencer playback? Almost every hardware synth and synth plugin I own that includes a built in arpeggiator can detect whether I have played a chord and arpeggiate that chord according to the notes in the chord and not the slightly different times that I play notes (unless I have "As Played" selected as the note order of playback)?

For instance, on my Sequential REV2 keyboard, the arpeggiator will play back the chords I input according to the notes in the chord and not the order in which they are played (unless I specify that). Obviously the REV2 doesn't feature a "time machine." (That sure would be nice!) But it somehow waits for input before "deciding" which note order to use as the basis of the arpeggiated pattern.

Can't BlueARP wait a few milliseconds after the first note played to detect that I have actually played a chord?

[robert_p]

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

[robert_p]

P.S. There is also a "safe" option: BlueARP3 with different plugin ID, so we can have both versions installed.

[rasmusklump]

Please no different id's.
That breaks backwards compatibility for everyone.

[robert_p]

Please no different id's.
That breaks backwards compatibility for everyone.

Not if you keep both versions installed. The downside is you won't be able to use newly implemented functions (i.e. drum sequencer) with the old version.

[rasmusklump]

I don't want multiple versions of plugins installed.
We already need two blue arp versions installed. And now a third one?

[robert_p]

I don't want multiple versions of plugins installed.
We already need two blue arp versions installed. And now a third one?

I know this is not a perfect solution - I don't like it either - but look at this scenario:

1. Update the BlueARP
2. Open your DAW and load the project created with v.2.3.9
3. Re-save your project
4. You found that the new version of BlueARP doesn't work as expected (no fixed notes if there is no MIDI input, silent MIDI thru dummy preset etc.)
5. Close your DAW, uninstall new version of BlueARP and install the old one
6. Open your DAW and load the project you just re-saved
7. Your DAW crashes - your project is lost, or (if you update BlueARP again) it won't play as before.

[rasmusklump]

You don't need to tell me how to operate a daw.
I voiced my opinion that I don't want a different ID just as you voiced yours.

[robert_p]

You don't need to tell me how to operate a daw.
I voiced my opinion that I don't want a different ID just as you voiced yours.

I'm not telling you how to operate a DAW - I'm writing about possible consequences of updating BlueARP to the new version. You can ignore my comments if you're a DAW Guru - but someone else might find them useful.

[graywolf2004]

I don't like the idea of different ID's. It's a road to hell. I'll check in FL if it is possible to use different versions of the same plugin, never questioned it actually. If some of you are so dependent on this 'fixed sequence with no input' feature, I can compile an un-official version working that way. Of my suggested options, I still like the most option 4, adding another operation mode, but it will take some time. If I make it, it will only require to adjust your projects one time.

[robert_p]

(...) 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