with all the open ends and inputs its no wonder that it crashes, there is no signalflow from input to output, the input gets just lost in a dead end after the input amp, this would also fit with your crash info that vstbridge lost connection....


Actually, please don't think that there are open ...

the whole plugin is broken, did you upload the right version? there are many dead ends and inputs are not connected .... its always good to clean up and tighten the schematic before sharing so it is easier for others to see what happens...


Other modules are not finished yet, that's why other ...

If you'd like to upload your plugin and schematic, that causes the problem, we can test and offer better advice. I can test in Reaper 32 bit and 64 bit on Windows 7 for example.

If you don't wish to share your schematic we can at least test the plugin which should help to prove if it's Cubase on ...

Not everything is DSPR's fault though. I have been working with 32 bit plugins and Reaper without problems. Apparently Cubase is less considerate with backward compatiility.

Yes you are right my friend. But the problem is, FS doesn't need to be backward. It just can be an updated technology. That ...

I know its happened ... just copy the .DLL file back into the VST folder [overwrite]. Then launch REAPER ... usually finds it [NEW].

Yes mate, this happens because DSPR can't handle customer care. They are really useless because of the 32 bit support only. They don't even care about it.

Damn I ...

Look s More like a cubase problem.... Did other versions of the VST work? Did you try Them with the 32 bit Version.......

Other 32 bit plugins work (they are not FS made). I have 64 bit version Cubase :I

Everytime I get this errors (because of FS's only 32 bit support); I really regret buying FS ...

Hello,
I had this error from FS made vst fx plugin today.

Does anyone know why it does that?

Best regards...

No. Reaper has a mechanism where each plugin during the checking is actually run and those who don't respond as expected are marked bad and don't make it into the list.

Reasons for not responding correctly are vast - but bit depth is not one of them.

So, what are the possible causes? I know ...

Hello
I had an issue with Reaper. I had to do a little bit of work to get the VST to appear in the Reaper V 5.40 plugin list, but after I cleared the cache and re-scanned it came up.

Is that about being my vst a 32bit plugin?

Best regards.

Thank you so much Adam, that's what I exactly want