MPlayer and KMP fullscreen picture quality
Alex Taylor
WarpVision, there is one fairly significant drawback. I've noticed that
the picture quality when running videos fullscreen is significantly
inferior to WarpVision for the exact same video file.
By that I mean that the image is noticeably rougher/blockier; the same
video shown fullscreen in WV is much crisper-looking.
Do other people see this? Is there anything that can be done about it?
Given that WV seems pretty much dead at this point, I'd like to reduce my
dependency on it...
--
Alex Taylor
Fukushima, Japan
http://www.socis.ca/~ataylo00
Please take off hat when replying.
KO Myung-Hun
Alex Taylor wrote:
> While in general, MPlayer and KMP are more consistently reliable than
> WarpVision, there is one fairly significant drawback. I've noticed that
> the picture quality when running videos fullscreen is significantly
> inferior to WarpVision for the exact same video file.
>
> By that I mean that the image is noticeably rougher/blockier; the same
> video shown fullscreen in WV is much crisper-looking.
>
> Do other people see this? Is there anything that can be done about it?
> Given that WV seems pretty much dead at this point, I'd like to reduce my
> dependency on it...
>
>
Which video mode are you using ?
And are you using post processing with WV ?
--
KO Myung-Hun
Using Mozilla SeaMonkey 1.1.14
Under OS/2 Warp 4 for Korean with FixPak #15
On AMD ThunderBird 1 GHz with 512 MB RAM
Korean OS/2 User Community : http://www.ecomstation.co.kr
Alex Taylor
> > While in general, MPlayer and KMP are more consistently reliable than
> > WarpVision, there is one fairly significant drawback. I've noticed that
> > the picture quality when running videos fullscreen is significantly
> > inferior to WarpVision for the exact same video file.
> >
> > By that I mean that the image is noticeably rougher/blockier; the same
> > video shown fullscreen in WV is much crisper-looking.
>
> Which video mode are you using ?
You mean resolution? Various screen sizes, including 1024x768, 1280x1024
and 1400x1050, on at least three different systems. All are on 32-bit
colour, however, and all use GRADD video drivers (either SNAP or Panorama).
> And are you using post processing with WV ?
No, just the default settings.
Heikki Kekki
On Fri, 27 Feb 2009 09:37:02 UTC, "Alex Taylor"
<mai...@reply.to.address> wrote:
> On Fri, 27 Feb 2009 06:18:34 UTC, KO Myung-Hun <ko...@chollian.net> wrote:
>
> > > While in general, MPlayer and KMP are more consistently reliable than
> > > WarpVision, there is one fairly significant drawback. I've noticed that
> > > the picture quality when running videos fullscreen is significantly
> > > inferior to WarpVision for the exact same video file.
> > >
> > > By that I mean that the image is noticeably rougher/blockier; the same
> > > video shown fullscreen in WV is much crisper-looking.
> >
> > Which video mode are you using ?
>
> You mean resolution? Various screen sizes, including 1024x768, 1280x1024
> and 1400x1050, on at least three different systems. All are on 32-bit
> colour, however, and all use GRADD video drivers (either SNAP or Panorama).
Here the picture quality when running videos fullscreen is about same,
maybe MPlayer is a little bit better. A big difference is CPU load,
Warpvision takes about 90% and Mplayer about 45%.
Fullscreen videosize is 1680x945, CPU 700 MHz Celeron, SNAP and
WarpOverlay.
VIDEO: [WMV3] 512x288 24bpp 1000.000 fps 702.0 kbps (85.7 kbyte/s)
http://areena.yle.fi/toista?quality=hi&id=1927267
Http-streaming, MPlayer user-agent must set NSPlayer/4.1.0.3856 or
similar. I use user-agent=NSPlayer/9.00.00.6980 line in config.
--
Hessu
KO Myung-Hun
Alex Taylor wrote:
> On Fri, 27 Feb 2009 06:18:34 UTC, KO Myung-Hun <ko...@chollian.net> wrote:
>
>
>>> While in general, MPlayer and KMP are more consistently reliable than
>>> WarpVision, there is one fairly significant drawback. I've noticed that
>>> the picture quality when running videos fullscreen is significantly
>>> inferior to WarpVision for the exact same video file.
>>>
>>> By that I mean that the image is noticeably rougher/blockier; the same
>>> video shown fullscreen in WV is much crisper-looking.
>>>
>>
>> Which video mode are you using ?
>>
>
> You mean resolution? Various screen sizes, including 1024x768, 1280x1024
> and 1400x1050, on at least three different systems. All are on 32-bit
> colour, however, and all use GRADD video drivers (either SNAP or Panorama).
>
>
I meant snap/wo/dive. ^^
I think you use DIVE mode. If so, you're right. MPlayer and KMP do not
enable DIVE dithering feature.
Now enabled it.
You can get the enabled version here,
for KMP
http://www.ecomstation.co.kr/komh/kmp_test.zip
for MPlayer
http://www.ecomstation.co.kr/komh/mplayer_test.zip
How about ?
Ruediger Ihle
> I think you use DIVE mode. If so, you're right. MPlayer and KMP do not
> enable DIVE dithering feature.
DIVE dithering is only for <= 256 color modes. So I don't think that's
the point here.
What's much more interesting: who is doing the color space conversion ?
DIVE's build-in YUV-to-RGB conversion sucks big time (even though it is
pretty fast). So for decent results, a player should convert YUV data
to the screen format (in case the screen uses 32bpb, convert to 24bpb)
and present RGB datat to the DIVE API. I don't know, if MPlayer and KMP
are doing that.
--
Ruediger "Rudi" Ihle [S&T Systemtechnik GmbH, Germany]
http://www.s-t.de
Please remove all characters left of the "R" in my email address
KO Myung-Hun
Ruediger Ihle wrote:
> On Fri, 27 Feb 2009 12:56:35 UTC, KO Myung-Hun <ko...@chollian.net> wrote:
>
>
>> I think you use DIVE mode. If so, you're right. MPlayer and KMP do not
>> enable DIVE dithering feature.
>>
>
> DIVE dithering is only for <= 256 color modes. So I don't think that's
> the point here.
>
That's too bad. If so, I have no clue. Because scaling is the factor and
I don't think WV would scale a image up for itself. Maybe it let DIVE to
scale up like MPlayer and KMP.
Anyway Alex's reply is needed.
> What's much more interesting: who is doing the color space conversion ?
> DIVE's build-in YUV-to-RGB conversion sucks big time (even though it is
> pretty fast).
More, YUV support itself is so buggy.
> So for decent results, a player should convert YUV data
> to the screen format (in case the screen uses 32bpb, convert to 24bpb)
> and present RGB datat to the DIVE API. I don't know, if MPlayer and KMP
> are doing that.
>
>
MPlayer and KMP do that using libswscale of FFmpeg. And many other
proejcts are using it.
Dave Yeo
> MPlayer and KMP do that using libswscale of FFmpeg. And many other
> proejcts are using it.
Actually libswscale comes from MPlayer
Dave
KO Myung-Hun
Their license says it's part of FFmpeg. But their codes are maintained
in MPlayer repository.
Christian Hennecke
<mai...@reply.to.address> wrote:
> While in general, MPlayer and KMP are more consistently reliable than
> WarpVision, there is one fairly significant drawback. I've noticed that
> the picture quality when running videos fullscreen is significantly
> inferior to WarpVision for the exact same video file.
>
> By that I mean that the image is noticeably rougher/blockier; the same
> video shown fullscreen in WV is much crisper-looking.
>
> Do other people see this? Is there anything that can be done about it?
> Given that WV seems pretty much dead at this point, I'd like to reduce my
> dependency on it...
From my experience, this depends somewhat on the format of the video
file. You could try choosing a different scaling method for MPlayer.
See:
http://www.mplayerhq.hu/DOCS/man/en/mplayer.1.html
--
"I smell blood and an era of prominent madmen." - W.H. Auden
Alex Taylor
<christian...@ruhr-uni-bochum.de> wrote:
> From my experience, this depends somewhat on the format of the video
> file. You could try choosing a different scaling method for MPlayer.
> See:
>
> http://www.mplayerhq.hu/DOCS/man/en/mplayer.1.html
Hmmm... any hints what I should be looking at? Most of that page is
frankly gibberish to me.
Alex Taylor
> >> Which video mode are you using ?
>
> I meant snap/wo/dive. ^^
Oh... I never really understood what that part of the readme was talking
about, so I never used the -vo option. Therefore I guess I'm using DIVE.
> You can get the enabled version here,
> for KMP
> http://www.ecomstation.co.kr/komh/kmp_test.zip
>
> for MPlayer
> http://www.ecomstation.co.kr/komh/mplayer_test.zip
>
> How about ?
Hmm... not sure if it makes a difference or not.
I went back and did some more comparisons with WVGui. I realize I may have
overstated the quality difference a bit.
I don't mean that MPlayer looks bad. It's very hard to actually quantify
the difference, because it's mostly noticeable if I spend a long time
watching something in WarpVision, then switch to MPlayer. However, doing
quick spot-comparisons between the two apps, it's hard to notice.
I get the definite impression that the fullscreen picture in WarpVision is
just slightly smoother, whereas there's a (very) faint suggestion of
pixellation from the upscaling in MPlayer. I think WarpVision may simply
soften the image out slightly somehow.
Christian Hennecke
<mai...@reply.to.address> wrote:
> > From my experience, this depends somewhat on the format of the video
> > file. You could try choosing a different scaling method for MPlayer.
> > See:
> >
> > http://www.mplayerhq.hu/DOCS/man/en/mplayer.1.html
>
> Hmmm... any hints what I should be looking at? Most of that page is
> frankly gibberish to me.
Under "Decoding/Filtering Options" looks at the option -sws, and for
even more stuff under "Video filters" look at -vf scale.
Christian Hennecke
<mai...@reply.to.address> wrote:
> > From my experience, this depends somewhat on the format of the video
> > file. You could try choosing a different scaling method for MPlayer.
> > See:
> >
> > http://www.mplayerhq.hu/DOCS/man/en/mplayer.1.html
>
> Hmmm... any hints what I should be looking at? Most of that page is
> frankly gibberish to me.
To choose a different scaling method, look at the -sws options under
"Decoding/Filtering Options". Also, you can change some parameters for
the scaling algorithm with -ssf and -vf scale (the latter is described
under "Video filters"). For postprocessing, have a look at the -vf pp
option. Some of this stuff *is* rather complicated and I haven't digged
deeper myself.
Heikki Kekki
On Tue, 3 Mar 2009 13:46:01 UTC, "Alex Taylor"
<mai...@reply.to.address> wrote:
> On Fri, 27 Feb 2009 12:56:35 UTC, KO Myung-Hun <ko...@chollian.net> wrote:
>
> > >> Which video mode are you using ?
> >
> > I meant snap/wo/dive. ^^
>
> Oh... I never really understood what that part of the readme was talking
> about, so I never used the -vo option. Therefore I guess I'm using DIVE.
If you use DIVE, you don't see good video quality at fullscreen and CPU
load is huge compared with WO.
http://www.os2site.com/sw/drivers/video/warpoverlay/warpoverlay-20060306
.zip
From warpoverlay.new file:
Manual install for cases, when WO not installed previously:
1. Put woverlay.dll and hwvideo.dll into your OS2\DLL directory.
2. Look into your config.sys for line: SET C1=SDDGRADD
3. Change it to: SET C1=SDDGRADD,WOVERLAY
4. Delete all copies of listed DLLs, other than was placed into
OS2\DLL
5. Reboot.
Playing Yle News from http://areena.yle.fi/toista?quality=hi&id=1932466
MPlayer SVN-r28593-OS2-4.3.3 (C) 2000-2009 MPlayer Team
VIDEO: [WMV3] 512x288 24bpp 1000.000 fps 702.0 kbps (85.7 kbyte/s)
CPU load is mostly under 50%, when using WO at fullscreen (videosize
1680x945). With DIVE at same size load is 99.9% and video is delayed.
PMView screen capture when using DIVE:
http://ossiuser.pp.fi/tmp/shot0004.jpg
SMPlayer screenshot when using WO:
http://ossiuser.pp.fi/tmp/shot0003.jpg
--
Hessu
KO Myung-Hun
Alex Taylor wrote:
> On Fri, 27 Feb 2009 12:56:35 UTC, KO Myung-Hun <ko...@chollian.net> wrote:
>
>
>>>> Which video mode are you using ?
>>>>
>> I meant snap/wo/dive. ^^
>>
>
> Oh... I never really understood what that part of the readme was talking
> about, so I never used the -vo option. Therefore I guess I'm using DIVE.
>
>
For sure, you can use -msglevel option as the following.
mplayer -msglevel vo=9 movie_file
And you can find the line in the log
KVA: Selected video mode = DIVE
>> You can get the enabled version here,
>> for KMP
>> http://www.ecomstation.co.kr/komh/kmp_test.zip
>>
>> for MPlayer
>> http://www.ecomstation.co.kr/komh/mplayer_test.zip
>>
>> How about ?
>>
>
> Hmm... not sure if it makes a difference or not.
>
>
>
That's too bad. T.T
> I went back and did some more comparisons with WVGui. I realize I may have
> overstated the quality difference a bit.
>
> I don't mean that MPlayer looks bad. It's very hard to actually quantify
> the difference, because it's mostly noticeable if I spend a long time
> watching something in WarpVision, then switch to MPlayer. However, doing
> quick spot-comparisons between the two apps, it's hard to notice.
>
> I get the definite impression that the fullscreen picture in WarpVision is
> just slightly smoother, whereas there's a (very) faint suggestion of
> pixellation from the upscaling in MPlayer. I think WarpVision may simply
> soften the image out slightly somehow.
>
>
Hmm... Then, which video plugin do you use in WarpVision ? You can
confirm it in 'Video' tab.
Elmer Fudd
(eCS 1.2MR) and then back again, I often find mplayer having paused and
showing a green screen. I then have to hit the spacebar once or twice to
restart mplayer. I am using mplayer 27724.
Configuration issue or something else?
On Wed, 04 Mar 2009 22:04:34 +0900, KO Myung-Hun wrote:
:>Hi/2.
:>
Elmer Fudd
play in mplayer? I would like to watch them using Firefox 3.0.5 - although I
expect I would have to use mediaplayerconnectivity to fool the site into
believing I am running the Windows Media Player or RealVideo, I have yet to
be successful.
On Wed, 04 Mar 2009 10:09:50 -0500 (EST), Elmer Fudd wrote:
:>When I switch from a full-screen mplayer session to another desktop in ePager
:>:>
:>
:>
Ilya Zakharevich
> When I switch from a full-screen mplayer session to another desktop in ePager
> (eCS 1.2MR) and then back again, I often find mplayer having paused and
> showing a green screen. I then have to hit the spacebar once or twice to
> restart mplayer. I am using mplayer 27724.
>
> Configuration issue or something else?
No need for anything as drastic as two desktops:
a) stop Mplayer, run
start /fs
they type `exit' in the newly opened full-screen session.
==> Green screen
b) If Mplayer is not stopped, I get
MPlayer interrupted by signal 11 in module: flip_page
- MPlayer crashed by bad usage of CPU/FPU/RAM.
instead.
But, I'm afraid that this is a bug in implementation of overlays, not
in MPlayer...
Hope this helps,
Ilya
Alex Taylor
> Hmm... Then, which video plugin do you use in WarpVision ? You can
> confirm it in 'Video' tab.
SNAP.
Chris McKenna
On Wed, 04 Mar 2009 07:26:06 GMT, Heikki Kekki wrote:
-snip-
>
>MPlayer SVN-r28593-OS2-4.3.3 (C) 2000-2009 MPlayer Team
Where is this version located? I can not find it anywhere....
Chris McKenna
Heikki Kekki
KO Myung-Hun
Alex Taylor wrote:
> On Wed, 4 Mar 2009 13:04:34 UTC, KO Myung-Hun <ko...@chollian.net> wrote:
>
>
>> Hmm... Then, which video plugin do you use in WarpVision ? You can
>> confirm it in 'Video' tab.
>>
>
> SNAP.
>
>
If so, it's strange that MPlayer does not use snap mode. And it's
natural that SNAP has a better quality than DIVE.
You can use SNAP with MPlayer using '-vo kva:snap' option. And be sure
that you place snapwrap.dll somewhere in libpath.