PlanetZ forums - scopeusers.com

Im having a lot of trouble with this set up.... dont seem to be able to get it to work at all... running V3 Pulsar software...

Firstly I have tried the setup with some edits to the cset.ini file recommended in the Pulsar installation manual.

I added:

[hw]
numcards=2

and:

[board0]
boardid=1
[board1]
boardid=0


I have tried alternating the board IDs as well in case the order was wrong.

What happens next is that the Pulsar V3 software will load.... all looks well until I try to open a file.... simply clicking the mouse on the menu causes the Pulsar V3 software to bail with y a typical MacOS error: "Application has unexpectedly quit...."

Is it possible to get a Pulsar2 and Luna2 working together?.... this is very frustrating... I hope someone has some intelligence on this.

Thanks for reading.

digit

Hi,

If this occured right after you installed the soft - then I have no clue what to do. But if this occured some time after installation - you have to install the soft once more (it's the simpliest way). CSET.INI gets corrupted (some half-strange strings appear in it) and it causes system crashes the way you experienced (just moving the cursor to the file menu). Once you install the soft - backup the cset.ini file to replace the corrupted one in the future (it's very important, like an oxygene for a humanbeing!!!). And there's one more thing you should pay attention to: the installation proccess: first install the luna 2.5, then the 2.52 update, then move Recording Mixer and Surround Mixer module files (they are the only modules you don't find in Pulsar 3) to a safe place (desktop, for instance) and delete the whole luna soft and installed drivers, then install Pulsar 3 soft, move the Rec. Mixer and Surr. Mixer to the P3 devices/mixer folder, then observe the results, then share your observations to us, please . This should work.

P.S.
In fact, you don't need to make any manual changes in the cset.ini (I mean the boardid, numcard and so on).


_________________
Sam Plaire

<font size=-1>[ This Message was edited by: samplaire on 2001-11-01 05:43 ]</font>

<font size=-1>[ This Message was edited by: samplaire on 2001-11-01 05:47 ]</font>

Thanks for your response samplaire....

I have been in touch with TechSup @ Creamware who have been reasonably helpful. They didnt actually provide me with any really useful information but they were nice.. .....

I am a seasoned ProTools MixPlus user so I'm used to running through all the permutations of OS/Soft versions and possibly corrupted files.....

My first proble was definitely the damn cset.ini file.... the old one had become corrupted and was causing the problems. I found this out by reinstalling the V3 software. However, reinstalling didnt work.... the cset.ini file from the new install didnt include all the relevant paths, so it couldnt find any of the hardware device I/Os and gave me heaps of error messages.

I solved the problems by comparing the old (corrupt) and new (incomplete) cset.ini files in a text editor... and copied and pasted between them until I got the V3 software to boot properly.

I did need to add the [numboard] and [boardid] strings to cset.ini file.... the V3 software did nto see the Pulsar2 card at all without those settings added.

My other problem was with ASIO. I use a lot of other digital toys in my studio.. in fact the Pulsar2 is connected to an O2R... and the my main Project template is configured for synch via ADAT.

Now... if I launch Pulsar and load up my default Project WITH external sync... WITHOUT turning on my O2R (thats providing the digital clock info) then launch Cubase.... Cubase reports that it is unable to locate the ASIO device.... then reports that it cant create the audio engine.... the upshot is that Pulsar doesnt seem to ENABLE the ASIO device driver if there is no clock present... simple really... but nothing anywhere in the manual as far as I can see that would alert you to that happening. Commonsense really though.

Also... Absynth 1.2.3 doesnt seem to like Creamware ASIO. Actually it doesnt seem to like much ASIO at all... I have tried it with DSP Factory as well... no good.... so I use it in Cubase as a VST instrument.

Just my thoughts...

Cheers, Digit.

About the cset.ini tweaks (boardid and so on) - in my case it was not necessary, in yours was (sorry for the wrong tip )

Now... if I launch Pulsar and load up my default Project WITH external sync... WITHOUT turning on my O2R (thats providing the digital clock info) then launch Cubase.... Cubase reports that it is unable to locate the ASIO device.... then reports that it cant create the audio engine.... the upshot is that Pulsar doesnt seem to ENABLE the ASIO device driver if there is no clock present... simple really... but nothing anywhere in the manual as far as I can see that would alert you to that happening. Commonsense really though.

And even more, if you want to change the sync while cubase's running (even in its idle state) it can cause problems as well (asio doesn't work, you have to save the song, recorddisable -> recordenable inputs and so on). But I don't find it being a bug (though they should warn us in the manual before attempting to do that, not each musician is a computer geek)