The Wonders Of Cubase

TomC · 24 May 2010

Dell wrote: When the majority of DAWs will accept Synmaker plug-ins, whereas Cubase won’t it is quite obvious the root of the problem is not Synthmaker.

Let me slightly disagree with you, it's a SynthMaker problem 🙂

There are several reasons:

- Steinberg, as the inventor of the VST interface, handles the protocol (normally) more strictly than other hosts, which may or may not have implemented workarounds for some plug-in issues, which of course are often rendered useless when a new version of the VST API is released.

- With Cubase 4 Steinberg introduced VST 3.0, but still supported VST 2.4. But they dropped support for the (really old) Vst 2.3. SynthMaker is still VST 2.3, so some things work, some thing do not work. Sometimes...

The second point was the reason for me to completely drop ALL my commercial plug-in projects.

I've informed malc back in April 2008 about the problems.

Cheers, Tom

Dell · 25 May 2010

Greetings Tom.

If you notice in the photo below, Cubase 4 (demonstration) will accept VSTs older than version 2.3 🙂

So, it may be something else creating the problem. I am not sure who develops Cubase, however Wavelab is not developed by Cubase although, sharing the Steinberg name.

Bear in mind my 10-year-old version of Wavelab will support every plug-in except VST 3.0 and multiple input plug-ins.

Possibly, we have confirmed something that is not the root of the problem?

TomC · 25 May 2010

Dell wrote: Greetings Tom.

If you notice in the photo below, Cubase 4 (demonstration) will accept VSTs older than version 2.3 🙂

I know. But Accepting is just one thing.

But to quote myself, "so some things work, some thing do not work. Sometimes..."

And, to quote the Cubase 4 FAQ:

Steinberg's knowledge base wrote: "Can I still use my existing plug-ins and instruments? Yes. Existing VST 2.4 plug-ins and instruments are fully compatible with Cubase 4. Any plug-in or instrument older than VST 2.4 must be tested and potentially updated."

Tom

stw · 25 May 2010

TomC wrote: - With Cubase 4 Steinberg introduced VST 3.0, but still supported VST 2.4. But they dropped support for the (really old) Vst 2.3. SynthMaker is still VST 2.3, so some things work, some thing do not work. Sometimes...

The second point was the reason for me to completely drop ALL my commercial plug-in projects.

I've informed malc back in April 2008 about the problems. Tom

I think that is a serious issue for all who are planning to release commercial plugs, which i do myself. Though i read about that in other threads before i start feeling bad about it because it seems nothing would happen. So what did Malc answer? And do you know any details in what works and what could cause trouble? And on the other hand what could be a meaningful excuse for not updating SM to a 2.4 support? 😠

TomC · 25 May 2010

stw wrote: I think that is a serious issue for all who are planning to release commercial plugs, which i do myself. Though i read about that in other threads before i start feeling bad about it because it seems nothing would happen. So what did Malc answer? And do you know any details in what works and what could cause trouble?

The last thing I know of is malc trying to get a NFR copy of Cubase 4 for testing. I have contacted them concerning this but malc has to ask for himself. They won't handle third party requests.

stw wrote: And on the other hand what could be a meaningful excuse for not updating SM to a 2.4 support? 😠

It's a lot of work because there are some serious changes.

Tom

Dell · 25 May 2010

Hi.

Steinberg’s disclaimer is common with all companies selling a product to prevent liability on using a device that is older than the product they are introducing “new to the public.”

I propose we try to find out the reason why some plug-ins, are identified in Cubase whereas others are not that offers a lower version than Steinberg's recomendation. From my experience it is usually something very simple that we tend to take for granted.

Here are a few examples:

Renaming a plug-in

Changing a sub folders name

Having SSE (1 or 2) enabled

Of course, there are others however I have yet to find them.

I am not familiar with Cubase (I would call myself intermediate) with its procedures on refreshing plug-ins. I may need to dig into the registry to find out.

Nevertheless, I really believe if we put our thoughts together, we can find a work around on some of the issues that plagues Cubase.

I would imagine if the developer of Synthmaker has not offered VST 2.4, it must be a reason. If it were not for Synthmaker, I would not be able to make my own designs for I am not familiar with C++. To be honest, if I were looking to go that route, I would abandon VSTs altogether and create hardware products since I am very familiar with audio hardware electronics.

Issues with Cubase appear to be a main problem from Non-Synthmaker developers as well. I never realised how finicky Cubase was until I began evaluating my designs in this platform.

I can’t seem to locate any Nuendo users having issues, which is marketed for those specialise in post-production. Lets gather our thoughts and try to reduce ratio in terms of failure rate on Cubase and, eliminate the negative reputation Synthmaker accumulated in the past years which stems from Cubase users. 🙂

Cheers!

stw · 25 May 2010

TomC wrote: The last thing I know of is malc trying to get a NFR copy of Cubase 4 for testing. I have contacted them concerning this but malc has to ask for himself. They won't handle third party requests.

erm... WHAT??? For testing purposes even a Cubase Essential Version would do the job which costs 140.-€ here in Germany - including VAT. Please tell me that SM or even Malc isn't THAT needy?

stw wrote: And on the other hand what could be a meaningful excuse for not updating SM to a 2.4 support? 😠

TomC wrote: It's a lot of work because there are some serious changes.

On the other hand it would mean SM will die sooner or later because it's commited to VST. And if it's not possible to be on par with the protocol development (even years back) SM will degrade to a toy. 😝

infuzion · 25 May 2010

stw wrote: TomC wrote: - With Cubase 4 Steinberg introduced VST 3.0, but still supported VST 2.4. But they dropped support for the (really old) Vst 2.3. SynthMaker is still VST 2.3, so some things work, some thing do not work. Sometimes... I've informed malc back in April 2008 about the problems.

I think that is a serious issue for all who are planning to release commercial plugs, which i do myself. And on the other hand what could be a meaningful excuse for not updating SM to a 2.4 support? 😠

For my target market (Ableton Live) & I think for VSTs over all, it is more of a disadvantage that SM is lacking OSX support than just VST2.4. I went to a Live tutoral lecture last night: 8 Mac Laptops, 1 PC laptop.

stw · 25 May 2010

infuzion wrote: For my target market (Ableton Live) & I think for VSTs over all, it is more of a disadvantage that SM is lacking OSX support than just VST2.4. I went to a Live tutoral lecture last night: 8 Mac Laptops, 1 PC laptop.

Absolutely! And the Apple mrket will grow faster then before! (Look at me - I bought my first Mac (27" iMac 4x2.8 - what a dream machine 😈 ) after my last G4 350MHz which still is doing my office and internet stuff). But i assume it's way less work to update to VST 2.4 than to OSX. Second one will never happen IMHO because that's definitely not realizable with a one man show.

infuzion · 25 May 2010

stw wrote: infuzion wrote: For my target market (Ableton Live) & I think for VSTs over all, it is more of a disadvantage that SM is lacking OSX support than just VST2.4. I went to a Live tutoral lecture last night: 8 Mac Laptops, 1 PC laptop.

Absolutely! And the Apple mrket will grow faster then before!... But I assume it's way less work to update to VST 2.4 than to OSX. Second one will never happen IMHO because that's definitely not realizable with a one man show.

I understand that SM is really a 0.6 man-show (considering time for customer service, sales, & SM-FL-specific work). But that really is no excuse, with C++ libs that produce VST2.4+ & Mac OSX & LINUX runtimes out there like JUCE, which many other respectable companies already use. Sorry if I seem grumpy, but I'm just tired of excuses; I simply want results. A drag-and-drop platform is supposed to reduce frustrations, not just 1-to-1 exchange some frustrations for others.

attic · 26 May 2010

Sorry if I seem grumpy, but I'm just tired of excuses

You have every right to be, I have been looking at very old request's for support and fixed functionality on this forum that have never been addressed and by the looks of it we cant expect much for updates, at-least not in a timely manner nor in keeping up with the market. I'm not sure what is going on with development on Synthmaker but it needs to be faster and user requests need to be taken seriously. I'm new to SM but my biggest beef is the midi implementation, it is like a car was built without the tires. I use five different keyboards and the results from any of them are all over the place, the implementation is unintuitive at best and completely unworkable at worst. Compared to Synthedit it's a joke ... no good. 😠 I watch Reaper kick out a new upgrade every three weeks that looks like what we might get here in five years. I am going to keep trying for a short period more and if I don't find solutions I will go back to Synthedit and it only costed 50 bucks. 😠 Sorry if I'm grumpy but the parts of Synthmaker that are a joy to use are severely offset by the lack of others. We need a developers Sdk and a way to communicate with outside environments. The midi system needs an upgrade, graphic functions need optimization etc, insert rant your of choice here ..... the 7 year old bugs need squashed. I enjoy this program it could have been a serious development environment.

mshilarious · 5 Jun 2010

I don't know about Cubase compatibility and old standards; I have SX2 and Wavelab 5--SM plugs work fine in SX2, but won't render properly in WL5 (they work fine monitoring). Those two are roughly the same era. I think that problem might have gone away in WL6, but I've been waiting for WL7 to upgrade. Although generally speaking I can't figure out if it's the hosts or SM or both that are the issue 😕 I don't seem to hear about troubles from other hosts . . .

Dell · 5 Jun 2010

mshilarious wrote: I don't know about Cubase compatibility and old standards; I have SX2 and Wavelab 5--SM plugs work fine in SX2, but won't render properly in WL5 (they work fine monitoring). Those two are roughly the same era. I think that problem might have gone away in WL6, but I've been waiting for WL7 to upgrade. Although generally speaking I can't figure out if it's the hosts or SM or both that are the issue 😕 I don't seem to hear about troubles from other hosts . . .

Hi.

Try inserting a preset module in your schematic. I was having the same issues with Wavelab 3 and solved the problem by adding a preset. Wavelab will read almost all VSTs. If Cubase 4/5 offered such a compatibility, there would not be such a long history of Cubase's inability to identify plug-ins.

Cheers!

mshilarious · 5 Jun 2010

Dell wrote: Try inserting a preset module in your schematic. I was having the same issues with Wavelab 3 and solved the problem by adding a preset. Wavelab will read almost all VSTs. If Cubase 4/5 offered such a compatibility, there would not be such a long history of Cubase's inability to identify plug-ins.

Cheers!

Brilliant, that does indeed work. Funny, I never thought to add a preset manager to VSTs, just VSTis, which of course don't work in WL . . . I really only like presets in maybe guitar amp VSTs, otherwise I don't use them.

Is there a sticky on known host compatibility issues? Man, I really need to come here more than twice a year 😊

Dell · 6 Jun 2010

mshilarious wrote: Dell wrote: Try inserting a preset module in your schematic. I was having the same issues with Wavelab 3 and solved the problem by adding a preset. Wavelab will read almost all VSTs. If Cubase 4/5 offered such a compatibility, there would not be such a long history of Cubase's inability to identify plug-ins.

Cheers!

Brilliant, that does indeed work. Funny, I never thought to add a preset manager to VSTs, just VSTis, which of course don't work in WL . . . I really only like presets in maybe guitar amp VSTs, otherwise I don't use them.

Is there a sticky on known host compatibility issues? Man, I really need to come here more than twice a year 😊

I discovered it upon downloading someone's Equaliser OSM. I was determined to find out why my designs would not render in Wavelab and being too old was not a good enough answer for me when other synthmaker plugins from other developers worked.

As far as I've tested, Cubase 4/5 is the only troublesome DAW that will not work properly with my designs. However, I am overcoming those obstacles one step at a time. It is precisely why I feel Synthmaker is not the root of the problem but, something simplistic that we may be overlooking.

Cheers!

infuzion · 6 Jun 2010

Dell wrote: As far as I've tested, Cubase 4/5 is the only troublesome DAW that will not work properly with my designs. However, I am overcoming those obstacles one step at a time. It is precisely why I feel Synthmaker is not the root of the problem but, something simplistic that we may be overlooking.

New versions of Cubase are only VST2.4+ compatible, SM is 2.3 = end of story. If you can get them to work with Cubase, that's swell, but don't get your underwear in a knot about about it. IMHO, your time is better spent learning C++ if 100% Cubase compatibility is important to you.

Mo · 6 Jun 2010

I have now tested my plugins in Cubase 5 very well and after two fixes i find it working just fine in Cubase.

Here is what i found out:

1. If you use arrays in presets then use preset sorting to move the array to be the last of the parameters or automation can be lost at following parameters. Also this can make Cubase stop on load or crash on close.

2. If you use default controls then remove RedrawLimiter module in the preset module. It can be replaced by the Redraw limiter alone, just before the redraw module (I can upload a fixed and optimized knob if people want). This will fix knob automation when GUI is closed.

And remember Cubase recognize plugins by VST ID so do not change that if you don't want it to be another plugin even if the name is the same.

Hope it helps.

mshilarious · 6 Jun 2010

I've been saving my pennies for WL7 (if it ever arrives), and I don't even think there is an upgrade path for SX2 anymore. So I guess I'll never find that problem . . . which gets me to thinking, why is there no paid upgrade for SM? I sure ain't gonna get WL7 for free, and Philippe Goutier runs a similarly brilliant one-man shop himself.

I don't understand all of the features people have asked for, but finishing up my latest plug I still can't believe there is no exponent in code. I mean, there is an ASM routine that does it, but the last time I tried assembly was for Apple ][, and it didn't go too well 25 years ago, so . . . I had to split my code module into two on either side of the power module, and that can't be good for CPU. I don't get it, if the ASM code exists, why can't the SM compiler do that for me? I am not that smart myself 😊

Anybody ever done a poll to see how many people would pay for an upgrade, and how much, and see if the powers that be can be bribed to complete an agreed on feature set? I'll volunteer to be the first . . .

MichaelBenjamin · 6 Jun 2010

the lack of widely used math expressions (pow, exp, sqrt, trigonometrics) is certainly one of the most important if not the most important area that could be improved. untill then you have to split up and waste some cpu. but better than nothing. i say fry the cpu, it is not there to be in idle all the time. idling is boring. cpus like number crunch, and they really dont care if it makes sense or not, only humans do. so give all that cpu efficiency squeezing a rest and churn in some mostly useless sin calculations mixed into the stream at 0.001 to get up the heat and ask yourself the question what you have all these cores for.

infuzion · 6 Jun 2010

Mo wrote: 2. If you use default controls then remove RedrawLimiter module in the preset module. It can be replaced by the Redraw limiter alone, just before the redraw module (I can upload a fixed and optimized knob if people want). This will fix knob automation when GUI is closed.

Nice sluthing Mo! A screenshot should be good. I wonder if my Heartbeat version is better? [old link]

mshilarious wrote: I mean, there is an ASM routine that does it, but the last time I tried assembly was for Apple ][, and it didn't go too well 25 years ago, so . . . I had to split my code module into two on either side of the power module, and that can't be good for CPU.

I can combine them for you... for an hourly rate 😉 But honestly, you're only losing 4-8cycles over what a Code power would do... though with hand optimizing ASM I could save you even more 😉

mshilarious wrote: Anybody ever done a poll to see how many people would pay for an upgrade, and how much, and see if the powers that be can be bribed to complete an agreed on feature set? I'll volunteer to be the first . . .

Do you mean a version 2? We've been waiting for about...3 years for that? I can

Mo · 6 Jun 2010

infuzion wrote: Nice sluthing Mo! A screenshot should be good. I wonder if my Heartbeat version is better? viewtopic.php?f=9&t=9301&start=11

I don't think redraw triggers can be optimized much more than this:

a trigger is only received when the knob image change (see Trigger Quantizer module). The float change module stops redraws when min or max is reached. Then the Redraw Limiter placed like that and not in the preset module to fix it show automation change when GUI is opened after being closed.

MichaelBenjamin · 7 Jun 2010

i dont know whats inside the trigger quantizer, but you should additionally use infuzions limiter to set the maximum refresh rate to something like 15-35 fps. the trigger limiter primitive afaik uses the screen refresh rate (min 60hz) and lets through too many unnecessary redraws.

mshilarious · 7 Jun 2010

infuzion wrote: I can combine them for you... for an hourly rate 😉 But honestly, you're only losing 4-8cycles over what a Code power would do... though with hand optimizing ASM I could save you even more 😉

Well that's what it has devolved to, sadly it seems. SM is such a brilliant tool for the casual programmer, but asking the hobbyists to learn assembly seems much harder than learning C++, which I can't really do either. My bff from school is an excellent programmer, I asked him to help me program MCUs, but when he's making well into six figures it's hard to get his attention 🙁 It's funny, he can't do hardware and I can't do software 😕 What I really need is somebody to write something like SM for MCUs, closest I've seen is Great Cow Basic and that's not really in the same league . . .

Well, I'm at 13% CPU on my aging P4, so I suppose that's not horrible . . . that doesn't include the GUI, which seems to add a lot, and SX2 doesn't seem to score that in its VST performance stat either. Hmmm.

Mo · 7 Jun 2010

MichaelBenjamin wrote: i dont know whats inside the trigger quantizer, but you should additionally use infuzions limiter to set the maximum refresh rate to something like 15-35 fps. the trigger limiter primitive afaik uses the screen refresh rate (min 60hz) and lets through too many unnecessary redraws.

Quantizer looks like this:

First multiply by frames of the knob to get a tick per frame. No unnecessary redraws there though.

Dell · 7 Jun 2010

infuzion wrote: Dell wrote: As far as I've tested, Cubase 4/5 is the only troublesome DAW that will not work properly with my designs. However, I am overcoming those obstacles one step at a time. It is precisely why I feel Synthmaker is not the root of the problem but, something simplistic that we may be overlooking.

New versions of Cubase are only VST2.4+ compatible, SM is 2.3 = end of story. If you can get them to work with Cubase, that's swell, but don't get your underwear in a knot about about it. IMHO, your time is better spent learning C++ if 100% Cubase compatibility is important to you.

Hi.

Possibly things may be different for VSTi’s however, there are lots of effects made in Sythnmaker & Synthedit that are operating in Cubase 4/5 offering VST 2.3. It is precisely the reason I won’t give up if one of my effect plug-ins is malfunctioning in Cubase.

I would imagine being a person that likes to build, repair, and troubleshoot, minimises any frustration when something is not functioning properly. I am not a Cubase user for I don’t make music. However, it is a very popular DAW so it is essential for me to have my effects operating to spec in Cubase along with all the other DAWs offered in the market.

Possibly I will explore C++ in the years to come. Hardware equipment is what I fancy the most due to starting out in the analogue market. So I would pursue building my own hardware designs first before learning C++.

Cheers.

trogluddite · 8 Jun 2010

mshilarious wrote: What I really need is somebody to write something like SM for MCUs, closest I've seen is Great Cow Basic

This is a bit of a shameless plug for my employers... http://www.matrixmultimedia.com/Flowcode3a-X.php Flowcode isn't quite as graphical as SM, but it still uses a flowchart method of building programs - including macro's that you can use as library of building blocks like SMs modules. If you use it with the e-block boards we make, the hardware interfacing is dead simple - there's even a MIDI board in the range. No idea how useful that is to you (I don't work on that product range), but I'll have a word with our new engineer - he got the job after showing the boss a hardware drum machine that he built himself, and he has some VST experience too. Not sure if our MCU's can handle 16bit audio, but they'd work lovely as a control system for an analogue audio path.

mshilarious · 9 Jun 2010

trogluddite wrote: mshilarious wrote: What I really need is somebody to write something like SM for MCUs, closest I've seen is Great Cow Basic

This is a bit of a shameless plug for my employers... . . . Not sure if our MCU's can handle 16bit audio, but they'd work lovely as a control system for an analogue audio path.

That looks very nice, I'm going to check that out for sure 🙂 Don't need any complicated DSP, just analog and ADC control, basic turning things on and off really. I have an ADC circuit I've wanted to do, but the cost of the electromechnicals was going to kill it, thus the need for the MCU.

Jamis · 12 Sept 2010

Hi

I have the same problem with cuabse 5.1

for test purposes ive modified an example synth, and replaced every single knob and selector with MO fixed_knob ( Fixed Animated Knob ), I also indexed values in the preset bank from 0 upwards - as recommended by MO ( Order of automatable VST parameters is a big mess -.- ) - and still no progress.

Actually every single plugin made in synhtmaker (including example-synths from the synthmaker home page) hangs my Cubase 5.1 on project load - especially if there is more than one instance per project.

Does anyone of you have a SM plugin that works under cubase 5? or is my cubase or win7 malfunctioning?

cheers

Jamis · 13 Sept 2010

It seems that only my cubase behaves so unexpectedly (other users seem unaffected by a bad luck I have recently :P)

over and out

Jamis

Andrew J · 13 Sept 2010

Jamis wrote: It seems that only my cubase behaves so unexpectedly (other users seem unaffected by a bad luck I have recently :P)

over and out

Jamis

Give people a bit of time - not everyone has Cubase 5.1. I didn't bother upgrading myself, it just wasn't worth it for me.

stw · 15 Sept 2010

I did some testing and can confirm the crashes. After various trial and error the main troubles seems to come from the preset manager itself. There's no problem with many instances of the example synth if it contains a fresh Preset Manager from the toolbox. As long as it doesn't count more than 2 Presets (Nof Programs). Just by setting an amount of 3 in the properties crashes cubase if more than one instance is present. Maybe someone can do some more testing on this.

I hope this can be fixed. If that should be a confirmed VST preset manager bug that would mean all SM PlugIns suffer from that.

As a workaround one can use Exos Preset Manager which uses only the first Preset as a dummy and does it's own Preset handling. Maybe MyCos worls as well.

Jamis · 15 Sept 2010

Hi, So far I've done extensive tests on several PCs, win XP64, Vista32, Vista64 and Win7 64, with two different audio interfaces on USB and Firewire and some integrated soundcards. Have used Nuendo, Cubase 5.1.0, 5.1.2 built 120 and have confirmed report of crashes also on C 5.1.x built 105 platform. All those things do not really influence the behaviour of SM plugins. Its something deeper.

My findings are, that there is problem with initialisation of several instances of SM plugin, especially if they're one after another in a rack. If you run just one ExampleSynth - it might run. Opening project with 2 instances also works. 3 work sometimes,... but running 4 synths in a row almost always crashes Cubase.

But If you interlace two different plugins, I mean, place ExampleSynth as first, the other plugin (might be a different SM plugin as well), then ExampleSynth, then the other plugin and so on - there fore changing the initialisation process for each (like giving the time for specific preset manager to open?) - you can save, and successfully open the project, with up to 16 instances each... well.. most of the time

Sometimes on opening the crashy project, it might run some of the synths, while killing the other. Attempt to play the other kills all cubase just as closing the crashy project does. Sometimes it hangs clipping audio on one instrument on-project-opening, crashing Cubase totally.

I also found out that ProjectManager might be responsible. When not present at all in ExampleSynth - I can instantiate as many syths as I want, knowing that they will load properly... but that's not the solution.

I have to test loading with 1 preset total - didnt know it might be a partial solution (thanx STW).

Anyway, I am pretty sure it is a problem with initialisation, caused probably by inadequate PresetManager handling.

Thats all I have found out.

We might as well summarise those information and post them in a Bug Report part of the forum.

cheers.. and back to testing..

Jamis

Jamis · 16 Sept 2010

Besides, I have G-media ImpOscar, which is VST 2.0 and it runs flawlessly in Cubase 5. So it's NOT Cubase vst 2.x compatibility issue.

cheers Jamis

TomC · 16 Sept 2010

Jamis wrote: Besides, I have G-media ImpOscar, which is VST 2.0 and it runs flawlessly in Cubase 5. So it's NOT Cubase vst 2.x compatibility issue.

cheers Jamis

It is. Just because one plug-in runs means nothing. You may go back to the beginning of this thread an read it again.

Tom

Jamis · 16 Sept 2010

It is. Just because one plug-in runs means nothing. You may go back to the beginning of this thread an read it again.

Tom

Sorry, I phrased it wrong

It is a compatibility issue, but Steinberg will not care, because some other plugins run well. I's been at least a year since Cubase 5 and half a year since SM 1.1.7 appeared, and we still have a urging compatibility issue.

And I'm not trying to blame anyone. Projects develop - Shit happens

you think this bug can be worked-around from within SM environment ?

Jamis

trogluddite · 16 Sept 2010

Jamis wrote: Steinberg will not care

But OutSim surely should! Some great detective work there people - but it seems that, yet again (much like the issue of SM documentation), licence paying end-users are being left to do the work that ought to be the job of SM's developers. There are some bugfixes/requests (e.g. green timing issues) that would involve massive rewrites of SMs underlying architecture - but this problem would seem to require just one primitive to be fixed, yet it is crucial to the compatability of plugin exports. I pity those people who shelled out the extra cash for a commercial license, the software is effectively unfit-for-purpose for them now - and that will surely cost OutSim a lot of lost revenue and reputation in the long term.

TomC · 16 Sept 2010

Jamis wrote: Steinberg will not care, because some other plugins run well.

Not because some plug-in run. The official statement for VST-developers is (more or less) "VST 2.3 isn't supported anymore. Test your plug-ins, if they run be happy, if not upgrade it to VST 2.4 or 3.0". They just don't care.

Jamis wrote: you think this bug can be worked-around from within SM environment ?

Maybe. The problem is that it's not the only severe problem, automation is the next one. If you REALLY want to find workarounds start with an empty plug-in and add stuff until it doesn't run anymore. First candidates are presets and automation. But it will be a lot of work because you'd have to test it with Cubase 4 and 5, with other plug-ins (SM and others) located before and after your plug-ins, more than one instance of your plug-in in the same VST chain, more than one instance on different tracks, and each of those combinations together with and without your plug-in as send-effect and on the master buss.

IMO not worth the time, especially when you don't know if it will work at all.

Tom

TomC · 16 Sept 2010

trogluddite wrote: I pity those people who shelled out the extra cash for a commercial license, the software is effectively unfit-for-purpose for them now - and that will surely cost OutSim a lot of lost revenue and reputation in the long term.

Yep. I bought the commercial license to sell my plug-ins, and completely stopped development when I found the compatibility problems with Cubase 4.

Bummer...

Tom

nix · 21 Sept 2010

Hello Jamis, Can you test my plug in Cubase5? Orion is reasonably good at hosting SM plugs, I had an issue with automation once though.

http://www.sendspace.com/pro/dl/q1xdee Entrancer VSTi

Don't bother if there's no hope or for whatever reason.

This sucks hmmm

PS- Maybe Kore could load these in Cubase? It costs, but may be a workaround?

Jamis · 25 Sept 2010

Nix wrote: Can you test my plug in Cubase5?

Yep - just tested it. 4 instances run smoothly, 8 however kills cubase on project load.

Nix wrote: PS- Maybe Kore could load these in Cubase? It costs, but may be a workaround?

I have successfully used method suggested by STW (The Wonders Of Cubase). Using one SM preset total - I save all the work to Cubase preset library - which is located in windows user folder (C:\Users\Jamis\AppData\Roaming\Steinberg\Cubase 5\Presets) so I can back it up as well as extract presets to SM .txt file anytime I want - one at a time

Besides Cubase project saves newly created sounds with the project - so i don't have to worry to much on the fly.

Im thinking about releasing my plugin in two different formats - handicapped Cubase version with all presets in xml format, and normal version with embedded SM presets.

Can not think anything better for now. If you have NI KORE try testing SM with it - Im happy to hear any resoults.

Jamis

nix · 25 Sept 2010

Thanks a bundle Jamis, If any of my users have Cubase problems, I will use your method 🙂 I have Kore, will test my stuff. Send me your .dll if you want it tested inside Kore in Orion. Thank you!