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

[graywolf2004]

Thanks! Unfortunately it won't show up in Studio One Pro 7 (latest) VST3 (I don't use VST2). That is, the plugin is listed but I can't use it.

Can you just check vst2, to let me know if this is a vst3 specific issue?

[phankiejankie303]

The guitar strum mode is really great! So much expression there and dynamics. Fantastic work!

I think now I have everything I need to reinvent myself as an American folk singer/songwriter .

[graywolf2004]

The guitar strum mode is really great! So much expression there and dynamics. Fantastic work!
I think now I have everything I need to reinvent myself as an American folk singer/songwriter .

Yep, guitar is a pretty universal thing now, almost like piano keys. Should work fine for various folk stuff I guess. I will also use it to sing along with friends, various pop and folk, but also electric guitar strumming patterns should work well, if you choose the mode with strings 1-3 or 1-4 only.

[vitocorleone123]

Thanks! Unfortunately it won't show up in Studio One Pro 7 (latest) VST3 (I don't use VST2). That is, the plugin is listed but I can't use it.

Can you just check vst2, to let me know if this is a vst3 specific issue?

Sure!

The VST2 loads immediately in S1 Pro 7 and works as expected.

[Uchmania]

please i cant find a way to import the guitar and drum banks.. the downloaded bank files are .fxb extensions but the blurarp is looking for .fxp files....any advise

[satYatunes]

please i cant find a way to import the guitar and drum banks.. the downloaded bank files are .fxb extensions but the blurarp is looking for .fxp files....any advise

Click on Menu > Bank > Load from file (*.fxb)

[Uchmania]

please i cant find a way to import the guitar and drum banks.. the downloaded bank files are .fxb extensions but the blurarp is looking for .fxp files....any advise

Click on Menu > Bank > Load from file (*.fxb)

thanks seen it

[Uchmania]

There is a bug or maybe issue. If i load any of the banks, i lose the banks for the other modes, eg if i load the guitar banks, i lose the arp and drum banks, same thing across board, if i load the drum sequencer bank i lose the arp and guitar strum banks...how do we ensure all the banks are retained??

[satYatunes]

If I am not mistaken that's how it works in almost all plugins. If you load one bank it will replace the previously loaded banks.
I would recommend loading banks in different instances if you want to use drum, guitar and other banks simultaneously. Basically separate tracks.

[graywolf2004]

If I am not mistaken that's how it works in almost all plugins. If you load one bank it will replace the previously loaded banks.
I would recommend loading banks in different instances if you want to use drum, guitar and other banks simultaneously. Basically separate tracks.

Yep, 100% correct. Moreover, changing the operation mode is basically transforming BlueARP into another plugin with a different set of parameters (at lest some will differ), so it has to re-initialize the bank and all the programs for that new operation mode. I already made a note for myself so I will emplasize this in the manual when I update it in a few weeks.

[graywolf2004]

...
Sure!
The VST2 loads immediately in S1 Pro 7 and works as expected.

I tried it in Studio One 7.0.1 on Windows 10 - don't see any issues with VST3. So looks like a nasty bug showing only on some systems. Can you please check one more thing - to help me narrow down the problem. When you load the VST3 version - does it actually work? It might be that there is a problem with the GUI showing up but the plugin itself is working, you will see it if you connect it to the synth and you should hear this rolling 16th notes of the default preset. Also any additional info is welcome - if you see any error messages etc.

[vitocorleone123]

...
Sure!
The VST2 loads immediately in S1 Pro 7 and works as expected.

I tried it in Studio One 7.0.1 on Windows 10 - don't see any issues with VST3. So looks like a nasty bug showing only on some systems. Can you please check one more thing - to help me narrow down the problem. When you load the VST3 version - does it actually work? It might be that there is a problem with the GUI showing up but the plugin itself is working, you will see it if you connect it to the synth and you should hear this rolling 16th notes of the default preset. Also any additional info is welcome - if you see any error messages etc.

Thankfully, reinstalling/copying into the VST3 folder made it work! So no bug here after all. Thanks so much, and apologies for causing some heart burn. Happy Holidays!

[graywolf2004]

...
Sure!
The VST2 loads immediately in S1 Pro 7 and works as expected.

I tried it in Studio One 7.0.1 on Windows 10 - don't see any issues with VST3. So looks like a nasty bug showing only on some systems. Can you please check one more thing - to help me narrow down the problem. When you load the VST3 version - does it actually work? It might be that there is a problem with the GUI showing up but the plugin itself is working, you will see it if you connect it to the synth and you should hear this rolling 16th notes of the default preset. Also any additional info is welcome - if you see any error messages etc.

Thankfully, reinstalling/copying into the VST3 folder made it work! So no bug here after all. Thanks so much, and apologies for causing some heart burn. Happy Holidays!

No worries, I checked VST3-related code, found some minor bugs there and fixed them. Btw I advise to use VST2, since it has better MIDI support. Some features like CC passthrough won't work with VST3, because $teinberg is deliberately fighting against usage of VST for MIDI plugins, and some things are just not possible in VST3. But for a basic arp usage VST3 should work.

[mabian]

...
Sure!
The VST2 loads immediately in S1 Pro 7 and works as expected.

I tried it in Studio One 7.0.1 on Windows 10 - don't see any issues with VST3. So looks like a nasty bug showing only on some systems. Can you please check one more thing - to help me narrow down the problem. When you load the VST3 version - does it actually work? It might be that there is a problem with the GUI showing up but the plugin itself is working, you will see it if you connect it to the synth and you should hear this rolling 16th notes of the default preset. Also any additional info is welcome - if you see any error messages etc.

Thankfully, reinstalling/copying into the VST3 folder made it work! So no bug here after all. Thanks so much, and apologies for causing some heart burn. Happy Holidays!

No worries, I checked VST3-related code, found some minor bugs there and fixed them. Btw I advise to use VST2, since it has better MIDI support. Some features like CC passthrough won't work with VST3, because $teinberg is deliberately fighting against usage of VST for MIDI plugins, and some things are just not possible in VST3. But for a basic arp usage VST3 should work.

I am happy to be using REAPER where VST2 is still a green valley but Cubase is phasing out big-time VST2s... S***ty stuff if you ask me... :\

[Uchmania]

...
Sure!
The VST2 loads immediately in S1 Pro 7 and works as expected.

I tried it in Studio One 7.0.1 on Windows 10 - don't see any issues with VST3. So looks like a nasty bug showing only on some systems. Can you please check one more thing - to help me narrow down the problem. When you load the VST3 version - does it actually work? It might be that there is a problem with the GUI showing up but the plugin itself is working, you will see it if you connect it to the synth and you should hear this rolling 16th notes of the default preset. Also any additional info is welcome - if you see any error messages etc.

Thankfully, reinstalling/copying into the VST3 folder made it work! So no bug here after all. Thanks so much, and apologies for causing some heart burn. Happy Holidays!

No worries, I checked VST3-related code, found some minor bugs there and fixed them. Btw I advise to use VST2, since it has better MIDI support. Some features like CC passthrough won't work with VST3, because $teinberg is deliberately fighting against usage of VST for MIDI plugins, and some things are just not possible in VST3. But for a basic arp usage VST3 should work.

But why is Steinberg doing that?? wont this push midi plugin developers to CLAP format, or they do not want midi plugin development anymore?? makes no sense imo....