Vb3 1.4

RELATED
PRODUCTS

Post

Hi,

I had that problem too where old patches all revert to the default preset. To get the factory patches back like they were, first unlock the <factory> bank. Then within VB3 call up each preset and save it as a receptor patch within that bank.

The v1.4 release notes mention this problem:

* Now programs and banks are saved as "custom chunks"
* Reorganized the .DAT file and renamed it to .INI ...

* These changes may cause an incompatibility with the data saved by the previous versions. Before updating, take note of your previous setting and consider re-making your own presets if you ever made any.

Geoff

Post

[quote="okifinoki"]I have been using VB3 v1.3 at gigs for a while now. It worked fine via the unsupported install method with the exception of an occasional audio clip (a rare pop maybe from a cpu spike?). ([/quote]

Hi - this is interesting!

I get this occasional full gained "BEEP" as well, running 1.3
(with a lot of comments from my band members)

I have asked Guido if he has any records of it. For me, it sounds like a percussion is triggered, like if one hit a G4 all drawbars in and full swell.

Can it really be a Receptor problem?

I have a couple of Voce drawbar controllers that had fixed CC# (not
configurable) settings for drawbars and pushbuttons
- the ingenious v1.3 new channels select for incoming CC on all three
manuals resolved the challenge of two equal controllers sending the
same CC (each manual has it's own channel), no need for a midi
enhancer. Take midi mapping seriously and you have a hit! (Good work
Guido!)

- I have noticed that there is quite a soundable difference in volume
per key going chromatically down the lowest octave scale, with or
without folded back.

- Ebel

Post

I have not experienced any "full gain beeps" running VB3 1.2 on my Receptor 2 - just saying...

Post

I know this is an old thread. Two and a half years later and Muse has still not updated Plugorama to support v1.4 install?
What gives? Are they going/gone out of business? Do they even care?

I have v1.2 on my Receptor2 and have not a clue how to get v1.4 on there. I read of an unsupported plug-in method, but have no idea how to perform it/find a tutorial.

Any help would be greatly appreciated!

Post

ebfunk wrote:I know this is an old thread. Two and a half years later and Muse has still not updated Plugorama to support v1.4 install?
What gives? Are they going/gone out of business? Do they even care?

I have v1.2 on my Receptor2 and have not a clue how to get v1.4 on there. I read of an unsupported plug-in method, but have no idea how to perform it/find a tutorial.

Any help would be greatly appreciated!
I did this a couple of years ago but if I remember correctly the install was pretty simple. First I deleted all of the v1.2 files and then used the unsupported plug-in method to install v1.4. I haven't had any problems with it.

There is a section in the Receptor Manual called "Installing a PlugIn on Receptor" (page 170 on my copy). I followed those directions and didn't have any problem. The Manual can be found on the Muse website at http://www.museresearch.com/downloads/d ... Manual.pdf

Ray

Post

rbisco wrote:
ebfunk wrote:I know this is an old thread. Two and a half years later and Muse has still not updated Plugorama to support v1.4 install?
What gives? Are they going/gone out of business? Do they even care?

I have v1.2 on my Receptor2 and have not a clue how to get v1.4 on there. I read of an unsupported plug-in method, but have no idea how to perform it/find a tutorial.

Any help would be greatly appreciated!
I did this a couple of years ago but if I remember correctly the install was pretty simple. First I deleted all of the v1.2 files and then used the unsupported plug-in method to install v1.4. I haven't had any problems with it.

There is a section in the Receptor Manual called "Installing a PlugIn on Receptor" (page 170 on my copy). I followed those directions and didn't have any problem. The Manual can be found on the Muse website at http://www.museresearch.com/downloads/d ... Manual.pdf

Ray

Success! Thanks to Ray and John, on another post, I combined the two suggestions and it worked!

Download the Windows version and drop the "VB3.dll" and "VB3fx.dll" files in the unsupported plug-ins folder -
from the setup window select Include "Unsupported Plugins" folder and install.

Thanks guys for your help, and thanks Guido for a great product!

Now to figure out where they hide "midi learn" in a Receptor. :)

Post

Good news and welcome to ver 1.4

yes, all I did was just to simply replace the whatever.dll files

1. I renamed the previous whatever.dll to whatever.old
2. then I copied new dll files into the VB3 folder on receptor

Bingo!


be aware that 1.4 uses new types of ini files for configuration!

Also: DO NOT USE ANY OTHER SAMPLE RATE BUT 44.1 ON THE RECEPTOR

If you use 48 or 96 khz the VB3 has a tendency to crash!
This next to the irritating "beep" was the most annoying thing.

About Midi setup.

You know VB3 (as all VST from Guido) can configure all parameters (buttons, drawbars) you see in the VST by right click, then assign (or even better learn)

I think I had a conflict in this implemenation, and I think this created the "beep". However, I "think" the "beeps" disappeared when I set Receptor to 44.1KHz

Hope this can be be of any help.

//Ebel


ps. Guido is still working with new release standalone VST. Until now, only the Hamicord or the Mojo keyboards have the new VB3 version installed. www.crumar.it
BR, Eystein

Post

According to Muse, 1.4 will work, but you cannot save your drawbar settings. Can you guys confirm whether that is the case?

Post

[quote="billw"]According to Muse, 1.4 will work, but you cannot save your drawbar settings. Can you guys confirm whether that is the case?[/quote]

Well,
when I save a patch, the drawbar-setting is reloaded.
VB3 has a "save as default" in the menu, meaning this is what all settings will be at startup.

Then, as said, there is an .ini file i the VB3 directory in which you can store drawbar preset. Just like the matrix in the back of the B3, but w/o wires...

If you have a keyboard with more than 61 keys, you can "assign" the left octave to be your "black keys", and these keys can be setup to choose A,B or any other drawbar program. For both manuals. Take a look at the Hamichord which is an implementaion of VB3 using these keys, as well as other midi controlled switches.

But again, you must edit the ini file to change the settings for each of the black keys (A and B (black key Bb and B) uses the drawbars and their continous state)

Best of luck

ps.
My headache is the midi implementation Receptor has chosen using the Non-Registered Parameter Number (NRPN), because my drawbar controller only sends standard CC. I would like to not have pass midi cc to the plugin, however use the mapping already done for the plugin. But the requirement of NRPN forces me to do select "pass cc to plugin" in the receptor setup. .d.s
BR, Eystein

Locked

Return to “Muse Research and Development”