New vstscanner versions

SDK for VST 3 audio plug-in and host development.
Arne Scheffler
Posts: 383
Joined: Mon Jun 20, 2016 7:53 am

New vstscanner versions

Post by Arne Scheffler »

Hi,
there are new versions of the VST scanners used in Cubase 9.

See: viewtopic.php?f=6&t=46#p750

Cheers
Arne

olilarkin
Posts: 31
Joined: Tue Jun 21, 2016 11:49 am

Re: New vstscanner versions

Post by olilarkin »

does Segmentation fault: 11 indicate the objc runtime issue?

As far as I can tell I have done what is suggested in the forum post, but the VST2 scanner still crashes like this

Arne Scheffler
Posts: 383
Joined: Mon Jun 20, 2016 7:53 am

Re: New vstscanner versions

Post by Arne Scheffler »

I need to see the call stack, at best the complete crashlog to tell you this.

Jakob
Posts: 10
Joined: Thu Feb 16, 2017 11:26 am

Re: New vstscanner versions

Post by Jakob »

I'm having a similar issue. So I am building my plugin with base SDK 10.7 and "Implicitly Link Objective-C runtime Library" set to off. Scanning it in macOS 10.12 Sierra works without problems. Scanning it in OS X 10.10 shows this output:

Segmentation Fault: 11

Terminal isn't crashing though, so I guess there's nothing I can do to find out what's happening, is there? Any ideas what I could do to solve this?

Additional infos: Scanning the plugin Krush from Tritik in OS X 10.10 works without issues. Cubase 9 sets my plugin to the blacklist in OS X 10.10, but when I tell Cubase 9 to use it anyway, it works without recognizable issues. It also works in Reaper.

Arne Scheffler
Posts: 383
Joined: Mon Jun 20, 2016 7:53 am

Re: New vstscanner versions

Post by Arne Scheffler »

Without crashlog or call stack it is impossible to tell you the reason.

Jakob
Posts: 10
Joined: Thu Feb 16, 2017 11:26 am

Re: New vstscanner versions

Post by Jakob »

OK, I've isolated the issue:

We're using JUCE. Cubase 9 blacklists our plugins on OS X 10.11 if we're calling juce::MidiInput::getDevices during initialization.

I've tested it with JUCE's current master (v4.3.1), compiled with XCode 8.2.1 on OS X 10.11, and Base SDK set to 10.7.

vst2xscanner gives this error: Segmentation fault: 11

If we avoid the call to juce::MidiInput::getDevices, then our plugins are parsed fine.

Also all is fine on macOS 10.12, even if we call juce::MidiInput::getDevices.

I am wondering though - all seems fine if we manually white-list our plugin, or if we run it in other DAWs. But I guess that indeed the call to MidiInput::getDevices does something wrong, for example writes to a wrong memory location. Interesting though that only vst2xscanner catches this (we're not aware of any crash bugs related to our plugins).

I've also posted to the JUCE forum - https://forum.juce.com/t/midiinput-getd ... se-9/21038 - would be great to solve this.

Arne Scheffler
Posts: 383
Joined: Mon Jun 20, 2016 7:53 am

Re: New vstscanner versions

Post by Arne Scheffler »

Really, to tell you if this is the Objective-C bug I need to see the crash call stack. Do you have a problem to post it ?

Jakob
Posts: 10
Joined: Thu Feb 16, 2017 11:26 am

Re: New vstscanner versions

Post by Jakob »

Arne Scheffler wrote:Really, to tell you if this is the Objective-C bug I need to see the crash call stack. Do you have a problem to post it ?
I am pretty sure it's not related to the Objective-C bug, as I am not linking to Objective-C.

Arne Scheffler
Posts: 383
Joined: Mon Jun 20, 2016 7:53 am

Re: New vstscanner versions

Post by Arne Scheffler »

It may gets linked in indirectly. But if you don't want to post a crashlog, I don't see a way to help you there.

Jakob
Posts: 10
Joined: Thu Feb 16, 2017 11:26 am

Re: New vstscanner versions

Post by Jakob »

Arne Scheffler wrote:It may gets linked in indirectly. But if you don't want to post a crashlog, I don't see a way to help you there.
Ah ok, I see. I'll post a crash log here today or tomorrow.

Post Reply