View Full Version : Avisynth plugins help-PLEASE
hardkorn
10th January 2009, 06:27
Hi
I test encoded a video. Source is 1920x1080 16:9 interlaced, and I want a standard mpeg2 720x480 output.
I have two captures, before and after, I want to show you. The output looks too choppy. I don't know what to use to smooth it out.
Can you guys lend me a helping hand?
Original
http://img133.imageshack.us/img133/1113/originalkg6.jpg
After
http://img154.imageshack.us/img154/8486/afterum1.jpg
Thank you
neuron2
10th January 2009, 06:31
You have to tell us how you processed the video (script) and how you encoded it. We can't read your mind.
hardkorn
10th January 2009, 06:39
:)
I did as you guided me. No offense there mate. Using CCE, progressive frame ntsc 16:9 using the script given by you.
# PLUGINS
LoadPlugin("I:\AUTHOR\GORDIA~1.2\DGMPGDec\DGDecode.dll")
LoadPlugin("I:\AUTHOR\GORDIA~1.2\AvisynthPlugins\LeakKernelDeint.dll")
MPEG2Source("H:\AAAAAA\segment.d2v",cpu=4)
leakkerneldeint(order=1)
spline36resize(720,480)
I also tried all deinterlace options inside GK' avisynth editor. I also deinterlaced using CCE engine. Same choppy.
But using HcEnc as you said, it looks much much better than using CCE, but still those "blocks" are hurting my eyes. But no more flickering. I'll post a short 3 seconds sample.
I can't believe that from a 1920x1080 the result can be so disastrous.
Thank you.
Sagekilla
10th January 2009, 06:41
You can safely use a dumb Bob() instead, which will speed up things a little bit.
Can you provide a short (5 - 10 second) sample of the video so we can have a look?
hardkorn
10th January 2009, 08:15
Here they are
CCE encoded 4PASSES-DEINTERLACED -6580 kbits/s
http://www.megaupload.com/?d=QS21Q75U
And
HCEnc encoded-2PASSES 6580 kbits/s
http://files.filefront.com/HCENCrar/;12926804;/fileinfo.html
Thanks
neuron2
10th January 2009, 09:06
I looked at the HC encode and I don't see the artifacts shown in your "After" shot. What blocks are you talking about? You can try raising the bitrate.
hardkorn
10th January 2009, 10:22
Time: 0:08. Look at the white collar! It's not as smooth as it should be. The bitrate is pretty high.
What about the artifacts produced by CCE? In the first few seconds they are more visible.
*.mp4 guy
10th January 2009, 10:59
Thats a farily average looking encode. The only real problems it has are the aliasing on the pillars in the first short shot, and the blocking/banding in the background (most visible in the upper right corner behind julie andrews, in the cce encode). There is also some aliasing throughout the encode (I think it is what you are talking about on the white collar), but it is at normal levels, and reducing it would cause other artifacts.
If you are very unhappy with the results you are getting, you could post a sample of the HD footage, and ask for advice on converting it to SD with as few artifacts as possible, and see what people can suggest. However, be warned, most proposed scripts will be significantly slower then what you are using now.
[edit] Also, a more desciptive thread title will get you more usefull replies.
hardkorn
10th January 2009, 11:26
Thanks for your input *mp4 guy.
Why does CCE give such a bad output comparing to HCEnc? And all that flicker right at the beginning? It was encoded with 4 passes and it's worse than hcenc. I've never had so much problems encoding any footage, ever.
What do you mean by SD? (me->noob)
*.mp4 guy
10th January 2009, 11:41
HD= high definition 1920 or 1280, by 1080 or 720 pixels
sd= standard definition, 720 by 480 or 576 pixels
both encodes look extremely similar to me, if you are seeing large differences between them, you are doing something wierd.
vBulletin® v3.8.5, Copyright ©2000-2012, Jelsoft Enterprises Ltd.