MSU deblocking 2.1 released!

[DmitriyV2]

MSU deblocking 2.1 for VirtualDub released!

Main advantages:
* Now work with high resolutions.
* Non SSE old processors now supported.

http://www.compression.ru/video/deblocking/index_en.html

Enjoy! ;)

[redfordxx]

Originally posted by DmitriyV2
MSU deblocking 2.1 for VirtualDub released!

Main advantages:
* Now work with high resolutions.
* Non SSE old processors now supported.

http://www.compression.ru/video/deblocking/index_en.html

Enjoy! ;)
I guess you are something like author...then pls take a look here
http://forum.doom9.org/showthread.php?threadid=91532
I already solved that using quite complex script but still...

[DmitriyV2]

Originally posted by redfordxx
I guess you are something like author...then pls take a look here
http://forum.doom9.org/showthread.php?threadid=91532
I already solved that using quite complex script but still...
Thanks for link!

[redfordxx]

Originally posted by DmitriyV2
Thanks for link!
OK, so probably you are author...
... then I will continue:
First, I must say, except the artefacts I described, I like the deblocking. (BTW, I use it in AviSynth so I have to convert the clip to RGB32, which is considered stupidity in doom9, but i think is't worth it) Then follow some observations:
1. deblocking is different when converting via pc.601 or pc.709
2. the quality depends on cropping the video (of course, always mod8, aligned with blocks (8x8))
3. on top of that when I crop to desired size and then add borders 8 to all directions the deblocking seems the best (it probably learns the size of blocks) but...
4. ...the black borders are bleeding into the picture
5. it crashes on specific sizes, so i have to crop-->deblock-->crop more

Does it really work in RGB32?

[DmitriyV2]

Originally posted by redfordxx
OK, so probably you are author...
Maybe... ;)
2. the quality depends on cropping the video (of course, always mod8, aligned with blocks (8x8))
Sure. It's mod16 necessary.

5. it crashes on specific sizes, so i have to crop-->deblock-->crop more
Very interesting! On what sizes???!!!

Does it really work in RGB32?
No. :)

[redfordxx]

Originally posted by DmitriyV2
Very interesting! On what sizes???!!! I will find out for you...
BTW, using 2.0 but according to changelog, shouldnot be difference

Does it really work in RGB32?
No. :) So, how is it in VDMod --- i've been told, VDMod works in RGB, vobs are in YV12. XviD ...YV12. For using this in AviSynth (which is muuuuch more powerful than VDMod, IMHO) I need to convert video to RGB32 and back.... and the filter internaly converts it to something else?
How is it?
Or, how is it with color conversions when using in VDM only, e.g:
vob-->crop-->deblock-->xvid

[DmitriyV2]

Originally posted by redfordxx
I will find out for you...
Ok! We will fix them if we will reproduce error.

BTW, using 2.0 but according to changelog, shouldnot be difference
Only bugfixes was there.

So, how is it in VDMod --- i've been told, VDMod works in RGB, vobs are in YV12. XviD ...YV12. For using this in AviSynth (which is muuuuch more powerful than VDMod, IMHO) I need to convert video to RGB32 and back.... and the filter internaly converts it to something else?
How is it? Or, how is it with color conversions when using in VDM only, e.g: vob-->crop-->deblock-->xvid
We will thinking about version for AviSynth (we developed most filters in VD or in standalone program).

[redfordxx]

Originally posted by DmitriyV2
Ok! We will fix them if we will reproduce error.
720x576 ok
720x448 ok
720x432 crash
720x416 ok
720x400 ok
718x432 ok!!!
704x432 ok
704x416 ok
704x400 ok
688x432 ok
688x416 crash
688x400 ok

... there were few more I think, but cannot remember. Let me know, if you can(not) reproduce it...
it was via AviSynth and VDM too (build 2439).

Still curious, how is it about the color conversion in VDM (if you have spare time)... I have thread "Frameserving with VDMod" here. The main reason for it was just to find another way to get MSUDeblocker to AviSynth. But when the color conversion is still there... no sense anymore

[DmitriyV2]

Originally posted by redfordxx
720x576 ok
720x448 ok
720x432 crash
720x416 ok
720x400 ok
718x432 ok!!!
704x432 ok
704x416 ok
704x400 ok
688x432 ok
688x416 crash
688x400 ok
... there were few more I think, but cannot remember. Let me know, if you can(not) reproduce it...
it was via AviSynth and VDM too (build 2439).
Very good bugreport. Thanks a lot! Hope we reproduce it easy.

Still curious, how is it about the color conversion in VDM (if you have spare time)... I have thread "Frameserving with VDMod" here. The main reason for it was just to find another way to get MSUDeblocker to AviSynth. But when the color conversion is still there... no sense anymore
It's look's like it's necessary to write MSUDeblocker for AviSynth...

[DmitriyV2]

Originally posted by redfordxx
720x432 crash
688x416 crash

Did you EXACTLY use MSU Deblocking 2.1 (last)?

We cannot crash it on this resolutions...

[redfordxx]

Originally posted by DmitriyV2
Did you EXACTLY use MSU Deblocking 2.1 (last)?

We cannot crash it on this resolutions...
I used 2.0 that time. (See my post 22nd March 2005 22:29)
I try it later again with the new one. Sorry for misunderstanding.

[DmitriyV2]

Originally posted by redfordxx
I used 2.0 that time. (See my post 22nd March 2005 22:29)
I try it later again with the new one. Sorry for misunderstanding.
We publish 14 March version 2.1 with bugfixes and it's looks like your bugs was fixed there. :)

[redfordxx]

Originally posted by DmitriyV2
Did you EXACTLY use MSU Deblocking 2.1 (last)?
We cannot crash it on this resolutions... 2.1 works, sorry for trouble.
But I advanced in solving the color problem I mentioned in the link in the beginning of the thread if you're interested. Speaking about avisynth usage of version 2.1.
There are, except the deblocked spots, broken colors in chroma, large areas of original+-1 value. When I deblock without chroma deblocking, the areas are still there. So when I Subtract the two deblocking differences, I receive the 99% of correctly deblocked spots.

[DmitriyV2]

Originally posted by redfordxx
2.1 works, sorry for trouble.
Wonderful! Thanks for confirmation!

But I advanced in solving the color problem I mentioned in the link in the beginning of the thread if you're interested. Speaking about avisynth usage of version 2.1.
There are, except the deblocked spots, broken colors in chroma, large areas of original+-1 value. When I deblock without chroma deblocking, the areas are still there. So when I Subtract the two deblocking differences, I receive the 99% of correctly deblocked spots.
Can you upload example to any site?

[redfordxx]

Originally posted by redfordxx
I guess you are something like author...then pls take a look here
http://forum.doom9.org/showthread.php?threadid=91532
I already solved that using quite complex script but still...
Now I think, maybe the problem could be in the ranges of color values [16,235] or what instead of [0,255]