Slackware - ARMThis forum is for the discussion of Slackware ARM.
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. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page 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.
Click Here to receive this Complete Guide absolutely free.
Yeah that's fine, but my Wolfson Audio Card SPDIF is alsa...
---------- Post added 06-06-14 at 12:20 PM ----------
Here's the first reply I had from mplayer mailing list:
Did you try capturing with -dumpstream and then playing that file?
I doubt your local files are in WMA format, in which case the comparison
doesn't make sense.
Also cpu frequency scaling unless you have disabled it will result in
CPU usage numbers being completely misleading.
The commands "perf record mplayer ..." and then after it is finished
"perf report" will tell where all the CPU time is used.
Also, which MPlayer version you are using would be helpful information.
However with the ridiculously outdated CPU of the Pi that kind of CPU
usage is most likely as expected, as it doesn't even include NEON,
which causes issues for the data conversions required.
In addition if whatever distribution you uses uses "softfloat" instead
of "hardfloat" that is likely to cost you a significant amount of
performance, as well as if your MPlayer isn't compiled specifically
for it (runtime CPU detection is a mess and basically does not work
on ARM, as a result generic distribution binaries a generally useless
I think this is to be expected since all of the maths is done in software rather than being offloaded to a FPU.
Stuart, I guess that that is what was meant by the hard float/soft float issue that was mentioned in the reply from the mplayer mailing list?
I'm guessing that it is using soft, since when I tried compiling omxplayer I had to specifically set it to 'soft'. Is it something that is set in gcc and all compiled apps have to follow that, or can some apps be made to use a hard float? Does a Pi even have a math co-processor?