New info.
After much frustration I finally got the gui version of mplayer to use the same settings as the sehll version and to play videos with lagging.
I had to go into the information screen and remove all tooltypes except for FRAMEDROP and GUI.
It no longer lags.
I am not sure which tooltype was causing the lag but at least it is gone now.
Got a little tired of running mplayer from the shell to get things to work right.

Quote:

Well, just for your information, only the "GUI" tooltype is considered. All the others have strictly no effect since a long time. So it's unrelated to what you did with tooltypes. And GUI version just uses the same parameters as the command line mode except for the parameters you can set in settings window (which are then saved in conf/gui.conf).
But by default, the settings are the same for both modes anyway, so you surely set something in the first place. Shell and GUI modes have the same performance in all benchmarks.

Also, framedrop option (which can be set in settings window) is not really recommanded for h264 files, it just gives nothing except extra lagging (decoding still has to be done, displaying isn't the bottleneck).



[ Edited by Fab 19.07.2013 - 10:52 ]

Quote:

1080p can be played properly on such a setup (depending on bitrate though), but it's close to 90/100% usage. Just uncomment lavdopts=skiploopfilter=all in conf/config file if it's not fully in sync.
As for 720p using 50/60% cpu, there's nothing wrong with that. Just so you know, OSX is much worse at that (when using just one core obviously).

That said, can you tell me if you're in overlay mode (an easy way to tell if you are is that you can freely resize the video window) ? If you're not, then it impacts performance quite a lot, especially for HD videos.



[ Edited by Fab 19.07.2013 - 10:57 ]

@bash64 @fab

I was able to turn off overlay in GMplayer, but that actually made it worse As of lowering color depth, I don't know how to do that except in prefs.

But I guess I was hoping too much, reading about the "35% CPU usage" Well, I'm pretty satisfied with 720p anyway.

It would be fun to see a youtube film showing the difference between G4, G5, MorphOS and MacOS to see the difference. I think such a movie would be more telling than benchmarks. If anyone is up to making such a film

Quote:

Fab already mentioned that disabling overlay will negatively affect performance. Switching color depths should only affect performance if overlay is disabled, which is not advised.


Quote:

Please note that video files with the same codec and resolution may still perform quite differently depending on how they were encoded.

hmmmmmmmmmm...........
I have confirmed. If you play with all of the tooltypes in place for gmplayer that videos will lag.
Removing all but framedrop and gui gets rid of something. I don't know what, but it gets rid of something that causes lag.
Worked for me.

ok,

Here is a link to my article on playing 1080p movies that use h.264 compression on MOS on a G5.
There is also a section on setting up the Ambient Desktop to allow double clicking on 1080p movies.
This is a compilation of all of my fooling around with this sort of thing.


http://bettyboopdatabase.0usa.com/mos/docs/1080p.html

The link to my personal knowledgebase:

http://bettyboopdatabase.0usa.com/mos/mos.html

> http://bettyboopdatabase.0usa.com/mos/docs/1080p.html

From there:

"MOS 3.2 comes with grunch, it is in sys:applications/grunch/grunch."

Are you sure this is the case?

Pretty sure.

Quote:

You are wrong. Grunch was never part of the os.

Geit

Quote:

Sorry, but i insist, this is really wrong. There's no significant cost in using the GUI (probably less than 0.01%). Just make sure you're using the same settings and that's it.

You can test it from shell using
sys:applications/mplayer/mplayer -gui 1 -cache 65536 -lavdopts skiploopfilter=all -framedrop yourfile

We can also benchmark it if you really need a proof. :)

[ Edited by Fab 25.07.2013 - 11:17 ]

ok.
Lets see the benckmarks.
I will test on my system using the -gui switch.

Currently the video I am using plays correctly from the shell but fails to play correctly from GMPlayer.

I will correct the 'grunch comes with mos 3.2' mistake.
I have an article on installing grunch so that will do.

NOTE:

Grunch mistake removed. First article now describes how to download grunch.

-framedrop was added to the mplayer options at the last minute out of habit. I would agree that there is no visible performance boost from this but there defintely is from -lavdopts skiploopfilter=all.


Other issues fixed with site.
Ambient desktop unfinished article removed.

Whatever benchmark tools you use I will need a copy to do my testng also.
I guess mplayer has built in benchmarking.

To benchmark, use

mplayer -gui 1 -benchmark -nosound -ao null -lavdopts skiploopfilter=all yourfile

and then

mplayer -benchmark -nosound -ao null -lavdopts skiploopfilter=all yourfile

Assuming you didn't change other settings specifically for the GUI (especially display output driver), then you shouldn't see any kind of visible difference.

I just tried with a 65s 1080p video file on my powermac g5 @2.3GHz:

MPlayer -benchmark -nosound -ao null -lavdopts skiploopfilter=all "Work:Star Trek Into Darkness - Teaser.mp4"
BENCHMARKs: VC: 35.080s VO: 17.294s A: 0.000s Sys: 2.141s = 54.515s
BENCHMARK%: VC: 64.3488% VO: 31.7240% A: 0.0000% Sys: 3.9272% = 100.0000%

MPlayer -gui 1 -benchmark -nosound -ao null -lavdopts skiploopfilter=all "Work:Star Trek Into Darkness - Teaser.mp4"
BENCHMARKs: VC: 36.501s VO: 17.627s A: 0.000s Sys: 0.285s = 54.413s
BENCHMARK%: VC: 67.0811% VO: 32.3955% A: 0.0000% Sys: 0.5233% = 100.0000%

As you can see, it's very close, both taking 54s to decode and display. And that's just expected. I repeat, the video driver is basically the very same except it displays in a mui window, the gui controls take almost nothing to refresh and all the rest (decoder, options and so on) are the same for both gui and non gui modes.

The video is taken from: http://www.digital-digest.com/movies/Star_Trek_Into_Darkness_1080p_Teaser_Trailer.html




[ Edited by Fab 26.07.2013 - 10:47 ]

I just finished Frankenweenie.
I will get back with you in a sec...

ok, I think I know where we misunderstand each other.

I am not refering to the -gui option when I talk about slowdown.
I am refering to gmplayer which cannot play frankenweenie or any other 1080p video to save its life.
To me, GMPlayer is GUI.
MPlayer is shell.

Quote:

But using -gui 1 (as first parameter) or using gmplayer is strictly equivalent. They both enable the GUI.

GMPlayer is just a standalone icon, with GUI tooltype enabled. That way, when run from workbench, it triggers the gui, just like running mplayer -gui 1 would. EXACTLY the same. :)

[ Edited by Fab 26.07.2013 - 18:10 ]

I tried using -gui without a 1 .
oops.
Let me try that....


ok, with -gui 1 I get the exact same play window that I get using mplayer from the shell.


I launched gmplayer by itself and I no longer get the pretty, pretty buttons like I used to.
Not sure why, but it won't play the movie right.
Sever lag.
I get the gui window items, just not the buttons like forward, backward, etc...

I have all the GUI options checkmarked but the toolbar buttons are gone.
Maybe I need to re-install.

BTW: Since gmplayer doesnt use the config file then there is no way to tell it to do -lavdopts skiploopfilter=all is there?
Without that option no movie will play right.

Certainly GMPlayer is reading the conf file.
MPlayer in GUI mode is not slower than in shell mode.
When the mplayer window is resizeable, then overlay mode is enabled.
When the mplayer window has a fixed size, then initializing the overlay mode has failed somehow.

[ Edited by Tom01 26.07.2013 - 21:52 ]

Actually the author claims it does not read the config file but uses its own called gui.conf


Quote Fab:

Well, just for your information, only the "GUI" tooltype is considered. All the others have strictly no effect since a long time. So it's unrelated to what you did with tooltypes. And GUI version just uses the same parameters as the command line mode except for the parameters you can set in settings window (which are then saved in conf/gui.conf).


[ Edited by bash64 26.07.2013 - 20:12 ]

Anyways, the fun continues.

I deleted and reinstalled mplayer using grunch.

GMPlayer cannot play the movie without severe lag but the shell can.

I am running on MOS 3.2 on a powermac G5 2.3ghz with ati 9600 Pro video card.

My desktop is 1920x1080x24bit.

I don't think overlay has anything to do with it as it works from the shell on this desktop.

I am using the defualt cgx_overlay_gui video driver for gmplayer.



If you have the exact same setup please try both modes.

Quote:

No i don't say that. Conf/config is definitely used in gui mode. It's just a *couple* settings are overridden by gui.conf (like vide driver and the others you can see in this file). So for instance, skiploopfilter option will be read from conf/config even in gui mode.

I strongly suspect you have a duplicate mplayer somewhere else that gmplayer standalone icon uses instead of the one in the current directory. Tha would explain all your very weird observations that really don't make much sense.

And if you run mplayer with -gui 1 as FIRST parameter you definitely get the gui.

> I strongly suspect you have a duplicate mplayer somewhere else that gmplayer
> standalone icon uses instead of the one in the current directory. Tha would
> explain all your very weird observations that really don't make much sense.

This sentence from his "unofficial MorphOS knowledgebase" might give something away I think:

"Copy mplayer to the C: folder in your system so that it will launch from anywhere:
> copy sys:applications/mplayer/mplayer c:"

Yes, I do copy mplayer into C: so it can be run from anywhere.
So you say gmplayer runs C:mplayer rather than sys:applications/mplayer/mplayer?
What difference does this make?

I am guessing it cannot find the conf folder with the conf file.
Is there supposed to be an assign for mplayer?