VB3 is crashin' on me!

[nl3]

So is there anything that can be done about it, Paolo? I've been thinking about getting VB3 soon for my Receptor

I think this isn't such a so unsolvable issue to Guido ZioKiller from SounFonts.it, but all of solutions have to be tested on a Receptor unit.
I remeber the same as this happened to Zebra2, up to the solution found by the same Urs from U-he/Zebra when working on a Receptor.
I'm not a programmer, only a musician and an advanced user, so my help to ZioKiller is limited to possibly test for possible solutions.
What's really needed is a direct Muse support to ZioKiller, as he requested time ago without any answer...
Anyway VB3 1.1 is perfectly working on Receptor, so if a wonderful hammond is needed, buy VB3 1.1. I personally sold my rockin' Roland Vk7 for using a better Receptor-with-Vb3 1.1
Try to ask ZioKiller if update from 1.1 to 1.2 could be free for Receptor users when 1.2 will be available for Musers, hoping this will be asap.
Paolo.

[ZioKiller]

With a license key for VB3 you can use either version 1.1 (still available for download) or version 1.2, or both at the same time. But VB3 1.1 needs the registry patch for the activation (kind of tricky on a Receptor but possible).

I had a look at the VST SDK Docs regarding the differences between 2.3 and 2.4 but none of them seems to not be covered in my code.

I presets are the cause, like nl2 states, I have a suspect that the Receptor host calls setProgram(0) (tries to recall the default patch settings) before starting the audio engine...

[fedde]

Hi Guido,

Thank you for responding again. I will try VB3 v1.1 on my Receptor. Is there any difference in the usage of patches between v1.1 and v1.2? Is calling SetProgram before starting the audio engine not according the VST specification?

BTW: is any engineer of Muse reading this thread? Any help solving this issue would surely be appreciated!

Fedde

[c3boy]

Yeah it runs fine as single plugs, even when i load up other stuff on other channels, it's when you try save it as the snapshot thinks fall down. Bearing in mind i have 1.7 but not the new remote software, i am not a beta tester for 1.7, muse just installed it when i had the C upgrade at xmas.

[nl3]

Yeah it runs fine as single plugs, even when i load up other stuff on other channels, it's when you try save it as the snapshot thinks fall down. Bearing in mind i have 1.7 but not the new remote software, i am not a beta tester for 1.7, muse just installed it when i had the C upgrade at xmas.

Do you mean in OS1.7 you are able to save a SINGLE with VB3 on the channel slot (ok with OS1.6 and no problem) and load it again as SINGLE and Receptor doesn't crash? (crashing in 1.6)
Paolo

[The Good Doctor]

AS I stated earlier I went back to 1.1 and still have had no crashes. I have Rev C and 1.7 OS (also becuase of an Xmas upgrade). I am using it on s Snaphot bank with no current trouble. Glad to have this but would sure appreciate a 1.2 solution.

The Good Doctor

[ZioKiller]

Question: has anybody ever tried my other plugin GS-201 on a Receptor?
I'm asking this because GS-201 (the latest version) is of type VST 2.4 like VB3 1.2 but it doesn't have any presets, it just uses a small set of default values. So, if a wrong preset management is really the cause of these crashes, GS-201 may give me the answer.

[c3boy]

Yeah it runs fine as single plugs, even when i load up other stuff on other channels, it's when you try save it as the snapshot thinks fall down. Bearing in mind i have 1.7 but not the new remote software, i am not a beta tester for 1.7, muse just installed it when i had the C upgrade at xmas.

Do you mean in OS1.7 you are able to save a SINGLE with VB3 on the channel slot (ok with OS1.6 and no problem) and load it again as SINGLE and Receptor doesn't crash? (crashing in 1.6)
Paolo

You can load it up no probs and select the presets, but when I try and save a Receptor preset single, then load it up again using the receptor single PATCH thats when it crashes. But it works fine when you load the plugin into a single slot, just not when you load a receptor patch using VB3 1.2

So deffo sounds something with the preset setup in Receptor and NOT the actual loading of VB3 1.2

Gary

[c3boy]

Question: has anybody ever tried my other plugin GS-201 on a Receptor?
I'm asking this because GS-201 (the latest version) is of type VST 2.4 like VB3 1.2 but it doesn't have any presets, it just uses a small set of default values. So, if a wrong preset management is really the cause of these crashes, GS-201 may give me the answer.

Ok I installed with no problems latest GS-201 from Soundfonts, I then put it into the channel slot fine, then i created a patch on it then saved that patch as a receptor patch. Closed it then opened it then loaded the receptor patch i had saved and it works fine Guido, no crashing like VB3 1.2

[nl3]

Question: has anybody ever tried my other plugin GS-201 on a Receptor?
I'm asking this because GS-201 (the latest version) is of type VST 2.4 like VB3 1.2 but it doesn't have any presets, it just uses a small set of default values. So, if a wrong preset management is really the cause of these crashes, GS-201 may give me the answer.

Ok I installed with no problems latest GS-201 from Soundfonts, I then put it into the channel slot fine, then i created a patch on it then saved that patch as a receptor patch. Closed it then opened it then loaded the receptor patch i had saved and it works fine Guido, no crashing like VB3 1.2

Hi,
did you save and re-load a receptorized patch in the vsti "domain" or a SINGLE Receptor patch?
VB3 1.2 only crashes when loading a SINGLE Receptor patch (and/or MULTI), not while loading a plugin receptorized patch, once manually instantiated.
Mind that VB3 1.2 (in Receptor) first loads its defined default patch but Receptor shows having loaded the first one on the internal VB3 1.2 list, instead of the last one loaded on Receptor, or the first in the list of receptorized plugin's patches, as for all other receptor working plugins, it seems VB3 is directly searching amongst its own patches, not amongst receptorized ones.
Paolo.

[c3boy]

Yes, VB3 will load up it's own internal factory patches fine when you load up VB3. It is only when you try and load up a receptor patch you have created in the single or multi that it causes receptor to restart.

[c3boy]

bumpety bump

[thesoundsmith]

Has there been any movement on this? I cannot use it on V1.6etc (latest release) as it locks up the Receptor as soon as I try to change patch. I don't have 1.1, and don't want to go through a lot of registry manipulation.

[ZioKiller]

I'm working at a new update for VB3 right now (including some minor bug fix, a new leslie sim., a tone cabinet sim., etc.) but I still can't figure out what's crashing the Receptor...

[fedde]

Hi Guido,

Wow, already working on a new version again... cool! I just had a lot of fun with the demo of your trumpet VST. I just need a good saxophone VST and my brass section is complete...

About VB3: do you have a lot of local variables in some of your functions? It might be that the stack size of the receptor host/OS is smaller than the windows hosts (there was a stack overflow message). If that is the case try to move variables in classes, make them global (this might not work well for multiple instances) or declare them dynamically.

Best regards,

Fedde