ffmpeg 20111002svn recompiled

There was a report, if I can recall it right, that ffmpeg does not work properly with Pmusic as network support is disabled.

Hmmm, there is a '--enable-network' configure option, but it seems to be the default. But, the 'ffserver' executable is not in the PET package.

Anyway, I have recompiled with that option, this time have put 'ffserver' into the PET. Interesting, the PET is a bit smaller this time.

PETs (2.5MB, 2.9MB):

These will be in the upcoming Wary/Racy 5.3 Release Candidate 1.

Posted on 17 Mar 2012, 18:51


Posted on 17 Mar 2012, 19:55 by zigbert
ffmpeg network
just for the record....

To play radio-stations, ffmpeg with network support is _not_ required if streamripper is installed. This is a qualified guess, as ffmpeg is used to play the stream, but as a delay of the buffered stream of streamripper (http://localhost:8002).

To support jamendo.com, ffmpeg must support internet streaming, since streamripper doesn't touch this feature.

Posted on 18 Mar 2012, 2:47 by BarryK
ffmpeg configure options
For the record, this is how I have configured the latest compile of ffmpeg:

# ./configure --prefix=/usr --cpu=i486 --enable-shared --enable-gpl --enable-nonfree --disable-ffplay --enable-x11grab --disable-network --enable-small --enable-runtime-cpudetect --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libdc1394 --enable-libfaac --enable-libfreetype --enable-libmp3lame --enable-libschroedinger --enable-libspeex --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxvid --enable-zlib --enable-postproc --disable-debug --enable-bzlib --enable-version3 --enable-libtheora --enable-swscale --enable-network --enable-libcdio

The difference from before is that I have added the last two. Though, --enable-libcdio is the default anyway, and I thought that --enable-network is too.

Note, Wary and Racy are now built with streamripper.

Posted on 18 Mar 2012, 4:24 by noryb009
Re: ffmpeg configure options
"and I thought that --enable-network is too."

You used the --disable-network flag:
# ./configure --prefix=/usr --cpu=i486 --enable-shared --enable-gpl --enable-nonfree --disable-ffplay --enable-x11grab --disable-network ...

Posted on 18 Mar 2012, 6:55 by zigbert
Barry said:
Note, Wary and Racy are now built with streamripper.

This is great news for Pmusic-users. Both for those who listen to radio (more station and detection of playing artist - title), and for those who use the grabber function (called Radio-hits).

Thank you

Posted on 18 Mar 2012, 7:35 by BarryK
re disable network
Ha ha, so I did!

Hmmm, so does my second --enable-network overrride the earlier --disable-network?

Posted on 18 Mar 2012, 8:05 by BarryK
ffmpeg recompiled
Well, just to be certain that nothing odd happens due to the earlier --disable-network, I have removed it and recompiled, and re-uploaded the PETs.

The config is now:

# ./configure --prefix=/usr --cpu=i486 --enable-shared --enable-gpl --enable-nonfree --disable-ffplay --enable-x11grab --enable-small --enable-runtime-cpudetect --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libdc1394 --enable-libfaac --enable-libfreetype --enable-libmp3lame --enable-libschroedinger --enable-libspeex --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxvid --enable-zlib --enable-postproc --disable-debug --enable-bzlib --enable-version3 --enable-libtheora --enable-swscale --enable-network --enable-libcdio

Posted on 27 Mar 2012, 3:07 by pete22
puppy package manager
Most of the time when I open the puppy package manager, it refuses to show me any packages. This is true in both ziggy and classic form.

I am sorry but I have never understood the instructions on how to add a new repo. When I read the instruction it makes my head spin. Perhaps someone could point me to a tutorial or something to help me.

In the mean time I think it would be grand if you would add the repo for wary's and racy's big sister, [b]Saluki!!!


I miss the page about our mascot teaching linux to the kangaroos. Can we get it back?

Posted on 25 Jul 2012, 4:25 by linuxcbon
I did report that ffmpeg needed disable-network to be removed.
Now it is discovered again and there is some improvement in x11grab : http://www.murga-linux.com/puppy/viewtopic.php?t=76182&start=270