Nice sale on VB3

[PhilMuller]

Really well said, adeptio!!

VB3 and Zebra2, in my book, are the two most important plugins (and I have them all). I know that in the case of Zebra2, some patches cause the Receptor problems, while most of the others work just fine. Zebra2 goes out to lunch after about 20 minutes or so as well. Being in the software business myself, I would say that the underlining problem is "Garbage Collection". IE: the plugin has to clean up (memory variables and temp space) after itself because most likely Linux does not do it automatically for the plugin. The plugin thinks the OS will do the garbage collection ... but it doesn't. I have noticed the CPU meter growing a little after about 15-20 minutes. This is probably because of extended swapping.

I believe VB3 is partially a sample based plugin whereas B4 was a sine wave generator. If this is indeed the case, VB3 needs a lot of disk space to load samples... especially since I change my drawbars constantly. I can go through 20 different patches in about 3 minutes. I am sure this reeks havoc with the OS.

I can't go back to VB3 Version 1.2. I just can't do it! LOL! It lacks quite a bit from V1.4. Absolutely brilliant plugin!

Also; I have found that the Receptor does not like to switch Sources or Multis while you are playing notes. That is reasonable to some extent.

I have a Receptor 2 Pro Max loaded with RAM. I wish I had a 1TB SSD... but they don't make them that big. sigh!! Adeptio, what Receptor system parameters are you using? EG: Dual Core, etc.

[Meo]

Anyone else out there pro VB3 ?

I have version 1.4 also, works like a charm.

We do mostly covers, so I think B4II and VB3 complete each other nicely.

For example, I think B4 is better suited for Santana style, but VB3 for Deep Purple style.

If I may ask, what is your strategy to save a setting in VB3 for receptor?

I usually pick up one preset, make some changes to it, then in receptor I save as a single. But I'm not entirely sure it keeps all my changes. Do you know a better way?

Cheers!

[adeptio]

Phil,

my receptor has 4 GB ram and dual core. The VB3 uses so little resources that I don't think this is the issue concerning the sudden VB3 stall. The VB3 uses no sample files, the sound is created 100% by using software algorithms only. VB3 does not write files to disk during operations either. But for sure, it uses memory...and its dll is dependent on a true win OS environment....

The receptor Linux (2.4) runs a WINE Windows API emulator, and has obviously a VST host application that sits between the plugins and the ASIO driver (if that's what Muse uses). A VST-type-Host made for windows may e.g. require a standard Microsoft library to run, which does not have an equivalent in Wine. How Muse has solved this host issue is a company secret.

So our little VB3 dll marvel has been compiled to run in a 100% compatible winOS VST host environment, or MAC equivalent. The compatibility issues with trying to run Windows format DLLs has been and still is the real challenge for Muse IMHO. Not to talk about 64 implementation....Suddenly it's a memory leak somewhere, or other faults, and the CPU starts getting more load. Or something, what do I know. You might be right about the pagefiles and increased swapping between the physical and virtual memory. Maybe this problem of ours is reduced if one only runs VB3, since it requires so little memory, period? I'll try again.

Using Receptor remote one can study the windows folders setup by Wine, and maybe start the Windows Task Manager and monitor cpu and memory..that would be cool (usually this requires access to Linux terminal, and not the familiar ctrl+alt+del )

So what needs to be done to find the cure...load VB3 in different versions with different receptor settings and look for changes, clues etc...(the sort of job I hate to do when I don't have access to the Linux system, and to be honest steal the time I need to play, not fiddling around with a darn computer - my reason for buying the receptor)

So hey -Rick, Kevin and Bryan - let's find a way to make the VB3 1.4 run w/o issues, shall we? Please -we beg you kindly. Or is it a good idea to sit and wait for the 2.0 release from Guido?

[adeptio]

[quote="Meo"]
I have version 1.4 also, works like a charm.
[/quote]

Hi Meo,
thanks fo your most welcomed post.

Does the 1.4 work e.g. more than 1 hour without showing any problems?

And does it do this together with some 5-6 plugins that is very memory intensive (like a sampled piano - ivory - acoustic piano - elektrik piano etc)[/quote]

[PhilMuller]

Adeptio - Kevin - Gary,

I have created Tickets on VB3. VB3 doesn't actually crash, it sort of goes into purgatory and then of course the audio goes out with the GUI. Since this doesn't generate any data to the System.log, it is hard to debug.

I believe VB3 is still an unsupported plugin? If so, what has to occur to make VB3 a supported plugin?

Phil

[Meo]

I have version 1.4 also, works like a charm.

Hi Meo,
thanks fo your most welcomed post.

Does the 1.4 work e.g. more than 1 hour without showing any problems?

And does it do this together with some 5-6 plugins that is very memory intensive (like a sampled piano - ivory - acoustic piano - elektrik piano etc)

[/quote]

Unfortunatly, I have no situation were I leave it loaded for such a long time.

I guess I should have specified.

I always have other pluggin loaded (like 3-4) but I switched multi banks every 4-5 songs.

[Meo]

A quick sample of VB3, that's my take on Deep Purple (Perfect Stranger) sound:

http://soundcloud.com/dniss/perfect-stranger

I can't do that with B4II.