Hi there,
I'm wondering if anybody else is having this problem?
Basically I can have a project of any size, length or amount of plugs... but as long as SubBoomBass is involved, the save time jumps about 1000%.
For instance, I have a project here, with 3 VST instruments, and maybe 5 VST effects, at well under 10% CPU... When I "Ctrl + S" it saves in about half a second. When I then add 1 instance of SubBoomBass, the save time jumps to about 5 seconds. Not only that, but the audio stream gets messed up like CRAZYTOWN.
If it's a bigger project, like hovering at 30-40% - the save time with SBB involved is staggering, and the sound of the glitches involved is freaky!
I also tried to install the single-core CPU version to see if it worked any better, but the single-core installer always installs a multi-core version anyways!?!!

I'm using Cubase 5 (will have my 6 upgrade this week)
the latest version of SBB
My machine is a Toshiba A500
Windows XP SP3
i7-720QM Processor
nVIdia Geforce 310M 512MB GPU
4 GB Ram, 7,200RPM HD
RME Fireface 400

I will login and send an official letter to support, I just thought I'd see if anybody is having a simmilar problem at all.

Hi there

Thanks for getting in contact. We haven't had such reports about saving time before I don't think, and SBB has been out around 18 months so far.

Are you using the 32 or 64 bit versions of Cubase , and the 32 or 64 bit versions of SBB ?

Cheers

Jon

Both 32 bit.

I will have Cubase 6 this week, so I will test as soon as I install. Hopefully (fingers crossed) the problem is just a Cubase 5 problem?...

But I have noticed more sound stream glitches with my Rob Papen plugs than any other of my plugs. Changing patches is less than gracefull when compared to almost anything else in my VST folder. Even Albino was like this... Why would this be the case? I actually sold Predator simply because of this problem. I miss the sound (and it may sound silly), but when I think of the glitches when changing patches, damn, i just couldn't bare it.

My system is Toshiba Satellite A500 i7-720QM Processor, nVIdia Geforce 310M 512MB, Windows XP SP3... I have a Windows Win 7 64 Pro partition which is waiting for Cubase 6, sometime this week. Moving to 64bit I think. Will grab Punch as soon as I can too, it sounds great and hopefully will be a huge saving grace in my live set, as my current drum sampler isn't cutting the mustard, and my drum synths need too much extra processing and dont have as much flexability when it comes to modulation and live performance. Out of the box, Punch is FAT.

Hi there

Let us know how things go in Cubase 6.

Weird that you say that Albino had similar problems when changing presets as say Predator.

Albino is produced by LinPlug for Rob, it shares no code or anything else with Predator, so there can be no intristic problems with the code causing this , because they don't share any.

So that points somewho to it be something to do your setup, because it's the only thing in common between the two plugins, which is odd, hmm.

Cheers

Jon

Hi,

appart from the fact, that there is maybe a problem in the software.
Changing presets, especially if reverb is involved is tricky.
This is even trick with hardware synthesizers or workstations.

Do you use preset midi program change commands?

Rob

Actually I haven't used Albino on this machine. I sold it a while ago.

As for MIDI program changes, no, and I'm only using patches nowdays because I have so little time to write music. I would like to use SubBoomBass in my live set, but I haven't tried to use the program change message with it in Cubase OR Ableton Live. Actually in Ableton Live SBB suffers from the same glitchy preset behaviour as did Predator, and Predator also did on 2 previous desktop machines.

Look, I wouldn't be surprised at all (with my luck) that I've just stumbled upon 3 different CPUs or GPUs which were incompatible with RP plugs... The Matrox card I had in my first desktop was troublesome with LinPlug's RMV, to the point of complete ridiculousness, and the CPU i had in that machine was a Hyperthreaded P4 Prescott (which was incompatible with some plugs like impOSCAR) and the temporary desktop after it I think didn't have a dedicated graphics card... But I just can't figure out these glitches. The only other thing that I've consistently used that I can think of is my RME Fireface 400 (god forbid). I have been using computers for music for long enough to understand when a buffer length needs to be increased, but it just makes me scratch my head when I have very low CPU use and I get pops.


Anyways, I'm going to take the plunge and buy Punch in the next few days. I should have Cubase 6 by Friday, I'll let you know how I go
For now I'will load up a big project and torture test the demo of Punch. Man that thing sounds tight, nice work guys!

Ok, hmm. Let me know how it goes with Punch, please let us know how that goes as well.

Cheers

Jon

...ok, Cubase 6 arrived and is installed on both partitions.

In Win XP SP3 32 bit, SubBoomBass is exhibiting the same behaviour. My Project is sitting around 30% CPU and if I save the project Cubase becomes frozen for maybe 6 seconds, thereabouts. If I then remove SBB from the instrument rack, and save the project, it saves in under 1 second. And if I have the song playing while SBB is inserted in the VST rack, the audio stream glitches out for the duration of the 6 seconds or so, when I remove SBB the audio stream generally offers a little click or jump (a la Cubase, depending on the size of the project) but keeps playing normal enough.

In Win 7 64 Pro; Cubase 32bit, if I save with the song playing SBB just drops out and all the other plugs keep playing as normal while the song saves.
In Win 7 64 Pro; Cubase 64 bit, SubBoomBass does not even show up in the program
It is installed and sitting in its folder, the 64 bit version, but no-show.

Suggestions? Workarounds?

Hi there

Hmm, about the 64 bit version I would install the single core 64 bit version, then delete the blacklist file Vst2xBlacklist.xml. This can be found at

C:\Users\<user name>\AppData\Roaming\Steinberg\<version of Cubase>\Vst2xBlacklist.xml

Where <user name> is your user name and <version of Cubase> is the version of Cubase such as Cubase5

This folder may not visible on your Windows systems. You may have to change the folder options to enable the display of hidden files and folders.

Deleting this file will force Cubase to do a rescan on all the plugins.

Beyond that, could you pm with your email. If it is ok with you I would like to send you some test stuff for SBB, because I'm keen to see what is going on here.

Cheers

Jon

PMed, thanks for your help Jon

No problem, it's best to see if I can fix these issues.

Cheers

Jon

...man whatever you changed with that dll seems to have worked.

I started at 512 samples buffer on Cubase 6 32bit Win XP SP3...
FLAWLESS, I made a Ctrl + Alt + S and a new project saved without so much as a noticeable stutter. And 256 samples was flawless. Even 128 was prety good, considering the amount of math going on in realtime...

Nice one, I don't have time to torture test it to much tonight, but I made the odd filter tweak and such, and no real problems as far as i can see.

Thanks Jon

Team Papen are helpfull

TOTALLY!

Cool, this is weirdness with updateDisplay in Cubase. I'll put a fix in the next update of SBB . If your having similar problems, let me know and I can send you this fixed version now.

Cheers

Jon