Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Problem with Direct Sound output (Read 4690 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Problem with Direct Sound output



When I use DS: Speakers (Realtek) output for playback, some programs that requre DS fail to work:
DS could not be started or DSound - Failed to start output buffer. Unknown error 0x88890000a

Also when changing the outputs i.e. from DS: Speakers (Realtek) to DS: Primary Driver and back a get this in console:
IDirectSoundBuffer::Play() failed : 8889000A
which is the same error that one of the programs reported

Using any other output device is OK, so I don't know if it's driver related (latest generic Realtek driver) or foobar related?

Problem with Direct Sound output

Reply #1 –
Well, no one replied, but I still have this problem.

i.e. today I was playing some music and after some time foobar just repeats 1-2 sec from track, ad infinitum. I close foobar, than start it again, but now it won't play it just freezes. I try with other players and they freeze too. So something happened with my DS and I must restart PC.

I can reproduce buggy behaviour when foobar is running and I launch Reason - than Reason can't accept nether DS nor ASIO4ALL, and I must exit foobar. It also happens with Cantabile host.

Perhaps the problem is with the driver (generic Realtek - 6.0.1.5911), and I don't want to use dedicated Realtek driver because it lacks Stereo mix and some other things. And this saying in case it's really driver problem, but I don't have problems with other audio programs and use only foobar for playback, so not sure enough.

Any thoughts?

Problem with Direct Sound output

Reply #2 –
I can't reproduce your problems. I installed the same driver on my Asus P5K motherboard with Realtek ALC883 on Windows 7 RC. I don't have Reason or Cantable, but I do have Cool Edit Pro. I methodically swapped outputs for the OS, Foobar, and Cool Edit, trying to cause a failure, but no success. All combinations work.

My thoughts:

1) Check the properties for your speakers. In Win7 there's Playback Devices / Advanced tab (I'm not sure about other OS's). These are the options I have enabled. See if changing your settings helps.
(a) For default format you can choose anything from 16bit/44.1K to 24bit/192K. I have chosen 24bit/48K.
(b) For exclusive mode, I have both options enabled: "Allow apps to take exclusive control" and "Give exclusive mode apps priority"

2) List your OS, motherboard, and Realtek chip in your next post. Maybe someone reading this thread will recognize your configuration.

3) Google your OS, mobo, Realtek chip, and driver version to see if any others are having similar problems.

4) Roll back to the original driver for your Realtek chip. If that works, I'm inclined to think the generic driver is at fault.
That's so plausible, I can't believe it.

Problem with Direct Sound output

Reply #3 –
Thank you for your reply
I'm not in a position to post meaningfully right now but here is something quick:

1. I have the same setting as you posted, and I did try to tweak those settings

2.
Code: [Select]
Mainboard :	945GCM-S (I had ASUS but this isn't ASUS - [url=http://www.asrock.com/MB/overview.asp?Model=945GCM-S]ASRock[/url] )
Chipset :	Intel i945G/GZ
Operating System :	Windows 7 Ultimate Professional 6.01.7127 
DirectX :	Version 10.00

Device Audio :	82801G (ICH7 Family) High Definition Audio Controller
	High Definition Audio Information :
	Version :	1.0 
	Output Stream :	4 
	Input Stream :	4 
	Bidirectionnal Stream :	No 
	64-bit support :	Yes 
	Mode :	High Definition Audio (HDA) 

	High Definition Audio Information :
	Version :	1.0 
	Output Stream :	4 
	Input Stream :	4 
	Bidirectionnal Stream :	No 
	64-bit support :	Yes 
	Mode :	High Definition Audio (HDA) 
	Manufacturer :	Realtek 
	Codec ID :	10EC0662 
	Codec Revision :	1.001

Device Audio :	82801G (ICH7 Family) High Definition Audio Controller
Audio Playback :	Speakers (SRS Audio Sandbox (WDM))
Audio Playback :	Speakers (Realtek High Definitition)
Audio Playback :	Microsoft Sound Mapper
Audio Recording :	Stereo Mix (Realtek High Definition)
Audio Recording :	Line In (Realtek High Definition)
Audio Recording :	Microphone (2- USB Audio Device)
Audio Recording :	Microphone (Realtek High Definition)
MIDI Output :	Microsoft GS Wavetable Synth
MIDI Output :	Out To MIDI Yoke:  1
MIDI Output :	Out To MIDI Yoke:  2
MIDI Output :	Out To MIDI Yoke:  3
MIDI Output :	Out To MIDI Yoke:  4
MIDI Output :	Out To MIDI Yoke:  5
MIDI Output :	Out To MIDI Yoke:  6
MIDI Output :	Out To MIDI Yoke:  7
MIDI Output :	Out To MIDI Yoke:  8
MIDI Output :	Microsoft MIDI Mapper
MIDI Input :	In From MIDI Yoke:  1
MIDI Input :	In From MIDI Yoke:  2
MIDI Input :	In From MIDI Yoke:  3
MIDI Input :	In From MIDI Yoke:  4
MIDI Input :	In From MIDI Yoke:  5
MIDI Input :	In From MIDI Yoke:  6
MIDI Input :	In From MIDI Yoke:  7
MIDI Input :	In From MIDI Yoke:  8
Mixer Device :	Speakers (SRS Audio Sandbox (WDM))
Mixer Device :	Speakers (Realtek High Definition)
Mixer Device :	Line In (Realtek High Definition)
Mixer Device :	Stereo Mix (Realtek High Definition)
Mixer Device :	Microphone (2- USB Audio Device)
Mixer Device :	Microphone (Realtek High Definition)
I use 4 channel output (channel mixer DSP)

3. I'll do that

4. I'll try that also to isolate the problem. And I don't want to go back to dedicated Realtek driver as I mentioned, because I use the features from generic driver that are lacking from Win7 driver for my soundcard

Screenshot of error when running foobar and trying to start Cantabile i.e. (Reason don't display errors only I can't select any audio device for output):

Problem with Direct Sound output

Reply #4 –
Just to report that the problem was in SRS Sandbox driver, which I didn't even use and don't really know why I installed it.
Removing the driver solved my problem