Req: *AVSRELOAD parameter

[Boulder]

Hi,

would it be possible to add the option to use *AVSRELOAD when encoding with HC? I have certain scripts that seem to work much better when *AVSRELOAD is utilized.

[jdobbs]

Done.

[Boulder]

Thanks :)

One other thing, the "lossless file for 2nd pass" option in HC0.22.1 is very useful with slow scripts. Would it be possible to add this one too?

[TomBrooklyn]

I suspect this may be one of those things that you shouldn't use if you don't know what it is, but now that it is on the Settings/HC Settings menu, but not yet in the Help Files as far as I could tell, I'll ask anyway...

What is AVSRELOAD and when should one select it?

[Boulder]

It simply forces reloading the Avisynth script when the 2nd pass initializes. It helps with seeking issues with certain scripts. If you don't know whether you need it or not - you don't ;)

[jdobbs]

I've added "*LOSSLESS" as an option for the next release.

[Boulder]

Thanks - I think it's soon time for a new donation since you've added a lot of my requests since the last one :)

[archaeo]

Hi,

would it be possible to add the option to use *AVSRELOAD when encoding with HC? I have certain scripts that seem to work much better when *AVSRELOAD is utilized.



Would you please elaborate on use for *AVSRELOAD and *LOSSLESS. How does it help certain scripts to run better in HC?

[Boulder]

I have some complex scripts that sometimes cause an Avisynth exception at the beginning of the 2nd pass if *AVSRELOAD is not used.

*LOSSLESS is like I mentioned in the other thread here, it speeds up the 2nd pass significantly if you use a slow script. On a script that only loads the source and doesn't do much more, it is not useful.

[archaeo]

*LOSSLESS is like I mentioned in the other thread here, it speeds up the 2nd pass significantly if you use a slow script. On a script that only loads the source and doesn't do much more, it is not useful.

So *LOSSLESS isn't a command that is of specific help to only HC encoder is it? Can *LOSSLESS also help to speed up a second pass when run through CCE? I ask because I have been testing some complex (and very slow) degraining scripts, and although they have worked extremely well, the speed is excruciatingly slow. I'll take any help I can get.

[Boulder]

It applies only to HC, HC creates the lossless file while doing the first pass and then uses it to run the second pass. There is a way to do a similar thing in other encoders, but it would mean some additional coding for jdobbs.

[Boulder]

Actually doing the same thing for any other encoder should be possible.

http://forum.doom9.org/showthread.php?t=132406

The only requirement is that the Avisynth script is loaded by the encoder every time a pass begins. I think CCE does that, I don't know what happens with the other ones.

EDIT: usage requires a bit of tweaking in the Filter Editor, but the basic idea remains.

[archaeo]

Interesting. The referenced script (Avs->Avi->HCenc) renders to avi before it renders to m2v, and it still runs faster :eek: (in some cases).
If I understand correctly - on first pass of a n pass encode it outputs video to the encoder and outputs a seperate AVI file at the same time (one pass = two outputs). On pass 2 it uses the avi file. In HCenc, *AVSRELOAD makes this possible. Pass 1 is slow (running full avs script), pass 2 is a lot faster (only using avisource). All in all it may enable a net speed gain by only running the avs script once..

I did read however there could be a problem with this on certain plugins that look at past/future frames, or where the video file is split.