No, I don't use many local variables in a function, especially if it's a time-critical function like the audio loop... I use to declare them globally (when I can) or if I have to re-use the function for multiple purposes (like for polyphony) I make new classes.
Anyway I don't think that could be a problem because a stack overflow should crash the OS every time, while they're experiencing crashes at a specific condition.
I think it's a matter of function calls by the host: probably the Receptor calls setProgram(0) before setSampleRate().
Since VB3 has to build internal wavetables with the very first setProgram(0) call, this could be a problem if the sample rate isn't defined yet. But this is just a guess... I cannot know if I don't have access to a Receptor for doing tests. I've added a lock to the setProgram() function that checks for the sampleRate variable, if it's not > 0 the function is skipped, and it's recalled by the resume() function when all classes and variables are properly initialized.
VB3 is crashin' on me!
-
- KVRian
- 1297 posts since 17 Aug, 2003 from Italy
-
- KVRian
- 1297 posts since 17 Aug, 2003 from Italy
Update:
as it seems, Muse Research has no interest in supporting VB3 for the Receptor, so I'm sorry to disappoint you, friends, but I won't be bothering any more trying to find out what's causing the crash we're discussing here.
VB3 is a plugin for Windows. Receptor is not Windows. Sorry.
Guido.
as it seems, Muse Research has no interest in supporting VB3 for the Receptor, so I'm sorry to disappoint you, friends, but I won't be bothering any more trying to find out what's causing the crash we're discussing here.
VB3 is a plugin for Windows. Receptor is not Windows. Sorry.
Guido.
-
- KVRist
- 120 posts since 21 Jan, 2005
Muse,ZioKiller wrote:Update:
as it seems, Muse Research has no interest in supporting VB3 for the Receptor, so I'm sorry to disappoint you, friends, but I won't be bothering any more trying to find out what's causing the crash we're discussing here.
VB3 is a plugin for Windows. Receptor is not Windows. Sorry.
Guido.
why don't you barely support SoundFonts.it to make VB3 completely working on Receptor?
It's just a tech or reference manual demand, i really dont' understand.
Really oriented to sell my two Receptors!
PGi
-
- KVRist
- 173 posts since 3 Sep, 2007 from CT
That will be a problem.ZioKiller wrote:Update:
as it seems, Muse Research has no interest in supporting VB3 for the Receptor, so I'm sorry to disappoint you, friends, but I won't be bothering any more trying to find out what's causing the crash we're discussing here.
VB3 is a plugin for Windows. Receptor is not Windows. Sorry.
Guido.
How about MRRAY73 Mark II? Is it user installable and Stable?
-
Rick@MuseResearch Rick@MuseResearch https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=18273
- MUSEician
- 350 posts since 23 Mar, 2004
It's true that Receptor is not compatable with vst 2.4 so when ever we have such a plugin we flag it in rm-host flag as vst 2.3, simple as that. As for VB3 we are trying it now using Direct Install.
Rick
Muse Research
Muse Research
-
- KVRian
- 524 posts since 25 Aug, 2005
Rick, I sure hope you can get this one working - it is the ONLY B3 plug that lets you change just the upper or lower manual preset, so if you have altered the other manual's registration, it does not change. This is VERY important when playing as a real organ...
-
- KVRist
- 103 posts since 10 Jan, 2007
Hi folks,
I managed to install VB3 1.1 now on my Receptor. It was not too hard, you only need the regedit rpm package (I received it from Hybernation) and import one .reg file with my VB3 user name and password. I tried it out on a gig yesterday night and I am *very* happy with it! I used the Jimmy preset and it sounded great... (even our guitar player noticed the difference...)
One secret tip: I programmed the rotary speed to the damper pedal (CC 64). This really works well! When I press my damper pedal the rotary speed raises. The longer I press the damper the faster the rotation.
Still, 1.2 sounds much better so a solution for that is very much appreciated. I saw that Guido made an update of VB3. Anyone tried that one? I will try later this weekend if I can find the time.
Ciao,
Fedde
I managed to install VB3 1.1 now on my Receptor. It was not too hard, you only need the regedit rpm package (I received it from Hybernation) and import one .reg file with my VB3 user name and password. I tried it out on a gig yesterday night and I am *very* happy with it! I used the Jimmy preset and it sounded great... (even our guitar player noticed the difference...)
One secret tip: I programmed the rotary speed to the damper pedal (CC 64). This really works well! When I press my damper pedal the rotary speed raises. The longer I press the damper the faster the rotation.
Still, 1.2 sounds much better so a solution for that is very much appreciated. I saw that Guido made an update of VB3. Anyone tried that one? I will try later this weekend if I can find the time.
Ciao,
Fedde
-
- KVRist
- 120 posts since 21 Jan, 2005
The update to 1.2/1.21 doesn't work, meaning when recalled to be intantiated in an empty vsti channel slot, eg. as a saved Single or Multi or in a Snapshot.. You can only save single vsti presets and manage these as usual, this doesn't crash the Receptor.fedde wrote:Hi folks,
Still, 1.2 sounds much better so a solution for that is very much appreciated. I saw that Guido made an update of VB3. Anyone tried that one? I will try later this weekend if I can find the time.
Ciao,
Fedde
Anyway if you instantiate it manually and let it there all the gig even if snapshots change and changing single vsti presets (not Single or Multi changes)...it stay there and sounding amazing, more and more than vb3 1.1
So you have to choose between the really good sounding and working 1.1 and the amazing but not completely working 1.2.1
Ciao,
PGi
-
- KVRian
- 691 posts since 13 May, 2004 from Silicon Valley
Hi everyone,
I don't own / haven't tried VB3 - but have been reading this thread with interest.
I have helped a few developers making their plugins Receptor compatible, and testing different versions.
I have found (often) if there are changes to the block of parameters saved in an FXP (the native format of a Receptorized patch) between versions of a plug (eg. if there are more parameters saved in an FXP file in version 1.1 since version 1.0). The Receptor host can crash when trying to load a plugs previous version FXP.
Note - when loading a Receptor Patch, this is like loading all of the parameters in an FXP into the VSTi's patch buffer directly. This is different than when a VSTi has loaded a full bank of FXPs - and indexes the patches internally through the VSTis patch management system.
What can be done to help this? A few potential things:
1.) Perhaps there is some way to scan the bits being forced into the patch buffer for an specific patch version (eg encoding the patch version into the data)
2.) Pad a patch buffer length with extra bytes - to account for changes in the patch buffer size between versions of the VSTi.
So I don't know how relevant this may be to VB3 - but perhaps these insights might help Guido.
Regards,
Kevin L
I don't own / haven't tried VB3 - but have been reading this thread with interest.
I have helped a few developers making their plugins Receptor compatible, and testing different versions.
I have found (often) if there are changes to the block of parameters saved in an FXP (the native format of a Receptorized patch) between versions of a plug (eg. if there are more parameters saved in an FXP file in version 1.1 since version 1.0). The Receptor host can crash when trying to load a plugs previous version FXP.
Note - when loading a Receptor Patch, this is like loading all of the parameters in an FXP into the VSTi's patch buffer directly. This is different than when a VSTi has loaded a full bank of FXPs - and indexes the patches internally through the VSTis patch management system.
What can be done to help this? A few potential things:
1.) Perhaps there is some way to scan the bits being forced into the patch buffer for an specific patch version (eg encoding the patch version into the data)
2.) Pad a patch buffer length with extra bytes - to account for changes in the patch buffer size between versions of the VSTi.
So I don't know how relevant this may be to VB3 - but perhaps these insights might help Guido.
Regards,
Kevin L
-
- KVRian
- 691 posts since 13 May, 2004 from Silicon Valley
OK - I Loaded up VB3 demo on Receptor (VB3 1.2.1, Receptor Pro OS 1.7).
So Now I see = the problem is with loading singles/multis saved from the same version of VB3. Loading internal patches and Receptorized patches seems to be fine.
BTW, I'm pretty impressed with VB3. It has that nice oscillating crunch when overdriven with all-bars out (Sounds like USB's Charlie - samples of the real thing) and still having Leslie spin up/down controls.
It would be nice if VB3 had more tone control (eg lo/mid/hi param eq), and a way to turn off preset selection from the keyboard.
Regards,
Kevin L
So Now I see = the problem is with loading singles/multis saved from the same version of VB3. Loading internal patches and Receptorized patches seems to be fine.
BTW, I'm pretty impressed with VB3. It has that nice oscillating crunch when overdriven with all-bars out (Sounds like USB's Charlie - samples of the real thing) and still having Leslie spin up/down controls.
It would be nice if VB3 had more tone control (eg lo/mid/hi param eq), and a way to turn off preset selection from the keyboard.
Regards,
Kevin L
-
- KVRist
- 120 posts since 21 Jan, 2005
Hi Kevin,looneytunes wrote:OK - I Loaded up VB3 demo on Receptor (VB3 1.2.1, Receptor Pro OS 1.7).
So Now I see = the problem is with loading singles/multis saved from the same version of VB3. Loading internal patches and Receptorized patches seems to be fine.
Kevin L
just for helping Guido from SoundFonts.it and every musician playing Hammond clones on a Receptor, like me,
do you know the way to monitor communication between Receptor's host and a plugin (eg. VB3) like VstMonitor from Steinberg does, that unfortunately doesn't work on Receptor?
It seems to be the only way to make VB3 completely working and able to be loaded as Single or in a Multi or in a Snapshot.
Thanks,
PGi
-
- KVRian
- 691 posts since 13 May, 2004 from Silicon Valley
Hi PGI,
No - I'm not aware of such a utility on Receptor, though I imagine the developers must have something like this in their dev environment to debug what is happening. Even something as simple as printing trace messages of VST API calls would be really useful!
Right now, I am looking at the error messages in my system log, which are slightly different from what 'The Good Doctor' originally got:
Jul 5 16:25:19 KTL-Recep-1 rm-host: err:seh:EXC_DefaultHandling Unhandled exception code c0000096 flags 0 addr 0x3750ea6
Jul 5 16:25:19 KTL-Recep-1 start-receptor: rm-host session ended
(Was reported after switching Multi)
Jul 5 16:25:21 KTL-Recep-1 rm-host: wine: Unhandled exception (thread 001a), starting debugger...
Jul 5 16:25:22 KTL-Recep-1 start-receptor: rm-host session ended
(Was reported after switching Single)
These would indicate some type of program exception was generated from VB3, but I can't tell yet what they are (I'm searching for Linux exception codes for what was reported in the first exception).
Per the VST 2.4 messages, I've seen these before reported from other plugins, but there is typically no effect on the host when the plug registers these
messages. I think they are benign.
I'm hunting some more ...
Thanks,
Kevin L
No - I'm not aware of such a utility on Receptor, though I imagine the developers must have something like this in their dev environment to debug what is happening. Even something as simple as printing trace messages of VST API calls would be really useful!
Right now, I am looking at the error messages in my system log, which are slightly different from what 'The Good Doctor' originally got:
Jul 5 16:25:19 KTL-Recep-1 rm-host: err:seh:EXC_DefaultHandling Unhandled exception code c0000096 flags 0 addr 0x3750ea6
Jul 5 16:25:19 KTL-Recep-1 start-receptor: rm-host session ended
(Was reported after switching Multi)
Jul 5 16:25:21 KTL-Recep-1 rm-host: wine: Unhandled exception (thread 001a), starting debugger...
Jul 5 16:25:22 KTL-Recep-1 start-receptor: rm-host session ended
(Was reported after switching Single)
These would indicate some type of program exception was generated from VB3, but I can't tell yet what they are (I'm searching for Linux exception codes for what was reported in the first exception).
Per the VST 2.4 messages, I've seen these before reported from other plugins, but there is typically no effect on the host when the plug registers these
messages. I think they are benign.
I'm hunting some more ...
Thanks,
Kevin L
-
- KVRist
- 413 posts since 5 Dec, 2005
Thanks Kevin, the stuff Soundfonts.it is putting out theses days DESERVES to be supported with Receptor. Guido is a great programmer of these and takes his vintage gear seriously. You only have to check out his gear on youtube, he has some nice original gear there! 