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/


[dvd::rip] Problems with most filters

Subject: [dvd::rip] Problems with most filters
From: Bruno Treguier <Bruno.Treguier@xxxxxxx>
Date: Thu, 26 Jan 2006 01:12:01 +0100
Hi there !

I'm new to this list ad have only been using dvdrip in a very basic way
until now.

Today I wanted to dig a little bit further into the filters,
specifically in order to add a watermark logo to certain films. During
that process I ran into several rather strange problems, perhaps linked
together.

I've browsed the list archives, and couldn't find anything relevant, but
please be indulgent if ever I missed something !

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):

Error executing a transcode socket command:

load logo file=logo.png:posdef=2:range=0-0


The text is pretty much the same for any filter... Anyone seeing a
reason for this ?

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...

When I cut'n paste the command from the log window and launch it manually,
however, the socket is correctly created ! 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.

Is there a reason why the socket would not show up in the /tmp
directory ? Could this be linked with the fact that most filters don't
work ?

Or what am I doing wrong ?

Thanks for any answer/pointer !

My configuration: transcode 1.0.2 - dvd::rip 0.52.6

Regards,

Bruno

-- 
-- Service Hydrographique et Oceanographique de la Marine ---  EPSHOM/CIS/MIC
--     13, rue du Chatellier ---  BP 30316  --- 29603 Brest Cedex, FRANCE
--        Phone: +33 2 98 22 17 49  ---  Email: Bruno.Treguier@xxxxxxx

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

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

[ top ]