Welcome Guest ( Log In | Register )


Important

The forums will be closing permanently the weekend of March 15th. Please see the notice in the announcements forum for details.

Pages: (5) 1 2 [3] 4 5  ( Go to first unread post )
Resolution Vs Compression, Best codec-approach with laced material
« Next Oldest | Next Newest » Track this topic | Email this topic | Print this topic
stephanV
Posted: Aug 28 2005, 06:03 PM


Spam killer ;)


Group: Moderators
Posts: 4348
Member No.: 8917
Joined: 18-February 04



QUOTE
you cannot do that, my good man, as bpp and average quant. are "bollocks" for you , as you said.

Well then something else needs to be thought of. smile.gif

QUOTE
it's kinda catch22 for you, isn't it? you have few theories that this can't work, and yet you can't prove it wrong, so now what will you do?

The problem is that the experience cannot be brought back to a workable model. Sure you can say q3 always looks good, but what use is it to me? Files turn out too large that way in any case. To drift off a bit, I can always assume something falls down on the ground when I throw it up... until I go into space. So the question is: Is there a "space" for video, and if so, where is it?

To restate the problem: I cant go and encode a video, use a bpp and have a targeted average q as result. Maybe if you make a q range of +/- 1 off the middle. But how useful is that? YMMV i guess...

QUOTE
what will you do?

Being a nihilist it seems. smile.gif

But that's ok, I'm just one of those people that attaches more value to understanding something than actually using it. smile.gif

@Frank
QUOTE
Another thing: when you use b-frames the std.deviation fails to calculate.

B-frames are meant to "over"-quantized, meaning they will normally have 1.5 to 2 times the quant value a p-frame would have. B-frames are designed for this purpose and normally have only a small reduction in quality compared to the p-frame that would be encoded, but a high reduction in frame size. Note that this will not only throw off your std, but also your average quant... although I'm not sure how DRF analyzer deals with this.

So now we already need at least to use different values if we want to also accomodate for b-frames. But b-frame behaviour is rather impredictable and depends highly on settings...

QUOTE
There are options in codec to set the quality of your session with quantizer instead of kb: move slider towards q2 encoding is better and so on...
So what's the problem with this utility assumptions if codecs themselves have this approach to set the quality?

You only set the quant, not the quality. If a codec calls constant quant constant quality this is rather silly.


--------------------
useful links:
VirtualDub, Input plugins and filters, AviSynth, AVI-Mux GUI, AC3ACM by fcchandler, VirtualDub FAQ
 
    Top
i4004
Posted: Aug 28 2005, 07:37 PM


Advanced Member


Group: Members
Posts: 2432
Member No.: 4935
Joined: 24-June 03



QUOTE
Well then something else needs to be thought of.

because drfanalyzer said you're mediocre?
tongue.gif
we said that "medium"="nice".
for us.
on our tv-outs. on average quant. of 4 on 512x576.
smile.gif
(hehehe..talking about the variables!)

QUOTE
If a codec calls constant quant constant quality this is rather silly.

because akupenguin said..something..somewhere?

constant quant mode indeed is constant quality.
please feel free to prove me wrong.

i think you failed once in this thread (as you said quant3 can look bad), let's see if you can do it again.
tongue.gif

please be aware; xvid encoding with b-frames and 5/8 quant(for example) is not constant quant. mode.

QUOTE
B-frames are designed for this purpose and normally have only a small reduction in quality compared to the p-frame that would be encoded, but a high reduction in frame size.


could you tell us what does "high reduction in frame size" means?
how much is the bitrate reduced, and how much is the image spoiled?
(one more tough one, no? smile.gif )

--------------------
my signature:
user posted image
 
     Top
stephanV
Posted: Aug 28 2005, 11:12 PM


Spam killer ;)


Group: Moderators
Posts: 4348
Member No.: 8917
Joined: 18-February 04



QUOTE
(hehehe..talking about the variables!)

indeed tongue.gif

QUOTE
please feel free to prove me wrong.

I can show you some stuff q3 stuff that actually looks pretty bad relatively speaking (on my monitor (=TFT), dont know about TV). Its a space shuttle in blue air. Its especially bad when watched in motion, dont even try full screen (res of vid is 624x352 BTW). Now you can say codecs do bad on gradients, but if codecs are bad on some stuff and good on other then they cant possibly give you constant quality on constant quant.

QUOTE
please be aware; xvid encoding with b-frames and 5/8 quant(for example) is not constant quant. mode.

Hey, I'm stubborn, not stupid. tongue.gif

QUOTE
could you tell us what does "high reduction in frame size" means?
how much is the bitrate reduced, and how much is the image spoiled?

This would depend very much on settings... but ill use XviD with defaults ok?

--------------------
useful links:
VirtualDub, Input plugins and filters, AviSynth, AVI-Mux GUI, AC3ACM by fcchandler, VirtualDub FAQ
 
    Top
i4004
Posted: Aug 29 2005, 12:35 AM


Advanced Member


Group: Members
Posts: 2432
Member No.: 4935
Joined: 24-June 03



QUOTE
but if codecs are bad on some stuff and good on other then they cant possibly give you constant quality on constant quant.

wacko.gif

i wanna see this clip. it was divx, or xvid, right?

one can reason in this way; if that codec will always give same artefacts on same quant on same source, it's constant quality. you may not like that quality, but it's constant.
(we can't change the fact mpeg is lossy, and that it hates some things, so no need to discuss that. we also can't change the fact that divx4/5 and xvid are crap.)

we're playing word games now, but i wanna see the clip. divx and xvid can crap-out on sky like no other (recent) codec. they band quickly, and produce false motion.

QUOTE
Hey, I'm stubborn, not stupid.

plenty people call such enc. cq, i'm afraid, so i was just checking.
smile.gif

QUOTE
This would depend very much on settings... but ill use XviD with defaults ok?

use whatever you want, but pick some tough source from here
http://www.ldv.ei.tum.de/liquid.php?page=70
or here
http://index.apple.com/~singer/sequences/testseq.html
(if you can get them in container you want... smile.gif )

i mean...you didn't thought i would be interested in re-encoding the dvds?
tongue.gif

--------------------
my signature:
user posted image
 
     Top
TechMage89
Posted: Aug 29 2005, 03:29 AM


Contemporary Anachronism


Group: Members
Posts: 225
Member No.: 11344
Joined: 6-August 04



Describing CQ as giving constant quality is a bit misleading. Saying it gives constant detail would probably be closer.

After all, what ever sort of (ugly) noise your video had when you encoded it would be included in your definition of "quality." tongue.gif

--------------------
I'm not insane, everyone else is!
 
     Top
stephanV
Posted: Aug 29 2005, 08:48 AM


Spam killer ;)


Group: Moderators
Posts: 4348
Member No.: 8917
Joined: 18-February 04



QUOTE
i wanna see this clip. it was divx, or xvid, right?

It was made with that nandub 1-pass tool. I just capped the quants to 3-3 range (which worked pretty well, although it was a bit heavy on the i-frames). If you don't agree with this method, you can suggest other settings. I will look for some space to upload a small clip and post it later on.

QUOTE
one can reason in this way; if that codec will always give same artefacts on same quant on same source, it's constant quality. you may not like that quality, but it's constant.

The point is that the complete video wasn't just the space shuttle in the sky, there were also people talking and that looked far less annoying to me, so I say quality is not constant. But if you are gonna define constant quality with such restrictions, then yes, you are right.

QUOTE
i mean...you didn't thought i would be interested in re-encoding the dvds?

Source is source; you cant make general comments about things if you only are interested in your specific use. But ill pick one of those. smile.gif

--------------------
useful links:
VirtualDub, Input plugins and filters, AviSynth, AVI-Mux GUI, AC3ACM by fcchandler, VirtualDub FAQ
 
    Top
frank10
Posted: Aug 29 2005, 10:02 AM


Advanced Member


Group: Members
Posts: 148
Member No.: 14177
Joined: 19-February 05



Apart from a q3 looking bad or good, it's the theory behind this that we're interested in.

We also don't have so many variables as you said:

Let's say we take a clip and a codec (doesn't matter which one with its weakness) with ffvfw (that has constant Quantizer option), some resolution (doesn't matter which one) and some other settings fixed.
Then we change ONLY the quantizer setting.
Let's say we choose a q4. Then we change it at q3 and so on...

Which final clip will be better (or will have a better quality, detail, look, psicovisual-acustic appearance rolleyes.gif biggrin.gif ).

For sure it's not the better compression efficiency in filesizes but here we're talking about quality (Can we use this word? smile.gif )

I mean if frameX in this clip has a q4, how can that same frame be better with the same settings-codec? Only with a q3 or q2. Simple. And that is linked with a gain in kbs (as you said earlier this gains quality).

So it seems to me that generally speaking different analysys of the same clip tweaked several times to gain lower average-std dev makes sense and the one with the lower q will look better.
 
     Top
stephanV
Posted: Aug 29 2005, 10:35 AM


Spam killer ;)


Group: Moderators
Posts: 4348
Member No.: 8917
Joined: 18-February 04



clip is here --> http://www.savefile.com/files/6087410 (0.5 MB)

QUOTE
Let's say we choose a q4. Then we change it at q3 and so on...

I never argued that for the SAME source q4 was better than q3. My argument is about two things:

1. While for the SAME source q3 is better than q4 (or definitely not worse), it doesn't necessarily mean q3 looks good. There is big difference in concept between 'better <-> worse' and 'good <-> bad'.
2. When different sources are compared, it might be that q4 vid is better than the q3 vid. (The clip I posted above looks pretty poor in my opinion and I can show you other clips at q4 that are more acceptable to watch then that.)

--------------------
useful links:
VirtualDub, Input plugins and filters, AviSynth, AVI-Mux GUI, AC3ACM by fcchandler, VirtualDub FAQ
 
    Top
i4004
Posted: Aug 29 2005, 02:17 PM


Advanced Member


Group: Members
Posts: 2432
Member No.: 4935
Joined: 24-June 03



techmage, sod off.

stephan; load this clip straight to vdub(i used 1410), and hit 'play input'. now rewind and hit 'play output'. now load via dshowsource (ffdshow decoding) and hit 'play output'.

you know, i was also recently tinkering with gradient (because i run into this ).

it's a colorspace limitation(namely, output colorspace limitation, as you saw different playback methods change things).


get this;
http://i4004.net/i4004/gradient/imagereader_3.m2v
load to vdub-mpeg2. how does it look?
play in (for example) windvd or with elecard. how does it look?

QUOTE
Source is source

certainly not.
if you use dvd as a source, then you're just recompressing the already smoothed video.
it is already smoothed for 2 reasons:
-it is a film source
-it passed one compression already

use something sharp that video camera produced.
or something that was artificially produced and has sharp edges etc. (graphics ..you know, the stuff that rings smile.gif )

QUOTE
2. When different sources are compared, it might be that q4 vid is better than the q3 vid. (The clip I posted above looks pretty poor in my opinion and I can show you other clips at q4 that are more acceptable to watch then that.)

wohoo..wait; you'll be comparing different quants on different sources?
what will that tell us?
blink.gif
talking about taking things too far.

--------------------
my signature:
user posted image
 
     Top
stephanV
Posted: Aug 29 2005, 03:36 PM


Spam killer ;)


Group: Moderators
Posts: 4348
Member No.: 8917
Joined: 18-February 04



QUOTE
it's a colorspace limitation(namely, output colorspace limitation, as you saw different playback methods change things).

Partly, since different codecs behave differently on this (ffvfw seems to have less banding). In any case, its highly annoying. Some guy from ateme said it was because codecs all optimize for PSNR and it is this what causes it... we'll see if it ever gets better though. smile.gif

QUOTE
wohoo..wait; you'll be comparing different quants on different sources?
what will that tell us?

Exactly what I have been trying to tell you: constant quant is not constant quality. Constant quality is not: "quality changes every time there is a scene change"
smile.gif

--------------------
useful links:
VirtualDub, Input plugins and filters, AviSynth, AVI-Mux GUI, AC3ACM by fcchandler, VirtualDub FAQ
 
    Top
i4004
Posted: Aug 29 2005, 05:02 PM


Advanced Member


Group: Members
Posts: 2432
Member No.: 4935
Joined: 24-June 03



QUOTE
we'll see if it ever gets better though.

as soon as luma and chroma planes get to be 16bit.
that should give it enuff levels. smile.gif
(i just laughed at our priv. forum how zx-spectrum was 8-bit.)

but i would say this is a rare problem. i'm not complaining.

cquant is constant quality in the mpeg context.
offcourse, as you've pointed out here, mpeg context is not the best (or absolute) merit for the reasons you mention.
yes.
i can't say that mpeg is compressing everything equally good. indeed.

but let's focus on the mpeg sequences test. i (still) don't have these sequences (should tell somebody to dload and send them to me) so i'm interested to hear about your attempts to decode these. perhaps a mere yuy2 decoder of huff could do. or ms' (from directx).


--------------------
my signature:
user posted image
 
     Top
frank10
Posted: Aug 29 2005, 05:23 PM


Advanced Member


Group: Members
Posts: 148
Member No.: 14177
Joined: 19-February 05



QUOTE
I never argued that for the SAME source q4 was better than q3. My argument is about two things:

1. While for the SAME source q3 is better than q4 (or definitely not worse), it doesn't necessarily mean q3 looks good. There is big difference in concept between 'better <-> worse' and 'good <-> bad'.
2. When different sources are compared, it might be that q4 vid is better than the q3 vid. (The clip I posted above looks pretty poor in my opinion and I can show you other clips at q4 that are more acceptable to watch then that.)


Well, stephanV, both points seem obvious to me: it always depends on the source. For example, if you get a noisy one, how can you compare to a clean one? There's no q (and nothing else) at all!

But i4004 and me were never saying to use this tool this way. I started this thread to ask how to adjust a clip regard the resolution and bpp; then I saw this drfAnalyzer and I thought this could help to find out when you are in the good way to get the best from THAT SAME clip. That doesn't mean of course that clip will look good (it's always a source thing), but that you're getting out the best you can from it. That's all.
At least here we are converging. smile.gif

I agree someone could be using this util wrong comparing different clips, but they aren't us. biggrin.gif

btw: in your shuttle clip DRFanalyzed it could have been some clue on poor quality because of bpp with the relative warning...
 
     Top
stephanV
Posted: Aug 29 2005, 06:49 PM


Spam killer ;)


Group: Moderators
Posts: 4348
Member No.: 8917
Joined: 18-February 04



@ivo:

QUOTE
i can't say that mpeg is compressing everything equally good. indeed.

I'm glad we have some sort of understanding then. smile.gif

QUOTE
but let's focus on the mpeg sequences test. i (still) don't have these sequences (should tell somebody to dload and send them to me) so i'm interested to hear about your attempts to decode these. perhaps a mere yuy2 decoder of huff could do. or ms' (from directx).

Its raw YUV data. use avisynth with rawsource:
CODE

loadplugin("d:\avsplugins\rawsource.dll")
rawsource("e:\downloads\720p50_mobcal_ter.yuv", 1280,720, "i420")

syntax is: rawsource(filename, width, height, colorspace)

@frank:

QUOTE
Well, stephanV, both points seem obvious to me

Good! smile.gif

QUOTE
btw: in your shuttle clip DRFanalyzed it could have been some clue on poor quality because of bpp with the relative warning...

Well I cant go any higher in bit rate as q1, and q3 is already quite high if you ask me. smile.gif

And now I'm off to do some b-frame testing. Not with XviD, but x264, since I dont want to install things anymore I won't use anyway. smile.gif

eeeeeeerrrrrrrrrrr - wait, theres no WAY i can play h264 720p@50fps, so i have to use XviD after all wacko.gif

(or do libav b-frames not crash anymore)

--------------------
useful links:
VirtualDub, Input plugins and filters, AviSynth, AVI-Mux GUI, AC3ACM by fcchandler, VirtualDub FAQ
 
    Top
i4004
Posted: Aug 29 2005, 09:20 PM


Advanced Member


Group: Members
Posts: 2432
Member No.: 4935
Joined: 24-June 03



ftp://ftp.ldv.e-technik.tu-muenchen.de/pu..._sequences/601/

use that and deinterlace.
i mean, do we care about 720p?
i don't.

btw. saw this
http://forum.doom9.org/showthread.php?p=68...7136#post687136

my experience is simillar; they don't really help. they can bring bitrate down, but with it the quality too.

--------------------
my signature:
user posted image
 
     Top
stephanV
Posted: Aug 30 2005, 12:18 PM


Spam killer ;)


Group: Moderators
Posts: 4348
Member No.: 8917
Joined: 18-February 04



any other wishes? resizing? deinterlacing method?

--------------------
useful links:
VirtualDub, Input plugins and filters, AviSynth, AVI-Mux GUI, AC3ACM by fcchandler, VirtualDub FAQ
 
    Top
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
67 replies since Aug 6 2005, 09:41 AM Track this topic | Email this topic | Print this topic
Pages: (5) 1 2 [3] 4 5 
<< Back to Codec Discussion