"OSD-non-working-at-all" is usually a path/font problem. OSD works for me in LiveForIt's mplayer.
Use Snoopy to see where it tries to load its config from. A preview version of MPlayer-GUI used wrong home-dir parameters when starting mplayer so it couldn't find its files.
Software developer for Amiga OS3 and OS4. Develops for OnyxSoft and the Amiga using E and C and occasionally C++
OSD-non-working-at-all" is usually a path/font problem. OSD works for me in LiveForIt's mplayer
Yes but what video driver are you using ?
Quote:
Use Snoopy to see where it tries to load its config from. A preview version of MPlayer-GUI used wrong home-dir parameters when starting mplayer so it couldn't find its files.
Mmm I doubt that problem could be related to that, i mean: Using the LiveForIt binary OSD works just fine with any video drivers here (except the p96_pip as i said) ...
To be sure in the same folder i copied the old MPlayer from Andrea ... and OSD works with its p96_pip, .. so for sure problem is not related to an erroneous config
Right, this was about the p96_pip driver. Kind of missed that part... Haven't use that in a couple of years since the RadeonHD cards haven't had overlay.
Software developer for Amiga OS3 and OS4. Develops for OnyxSoft and the Amiga using E and C and occasionally C++
p96_pip fixes Implementing menus in mplayer Drag and Drop Adding Screenshotdir and EXTPATTERN AmiUpdate support New feanor ffmpeg integration 64Bit fix Transferring of bounty will happens after beta-tests and before public release OpenSource
@Liveforit for 1300 Euro ? Deletion of install script saves 2 days
I agree if Ka1e finds the p96 OSD fix or else, I have to spend a day or two on that.
I think AmiUpdate support is going to useless without a install script, how will AmiUpdate know if its altivec versions that’s going to be installed or the none altivec version, and how I'm going to get fonts and config file installed, without install script?
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
Please remove AmiUpdate from the bounty! It's a waste of LiveForIt's time and our money because someone else can do it instead. That someone else will also do the install script at the same time. That's the only thing that makes sense.
I would also like to get the priorities straight: 1. New feanor ffmpeg integration (money has been payed to get this into our mplayer so it should be done first) 2. p96_pip fixes 3. Implementing menus in mplayer 4. 64Bit fix 5. Drag and Drop 6. Adding Screenshotdir and EXTPATTERN
What is the point of candy (menu, DnD, screenshot, file patterns) if mplayer isn't even working properly?
Merging code and get the codecs to work has to be done first. It would be nice to see a beta-release after each step. Then stuff that isn't really necessary to play videos, like menu, dnd etc can be implemented.
Install+AmiUpdate someone else should do in parallel.
Software developer for Amiga OS3 and OS4. Develops for OnyxSoft and the Amiga using E and C and occasionally C++
Exactly. What "AmiUpdate stuff" would that be anyway? Starting from OS4.1 Update 1 you no longer need to add any code in your program to support AmiUpdate: you just register the program's AppDir: variable with the AmiUpdate server, and that's it. As for the (optional) autoupdate script, I believe anyone can write a line of code with 'copystore' in it?
Aniway pls post here the source related to your OSD (p96_pip) so LiveForIt might start to look at .. :)
@LiveForIt
If i understand correctly actually you are totally unable to do any real test with all that p96 stuff right ?
If so, after you have implemented that 2 patches from kas1e, please feel free to publish a public binary to test, so we can test this specific driver for you
If I understand correctly actually you are totally unable to do any real test with all that p96 stuff right?
Well I have on AmigaONE-XE, with 9250 gfx card, I have ordered AmigaOS4.1 Final, so I can test it with a up to date OS. So if I do not work on it, its cash out the window so to speak.
I have a KWM (2 ports) I use with my PC and AmigaONE-X1000, connected, maybe I should spend some of the bounty money on larger KWM (3 ports), so I switch between all computers. My AmigaONE-XE is connected to an old Plasma TV, I'm afraid the image will burn in to the TV every time I use it.
o_O
Just because it works on a 9250 does not mean it works on 9200 gfx card or some other gfx card. That is where beta testers comes in, to see if it works ok on their setup. (Does not need to be OS4 beta testers, I'm not working on any secret A-EON or Hyperion cooperation project), you just need the time to respond. If no one reports bugs then its working.
Right now the most important thing is getting a repository working, so I can commit my changes from AmigaOS, with out having to FTP stuff to my PC :-/
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
But probably not of much help, as i do nothing about OSD there. If it didn't works in other versions of mplayer, then dunno.
Also do not know in what state source is, maybe even broken, but at least that ones come from latest compile of muimplayer which i put before in beta-thread.
p96_pip fixes Implementing menus in mplayer Drag and Drop Adding Screenshotdir and EXTPATTERN New feanor ffmpeg integration 64Bit fix Transferring of bounty will happens after beta-tests and before public release OpenSource
@Liveforit for 1300 Euro ? Deletion of install script saves 2 days
Just because it works on a 9250 does not mean it works on 9200 gfx card or some other gfx card.
As far as i know this "p96_pip" driver posted by kas1e should work correctly in any R100/R200 gfx card, and it works without the "white stripes" behaviour bug
Anyone can test it easly: just downloading the latest beta 9 of MUI MPlayer
OSD in p96_pip instead still buggy in both versions, but while in your version OSD are not visible at all, in the kas1e version all is visible but with some minor problem (it fliker a bit)..
Ideally later this one might be fixed in both version, but in alternative you might have a look at the new driver created by Joerg