Hya,
So, from what's been said here there isn't anything we can do to have MEncoder to read avs or d2v files, right
Darn
That is very sad. So the only way, such as in FFvfw or QuEnc, is waiting that the MPlayer team develops an external tool for this purpose.
Sad again. Because they aren't going to make tools for win32 only.
This whole project is based on the portability of the product.
In such sense either we accept that the speed achieved with makeAVIS is the maximum possible for reading avs files or we come up
with a new AVS AVI wrapper faster than makeAVIS.
If so we really should open different threads for MEncoder internal filters and other for Avisynth makeAVIS MEncoder threads.
Or else just consider droping avisynth which to me is not an option given the enormous amount of possibilities it gives us.
Not to mention that by droping Avisynth we'd loose MA for instance
Care to comment my last paragraph, please.
Cheers

__________________
Rui

Does nobody here can make the same?
It is so hard to compile a wraper?

Here a trick for all of us what so like Avisynth. (Spanish Forum).
If anybody needs translation, just tell me it.

Prodater,
if I understood well your way, this is a way to automate the proccess of loading an avs in makeavis and load the output avi in mencodeme, isn't it?.
It's nice. And if we add the audio encoding/trascoding as Inc posted, better. I hope we'll find the way to make this within mencoder, to speed it up (your way makes it easier, but doesn't affect the speed, isn't it?).

Yes, it is.
I have same hope than you, but meanwhile...

Would this work? But I dunno the 4cc (xxxx) code.. I suppose it won't work without it, huh...

videocodec d2v
info "d2v directshow"
status untested
fourcc xxxx
driver dshow
dll "d2vsource.ax"
out YV12

d2vsource.ax driver http://sourceforge.net/projects/guliverkli

Also Media Player Classic!!

__________________
|
Meeow!

Hi Fluff,
I've been trying also with much similar config:
But there's no way I can get it to work.
See if you have more luck than I do.
Cheers

__________________
Rui

I already tried that d2vsource.ax driver settings in codecs.conf

but it doesnt work as d2v is not a container incl. a FourCC digit.

What about changing the registry to add a 4cc?

eg:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\ActiveMovie\d evenum\{33D9A760-90C8-11D0-BD43-00A0C911CE86}\avis]
"FriendlyName"="ffvfw MPEG-4 Codec"
"CLSID"="{D76E2820-1563-11CF-AC98-00AA004C0FA9}"
"FilterData"=hex:02,00,00,00,00,00,20,00,02,00,00, 00,00,00,00,00,30,70,69,33,\
00,00,00,00,00,00,00,00,01,00,00,00,00,00,00,00,00 ,00,00,00,30,74,79,33,00,\
00,00,00,60,00,00,00,70,00,00,00,31,70,69,33,08,00 ,00,00,00,00,00,00,01,00,\
00,00,00,00,00,00,00,00,00,00,30,74,79,33,00,00,00 ,00,60,00,00,00,80,00,00,\
00,76,69,64,73,00,00,10,00,80,00,00,aa,00,38,9b,71 ,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,61,76,69,73,00,00,10,00,80 ,00,00,aa,00,38,9b,71
"FccHandler"="avis"
"ClassManagerFlags"=dword:00000000

Is the FFVfw code - can we change that to allow D2VS to be seen?

<edit> actually it'd take more than that - the "CLSID"="{D76E2820-1563-11CF-AC98-00AA004C0FA9}
would have to be created too, and the filter data changed to match the format of the files the d2v pointed too - if you had a d2v from mpeg (vob) it'd be one filter, a d2v from mpeg4 (xvid) would be another filter.

I suspect it won't work this way - I'll play with my registry over the next few days and report.. <edit>

Nope - there's no real way to select the {xxx code (and there's about 1200 already in use (most for bloody adverts/trojans/adware), and i have no idea what to make of the filter data.

I'm giving up on this track - but not on importing avs or d2v...

__________________
|
Meeow!

I just recognised at configure options for compiling mencoder this:

--disable-dshow _____=disable Win32/DirectShow support [autodetect]

Means, I should try to set "--enable-dshow" before compiling as the d2vsource.ax is a directshow driver.

Ill try that these days.

Just a silly question, I'm sure that with an obvious answer...
What's the advantage of loading d2v in mencoder, compared to loading directly vob files or avi files?.
Because I just use DVD2AVI to feed the video to avisynth, I don't process at all the video in DVD2AVI.

... I know, it's cristal clear to everybody, but I don't see it now

But, as I see advances (at least ideas) in d2v way, I'm sure we'll manage to feed avs files to mencoder soon ( ), in a faster way than makeAVIS one.

@ Digi Doc

Win98 (Fat32) doesn`t support full size VOB files like 6GB ones, ... you see?
I got Win2000 (NTFS) but some users do have still Win98.

@ Digi Doc

Plus also, the less paths you use between source and output, the faster things will be.

I only use avisynth to frameserve the vobs to mencoder (I think I've got 'deen' , but only as a slight cleaner upper)

vob-d2v-avs-avi-mencoder, if I could go vob-d2v-mencoder it'd be faster.

I'm in xp, but not using ntfs, so I've also got the 4G limit.

__________________
|
Meeow!

Maybe you can make a NTFS partition (with partition magic or any other).

Probably. I seem to recall that ntfs read/write from fat32 need specail drivers that run in 16 bit mode - not very fast or safe.

Nah, I'm happy frame serving - I don't miss >4G files.. they're a bugger to defrag anyway LOL

__________________
|
Meeow!

In regular you got a second partition where you store your VOB rips only for that time they are needed - afterwards they will be deleted.

And as Mencoder or any other encoder wont be recognisable slower in case of some fragments of source HD, that doesnt make it worth to keep everything in Fat31 ... so just format one Partition to NTFS.

I remember the days when RAM was that expensive and therefore we build an FWB sledgehammer RAID on a MAC cause there in the case to use Photoshop and a allocation to the HD as Virtual RAM .... there a mega clean Raid/Drive made sense

I was afraid it was evident to everybody...

Fluff, you've got an even shorter possibility to feed splitted-vobs to mencoder. You can pipe vobs in mencoder.
If you don't know how, make me know and we can explain.
This way there won't be paths, just vob -> mencoder (through piping)

@ Digi Doc

Ya, I tried the copy /b vob + vob + vob > mencoder (obviously with the right file names.. )

but it thrashed the hard drive for minutes reading the vob files. In the end I gave up.

__________________
|
Meeow!

@ Fluffbut

As you said you are working under FAT32 .... a merging of the VOBs would overflow the specs of max FAT32 filesize!

DigitallDoc meant the way how mencoder does automatically recognises the following VOBs if just pointig to the first VOB using a special Command in Mencoder.

From mencoder manpage.html :

cat D:\PathToVobs\*.VOB | mencoder <options> -

So try to put all your VOB beginning from VTS_XX_1.VOB (not 0!! Thats the Vob contain. the menues) into a folder and point to that via mencoder:

(VTS_01_0.VOB) not!
VTS_01_1.VOB
VTS_01_2.VOB
VTS_01_3.VOB
VTS_01_4.VOB
VTS_01_5.VOB

In here _01_ is the track incl. the movie

Seems that the "cat" tells mencoder that there is a "catalogue" of vobs to be encoded as one resulting file (m2v) ?

So this post here is JUST IMHO!

@ Fluffbut
Look at
http://zebra.fh-weingarten.de/~maxi/.../msg00374.html
and http://article.gmane.org/gmane.comp....yer.user/28318