Install Mplayer Debian Wheezy No Sound

A lot of the time, this can be traced to installing ffmpeg and its associated libavcodec52 library from debian-multimedia. If this is the case, pretty much the only solution for Squeeze is to recompile VLC against the debian-multimedia versions of libavcodec-dev, and I would also suggest using mplayer2 instead of mplayer, since it is pretty much immune to these library changes. At least that's what has solved similar issues in the Squeeze-based community repo I build packages for, though it comes with an ffmpeg 0.6.1 from upstream Debian that is close enough to debian-multimedia's that programs built against either one work fine--but Squeeze's VLC has lots of trouble with some codecs.

Installing OMXPlayer on Raspberry Pi. (Debian Wheezy). If there is no sound when playing through the HDMI interface make sure your /boot/config.txt file. There was sound the in the debian wheezy but i reinstalled the wheezy and now there is no sound and the players like smplayer and mplayer cannot play. A set of MM's. Hit M to unmute. If you started out from scratch with a new system you need to make sure the needed codecs and plugins are installed.

You may try the mplayer2 build, most mplayer front-ends such as SMPlayer allow you to specify 'mplayer2' as the mplayer binary to use. You want the 2.0~git201104.etc. Version, mcr110+1 will install into Squeeze without trouble. You can also rebuild your own deb packages of VLC 1.1.11 upon Squeeze from upstream Debian, see this method.

Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free.

Download Mp3 Super Junior M Swing Korean Ver on this page. Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions.org? Visit the following links: If you have any problems with the registration process or your account login, please. If you need to reset your password,. Having a problem logging in?

Please visit to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.

For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

To receive this Complete Guide absolutely free. Pulse audio lacks a few configuration files for a few cards. My delta 44 required the addition of 2 extra files created just for it. /usr/share/pulseaudio/alsa-mixer/profile-sets/via-ice1712.conf /etc/udev/rules.d/ice1712-pulseaudio-workaround.rules I cut and pasted these for the most part from another page. Obviously your card is not a delta 44 and requires different files and options.

Not sure if that helps but it should give you something to look for. ----- Alternatively stop running pulseaudio. In /etc/pulse/client.conf change or add 'autospawn = no' to prevent pulseaudio from automagically restarting when you stop it or kill it. Then switch between using and NOT using pulseaudio. $ nano /etc/pulse/client.conf $ pulseaudio --start $ pulseaudio --kill For some reason --stop doesn't seem valid, kind of lame imo. I'd recommend using pulseaudio even though I'm not a fan of it.

Your openjdk and other things are likely configured for it, and fail to do certain things if you don't use pulseaudio. Like in the game runescape all you get is the musak tracks and none of the sound effects if you don't use pulseaudio. Be sure to add the user to the audio group and the pulse, pulse-access groups. $ groups cdrom audio video games pulse pulse-access That being said pulseaudio does suck, it lacks many things many would consider deal breakers. If you run pulse, even pulse over jack for a software synth you will have a high latency because the sounds will be resampled before actually being outputted.

So having the option to opt out of pulseaudio is a good one. Other tricks are to rename your.asoundrc file if you have one. This should force things to use alsa natively. You can also have different versions of.asoundrc with the renaming trick depending on how you use your soundcard. One for pulse, one for alsa, one for jack, and so on. You might also try purging the.pulse folder and restarting pulse.

$ rm -rf.pulse* $ pulseaudio --kill $ pulseaudio --start Hope this helps. Make sure your sound levels are set which you seemed to have done. You can save your levels with alsa-ctl # alsa-ctl store And they should be restored at the next boot. It's saved to /var/lib/alsa/asound.state.

If you have another mixer application that your prefer that saves settings like aumix, you may want to delete that asound.state file so your settings will be restored. The debian boot sequence will restore mixer settings from asound.state if it exists and bypass aumix settings when both files / settings exist. I'm not a fan of 100% volume settings, a lot of cards distort noticeably when >90%. Quote: #mplayer -ao alsa:device=CMI8738-MC6 20051210-w50s.flv MPlayer2 UNKNOWN (C) 2000-2012 MPlayer Team mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Playing 20051210-w50s.flv. Detected file format: FLV format (libavformat) [flv @ 0xb5ebed00]Estimating duration from bitrate, this may be inaccurate [lavf] stream 0: video (vp6f), -vid 0 [lavf] stream 1: audio (mp3), -aid 0 VIDEO: [VP6F] 360x288 0bpp 25.000 fps 266.2 kbps (32.5 kbyte/s) Clip info: audiodelay: 0 canSeekToEnd: 1 creationdate: Fri Feb 03 11: Load subtitles in.

Code: [AO_ALSA] alsa-lib: pcm.c:2217snd_pcm_open_noupdate) Unknown PCM CMI8738-MC6 [AO_ALSA] Playback open error: No such file or directory Failed to initialize audio driver 'alsa:device=CMI8738-MC6'Did you typo this? Perhaps -CM6? Or is that what you named it in.asoundrc? In either case it cannot find it. And if you're setup for pulse it should be '-ao pulse' on the mplayer command. And/or those default settings in /etc/mplayer/mplayer.conf Will it work if you do something like this?

$ pulseaudio --kill $ mv ~/.asoundrc ~/.zzzasoundrc $ mplayer -ao alsa:device=hw,0 And don't forget to move.asoundrc back to it's former name. With adjustments if that somehow works for you. Because if it does work, then it is NOT a driver issue.

It is a system configuration issue. Note that mplayers syntax is a bit odd as it's not hw:0 like we would use with anything that is alsa. Cod4 Promod 204 Download Games. And where 0 is the number of the device you want to use (as listed in /proc/asound/cards) which may not be 0. For some things you can have a single line in.asoundrc if 0 is not your primary audio device. Quote: #mplayer -ao alsa:device=hw,0 20051210-w50s.flv MPlayer2 UNKNOWN (C) 2000-2012 MPlayer Team mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control.

Playing 20051210-w50s.flv. Detected file format: FLV format (libavformat) [flv @ 0xb5e90d00]Estimating duration from bitrate, this may be inaccurate [lavf] stream 0: video (vp6f), -vid 0 [lavf] stream 1: audio (mp3), -aid 0 VIDEO: [VP6F] 360x288 0bpp 25.000 fps 266.2 kbps (32.5 kbyte/s) Clip info: audiodelay: 0 canSeekToEnd: 1 creationdate: Fri Feb 03 11: Load subtitles in.