I consider SL as very unreliable and unstable for safe work.
Pls fix the bugs first, before implementing any new features (including my feature requests).
I love SL, but it just scares the hell out of me every time, the program crashes for this or that. Than, I go back to Audacity or Wavelab and they work fine. The stability issues are dominant when using VST3-Plugins.
It can be sais safely, that this is an issue with SL, because the other programs just run fine.
Even if a plugins itself may be in error, the host-application, i. e. SL, should not crash or behave odly afterwards.
Pls make SL as hard as a tank running through a data-minefield.
Since video-upload of size over 4MB is not allowed, here screenshots.
I’ve fixed the VST3 issues each time they were mentioned here. If you have VST3 plugins that make SL crash, please list them here, that’s the only way I can be aware of issues like that and fix them.
That being said, as said previously SL is not a VST-centric application at its core, that’s more a side bonus - if you find a workflow that works better for you with VST, such as with WaveLab or Audacity, it’s probably easier to use VST there ?
Also, I’m not gonna stop implementing feature requests just because there are remaining issues with VST3 - there are as many potential issues that there are VST3 plugin manufacturers, it would freeze all development of SpectraLayers, and honestly I don’t think people use SpectraLayers primarily for its VST3 features
Hi Robin, clear “no”!
The plugins are very useful to use with SL.
If they should not be used, than the interface should not be there at all.
As it is now, I can not even remove the plugin. Even with “none”, the application crashes, as I have tried now. This is somewhat of a showstopper for me.
Oki, here maybe the solution: Rescan for the plugins, than restart.
But I still think, this is somewhat awkward. It might be better not to have a VST3-plugin interface at all, if they are not supposed to get used by the customer. Quality over quantity. This is just my personal opinion on this matter.
Well yes, I agree in principle.
The point is, that the plugins I use, work flawlessly in Audacity or Wavelab, but not in Spectral layers. So, in conclusion, there is something wrong in SL, that does not seem right. May someone proof otherwise.
And isn’t VST made by Steinberg? At least the interface definition should be clear and error proof for the host-application, or not? Who am I to know?
Unfortunately there’s no clear documentation to fully create a VST host from scratch (as opposed to creating a VST plugin)… Which is why it requires time and lots of iterations to reach a state where almost all VST plugins can safely be handled. Audacity and WaveLab have been supporting VST plugins for longer than SL.
There is a discussion every now and then over at the WaveLab forum about plugins that crash in WaveLab exclusively.
WaveLab creator Philippe Goutier says every time that the crashing plugins are not correctly written, that they don’t adhere to VST3 standards.
I don’t know anything about coding but it seems like plugins from the big and well known vendors don’t seem to crash or cause hangups as often as those from the smaller ones.
I have no idea what ”recover” does under the hood, I just know from experience that if I re-launch SL after a crash and choose ”recover” in that dialog box, SL will recover the ’lost’ project and very often I will be able to get almost to the point where SL crashed and continue to work from there.
I believe that when choosing ”recover” SL will search, find and open the last autosaved project file or something like that. I don’t know though at what intervals SL will autosave, if it’s every 5 or 10 minutes.
Oh, and the ”reset” button will reset SL to default settings, like when it is freshly installed, I believe.
OK, so to be clear, you click “Yes” in the Restore Dialog…unless the button has “Recover” syntax on the button on mac…
not in my experience; every time I have clicked “yes” on the Recover Session dialog after a crash, I have had issues
only when I have chosen “Restore” is my job unaffected
EDIT
Sorry, I mean “Reset” and not “Restore”
I do not knowingly use auto-save- I save manually ctrl-s all the time while working and now save a safety version (different filename) after every 10 mins or so…especially after completing any tedious editing
I click ”Yes” in the ”Recover session” dialog box, like I said.
I don’t know how to choose ”Restore” in this dialog box. The dialog box I have been talking about all the time in this and that other thread is the very same as the one shown in Marc’s post above, called ”Recover session”. And it doesn’t have any button saying ”Restore”.
I have not seen any ”Restore” dialog box so I can’t relate to your questions in that matter. It is probably better to address your questions regarding your restore experiences to Robin.
This application of Spectralayers wasn’t really designed to host VST’s, however on the other hand Spectralayers is distributed by Steinberg and Steinberg literally invented the VST’S and maintains the standard (so it’s a “catch 22”). In this scenario (ironically) both parties(@Sunnyman and @Robin_Lobel) are right!
I more-or-so side with and agree with @Sunnyman in the fact that the VST functionality should be deprecated and removed from Spectralayers altogether. I understand that both Steinberg and @Robin_Lobel may want to keep the VST aspect within Spectralayers because they want to upsell Spectralayers as much as possible, but the good honest morally right thing to do is to remove all VST functionality altogether because (as of right now) other VST hosts have a more stable code for VST’S than Spectralayers and other hosts are much more stable for VST’s than Spectralayers.
For Spectralayers to keep VST’s as apart of the application to upsell it as an additional feature (especially when it doesn’t work) is misleading to the consumer and can be considered false advertising, it also gives the notion that users can use VST plugins when in fact they cant and will experience many problems.
The only reason why I believe all VST functionality should be removed altogether from Spectralayers is because that would be the best thing for both the developer(in-terms of running behind every problem and scrambling to patch it up) and all users of Spectralayers. That way nobody or any user in the future can report any issues with VST’s and therefore the developer is free to focus on other important features and doesn’t always have to fix every VST issue not working nor patch it up. Also (over the years) I have noticed some features quietly be deprecated and or removed from Spectralayers and although it is SUBTLE I noticed it, I say that to make the point that if features have been removed/deprecated from Spectralayers before then removing all VST functionality should be no exception and it wouldn’t take away from Spectralayers but add to it (in the fact that the developer no longer has to maintain the VST aspect of Spectralayers and can focus on other important things).
Ohh and BTW (because I know @Robin_Lobel is going to reply and say “you keep saying that VST’s doesn’t work in Spectralayers and yet none of you are telling me which plugins you’re having the problems with nor providing me with examples to reproduce the issue, therefore I automatically deem this topic solved)”. The main issue I experience with VST’s is previewing VST’S with selections (especially small selections and a high FFT size such as 8000 smp).
)
I have no idea what ”recover” does under the hood, I just know from experience that if I re-launch SL after a crash and choose ”recover” in that dialog box, SL will recover the ’lost’ project and very often I will be able to get almost to the point where SL crashed and continue to work from there.