HC encoder, release 016 [Archive] - Page 4

Prodater64

30th December 2005, 17:33

704x480, 23,976, and HCenc gives me warning that this is not DVD compliant framerate :confused: Of course I can't start encoding (press encode, blink of encoder window, and back to gui).
Help ?
Actualy I must add, that I don't remember to have this error under wine, strange :|

You wrote 23,976.
Try 23.976.

christoofar

30th December 2005, 18:45

Prodater

any new complie of HC_error kill to try yet?

cheers

Asmodeus

30th December 2005, 20:45

You wrote 23,976.
Try 23.976.
It's obvious that avisynt accepting "." not "," , it's misswriting. If it was "," then I will get avisynth error, and not hc problem.

neo squidward

30th December 2005, 21:26

Usually at the very end of each encode when HCBatch_016.exe is exiting, I get an error. I also get this error sometimes when just clicking "Exit". It is really getting on my nerves because last night I had a batch file running and it was supposed to do a couple movies, but this error pops up after the first movie gets encoded and makes my batch file pause so when I wake up only one movie got encoded. Very frustrating. The error is usually saying cant read/write to some place in memory (I'm not sure the exact error). This and HCGUI is the only programs I get these kind of errors on so I doubt my memory is bad.

Prodater64

30th December 2005, 21:53

neo squidward

30th December 2005, 22:43

Thanks but the link is down for HC encoder error killer. http://rapidshare.de/files/4338185/HC_Encoder_-_Kill-Error.zip.html

Prodater64

31st December 2005, 00:48

That is a bug in HC Encoder (and many other programs) together with Windows XP SP2, and maybe programation language or codecs.

Your workaround ATM is http://forum.doom9.org/showthread.php?p=703225#post703225

You are trying to download an old file, go
http://forum.doom9.org/showthread.php?p=703225#post703225
and download Kill-error_en.zip (i suppose your system is in english language).

Please if you have a question related to Kill-error, post in its own thread, thanks.

@hank315: "memory couldn't be read" error is each day more frequent with HC (and other programs). The problem could be programation language together with mpeg codecs and XP issues. Could you investigate in this aspect.
The problem is not only with HC, i have same problem with programs that manage codecs as Power DVD, Media Player Classic, AVI codec, Camtasia Recorder, etc. There are many factors. It would be nice find out the trully reason of this error.

dragongodz

31st December 2005, 07:06

Usually at the very end of each encode when HCBatch_016.exe is exiting, I get an error.
http://forum.doom9.org/showthread.php?t=103195 :D

neo squidward

31st December 2005, 07:47

So I guess this means hank315 is aware and the problem will be fixed in the next release. Great news

ljpp

4th January 2006, 20:18

Okay, about time for the HC to get an official homepage, and now it does:
http://hcencoder.bitburners.com/

gilligan2

4th January 2006, 21:01

Okay, about time for the HC to get an official homepage, and now it does:
http://hcencoder.bitburners.com/

nice. ;) :goodpost:

FredThompson

8th January 2006, 03:14

To my eyes, HC gives better results for almost every source except high-speed interlaced for which I prefer the results of ProCoder. Maybe that's an issue of motion detection, maybe not. I have, however, noticed on quite a few inspections that ProCoder does a very good job of keeping the chroma of edge pixels of the 8x8 blocks quite similar. HC doesn't do as good a job. Perhaps, just perhaps, there is something to be mimiced here. If the edge of one block is more similar to the edge of the adjacent block, that should yield a smoother image as seen by human eyes, which are especially attuned to motion and straight edges. Why do I say this? I'd love to see HC outperform ProCoder.

PlazzTT

12th January 2006, 21:40

I'm having trouble getting my AviSynth files to load.

I have AviSynth 2.5.6.0 (checked in HC) but when I try to load my AVS file, the words "AVS file opened" flash in the info box for just a sec, and then they disappear and the input file name remains unspecified.

My AVS file is just an AviSource line, loading an AVI. The AVI is encoded with Arithyuv Lossless Codec. The AVS works okay in MPC.

HC can open AVS files with an MPEG2Source line.

EDIT: Also tryed AviSynth 2.5.5, no luck.

Boulder

12th January 2006, 22:22

Does it work with DirectShowSource? I don't know if Arithyuv has a DirectShow decoder though. I've sometimes had problems opening files encoded with ffdshow's mjpeg codec with AVISource, but with DSS they work just fine.

Ebobtron

12th January 2006, 23:15

@PlazzTT
HC can open AVS files with an MPEG2Source line.Sure it works when using Mpeg2Source in your scripts as most mpg sources result in a YV12 color space output from AviSynth.
Many Avi Sources will be other than YV12 which can be the problem because HC only takes AviSynth scripts that output YV12
Put info() in your AviSource scripts, it will tell you what your script is outputting.
Use ConvertToYV12() to convert before HC
ATM it appears that HC is trapping the incorrect input file but doesn't tell us about it, just ignores it.

http://members.aol.com/avsfilmcutter
If you where using FilmCutter you could just hit F8 to see your script output properties. You can even test your script for proper ColorSpace when you launch your encoder from FilmCutter. <- shamless plug, sorry

PlazzTT

13th January 2006, 00:16

Excellent, thanks. DirectShowSource works, I'm guessing AviSource with ConvertToYV12() will too.

Ebobtron

13th January 2006, 13:08

Excellent, thanks. DirectShowSource works, I'm guessing AviSource with ConvertToYV12() will too.
I should recuse myself from any comments about DirectShow and DirectShowSource. But to speak about “Arithyuv” which is a VideoForWindows codec, I believe you would be far better off using AviSource.

In order for DSS to output YV12 when using a clip encoded as YUY2, DSS in using a color space conversion filter which you may not have any control over. You do not need DSS to input the source, so you again a little speed, much better seeking. And IMHO something that will work next month as it does this month.

Good luck

Boulder

13th January 2006, 13:13

You can force DirectShowSource to output the colorspace you want. If you know that the original colorspace is YUY2, just use the parameter pixel_type="YUY2".

As I was unsure whether the codec contains YV12 stuff or not, I suggested trying DSS;) In fact, AVISource will always output YV12 first if the codec supports outputting it. That's something you need to remember for example when dealing with YUY2 capture files.

Mug Funky

16th January 2006, 10:11

about ffdshow, avisource and HC:

i find anything that ff_vfw.dll decodes crashes HC on opening. with directshowsource it doesn't. strange.

i've tried 3 ffdshow builds, and several different codecs within ffdshow and all die. but with directshowsource it's fine... peculiar.

Mug Funky

25th January 2006, 02:30

wee! i just discovered this morning that if you encode off the network and the computer your files are on crashes, HC keeps patiently waiting until that machine is back, and then continues encoding! that's very cool :)

scraper

26th January 2006, 19:15

Hi Hank,

Just noticed something in the log-file while fooling around:
I was encoding a 23.976fps source with a width*height of 720*576.

Here's part of the log:

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

nr. of frames in source: 127690
width*height: 720*480
fps: 23.98

:confused: Is width*height assumed, base on fps?

See you, Jan Peter

Rippraff

26th January 2006, 19:34

23.976fps
This is NTSC
and this 720*576is PAL.

720*480 is the correct resolution for NTSC.

Cu Rippraff

ron spencer

26th January 2006, 19:51

I just wanted to say that this encoder has been doing a superb job for me with my interlaced hi-8 home movies....slow on my pIII 866 but well worth the overnight wait!!!! I can't wait to see new versions!!!!

Boulder

26th January 2006, 21:04

This is NTSC
and this is PAL.

720*480 is the correct resolution for NTSC.

Cu Rippraff
Maybe he wants to use DGPulldown and do a 23.976->25fps pulldown for NTSC->PAL conversion? That way he can use the original audio track. (However, there is a slight jitter introduced to the video with such conversion)

Ebobtron

27th January 2006, 05:46

scraper,Is width*height assumed, base on fps?
No. Width, height and fps are provided by the source. If your encoded m2v is the width, height and fps that you expected the problem is, I'm sure in the log generation.
:goodpost:
I is sure Hank will fix.

As for the rest ???
23.976fps is NTSB Film.

scraper

30th January 2006, 08:37

Hi guys,

sorry for the late reply... buzy few days.
I was in fact trying to use dgpulldown to do a ntsc > pal conversion. So i had to use that combination of weirdness...
Which introduced another thing:
When i muxed it all together, muxman complained about a buffer underflow being detected. Shouldn't that have been detected by HC?

JP

smok3

2nd February 2006, 09:07

iam planning to encode certain files using q5 + dvd compliance bitrate limiter, however iam seeing some weird seeking problems using either mplayer or powerdvd (lenght is changing in powerdvd, mplayer cannot decide where it is also - looking at the osd)

virtualdubmod seems to open them fine, also no problems with mpc.

ini file is simply:
*MAXBITRATE 8000
*FRAMES 1 15000
*ASPECT 4:3
*CQ_MAXBITRATE 5.000
*MATRIX mpeg

Mug Funky

2nd February 2006, 09:42

@ scraper:

it might just play fine anyway... :)

different programs have different ways of measuring bitrate, as do different playback devices. HC (i think) measures bitrate GOP wise - it measures bits/sec for each GOP, but i'm not aware if it takes other GOPs into account. anyway, it should be fine, but burn a RW and check in a standalone or two :)