Subject:V 4d sound manager issues

Posted by: aress

Date:6/9/2003 4:42:47 PM

anyone working on XP pro, getting microsoft sound manager not found error?
version 4d works fine in ASIO but not in mapper mode, or classic waves driver...


didnt have this issue with 4b

sound card is ECHO MIA..........

Subject:RE: V 4d sound manager issues

Reply by: spesimen

Date:6/9/2003 8:45:29 PM

i think this is common to echo products. i use a gina24 and 4.0d also made these drivers not work.

i could care less however since ASIO mode works perfectly now! i hadn't been able to use it until this revision, so i'm a happy camper anyway.

Subject:RE: V 4d sound manager issues

Reply by: dkistner

Date:6/10/2003 6:17:49 AM

Hey, spesimen, this is good to know. I've got a Mia, and I love the sound of it.

Question: In my Control Panel sound properties window in XP, under the Volume tab, I keep showing "No Audio Device." Is this caused by the Echo drivers seizing control of the Windows Volume, you think? I thought at first it meant my card was being dropped, and I was reinstalling the drivers, but then I realized I was getting sound using ASIO.

So does that just mean there's no Windows audio device...and not that there's no audio device at all?

Subject:RE: V 4d sound manager issues

Reply by: Iacobus

Date:6/10/2003 9:45:06 AM

Sounds logical, since Windows uses its own driver model instead of ASIO. If the WDM (Windows Classic) drivers are hosed, then you won't have it as a choice in ACID or listed in the "Sounds and Audio Devices" applet under Control Panel. Did any of you contact Echo on the matter?

Is there an uninstall routine you have to go through before installing newer or other drivers? I know I have to go through such a routine when installing newer Delta drivers or installing drivers for my M-Audio Duo.

HTH,
Iacobus

Subject:RE: V 4d sound manager issues

Reply by: dkistner

Date:6/10/2003 10:13:37 AM

When I go to install an updated Echo driver, it first uninstalls the earlier driver. Then I have to reinstall again, at which time it installs everything.

I'll send Echo the link to this thread. Doing that now. I'll let you know if I hear anything of importance.

Subject:Same problem, but...

Reply by: H2000

Date:6/10/2003 11:09:57 AM

I have the same problem since version 4c. I sometimes listen and make adjustments on my XP Home laptop using only the built in Yamaha Audio headphone outputs and I get the error now too. It never occured in any versions prior to 4c.

It will work fine for the first play, but then move the song position or do anything really, and next play is when the message comes up. Going back to the Audio Preferences tab and resetting the audio to Sound Mapper and hitting apply resets the problem and gives you one or two more plays before it happens again.

However, I did notice that the bit depth setting for me makes the error go away. Whereas before I could play the 24bit song on the Yamaha outputs with no error messages, now this error comes up. Setting the song bit depth to 16 bit causes the error to go away. I'm not even sure what the Yamaha outputs are, although my guess is that they are 16 bit, and thus the problem. The error message might be a little misleading though.

Are your bit depth settings correlated between Acid and your soundcard?

Subject:RE: Same problem, but...

Reply by: dkistner

Date:6/10/2003 5:38:54 PM

First, to answer that last question, I keep my Echo Mia locked to 44,100. I read that if you let Windows manage it, it can cause problems. I haven't been in the new Acid enough yet to have encountered any problems.

I got a quick reply from the Echo Audio folks about that "No Audio Device" thing:

> In my Control Panel/Sound Properties window, under the Volume tab, I
> show
\"No Audio Device.\" At first I thought this meant my Mia sound card was not being recognized, although it does seem to be working just fine. This started happening when I updated to the new 6.80 driver, as I recall.
>
> So the question is, does this message simply mean that the Echo
> Console
has seized control of the Windows Volume and this is nothing to worry about?

- Yes, you only want to use your Mia console. Start / Programs / Echo Digital Audio / Console3

Does it indicate the need to do anything?

- No.

Subject:RE: Same problem, but...

Reply by: pwppch

Date:6/11/2003 8:04:23 AM

>>However, I did notice that the bit depth setting for me makes the error go away. Whereas before I could play the 24bit song on the Yamaha outputs with no error messages, now this error comes up. Setting the song bit depth to 16 bit causes the error to go away. I'm not even sure what the Yamaha outputs are, although my guess is that they are 16 bit, and thus the problem. The error message might be a little misleading though.
<<
This is a known problem in ACID 4.0c/d. We are working on a fix and will release an update as soon as it is completed. No, I don't know when that will be.

The work around is to work only in 16 bit mode in ACID for Classic Wave Drivers.

Peter

Subject:RE: Same problem, but...

Reply by: MyST

Date:6/13/2003 9:36:40 PM

Add my name to the list of Mia owners this is happening to. :(
Just bought/downloaded my Pro 4.0 tonight. :)

Subject:RE: Same problem, but...

Reply by: aress

Date:6/15/2003 11:46:39 AM

since the 4d update, i have have had more weird issues with my trusty old MIA card...

all seem to be related to sound manager... but since i am still using vegas 3 i cant use asio and run both programs at the same time....

i have updated the recent drivers on ECHOAUDIO, but these WDM issues keep cropping up...

Subject:RE: Same problem, but...

Reply by: dkistner

Date:6/16/2003 8:23:24 AM

Did I hear that wrong? You're trying to run two different ASIO programs at the same time? I know you can't do that. It has nothing to do with Acid. I have to stop the audio (and release the ASIO driver) in Chainer, for example, before I can open a wave file in Cool Edit. Otherwise, I get very weird errors.

I'm using the Echo Pure Wave drivers, rather than WDM. I think Peter was saying these work the best in Acid. The only time I have any trouble is when I'm trying to change a bunch of things while I'm playing back audio...and then I'll crash. But that happens in any program I'm working in. I have to get in the habit of stopping/restarting playback when I'm adding effects and such.

Subject:RE: Same problem, but...

Reply by: spongebob

Date:6/16/2003 9:44:02 AM

Somewhat related to this topic- I recently got a MIA, and since the Echo drivers seize control over the Wondows volume, I can no longer use the handy volume knob on my pc keyboard. Is there a way to assign the volume in the MIA console to my pc keyboard?

Subject:RE: V 4d sound manager issues

Reply by: aress

Date:6/18/2003 2:23:57 PM

looks like this issue is cropping up with other users...............

Subject:RE: V 4d sound manager issues

Reply by: Spheris

Date:6/18/2003 3:59:40 PM

No kidding...
apparently alot of other users.