1

[Mauri]

Well I managed to do the update but I’m not at all sure how I did it.

After much searching (and swearing), altering the registry, running the cmd prompt, installing and re-installing both, 32 bit and 64 bit, I ran the ‘Repair’ option with the 64 bit installer then ran the update and voila, it worked. I then uninstalled the 32 bit version.

What a ‘bloody’ mess…

Reply To: 2.2.0 x64 update fail. version: 2.2.0
Operating system: Windows 10

Cubase Pro 11 x64 with jBridge | WaveLab Elements 10.0.50 | W10 Pro x64 Dual Boot on 2 SSDs plus 3 SSDs for samples and project/audio files | i7 5930K @ 4.6GHz (stable) | ASUS X99 Pro | 32GB G.SKILL Ripjaws RAM | RME HDSPe AIO | GPU AMD Radeon RX 580 Series | Mackie HR624 MKII | 2 x UAD2 Solo PCIe | 2 x 24" LED monitors...

[Mauri]

Disabled Windows antivirus, still the same result.

Reply To: 2.2.0 x64 update fail. version: 2.1.8
Operating system: Windows 10

Cubase Pro 11 x64 with jBridge | WaveLab Elements 10.0.50 | W10 Pro x64 Dual Boot on 2 SSDs plus 3 SSDs for samples and project/audio files | i7 5930K @ 4.6GHz (stable) | ASUS X99 Pro | 32GB G.SKILL Ripjaws RAM | RME HDSPe AIO | GPU AMD Radeon RX 580 Series | Mackie HR624 MKII | 2 x UAD2 Solo PCIe | 2 x 24" LED monitors...

[Mauri]

I just had a look at the EZDrummer2 installation package, that’s where those files are. I assume they are content files and you need’nt be concerned about them, just run the installer and you should be ok.

Are you having some kind of a problem?

Cubase Pro 11 x64 with jBridge | WaveLab Elements 10.0.50 | W10 Pro x64 Dual Boot on 2 SSDs plus 3 SSDs for samples and project/audio files | i7 5930K @ 4.6GHz (stable) | ASUS X99 Pro | 32GB G.SKILL Ripjaws RAM | RME HDSPe AIO | GPU AMD Radeon RX 580 Series | Mackie HR624 MKII | 2 x UAD2 Solo PCIe | 2 x 24" LED monitors...

[Mauri]

Hi, and welcome to Toontrack!

Where are these files, are they in the installation package?

Mauri.

Cubase Pro 11 x64 with jBridge | WaveLab Elements 10.0.50 | W10 Pro x64 Dual Boot on 2 SSDs plus 3 SSDs for samples and project/audio files | i7 5930K @ 4.6GHz (stable) | ASUS X99 Pro | 32GB G.SKILL Ripjaws RAM | RME HDSPe AIO | GPU AMD Radeon RX 580 Series | Mackie HR624 MKII | 2 x UAD2 Solo PCIe | 2 x 24" LED monitors...

[Mauri]

A ‘short’, Thank You :)!

Mauri.

Cubase Pro 11 x64 with jBridge | WaveLab Elements 10.0.50 | W10 Pro x64 Dual Boot on 2 SSDs plus 3 SSDs for samples and project/audio files | i7 5930K @ 4.6GHz (stable) | ASUS X99 Pro | 32GB G.SKILL Ripjaws RAM | RME HDSPe AIO | GPU AMD Radeon RX 580 Series | Mackie HR624 MKII | 2 x UAD2 Solo PCIe | 2 x 24" LED monitors...

[Mauri]

Greetings,

Just letting you know, for the benfit of other users, the cause of my problem ended up being Waves update V9r19. gearslutz user ‘eightyeightkeys’ posted the solution:

“Un-install Waves
C: Program Files(x86)/…..Delete the Waves Folder

Go to C:UsersyouruserAppDataRoamingWaves Audio…Delete the Caches and Preferences folders from that location.

Empty Recycle bin

Re-install latest (V9r20) versions of Waves

Boot Cubase
Rescan PlugIns/Update/Update Plug-In Information

It worked. My crash on exit issue issue is now gone.”

It worked well for me as well!

Cheers,

Mauri.

Cubase Pro 11 x64 with jBridge | WaveLab Elements 10.0.50 | W10 Pro x64 Dual Boot on 2 SSDs plus 3 SSDs for samples and project/audio files | i7 5930K @ 4.6GHz (stable) | ASUS X99 Pro | 32GB G.SKILL Ripjaws RAM | RME HDSPe AIO | GPU AMD Radeon RX 580 Series | Mackie HR624 MKII | 2 x UAD2 Solo PCIe | 2 x 24" LED monitors...

[Mauri]

Hi,

It turns out this error happens quite randomly. In testing, I found by unloading and reloading EZD2 in one project the error did’nt occur, in another project that did’nt work.
Then I found by unloading Slate VTMs (one instance on every EZD2 channel in Cubase) the error did’nt occur. In another project that did’nt work and I got the error.

The same error also happens when using the latest version Superior2.

Both EZD2 2.01 and SD2 2.40 are properly installed and work as expected. It’s only when saving and closing projects in Cubase which is the problem here.

I give up, the error is somewhat annoying but does not cause any damage so I’ll just put up with it.

Sorry if I’ve wasted anyone’s time,

Sincerely,

Mauri Berg.

Cubase Pro 11 x64 with jBridge | WaveLab Elements 10.0.50 | W10 Pro x64 Dual Boot on 2 SSDs plus 3 SSDs for samples and project/audio files | i7 5930K @ 4.6GHz (stable) | ASUS X99 Pro | 32GB G.SKILL Ripjaws RAM | RME HDSPe AIO | GPU AMD Radeon RX 580 Series | Mackie HR624 MKII | 2 x UAD2 Solo PCIe | 2 x 24" LED monitors...

[Mauri]

I don’t know what host you are using but in Cubase I have the 64-bit plugin installed in the same place as all other 64-bit plugs: C:Program FilesSteinbergVSTPlugins Cubase will automatically ‘see’ it there. If your location C:ProgramFilesVstPlugins works with your host then obviously install the 64-bit plugin there. Mauri in Very Hot Australia.

Cubase Pro 11 x64 with jBridge | WaveLab Elements 10.0.50 | W10 Pro x64 Dual Boot on 2 SSDs plus 3 SSDs for samples and project/audio files | i7 5930K @ 4.6GHz (stable) | ASUS X99 Pro | 32GB G.SKILL Ripjaws RAM | RME HDSPe AIO | GPU AMD Radeon RX 580 Series | Mackie HR624 MKII | 2 x UAD2 Solo PCIe | 2 x 24" LED monitors...

[Mauri]

Hi, Robin,

I would strongly suggest you have at least minimum of 8GB of RAM in your new machine, preferably 16GB, or even more.

When I changed from a 32bit to a 64bit setup I was so relieved not have to worry about RAM usage. Using a 32bit operating system (talking about Windows) you can utilise up to 1.7 or so GB of RAM, a bit more with a particular tweak.

My 8GB of RAM at the moment is enough for my way of working.

Good luck,

Mauri.

Cubase Pro 11 x64 with jBridge | WaveLab Elements 10.0.50 | W10 Pro x64 Dual Boot on 2 SSDs plus 3 SSDs for samples and project/audio files | i7 5930K @ 4.6GHz (stable) | ASUS X99 Pro | 32GB G.SKILL Ripjaws RAM | RME HDSPe AIO | GPU AMD Radeon RX 580 Series | Mackie HR624 MKII | 2 x UAD2 Solo PCIe | 2 x 24" LED monitors...

[Mauri]

IMHO I would suggest that a groove played by a ‘real’ drummer at a certain tempo should be used close to the original, otherwise the groove will sound increasingly ‘unreal’ as the tempo is increased or decreased. In other words, the drummer would play the same thing quite differently at a given different tempo. For example, a ballad type (speed) of groove does not sound good (realistic) as a fast rock groove.

Of course I realise the limitations of using premade grooves in EZD or Superior so there is (has to be!) room for reasonable tempo variations.

Mauri.

Cubase Pro 11 x64 with jBridge | WaveLab Elements 10.0.50 | W10 Pro x64 Dual Boot on 2 SSDs plus 3 SSDs for samples and project/audio files | i7 5930K @ 4.6GHz (stable) | ASUS X99 Pro | 32GB G.SKILL Ripjaws RAM | RME HDSPe AIO | GPU AMD Radeon RX 580 Series | Mackie HR624 MKII | 2 x UAD2 Solo PCIe | 2 x 24" LED monitors...

[Mauri]

Have you tried increasing the buffer size in protools?

Cubase Pro 11 x64 with jBridge | WaveLab Elements 10.0.50 | W10 Pro x64 Dual Boot on 2 SSDs plus 3 SSDs for samples and project/audio files | i7 5930K @ 4.6GHz (stable) | ASUS X99 Pro | 32GB G.SKILL Ripjaws RAM | RME HDSPe AIO | GPU AMD Radeon RX 580 Series | Mackie HR624 MKII | 2 x UAD2 Solo PCIe | 2 x 24" LED monitors...

[Mauri]

I sometimes have issues with spiking (volume) in EZdrummer, the problem usually is the ‘Random’ feature’, there should be an ability to adjust the amount of ‘randomness’.
It is too unpredictable (being random;)) the way it is now…although it can be turned off, but that is not a good solution.

Have a good Christmas, everyone at Toontrack,

Mauri.

Cubase Pro 11 x64 with jBridge | WaveLab Elements 10.0.50 | W10 Pro x64 Dual Boot on 2 SSDs plus 3 SSDs for samples and project/audio files | i7 5930K @ 4.6GHz (stable) | ASUS X99 Pro | 32GB G.SKILL Ripjaws RAM | RME HDSPe AIO | GPU AMD Radeon RX 580 Series | Mackie HR624 MKII | 2 x UAD2 Solo PCIe | 2 x 24" LED monitors...

[Mauri]

As I understand it, it’s never a good thing to convert sample rates if it can be avoided.
So I would think using EZdrummer at 44.1kHz will produce the optimum sound from it.

As far as I’m concerned 44.1Khz is plenty good enough unless you’re doing sound for video or movies.

Mauri.

Cubase Pro 11 x64 with jBridge | WaveLab Elements 10.0.50 | W10 Pro x64 Dual Boot on 2 SSDs plus 3 SSDs for samples and project/audio files | i7 5930K @ 4.6GHz (stable) | ASUS X99 Pro | 32GB G.SKILL Ripjaws RAM | RME HDSPe AIO | GPU AMD Radeon RX 580 Series | Mackie HR624 MKII | 2 x UAD2 Solo PCIe | 2 x 24" LED monitors...

[Mauri]

I’m sure Toontrack will help you out if you contact them and explain your situation.

Mauri.

Cubase Pro 11 x64 with jBridge | WaveLab Elements 10.0.50 | W10 Pro x64 Dual Boot on 2 SSDs plus 3 SSDs for samples and project/audio files | i7 5930K @ 4.6GHz (stable) | ASUS X99 Pro | 32GB G.SKILL Ripjaws RAM | RME HDSPe AIO | GPU AMD Radeon RX 580 Series | Mackie HR624 MKII | 2 x UAD2 Solo PCIe | 2 x 24" LED monitors...

[Mauri]

HI orchetect, I know this won’t help you but the 32bit version works fine here too.

Cheers,

Mauri.

Cubase Pro 11 x64 with jBridge | WaveLab Elements 10.0.50 | W10 Pro x64 Dual Boot on 2 SSDs plus 3 SSDs for samples and project/audio files | i7 5930K @ 4.6GHz (stable) | ASUS X99 Pro | 32GB G.SKILL Ripjaws RAM | RME HDSPe AIO | GPU AMD Radeon RX 580 Series | Mackie HR624 MKII | 2 x UAD2 Solo PCIe | 2 x 24" LED monitors...

[Author]

Replies