Any altivec experts? (H.264 codec)

@zzd10h and LiveforIt

This is the preliminary text for this bounty:


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.

@tommysammy

Sounds good for me.

Concerning webm, could you try to stream this video through SMTube with settings = 480p webm ?

http://www.youtube.com/watch?v=81hWewkzflc

For me, video display is trashed with liveforit mplayer but works fine with MickJT_MPlayer.
Thanks

@tommysammy

Thanks Tommy, real appreciate your work in managing these bounties. I think I may well back this to support Liveforit.

My personal thoughts are that the first five things in the list seem almost like nice to have fixes rather than must have fixes.

Implementing menus in mplayer - mPlayer GUI works well enough for me.
Drag and Drop - mPlayer GUI does this.
Install script - I have never felt the need.
Adding Screenshotdir and EXTPATTERN - I have no need for screenshots.
AmiUpdate support - I don't see the need for this.

I am not suggesting that they be excluded, but perhaps rework the list so that it reads in order of importance?
I would have feanor's speedups as item number one.

@tommysammy

Let's see when he replied, however p96_pip (and its related fixes) are 1000 times more important than AmiUpdate support (for example) so it should be a priority ...

@samo79
We can add more things to the bounty but this would be a higher prize, you know?
We can think about that what we together want and pay

@tommysammy @samo78

Are vo_comp & vo_yuv2 usables on non RadeonHD systems ?

If p96_pip is used by a big portion of OS4 users, Samo79 is certainly right.

If more OS4 users will benefit from this new version, more OS4 users will donate, no ?

If LiveForIt agree, maybe better to replace "install script" by this p96_pip ?

@TommySammy @ddni
Did you try to stream the Youtube video that I linked previously ?
Thx

@zzd10h
i am at work, i will test it tomorrow

@zzd10h

I am at work too. Will try this evening.

@ddni@TommySammy

Thank you by advance (I'm at work too ;) )

@zzd10h

Are vo_comp & vo_yuv2 usables on non RadeonHD systems?

Vo_comp works with any graphic card that support composition, this is not exclusive to RadeonHD, vo_comp is ARGB video output it's not a yuv420p video output, so it's slower than p96 and vo_yuv2/vo_yuv, but faster than vo_SDL.

I am not sure, if composition works with voodoo cards on classic Amiga, but if it does you should be able to use it on that card as well.

The only requirement for vo_comp should be AmigaOS4.1 final.

@LiveForIt

Therefore why p96_pip is still used if vo_comp works on all OS4FE ?

If exlusively for speed improvements, it's important.

Samo79 ?

Thx

@zzd10h

He he, this is starting to look like SCRUM, for people who do not know how SCRUM works.

It works by assigning a time estimate to work item, then someone assigns a BV or usefulness value to item, and then you arrange the items, depending on how useful the items are.

The items are then put into what is called a deliverable or a sprint. This one-month payment, we have agree on is kind like a sprint.

we are taking about two different p96 problem's, one issue is white tripe issue, this one is problematic to estimate the time for, it's going to take, I'm not even sure I can reproduce the problem on my Radeon 9250 card. Or what cause of this issue is.

The other problem the p96 OSD problem that might be two days work. If you want me to fix the OSD problem instead of install script, I be willing to do that.

@zzd10h

Therefore why p96_pip is still used if vo_comp works on all OS4FE?

well a yuv420p format consists of 12bit vs 32bit data, its faster to transfer to the graphic card, and in some cases, you don't even need to convert the format from A to B, there is a conversion in AmigaOS4.1 p96_pip I'm not sure way that is, maybe it's not yuv420p, but some other yuv format.

Vo_comp is ARGB so its lot more data that has to be sent to graphic card.

In the latest p96 video output from Joerg Stromayer he was experimenting with different yuv formats, many of the formats does not work on my Radion 7250 graphic card.

The older p96_pip was picked over p96, because people was saying it worked better.

@zzd10h

If I remember well the webm codec doesn't function with vo_yuv but If you use vo_comp it works fine. (I wrote it some time ago on Amiga-NG.fr when testing the new mplayer with smtube)

I will try again later with latest Radeon HD driver.

If someone wants me to do an SDL version with Feanor's altivec changes, that *probably* won't take long. I'd look at it at the start of next week. Just remember it's likely to still be slower than the current LiveForIt-MPlayer, and Feanor's changes are mainly for H.264 decoding.

I might be able to retrofit some of the other Amiga specific output modes (heavy emphasis on might), but this 64bit / largefile support I still don't know how to do.

If anyone can come up with a speedup for decoding H.264 MP4 on Sam460ex's this would be welcomed (with open wallet of course)

@zzd10h

Quote:

No they are not usable with the older graphic cards (for example Radeon 9250)

If you set those what you obtain is a "white" window, aka no output

See: http://s18.postimg.org/yr625qm21/no_output.png

In the current LiveForIt version (using a R100/R200 gfx) the only supported video drivers are :

- p96_pip --> the best one, it only need to be finished (see bugtracker for details)
- cgx_wpa --> a bit slow but works, (see bugtracker for details)
- sdl --> a bit slow but works (apart little tidy no need to modify it further)

Quote:

If this "vo_comp" is the one that will be activated setting "default" in MPlayerGUI, then my response is: no

See the grab above

Eventually, similar to the old p96_pip we have also a new one from Joerg (called vo_pip.c)

This driver is maybe the faster one, even faster than p96_pip (if you are using an older cards of course), however it was never finished and at this point i doubt it will be anytime soon, source still there aniway ...

https://code.google.com/p/mplayer-amigaos/source/detail?r=68

@LiveForIt

Quote:

As i told you many time, (even in bugtracker) kas1e fixed the white stripes issue in one of his internal betas of MUI MPlayer, so all you need is just ask him for the fix ... the p96_pip driver are exactly the same in both versions !

@ddni and all

It's important IMO to not burden LiveForIt with trivial things that does not require the build environment for mplayer.

Things like AmiUpdate and install script, anyone can do. You don't need to compile mplayer to do this, therefore someone else should do it instead of adding to the bounty, slowing down the important work, which is to make the codecs and video driver to work.

@samo79

Then provide video files so I can test, or are we talking about all?