I managed to get it working via removing the -d path. One other thing i have noticed is when its recording and the feed drops it will keep trying to connect which is great. However when it does connect when the feed comes back it restarts the recording so deletes what has been recorded and then starts recording again.
Can you get it to either add to the existing file or simply split the recording so we could then stitch the recording back together once its finished. On 22 Jan 2016 17:24, "Yuri D'Elia" <[email protected]> wrote: > On 21/01/16 12:33, Stuart Downton wrote: > > Hi > > > > I am trying to setup fPls to record a stream we have. > > > > I can see fPls grabs the URL however when it then hits fIcy I just get a > > fIcy: Unknown host error. > > > > I have tried just using fIcy direct with the URL and it records the > > stream without any issues so not sure why in conjunction with the fPls > > it fails to record the stream. > > > > My command is: > > > > fPls -v -i 60m -T 1s -L-1 http://[icecast server]/mos.mp3.m3u -o > > /home/recorder/audio/$stream/$date.$stream -d > > /home/recorder/logs/$stream.log -M 60m > > > > When running the command i just get: > > > > fPls: stream http://[icecast server]:80/mos.mp3: retry 1 of loop 20 > > fIcy: Unknown host > > It could be an encoding issue of the m3u file of some kind. > fPls is pretty dumb in that sense (no recording is attempted), so it > might send to fIcy something broken. > > Could you send me the url of the playlist (even privately) so that I can > try from here? > > Some way to test this locally would be using strace(1), > > strace -o trace.log -e trace=process fPls.... > > to see how fPls in invoked. > > > >
