hi i have installed latest r2r bazille,on cubase 13 pro pc,no sound comming from instrument,64 bit version.
vst3 version crashes cubase.
anyone else having this issue?
vst is enabled.
thanks

 

no, working flawlessly, it's like having the legit version

you say "no sound coming from instrument....crashes cubase"
it crashes or loads and doesnt work? lol it's different problem

anyhow sounds like something weird in your setup

 

not u again! hehe o.joking.
thanks for reply.
so i just came in there was gonna load vst 3 version to see what the error message was so i culd let u know.
decided to update plugin information through plugin manager.
i have some waves plugins,and its looking me to select waves 13.1 plugins folder.
like where the heck is it?

 

so in vst 2 verison of bazille when i load it play midi keyboard i hear no sound.
the vst is enabled,
all that happens visually is the "event recieved indicator" beside the R W automation buttons on the instrument flash when i press notes.
no meters move on the channel.
as for the vst 3,it loads but as soon as i press a key on midi keyboard i get cubase error "a serious problem has occured in the following file( it gives the path of vst bazille)
cubase 13.0.41 has become unstable..
once i press ok cubase dissapears(closes)

 

100% issue in your system, maybe a wrong installation process, or you had an old version from another team and you didn't properly clean up

If you have R2R Cubase and Bazille it's like having 1:1 legit versions

You could try uninstall, deep clean as R2R explains and then reinstall

If you use Cubase only you should always avoid VST2, do not install that version at all if you don't have a proper reason [doesn't matter what you've found in the NFO]

BEFORE uninstall, just to have a definite check, you could try to load Bazille both VST2 and VST3 in
1 bluecats patchwork standalone
2 bluecats patchwork VST inside Cubase
and test if it has the same behaviour as in the daw

 

That to me sounds like something has dialled home, which in turn has screwed up the software!

 

People have mentioned before about versions of u-he stuff just expiring, normally. I do not know if that is true, but those Mac beta versions a few years ago certainly did this. They would not crash though, they would just make a slight white noise like any expired demo can do. They were just going to do that as planned, either way.

But the last r2r versions of Bazille mention nothing about them patching them at all, and nothing about them being from either Beta or Demo versions of them anyway. One just Regged, and the more recent one with a keygen. @funkman, you can make sure you have blocked in hosts, or firewall correctly; or even download the most current official demo version. Just to be able to say you already checked those things too.

This is as close to a "likely problem on your end" as it gets. If/when Cubase crashes again, get the Cubase crashdump file and upload or paste it somewhere.

 

^^^^ This

 

the pc has not been connected to internet since i installed bazille,and i blocked hosts like it said in file

 

im right in saying that there is no uninstaller for bazille?

 

ok,installed patchwork,loaded bazille 64 bit,it loaded,as soon as i pressed key on midi keyboard all dissapeared,patchwork closed.

 

that confirms that Cubase is not involved, the problem is in Bazille. Are you sure you didnt install a wrong plugin version? Maybe 32bit or something. Its a very light plugin. Anyhow...

Uninstall and deep clean, but I would proceed this way, because its weird you dont see the unistall option in Windows.

1 INSTALL again over your actual situation (install only, no need to put R2R user again)
2 reboot
3 uninstall
4 deep clean
5 reboot

then proceed to a fresh install, I would suggest to tick VST3-64 bit only

I didnt even notice who you are, and I dont matter, I told why I write.

 

how do u (if u needed to) uninstall? as i said i just delete the .dll and data folder.
im doing a search in this pc for "bazille"
the com.u-he lisings come up.
where are they on my pc? it dosent give a path
and "deep clean" how do i do that?

 

I wrote numbers just to solve that. Just follow the order.

1 INSTALL
2 reboot
3 UNINSTALL
understand?

If you install correctely what you find in R2R package you will have the uninstall option from the WIN uninstall app. As easy as that

INSTALL OVER, so you dont need to uninstall manually. ok?

 

"deep clean" means even a windows register cleaning, search the boards for that

someone will probably use an app like reg cleaner or something, someone will tell to do it manually. I dont use any app except the stock in Windows "regedit", but thats everyone's choice. Just search and make your choice

 

Weren't you on a PC without AVX? Might be why the VST3 crashes.

E: From Bazille's system requirements: Intel Nehalem or newer, AMD Bulldozer or newer

 

Last edited: Sep 14, 2024

Only if you launch Cubase and then patchwork as a wrapper plugin inside it, after it works fine in a standalone application version. If it crashes Standalone Patchwork, then you more or less know it is the plugin only.

There are a few ways you can load plugins into patchwork now. Some of them won't work they way you think they should/used to. You might be not even loading the same kinds of instances. It can load a Patchwork synth in an audio insert slot in some DAWs. You can screw this up now, in new versions. Now it lets you load things incorrectly, and both plugins look nearly identical.

If you look in your Plugin Manager for Cubase, do you have 4 different plugins? Is that what was just recently changed? It will show: BC Patchwork type: Midi-Controlled effect, " bc patchwork" MFX: type: Midi Processor, Patchwork Synth types Midi Controlled effect, and Instrument.

 

Last edited: Sep 14, 2024

yes on pc without avx

 

I would suggest Revo Uninstaller if there is an uninstall option. If however there isn't one, then something like CCleaner to clean the registry, but be very careful with that, as if you don't know what you're doing, you can create more problems that you have now.

Make sure you only remove references you know for certain are to do with Bazille, maybe you can widen it to allow for ALL u-He products and then do a clean install of all U He stuff afterwards.

 

thats what I told to do but as you can see he doesnt follow instructions and doesnt report properly whats happening

so we have to stay on the

thingy...