Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Mon 30 May 2016, 22:03
All times are UTC - 4
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Multimedia
ffmpeg is deprecated : winff GUI for avconv and ffmpeg
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 1 [5 Posts]  
Author Message

Joined: 16 Jun 2008
Posts: 1385
Location: 500 seconds from Sol

PostPosted: Fri 17 Jan 2014, 00:15    Post subject:  ffmpeg is deprecated : winff GUI for avconv and ffmpeg  

Hi all,

Skip this if you not running Precise, Raring, Wheezy or (?) dpup Squeeze. Both debian and ubuntu deprecated ffmpeg and have used avconv instead for the last couple of years. If you type "avconv --version" in a terminal, you may discover --as I did in upup precise-- that avconv is already installed. If not, you may want to install it. [Not available in Lupu].
If you have it, you may want a GUI. Winff is available from the ubuntu repos. Sorry no pet attached as even after stripping out obvious things not needed by Puppy --gazillion languages and docs-- the pet I made was 1.7 megs. Just type "winff" in PPM's search box. In upup precise PPM claimed there were several dependencies, but they all related to Xterm. You won't need anything other than the winff.deb. You can install it, or download and extract it, remove stuff you won't need and turn it into a pet for later use.

It's set to use ffmpeg by default, but the following webpage will show you how to configure it for use with avconv by changing preferences. Just click Edit>Preferences on its tool bar and the GUI will enable you to browse to the executables of avconv, avplay and the terminal of you choice. They're all in /usr/bin.


The app from ubuntu precise's repo had pre-configured presets. No guaranties. Hopefully, someone who knows what he or she is doing will do a proper job.

Back to top
View user's profile Send private message 
Official Dog Handler

Joined: 04 May 2005
Posts: 11918
Location: Arizona USA

PostPosted: Fri 17 Jan 2014, 00:53    Post subject:  

I'm using Precise at the moment. I don't think I've seen a more useless help page than what showed up when I entered avconv -h. Confused
Back to top
View user's profile Send private message 

Joined: 28 Sep 2012
Posts: 1018

PostPosted: Fri 17 Jan 2014, 01:53    Post subject:  

A good explanation of the problem was provided by user mcewanw in precise 5.4.3 thread:

mcewanw wrote:
watchdog wrote:
I have understood that ffmpeg is going to get retired and supported only for compatibility problems. If you try to use directly ffmpeg in precise you are adviced that it is not possible and another standard is used (I don't remember the name, now I am in wary EDIT: avconv).

FFmpeg is a separate project from the avconv project (which was forked off from FFmpeg code). As far as I know the FFmpeg project has not been retired; at this moment the latest version of its ffmpeg code is version 1.1, which was released on 7 January 2013.


However, Debian and Ubuntu have adopted project code (avconv) from the libav project in preference to the FFmpeg project code. A problem that arises is that though the use and commandline options between the two (libav project's avconv and FFmpeg project's ffmpeg) is almost the same they are apparently not always exactly identical. Furthermore, as the following link (second post) points out the libav project also released their own temporary version of code they called "ffmpeg" which is the one which outputs the misleading warning message about ffmpeg binary being "provided for compatibility only":


The "compatibility" message is misleading because libav project's ffmpeg code IS NOT the same as the continuing to be developed ffmpeg code from FFmpeg project. Newer versions of libav project code apparently no longer provide the temporary ffmpeg and only avconv.

In summary, however, since Debian and Ubuntu are providing libav project code in preference to FFmpeg code (original ffmpeg) it may be necessary to start using avconv directly since if the use of the program options are not identical to ffmpeg then a symlink will not resolve the issue. I'm not sure of the situation with other Linux versions, however, and various programs traditionally relied on FFmpeg project ffmpeg (e.g. Mplayer, VLC, xine), so that potental problem has to be considered too.

As of 7 Jan 2013, the latest libav code is version 9.1. The version of libav project's avconv in Precise retro 5.4.3 (which I use) is 0.8.3. It also provides a libav project ffmpeg binary (which allows programs which refer to ffmpeg to work, albeit sometimes with some modifications to options and their commandline placement). Some differences between FFmpeg project ffmpeg and avconv are itemised in the libav code changelog for earlier libav code version 0.8_beta1:


- ffplay/ffprobe/ffserver renamed to avplay/avprobe/avserver
100 - ffmpeg deprecated, added avconv, which is almost the same for now, except
101 for a few incompatible changes in the options, which will hopefully make them
102 easier to use. The changes are:
103 * The options placement is now strictly enforced! While in theory the
104 options for ffmpeg should be given in [input options] -i INPUT [output
105 options] OUTPUT order, in practice it was possible to give output options
106 before the -i and it mostly worked. Except when it didn't - the behavior was
107 a bit inconsistent. In avconv, it is not possible to mix input and output
108 options. All non-global options are reset after an input or output filename.
109 * All per-file options are now truly per-file - they apply only to the next
110 input or output file and specifying different values for different files
111 will now work properly (notably -ss and -t options).
112 * All per-stream options are now truly per-stream - it is possible to
113 specify which stream(s) should a given option apply to. See the Stream
114 specifiers section in the avconv manual for details.
115 * In ffmpeg some options (like -newvideo/-newaudio/...) are irregular in the
116 sense that they're specified after the output filename instead of before,
117 like all other options. In avconv this irregularity is removed, all options
118 apply to the next input or output file.
119 * -newvideo/-newaudio/-newsubtitle options were removed. Not only were they
120 irregular and highly confusing, they were also redundant. In avconv the -map
121 option will create new streams in the output file and map input streams to
122 them. E.g. avconv -i INPUT -map 0 OUTPUT will create an output stream for
123 each stream in the first input file.
124 * The -map option now has slightly different and more powerful syntax:
125 + Colons (':') are used to separate file index/stream type/stream index
126 instead of dots. Comma (',') is used to separate the sync stream instead
127 of colon.. This is done for consistency with other options.
128 + It's possible to specify stream type. E.g. -map 0:a:2 creates an
129 output stream from the third input audio stream.
130 + Omitting the stream index now maps all the streams of the given type,
131 not just the first. E.g. -map 0:s creates output streams for all the
132 subtitle streams in the first input file.
133 + Since -map can now match multiple streams, negative mappings were
134 introduced. Negative mappings disable some streams from an already
135 defined map. E.g. '-map 0 -map -0:a:1' means 'create output streams for
136 all the stream in the first input file, except for the second audio
137 stream'.
138 * There is a new option -c (or -codec) for choosing the decoder/encoder to
139 use, which allows to precisely specify target stream(s) consistently with
140 other options. E.g. -c:v lib264 sets the codec for all video streams, -c:a:0
141 libvorbis sets the codec for the first audio stream and -c copy copies all
142 the streams without reencoding. Old -vcodec/-acodec/-scodec options are now
143 aliases to -c:v/a/s
144 * It is now possible to precisely specify which stream should an AVOption
145 apply to. E.g. -b:v:0 2M sets the bitrate for the first video stream, while
146 -b:a 128k sets the bitrate for all audio streams. Note that the old -ab 128k
147 syntax is deprecated and will stop working soon.
148 * -map_chapters now takes only an input file index and applies to the next
149 output file. This is consistent with how all the other options work.
150 * -map_metadata now takes only an input metadata specifier and applies to
151 the next output file. Output metadata specifier is now part of the option
152 name, similarly to the AVOptions/map/codec feature above.
153 * -metadata can now be used to set metadata on streams and chapters, e.g.
154 -metadata:s:1 language=eng sets the language of the first stream to 'eng'.
155 This made -vlang/-alang/-slang options redundant, so they were removed.
156 * -qscale option now uses stream specifiers and applies to all streams, not
157 just video. I.e. plain -qscale number would now apply to all streams. To get
158 the old behavior, use -qscale:v. Also there is now a shortcut -q for -qscale
159 and -aq is now an alias for -q:a.
160 * -vbsf/-absf/-sbsf options were removed and replaced by a -bsf option which
161 uses stream specifiers. Use -bsf:v/a/s instead of the old options.
162 * -itsscale option now uses stream specifiers, so its argument is only the
163 scale parameter.
164 * -intra option was removed, use -g 0 for the same effect.
165 * -psnr option was removed, use -flags +psnr for the same effect.
166 * -vf option is now an alias to the new -filter option, which uses stream specifiers.
167 * -vframes/-aframes/-dframes options are now aliases to the new -frames option.
168 * -vtag/-atag/-stag options are now aliases to the new -tag option.

mcewanw (author of precord and pavrecord)
Back to top
View user's profile Send private message 

Joined: 11 Oct 2008
Posts: 8491
Location: qld

PostPosted: Fri 17 Jan 2014, 01:57    Post subject:  

I think, in the spirit of open source, that the avconv developers, or whatever they want to to call themselves, took a pretty gutless approach to forking a project. That's why I don't feel (yes emotional bullshit) like supporting anything they do. Something struck a chord with that for me today and I quote; "It is fine to fork it for this purpose ... just don't do stuff that will make it incapable of being merged." . The author may or may not agree in the context of this post.

ffmpeg is alive and well. Just because Ubuntu doesn't support it does not mean that it is deprecated.

PS: thanks watchdog

Puppy Linux Blog - contact me for access
Back to top
View user's profile Send private message Visit poster's website 

Joined: 16 Jun 2008
Posts: 1385
Location: 500 seconds from Sol

PostPosted: Fri 17 Jan 2014, 20:35    Post subject: Thanks watchdog  

Thanks, watchdog, for the clear explanation. Sorry I originally missed it.

If this had occurred in the "for profit" sector, avconv would probably have been sued for defamation, misleading advertisements and probably trademark infringement. Or something to that effect. Intellectual property rights wasn't on my daily watch list.

Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 1 [5 Posts]  
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Multimedia
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum

Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0584s ][ Queries: 11 (0.0040s) ][ GZIP on ]