Prboom and doomsdays sound delay problems?

I recently started playing Doom2 on Linux using the prboom engine
and I’ve noticed some really strange behavior with the sound. If I
start the program as a non-root user there is about a 3/4 second
delay for all the sound effects. If I start the program as room the
sound delay goes away. I just figured this was a bug with prboom, so
I just play the game as root.

However, yesterday I picked up the Doomsday engine. I realize that
it has the exact same audio delay problems. So now I’m thinking
perhaps it’s not a problem with the engine, but maybe it’s a problem
with SDL? Is there some way I can test this?

I’m running a pretty vanilla copy of Fedora Core 3. I’m able to
reproduce the problem on two different installations even.

http://www.doomsdayhq.com/files.php?pro=1
http://prboom.sourceforge.net/

Scott Baker wrote:

I recently started playing Doom2 on Linux using the prboom engine and
I’ve noticed some really strange behavior with the sound. If I start the
program as a non-root user there is about a 3/4 second delay for all the
sound effects. If I start the program as room the sound delay goes away.
I just figured this was a bug with prboom, so I just play the game as root.

that long of a delay is typical when using a sound daemon like artsd or esd.
also, perhaps the daemons have suid privs for the /dev/dsp where the user doesn’t
have access directly to the /dev/dsp… so check file permissions.

-LIM-

Is there an easy to test that? Is there a simple application I can
use to play a sound, or a simple demo that outputs some sound that I
can check the latency with?

Scott

Jonathan Atkins wrote:> Scott Baker wrote:

I recently started playing Doom2 on Linux using the prboom engine and
I’ve noticed some really strange behavior with the sound. If I start
the program as a non-root user there is about a 3/4 second delay for
all the sound effects. If I start the program as room the sound delay
goes away. I just figured this was a bug with prboom, so I just play
the game as root.

that long of a delay is typical when using a sound daemon like artsd or
esd.
also, perhaps the daemons have suid privs for the /dev/dsp where the
user doesn’t
have access directly to the /dev/dsp… so check file permissions.

-LIM-


SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl

Just run: ps -auxww|egrep 'artsd|esd’
and to check the device permissions: ls -la /dev/dsp
then: id
see if any groups from the id command match the dsp and the the dsp has group writability.
also export ESD_NO_SPAWN=1
to prevent SDL from starting esd
you may also wish to use an alternate dsp if you have two sound cards…: export SDL_PATH_DSP=/dev/dsp
of course, you’d need to specify the proper dsp device.

Scott Baker wrote:> Is there an easy to test that? Is there a simple application I can use

to play a sound, or a simple demo that outputs some sound that I can
check the latency with?

Scott

Jonathan Atkins wrote:

Scott Baker wrote:

I recently started playing Doom2 on Linux using the prboom engine and
I’ve noticed some really strange behavior with the sound. If I start
the program as a non-root user there is about a 3/4 second delay for
all the sound effects. If I start the program as room the sound delay
goes away. I just figured this was a bug with prboom, so I just play
the game as root.

that long of a delay is typical when using a sound daemon like artsd
or esd.
also, perhaps the daemons have suid privs for the /dev/dsp where the
user doesn’t
have access directly to the /dev/dsp… so check file permissions.

-LIM-


SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl


SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl