links not working(empty), plz fix.

_________________
Simone"Tuxedo"Monsignori, Perugia, ITALY.

https://www.bountysource.com/teams/amigaos41/fundraiser

Umm.. is this for "MUI-MPlayer" or for some other MPlayer port? Shouldn't MUI port already have at least menus and d&d?

_________________
- The wiki based MorphOS Library - Your starting point for MorphOS
- Software made by jPV^RNO

@jpv

MUI Mplayer has all this already, and merging OS4 specific video drivers would of course be the easiest way (a 1 hour job or so), but it seems developing one mplayer fork for each new "feature" is more fun. :)
Why not!

@Fab

Quote:

merging OS4 specific video drivers would of course be the easiest way (a 1 hour job or so), but it seems developing one mplayer fork for each new "feature" is more fun.

Exactly what I think about this fun raiser :)

_________________
The Rear Window blog

AmigaOne X5000/020 @ 2GHz / 4GB RAM / Radeon RX 560 / ESI Juli@ / AmigaOS 4.1 Final Edition
SAM440ep-flex @ 667MHz / 1GB RAM / Radeon 9250 / AmigaOS 4.1 Final Edition

@Fab
You did say somewhere that you did not want your latest MuiMplayer in a repository, this is partly way I'm working on the earlier one from AfxGroup.

The source code is open to everyone so, if Ka1e wanted to do back port the video outputs into MUIMplayer, he can do that.

Porting the video outputs in my version into the MorphOS version will require some new features in MorphOS I think.

Quote:

a 1 hour job or so

Yes that is about the time it takes to compile the mplayer code, after doing a make clean. Without doing any changes to the code.

The code I'm working is a bit of a mess, because the code was originally written to only to work with p96pip video output, now I need to make that code work with all video outputs.

The basic work that need to be done is clean the code up, a lot of tabs, add enum in stead of numeric values (hard to understand what the CASE does when you work with number instead of names), make the code more readable by moving code out of case switch's into functions.

Also the numeric values had to go, because, if change or add something to the menus, the number positions in the menus be all wrong.

Remove the "Interface", I compile with –D__USE_INLINE__, no need to make code less portable. And I kind of like not to need to type IExec, IDOS, way should I when the macros do it for me.

Now after all that; test and make sure it works. Then fix bugs, which might have been in the original code, or because Mplayer core code is more up to date, or maybe because of all the changes.

Then I have to make it work with all video outputs, and get feedback from beta testers and possible fix more bugs.

So most definitely, more than 1-hour job.

I'm sure Ka1e spent more than 1 hour poring MUIMplayer, most developers are over optimistic when they make time estimates, while AmigaOS4 and MPlayer has common past, I bet you used things is only work on MorphOS, and there are things needs to done on AmigaOS4 version like opening and closing interfaces.

Quote:

but it seems developing one mplayer fork for each new "feature"

This not the case, the code is in repository, so other developers can help out, but that does not happen for the most part. I started with mplayer because nothing was happening. The X1000 does not have Overlay, so a different way displaying graphics was needed, at the time.

There are some individual ports like one from MikeJT, I think he is compiling directly from MplayerHQ, there are some AmigaOS stuff in there, but he does not change the code; he only ports mplayer. (Recompile mplayer.)

There might be 4 or 5 mplayers for AmigaOS/MorphOS, but there is only 3 places the sources come from.

MPlayerHQ, MUIMplayer, or AFXGroup Mplayer.

(LiveForIt-Mplayer is sort of a reboot of AFXGroup version.)

Quote:

more fun. :)

Working on this version of mplayer, I think people do expect things to stay true to AfxGroup MPlayer look and feel, this also something I try to keep in mind when working on the code.

However, I think I have more freedom to do things the way I like things to be done.

Last edited by NutsAboutAmiga on 04-May-2015 at 10:16 AM.
Last edited by NutsAboutAmiga on 04-May-2015 at 09:58 AM.
Last edited by NutsAboutAmiga on 04-May-2015 at 09:50 AM.
Last edited by NutsAboutAmiga on 04-May-2015 at 09:44 AM.
Last edited by NutsAboutAmiga on 04-May-2015 at 09:35 AM.
Last edited by NutsAboutAmiga on 04-May-2015 at 09:28 AM.
Last edited by NutsAboutAmiga on 04-May-2015 at 09:13 AM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

My incentive to donate for this is to get an MPlayer with the Altivec optimizations done by feanor to get more HD videos to play at full speed on the X1000.

_________________
- Don't get fooled by my avatar, I'm not like that (anymore, mostly... maybe only sometimes)
> Amiga Classic and OS4 developer for OnyxSoft.

Yes, that was original idea.

Fix the 64bit off_t stuff, copy the new FFMEG into mplayer, recompile, DONE.
Then some suggested we need to add/do more stuff, to get people to donate. As not everyone has AltiVec.

My original idea was that might donate for thing they won't, not for everything as package.

Not everyone agreed, so we ended with package deal, this is way the bounty contains things like Menus and Drag and Drop and so on, and other fixes.

Last edited by NutsAboutAmiga on 04-May-2015 at 10:42 AM.
Last edited by NutsAboutAmiga on 04-May-2015 at 10:39 AM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

That's fine, as long as you manage a SCRUM-like development scheme with incremental releases

_________________
- Don't get fooled by my avatar, I'm not like that (anymore, mostly... maybe only sometimes)
> Amiga Classic and OS4 developer for OnyxSoft.

Even now SCRUM, like approach dictated what I was going to do, what people wonted to pay for or not.

Product Owner: Was the community.
Business value is what the community is willing to pay for item x.

Estimated the time need to write an install script and put a price tag on writing a install script, people did not wont me to do it.

That's was okay for me I only wonted to wast my time on this if generated a income.

"Business Value" for install script was less then the effort needed to write it, and test it.

Sprint backlog is sort of the things we agree on the bunty.
Was dictated by the upper value of the community was willing to donate.
(Already gave a 50% discount and donated 50$ my self.)

Sprint was agreed to be around 27 days. (based on the time estimate for etch item in back backlog)

Working increment is what goes back to the repository.

Sure I can divide the backlog into 2 or 3 sprints, that's what I'm thinking, but first the money needs to be collected, so I can get to work.

Beta testers is written in the bunty, if people like to get BETA versions before the Bunty is completed they need to agree to BETA testing, I will only accept people who has donated as beta testers.

Last edited by NutsAboutAmiga on 04-May-2015 at 08:08 PM.
Last edited by NutsAboutAmiga on 04-May-2015 at 08:01 PM.
Last edited by NutsAboutAmiga on 04-May-2015 at 07:56 PM.
Last edited by NutsAboutAmiga on 04-May-2015 at 07:44 PM.
Last edited by NutsAboutAmiga on 04-May-2015 at 07:40 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

Hey, let's invent the wheel once more. There are way too few wheels invented yet...

Always funny. I have a brilliant idea for the next stupid money tp spend: What about a fundraiser for OWB to bring it on par with MUI-OWB?

_________________
My programs: via.bckrs.de
MorphOS user since V0.4 (2001)

@Zylesea

If I was able to get OWB compiling (I have tried before and failed), I be happy to do work on OWB, if people are willing to pay for it. It's nothing wrong in having different versions of things, people like different things.

I think the number one thing people wont in MUIOWB is faster video playback on X1000, and full screen support. Like you have on MorphOS. I bet few people will donate to get that. So if there is developer willing to do that kind of work, step forward.

Sure it benefit more people if we worked on same source code. keeping mplayer up to date whit latest patches and versions.

But it's not easy to commit changes to TAR balls, I need repository, and need a bug tracker to see what needs fixing, so if FAB don't wont to keep the source in repository, its not easy to cooperate.

Merging TAR balls manually is not fun, we need better developement tools.
Even SVN is stinking old, it does not support SSL, like SF.net requires, so I'm trying out SGIT now.

Last edited by NutsAboutAmiga on 04-May-2015 at 11:11 PM.
Last edited by NutsAboutAmiga on 04-May-2015 at 09:35 PM.
Last edited by NutsAboutAmiga on 04-May-2015 at 09:07 PM.
Last edited by NutsAboutAmiga on 04-May-2015 at 09:03 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@Nutsaboutamiga

Quote:

It's nothing wrong in having different versions of things, people like different things.

Isn't the point of the bounty to reduce the number of baffling choices, and just provide one mplayer that does all the stuff people have created in separate builds?

Last edited by Boot_WB on 05-May-2015 at 08:50 AM.

_________________
Troll - n., A disenfranchised former potential customer who remains interested enough to stay informed and express critical opinions.
opp., the vast majority who voted silently with their feet.

@Boot_WB

+1

@NutsAboutAmiga

Please don't spend time on the old OWB. Odyssey needs a new webkit engine and some improvements in the video area, like composition scaling maybe, and a bigger stack! Otherwise it's GUI is complete, unlike OWB. It always gets unstable after playing any video in Odyssey and I suspect a too small hardcoded stack when launching it...

Last edited by Deniil715 on 06-May-2015 at 07:00 AM.

_________________
- Don't get fooled by my avatar, I'm not like that (anymore, mostly... maybe only sometimes)
> Amiga Classic and OS4 developer for OnyxSoft.