Michel Bardiaux wrote:
Cool_Zer0 wrote:
Michel Bardiaux wrote:
Cool_Zer0 wrote:
Michel Bardiaux wrote:
Cool_Zer0 wrote:
Michel Bardiaux wrote: > Cool_Zer0 wrote: >> Hi there, >> >> I'm facing a low quality [snip] > > Quality depends on what you put in enc_context. If you keep the > defaults, that will be 200kbits, which by my > seat-of-the-pants-o-meter should be roughly equivalent to a > 400kbits MPEG1, ie a little worse than long-play VCR.
Please tell if you have indeed this.
What I asked for was whether my guess at what you call low-quality, is right.
Oh.. Sorry.. Well... It's not a low-quality... I can see the image but it's a lot pixelized...
I'll give you too samples... This is the original frame on 176x144: http://www.ncenteio.net/original.bmp This is what the other side is receiving. http://www.ncenteio.net/compressed.bmp The image is with other dimensions but that's because the other side client is resizing it... But it's clear that the image (quality) isn't enough...
So.. What do you think? In your profissional opinion :)
Well, its not the same frame, but it seems about right for 200kbits H263.
[SNIPPET]
avcodec_alloc_context sets it to AV_CODEC_DEFAULT_BITRATE 200*1000.
My usual strategy is to rehearse using ffmpeg, then dump the whole codeccontext, then set the parameters in my own code.
Oh my god :( The worst happens... When I compress the .bmp's with ffmpeg it looks pretty good... Almost the same... Input #0, image2, from 'bitmap/bmp%d.bmp': Duration: 00:00:14.6, start: 0.000000, bitrate: N/A Stream #0.0: Video: bmp, bgr24, 176x144, 25.00 fps(r) File 'teste.h263' already exists. Overwrite ? [y/N] y Output #0, h263, to 'teste.h263': Stream #0.0: Video: h263, yuv420p, 176x144, q=2-31, 200 kb/s, 25.00 fps(c) So.. I guess that it's something between the compression with ffmpeg and the decompression used by Microsoft RTC H.263 codec... Right? Now I really don't know what to do :(