dvd::rip

->ABOUT / NEWS

->DOCUMENTATION
-TABLE OF CONTENTS
-INSTALLATION
-USING THE GUI
-CLUSTER MODE
-FAQ

->KEY FEATURES

->DOWNLOAD

->SUPPORT

->TRANSLATIONS

->MAILING LIST
-SEARCH ARCHIVE

->CHANGE LOG

->CREDITS

->TODO

->LINKS

http://www.exit1.org/


Re: [dvd::rip] dvdrip fails ffmpeg/h264 2nd pass, wrong log filename

Subject: Re: [dvd::rip] dvdrip fails ffmpeg/h264 2nd pass, wrong log filename
From: Francesco Romani <fromani@xxxxxxxxx>
Date: Sat, 7 Jan 2006 12:06:05 +0100
On Sat,  7 Jan 2006 09:54:55 +0100
Jörn Reder <joern@xxxxxx> wrote:

Hi,

> > > When encoding to h264 using ffmpeg, ffmpeg seems to drop the h264
> > > multipass log to tmp/x264_2pass.log .. not tmp/divx4.log which is
> > > where dvdrip looks for it from.
> > > I got around this by simply copying tmp/x264_2pass.log to
> > > tmp/divx4.log and manually doing pass 2 in a terminal,
> > Hmm, did you try to do the 2nd pass manually with "reuse log"
> > enabled? That's the only situation where dvd::rip makes assumptions
> > about the log filename. If you do a straight 2-pass transcoding it
> > should work.
> Yes, it should if transcode would support 2-pass h264 encoding. I
> just reproduced the problem on my system and found this
> transcode-users posting on this topic:
>   http://article.gmane.org/gmane.comp.video.transcode.user/17307/

Interesting.
Unfortunately, I've started to play with {x,h}264 only recently, on a
new i386 box, since I've had some trouble to make it work on amd64, so
this sound new to me.
Anyway, I'm really interested on x264 and I would like to support better
on tc. In those days I'm pretty busy with my own business, and rewriting
the export layer for tc 1.1.0 (especialli the ffmpeg module ;).
I'm also planning from quite a long time to add a specific x264 encoder
module, and this should be one of the new features when new module
system is ready and stable enough. For stable codebase (1.0.x) I've no
plans. I would like to investigate this issue and hopefully brew up a
fix for next 1.0.3, but I can't do it soon :\

> So it's not only a wrong log filename, but a file with 0 byte size as 
> well. So renaming it to x264_2pass.log may make ffmpeg happy (in
> terms of it doesn't complaing about the missing file), but I can't
> imagine that you get a proper h264 2pass encoding from that... ;)

Just a thought, but this sounds like a problem in integration between
libavcodec and x264, an upstream solution should be a better thing.
Of course we will do our best to provide a good short-term solution ;)

> > Yep, I'll check h264 myself and will make it an officially
> > supported codec.

Me too. I really want a good support for x264 (and mp4 container, libmp4
looks nice) into next TCs.

Best regards,

-- 
Francesco Romani -- Ikitt 
'people always complain, no matther what you do' 
IM contact: (drop me a note via email first, I have antispam default
deny!) jabber://ikitt-at-jabber-dot-linux-dot-it icq://27-83-87-867

<Prev in Thread] Current Thread [Next in Thread>
 

Archive powered by MHonArc. Search powered by ht://dig.

[ top ]