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] Problems with most filters

Subject: Re: [dvd::rip] Problems with most filters
From: Jörn Reder <joern@xxxxxx>
Date: Sat, 28 Jan 2006 14:58:37 +0100
Bruno Treguier wrote:

> First of all, I've been unable to run most of the filters, and it seems
> that in the end, the only ones I've managed to get working are the ones
> that don't need any parameter. Any attempt to use a filter needing a
> parameter results in a pop-up window spawning and stating something like
> this (for the logo filter here):
> [...]

I just reproduced this problem. transcode fails if more than one 
parameter is passed to the module. Modules without any parameters or 
just one parameter work.

I just posted a correspondent report to the transcode developers.

> As the pop-up window was related to a problem with the socket command
> passed to transcode, I tried to see what could be wrong on that side. I
> then realized that though the transcode command logged in the log window
> had correct parameters (especially the --socket option), the socket was
> _not_ physically present in the /tmp directory (which prevents the use
> of tcmodinfo -s, by the way). I know that this can happen: as long as
> a process holds a file descriptor open on a file or socket, it can be
> used without any reference to it being present and accessible via a
> name on the filesystem, but I find this rather strange in dvdrip's
> case...

Why? dvd::rip removes the socket just after transcode was started (which
creates the socket). This way the socket doesn't leak if something fail
badly, e.g. a dvd::rip or transcode crash. The filesystem entry is not 
needed for proper operation once both processes are connected to the 
socket, which was represented by it.

> When I cut'n paste the command from the log window and launch it manually,
> however, the socket is correctly created !

Yep, transcode creates the socket.

> An important detail: the
> transcode command in the log window is really the one launched, from what
> I can see via a "ps" command or examining directly the "cmdline" file
> within the /proc pseudo-filesystem.

Hmm, what did you expect? ;)

Regards,

Joern

-- 
sub i($){print$_[0]}*j=*ENV;sub w($){sleep$_[0]}sub _($){i"$p:$c> ",w+01
,$_=$_[0],tr;i-za-h,;a-hi-z ;,i$_,w+01,i"\n"}$|=1;$f='HO';($c=$j{PWD})=~
s+$j{$f."ME"}+~+;$p.="$j{USER}\@".`hostname`;chop$p;_"kl",$c='~',_"zu,".
"-zn,*",_"#,epg,lw,gwc,mfmkcbm,cvsvwev,uiqt,kwvbmvb?",i"$p:$c> ";w+1<<07

Attachment: pgpTUfTrr191M.pgp
Description: PGP signature

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

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

[ top ]