The official "ZDoom on Linux" thread.

Handy guides on how to do things, written by users for users.
Forum rules
Please don't start threads here asking for help. This forum is not for requesting guides, only for posting them. If you need help, the Editing forum is for you.
User avatar
Grubber
Posts: 1031
Joined: Wed Oct 15, 2003 12:19 am
Location: Czech Republic

Post by Grubber »

Try running "zdoom +snd_output oss".
Top
User avatar
Mannequin
Posts: 441
Joined: Tue Jul 15, 2003 8:21 pm
Location: On The Lonely Island somewhere.

Post by Mannequin »

Any reason not to use ALSA? Is ALSA even an option?

I've tried FMOD, ESD, ALSA, and OSS, but none of them work properly. FMOD and OSS give the same very choppy sound. ALSA does nothing. ESD is very, very delayed.

Any other options that might make a difference?

-M.
Top
stinkball
Posts: 2
Joined: Sun Feb 11, 2007 9:11 pm

FMOD

Post by stinkball »

I'm having trouble compiling zdoom under ubuntu 6.10. The only problem seems to be fmodsound.cpp. I followed grubbers instructions at the beginning of the thread, and still end up with an fmod problem. the output is in the spoiler.
Spoiler:
Top
User avatar
Mannequin
Posts: 441
Joined: Tue Jul 15, 2003 8:21 pm
Location: On The Lonely Island somewhere.

Post by Mannequin »

I'm having trouble compiling zdoom under ubuntu 6.10. The only problem seems to be fmodsound.cpp. I followed grubbers instructions at the beginning of the thread, and still end up with an fmod problem. the output is in the spoiler.
:arrow: My advise is to do this (which is just a modification of Grubber's):

Code: Select all

cd /opt

#download fmod
wget http://www.fmod.org/files/fmodapi375linux.tar.gz

#extract files from the archive
tar -xzf fmodapi375linux.tar.gz

#we don't need the archive anymore
rm fmodapi375linux.tar.gz

#create links so that the system know about fmod
ln -s /opt/fmodapi375linux/api/libfmod-3.75.so /usr/lib/libfmod.so
ln -s /opt/fmodapi375linux/api/inc /usr/include/fmod

#create <fmod.h>
echo '#include <fmod/fmod.h>' > /usr/include/fmod.h
Many times, in my experience, if you haven't included the '/opt/' portion when you make the symlink, it creates a bad symlink. Doing this ensures that it knows where the 'fmodapi375linux' directory is.

:arrow: The other way would be to *copy* 'libfmod-3.75.so' directly to '/usr/lib' and in the process rename it to 'libfmod.so':

Code: Select all

sudo cp /opt/fmodapi375linux/api/libfmod-3.75.so /usr/lib/libfmod.so
Also something similar to the 'inc' directory:

Code: Select all

sudo mkdir /usr/include/fmod
sudo cp -r /opt/fmodapi375linux/api/inc/ /usr/include/fmod/
Now the whole process of creating *copies* instead of *symlinks*:

Code: Select all

#download fmod
wget http://www.fmod.org/files/fmodapi375linux.tar.gz

#extract files from the archive
tar -xzf fmodapi375linux.tar.gz

#we don't need the archive anymore
rm fmodapi375linux.tar.gz

#create COPIES so that the system knows about fmod
sudo cp /opt/fmodapi375linux/api/libfmod-3.75.so /usr/lib/libfmod.so
sudo mkdir /usr/include/fmod
sudo cp -r /opt/fmodapi375linux/api/inc/ /usr/include/fmod/

#create <fmod.h>
echo '#include <fmod/fmod.h>' > /usr/include/fmod.h
After doing that, you can then get rid of the 'fmodapi375linux' directory located in '/opt'.
HTH,
-M.
Top
stinkball
Posts: 2
Joined: Sun Feb 11, 2007 9:11 pm

Post by stinkball »

thanks, worked great, runs (so far) no problems.
Top
User avatar
Mannequin
Posts: 441
Joined: Tue Jul 15, 2003 8:21 pm
Location: On The Lonely Island somewhere.

Post by Mannequin »

Good, glad to hear it. :)

-M.
Top
User avatar
Csonicgo
Posts: 1193
Joined: Thu Apr 15, 2004 3:28 pm
Location: Leeds

Post by Csonicgo »

That fmod garbage never ceases to amaze me.
Top
User avatar
Mannequin
Posts: 441
Joined: Tue Jul 15, 2003 8:21 pm
Location: On The Lonely Island somewhere.

Post by Mannequin »

I agree with that...

-M.
Top
User avatar
Csonicgo
Posts: 1193
Joined: Thu Apr 15, 2004 3:28 pm
Location: Leeds

Post by Csonicgo »

Then why don't we just drop it? There has to be a better alternative than this propriatary might-work-might-not library. Fmod has been a total bitch in non-windows environments. The archive Fmod.org provides for their libraries are- you guessed it- LOCKED to normal users in Linux! Whoever thought of that idea, thanks a lot.

Seriously, the only thing that comes out of that library are loads of problems. Linux help forums are filled with "fmod troubles" or "I'm getting errors with sound" or "this application will not compile".

It's ridiculous. The only way I can compile zdoom is to put fmod.h in the /src/sound directory in my zdoom source folder.
Top
User avatar
randi
Site Admin
Posts: 7749
Joined: Wed Jul 09, 2003 10:30 pm

Post by randi »

Csonicgo wrote:Then why don't we just drop it?
Because it's awesome for Windows, and I'm not going to use something else just to appease the vast minority of users. Basically it's the reverse reason I won't use SDL for Windows.

Anyway, how is FMOD Ex? Why don't you try the samples that come with that and see how they work? It's supposed to be a complete rewrite, so hopefully it works better under Linux. (And if it doesn't, well, that's that.)

Edit: I've spent a little more time looking at FMOD Ex, and it looks if its standard Linux support isn't good enough, one can write an output plugin to use something else like SDL. That ought to satisfy the people complaining just because it doesn't work well enough for them.

Second edit: Just playing with the examples on Linux using VMWare, OSS output is terribly broken and choppy (which I attribute to the virtualization), but ALSA is perfect. I really do need to stop procrastinating and update.
Top
User avatar
Mannequin
Posts: 441
Joined: Tue Jul 15, 2003 8:21 pm
Location: On The Lonely Island somewhere.

Post by Mannequin »

Second edit: Just playing with the examples on Linux using VMWare, OSS output is terribly broken and choppy (which I attribute to the virtualization), but ALSA is perfect. I really do need to stop procrastinating and update.
It's horribly choppy and broken for me without VMWare. :)

I couldn't find anything that would work with it, either. When you say that you need to update, does that mean that you are going to upgrade ZDoom to work better with ALSA?

-M.
Top
User avatar
randi
Site Admin
Posts: 7749
Joined: Wed Jul 09, 2003 10:30 pm

Post by randi »

I mean update it to use FMOD Ex instead of FMOD. That should automatically bring better ALSA support.
Top
User avatar
Mannequin
Posts: 441
Joined: Tue Jul 15, 2003 8:21 pm
Location: On The Lonely Island somewhere.

Post by Mannequin »

I would be interested to see the results...

Although, I'd love to see SDL being used for Linux sound. I was playing another DOOM game (not too far from the original source release), and the sound (and graphics) using SDL were exactly what I expected. (Meaning they were great. ;) )

I'm not saying to move Winders to SDL here, just Linux. ;) :)

-M.
Top
env

Post by env »

Hi there, just thought I'd add my experiences.

Just compiled zdoom 2.7.1 (R336) on Debian etch having figured out I had to manually shift the fmod.h to the sound folder. Whenever I start zdoom sometimes I get no sound, others I do. It takes anywhere between 1 - 3 attempts of loading it before it works and then it cuts off after about 5 minutes. I can't be too sure if it's the same amount of time but it seems like it. Fairly sure it has nothing to do with a particular sound - I could stand still in a silent room and it'd still go.

Tryed running with +snd_output <just about every option>. Running without and with the param alsa has no effect. Neither does prefixing the whole command with aoss (aoss ./zdoom ...) which seems to fix my silent realplayer.

Any ideas whats going on here? Or is it another fmod peculiarity :?


Edit: Tryed compiling with fmod ex instead of fmod but it's incompatible with the zdoom source.
Top
User avatar
Grubber
Posts: 1031
Joined: Wed Oct 15, 2003 12:19 am
Location: Czech Republic

Post by Grubber »

It's fmod problem, there's probably nothing you can do about it.
Top

Return to “Tutorials”