"-5 bug" error in ASIO applications

switzoid · Dec 16, 2002, 07:43 PM

Hi,

First: Thanks for such a great driver!!!!! It has really been a tremendoud help!!!!!
I would be dead in the water otherwise

So, the above subject, and more detailed below, is a bug I get when I try to shut down projects in Cubase SX, running the latest KX driver with a Soundblaster Live! with break-out Live! Drive box.

My system is 996MHz AMD Duron on a an ECS K7s5a
mainboard, with 512MB DDR-SDRAM and a 200mhz memory bus speed system.
But the harddrives are a bit old...3 of them in the system, all 5400rpm,
2 6gigs, and 1 12gig.

The full error is in a Kx ASIO dialog error box and says:

Error creating output buffer #1: error = -105[size=1024] GetLastError()=2

VirtualLock failed ('-5' bug). Compact your memory and retry.

Retry?

Anyone else get this error? Will it/does it cause problems?

t9ya · Dec 17, 2002, 01:50 AM

Hi,

When I use kX ASIO (3527) with HALion 1.13 in CubaseSX 1.05, I always getting Error.

See this link.
http://www.mindgame.net/kx/kX_ASIO_Error.jpg

How can I do?
Please give me some advice or information.

imperia · Dec 18, 2002, 07:13 AM

try to open kx DSP then rightclick and Reinitialise DSP.

tell me if this works for you.

t9ya · Dec 18, 2002, 10:08 PM

Thank you imperia,

I did Reinitialise DSP.
But situation does not change.
I'm getting same error.

Guest46534 · Dec 20, 2002, 11:30 AM

Hi,

it's the same problem with my WinXP and Logic Audio. ASIO drivers cannod be load in the preferences.
"Error creating output buffer" is the answer. Which release of KX driver do you use? I have the latest BETA 3528.

schneesteinauge

Soeren_B · Dec 21, 2002, 08:04 PM

Regarding Logic:

Logic seems to be more resource hungry (compared to Cubase). This may be related to the face that Logic tries tp allocate max number og in- and outputs. In kX' case this is 16 in and 16 out which is probably a lot more than you will ever need

The trick to make Logic run more smoothly is to enter the audio settings (Menu: Audio->Audio Hardware and Drivers -> Audio Driver 2 -> ASIO) and reduce the number of I/O streams to a number that you are more likely to use, like 2 in and 2 out (more outs if you use surround mixing)

Cheers
Soeren

Longe · Dec 25, 2002, 07:18 PM

I have the same problem with the last kx driver and cubase on windows 2000 so

Guest46534 · Dec 26, 2002, 09:20 PM

Hello at all,

I could solve that problem with following presets:

- don't use the KX 3528beta driver in that case! Try 3526_stable for Logic and maybe Cubase too.
- use the idea Soeren_B = reduce MaxI/O to 2 or 4 in your Audio Settings of your apps.

So you can adjust ASIO in your settings. Maybe cou can't record or hear a sound: [this was my problem too]:
Use KX DSP [right click on tray button KX] and disconnect the cable of "prolog" - Line2/Mic2 Left and same right to >routing<. Instead connect these port to "epilog" - ASIO 0 and ASIO 1.

Use the same way with other INPUTS in the >prolog< if you want to record from another Input.
Please let me know if this solution works for you.

yo!

sedgetone · Jan 11, 2003, 08:57 PM

Windows 2000 SP3
DirectX 8.1
kX 5,10,00,3526 - debug (Latency set to 5.33ms)
Soundblaster Live!
MSI 845 Pro2 Motherboard, Intel P4 1.7GHz, 256M Ram, x2 20G IBM DJNA352030 Hard Disks

Cubase SL V1.0.5.61
HALion V1.13

All software is legitimate copy's!!!!!

Error message as follows when exiting Cubase SL with HALion loaded; doesn't happen with Cubase VST V5.1R1:
==============================================
kX ASIO
==============================================
Error creating output buffer #0 error = -105[size=1024]
GetLastEmpty[]=2

VirtualLock failed ['-5'bug]. Compact your memory and retry.

Retry?
Yes No
==============================================

The problem can be recreated by following the following steps:
1, Open SL and either create a new project or open an existing one. You don't have to have any channels just the blank project.

2, Load HALion into any VSTi slot.

3, Exit SL from either the file menu or the upper right X button.

The message then appears, clicking Yes does nothing. The bug doesn't seem to do any harm but is a little annoying. Must say it's a huge improvement of the Creative Labs driver!!!!

Sedgetone

**Eugene Gavrilov** · Jan 12, 2003, 12:23 AM

3529 will introduce a new memory management code which might help fighting these '-105' bugs

stay tuned!

/Eugene

kato · Jan 13, 2003, 07:22 PM

Meanwhile you can try and start Cubase empty, change latency to 170, open project, change latency to 5.33 (2.66 if working only with audio),do your thing, and dont forget to change latency to 170 before you close your project. Works for me. (xp and Cubase sx.)

great drivers by the way, thanks!

JS2138 · Jan 14, 2003, 10:55 PM

kx is a marvelous driver, no question about that!!

additional to the -105-bug documented above I get following message:

“Error increasing current process’s virtual memory amount. You should have Administrator privileges. Error code: 57”

I tried all tricks mentioned (changing latency, reinitialising DSP...), but still: when I try to open files with more than, let’s say, 4-5 instruments loaded in Halion, I get those two error messages alternatively. Finally I have to answer the “retry?”-question with “no”, and in cubase (VST Multitrack) the default driver is now DirectX, unable to change it back to kx asio (if I do so I get the 57-error).
Strange thing is that its sometimes possible to open any file (after many tries), but I have no idea yet how I have managed it.
Thx for help!
____
Intel 2,4. 1 GB RAM, Soundblaster life, WinXP pro (admin), kx 3526, Cubase SX, Halion 1.1.

imperia · Jan 15, 2003, 08:41 AM

why you do not use the latest build - 3528?

JS2138 · Jan 15, 2003, 07:55 PM

thanks for your hint, installed 3528, but problems are the same.

guess I have to wait for the new memory management in 3529...

js

kato · Jan 15, 2003, 09:47 PM

If you are desperate you can unload Halion before you close cubase (notepad or something to remember what you had in Halion) . When you start Cubase next time it says something like "missing...continue without etc" and you click ok. You then insert halion in the same track. Automation and stuff is still there but you have to reload your instruments in Halion. It´s awkward but worked for me when I needed it.

Dec 17, 2002, 01:50 AM	#2
t9ya DriverHeaven Newbie Join Date: Dec 2002 Location: Japan Posts: 6 Rep Power: 0	I'm getteing kX ASIO Error. Hi, When I use kX ASIO (3527) with HALion 1.13 in CubaseSX 1.05, I always getting Error. See this link. http://www.mindgame.net/kx/kX_ASIO_Error.jpg How can I do? Please give me some advice or information. __________________ --*-> t9ya

Dec 18, 2002, 07:13 AM	#3
imperia HardwareHeaven Lover Join Date: Dec 2002 Location: Sofia, Bulgaria Posts: 174 Rep Power: 0	try this try to open kx DSP then rightclick and Reinitialise DSP. tell me if this works for you.

Dec 18, 2002, 10:08 PM	#4
t9ya DriverHeaven Newbie Join Date: Dec 2002 Location: Japan Posts: 6 Rep Power: 0	Nothing to change. Thank you imperia, I did Reinitialise DSP. But situation does not change. I'm getting same error. __________________ --*-> t9ya

Dec 20, 2002, 11:30 AM	#5
Guest46534 Guest Join Date: Dec 2002 Location: magdeburg Posts: 7 Rep Power: 0	VirtualLock failed ('-5' bug) Hi, it's the same problem with my WinXP and Logic Audio. ASIO drivers cannod be load in the preferences. "Error creating output buffer" is the answer. Which release of KX driver do you use? I have the latest BETA 3528. schneesteinauge

Dec 26, 2002, 09:20 PM	#8
Guest46534 Guest Join Date: Dec 2002 Location: magdeburg Posts: 7 Rep Power: 0	ASIO problem and VirtualLock failed ('-5' bug) for Logic, Cubase etc. Hello at all, I could solve that problem with following presets: - don't use the KX 3528beta driver in that case! Try 3526_stable for Logic and maybe Cubase too. - use the idea Soeren_B = reduce MaxI/O to 2 or 4 in your Audio Settings of your apps. So you can adjust ASIO in your settings. Maybe cou can't record or hear a sound: [this was my problem too]: Use KX DSP [right click on tray button KX] and disconnect the cable of "prolog" - Line2/Mic2 Left and same right to >routing<. Instead connect these port to "epilog" - ASIO 0 and ASIO 1. Use the same way with other INPUTS in the >prolog< if you want to record from another Input. Please let me know if this solution works for you. yo!

Dec 16, 2002, 07:43 PM	#1
switzoid DriverHeaven Junior Member Join Date: Dec 2002 Posts: 35 Rep Power: 0	VirtualLock failed ('-5') Compact your memory Hi, First: Thanks for such a great driver!!!!! It has really been a tremendoud help!!!!! I would be dead in the water otherwise So, the above subject, and more detailed below, is a bug I get when I try to shut down projects in Cubase SX, running the latest KX driver with a Soundblaster Live! with break-out Live! Drive box. My system is 996MHz AMD Duron on a an ECS K7s5a mainboard, with 512MB DDR-SDRAM and a 200mhz memory bus speed system. But the harddrives are a bit old...3 of them in the system, all 5400rpm, 2 6gigs, and 1 12gig. The full error is in a Kx ASIO dialog error box and says: Error creating output buffer #1: error = -105[size=1024] GetLastError()=2 VirtualLock failed ('-5' bug). Compact your memory and retry. Retry? Anyone else get this error? Will it/does it cause problems?

Dec 21, 2002, 08:04 PM	#6
Soeren_B kX Project DSP Engineer Join Date: Dec 2002 Location: Denmark Posts: 94 Rep Power: 0	Regarding Logic: Logic seems to be more resource hungry (compared to Cubase). This may be related to the face that Logic tries tp allocate max number og in- and outputs. In kX' case this is 16 in and 16 out which is probably a lot more than you will ever need The trick to make Logic run more smoothly is to enter the audio settings (Menu: Audio->Audio Hardware and Drivers -> Audio Driver 2 -> ASIO) and reduce the number of I/O streams to a number that you are more likely to use, like 2 in and 2 out (more outs if you use surround mixing) Cheers Soeren

Dec 25, 2002, 07:18 PM	#7
Longe DriverHeaven Newbie Join Date: Dec 2002 Location: Milan Posts: 2 Rep Power: 0	I have the same problem with the last kx driver and cubase on windows 2000 so

Jan 11, 2003, 08:57 PM	#9
sedgetone DriverHeaven Newbie Join Date: Jan 2003 Posts: 1 Rep Power: 0	VirtualLock failed, Cubase SL & HALion Windows 2000 SP3 DirectX 8.1 kX 5,10,00,3526 - debug (Latency set to 5.33ms) Soundblaster Live! MSI 845 Pro2 Motherboard, Intel P4 1.7GHz, 256M Ram, x2 20G IBM DJNA352030 Hard Disks Cubase SL V1.0.5.61 HALion V1.13 All software is legitimate copy's!!!!! Error message as follows when exiting Cubase SL with HALion loaded; doesn't happen with Cubase VST V5.1R1: ============================================== kX ASIO ============================================== Error creating output buffer #0 error = -105[size=1024] GetLastEmpty[]=2 VirtualLock failed ['-5'bug]. Compact your memory and retry. Retry? Yes No ============================================== The problem can be recreated by following the following steps: 1, Open SL and either create a new project or open an existing one. You don't have to have any channels just the blank project. 2, Load HALion into any VSTi slot. 3, Exit SL from either the file menu or the upper right X button. The message then appears, clicking Yes does nothing. The bug doesn't seem to do any harm but is a little annoying. Must say it's a huge improvement of the Creative Labs driver!!!! Sedgetone

Jan 12, 2003, 12:23 AM	#10
Eugene Gavrilov kX Project Lead Programmer and Coordinator Join Date: Dec 2002 Posts: 3,119 Rep Power: 75	3529 will introduce a new memory management code which might help fighting these '-105' bugs stay tuned! /Eugene

Jan 13, 2003, 07:22 PM	#11
kato DriverHeaven Junior Member Join Date: Jan 2003 Location: sweden Posts: 48 Rep Power: 0	temporary solution for cubase sx? Meanwhile you can try and start Cubase empty, change latency to 170, open project, change latency to 5.33 (2.66 if working only with audio),do your thing, and dont forget to change latency to 170 before you close your project. Works for me. (xp and Cubase sx.) great drivers by the way, thanks!

Jan 14, 2003, 10:55 PM	#12
JS2138 DriverHeaven Newbie Join Date: Jan 2003 Posts: 2 Rep Power: 0	kx is a marvelous driver, no question about that!! additional to the -105-bug documented above I get following message: “Error increasing current process’s virtual memory amount. You should have Administrator privileges. Error code: 57” I tried all tricks mentioned (changing latency, reinitialising DSP...), but still: when I try to open files with more than, let’s say, 4-5 instruments loaded in Halion, I get those two error messages alternatively. Finally I have to answer the “retry?”-question with “no”, and in cubase (VST Multitrack) the default driver is now DirectX, unable to change it back to kx asio (if I do so I get the 57-error). Strange thing is that its sometimes possible to open any file (after many tries), but I have no idea yet how I have managed it. Thx for help! ____ Intel 2,4. 1 GB RAM, Soundblaster life, WinXP pro (admin), kx 3526, Cubase SX, Halion 1.1.

Jan 15, 2003, 08:41 AM	#13
imperia HardwareHeaven Lover Join Date: Dec 2002 Location: Sofia, Bulgaria Posts: 174 Rep Power: 0	3528? why you do not use the latest build - 3528?

Jan 15, 2003, 07:55 PM	#14
JS2138 DriverHeaven Newbie Join Date: Jan 2003 Posts: 2 Rep Power: 0	3528? thanks for your hint, installed 3528, but problems are the same. guess I have to wait for the new memory management in 3529... js

Jan 15, 2003, 09:47 PM	#15
kato DriverHeaven Junior Member Join Date: Jan 2003 Location: sweden Posts: 48 Rep Power: 0	If you are desperate you can unload Halion before you close cubase (notepad or something to remember what you had in Halion) . When you start Cubase next time it says something like "missing...continue without etc" and you click ok. You then insert halion in the same track. Automation and stuff is still there but you have to reload your instruments in Halion. It´s awkward but worked for me when I needed it.