On Tue, Jan 01, 2013 at 06:22:21PM +0100, Armin K. wrote: > > Happy new year to you, too. Looking at your patch it looks like > trasncode calls "-vpre medium" but some claim that the correct switch > might be "-preset medium". That might be only true for x264 encoded > files though. > > See "Note:" > https://en.wikibooks.org/wiki/FFMPEG_An_Intermediate_Guide/h.264#Presets > I'll take a look later, but there is _so_much_ out there about using ffmpeg which was (presumably) correct when it was written, but now no longer works. Whatever, everything in transcode, except any options passed with -y ffmpeg -F ..., is hardcoded.
> This is my ffmpeg configuration: > > $ ffmpeg > ffmpeg version 1.0.1 Copyright (c) 2000-2012 the FFmpeg developers > built on Dec 9 2012 19:15:54 with gcc 4.7.2 (Krejzi 4.7.2) > configuration: --prefix=/usr --enable-gpl --enable-nonfree > --enable-openal --enable-postproc --enable-shared --enable-vaapi > --enable-version3 --enable-vdpau --enable-x11grab --disable-debug > --disable-static --enable-libass --enable-libcdio --enable-libfaac > --enable-libfreetype --enable-libgsm --enable-libmp3lame > --enable-libopencore-amrnb --enable-libopencore-amrwb > --enable-libopenjpeg --enable-openssl --enable-libpulse --enable-librtmp > --enable-libspeex --enable-libtheora --enable-libtwolame > --enable-libv4l2 --enable-libvo-aacenc --enable-libvo-amrwbenc > --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxvid > > Ooh, a few more options for me to look at ;-) Actually, I think I already have many of those. I know I dropped libfaac, and ISTR there is an experimental encoder to replace it : needs to be enabled at *runtime* (I'll check this later, if I remember). > > I think the real question is whether people using k3b, such as > > Baho, and anyone using dvd::rip, can get those to successfully use > > transcode. For people using transcode on the command line, I suspect > > that transcode commands which use ffmpeg will still be problematic. > > > > > I've built dvd::rip last night, and ran some basic rip and transcode > (using defaults - I don't know how to configure stuff) and I didn't seem > to experience any problems. It was running too long, so I didn't let it > finish. I do have k3b, too. I can try using transcode with it, but > you'll need to point me at some guide for that. > If you don't know how to configure things, what hope is there for the rest of us ? Transcode has a lot in the README files, and various things hidden away in the man pages, particularly for export, but it is hard to find your way around them, and much of the detail is obscure. It's also the worst possible project name to use when googling for help - almost everything that comes up is related to the general subject of transcoding. Googling for transcode-1.1 sometimes helps, but it is still hard to find useful information. That's why I prefer to use ffmpeg to do the transcoding - it's then just a question of passing the correct settings, in the correct order. Even that takes a lot of testing : after the power came back I restarted a conversion to webm - with 4 threads on my Sandy Bridge i3 it typically used 250% to 300% cpu and took significantly longer than real time, and although it looks acceptable the bit rates didn't all get applied where I thought they would - low video bitrate, high max bitrate got applied to the audio (according to what mediainfo reports). For k3b you'll need to ask Baho - my impression is that both transcode and the projects which use it have default settings and probably expect those to be adequate. This stuff all dates from the days when people were grateful to be able to use the DVDs they had bought, and had limited storage. The days when people thought mp3 was good. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
