HCenc 022 released

[hank315]

Major changes:
- multiprocessor support
- improved interlaced encoding
- more CLI input
- as usual some bug fixes

Also added settings for:
- priority
- colorimetry
- MPEG level
- Avisynth

http://hcencoder.bitburners.com

[Guest]

Thank you, Hank!

[Lorax2161]

Major changes:
- multiprocessor support
- improved interlaced encoding


Gratefully appreciated. Looking forward to many hours of encoding this week!

- Lorax2161

[Dkruskie]

Thanks

[video_magic]

Thanks Hank! Especially for a priority option :)

[45tripp]

very nice additions
:thanks:

[Adub]

Holy Smiling Cows, Batman!

Thanks a lot, Hank! Know that your work is always appreciated!

[urvieh]

This is excellent, man. Encoding (BEST level) at 160 fps with one encoder window only ... And the processor shows 85 percent ... Great! Thank you!

[linx05]

Thank you so much. I was going through the threads last night wondering when a new release was going to happen.

[Sharc]

The colorimetry settings are most appreciated. Thanks!

[tom942]

Thank you for the new release :).

[Pookie]

Hank, you're a great man. Thanks so much. :)

[kumi]

Thanks Hank, it's great to have a new version.

Can you give us some more details about the nature of your improvements to interlaced encoding? What differences should we look for, if we're comparing HC 0.21 to 0.22?

[Malcolm]

Great!

[AlanHK]

Thanks. Using it now.

However, it still has the "feature" of forcing the name of output files all lower case.

[FrontierDK]

Major changes:http://hcencoder.bitburners.com

Is there a chance that we'll one day see a normal AVI import? This encoder is truky one of the best around, but doing something as simple as opening an AVI and encode it...is quitle a hazzle, especially for newbies...

So...why not implement .AVI (and maybe even frameserving from VirtualDub)? :-)

[AlanHK]

So...why not implement .AVI (and maybe even frameserving from VirtualDub)? :-)

In the meantime, just use FitCD to make an AVS script. That's how I start most of my scripts.

Actually, to do what you want, Hank would have to make a front end pretty much like FitCD.

There are several apps like AVI2DVD and FAVC that can take an AVI and generate a DVD fileset, using HCEnc to make the MPEG.

[MrC]

- multiprocessor support


Great!


- more CLI input


Great^2!

Keep up your wonderful job!

:thanks:

Bye

[buzzqw]

:thanks: hank315!!!

BHH

[smok3]

:thanks:

how would i go with autodetect interlacing? (from cmd)

[buzzqw]

i suppose you must firstly know your source file...

like for DV

BHH

[Rippraff]

:cool: Thank you very much, Hank! :)

Cu Rippraff

[totya]

Multiprocessor support... Thank you! :)

...and small question, which mpeg2 matrix recommended for low, average, and high bitrate?

[phXql]

Thank you, Hank!

[hank315]

About interlaced encoding:

It now has settings for:
- progressive, stream is handled as completely progressive
- interlaced, default TFF (can be set to BFF)
- DV source, default BFF (can be set to TFF)

If no setting is given it will auto detect the nature of each frame and then encode it as progressive or interlaced.
TFF is default but can be set to BFF.


Using it from the command line the same applies, possible parameters:
-progressive
-interlaced
-dvsource
If none of these are given it runs in auto detect mode.

Using the *FRAMELOG command you can get info about the encoding:
- frame type and frame size
- progressive or interlaced
If a frame is encoded interlaced the % column shows the percentage of MBs which are done with DCT field encoding.

Is there a chance that we'll one day see a normal AVI import?
It's not as easy as it seems, using Fortran it's not possible to call the AVIFile API directly AFAIK, I need to write a lot of interface routines for that.
But maybe, some day...

...and small question, which mpeg2 matrix recommended for low, average, and high bitrate?
It's very dependent of the source and personal taste.

This what I use most:
- high bitrate FOX1 or FOX2
- average bitrate MPEG or BACH1
- low bitrate HCLOW or BACH1
Most of the time I also use *LUMGAIN 3.
But it's all a matter of taste.

[totya]

It's very dependent of the source and personal taste.

This what I use most:
- high bitrate FOX1 or FOX2
- average bitrate MPEG or BACH1
- low bitrate HCLOW or BACH1
Most of the time I also use *LUMGAIN 3.
But it's all a matter of taste.

Very thank you!

Then next question, which matrix recommended of high/med/low quality avi?

[six13]

Nice work Hank !! but what bit range do you consider high, medium and low for a DVD source?

thanks, good work.

[SquallMX]

HCEnc 0.22 Bug?:

"HCEnc: (6) ERROR, can´t not load Avisynth CreateScriptEnvironment"

# SOURCE
mpeg2source("E:\Temp\DVDTemp\Ratatoille\FullDisc\RATATOUILLE\VTitle 1\Ok.d2v")
#Telecide(order=1,guide=1).Decimate()
#FieldDeinterlace()
#FieldDeinterlace(blend=false)
#TomsMoComp(1,5,1)
#KernelDeInt(order=1,sharp=true)
#DGBob(order=1,mode=0)
#GreedyHMA(1,0,0,0,0,0,0,0)
#Telecide()
#SeparateFields()
# CROPPING
#crop(0,0,720,480)
#VobSub("FileName")
Undot()
#Temporalsoften(2,3,3,mode=2,scenechange=6)
#mergechroma(blur(1.3))
#FluxSmoothST(5,7)
#Temporalsoften(3,5,5,mode=2,scenechange=10)
#Convolution3d("moviehq")
#FluxSmoothST(7,7)
#Temporalsoften(4,8,8,mode=2,scenechange=10)
#Convolution3d("movielq")
#FluxSmoothST(10,15)
#SelectRangeEvery(280,14)
# FOOL CCEnc
#empty = BlankClip()
#AudioDub(last,empty)
converttoyv12()

Only with AVS scripts, version 0.21 works fine.

:thanks:

[buzzqw]

trim it to

mpeg2source("E:\Temp\DVDTemp\Ratatoille\FullDisc\RATATOUILLE\VTitle 1\Ok.d2v")
Undot()

(converttoyv12 isn't needed since mpeg2source already outputted yv12..)

and open in virtualdub

any errors ?

BHH

[SquallMX]

Hi buzzqw, VirtualDub load the script fine, same with HC 0.21.

:thanks:

[buzzqw]

SquallMX

i have test some more coplex avs script AND it's working

i suggest to reinstall avisynth 2.5.7, redo d2v with latest dgindex AND load the correct dgindex

BHH

[cweb]

Thanks for the new version!

[smok3]

If no setting is given it will auto detect the nature of each frame and then encode it as progressive or interlaced.
TFF is default but can be set to BFF.
tnx for explanation, another question: is there a way to get TTF/BFF info from avisynth to HC?

[tom942]

This what I use most:
- high bitrate FOX1 or FOX2
- average bitrate MPEG or BACH1
- low bitrate HCLOW or BACH1
Most of the time I also use *LUMGAIN 3.
But it's all a matter of taste.

High bitrate I suppose that it is over 4000

But, what is medium bitrate, a range between 3000 and 4000?

And what is low bitrate, a range between 2000 and 3000?

I ask this because each one got a different idea of what, high, medium an low is :).

Regards.

[SquallMX]

i have test some more coplex avs script AND it's working

i suggest to reinstall avisynth 2.5.7, redo d2v with latest dgindex AND load the correct dgindex

BHH

I was using Avisynth 2.5.6, with avisynth 2.5.7 works fine, thank you.

:thanks::thanks::thanks:

[totya]

High bitrate I suppose that it is over 4000

But, what is medium bitrate, a range between 3000 and 4000?

And what is low bitrate, a range between 2000 and 3000?

I ask this because each one got a different idea of what, high, medium an low is :).

Regards.

I think low is under 3500, 3500-6000 is med, high is above 6000.

[Boulder]

As has been said many times, high/medium/low bitrate depends on the material in question. For some material, 4000kbps is low but for some it is more than enough.

[tom942]

So Boulder, you are saying that is more reliable to take into account the average quantization, using for instance, Bitrate Viewer (I don´t know if there is a better tool).

Regards.

[Chumbo]

Many thanks. :)

[disturbed1]

Nice, SMP works great, allocated 720MB of RAM to avisynth.

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
9322 disturbed 18 0 2640m 807m 13m S 188 39.8 32:28.73 HCenc_022.exe

[Boulder]

So Boulder, you are saying that is more reliable to take into account the average quantization, using for instance, Bitrate Viewer (I don´t know if there is a better tool).

Regards.I usually set a level of quantization that is acceptable to my eyes, then either encode a sample large enough to represent the whole video or encode the whole video using constant quantization. I have P-factor at 1.05 and B-factor at 1.60 for this analysis phase. Then I check the average bitrate of the sample and compare it to the bitrate that I can allocate to the video.

[archaeo]

working great - thanks Hank

[six13]

@Boulder

so then you prefer to look at average quantization rather than bitrate. I ran a .VOB the source file was a TV capture interlaced that was authored to DVD files. With Bitrate Viewer the info. I got was Bitrate peak => 7736 and the Avg. bitrate was 4870 The Q level peak was 4.22 and the Avg. was 1.98

I tried it with a .VOB from a DVD rip Progressize and the #'s were.


Bitrate peak => 10179 and the Avg. bitrate was 8989 The Q level peak was 15.76 and the Avg. was 4.08

How should I read these #'s and how could I apply them to selecting a matrix, since you consider this a better method than high/medium/low when refering to bitrate?

[Boulder]

I don't use the characteristics of an existing encode, I use the sampling method in which I use the filters and matrix that I wish to use. Most of the time I use the MPEG standard.

In your first example, you probably could use a high-bitrate matrix. In the second one, I would first try a mid-bitrate matrix and see how it performs.

[six13]

thanks Boulder, but I am trying to understand how you determine that based on the #'s I provided. IE use a high bitrate for the first one and a medium for the second one.

With the first example it was encoded at 90%, the second one I haven't done yet, I have the files from the rip on my HDD.

thanks for the help.

[SpazzHH]

:thanks: Thanks Hank so much for all your hard work. I can't even begin to tell you how much enjoyment your encoder has given me.

[Terranigma]

I have a request. In future builds, could you allow for us to use more than 2 b-frames?
nvm, I found it. :D
It's in "Settings 2". :)
Kudos for such a great encoder.

Now all we need is for the ability to specify a minumum bitrate.

[Boulder]

thanks Boulder, but I am trying to understand how you determine that based on the #'s I provided. IE use a high bitrate for the first one and a medium for the second one.The quantization levels are very low in the first case, you might even notice encoder saturation. The second one has a rather low quantization level too, but I would be careful and play with MPEG standard first. Of course, the matrices that have been used in these videos play a big part. I assume that the MPEG standard or something similar has been applied.

[starkhouse33]

hi
When converting an vc1 evo to mpeg2 using hc.22 im getting an error source mismatch in pass 2 starting at frame: 109 in my log.this has happened twice now. encoding completes and everything looks correct just wondering what that error means.
Thanks

heres what it looks like in my log

---------------------
| encoding - pass 2 |
---------------------

*** ERROR, source mismatch in pass 2 starting at frame: 109

*** INFO, adjusting average bitrate: -0.03 %
*** INFO, adjusting average bitrate: -0.05 %
*** INFO, adjusting average bitrate: -0.06 %
*** INFO, adjusting average bitrate: -0.08 %
*** INFO, adjusting average bitrate: -0.10 %
*** INFO, adjusting average bitrate: -0.12 %
*** INFO, adjusting average bitrate: -0.14 %
*** INFO, adjusting average bitrate: -0.16 %
*** INFO, adjusting average bitrate: -0.19 %
pass 2 encoding time: 6:54:09 (24848.83 s)
fps: 8.8

[hank315]

*** ERROR, source mismatch in pass 2 starting at frame: 109
This means Avisynth didn't serve the same frame in the second pass, the mismatch starts at frame 109, this is most probably a codec issue.
The result might look good but it's not, the info which was gathered from the first pass is now applied on the wrong frames.
Try to solve it by checking "Reload Avisynth" in the settings 3 tab.