SONAR 2.2 + kx

lee miran · Feb 6, 2003, 12:17 AM

I upgraded SONAR to vers. 2.2 which now is ASIO capable. However, I am getting the following error message:

Quote:

Error creating input buffer #0: error = -150 [size=2048]
GetLastError()=2

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

Retry?

Retrying only generates another instance of the message.

According to another user on another forum, he has it working.

Any suggestions?

James Argo · Feb 6, 2003, 12:52 AM

Quote:

Originally posted by lee miran

According to another user on another forum, he has it working.

...That was me lee miran...

I was about to ask your question here...

Hang on, lets see what they got...

kato · Feb 6, 2003, 02:03 AM

well, I have the same problem. It´s an old problem with kxdrivers. Maybe a solution in the new version coming soon, who knows?
In Cubase you can start the program empty, with no project loaded, and change the latency to 170 ms before you open. (Look for more info in the ASIO section of the forum, there is a thread on this bug).

I cant get to the ASIO panel in Sonar without error message all the time so I cant change to higher latency once the error has come.
Fortunately I have cubase sx also on my system, can open cubase, change to high latency, close cubase and open Sonar again.

If you don´t have another app to get to the ASIO panel, you can always change back to wdm drivers. Maybe a little bigger latency but not that much really.

(There is a trick with deleting kxASIO in the registry somewhere but I dont remember where in the registry or how...)

s3n71nel · Feb 7, 2003, 10:28 AM

I just downloaded the 2.2 patch and did a quick asio recording test and it worked fine. I just recorded one track to see if it works.
Maybe try rinstalling the latest 3528 kx drivers. I think I seen an error something like that with cubase a long time ago and thats what I did.

Cool now i will be able to do 6 inputs with sonar .

cya

RIV@NVX · Feb 7, 2003, 11:29 AM

-5 bug will hopefully be fixed in 3529 (which introduces new ASIO code).

James Argo · Feb 9, 2003, 03:03 PM

Thanks everybody... I'll check it out tonight.
Thank you...

Jaymz

Feb 7, 2003, 11:29 AM	#5
RIV@NVX Freedom is a feature. Join Date: Jul 2002 Location: Croatia, Rijeka Posts: 4,476 Rep Power: 67 System Specs	-5 bug will hopefully be fixed in 3529 (which introduces new ASIO code). __________________ -- Vedran

Feb 9, 2003, 03:03 PM	#6
James Argo DriverHeaven Newbie Join Date: Feb 2003 Location: Indonesia Posts: 6 Rep Power: 0	Thanks everybody... I'll check it out tonight. Thank you... Jaymz __________________ Keep Rockin' & Rollin'

Feb 6, 2003, 02:03 AM	#3
kato DriverHeaven Junior Member Join Date: Jan 2003 Location: sweden Posts: 48 Rep Power: 0	well, I have the same problem. It´s an old problem with kxdrivers. Maybe a solution in the new version coming soon, who knows? In Cubase you can start the program empty, with no project loaded, and change the latency to 170 ms before you open. (Look for more info in the ASIO section of the forum, there is a thread on this bug). I cant get to the ASIO panel in Sonar without error message all the time so I cant change to higher latency once the error has come. Fortunately I have cubase sx also on my system, can open cubase, change to high latency, close cubase and open Sonar again. If you don´t have another app to get to the ASIO panel, you can always change back to wdm drivers. Maybe a little bigger latency but not that much really. (There is a trick with deleting kxASIO in the registry somewhere but I dont remember where in the registry or how...)

Feb 7, 2003, 10:28 AM	#4
s3n71nel DriverHeaven Junior Member Join Date: Dec 2002 Posts: 41 Rep Power: 0	I just downloaded the 2.2 patch and did a quick asio recording test and it worked fine. I just recorded one track to see if it works. Maybe try rinstalling the latest 3528 kx drivers. I think I seen an error something like that with cubase a long time ago and thats what I did. Cool now i will be able to do 6 inputs with sonar . cya