Command Line Compressor - AVS2AVI

[DaveEL]

make sure you dont have a resume.codec in the current directory and don't use the -r switch (which will create a resume.codec) it should then never use the resume support if you still have the problem post here again and ill have a look.

DaveEL

[TaZ4hvn]

It was with 1.25, strangely enought it wanted to resume a job already finished !
And I'm definitly sure I didn't use the -r switch.
Reading this thread I shearched for a resume.codec but didn't find any...( that's perhaps why it failed to resume I guess).

I switched to 1.26, then had a resume.codec and a resume.stats, deleted them, and now all is going as expected.

Thanks for you reply and especially for this great tool :)

[DaveEL]

ok new version at last just a changed avi writer no resuming support at all (all code has been removed pending a rewrite use 1.25 if you want that).

http://daveel.leffe.dnsalias.com/avs2avi-126.zip

DaveEL

[TaZ4hvn]

Thanks a lot for the mod.
I'll try to see if it works the way I want...

[wotef]

a couple of feature requests from me:

prior to executing an encode, is there some way to set the processing priority to "below normal" or "idle" - like vdub ("lower","lowest", etc)?

also, prior to pressing the "encode" button on the gui (which prompts the user to select and configure a codec from the codec window), is it possible to set a default codec, e.g. to immediately be able to encode to huffyuv all the time? or via a command line?

[[Toff]]

For priority it's the "p" parameter:
-p [0-3] : Priority (0:idle, 1:normal, 2: above, 3:high)

To use the huffyuv codec without prompt you can use :
-c <4cc> : Use codec having <4cc> with default settings

Example:
avs2avi movie.avs movie.avi -p 0 -c HFYU

[wotef]

thanks - it would be nice to have a readme.txt at some point + corresponding gui enhancements

btw, with the latest binary, huffyuv encoding creates invalid avis that cause vdub to say "unable to locate decompressor for fourcc hfyu" when attempting to open them - attempting to play them crashes both bsplayer and zoomplayer

[DaveEL]

if you run avs2avi without any parameters it will tell you about all the options it supports the and gui is made by someone else.

DaveEL

[TaZ4hvn]

@DaveEL:

I intensively tested the version you made without resume support and it works flawlessly: Thanks a lot.
But it remains the samll cosmetic issue of the fps, doing over 6000fps must remains a dream :D
If you can fix it in this version too ...

Regards

[DaveEL]

Once my final year project is done ill take a look at fixing it but im rather busy at the moment. :)

DaveEL

[TaZ4hvn]

Sure ! This is far from being a major issue :p

[mfluder]

Originally posted by wotef
a couple of feature requests from me:

prior to executing an encode, is there some way to set the processing priority to "below normal" or "idle" - like vdub ("lower","lowest", etc)?

also, prior to pressing the "encode" button on the gui (which prompts the user to select and configure a codec from the codec window), is it possible to set a default codec, e.g. to immediately be able to encode to huffyuv all the time? or via a command line?
This is already available in my GUI. You can set process priority just like [Toff] wrote and you can also use any codec you want by typing in a 4cc of that codec in editbox labeled "Use codec:" or if you use XviD (which you probably do) you can just enable that checkbox and also configure it with "Settings" button.

There is a possibility that you don't have the latest version of my GUI so if that is the case then go to page 8 of this thread and you'll see my post with attachment.

mfluder

[wotef]

thanks again

:stupid:

[TheUnforgiven]

I get AVISetStream Error message (or something similar) in the beginning of the second pass when i use with DivX5.05. maybe i am doing something stupid cuz i left divx to xvid long time ago.

[DaveEL]

ill check that one tomorrow divx doesnt get a lot of testing as i use xvid all the time too :) if you can post exact error and version of avs2avi it would be good.

DaveEL

[Wilbert]

Could you include the latest gui in the avs2avi package in the first post on the first page? That way, people can't find it a bit easier :)

[TheUnforgiven]

the error is "AVIStreamSetFormat Failure"
and the version is the latest

[DaveEL]

Originally posted by TheUnforgiven

and the version is the latest

No its not latest is 1.26 that code doesn't exist in 1.26.

DaveEL

[TheUnforgiven]

Sorry it is 1.25
does that mean 1.26 does not have this problem?
gonna dload it now.

[jonny]

1.26 use a new lib to write Avi (avilib)
This is a good step to avoid vfw problems (MS vfw interface is full of bugs :))

[Satirik]

i don't know if anyone ever say that but whan i make xvid files , they are corrupted with version 1.26 ... i think the header is bad ...

[jonny]

What happen exactly?
The avi isn't playable or there are problems on video?

If i'm not wrong, the main difference is that with avilib the "strf" tag is fixed to 40 bytes (so a normal BITMAPINFOHEADER structure).

VDub creates strf of 40 bytes for DivX
With VDub+XviD strf is 108 bytes long, so i think that calling ICCompressGetFormat is needed here (i don't know if it's easy to fix this on avilib... i'm not sure this is the problem :))

[DaveEL]

I was sure i created working xvid stuff with 1.26 oh well avilib seems to have other problems so im going to have to switch libs anyway.

DaveEL

[jonny]

The avilib fix could be not hard.
Let's see what is the exact Satirik's problem first.

[Satirik]

Originally posted by jonny
The avilib fix could be not hard.
Let's see what is the exact Satirik's problem first.

divx are perfect no problems ... i make xvid and mediaplayer can't read them and vdub either ... i opened these with note pad and the header was apparently not the same for divx and xvid but i didn't search more :) because i didn't understand how a soft can make two different header with two different codec with the same avilib :) normaly only the fourcc change nope ?

[DaveEL]

Ok i worked out why it worked for me it decodes fine in ffdshow/ffvfw but not the xvid decoder.

DaveEL

[jonny]

I've added AVS2AVI support on Enc.
For those interested, check this thread:
http://forum.doom9.org/showthread.php?s=&threadid=50714
(AVS2AVI v1.27, not released by Dave, is included in my homepage)

@Satirik:

because i didn't understand how a soft can make two different header with two different codec with the same avilib normaly only the fourcc change nope ?

avilib it's a library that came from linux, and it's a bit different from the VDub lib. Actually there are 100+ different ways to write an Avi file, the header it's composed by different parts and one of this parts is not correctly managed by avilib.

[bilu]

@jonny and DaveEL

What's new on this version? Should I update it also in my tool?

Bilu

[jonny]

There is a new option: -o l
This option generate a log file containing the type & size of each frame encoded.

Example:
avs2avi test.avs vdenc.log -o l

Using -o l the log file is written, instead of the avi file.

It's basically a porting of VirtualDubMod's /log /nowrite on avs2avi :)

The log format is something like this:

1 43433
0 10003
0 8993
0 3221
0 5004
1 30329
0 3433
and so on ...

The first number in each line is the frame type (1=keyframe, 0=deltaframe).
The second number is the size in bytes of the encoded frame.

This log is power for size prediction ;)

[DaveEL]

Just like 1.27 but should work this time. :)

http://daveel.leffe.dnsalias.com/avs2avi-128.zip

DaveEL

[Satirik]

it work perfectly this time :)

[TaZ4hvn]

Thanks DaveEl for systematic reporting of new version in bilu's thread and mine.
I'm giving 1.28 a try right now :p

[DaveEL]

Im not sure ill do it again its a little too close to rule 8 but its an important update for the xvid tools.

DaveEL

[eXistenZ]

After a while being out of "encoding world", I've restarted to test all this great tools...

I've encoded a 3hr movie using the following chain:
avisynth 2.5.2 (mpeg2dec3 1.04)
koepi's xvid 14052003-1 b-frame 2/100/200/0
avs2avi 1.28
enc 1.03

The result avi is not seekable and opening it with virtualdubmod 1.4.13.2, reports "BFrame Decoder Lag"...
Well, technically, it's seekable, but it takes a while...

I think it's avs2avi fault, 'cause encoding with virtualdubmod 1.4.13.2 works fine...

BTW, this thread is becoming huge, why not split it, or create an avs2avi forum :p

[DaveEL]

1.29 is out

http://daveel.leffe.dnsalias.com

It writes out keyframes this time :)

DaveEL
PS if anyone wants me to e-mail them when i release send me a pm.

[eXistenZ]

Well, thank you for your work and the quick reply :),but
sorry DaveEl, I can't find avs2avi 1.29 at your url :confused:

And, I think 1.29 is supposed to correct "BFrame Decoder Lag" bug, isn't it? ;)

[DaveEL]

whoops looks like i reuploaded 1.28 again :) try now

DaveEL

[DaveEL]

Originally posted by eXistenZ
BTW, this thread is becoming huge, why not split it, or create an avs2avi forum :p

I need to find time to summarise the thread then ill open a new one and close this one, but i don't really have time.. unless someone else wants to do it for me :)

DaveEL

[kilg0r3]

Originally posted by eXistenZ
"BFrame Decoder Lag" bug, isn't it? ;)
Afaik this is no bug but due to not using DX50 compatibility mode. BTW it does not affect playback, AFAIK at least.

[DaveEL]

Originally posted by kilg0r3
Afaik this is no bug but due to not using DX50 compatibility mode. BTW it does not affect playback, AFAIK at least.

No this is a seperate bug in in avs2avi 1.28 which produced the same error message.

DaveEL

[kilg0r3]

o.k. :)

[eXistenZ]

Yep, I tested avs2avi 1.29 with the same chain and option as reported previously... and I happily confirm that bug's dead :D

(of course I always keep DX50 compatibility a.k.a. closed GOP on)

eXistenZ

[TaZ4hvn]

For some strange reasons I enabled error reporting in XP and avs2avi generates an error when closing each time.
Not a big thing since I can add it to ignorer list, but i think you'd like to know :)

[DaveEL]

Hmm strange does the xp error report allow you to get more info? If so could you post it please.

DaveEL

[TaZ4hvn]

Sorry that's what I should have begin with :p.

AppName: avs2avi.exe AppVer: 0.0.0.0 ModName: unknown
ModVer: 0.0.0.0 Offset: 0115f6c0

Sorry i cannot copy the full memory dump, anyway i'm not sure it would be usefull !
Well finally looks like i can't give usefull info. But I realised that was with 1.25 (sorry), I will try with 1.29.

EDIT: It does it with 1.29 also :(
I'm looking for a way to give usefull information ...

[TaZ4hvn]

Another cosmetic problem in 1.29:
while things are ok when program is running, size changes to 0.000MB and fps to 0.00fps as soon as it finishes.

[Satirik]

hum please write averange fps not instant fps ...

[joker]

no, instant is just fine while it is encoding, average at the end.
that's the way it should be.

(or maybe better: write 'instant / average' while it is encoding?)

[N_F]

Originally posted by DaveEL
I need to find time to summarise the thread then ill open a new one and close this one, but i don't really have time.. unless someone else wants to do it for me :)

DaveEL

That would be nice. I only became aware of this program when jonny added support for it in Enc. I'm not too keen on reading through 300 posts so a summary would be very nice.

[TaZ4hvn]

hum please write averange fps not instant fps ...
Isn't it exactly what I did :confused:

no, instant is just fine while it is encoding, average at the end.
Ho come on guy ! Your first post ... I hope next will be better.
I'm very glad to know it works for you :D
It remains it does not for me.
If every time somebody is posting a problem with his box, everybody not having this problem reply to say it's ok for them, threads will certainly grow a bit ... and what is it good for ??

(or maybe better: write 'instant / average' while it is encoding?)
Try the program and you see there's no average fps while encoding :sly: