Just the chip in and report that I had exactly this happen to me today
on one of my Radios, using Logitech Media Server Version: 7.9.2. A
reboot of the Radio resolved it.
rickwookie's Profile:
ralphy wrote:
> 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
Code:
root@SqueezePlug:~# cat /etc/debian_version
7.11
root@SqueezePlug:~# cat /etc/os-release
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.
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
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
bpa wrote:
> Has the replacement file got all the same characteristics permissions/
> owner etc as other files in the Bin directory ?
>
> Does WebUI setting/Advanced/Filetypes under AAC show faa/flac etc or
> disabled ?
Code:
bpa wrote:
> Worse ? Did it hang ? If it didn't hang then it is a bit better !!
>
> I think the problem is a WAV file header "data" chunk size is set to
> zero bytes which is norm for streaming data but not for file players who
> see an zero length file and not an infinite length file.
>
>
bpa wrote:
> Yes. Try the armhf one from there.
>
> https://sourceforge.net/projects/lmsclients/files/utility/faad/20170831-383f2b0/
Worse, that doesn't even work with the "fixed" track, nor any other m4a
track I have.
https://pastebin.com/bNEpvv7Z
If I ssh in to the Pi and do:
Code:
ralphy wrote:
> I agree. But it does appear from the 'github issue'
> (https://github.com/ralph-irving/faad2/issues/4) that there still is a
> problem with certain mp4 iplayer files.
>
> Perhaps @rickwookie would try replacing the faad binary from my builds
> just as a chec
bpa wrote:
> It's late & i'm not doing anything else tonight - your link to fixed
> file doesn't seem to work. So just give commands used to extract and
> reinsert the art.
>
> edit:
>
> the link has "..." in it so it isn't complete.
Re sent the fixed link. I can't give the commands as
bpa wrote:
> If you give the command you used to reinsert the art, I'll try to
> reproduce. I've other tools to pull MPEG4 files apart down to the
> "atoms" as file structure is probably the underlying issue (the order of
> "atoms" can matter) . But as I said in my previous post - the
bpa wrote:
> The problem is that it is not a embedded covert which is metadata. It
> has been stored as a single stream which has a video and audio component
> - just like a full movie. faad was initially just a AAC decoder from
> ADTS fromatted streams and then a partial MPEG4 format decoder
Ok, I've run the file through ffmpeg (a newer version on my Windows
machine) with the stream copy options as you suggested, and sure enough
that file plays fine. However, I'm confused as to why what is
essentially just the embedded cover art is causing the problem. Lots of
the other m4a files I
bpa wrote:
> This is MPEG-4 - not thre same as tracks in a CD
>
> This mean there is a stream which has a video track and an audio track -
> faad doesn't like "video" parts as MPEG4 support was grafted on whereas
> Touch has a proper MPEG4 decoder which can ignore video.
Oh I see, the problem
bpa wrote:
> IIRC There was a "split" in the developers - so some distros have avconv
> others have ffmpeg. Usually interchanegable except for some build
> options.
>
> What happened to the remainder of the command in red ?
>
> avconv -i "/mnt/samba/Music/Albums/Various Artists - In the
Hmm...
Code:
root@SqueezePlug:~# ffmpeg -i "/mnt/samba/Music/Albums/Various Artists - In
the Night Garden/24 Time to Go to Sleep.m4a"
ffmpeg version 0.8.21-6:0.8.21-0+deb7u1+rpi1, Copyright (c) 2000-2014 the
Libav developers
built on Oct 26 2017 14:35:48 with
bpa wrote:
> I'd be interested to examine the track in detail. It;'s the only way to
> tackle these odd issues., MPEG4 has many options and so hard to say
> offhand what the issue could be. You can use something like ffmpeg to
> re-encode without having to rerip but it is not a friendly
I'm happy to DM you a link to one of the curious tracks if you're
interested, but I think the sensible thing for me to do in the
circumstances is just re-encode that one album and see if it fixes it,
because clearly there's nothing wrong with my transcoding settings if
they work for every other
bpa wrote:
> MPEG4 is the most generic description. It doesn't tell how file is
> structured. In LMS there can be an additional qualification "leading
> audio" which gives a hint at structure.
>
> Your problem is odd - usually files can be played using faad but fail
> when playing natively
bpa wrote:
> The problem is not the codec AAC but the file structure MPEG4 (aka mp4).
>
> faad support some but not all the possibles variants of MPEG4.
>
> On LMS WebUI when you drill down onto the problem track - what does LMS
> say the "File format" is (this is on the same display with
bpa wrote:
> m4a files can have many reasons not to be transcoded by faad.
>
> Can you confirm that faad and flac work OK on your Pi. Test by playing a
> http/AAC stream
> http://www.somafm.com/illstreet64.pls
Yes, that's transcoding fine and plays on my Transporter.
29525
I don't why it's
Could anyone help me resolve why I can't get m4a files playing on my
Transporter? They play fine on my Touch, but I understand this is
because the Touch supports aac natively, and the Transporter doesn't. My
conversion settings seem to me to be set up ok, to use faad, but it's
not working.
I'm
Paul Webster wrote:
> "New Music" uses the file date rather than when the scan found it - so
> Clear and Rescan should not cause a problem there.
Ok, that's good to know. It would be nice to understand the mechanism
that's causing these tracks to get ignored on a "new and changed" scan
though.
d6jg wrote:
> Not clear whether you have tried a Full Clear & Rescan
No, but I was hoping to avoid that in order to keep my "New Music" and
other library statistics.
rickwookie's Profile:
After a power cut, my LMS (running on a Pi) booted before my NAS (where
my media library resides) and thus the media share was not mounted.
Attempting to play an album, quickly failed to find the first five
tracks (before I stopped it and realised the problem) and as a result
those tracks got
Could you share the solution with the rest of us?
I'm also getting the same failed media scan after updating 'Music and
Artist Information' to v1.6.7 today.
Media scan terminated unexpectedly (Scanning Progress)
>From the scan log:
Code:
[19-10-13 13:31:07.8777]
26 matches
Mail list logo
