PlanetZ forums - scopeusers.com

Hello all!
I have a problem with pulsar in WindowsXP
after install SFP 3.1 in Device Manager -> Sound, Video nad game controllers -> Creamware Pulsar i click Properties in Settings selection (wave setup) i have Preferred Bit depth 16 24 32, and i can choose only 16 bit, other 24 and 32 options are disabled .

driver date: 07/05/2002
ver. 1.50.10.0

my computer:
board: GA-7vaxp + AMD2000xp (bios F-15)
memory: 512mb GEIL
video: Gigabyte RADEON 9200

please help me.

the scope card is not the same as a soundblaster. that behavior is normal and meaningless.

in other words, you say, that i can load the 24bit Wave source in pulsar and it will work 24 bit?

[edit] Something went wrong here, wrong paste or something, and the reply didn't make it here

PS. Hey I was in Tel Aviv again last saturday, too bad only 4 hrs then had to fly back :/ Wanna see more of the country!

_________________
More has been done with less.

<font size=-1>[ This Message was edited by: at0m|c on 2004-10-22 14:46 ]</font>

yes, the 24bit module will work.

Can one of guys clarify this for me, because I am in a similar situation, but with Windows 2000.

In the card settings for Pulsar, it shows that the driver bit depth can only be set to 16 bit - Fine.

I can load 24 bit Wave Sources and Destinations - Also fine.

Then I have to set the driver bit depth and the file bit depth in Sonar. I can set the file depth, but if I set the driver bit depth to 24, I get a driver conflict. So are you saying that if the card and the sequencer app both believe that the driver is 16 bit, it is still working at 24 bit?

I'm skeptical...

<font size=-1>[ This Message was edited by: poidog on 2004-11-03 16:19 ]</font>

So are you saying that if the card and the sequencer app both believe that the driver is 16 bit, it is still working at 24 bit?

Exactly. This 16/24 driver option is irrelevant after Win98. There must be some other problem going on in your Sonar.

Exactly. This 16/24 driver option is irrelevant after Win98. There must be some other problem going on in your Sonar.

I know for certain that there is a problem in Sonar. Specifically, in the Audio options, you must choose a bit depth for the drivers that you use in the project. If I choose 16 bit, everything works. If I choose 24, it doesn't (driver conflict).

So I'm comfortable with the idea that Creamware is running at 24 bit, even though Windows thinks its running at 16 bit. What worries me is that the actual recording application itself also thinks the driver is 16 bit. If my recording app is expecting a 16 bit stream, how can it record it at 24?

Sorry for the barrage of question. I really appreciate the feedback.

hmmm, 24 bit works fine here. do you truly have the 24bit modules in your project BEFORE opening sonar? also, asio SHOULD work better.....

The point is that pulsar and CW cards doesnt works with 16bits so do not be sceptical because it is windows problem

On 2004-11-03 21:43, garyb wrote:
hmmm, 24 bit works fine here. do you truly have the 24bit modules in your project BEFORE opening sonar? also, asio SHOULD work better.....

Yes, I do. And I apologize if I am running you guys in circles, but I'm not sure what my next logical step is. Here is my order of operation. I open the Scope interface. Load up 3 different 24-bit Wave source modules, connect them to mixer ins, and then hook up the outs appropriately.

Then I go to launch Sonar. One of two things happens here. If Sonar was previously configured to work with 24 bit audio drivers (and it was), then Sonar will pop up an error box showing the same 3 Creamware drivers I just created and say these "These drivers do not support current audio format, do you wish to use them anyway?". If I say no, then they are disabled, if I say yes, then they don't work.

Now if Sonar is configured to work with 16 bit drivers, then it recognizes the 3 new Creamware Wave drivers, and they more or less work. I still get more dropouts then I ever did with my Echo card, and I get a weird digital stuttering effect whenever I stop playing audio, but I'll deal with those issues later. Again my issue is NOT that I don't believe that Scope is running at 24 bit. My issue is that if my recording software thinks the driver is talking in 16 bit, then its unlikely that software is actually recording a 24 bit stream.

I'm happy to use either Wave or ASIO, I just want to find a 24-bit combination that works. Any troubleshooting steps you can recommend?

Sonar in 24bit and Scope with Asio 2 24bit drivers no problems.

the 16/24bit in win2K and WinXP is set in projects and no longer you can choose this in device manager.

if you open Scope and load Asio 2 24bit
then open Sonar and set it to Asio and 24 bit you should not have those driver errors.
Something is not right in your setup.

Also how many tracks are you recording in 24 bit .? what is the speed of your CPU and RAM?

I have the same problem. I have an original Pulsar, Scope 4.0, Sonar 4.01, a fast computer with lots of memory.

ASIO drivers aren't an option - I need both Pulsar/Scope (for synths and ADAT I/O) and a firewire interface to a Tascam DM-24. ASIO only allows one card at a time...

What gives?