BlueARP VST Arpeggiator development - let's discuss! (OSX MIDI-FX is out)

VST, AU, AAX, etc. plug-in Virtual Instruments discussion
User avatar
KVRian

Topic Starter

616 posts since 15 Apr, 2012 from Moscow, Russia

Post Mon Apr 19, 2021 2:28 am

chk071 wrote:
Mon Apr 19, 2021 2:23 am
I made a video showing the issue. It's nothing fancy really, to reproduce, just create a new project, add an instance of BlueARP, which opens the GUI, or tries to do so. Then you close the window again, re-open it, and then it shows the BlueARP GUI correctly. This happens with every new instance of BlueARP you add, by the way...
Cool, thanks, now I have the clear idea. Can you please check if adding VST2 version causes the same issue? I'd like to know whether it is due to changes in GUI logic in general of something VST3-specific

KVRAF
27905 posts since 11 Apr, 2010 from Germany

Post Mon Apr 19, 2021 3:21 am

graywolf2004 wrote:
Mon Apr 19, 2021 2:28 am
chk071 wrote:
Mon Apr 19, 2021 2:23 am
I made a video showing the issue. It's nothing fancy really, to reproduce, just create a new project, add an instance of BlueARP, which opens the GUI, or tries to do so. Then you close the window again, re-open it, and then it shows the BlueARP GUI correctly. This happens with every new instance of BlueARP you add, by the way...
Cool, thanks, now I have the clear idea. Can you please check if adding VST2 version causes the same issue? I'd like to know whether it is due to changes in GUI logic in general of something VST3-specific
I just checked, and, the VST2 works fine. So, it seems like only the VST3 has that issue.
Plugins and a DAW. On an operating system. Which runs on a computer.

KVRer
19 posts since 21 Jan, 2020

Post Mon Apr 19, 2021 7:59 am

The VST3 immediately crashes Ableton 11 for me upon loading with a "this program has encountered a serious error" message. Windows 10, build 20H2.

VST2 (64 bit) seems to work fine.
Last edited by billybuck on Mon Apr 19, 2021 8:04 am, edited 1 time in total.

KVRian
1224 posts since 13 May, 2004 from Germany

Post Mon Apr 19, 2021 8:02 am

After I inserted the vst3 version in Cubase 11 (windows 10 20h2) the left level meter of that track went in the red and I got an ultra loud buzzing noise. Using the blue cat patchwork in between everything works. Also in patchwork standalone it works.

ree
KVRer
6 posts since 7 Jul, 2014

Post Mon Apr 19, 2021 10:36 am

billybuck wrote:
Mon Apr 19, 2021 7:59 am
The VST3 immediately crashes Ableton 11 for me upon loading with a "this program has encountered a serious error" message. Windows 10, build 20H2.

VST2 (64 bit) seems to work fine.
I have the same issue with Ableton 11 Suite in Windows 10.Crashed with VST3, VST2 64 bit loaded without issue.

KVRer
6 posts since 18 Jul, 2020

Post Mon Apr 19, 2021 4:13 pm

Version 2.3.5 (32 bit vst 2) works now in steinberg nuendo 4 on windows xp pro sp3 32 bits and on windows 10 pro 64 bits. The previous version 2.3.1 did not work. I am glad that you used the other compiler so that it works now. Thank you!

Like you (Graywolf) said on page 122: you ripped off some stuff from VS2013 package and installed an older windows SDK. It is probably working because of that.

User avatar
KVRian

Topic Starter

616 posts since 15 Apr, 2012 from Moscow, Russia

Post Mon Apr 19, 2021 10:26 pm

billybuck wrote:
Mon Apr 19, 2021 7:59 am
The VST3 immediately crashes Ableton 11 for me upon loading with a "this program has encountered a serious error" message. Windows 10, build 20H2.
VST2 (64 bit) seems to work fine.
Can you please make a screenshot of that crash, or save it to txt if possible? I need something like memory offset address inside dll, this will allow me to figure out the exact line of the code where it went wrong.

User avatar
KVRian

Topic Starter

616 posts since 15 Apr, 2012 from Moscow, Russia

Post Mon Apr 19, 2021 10:29 pm

rasmusklump wrote:
Mon Apr 19, 2021 8:02 am
After I inserted the vst3 version in Cubase 11 (windows 10 20h2) the left level meter of that track went in the red and I got an ultra loud buzzing noise. Using the blue cat patchwork in between everything works. Also in patchwork standalone it works.
Something wrong with fake audio outputs probably. I'm not sure if it is technically possible to compile MIDI-only VST3 with no audio outs (seems like $teinberg doesn't much respect MIDI in VST context), but I will try and post this version here, looks like a good idea to me.

KVRist
197 posts since 9 Oct, 2013 from uk

Post Tue Apr 20, 2021 6:00 am

rasmusklump wrote:
Mon Apr 19, 2021 8:02 am
After I inserted the vst3 version in Cubase 11 (windows 10 20h2) the left level meter of that track went in the red and I got an ultra loud buzzing noise.
confirmed +1 (BlueARP v2.3.5)
Win10;i7; 16Gb; GTX750Ti; Cubase Pro v11.0.20; Wavelab Pro v10.0.70; StudioOne v5.2.1; UR44 audio/MIDI; HS80 and Equator D5 monitoring. Komplete 12; Stylus RMX

KVRAF
8394 posts since 16 Aug, 2006

Post Tue Apr 20, 2021 6:38 am

Isn't it amazing how Steiny somehow made VST3 worse than VST2 with respect to MIDI? And yet, they are part of the MIDI 2.0 coalition! VST3 didn't even allow for any kind of official MIDI Learn implementation until a little over a year ago. And yet, people will still swear VST3 is "better."

KVRian
1224 posts since 13 May, 2004 from Germany

Post Tue Apr 20, 2021 8:00 am

Did the vst2 version get a new ID?
My old projects don't find the plugin anymore..

User avatar
KVRian

Topic Starter

616 posts since 15 Apr, 2012 from Moscow, Russia

Post Tue Apr 20, 2021 10:28 pm

rasmusklump wrote:
Tue Apr 20, 2021 8:00 am
Did the vst2 version get a new ID?
My old projects don't find the plugin anymore..
Yes, I changed ID to 'BArp' to make it the same across all versions. FL Studio doesn't care about this, but looks like your DAW does. Which one is it? I don't want to keep separate ID's for different versions, so can you please try - will it work for you if you have both versions together - 2.3.2 for your older orojects and 2.3.5 for newer ones?

KVRian
1224 posts since 13 May, 2004 from Germany

Post Tue Apr 20, 2021 10:57 pm

Cubase. That means Nuendo will also have a problem.
When I reload the plugin the settings are gone.....

KVRian
1224 posts since 13 May, 2004 from Germany

Post Tue Apr 20, 2021 10:57 pm

graywolf2004 wrote:
Tue Apr 20, 2021 10:28 pm
rasmusklump wrote:
Tue Apr 20, 2021 8:00 am
Did the vst2 version get a new ID?
My old projects don't find the plugin anymore..
I don't want to keep separate ID's for different versions, so can you please try - will it work for you if you have both versions together - 2.3.2 for your older orojects and 2.3.5 for newer ones?
I will have to check that. Thanks for the tip.

KVRian
1224 posts since 13 May, 2004 from Germany

Post Tue Apr 20, 2021 11:02 pm

One other question: As there is sadly no Midifx for PC and I don't want to use more than one track (Console 1 user here) I load up the Bluecat Patchwork plugin into a track and inside patchwork the Arp and the Synth. Now I noticed that in this case the Arp is absolutely sloppy as if there was no sync, the temp is correct but within a bar everything is sloppy, slows down and gets quicker again When I insert it directly into Cubase everything is tight. Is this something I have to discuss with the creator of patchwork ?

Return to “Instruments”