@kasle, elwood, etc, We are a majority to think that this bounty should focus to essentials things, no need for minor useless candy things. (remember DJNick bounty...)
But, why do you avoid the p96_pip ? Ok, you and me use vo_comp codecs but as Samo79 said others OS4–Amigans still use p96.
Stay as "vo_comp" only and you will remove a substantial part of os4 users... Remember Feanor bounty... ;)
@LiveForIt You are the only one to know if you want (will) to implement/fix p96_pip. Maybe too difficult, but maybe we will be only radeonHD users to fill your bounty...
@tommysammy@LiveForIt Please, reply, ok or not for
"p96_pip fixes (to gather more amigans to this bounty) New feanor ffmpeg integration 64Bit fix (as salass00 said, does it worth a bounty step ?) Transferring of bounty will happens after beta-tests and before public release OpenSource"
@zzd10h and LiveforIt Is it ok now? I don`t want to delete Installscript and Amiupdate support because we have novice user too. For us expert users are much things not hard to use. We must always find a balance
Any suggestion to add to the bounty? Remember, we have to ask for the price. LiveforIt will not do it for free and there is no need to make it for free(in my opinion) I will wait a few days for all suggestion and then create the bounty
This is the preliminary text for this bounty:
p96_pip fixes Implementing menus in mplayer Drag and Drop Install script 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
1400 Euro +10% bountysource fee +1,9% + 0,35 Euro per transaction -------------------------------------------------- 1566,95 Euro -------------------------------------------------- 1687,37 US Dollar Since there are always fluctuations, i would collect 1.700 USD
I will create a bounty at bountysource.com After we reach the goal, it takes about a month until payment.
Install script is pointless. Unatchive it and run it, even my tech hating wife could do it. Amiupdate is equally pointless, it will never be used. Most users like to keep and compare mplayer versions.
tommysammy, as it seems that the Installscript and Amiupdate support can be done by others and don't require programmer's skill, we should remove it from the bounty.
As soon as the executable has been delivered by LiveForIt, we could add the install script/amiupdate, pack all the stuff in an archive and upload it to os4depot. Then add it to the amiupdate database etc.
I don`t want to delete Installscript and Amiupdate support because we have novice user too.
Its still waste of time and money. Everyone who run install script, will unpack archive itself. If he do so, then why he need any kind of script, which will just COPY where user can copy myself ? Its just really complicate the things
And AmiUpdate waste of time and money too. Because Mplayer is not the programm which will have contant updates. It will waste of time, money, dirty the code but non-necessary parts and so on.
Everything should be focused on _real_ things. And if money will be payed, it should be payed for _real_ things, not for some crap which any of us can do (i.e. install scripts and amiupdate integration).
@zzd10h Quote:
But, why do you avoid the p96_pip ? Ok, you and me use vo_comp codecs but as Samo79 said others OS4–Amigans still use p96.
I not avoid :) I through p96_pip already works fine (as in muimplayer), and already used in the version from liveforit ? Is there new problems which wasn't happens before?
I not avoid :) I through p96_pip already works fine (as in muimplayer), and already used in the version from liveforit ? Is there new problems which wasn't happens before?
No it's not the same, what he have now is only the old driver from the old afxgroup's version, however since then you added a fix for the "white stipes"
Okay, I see almost everyone agrees that install scripts are useless, this is way has not been done before anyway.
I understand TommySammy for wonting to keeping it on. This is simply just work, it not challenge as was pointed out by few people, writing and testing to see if its working, in order to getting It right. You can do it simple by copy script, your can do it with stylish with an install program, the result is the same. Things is put on the hard-drive, hopefully in directory you expected.
It's no brainer.
The p96 problem consists of two problems, so you won't me to do that you need to remove two things from the list. (AmiUpdate support kind depends on install script, but AmiUpdate is only half a hour work, so does not really count, beside I ended giving you that one for free.).
* Adding Screenshotdir and EXTPATTERN
Will actually require me to fix vo_png or vo_jpeg, or what is use being able set directory in mplayer if mplayer crash when you are trying to take a snapshot.
* Drag and Drop.
yes sure it can be done, do you need it?
One more thing I have ordered a copy of AmigaOS4.1 Final for AmigaONE-XE, in case you decided I should look into p96 work, instead of install script/amiupdate and something else.
I know you have been waiting for working menus for a while, so that is one has to be done. When it's done it should work in all native Amiga video outputs, that excludes vo_SDL, this will be supported vo_yuv, vo_yuv2, vo_comp, vo_cgx, vo_p96pip.
Edited by LiveForIt on 2015/4/19 13:13:58 Edited by LiveForIt on 2015/4/19 13:15:25
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
I'd like to suggest including the AmigaOS startup code into MPlayer for handling "Project" files, etc., so it can finally be used as a def_icons "Tool" and let users just double-click on vids to play them.
Simple enough that *I* could figure it out. ;) ...
re: Installation - I'd also suggest an installer seems like overkill, but I think it would be good if the distrib did a couple things to make it easy for the user:
First, keep the archive so it creates a directory. The user can then just grab it and move it wherever they want. No fuss, no muss!
Finally, make any default config file(s) separate from any config file(s) created by the user - f.e. have a "default.config" and let the user create their own "user.config" file if they want.
MPlayer would have to look for both files, but that would allow for simply decompressing distributions over top of an existing install without losing all one's settings.
LiveForIt, thanks for all your work on MPlayer thus far! I'm looking forward to seeing what more you and feanor and all can do with it and more then happy to support your efforts with the bounty.
p96_pip fixes Implementing menus in mplayer Drag and Drop -----------------Install script (removed for p96_pip) Adding Screenshotdir and EXTPATTERN AmiUpdate support New feanor ffmpeg integration -----------------64Bit fix (removed for p96_pip, are >4gb videos frequently used ?) Transferring of bounty will happens after beta-tests and before public release OpenSource
@zzd10h this list?I want have 64 Bit fix because i have much movies over 4GB
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
Personally i may obtain a fixed driver for p96_pip soon, then it could be merged quite easily without any modification, certain i don't think people should pay for this
Personally i may obtain a fixed driver for p96_pip soon, then it could be merged quite easily without any modification, certain i don't think people should pay for this
If someone else has fixed it already, then it should not be a bounty requirement.
I like to do a DIFF compare, to see what fix is, when you have that code.
Maybe someone has something else I should work on instead.
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
Of course it was fixed already, how many times do i need to repeat you :) I'm waiting kas1e for the file, but if you like to have it directly (without passing from me) just contact him at:
I think AmiUpdate should also be dropped form the bounty. LiveForIt said he'll do it for free, which means it doesn't have to be in the bounty. besides, if he decides he doesn't have time, someone else can do it and the bounty would still be valid.
AmiUpdate is not important also since it isn't updated very often.
Everything not essential to the mplayer code should not be in the bounty to prevent extra delays.
Software developer for Amiga OS3 and OS4. Develops for OnyxSoft and the Amiga using E and C and occasionally C++
Joerg's P96_PIP is still the fastest implementation and really works flawlessly (I do not know if kas1e's implementation is the same). This one should be the new p96_pip.
@K-L Yep, in muimplayer i just use Joerg's p96 pip, old one, which works everywhere. As i remember Joerg lately made some new version, and probably upload it to the repo of our port, so dunno what version in now.
@samo I dig in into the code, and probably no needs to send anything, as fix for the "white strips" are trivial (joerg just help with it back in time):
SA_Compositing should be in FALSE to fix those white strips.
But for now no one use it (in any real version of MPlayer) At the time we tested a standalone binary (a plain one compiled by Joerg) and according to our test it was the faster version around, but as you can read in changelog it still unfinished ... of course would be good if someone can complete it and then bundle in current MPlayer but for now let's be realistic and hope to have atleast a fixed version for the good old p96_pip
Quote:
I dig in into the code, and probably no needs to send anything, as fix for the "white strips" are trivial (joerg just help with it back in time):
SA_Compositing should be in FALSE to fix those white strips.
Ok thanks for the patch, this will fix the white stripes bug.
Just another thing: can you post here also the part of code releated to the OSD ?
To be honest OSD still a bit bugged also in your driver (it flicker a lot) however more or less it works, so always better compared to the current "OSD-non-working-at-all" situation of the current LiveForIt version :)