Haali Renderer [Archive] - Page 15

leeperry

27th May 2007, 12:15

Having signals go lower that 16 is expected as well as higher than 235. It has to do with the fact that sharp filtering of signals (like you would want) and its manipulation is very hard for equipment that process such analog signals. (yeah, it comes back to limitations of analog equipment) But still, all useful information is to be considered the one inside the 16-235 range.

indeed.
but the screenshots show otherwise, the data <16 is actually "useful".......your filtering/signal issue might very well be the other way around ;)

Peuj

27th May 2007, 13:53

Am I the only one thinking here that he should be making code diffs available alongside his ax file?

np: Vladislav Delay - Wanted To (Kill) (Whistleblower)

Yep maybe he didn't think about it and we could simply ask him (I know he's reading this forum). Or maybe he's waiting for a more stable version?

The_Keymaker

27th May 2007, 19:22

Forgive me if the issue I'm about to raise has already been addressed.

Anyway, I like the Haali renderer, but when I use it I experience A/V sync issues compared to VMR9.

I've adjusted the frames and buffer numbers but it doesn't seem to solve the problem. Is there something else I'm missing?

My system is:
C2D E6300
2Gig Ram
nVidia 8600GT
Vista 32 OS

Any help solving this would be greatly appreciate.

ffmpeg

29th May 2007, 01:37

Are haali splitter and haali renderer open source?

chros

29th May 2007, 09:25

@The_Keymaker: a sample file? I only encounter A/V desync when my CPU isn't enough quick (so no problem with Haali's renderer)

@ffmpeg: No, they aren't.

The_Keymaker

29th May 2007, 15:47

Chros,

I think you're right.

After installing faster memory which allowed me to Over Clock, much of the sync problems went away.

Compared to VMR9, Haali renderer is more CPU intensive. In addition, since I am not using PowerDVd 7.x to view HD-DVd, I am unable to make use of the hardware acceleration capabilities of the 8600GT card.

Seb.26

30th May 2007, 09:15

But still, all useful information is to be considered the one inside the 16-235 range.
Wrong IMO ... there are lots of DVD encoded with some (a lot?) pixels in BTB and WTW ...
( try looking "The village" ie. without BTB, blacks are really bad ... )

NB: That's why I've modify the level's filter in FFDShow for including this values during the YUV->RGB conversion ... :)

KoD

30th May 2007, 10:03

leeperry

30th May 2007, 10:47

yeah that's what I kept saying on that french forum.......it's not because some DVD's are poorly mastered that the decoding process should change....but still a auto-detection feature in HR wouldn't hurt :D

Seb.26

30th May 2007, 17:37

You know, you are defending a DVD-Video that was not mastered as it should have been, and now claiming that the DVD is fine, but the standards that should have been respected are wrong. It doesn't work that way. If you want to be dissatisfied with someone, be dissatisfied of the mastering house. (although it's still possible the encoder they used and the material they had to encode simply gave this kind of results beacuse it couldn't do better it that situation)
I suppose you also look in 4/3 all movies that have been wrongly flagged ... :rolleyes: ... lol

In any case, the fact is that there are some movies with BTB ... but i don't think it's the render's job to decide what must be displayed and what must be hidden ... a render must render ... that's all IMO ... so no probem 4 me with what HR do ... ;)

leeperry

30th May 2007, 17:46

Seb.26

30th May 2007, 18:09

well it's very nice that you modify ffdshow code but I like to use the latest official builds of ffd and most likely your modifications are not part of these.
and besides I'd love HR to do it for any kind of concent, like MPEG2 videos/AVC/etc....not just ffdshow...
you can try to use pc.601 instead of rec.601 in HR ( I saw last release offer this choice ) ... and them calibrate your screen on [16~235] instead [0~255] ... and when needed, just adjust the brightness of your screen ... so you have it for any kind of concent ... ;)

foxyshadis

31st May 2007, 05:32

but I like to use the latest official builds of ffd

The abandoned three year old one? Or clsid's and drevil's?

leeperry

31st May 2007, 07:51

cls' : http://sourceforge.net/project/showfiles.php?group_id=173941&package_id=199416&release_id=439938

Flash_Git

1st June 2007, 04:54

All of a sudden I can no longer load shaders with MPC + Haali. What could cause this?

leeperry

1st June 2007, 13:33

All of a sudden I can no longer load shaders with MPC + Haali. What could cause this?
terrorists ? :p

you can try to use pc.601 instead of rec.601 in HR ( I saw last release offer this choice ) ... and them calibrate your screen on [16~235] instead [0~255] ... and when needed, just adjust the brightness of your screen ... so you have it for any kind of concent ... ;)
AFAIK there's only rec.601 and rec.709 in HR....and besides my Sanyo Z3 is perfectly calibrated with the color.HCFR, so I can't be hassled to mess up with the brightness control all the bloody time :D

KoD

2nd June 2007, 09:45

What is pc.601 ? Never heard of it.

foxyshadis

2nd June 2007, 11:44

Avisynth's term for fullscale bt.601.

leeperry

2nd June 2007, 20:45

well the more it goes, the more I'm able to "see" if a movie is 601 or 709 not being decoded in the right colorspace.....but still some automatic detection scheme within HR would be totally tits :D

Mangix

2nd June 2007, 21:38

is Haali Renderer faster than Overlay?

kurt

2nd June 2007, 22:20

nope
http://forum.doom9.org/showthread.php?p=962405#post962405

B.Slisk

3rd June 2007, 10:37

New version of Haali Media Splitter posted: http://haali.cs.msu.ru/mkv/

A change to the renderer mentioned: Fixed GetCurrentImage in the renderer so it behaves correctly when called indirectly via FGM.

Warpman

4th June 2007, 10:37

OSD seems not working in the new version

kurt

4th June 2007, 11:43

OSD is working here :)

KoD

4th June 2007, 11:47

If there's no resizing being performed (the video resolution is the same as the playback on screen resolution), there will be no OSD shown. But that was the behavior before as well. What has changed is that the OSD doesn't show the bitrate graph anymore.

chros

4th June 2007, 17:14

A change to the renderer mentioned: Fixed GetCurrentImage in the renderer so it behaves correctly when called indirectly via FGM.
What does it mean in practice?

Dethis

4th June 2007, 17:54

How can someone take a capture at the current colorspace ??.

I just checked and found that by selecting the BT.601 or BT.709 colorspace with Haali Renderer's controls i can clearly see the differences on the rendered image ... but the captured images are always the same and identical with the BT.601 one.

B.Slisk

4th June 2007, 20:02

How can someone take a capture at the current colorspace ??.Don't use the Save Image feature, take a screen shot instead.

If you press PrtScr a screen shot will be saved in the memory. Open your paint program of choice, even mspaint will do in a pinch, and paste the screen shot into a new document.

Pressing Alt+PrtScr will result in a screen shot of just the active program window. This can be used when you want to take a screen shot of the un-scaled image.

Taking screen shots using PrtScr will not work with some renderers but I know it works with Halli and VMR9 renderless .

Dethis

4th June 2007, 21:23

Don't use the Save Image feature, take a screen shot instead.

If you press PrtScr a screen shot will be saved in the memory. Open your paint program of choice, even mspaint will do in a pinch, and paste the screen shot into a new document.

Pressing Alt+PrtScr will result in a screen shot of just the active program window. This can be used when you want to take a screen shot of the un-scaled image.

Taking screen shots using PrtScr will not work with some renderers but I know it works with Halli and VMR9 renderless .

Thanks B.Slisk,
but unfortunately i only have a 1280X1024 screen while the desired image is 1920X1080 and i want it un-scaled.
In quick check even this downscaled image needed levels correction (pc->tv), while i didn't check at all for BT.709 compliancy.

mrkazador

4th June 2007, 21:30

Maybe someone could help me...
Why is it when using the Haali Video renderer in Zoom Player I only get half the resolution? ex..1280x720p is shown as 640x360. Tried different video codecs and splitters, still the same.
Tried using MPC and I get an error message:
"Could not load shader: Shader complex (jim.ro)"
If I continue and play it works perfectly fine.
Im using an x800gt with latest drivers.

foxyshadis

4th June 2007, 23:16

If you search this thread, others have had your concern before. If you really want the player to overflow the screen, just set it to 200% zoom. Or just use fullscreen and ignore the size it loads at, like everyone else. The renderer never sizes down and then back up, it always resizes only once at full quality, but it'll force it to load at a lower size than normal if it would overflow the screen otherwise.

The MPC error is odd, since x800 should have PS2 at least.

chros

5th June 2007, 08:22

Tried using MPC and I get an error message:
"Could not load shader: Shader complex (jim.ro)"
If I continue and play it works perfectly fine.
For me the same: so if you use Haali's renderer then you can't use shaders.

chros

5th June 2007, 08:45

A technical question:
I'm watching 23.976 fps progressive content on my LCD TV running on 60 Hz with your renderer.
What happens with the missing frames? Eg.: does Halli's renderer with the videocard driver automatically create a 3:2 pulldown?
And what do the other renderers (overlay mixer, VMR9 renderless)?

Thanks

Seb.26

5th June 2007, 17:25

chros

5th June 2007, 20:10

IMO : same frame is displayed twice ...
or displayed twice as long?
And what happens with the missing 12 frame? (24*2=48, 60-48=12)

Thanks

Leak

5th June 2007, 20:22

or displayed twice as long?
And what happens with the missing 12 frame? (24*2=48, 60-48=12)
Well, the next frame is drawn during the next vertical blank, to prevent tearing, so some frames will be displayed for 2 frames and some for 3 frames (probably alternating) - exactly what you wanted to do using AviSynth... :)

It all depends on how the renderer synchronizes with the screen's vertical refresh...

np: Legiac - Opaque (Mings Feaner)

aydc

5th June 2007, 21:03

nope
http://forum.doom9.org/showthread.php?p=962405#post962405

I have this same problem too. Jagged edges are killing the image quality, due to broken resizing. I'm using the latest version of the renderer, latest nvidia drivers on a GeForce 8800 GTX. I had the same problem when I had a GeForce 7900 GS and so far nothing has changed. I'm amazed that such a problem could not be solved so far.

KoD

6th June 2007, 05:31

What is the resolution of the video file you are trying to play and to which resolution is it resized ? (you can see those figures enabling the OSD of Haali's renderer, for instance)

Also, grab a screenshot of that file in original resolution using ffdshow's "grab" feature. Post is as a png on sites like xs.to Let's see if the "jagged edges" are not there in the original. VMR9 likes to "smooth" the image sometimes and that's why jaggies are not that visible. A sharper resizing will show them in all their glory though.

chros

6th June 2007, 10:05

Well, the next frame is drawn during the next vertical blank, to prevent tearing, so some frames will be displayed for 2 frames and some for 3 frames (probably alternating) - exactly what you wanted to do using AviSynth... :)

It all depends on how the renderer synchronizes with the screen's vertical refresh...
Thanks. So it depends on the renderer and the videocard driver ...
At least I haven't got to play around the changefps() function in the script ... :)

aydc

6th June 2007, 19:10

nope
http://forum.doom9.org/showthread.php?p=962405#post962405

What is the resolution of the video file you are trying to play and to which resolution is it resized ? (you can see those figures enabling the OSD of Haali's renderer, for instance)

Also, grab a screenshot of that file in original resolution using ffdshow's "grab" feature. Post is as a png on sites like xs.to Let's see if the "jagged edges" are not there in the original. VMR9 likes to "smooth" the image sometimes and that's why jaggies are not that visible. A sharper resizing will show them in all their glory though.

The problem is completely the same as with the screenshots that you see on the link kurt posted above, so it won't make a difference if I make another set of screenshots.

The problem is even more apparent if I set Haali's sharpness slider to minimum, so it's not about the resizing algorythm. It happens on all sorts of low res (like 320x200) videos. If the resolution is higher, the problem can't be seen easily, but it's still there if I look carefully.

obieobieobie

7th June 2007, 03:28

I'm really impressed by the progress of this renderer. I now use it all the time and have yet to see any problems. Well done, Haali! :)

ShadowVlican

7th June 2007, 05:35

I'm really impressed by the progress of this renderer. I now use it all the time and have yet to see any problems. Well done, Haali! :)
same here!

guess i'm one of the luckier ones? :devil:

Athlon64 X2 3800+
MSI 7300GT
Dell 2405FPW LCD

aydc

7th June 2007, 15:00

I've changed a few things that might fix the gf5xxx problem, please check http://haali.cs.msu.ru/mkv/mkx.I.4.exe

Haali, while my 8800 GTX isn't GF5xxx, the symptoms are completely the same with people who you made this patch for. (Broken resizing, blocky image)

The link is dead now. Could you upload it again to let me try it?

leeperry

7th June 2007, 20:49

any chance getting a reply from Haali himself to know whether he could add 601/709 and PC/TV automatic detection ?
some DVD's actually contain valuable data <16 and >236, and some DVD's are 601, some others are 709...........so some simple auto-detection feature would be awesome.

if that's a no-no, some hotkeys and systray options to toggle these 2 options would make HR even better IMHO :)

Thanks for reading!

B.Slisk

9th June 2007, 21:52

any chance getting a reply from Haali himself
Perhaps you should try the mailing list mentioned on the Haali Media Splitter home page (http://haali.cs.msu.ru/mkv/).
Bug reports and feature requests
Please send feedback to our development mailing list at lists.matroska.org (http://lists.matroska.org/), or if you prefer web interface, at gmane (http://dir.gmane.org/gmane.comp.multimedia.matroska.devel).

leeperry

10th June 2007, 00:30

well these are MKV lists, and besides Haali often comes around on this topic.

but I guess he doesn't care..

aydc

10th June 2007, 16:02

well these are MKV lists, and besides Haali often comes around on this topic.

but I guess he doesn't care..

Haali has programmed the best renderer on the market and he's giving it away for free. I think we should show more appreciation. He'll answer questions when he has the time. It's not like you're paying him anything.

leeperry

10th June 2007, 19:42

hummmm ? I've praised his renderer in each and every of my posts in this topic if you look well.

I am well aware that this is the best renderer around ;)

I would just appreciate a reply, but well he prolly got better things to do than answer silly questions on doom9 forum :D