No ASIO Driver Problem ?

Spirit · Post by **Spirit** » Fri Jan 04, 2002 1:45 am

Here's some very good info on cooling:

http://www.dansdata.com/coolers.htm
http://www.dansdata.com/hx45fan.htm

cheers

ChrisWerner · Post by **ChrisWerner** » Fri Jan 04, 2002 3:19 am

Hello everybody,I got a Pulasr 1 and a srb board.I getting the "No Asio Message" so often that I getting ill if this will not happen.I will get the problem when I crashes Cubase because I uses again to many Plug´s and the Cpu Usage getting above the limit.
Cubase will crash.I have to close Cubase and if I restart it, while leaving the same Creamware Projekt in back, you will get this No AsioDriver Message.
The Solutaion I found.If Cubase crashes close it and close Pulsar,the best way is to reboot you System.Then start Cubase and then the PulsarSoftware(with AsioProjekt).Cubase will find the Asio again or reselect it in the AudioSettings.If not a walkthrough in the Cubase MME Settup can help and to rename the Def Files from Cubase(def.all and def.vmx .Important ,you have to save your MixerSetting as def.vmx and the Cubase Def.all Song(Cubase 5 recommended)once you have get all setting together.After this close Cubase to give it the "feeling" everthing is okay.Now you can work laid back again, starting Pulsar then Cubase and everthink is set for you.
I got 4 fan´s in my Comuter the CPU ,PowerUnit ,one for the Case and one on the GraphicCard,anythink work quite good.
Maybe I could help someone here.
Cu

arish · Post by **arish** » Fri Jan 04, 2002 9:31 am

Thanks, chris and the other,
So far after i cleaned up the fan
Every thing work well,
Strange things happned i guess when fan is not working!

But, the is more people on the list out there that needs Help on 'asio problem'...

arish

subhuman · Post by **subhuman** » Fri Jan 04, 2002 3:39 pm

When Cubase crashes it doesn't let go of Pulsar's ASIO drivers

The best way I know of is to reboot, as mentioned above, to remove Cubase's strangle-hold.

minipax · Post by **minipax** » Mon Jan 07, 2002 3:28 am

goddamn it

i got my pulsar 2 on friday and it wasn't running properly after i installed poison,the STS 5000 and the free plug-ins(kept getting a 'no aiso driver' message) so i reinstalled the pulsar software,reinstalled the drivers and everthing worked great!....for about 4 hours,then suddenly while working on a track in Cubase 5 (i had 3 modular synths,poison,and the micromixer open)the sound went dead....then the 'NO AISO DRIVER' message came up again and the pulsar environment cursor kept on spinning (meaning the program was busy)

i rebooted and the environment was 'busy' right from the start,even before i started cubase,and of course cubase couldn't find the AISO SCOPE driver

i reinstalled the pulsar driver but to no avail,do you guys seriously think it could be dust???

maybe the Poison plug-in is the culprit.

my pulsar will still output sound if i say just connect a drum machine to the analogue outs and turn on the sequencer.

i hope you guys can help me soon cause even in those short few hours that i had the pulsar up and running it totally blew me away! it's so bloody intuitive to use and the sounds are something else....
cheers,
minipax

subhuman · Post by **subhuman** » Mon Jan 07, 2002 10:11 am

Not sure about Cubase, but to fix just about any Pulsar problems, just reinstall the latest "service pack." That's currently the V3.01 update (followed by V3.01b if you need it; I'm not running that since I don't need it). That should fix any cset.ini problems and dsp.idx problems (which do arrise when installing new plugins especially ones with new DSP files, and also happens when you change your hardware/adding/removing/moving your Creamware cards around).

For Cubase to behave, I have heard the public beta before V5.1 was more stable. But again I don't use it so this is not first hand knowledge.