digitalFAQ.com Forums [Archives] - Avisynth: Blocks in black background!!

Page 2 of 3

Show 40 post(s) from this thread on one page

digitalFAQ.com Forums [Archives] (http://www.digitalfaq.com/archives/)

- Avisynth Scripting (http://www.digitalfaq.com/archives/avisynth/)

- - Avisynth: Blocks in black background!! (http://www.digitalfaq.com/archives/avisynth/4449-avisynth-blocks-black.html)

jorel

07-11-2003 03:08 PM

nothing change bman,
just the same.
:!:

plautzer

07-15-2003 02:59 PM

Well,
did anybody solve this problem,
I had no luck with anything I did!! :oops:
OR what could u actually change to get rid of it??
What filter is responsible for that problem?

THx

Plautzer

ovg64

07-15-2003 03:54 PM

Quote:

Originally Posted by plautzer

Well,
did anybody solve this problem,
I had no luck with anything I did!! :oops:
OR what could u actually change to get rid of it??
What filter is responsible for that problem?

THx

Plautzer

What resolution u r using Plautzer :?:

plautzer

07-16-2003 06:02 AM

I use 528x480 for NTSC and 528x576 for Pal!!

Plautzer

plautzer

07-17-2003 12:39 PM

@ Jorel:
Do u see the blockz in preview when u load the .vobs in DVD2AVI??

I would like to show a pic but it doesnt work with 'print screen' and paste in paint!!

But u can see in the preview that there blocks, they're not that intense but still, u can see them!!
What could that be??
I mean what could u do wrong when u rip a dvd on ur hard drive?!?!

Plautzer

jorel

07-17-2003 03:45 PM

Quote:

Originally Posted by plautzer

no plautzer,in power dvd or in dvd2avi i can't see any problem.
the image is clear,,i can call the quality like "fantastic".
i think in all possibilities and i was copy the full dvd to hd
and rip with VStrip and trash the "video_ts" folder of my hd after rip.
if i load the vobs or ifo in power dvd,wmplayerClassic,
vdubmod or dvd2avi(176,1773 or 1774) the image is wonderfull......

it all means:
i'm lost,don't know what is wrong.
if i load a simple .avs scrip without any filter in vdubmod,ToK,Tmpgenc,
the image show:
strange dark green in dark scenes,some blocks sometimes and
little "moving ants",dont matter the "resize"(resolution)
choosed in the script :!:

and more, this source is ntsc interlaced 29,97and
if i use GOP30 (auto GOP in ToK) in tmpgenc and encode,
the image seems "breathing" like i posted before.
seems better if i change the GOP to 24 but this is not correct,i think!

strange but true my friend.
:wink:

andybno1

07-20-2003 04:06 PM

so since thursday anyone managed to figure something out???? I am gettin this problem too in dark scenes and I am noticing some colour bleeding mainly blue.

here is the script I was using:

Code:

##DLL Section ##

#

LoadPlugin("C:\Program Files\MovieStacker\Filters\MPEG2Dec3.dll")

LoadPlugin("C:\Program Files\MovieStacker\Filters\GripFit_YV12.dll")

LoadPlugin("C:\Program Files\MovieStacker\Filters\STMedianFilter.dll")

LoadPlugin("C:\Program Files\MovieStacker\Filters\asharp.dll")

LoadPlugin("C:\Program Files\MovieStacker\Filters\unfilter.dll")

LoadPlugin("C:\Program Files\MovieStacker\Filters\undot.dll")

#

####



##Defined Variables and Constants ##

#

MaxTreshold = 1.50

nf =  0 #Current frame.

#

####



##Main section and static filters ###

#

Mpeg2Source("C:\DVD Movie\MI2.d2v")

#

undot()

Limiter()

asharp(1, 4)

GripCrop(352, 576)

GripSize(resizer="BicubicResize")

STMedianFilter(8, 32, 0, 0 )

MergeChroma(blur(MaxTreshold))

MergeLuma(blur(0.1))

#

#



##Linear Motion Adaptive Filtering ##

#

#( Portions from AviSynth's manual )- This will apply temporalsoften to

#very static scenes, and apply variable blur on moving scenes.

#We also assign a variable - and this is why a line break is inserted:



SwitchThreshold = (Width<=352)? 4 : (Width<=480)? 3 : 2

ScriptClip("nf = YDifferenceToNext()"+chr(13)+ "nf >= SwitchThreshold ? \

unfilter( -(fmin(round(nf)*2, 100)), -(fmin(round(nf)*2, 100))): \

TemporalSoften( fmin( round(2/nf), 6), round(1/nf), round(3/nf), 1, 1)")



#

#

#



GripBorders()

#LetterBox( Your_Values_Here )#Depends on situation. Use MovieStacker!

Limiter()



#

#

##Functions ###



function fmin( int f1, int f2){

  return ( f1<f2 )? f1 : f2

}



#

####

Holomatrix

07-29-2003 11:30 AM

So should we definatly be using Limiter() then? to help with the blocks.

andybno1

07-29-2003 12:09 PM

well I have limiter on and I'm gettin blocks, I haven't a clue when it comes to the scripts, I just see if there is a updated version and use it :lol: I have tried to get into the scriptin language but I just find it recks my head. I do appreciate all the help off here just can't rack my head round the script.

Yoda	07-29-2003 12:18 PM

I think the only way to solve this problem is to go back to the previous version of avisynth. I'll bet the problem clears up.

-Yoda

andybno1

07-29-2003 03:12 PM

so is it gonna be a case of someone lookin over the script and seein whats what?

Bchteam

08-02-2003 05:45 AM

Those Blocks appear, because of the Television. My Panasonic TV plays KVCD well, while on my brothers Grundig TV KVCD looks crappy with a lot of blocks on black backgrounds. For Instance the beginning credits on black background are looking fine on my TV, but on my Brothers TV a lot of Grey/Darkgreen Blocks appear. Those blocks are not still, they are kind of moving. It looks like kind of "pixelporridge". Very Ugly. But I also noticed that even some original DVD's look blocky on my Bro's TV, when it comes to scenes with still background.

On the Computer everything looks OK.

I really assume that it has nothing to do with script, the Vob's or whatsoever. It's a TV related thing.

plautzer

08-02-2003 06:48 AM

Hi,

Quote:

Originally Posted by Bchteam

On the Computer everything looks OK.

Negativ, it looks bad on my computer and on my TV!!

Quote:

Originally Posted by Bchteam

I really assume that it has nothing to do with script, the Vob's or whatsoever. It's a TV related thing.

Im not sure if it has to with the TV or with script... cuz for some people the script works perfect... or does everybody has this problem??
Has it maybe somethin gto do with the hardware??
I tested it on my laptop and on PC and I got the blockz with both.
I also tried a PAL and NTSC dvd and there werent differences neither!!

When I rip a dvd with Davideo.... picture looks pretty good, no blockz or everything.... I dont really know what to do!!

Cu

Plautzer

andybno1

08-02-2003 04:06 PM

can't be my TV cause it looked the same when played on my PC, plus I noticed what could only be described as the blue bleeding into the picture in dark scenes when I done MI:2 when it was semi dark parts.

Holomatrix

08-08-2003 07:29 AM

Quote:

Originally Posted by Dialhot

Quote:

Originally Posted by bman

@ Jorel
2) Maybe u just check option -Output YUV data as basic YCbCr not CCIR601 - in TMPGenc under Quantize matrix TAB to convert all near black to real black ??? Worth to try 8) 8)
bman

Doing this is a nonsense as it does exactly the opposite that you want to do by using Limiter() in your script.

THAT is the thing to change if you find your black to "green".

(reminder : limiter changes all luma value below 0 to 16, that means that a true black (L=0) is changed to a dark grey (L=16))

So are you saying that we don't really want true black because that causes the encoder problems and causes blocks? Just trying to clerify for myself this Limiter() stuff. Thanks

Dialhot

08-08-2003 07:52 AM

In fact I wasn't talking at all of the blocks in dark you were talking about. The fact is I never had such blocks, and I never use Limiter. Can't say if that is really the source of the problem.

Holomatrix

08-08-2003 07:56 AM

Quote:

Originally Posted by Dialhot

In fact I wasn't talking at all of the blocks in dark you were talking about. The fact is I never had such blocks, and I never use Limiter. Can't say if that is really the source of the problem.

Oh, I thought that is what were doing. What is the reason for Limiter() then? turn Black to green or dark grey? why would we want to do that?
Thanks

jorel

08-08-2003 08:06 AM

from the docs under avisynth:

limiter

This filter is present in v2.5. The standard known as CCIR-601
defines the range of pixel values considered legal for presenting on a TV.
These ranges are 16-236 for the luma component and 16-240
for the chroma component.

Pixels outside this range are known to cause problems with some TV sets,
and thus it is best to remove them before encoding
if that is your intended display device.
By default this filter clips (or "clamps") pixels under 16 to 16
and over 236 (or 240) to 236 (or 240).
:!:

Dialhot

08-08-2003 08:06 AM

Old TV sets had problems with extrem values as picture too dark or too bright. That is why the standard CCIR601 was decided. As on these old screens, the material wasn't black indeed but very dark green, I think this problem wasn't a real one.

Now, as there are TV set with perfectly dark screen, that is an other question.

Same for limitation in high value : the problem appears only on weak electronics (the image seems to "pump" when you have a very bright area to display). In 2003, all TV set can handle very high luma.

I think Jorel can say something more on this point : that is his everyday labor :-)

Wilbert

08-08-2003 08:07 AM

See http://www.avisynth.org/index.php?page=Limiter

It rounds [0,16] to 16 and [236,255] to 236.

edit: too late :)

Page 2 of 3

Show 40 post(s) from this thread on one page