"No more driver memory for async vxd connections"

[rhythmaster]

Hi!

I have this nasty error message when I work in XTC-Mode (VSTi) in Cubase 6.0.5 32 Bit PC.
This problem appears when a certain amount of Soniccore gear is inserted in my Cubase Project.
Then it's game over although the XTC-Load displays only apprx. 20 %.

So what can be done to load more devices??
Has it to do with the XITE-1 or with the PC configuration.
Do you need more info about my PC?
Reinstalling the SCOPE Software brought no success.

SC Xite-1 with latest Software
Win 7 32 Bit all updates done
Cubase 6.0.5 (latest version)
INTEL DP35DP Mainboard with QuadCore and 2 GB RAM

Any help welcome
Thanks
Harry

[garyb]

i'm sure the XITE can load more devices than the software/hardware environment will allow. everything has a limit. that's just my guess.

in Scope mode this wouldn't be an issue, but with the massive amount of communication involved with integrating into the sequencer, there is probably a limit imposed by the system itself.

[dante]

Can you post a list of the devices / sample rate / synth poly and DSP meter (if XTC mode has one ) ?

[rhythmaster]

Ok. I will post it.

I also guess that this problem started with Cubase 6.0.2 or so.
With older versions I didn't have this problem.

I have to figure out how a fallback from 6.0.5 to e.g. 6.0 works. It seems not so easy for
I can't execute the 6.0.2 update-installer because there is a message which says that
the current version is newer than the one I try to install. So completely uninstalling Cubase and starting
again with an older version could be an option ?!?!?

Harry

[YISH313z]

Bumping this as I am getting this error as well.

I finally reinstalled V5.1, and this error appears in Scope only mode after adding a second STS 3000 sampler or using more than 32 voices for one STS .

Thing is I was able to run two STS 3000 in Scope 4.0 with no issues.

I also tried this with no other devices running in SFP mode(I don't use XTC)

Win XP sp3
2 Pulsar II & 1 Luna II
3 gigs ram
Scope v5.1

[YISH313z]

Something has definitely changed between 4 and 5.1 in regards to this error. I reloaded 4.0 to see how many STS 3000 I could load on my cards and here is the result...


On 15 DSP's Maxed:
5 @ 32 voices
1 @ 20 voices

[dante]

On my XITE-1D I can only load one STS5000 at 32 voice polyphony, then the second one gives the async error.

On my PCI cards (12DSP) I can load 6 at 32 voices and dont get the error yet.

Both are running Scope 5.1 (WinXP 32 bit 4gig RAM)

[siriusbliss]

On my XITE-1D I can only load one STS5000 at 32 voice polyphony, then the second one gives the async error.

On my PCI cards (12DSP) I can load 6 at 32 voices and dont get the error yet.

Both are running Scope 5.1 (WinXP 32 bit 4gig RAM)

Probably a good idea to post this to Holger and the guys at SC.

G

[dante]

I didnt try assigning to specific DSP on XITE, like Maustrax suggested here :

http://www.xited.org/viewtopic.php?f=16 ... =STS#p8610

But if I were going to build a project using many STS voices I would use the cards anyways .

Having both cards and XITE doubles the scope for workarounds...

[rhythmaster]

This issue appeard suddenly. No change of SCOPE 5.1 Software (I had the latest version installed when it was working well).
Then this error-message appeared

Probably an hardware-issue??? Will there be the need for a firmware-upgrade of the hardware??? Any counter???

I can't go on with this issue it kills my creativity.

I use SCOPE mainly in Cubase XTC-Mode (Cubase latest version 6.0.5 PC, WIN7 32 Bit)

Harry

[rhythmaster]

I passed it on to Holger ...

Let's see!



Harry

[spacef]

if the problem didn't happen before Cubase 6, may be it is cubase 6 probelm ?

You should try Studio One v2 : it is better than Cubase 12....
I can run Scope/Studio One v2 in 32 bit as smoothly as Cubase 553 at 24 bits... and cubase just can't handle 32 bits on my system, while Studio One does it without bothering (well, one pci overflow at start and quiting of Studio One v2.. vs infinite pci overflow loop when using cubase... cubase has a problem with asio).

First, it uses the same shortcuts as Cubase, same ways to work, so the crossgrade is not painful (you can also tell it to use shortcuts of most audio-sequencers instead of cubase).
The inclusion of Melodyne Editor is awesome.
The library for you midi clips, audio clips, whatever clips, by drag and drop is awesome.
The sound of the same 24 or 16 bit wavesample from third party is awesome, nothing to do with cubase.
The ableton-like sample previews (ie, at song's tempo) is just awesome.
The few things I have been able to test since a week now with the demo version... evrything is awe...wait for it...some.
The mixer is still a little bit mysterious to me, because i didn't yet dig in and the inserts is not good looking to me, but there are groups and busses (groups = linking faders of multiple tracks: imagine when tracking vocalist on multiple tracks ... isn't this awesome?).
For me, it is cubase the way i waited it to evolve for years...

390 euros for the producer version, i can easily and gladly dump Cubase, Reaper, and all that crap, for something that is really better.

Try it, if it doesn"t work, well, it doesn't work... but any cubase user should give it a try , watch the tutorials on their site (multitrack piano roll edition = incredible and ..awesome http://studioone.presonus.com/tutorials/editing/ 3rd video).

[rhythmaster]

Hey!

Thanks for this advise. But I also tried it with Cubase 5 now --> same error.
But it appeared suddenly when I upgraded from Cubase 6.0.4 to 6.0.5
When I made a fallback to Cubase 5 and Cubase 6.0.0 --> same error now.

Maybe a hardware issue with my PC.

I will give Studio One v2 a try - thanks

Harry

[Bud Weiser]

if the problem didn't happen before Cubase 6, may be it is cubase 6 probelm ?

You should try Studio One v2 : it is better than Cubase 12....
I can run Scope/Studio One v2 in 32 bit as smoothly as Cubase 553 at 24 bits... and cubase just can't handle 32 bits on my system, while Studio One does it without bothering (well, one pci overflow at start and quiting of Studio One v2.. vs infinite pci overflow loop when using cubase... cubase has a problem with asio).

First, it uses the same shortcuts as Cubase, same ways to work, so the crossgrade is not painful (you can also tell it to use shortcuts of most audio-sequencers instead of cubase).
The inclusion of Melodyne Editor is awesome.
The library for you midi clips, audio clips, whatever clips, by drag and drop is awesome.
The sound of the same 24 or 16 bit wavesample from third party is awesome, nothing to do with cubase.
The ableton-like sample previews (ie, at song's tempo) is just awesome.
The few things I have been able to test since a week now with the demo version... evrything is awe...wait for it...some.
The mixer is still a little bit mysterious to me, because i didn't yet dig in and the inserts is not good looking to me, but there are groups and busses (groups = linking faders of multiple tracks: imagine when tracking vocalist on multiple tracks ... isn't this awesome?).
For me, it is cubase the way i waited it to evolve for years...

390 euros for the producer version, i can easily and gladly dump Cubase, Reaper, and all that crap, for something that is really better.

Try it, if it doesn"t work, well, it doesn't work... but any cubase user should give it a try , watch the tutorials on their site (multitrack piano roll edition = incredible and ..awesome http://studioone.presonus.com/tutorials/editing/ 3rd video).

I got my Presonus Studio One v2 Pro 2 days ago and after I used v1 Pro for some time and confirm it´s a great program.
De-installed Cubase as also Wavelab.
Maybe I keep Reaper too because of some specialities.
Used Scope 4 up to now, but will order Scope 5.1 next week and check all out then.

B.t.w., if you used the demo version, you didn´t use the v 2.04 build which comes w/ fixes.
When I installed from the DVDs, the next step was updating and then it didn´t crash while scanning VSTplugins folder what it did 1st.
May I ask which accuracy you ran on your 32Bit system ?
Did you check 32Bit or 64Bit internal accuracy in the preferences/program options ?

I myself I checked 64Bit accuracy and that might have caused crackling and nearly 100% processor load w/ one of the demo projects coming w/ Studio One v2 Pro,- and I have a older dual core machine too, 2x 3.86GHz, running Win XP 32Bit SP3.

Bud

[rhythmaster]

Hi!

Does Studio One v2 support VSTIm (XTC)-Mode? I've installed it but it can't be initialized (

Harry

[rhythmaster]

cub.jpg (195.79 KiB) Viewed 3538 times

I've posted now a screenshot with this problem!
I've added 7 Profit-5's (1 voice each) and with the 8th there is this message.

Is it related to the XITE-1 Hardware or to my PC-Hardware or to the PCI-Express-Interface?

Cubase 6.0.5. 32 Bit Win7
Intel Core2 Quad CPU Q9450 2,66 Ghz
INTEL DP35DP

[YISH313z]

This seems only related to Scope 5.1. I have neither cubase or studio one and recieve the error when using Scope 5.1 standalone with no other software loaded. No such error in 4.0.

[ehasting]

Same here!
Gets the same result..

[YISH313z]

ehasting what motherboard are you using?

[spacef]

>>>>
May I ask which accuracy you ran on your 32Bit system ?
Did you check 32Bit or 64Bit internal accuracy in the preferences/program options ?
I myself I checked 64Bit accuracy and that might have caused crackling and nearly 100% processor load w/ one of the demo projects coming w/ Studio One v2 Pro,- and I have a older dual core machine too, 2x 3.86GHz, running Win XP 32Bit SP3.

Bud
>>>>

Not sure the question is for me....
if yes, then;
For the moment I didn't really play with the bits. I am just trying with 1 project where i didn't modify any of the default settings.
When I look in the preferences, all i see is "32 bits" (which is Scope's bit depth). I have w7 pro-x64, i can run 64 bits plugins fine (no difference with cubase 64 bits)
My system is based on Scope pro PCI with Scope 5.1 on w7 64 bits , very sensitive to PCI overflow issues and currently limited in term of asio outputs (as the mobo is recent, it does not handle PCI as well as 5 or 10 years ago).

I cannot tell anything about XTC as I don't use it.
On dsp/native development mailing list, many people who seem to know what they talk about, say that 64 bit accuracy does not bring anything soundwise except for marketing/advertising purposes. I don't know if this is absolutely true, but having attempted to read their production in articles and blogs, highly technical, i'm enclined to think they could be right.

My point was to (advertise for studio one, lol) , was to point out that Studio One is more solid than cubase on the same hardware pc/soundcard at same bit depth/sampling rate. and so may be there were chances that it solves some issues.

Mehdi

ps, that's what i have as preferences (pic below)
ps2 it does not crash when starting and scanning my /vst_64/ folder.