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

[satYatunes]

Is it normal that when I have changed the mode to drum or guitar I can't change it back to normal arp?
I already had this with the drum mode in the previous version.

But the best arp gets better and better with the time.
Thank you very much.

By clicking the left or right arrow on operation mode?

[rasmusklump]

Either the arrows or the drop down menu.

[satYatunes]

Either the arrows or the drop down menu.

That means I was not the only one. It may be a bug then. Sometimes it does not work, it just goes back and forth between first two options. Right click drop down also stops showing up sometimes. I couldn't replicate it consistently so didn't report it.

System spec - Windows 10, Reaper 7.28. same behaviour in Savihost as well.

[phreaque]

If you want to try DecentSampler (free) then try this sample pack (also free) with it.
https://www.pianobook.co.uk/packs/12-string-acoustic/

I would avoid DS, it is known to cause lots of crashes.

[satYatunes]

I don't use it much, only a handful instruments / sample packs. The 12-string acoustic pack that I shared is really good. Just another option that's all.

[satYatunes]

So far so good, I didin't find any other bugs. So apart from the incorrectly working setting in guitar mode and wrong voicing of some inverted 7th chords (when you play 3 notes instead of 4) it seems fine. So if you play just regular m/Maj chords and 7th chords with all 4 keys pressed (even inverted) it should work fine.

Thanks for the above. I had all triads when I was playing around with it. I just added a 4th note and I don't hear any out of tune voices.

[graywolf2004]

Either the arrows or the drop down menu.

That means I was not the only one. It may be a bug then. Sometimes it does not work, it just goes back and forth between first two options. Right click drop down also stops showing up sometimes. I couldn't replicate it consistently so didn't report it.
System spec - Windows 10, Reaper 7.28. same behaviour in Savihost as well.

I just can't reproduce it... Is it VST2 or VST3 version? VST3 version can be more buggy, cause I test it less and because of the VST3 over-complexity. But I just tried both versions and switching operation mode back and forth doesn't give any issues on my side. Maybe some other clues? Like does it when it plays, or doesn't matter?

[rasmusklump]

In my case vst3 in Cubase 11 on win 10.
I can switch from the normal mode to the drum or guitar mode but not back to the arp mode. I have to reload the plugin. No big deal, I just wanted to see if it was intentional for some technical reason or a bug.

[graywolf2004]

In my case vst3 in Cubase 11 on win 10.
I can switch from the normal mode to the drum or guitar mode but not back to the arp mode. I have to reload the plugin. No big deal, I just wanted to see if it was intentional for some technical reason or a bug.

My advice is to use vst2 if possible, it is more reliable and better tested. AFAIK Steinberg pushes away vst2 and in Cubase if you have both vst2 and vst3, it won't let you use vst2, but with only vst2 installed it should work. I was reviewing my vst3 implementation recently and fixed some bugs there, might be the case. I will try to compare my current build vst3 and the released v270 vst3 to check if I can reproduce the issue with v270 vst3.

[satYatunes]

Either the arrows or the drop down menu.

That means I was not the only one. It may be a bug then. Sometimes it does not work, it just goes back and forth between first two options. Right click drop down also stops showing up sometimes. I couldn't replicate it consistently so didn't report it.
System spec - Windows 10, Reaper 7.28. same behaviour in Savihost as well.

I just can't reproduce it... Is it VST2 or VST3 version? VST3 version can be more buggy, cause I test it less and because of the VST3 over-complexity. But I just tried both versions and switching operation mode back and forth doesn't give any issues on my side. Maybe some other clues? Like does it when it plays, or doesn't matter?

I couldn't recreate it consistently hence didn't report it but it happened a few times and it was annoying. I had to reload the plugin. I am using VST2 only, haven't even installed VST3. Using it in Reaper and FLS.

[graywolf2004]

...
I couldn't recreate it consistently hence didn't report it but it happened a few times and it was annoying. I had to reload the plugin. I am using VST2 only, haven't even installed VST3. Using it in Reaper and FLS.

Ok, if it happens with VST2 as well then probably some 'floating' bug. I can't reproduce it though, but I made a note for myself to check that part of code, maybe I'll see what could go wrong there.

[rasmusklump]

Thanks much for your hard work.

[electro]

My advice is to use vst2 if possible, it is more reliable and better tested.

How many other plugins does this rule apply to?

[phreaque]

Almost all plugins. The VST2 format is much stable & well implemented.

[graywolf2004]

My advice is to use vst2 if possible, it is more reliable and better tested.

How many other plugins does this rule apply to?

I was saying that about BlueARP, but I agree with phreaque - between vst2 and vst3 I'd better use vst2, unless I need some specific features of vst3 (which I can't even imagine at this point)
Number '3' in vst3 doesn't mean that it is better than vst2 in every aspect. In general it is over-complicated and over-engineered (I already commented on that here), especially for simple plugins. VST3 might be better for multi-timbral / multi-layer plugins with complex GUI and patch structure, only in this case the complexity of VST3 might give some benefits. Recently I checked CLAP documentation and examples and I like what I saw so far, so hopefully after a while I will be able to introduce BlueARP as a CLAP plugin and maybe even discontinue VST3 (which is always additional PITA to test)