Metro 2033 Redux

Metro 2033 Redux

データを表示:
Linux no sound (solved)
Game runs but with no sound. There is any option I can pass to the executable to save a log file? When I exit the game I can see a log, for a second, with fails in audio subsystem, but I can't read it.


Same with Last Light Redux.

My Linux box is a openSuSE 13.2 with KDE 4. I also have Metro Last Light (no redux) and it runs fine.
最近の変更はLord_LTが行いました; 2014年12月13日 9時38分
< >
1-15 / 18 のコメントを表示
+1


Running Manjaro x64 with Pulseaudio.
+1

opensuse 13.2 x86-64, kde4
I also have no sound on opensuse 13.1 with an intel sound chip and pulse audio. I also managed to capture the log output when exiting the game: http://i.imgur.com/SLOu35b.png
Over at the Last Light forums I found a fix for the no sound issue and it worked for me:


Simply right click on Metro in your library and choose properties.
Open up "set launch options..."
Enter the following line :
SDL_AUDIODRIVER=alsa %command%
salzpeter の投稿を引用:
Over at the Last Light forums I found a fix for the no sound issue and it worked for me:


Simply right click on Metro in your library and choose properties.
Open up "set launch options..."
Enter the following line :
SDL_AUDIODRIVER=alsa %command%

Returned sound for me, but stuttering and lagging and causing a huge performance drop :<
This solution works, but I have glitches in sound, that is caused by alsa driver throw pulseaudio and back. To solve this, and performace drop, you may to create a file in your $HOME directory called '.asoundrc' with this content:

pcm.!default { type hw card 0 device 0 } ctl.!default { type hw card 0 device 0 }


In my case, I have multiple output devices like a USB Headphones or HDMI output throw graphics card, so I have to change the card numer and device number for each device. Use of the command 'aplay -l' lists cards and devices. For example, if you have an optical output in your motherboard and you wish to use it with this game, the output of this command lists has this:

$> aplay -l **** List of PLAYBACK Hardware Devices **** card 0: SB [HDA ATI SB], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: SB [HDA ATI SB], device 1: ALC892 Digital [ALC892 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0

so, you must change device number to 1, and if you have a secondary sound card, it will be listed has "card 1".

That's all.

最近の変更はLord_LTが行いました; 2014年12月13日 9時32分
salzpeter の投稿を引用:
Over at the Last Light forums I found a fix for the no sound issue and it worked for me:


Thanks a huge bunch, that solved it for me! Appears that the game(s) lack Pulseaudio support through SDL and need to be forced to use ALSA to get sound to work.

Takios の投稿を引用:
Returned sound for me, but stuttering and lagging and causing a huge performance drop :<

I used to have the same issues you describe when forcing ALSA through Pulseaudio. It took some work to tweak Pulseaudio/ALSA/SDL properly. I wish I could offer a step-by-step guide, but as I did it a long time ago I can't remember much else other than trying out different settings according to this guide: https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skips_or_crackling

(Regardless of which Linux distro you use, the configuration of PulseAudio is pretty much the same, what might differ is the location of the various configuration files)
Lord_LT の投稿を引用:
This solution works, but I have glitches in sound, that is caused by alsa driver throw pulseaudio and back. To solve this, and performace drop, you may to create a file in your $HOME directory called '.asoundrc' with this content:

pcm.!default { type hw card 0 device 0 } ctl.!default { type hw card 0 device 0 }


This worked for me though I don't understand why. As far as I can tell it just says which device alsa should use?

Takios の投稿を引用:
Lord_LT の投稿を引用:
This solution works, but I have glitches in sound, that is caused by alsa driver throw pulseaudio and back. To solve this, and performace drop, you may to create a file in your $HOME directory called '.asoundrc' with this content:

pcm.!default { type hw card 0 device 0 } ctl.!default { type hw card 0 device 0 }


This worked for me though I don't understand why. As far as I can tell it just says which device alsa should use?

Using this file overrides use of pulseaudio and send sound directly to hardware specified in file. You can list your sound cards and devices using 'aplay -l' command. You can find more information about this file in the alsa project page.
Lord_LT の投稿を引用:
Takios の投稿を引用:


This worked for me though I don't understand why. As far as I can tell it just says which device alsa should use?

Using this file overrides use of pulseaudio and send sound directly to hardware specified in file. You can list your sound cards and devices using 'aplay -l' command. You can find more information about this file in the alsa project page.



It doesn't works for me (Xubuntu 14.04, Sound Blaster X-Fi Titanium "Module-snd-ctxfi" ).

device 0, causes an error in alsamixer: "cannot open mixer: Invalid argument"
(it works if I remove "device 0")



Anyway, glitches in sound still remain.


The card is a SoundBlaster XFI Titanium; if i use the integrated one, a Realtek ALC887 instead, no glitch.


Unfortunately, I must admit that my SoundBlaster, problems aside, it sounds much better than the integrated card, is the only reason why I still use.



Solutions?

---------------------
SOLVED

Solving Creative Sound Blaster X-Fi Titanium crackling/distortion on Linux

Jun 4 2013

I own a Creative Sound Blaster X-Fi Titanium Fatal1ty soundcard, an awesome piece of hardware, though I’ve always experienced audio issues with it on Linux (damn drivers!).
My research showed that those bugs are a result of interactions between Pulseaudio and ALSA, and that the available fixes do not work for everyone. I’m glad they do work for me.

The trick is disabling PulseAudio’s timer-based scheduling. Fire up the terminal, then type:

sudo nano /etc/pulse/default.pa

Look for the line that contains load-module module-udev-detect, and append tsched=0 to it. Now it should look like this:

load-module module-udev-detect tsched=0

Save the buffer and exit the editor, then restart PulseAudio with the following commands:

pulseaudio -k
pulseaudio --start

Now your audio should be crystal clear. If it’s not, you will probably need to use another fix. Yeah, that sucks. :P

Source:
https://guh.me/solving-creative-sound-blaster-x-fi-titanium-crackling-slash-distortion-on-linux
最近の変更はSoma/Talosが行いました; 2016年7月23日 9時02分
This thread helped me get sound working and I thank everyone here for that. However, after that first time I got to play, I have not been able to get the sound working again. I have the .asoundrc in my home folder, and I have the prefix as stated in my startup options for the game. Has anyone else had the problem come back after these steps? If so, how did you work them out?
Well, I just figured out that I need to do `pulseaudio -k` first to free up the device. Has anyone tried enabling dmix while using pulse? I'm thinking about trying that just for this game.
Strange, it's been working ever since I tried this workaround the first time, without any need to free up the seound device first.

I'm hoping the linux version will get proper pulseaudio support anytime soon though.
Solving Creative Sound Blaster X-Fi Titanium crackling/distortion on Linux

Jun 4 2013

I own a Creative Sound Blaster X-Fi Titanium Fatal1ty soundcard, an awesome piece of hardware, though I’ve always experienced audio issues with it on Linux (damn drivers!).
My research showed that those bugs are a result of interactions between Pulseaudio and ALSA, and that the available fixes do not work for everyone. I’m glad they do work for me.

The trick is disabling PulseAudio’s timer-based scheduling. Fire up the terminal, then type:

sudo nano /etc/pulse/default.pa

Look for the line that contains load-module module-udev-detect, and append tsched=0 to it. Now it should look like this:

load-module module-udev-detect tsched=0

Save the buffer and exit the editor, then restart PulseAudio with the following commands:

pulseaudio -k
pulseaudio --start

Now your audio should be crystal clear. If it’s not, you will probably need to use another fix. Yeah, that sucks. :P

Source:
https://guh.me/solving-creative-sound-blaster-x-fi-titanium-crackling-slash-distortion-on-linux

Thanks its work!
最近の変更はatterratioが行いました; 2019年8月1日 5時41分
Bounteous 2019年8月21日 15時39分 
In case you are using Archlinux, Manjaro or any other distribution based on Arch, you need to install "pulseaudio-alsa" for this solution.

pacman -S pulseaudio-alsa

They also recommend installing 32 bits support

pacman -S lib32-libpulse lib32-alsa-plugins

More info: https://wiki.archlinux.org/index.php/PulseAudio#ALSA

If you doesn't install that packages "/etc/asound.conf" and ".asoundrc", these files will not do anything.

I can confirm the solution works on linux-5.3 and nvidia-430, running Manjaro with i3wm over Xorg.

Faeyben の投稿を引用:
Lord_LT の投稿を引用:
This solution works, but I have glitches in sound, that is caused by alsa driver throw pulseaudio and back. To solve this, and performace drop, you may to create a file in your $HOME directory called '.asoundrc' with this content:

pcm.!default { type hw card 0 device 0 } ctl.!default { type hw card 0 device 0 }


This worked for me though I don't understand why. As far as I can tell it just says which device alsa should use?
< >
1-15 / 18 のコメントを表示
ページ毎: 1530 50