|
11-20-2017, 02:00 AM
|
#1
|
Human being with feelings
Join Date: Dec 2015
Posts: 331
|
Studio One 3 and VST
My plugin works in almost every host I've tried, AAX/AU/VST2/VST3, Mac/PC. Except Studio One 3 VST/VST3, at least on Mac (Studio One 3 has crippling performance issues on my Win10 VM, can't test; I think the report was VST3 failed there too). If I instantiate VST(2), the plugin works, but if I remove the plugin and save, crash. VST3 works too, but the crash comes immediately when I remove it. AU works fine.
It seems that it's an IPlug issue, because Youlean loudness Meter BETA has exactly the same issues.
Obviously, Studio One 3 is a bit picky in general—it complains about many plugs (from iZotope, Native Instruments...), although it seems to run them fine on a quick check.
Any ideas, comments?
|
|
|
11-20-2017, 03:43 AM
|
#3
|
Human being with feelings
Join Date: Apr 2012
Posts: 279
|
Quote:
Originally Posted by earlevel
My plugin works in almost every host I've tried, AAX/AU/VST2/VST3, Mac/PC. Except Studio One 3 VST/VST3, at least on Mac (Studio One 3 has crippling performance issues on my Win10 VM, can't test; I think the report was VST3 failed there too). If I instantiate VST(2), the plugin works, but if I remove the plugin and save, crash. VST3 works too, but the crash comes immediately when I remove it. AU works fine.
It seems that it's an IPlug issue, because Youlean loudness Meter BETA has exactly the same issues.
Obviously, Studio One 3 is a bit picky in general—it complains about many plugs (from iZotope, Native Instruments...), although it seems to run them fine on a quick check.
Any ideas, comments?
|
Just installed it to see what it does to my current plug.
Got tons of errors with plugs working fine in other hosts. So yes, that proggy seems to be somewhat picky
To my surprise my plug seems to work fine in all formats. At least for some short testing especially your mentioned issues.
Tried only the Mac version.
|
|
|
11-20-2017, 01:00 PM
|
#4
|
Human being with feelings
Join Date: Dec 2015
Posts: 331
|
Quote:
Originally Posted by Youlean
|
Ah, thanks. I knew I had seen that before ("...reporting too many channels..."), but couldn't find it. It doesn't help that the search feature of this forum apparently doesn't like real short search strings (search for posts with "VST"—none found), and that it doesn't observe quoted strings ("Studio One" will find every instance of the words studio and one—a lot of posts unrelated to Studio one). Yes, I tried google search too, but the problem is that there is not way to confine it to this forum, so many Reaper discussions of Studio One and VST.
I should have mentioned that I only support 64-bit, so the symptoms I described aren't for 32-bit plugins.
|
|
|
11-21-2017, 02:06 AM
|
#5
|
Human being with feelings
Join Date: May 2015
Location: Serbia
Posts: 654
|
Quote:
Originally Posted by earlevel
Ah, thanks. I knew I had seen that before ("...reporting too many channels..."), but couldn't find it. It doesn't help that the search feature of this forum apparently doesn't like real short search strings (search for posts with "VST"—none found), and that it doesn't observe quoted strings ("Studio One" will find every instance of the words studio and one—a lot of posts unrelated to Studio one). Yes, I tried google search too, but the problem is that there is not way to confine it to this forum, so many Reaper discussions of Studio One and VST.
I should have mentioned that I only support 64-bit, so the symptoms I described aren't for 32-bit plugins.
|
Indeed, search is terrible here...
Saving problem is probably in the serialize state function...
|
|
|
11-21-2017, 10:51 AM
|
#6
|
Human being with feelings
Join Date: Dec 2015
Posts: 331
|
Quote:
Originally Posted by Youlean
Indeed, search is terrible here...
Saving problem is probably in the serialize state function...
|
Oh, good point...
|
|
|
11-22-2017, 04:35 PM
|
#7
|
Human being with feelings
Join Date: Dec 2015
Posts: 331
|
Quote:
Originally Posted by Youlean
Indeed, search is terrible here...
Saving problem is probably in the serialize state function...
|
Hi, Youlean. OK, didn't have time to follow up then, but could you elaborate?
To be clear, the VST and VST3 crashes occur only in Studio One 3. The crash occurs when I add my plugin to a project, remove it from the project, and save.
Further, I don't override or otherwise use serialize state functions directly. I just use the default behavior. My AAX version supports factory-bundled presets included with the plugin, but for AU/VST/VST3, the user is on his own, relying on the native patch and state saving of the host.
Do you still think it's the serial state function, and do you have a particular reason or knowledge of that problem?
Thanks!
|
|
|
11-22-2017, 05:18 PM
|
#8
|
Human being with feelings
Join Date: May 2015
Location: Serbia
Posts: 654
|
Quote:
Originally Posted by earlevel
Hi, Youlean. OK, didn't have time to follow up then, but could you elaborate?
To be clear, the VST and VST3 crashes occur only in Studio One 3. The crash occurs when I add my plugin to a project, remove it from the project, and save.
Further, I don't override or otherwise use serialize state functions directly. I just use the default behavior. My AAX version supports factory-bundled presets included with the plugin, but for AU/VST/VST3, the user is on his own, relying on the native patch and state saving of the host.
Do you still think it's the serial state function, and do you have a particular reason or knowledge of that problem?
Thanks!
|
You are right, it shouldn't be serialize state function. It look more like plugin was not cleaned properly... First thing to try is to test IPlugEffect when it comes to this, but I guess it will crash too. I have not yet looked at this issue on mac since my macbook is currently on repair, but it should be ready next week to test. Try attaching it XCode and see what it says.
|
|
|
11-22-2017, 05:53 PM
|
#9
|
Human being with feelings
Join Date: May 2015
Location: Serbia
Posts: 654
|
Also if you have not yet done it, you need to update base and lice projects (i think) on mac since it has broken deployment target settings and if you target version other than SDK you will get occasionally some weird crashes on older systems. Look at my fork for that. I also had problem with AU and multichannel so you can look for that too if you need it.
|
|
|
11-22-2017, 07:19 PM
|
#10
|
Human being with feelings
Join Date: Dec 2015
Posts: 331
|
Quote:
Originally Posted by Youlean
Also if you have not yet done it, you need to update base and lice projects (i think) on mac since it has broken deployment target settings and if you target version other than SDK you will get occasionally some weird crashes on older systems. Look at my fork for that. I also had problem with AU and multichannel so you can look for that too if you need it.
|
OK, but... to be clear, your plugin has the same behavior—both V1.0.5 and V1.5.0 beta, from your website. But maybe you know that and have made changes to you IPlug fork, not reflected in those older loudness meter builds?
PS—OK, I guess you were saying earlier you didn't have your Mac right now, and expected it might crash too—buff said...I'll debug it this weekend.
Last edited by earlevel; 11-22-2017 at 08:18 PM.
|
|
|
11-24-2017, 06:08 AM
|
#11
|
Human being with feelings
Join Date: Feb 2011
Posts: 171
|
Studio one since 3.5 hasn't played well with IPlug.
I have quite a bit of bugs open for studio one usually VST2 work fine but VST3 has problems.
Honestly i have an old VST3 sdk so i thought this was the cause, also i still build with Visual Studio 2013 (to make sure XP is still correctly supported, you can't imagine how many customers ask for XP or mac 10.6 compatibility, yesterday i had a complain that one of our plugin doesn't run on PT9)
Oh btw our issues are on windows, i don't remember having them on mac.
I promise i'll dig into it when i find some time (but i have to sync my IPlug branch completely with youlean's first, actually is sort of frankenstein branch i cannot pull from youlean's or oli branch without having major merge issues...)
Saverio
|
|
|
11-25-2017, 03:23 PM
|
#12
|
Human being with feelings
Join Date: Dec 2015
Posts: 331
|
Quote:
Originally Posted by HoRNet
I have quite a bit of bugs open for studio one usually VST2 work fine but VST3 has problems.
|
I see a lot of issues with VST2 on Mac...
Last edited by earlevel; 11-25-2017 at 03:29 PM.
|
|
|
06-28-2018, 03:00 PM
|
#13
|
Human being with feelings
Join Date: Dec 2015
Posts: 331
|
Update: My IPlug VST/VST3 plug-in seems to work fine on Studio One 4. Interestingly, Studio One 3 now works fine too (I suppose a conflicting component was updated by the S1v4 install).
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 07:52 AM.
|