Log in

View Full Version : picture too dark with avisynth script


Pages : 1 [2]

baz00ie
2nd July 2004, 16:30
Guys, All i'm trying to do is help some people out, not confuse them even more - which is what's happenning...

Trevlac, thank you for reminding me about the saturation adjustment, i had mentioned it in an earlier post but forgot to do so in my last post.

Didée, yes i know VirtualDub has the correct colour output, but most people don't watch their movies through VirtualDub, they use their favorite player, which makes use of the DirectShow overlay - hence the added "brightness" adjustment.

Guys, if you'll notice, i always put the word correct in quotes, indicating that it was not really correct, but merly an approximation. When dealing with NTSC (North America) that's the best we can do. Television technicians work with hundreds of thousands, if not millions of dollars worth of equipment. They spend long hours trying to time the equipment using everything at their disposal - yet at the end of the the day, the final decission comes down to looking at the monitor and making adjustments based on WHAT LOOKS GOOD. And even then, they can get it wrong, you just have to watch certain shows on PBS that look like the equipment was timed by a colour blind monkey.

Of course, most of us here don't have millions of dollars worth of broadcast equipment, all we have is a 300KB "dll" file - and yet, it still comes down to WHAT LOOKS GOOD. Also, with the varying quality of DVDs on the world market, it's kinda like working with NTSC - you have to spend a lot of time trying to make them look good.

Therefor, i still stand by my suggestion, that if you're making a video to watch through your television set, DON'T change any of the levels or brightness/contrast settings. If, however, you wish to view your video through your computer, then you should make some adjustments to deal with the darkened image. The level and saturation adjustments i mentioned above are one idea, but i'm sure there are others.

Jorel, i don't think there will ever be a "perfect" solution until they start plugging the damn things directly into our brains.

take care
baz

Wilbert
2nd July 2004, 16:40
Did you even bother to read the whole thread? What you are describing is not the problem we were discussing here.

I will repeat it:

"I tried it myself with the movie From Hell (**).

1) vob -> vdubmod -> png
2) vob -> d2v -> avs -> vdubmod -> png

You guys are right. There is a difference in brightness (the latter being a bit darker)."

In the avs script it didn't matter whether there's a color conversion or not. The problem is that both clips ((1) and (2)) should result in the same brightness, but (1) is brighter.

Jorel posted some screenshots in this thread, I also posted some screenshots here:

http://forum.doom9.org/showthread.php?s=&threadid=78514

I though the problem had to do with out of bound luma range clips, but I can't duplicate it by making artificial out of bound luma range clips from AviSynth.


The artificial clip can be found here (upper half is luma=0, lower half is luma=50):

http://www.geocities.com/wilbertdijkhof/mix.m2v

jorel
2nd July 2004, 17:24
Originally posted by baz00ie
Television technicians work with hundreds of thousands, if not millions of dollars worth of equipment. They spend long hours trying to time the equipment using everything at their disposal - yet at the end of the the day, the final decission comes down to looking at the monitor and making adjustments based on WHAT LOOKS GOOD. And even then, they can get it wrong, you just have to watch certain shows on PBS that look like the equipment was timed by a colour blind monkey.i understand cos i was technician (retired) for 30 years,.. still a hobby!
Originally posted by baz00ie
Didée, yes i know VirtualDub has the correct colour output, but most people don't watch their movies through VirtualDub, they use their favorite player, which makes use of the DirectShow overlay - hence the added "brightness" adjustment.well, if we get this differences in vdub after load the avisynth script,the remainder steps of the encode will always be dark no matter what encoder you use to watch the result
-->in tvs without changes in the adjusts!
Originally posted by baz00ie
Therefor, i still stand by my suggestion, that if you're making a video to watch through your television set, DON'T change any of the levels or brightness/contrast settings..[/B]but this is the point: i don't see the differences from the dvd source and from the movie encoded in the pc only...--> i see in all my 5 tvs without change any adjust(bright,contast,saturation,etc).i posted that pictures showing that the image is dark--->after using the avisynth script and i think that need corrections in this point.
Originally posted by baz00ie
Jorel, i don't think there will ever be a "perfect" solution until they start plugging the damn things directly into our brains.[/B]ok, maybe it's impossible and nobody can give that "perfect" solution but this (perfections) is what i'm always searching in my encodes.
thanks! :)

baz00ie
3rd July 2004, 04:50
.

jorel
3rd July 2004, 14:30
no...it's not a vdubmod(any version) problem...quoting myself:
Originally posted by jorel
screenshots for comparisons.

from vob in vdubmpeg2: http://img37.imageshack.us/img37/6026/vob.jpg

from avisynth script(using dvd2avi project) in vdubmpeg2: http://img37.imageshack.us/img37/5411/avisynthscript.jpg
here my sample was using vdubmpeg2,as you can see...
i did tests with all vdubs but maybe i'm still unclear...i know that my english is horrible but i'm writing the same 3 times:
the result is different in the -->TV<-- after you encode the movie and use the original dvd source to compare with the same movie encoded.
the step where i found that difference was after the avisynth script!
the pictures posted was trying to show that differences and -->maybe<--- avisynth give this differences as you can see in the pc -->too<--!

and the 91638's post is showing the -->same<-- problem like he wrote:
Originally posted by 91638
Hi,

i noticed that the picture ist too dark when i use avysinth as frameserver. No matter what Version of Avisynth i use, always the same problem. If i open the *.d2v file in TMPG the picture is O.K.
Does anybody know a solution for this problem. I used the search in this forum but found no thread helping me.

I know my english is worth to improve but maybe you can understand my problem and help me. Thanks.

are we still unclear?

:confused:
hey...you erease your post and now my answer is without sense! :p
but i still have your pictures posted before you edit your post!

jorel
21st July 2004, 00:42
hy all! :)
no news about that problems or temporary solutions? i stop to encode waiting better results and, using the last avisynth version the same is happen! thanks.

Didée
21st July 2004, 08:20
Well, obviously no-one has better ideas or findings to come up with, and so haven't I. Somewhat clueless here as well.

But I have a temporary solution for too dark pictures ;)

Check this thread (http://forum.doom9.org/showthread.php?s=&threadid=79898). These little functions come quite handy for brightening up too dark video, while mostly avoiding the washed-out look one usually gets by "normal" level/gamma adjustments.

Speed-wise, they should run easily @ realtime in ffdshow. But honestly, I didn't even check up to now if it *works at all* in ffdshow - so little time, again ...


- Didée

Wilbert
12th September 2004, 00:30
@Didee, Jorel and others,

We finally found out this cause of this, and how to correct it using an avs filter. See:

http://forum.doom9.org/showthread.php?s=&threadid=82217

shon3i
23rd January 2007, 19:02
I am apology for return this form dead, but i want to say that colormatrix can't help in this, nevermind is source avi or avs, encoded mpeg via tmpgenc 2/3/4, contarst is different. So is there some other solution, because i tryed all combinations in colormatrix 2.

Thanks