Closed GoogleCodeExporter closed 8 years ago
Actually my bad, sorry for not simply attaching my presets, now attached to
this reply...
THANKS!
Original comment by das...@gmail.com
on 18 Aug 2012 at 5:38
Attachments:
I don't know what ffmpeg 0.11 means. What version of libavcodec does it
contain. To get that information, run "ffmpeg -version". Maybe you should use
one of the other preset files we provide.
Original comment by poipodec...@hotmail.com
on 18 Aug 2012 at 12:46
Hi,
0.11 is the version of ffmpeg.
http://ffmpeg.org/download.html#release_0.11
That is the version I'm using and I've tried all the presets and only some
presets in the files will work but not everything, this is why I'm asking for
an update to the presets so whatever presets you are creating for WinFF, all of
them will work with this version.
Here's what 'ffmpeg -version' gives me;
ffmpeg -version
ffmpeg version 0.11
built on Aug 17 2012 18:57:05 with gcc 4.5.2
configuration: --prefix=/usr --libdir=/usr/lib --shlibdir=/usr/lib
--mandir=/usr/man --enable-libmp3lame --enable-libfaac --enable-libvo-aacenc
--enable-nonfree --enable-gpl --enable-version3 --enable-postproc
--enable-avfilter --enable-libass --enable-libdc1394 --enable-libgsm
--enable-libopencore-amrnb --enable-libopencore-amrwb --enable-librtmp
--enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libv4l2
--enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libx264
--enable-libxvid --enable-runtime-cpudetect --enable-vaapi --disable-vdpau
--enable-memalign-hack --enable-pthreads --enable-x11grab --enable-bzlib
--enable-zlib --enable-shared --enable-static --disable-debug
--extra-cflags='-I/tmp/build/tmp-ffmpeg/ffmpegdeps/usr/include
-DRUNTIME_CPUDETECT'
--extra-ldflags='-L/tmp/build/tmp-ffmpeg/ffmpegdeps/usr/lib -lssl -lcrypto -lz
-lusb'
libavutil 51. 54.100 / 51. 54.100
libavcodec 54. 23.100 / 54. 23.100
libavformat 54. 6.100 / 54. 6.100
libavdevice 54. 0.100 / 54. 0.100
libavfilter 2. 77.100 / 2. 77.100
libswscale 2. 1.100 / 2. 1.100
libswresample 0. 15.100 / 0. 15.100
libpostproc 52. 0.100 / 52. 0.100
THANKS
Original comment by das...@gmail.com
on 18 Aug 2012 at 9:46
By the way, since I run Slackware and compile ffmpeg from source ffmpeg
recommends users that wish to compile from source themselves are strongly
encouraged to consider using the development branch...
Since ffmpeg actually recommends the development branch I'd like to follow it
and I ask that maybe WinFF do so and keep up to date presets for it...
Today I compiled from GIT version 0.11.1.git and this is what ffmpeg -version
shows;
ffmpeg version N-43735-gb1acf5d
built on Aug 19 2012 18:25:45 with gcc 4.5.2 (GCC)
configuration: --prefix=/usr --libdir=/usr/lib --shlibdir=/usr/lib
--mandir=/usr/man --enable-libmp3lame --enable-libfaac --enable-libvo-aacenc
--enable-nonfree --enable-gpl --enable-version3 --enable-postproc
--enable-avfilter --enable-libass --enable-libdc1394 --enable-libgsm
--enable-libopencore-amrnb --enable-libopencore-amrwb --enable-librtmp
--enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libv4l2
--enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libx264
--enable-libxvid --enable-runtime-cpudetect --enable-vaapi --disable-vdpau
--enable-memalign-hack --enable-pthreads --enable-x11grab --enable-bzlib
--enable-zlib --enable-shared --enable-static --disable-debug
--extra-cflags='-I/tmp/build/tmp-ffmpeg/ffmpegdeps/usr/include
-DRUNTIME_CPUDETECT'
--extra-ldflags='-L/tmp/build/tmp-ffmpeg/ffmpegdeps/usr/lib -lssl -lcrypto -lz
-lusb'
libavutil 51. 70.100 / 51. 70.100
libavcodec 54. 53.100 / 54. 53.100
libavformat 54. 25.104 / 54. 25.104
libavdevice 54. 2.100 / 54. 2.100
libavfilter 3. 11.101 / 3. 11.101
libswscale 2. 1.101 / 2. 1.101
libswresample 0. 15.100 / 0. 15.100
libpostproc 52. 0.100 / 52. 0.100
THANKS
Original comment by das...@gmail.com
on 20 Aug 2012 at 4:45
Unfortunately, I am not in the position yet to test this myself, as Debian and
Ubuntu don't have a ffmpeg with libavcodec54 yet. Maybe one of the other
developers can help?
Original comment by poipodec...@hotmail.com
on 21 Aug 2012 at 7:52
[deleted comment]
WinFF is a really great project and I would not just rely on running Ubuntu and
Debian and go by whatever version(s) they have and base this project off of
that, the reason being, the ffmpeg development version is the only version on
which FFmpeg developers actively work.
Granted many distros won't follow the development branch, I can understand
this, so have a version based off what you like, but I certainly hope in the
future you can please base a version off the development branch too, to allow
greater flexibility in this project, since it's the version that is actively
worked on...
In the meantime if this is something you'd like to pursue, I do have Slackware
for VirtualBox I can give you, that I set up and installed, then you'll have a
distro you can compile from and if you are not familiar with this, then I can
show you how to maintain this, it's not complicated using Slackware build
scripts...
AlienBob from Slackware already has a script set up for this;
http://www.slackware.com/~alien/slackbuilds/ffmpeg/build/
THANKS
Original comment by das...@gmail.com
on 21 Aug 2012 at 11:22
I can always go back and recompile for libavcodec53 ffmpeg 0.10, that's not a
problem for me. I just thought with this project it might be benefical to have
support for libavcodec54?
So has any other developer seen or given this thought?
THANKS
Original comment by das...@gmail.com
on 31 Aug 2012 at 2:13
@dasfox:
1) off course we want to support libavcodec54 (at some moment)
2) somebody needs to do the work.
3) most of our users are not using libavcodec54 based ffmpegs. Also they either
get ffmpeg with winff (Windows) or with their own distribution (Linuxes). In
the later case, if the distribution is already using libavcodec54, the
maintainer of the winff package for the distribution could/should do the work
at this moment. As I do the maintenance for Debian/Ubuntu and did most work on
having the presets updated BEFORE a new winff release with a new ffmpeg
release, I will get to it, but it might not be before the next release of
Debian.
4) If somebody (you?) create presets that work with libavcodec54 we will be
very happy to use and distribute that file.
Original comment by poipodec...@hotmail.com
on 1 Sep 2012 at 11:51
-deblockalpha is deprecated and can be removed. Do the presets work if you
remove that part (including the number behind it)?
Original comment by poipodec...@hotmail.com
on 5 Sep 2012 at 8:10
If I remove -deblockalpha then it complains about -deblockbeta;
Unrecognized option 'deblockbeta'
Failed to set value '0' for option 'deblockbeta'
So then I remove -deblockbeta and now it gives me this;
Please use -b:a or -b:v, -b is ambiguous
Unrecognized option 'directpred'
Failed to set value '3' for option 'directpred'
I get this for both MPEG-4 Fullscreen & Widescreen, I'll attach presets with
both the deblockalpha and deblockbeta removed...
THANKS
Original comment by das...@gmail.com
on 6 Sep 2012 at 12:17
Attachments:
Forgot to mention when looking over the presets I get this when converting to
OGG;
[libvorbis @ 0x93bca40] Que input is backward in time
THANKS
Original comment by das...@gmail.com
on 6 Sep 2012 at 12:18
Debian now has avconv with libavcodec54 in experimental. I am working on
updated presets for it.
Original comment by poipodec...@hotmail.com
on 9 Nov 2012 at 8:46
Thanks, now that ffmpeg is at 1.x version, it seems like maybe it's a good
version to now shoot for?
THANKS
Original comment by das...@gmail.com
on 9 Nov 2012 at 11:18
Please checkout:
http://code.google.com/p/winff/downloads/detail?name=presets-libavcodec54_v1.wff
&can=2&q=
We still need to decide on how to replace async 1, but the rest works here.
Original comment by poipodec...@hotmail.com
on 10 Nov 2012 at 1:49
Oh so this pretty much suppose to work with ffmpeg 1.x version?
THANKS
Original comment by das...@gmail.com
on 10 Nov 2012 at 9:06
Right. Most intelligence is in the presets.
Of course we need to make sure that all the additional options work. I have not
found any yet, except for -deinterlace, that does not work anymore. But if you
find any, don't hesitate to report it as a bug.
Original comment by poipodec...@hotmail.com
on 11 Nov 2012 at 1:47
Original issue reported on code.google.com by
das...@gmail.com
on 18 Aug 2012 at 5:36