HCenc v 0.20 new version released

[grannyGeek]

http://www.bitburners.com/Software/Download/Video_Codecs_and_Encoders/HC_Encoder/HC_Encoder_v0.20/

First reports at doom9 speak of marked speed increases.

[FulciLives]

I can't wait to try it ... I just hope the built-in 3:2 pulldown was fixed because it wasn't working correctly in the last version yet I see no specific mention of it being fixed in the change log.

- John "FulciLives" Coleman

[Robert Simandl]

Faster? Wow, this program already smoked TMPGEnc Plus (I tried the same avs script with the same options in both a few months back and HC v0.19 got the job done in an hour and a half while TMPGEnc took 4 hours).

[hank315]

I can't wait to try it ... I just hope the built-in 3:2 pulldown was fixed because it wasn't working correctly in the last version yet I see no specific mention of it being fixed in the change log.

There's a fix implemented for 3:2 pulldown, in HC019 flags were written correctly but timecodes weren't
Should be fixed in this release, some feedback would be useful

[AlanHK]

Just tried it. About 14% faster it seems on my PC.

AutoGOP apparently has a lower setting for 23.976 fps, so that should keep it in spec.

[FulciLives]

Just tried it. About 14% faster it seems on my PC.

AutoGOP apparently has a lower setting for 23.976 fps, so that should keep it in spec.

I did read some (most) of the doom9 thread and I noticed that the GOP issue was addressed but saw nothing about 3:2 pulldown. I am glad to hear that 3:2 pulldown should work now.

I will report on this once I get a chance to encode something.

- John "FulciLives" Coleman

[hank315]

Autogop still uses a standard GOP length of 15, if the source is 23.976 it will switch to a GOP length of 12 because it's a candidate for pulldown.
GOP lengths of 12 - 14 are valid for pulldown but some authoring apps only take 12 as input.

I did read some (most) of the doom9 thread and I noticed that the GOP issue was addressed but saw nothing about 3:2 pulldown. I am glad to hear that 3:2 pulldown should work now.

I will report on this once I get a chance to encode something.

Thanks, appreciated

[andie41]

I have an Athlon Xp and only MMX/SSE but the new version is still approx 12% faster, when using the standard 2pass encode. However; when using CQ and VBV/max bitrate checked, the new version takes almost 3 times as long as version HC v0.19.

[gadgetguy]

I've used the new version a couple times now, but I set it and go to bed so I don't know if it's faster. I generally run HC from a .bat file and the new version removes the Caps from the target file name. ie: MyVideo.m2v becomes myvideo.m2v. Not a big deal, just something I noticed.

[AlanHK]

I've used the new version a couple times now, but I set it and go to bed so I don't know if it's faster. I generally run HC from a .bat file and the new version removes the Caps from the target file name. ie: MyVideo.m2v becomes myvideo.m2v. Not a big deal, just something I noticed.

That's a regression, I pointed that out and Hank fixed it a couple of versions ago.

You can read off the exact times it takes from the log file, that's how I gave my estimate.

[FulciLives]

I finally got a chance to use HCenc v 0.20

The source was a downloaded Xvid AVI with a frame rate of 23.976fps

I used AviSynth to "prepare" the file (resize and filter) and used the auto GOP option and the 3:2 pulldown option in HCenc (I also did CLOSED GOP's).

The resulting video file seems to be A-OK ... the GOP was correct at 12 and the 3:2 pulldown appears to be correct. TMPGEnc DVD Author 2.0 did not "puke all over" the file (as with the previous version of HCenc) and MUXMAN also worked A-OK.

Haven't played back on a TV yet but PowerDVD played back OK and both authoring applications seemed to "like" the file so ... I think the 3:2 pulldown is working A-OK right now

- John "FulciLives" Coleman

[dvd3500]

Hey FulciLives,
Any noticible speed increases?
Thanks...

[gadgetguy]

You can read off the exact times it takes from the log file, that's how I gave my estimate.

I could, but I don't keep the logs, so I don't have any old ones to compare with. I did notice the estimates were shorter, but Ive never had much faith in those estimates anyway.
I haven't had the chance yet to see if this version corrects the other problem I was having using HC encoded files with TDA1.5. (in this thread) But I should be able to test that sometime next week.

[hank315]

I think the 3:2 pulldown is working A-OK right now

OK , thanks for testing...

MyVideo.m2v becomes myvideo.m2v. Not a big deal, just something I noticed.

Will have a look at it and fix it...

@andie41
What settings did you use in the CQ encoding?

[andie41]

What settings did you use in the CQ encoding?

I am not really concerned about file size, so I have been using CQ 2.00 to 2.50 with max bitrate of 8500 kb/s. My source is NTSC DV interlaced, BFF, using default MPEG matrix, GOP 15, no avisynth filters. After more testing, not quite 3x, but over 2x for encode times with v0.20. Also, the file sizes are aprox 10% smaller with v0.20, so perhaps more efficient compression.

[FulciLives]

Hey FulciLives,
Any noticible speed increases?
Thanks...

According to the log file it took a total of 2 hours 15 minutes and 2 seconds for a 2 pass VBR on the "BEST" setting. The source was only 42 or 43 minutes long but it was YV12 and I had to convert to YUY2 for some filter use and then back to YV12 so I suppose that is why it took as long as it did. I know it would have taken longer with CCE SP but then again when I use CCE SP I tend to use 4 pass VBR (1 for the VAF with 4 additional passes for 5 total). I think the speed achieved was very good considering the colorspace change and filtering done. How it compares to HCenc v 0.19 speed wise though I don't know.

Here is the AviSynth script I used:

LoadPlugin("C:\COPY_DVD\Convolution3D_yuy2\convolution3d.dll")
LoadPlugin("C:\COPY_DVD\blockbuster_25_dll_20030204\blockbuster.dll")
AVISource("L:\VIDEOS\video.avi")
ConvertToYUY2()
BlockBuster(method="noise")
Convolution3d (preset="movieLQ")
LanczosResize(672,448,0,0,624,352)
AddBorders(24,16,24,16)
ConvertToYV12()

Here is the log file from HCenc v 0.20

              -----------------------------------------
              | HCenc - MPEG2 encoder - rel. 0.20.0.0 |
              -----------------------------------------

MPEG profile@level:   MP@ML
input:                c:\zzz\video.avs
output:               c:\zzz\video.m2v

              --------------------
              | encoder settings |
              --------------------

profile:              BEST
frames:                      0   60799
framerate:              23.976
aspect ratio:         16:9
bitrate Kb/s:             5800
max. bitrate Kb/s:        8000
pulldown:             yes, 23.976 --> 29.97
closed gops:          yes
VBV check:            yes
scene change det.:    yes
interlaced:           no
goplen,B-pic:         AUTO
dc_precision:               10
scan method:          ZIGZAG
bias:                        0
chapter frames:              0
time code:                   0       0       0       0
CPU:                  SSE3
matrix:               MPEG

              ------------------
              |  source stats  |
              ------------------

nr. of frames in source:           60800
width*height:                   720x480
fps:                               23.98
nr. of frames to encode:           60800
frames to encode:                      0 -    60799

              ---------------------
              | encoding - pass 1 |
              ---------------------

pass1 encoding time:             0:56:56  (3416 s)
fps:                                17.8

              --------------------------------
              | encoding - intermediate pass |
              --------------------------------

bitrate set to:                     5800 kb/s
est. outfile length:             1795413 kB
intermediate encoding time:          0.7 s

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

 *** INFO, adjusting average bitrate:  -0.26  %
 *** INFO, adjusting average bitrate:  -0.44  %
 *** INFO, adjusting average bitrate:  -0.55  %
 *** INFO, adjusting average bitrate:  -0.69  %
 *** INFO, adjusting average bitrate:  -0.85  %
 *** INFO, adjusting average bitrate:  -0.91  %
 *** INFO, adjusting average bitrate:  -1.01  %
pass2 encoding time:             1:13:51  (4431 s)
fps:                                13.7

              ------------------
              | encoding stats |
              ------------------

total CPU time:                  2:10:48  (7848 s)

intra matrix used
   8  16  19  22  26  27  29  34
  16  16  22  24  27  29  34  37
  19  22  26  27  29  34  34  38
  22  22  26  27  29  34  37  40
  22  26  27  29  32  35  40  48
  26  27  29  32  35  40  48  58
  26  27  29  34  38  46  56  69
  27  29  35  38  46  56  69  83

non-intra matrix used
  16  17  18  19  20  21  22  23
  17  18  19  20  21  22  23  24
  18  19  20  21  22  23  24  25
  19  20  21  22  23  24  26  27
  20  21  22  23  25  26  27  28
  21  22  23  24  26  27  28  30
  22  23  24  26  27  28  30  31
  23  24  25  27  28  30  31  33

nr. of gops:                        5512
nr. of frames:                     60800
nr. of I-frames:                    5512
nr. of P-frames:                   22575
nr. of B-frames:                   32713
average bitrate:                    5739
minimum bitrate:                     138
maximum bitrate:                    7999

bytes in bitstream:           1819816927
bits in bitstream:           14558535416

total elapsed time:              2:15:02  (8101.89 s)

To be honest I am not all that concerned with the supposed speed increase. I am more concerned with the auto GOP setting and 3:2 pulldown setting ... both now seem to work as they should ... this was not the case with the last version of HCenc. So I am a happy camper!

I admit I am interested with the HDTV resolution support but for now I have no need for it although I am sure that once HD DVD and/or Blu-Ray computer burners become more commonly available that this will be a feature that will become important. For now though it's more of a "huh that's kinda kewl" thing but I can't really do anything with it ... yet.

Please note that the computer specs listed on my account is the computer I used for this encoding.

- John "FulciLives" Coleman

[gadgetguy]

I haven't had the chance yet to see if this version corrects the other problem I was having using HC encoded files with TDA1.5. (in this thread) But I should be able to test that sometime next week.

Tested today and I no longer have the problem. HCenc v0.20 resolved the issue.