Progress on vo_comp output driver: * Back-fill routine now implemented for vo_comp * Routine to find max screen resolution implemented. * Alignment changed from 32bit to 64bit..
Other stuff: * Striped down p96_pip (don't think it works, but anyway its there) * Linux paths fix for mplayer. * Added MikeJT SDL full screen fix.
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
The comp driver is the fastest of them all with the shortest playback time and lowest VO time. The cgx_wpa driver in the MUI-mplayer is slightly faster than this new mplayer, but not by much. But it's h264 codec is a bit slower so it still ends up at the bottom of these.
Btw: How to I get OSB fonts to load properly? It looks in ~/.mplayer/subfont.ttf. I created the .mplayer/, and later ~/.mplayer/ but it still can't find it.
Software developer for Amiga OS3 and OS4. Develops for OnyxSoft and the Amiga using E and C and occasionally C++
Btw: How to I get OSB fonts to load properly? It looks in ~/.mplayer/subfont.ttf. I created the .mplayer/, and later ~/.mplayer/ but it still can't find it.
you don't as I just fixed that.
And the error messages in mplayer is misleading, use snoopy to see where really looks for it.
EDIT: corrected the error message for next version.
Edited by LiveForIt on 2014/4/6 19:33:40
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
Let's hope p96_pip works with your version on MPLayer in order fot us to have only ONE version for every system. And we'll also need a Non AltiVec version
I don not have the money right now (next month I hope) but I shoulg dive to everyone involved : Kas1e, LiveForIt (you) and Joerg (and maybe some I do forget ).
The cgx_* modes are MorphOS/CyberGraphX code and of course not usable on AmigaOS (AmigaOS doesn't have a cybergraphics.library, except for a very minimal emulation for ancient AmigaOS 3.x/m68k software only).
its probably just a wrapper, what ever goes into CyberGraphX end up in Picasso96, I can change and see what happens if I change to ARGB.
The wrapper is JIT compiled and most of the work is done by function it calls natively, I don't think it going to do a major difference.
What I wrote earlier on is wrong, it does not use a bitmap at all, and just use a memory buffer, it uses the Cybergraphic equivalent to IP96->p96WritePixelArray(), to draw the graphics.
It should be calling Picasso96 function direct, but it's not important.
Maybe the the best thing to do is use some macro magic or if defines, its not like the source code is flooded whit CyberGraphX stuff.
Stupid to have two different versions of the source code to maintain, that will be just be more work in the end.
Edited by LiveForIt on 2014/4/7 4:10:55 Edited by LiveForIt on 2014/4/7 4:11:39
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
It didn't have gui code , so we need just reuse it as well.
Maybe I'm being overcritical but it has some GUI event code there.
I'm not saying we don't need some event code for the window.
But if you have a different GUI's maybe there should be different event codes as well.
That's what I'm thinking.
That's way I think it should be in GUI/ maybe even create a file called GUI/AmigaOS_no_gui.c, where all window handling goes, Opening, closing window, events.
Edited by LiveForIt on 2014/4/7 4:37:51 Edited by LiveForIt on 2014/4/7 4:40:32 Edited by LiveForIt on 2014/4/7 4:42:38 Edited by LiveForIt on 2014/4/7 5:30:58
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
Progress on vo_comp output driver: * Back-fill routine now implemented for vo_comp * Routine to find max screen resolution implemented. * Alignment changed from 32bit to 64bit..
Other stuff: * Striped down p96_pip (don't think it works, but anyway its there) * Linux paths fix for mplayer. * Added MikeJT SDL full screen fix. * New cgx_wpa driver whit ARGB (should be faster)
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
On my peg2/radeon9250, vo_comp works almost the same by speed as cgx_wpa, just a little faster (cgx_wpa give 45% cpu loading on some video, vo_comp give 41-42% cpu loading). overlay driver give 26% of cpu loading on same video.
In compare with vo_comp from beta2, its the same for my config.
Quote:
Striped down p96_pip (don't think it works, but anyway its there)
P96 driver works in window mode, just events didn't handles (i.e. can't make fullscreen by dbl-click, can't press "esc"). Running it with -fs in command line (so to fullscreen), make it crash:
Is your beta3 still altivec binary or generic ? Why i ask, is because now in beta3 your cgx_wpa the same by speed as my cgx_wpa on generic binary. While, in your beta2 it was on 10% faster (becaus of altivec). If now its generic binary, then its probably indeed a bit faster (on 2-3%), but if that altivec binary still, then something wrong and it slower than before on 10%.
Are you sure P96_PIP works with LiveForIt's Beta 3? When entering -vo p96_pip I only get : "Error opening/initializing the selected video_out (-vo) device".
And vo_comp still doesn't work with my Radeon 9000 Pro (grey screen and 100% CPU). Weird since it works for you.
Regarding Altivec, wehen looking a the debug output of MPlayer I can see this : "[swscaler @ 0x591c3bb0]ALTIVEC: Color Space ARGB"
SDL is still really slow on non Radeon HD systems and results of every version is about the same with this video output on my A1.
Comp
Still doesn't work on my Radeon 9000 Pro on AGP (grey screen and 100%CPU usage). I don't know why. I doubt this card doesn't support compositing since Radeon HD Boing Ball from Hans works.
@K-L Are you sure that with p96_pip its all not placebo or some sideeffects ? Why i ask, because p96 driver we use in both versions are the same. And by changelogs LiveForIt show, he didn't add anything to it, instead of making it works.
Also i do test right now his beta3 and my beta6 : p96_pip driver works 1:1 the same by speed (even if his version are from altivec binary, and my from generic). At least on pegasos2 it is like this, and should be like this , as driver code are the same.
More of it, my should be been a very little faster, because by fixing white strips it mean disabling of compositing, which reduce transfers a bit as well.
Can you just grab beta3 from liveforit, my beta6, then hard reboot for everytest you do, and compare it then. My bet it will be 1:1 the same. + - a little which will depends on moon phase.
Quote:
Still doesn't work on my Radeon 9000 Pro on AGP (grey screen and 100%CPU usage). I don't know why. I doubt this card doesn't support compositing since Radeon HD Boing Ball from Hans works.
Maybe some more init code missing in vo_comp for now..
@K-L Probably just differences bettwen altivec and genertic versions yep. Once will sort all bugs with muimplayer will compile altivec one as well
@LiveForIT
Btw, as for putting events handling out of drivers, that imho not very good idea, as we better need to follow original mplayer logic: they have it in all their drivers as i see. So to avoid any mess and making things different imho better just do it as it done in mplayer : gui/mui , gui/reaction, and events are in drivers as it now (that minimal set of course, not whole).