On 9/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi there!

Hi!
 

So I installed transcode from cvs these days and played a bit around. I
noticed that there really is some new stuff, in features :)

Nice to read so ;)
 

but also in cli syntax, which is not trivial..

Yes, I'll defintively write out a 1.0.x -> 1.1.0 CLI transition table before to release.
 

First I had some trouble to figure out how to use x264 at all but with a
little help from IRC and the man page I got it (more or less) working.
It's quite strange that I had to specify the muxer (-y ..,..,..) since it
is marked optional in the man page.So when I tried

Yes, there is a bit of confusion here since we've stopped and delayed the
transition of export layer from old to new module system.

Let me explain a bit.
One of historical weekness of transcode is the poor granularity of import/export module.
Not clearling separate encoding/muxing and demuxing/decoding allow to some unpleasant
situation like code duplication, difficult to add support for more formats/codecs, poor
support for non-avi/non-raw formats.
During 1.1.0 development cycle we've addressed this issue by designing and implementing
foundation of the new module system. We miss mainly one big piece, new export (now split
in encoding + muxing) modules. Due to lack of time, we've chosen to delay this task to
post 1.1.0 in order to escape ASAP from aging 1.0.x codebase.

Now, the problem is that cool stuff (as for x264 encoder) was originally written or rapidly
ported to new module system. Now we need to provide temporary compatibility layer
to let them work with old module system.

I'll do ASAP during next week :)

transcode -i /mnt/tmp/ -x dvd -y x264 -w 1000 -o tc-dvd-test
..I'm getting
>[transcode] warning: /usr/local/lib/transcode/export_x264.so: cannot open
>shared object file: No such file or directory>[transcode] warning: (dl_loader.c) loading
>"/usr/local/lib/transcode/export_x264.so" failed(so it is looking for an export module).
Same with -y x264,lame (tc is looking for encoder_lame, while it should
use the export_ module)

I'll recheck this one too.
 

Finally,
transcode -i /mnt/tmp/ -x dvd -y x264,null,avi -w 1000 -o tc-dvd-test
loaded encode_x264, *but* it seems that no file is created..

Looks strange, but I can't check it right now; expect a followup soon.
 

Comments welcome, I'm a bit lost here.
Once I understand everything, I'm willing to help with the documentaion.

And that would be really nice :)
 

## bitrate  ->  -w
+## pass     ->  -R
##

(only guessing here..)

Looks ok
 
Also, a more general question about x264.cfg: It refers to the mencoder
man page (which makes perfectly sense)

Yes, it make sense since most documentation come from mplayer crew, but honestly
speaking I don't like soo much being so dependent mplayer/mencoder :\
But I guess documentation duplication (and out-of-sync-documentation issues)
are even worse...

but does that imply that all
default values are set in the same way? (I don't know if these are encoder
defaults or set by the application (tc/mencoder))

defaults are set by application, and (IIRC, I haven't sources handy) tc module
uses just the same values of mencoder.
 
best regards,

--
Francesco Romani

Reply via email to