LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   w32 codec fix seems to have killed my audo playback (https://www.linuxquestions.org/questions/linux-hardware-18/w32-codec-fix-seems-to-have-killed-my-audo-playback-508979/)

tokyo_ 12-09-2006 10:10 PM

w32 codec fix seems to have killed my audo playback
 
i was searching around for a fix for playing .wmv files when i stumbled upon this

https://help.ubuntu.com/community/Re...mats#w32codecs

after following the directions:

Quote:

wget -c http://www.debian-multimedia.org/poo...2-0.0_i386.deb
sudo dpkg -i w32codecs_20061022-0.0_i386.deb
everything was working fine for about 5 minutes, then i noticed that the audio track to the video i was viewing cut out. i thought it was just the file, so i went to a few audio players to see if the rest of the sound was out, turns out, any mp3 i attempted to play came out as silence.

i rebooted my computer, hoping it was a fluke, but no start up jingle, and still no audio playback.

when i adjust the volume very quickly up and down, i can hear the static in the line from it adjusting, so i know it's not my speakers.

if anyone has help or can point me in a better direction, it would be appreciated.

i am using Ubuntu 6.06

-cheers

PatrickNew 12-09-2006 10:18 PM

I occasionally have problems with MPlayer grabbing ahold of my sound driver and refusing to let go. Was MPlayer the video player? Try opening a terminal and typing "ps -A" and see if you find anything with "mplayer" in the name. If you do, then notice the number (4 or 5 digits) next to it and type "kill -9 " followed by that number. That may fix it, if somehow Mplayer is autoloading itself at boot.

tokyo_ 12-09-2006 10:29 PM

Quote:

Originally Posted by PatrickNew
I occasionally have problems with MPlayer grabbing ahold of my sound driver and refusing to let go. Was MPlayer the video player? Try opening a terminal and typing "ps -A" and see if you find anything with "mplayer" in the name. If you do, then notice the number (4 or 5 digits) next to it and type "kill -9 " followed by that number. That may fix it, if somehow Mplayer is autoloading itself at boot.

i was using 'xine movie player' which i came to understand is just a frontend for xine, but i'm not really knowledgeable about that.

anyhow, i did just as you said and this was the result:

Quote:

PID TTY TIME CMD
1 ? 00:00:00 init
2 ? 00:00:00 ksoftirqd/0
3 ? 00:00:00 watchdog/0
4 ? 00:00:00 events/0
5 ? 00:00:00 khelper
6 ? 00:00:00 kthread
8 ? 00:00:00 kblockd/0
9 ? 00:00:00 kacpid
121 ? 00:00:00 pdflush
122 ? 00:00:00 pdflush
124 ? 00:00:00 aio/0
123 ? 00:00:00 kswapd0
711 ? 00:00:00 kseriod
1813 ? 00:00:00 khubd
1825 ? 00:00:00 khpsbpkt
1852 ? 00:00:00 knodemgrd_0
1925 ? 00:00:00 kjournald
2154 ? 00:00:00 udevd
2925 ? 00:00:00 shpchpd_event
2974 ? 00:00:00 pccardd
2996 ? 00:00:00 kacpid-work-0
3010 ? 00:00:00 kgameportd
3240 ? 00:00:00 wrapper_wq
3920 ? 00:00:00 acpid
4007 ? 00:00:00 syslogd
4033 ? 00:00:00 dd
4035 ? 00:00:00 klogd
4355 ? 00:00:00 gdm
4372 ? 00:00:00 gdm
4389 tty7 00:01:17 Xorg
4396 ? 00:00:00 hpiod
4412 ? 00:00:00 python
4463 ? 00:00:00 cupsd
4488 ? 00:00:00 dbus-daemon
4503 ? 00:00:01 hald
4504 ? 00:00:00 hald-runner
4509 ? 00:00:00 hald-addon-acpi
4563 ? 00:00:00 hald-addon-keyb
4573 ? 00:00:00 hald-addon-stor
4574 ? 00:00:00 hald-addon-stor
4598 ? 00:00:00 dhcdbd
4615 ? 00:00:00 NetworkManager
4634 ? 00:00:00 avahi-daemon
4635 ? 00:00:00 avahi-daemon
4654 ? 00:00:00 NetworkManagerD
4688 ? 00:00:00 powernowd
4748 ? 00:00:00 hcid
4752 ? 00:00:00 sdpd
4769 ? 00:00:00 krfcommd
4782 ? 00:00:00 mdadm
4817 ? 00:00:00 atd
4833 ? 00:00:00 cron
4930 tty1 00:00:00 getty
4931 tty2 00:00:00 getty
4932 tty3 00:00:00 getty
4933 tty4 00:00:00 getty
4934 tty5 00:00:00 getty
4935 tty6 00:00:00 getty
4981 ? 00:00:00 dhclient
4994 ? 00:00:00 dhclient3
5001 ? 00:00:00 gnome-session
5044 ? 00:00:00 ssh-agent
5047 ? 00:00:00 dbus-launch
5048 ? 00:00:00 dbus-daemon
5050 ? 00:00:01 gconfd-2
5053 ? 00:00:00 gnome-keyring-d
5055 ? 00:00:00 bonobo-activati
5057 ? 00:00:02 gnome-settings-
5061 ? 00:00:00 esd
5067 ? 00:00:01 vino-server
5070 ? 00:00:13 metacity
5077 ? 00:00:07 nautilus
5079 ? 00:00:12 gnome-panel
5080 ? 00:00:01 gnome-volume-ma
5086 ? 00:00:00 dhclient3
5096 ? 00:00:00 update-notifier
5099 ? 00:00:00 gnome-vfs-daemo
5103 ? 00:00:02 gnome-cups-icon
5113 ? 00:00:01 nm-applet
5117 ? 00:00:01 gnome-screensav
5119 ? 00:00:02 checkgmail
5125 ? 00:00:01 gnome-window-de
5139 ? 00:00:00 gnome-power-man
5141 ? 00:00:02 mixer_applet2
5144 ? 00:00:00 mapping-daemon
5150 ? 00:00:00 clock-applet
5153 ? 00:00:01 gweather-applet
5308 ? 00:00:00 swiftfox
5311 ? 00:00:00 run-mozilla.sh
5316 ? 00:02:03 swiftfox-bin
5327 ? 00:00:00 netstat <defunct>
6443 ? 00:00:04 hal-device-mana
6742 ? 00:00:13 gnome-search-to
6834 ? 00:00:00 xterm
6835 pts/0 00:00:00 bash
6949 pts/0 00:00:00 ps
nothing about mplayer and/or xine in there from what i can tell. any ideas?

tokyo_ 12-10-2006 02:50 AM

thank you for your response patrick, i seemed to have solved this issue (rather embarrassing really)

just in case anyone else has tried to install w32 drivers and run into the same issue i'll tell you what happened.

turns out the PCM volume was muted (by default PCM does not show in the volume control, you have to enable it in the preferences) when i installed the w32 drivers and started watching .wmv files.

i have no idea how or why this came about as an issue, but if you run into this, make sure you check ALL the volume levels.

PatrickNew 12-10-2006 11:51 AM

glad you fixed it, sorry for the red herring :-)


All times are GMT -5. The time now is 08:35 AM.