Problem getting m4a to play (trancoded?) on Transporter

[rickwookie]

If I try to "play" a duff track for about 30 seconds I get this:

https://pastebin.com/zxqpNhMu

and the play time counter seems to tick up as if it's playing, but there's no sound (or movement of the VU visualiser). This is what I get with the old faad too.
The faad processes seem to be still running after I stop playback (and even switch the player into standby). With the new faad build, I get this:



and with the old bundled build swapped back in I get this (a while after stopping attempted playback and switching transporter into standby):



Note the high cifsd usage too, suggesting that a file is still being accessed from my NAS (samba share)?

[rickwookie]

NEW INFORMATION ALERT!!!

Playing around switching between the old and new build again... and now it works!!!

Does the system somehow cache the faad binary??? Because all I did was reboot the Pi between the last attempt and this one (to kill that 100% cpu gobbling faad process).

Anyway, the headline is THE NEW BUILD FIXES WHATEVER THE PLAYBACK ISSUE WITH THOSE ROGUE ITUNES TRACKS.

I wonder why the faad process(es) never terminate(s). And why are there two faad processes running?

This is minutes after stopping all players, putting them all into standby, and clearing all playlists (playback queues)...




I appreciate this is a different issue. but now I know it's there (gobbling up my Pi's CPU resources for no apparent reason) it would be nice if there was a fix for that too.

edit: Is it that LMS never closes faad once opened, and just pipes streams through it as it needs, and thus I was not actually using the new build until I rebooted (or restarted LMS)? If that's the case, what's cifs still doing after playback ends that's so heavy?

[rickwookie]

Ok. Ignore all that. After another reboot and lots more playing of various combinations of m4a and flac and stopping and turning off during playback, etc. I can't get it to repeat that behaviour at all, so all is good.

Consider the newer faad build worth including with LMS for sure.

Thanks bpa and ralphy for looking at this.

I suppose those duff iTunes tracks are still not "right" (since other old tools have issues with them too), but that's not something that can ever get fixed (certainly not here anyway).

[ralphy]

That's great news!

Just to confirm your rpi is running debian wheezy?

And what rpi model are you using?

[rickwookie]

That's great news!

Just to confirm your rpi is running debian wheezy?

And what rpi model are you using?

Yes, Pi 2 B on Wheezy

root@SqueezePlug:~# cat /etc/debian_version
7.11
root@SqueezePlug:~# cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 7 (wheezy)"
NAME="Raspbian GNU/Linux"
VERSION_ID="7"
VERSION="7 (wheezy)"
ID=raspbian
ID_LIKE=debian
ANSI_COLOR="1;31"
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
root@SqueezePlug:~# uname -a
Linux SqueezePlug 4.9.68-v7+ #1064 SMP Tue Dec 12 15:08:24 GMT 2017 armv7l GNU/Linux
root@SqueezePlug:~# cat /proc/cpuinfo|grep Revision
Revision        : a01041

[ralphy]

Thanks for confirming.

I'll create a pull request for the newer faad binaries for lms 8.0 in the next few days, provided no other issues arise.

[ralphy]

I'll create a pull request for the newer faad binaries for lms 8.0 in the next few days, provided no other issues arise.

The updated faad binaries are included in LMS 8.0 builds from March 3rd.