Any altivec experts? (H.264 codec)

@zzd10h

The webm link does not play with the settings that you requested.
http://www.youtube.com/watch?v=81hWewkzflc



Edit that video doesn't seem to play with any setting.

http://www.youtube.com/watch?v=ngElkyQ6Rhs Star Wars teaser#2
Plays fine with 480 webm

@LiveForIt

Quote:

Don't understand what video files do you need ?

@samo79

I think he meant if there's any specific video files for testing, or just all

@ddni

Could you also try this video in 480 webm please with -vo comp_yuv2?
http://www.youtube.com/watch?v=-IunmW3wI5Q

StarWars is playing fine, the above one don't (amongst others).

@noXLar

Ah, of course it's the same with any kind of videos, simply there is no video output at all (audio is ok)

@davebraco

Ah yes, you are right, I forgot your advice on AmigaNG "-vo comp" works fine.

Your latest URL with "-vo comp_yuv2"




Your latest URL with "-vo comp"





@ddni
try to delete your Qt:home/.config/smtube/yt.js and retry the SMTube video.


@LiveForIt & Samo79
Thanks for the technical explanation about p96 and SCRUM.

@MickJt
Yes, if it's easy for you, please implement Feanor change in your SDLMplayer ;)
Thank you

@zzd19h

comp_yuv2 is async, it might be some key frames are rendered into wrong buffer, I have seen corruption due to heavy CPU load before.

There is number of factors that can mess things up, remember I'm using DRI also this complicates the video output.

Mplayer mymovie.avi –vo comp_yuv2:nodri
Mplayer mymovie.avi –vo comp_yuv2:nodma

Check if you have the same problem with comp_yuv.

@LiveForIt

Tested

–vo comp_yuv2:nodri
–vo comp_yuv2:noma
–vo comp_yuv,

but same distorsions.

CPU workload is very low during video, around 02%

@zzd10h

Deleting Qt:home/.config/smtube/yt.js worked. Using -vo comp the webm videos linked to in this thread play fine.

@ddni

Great, and using -vo comp_yuv2 (the default) ?

@zzd10h

using the default, I get the same smearing distortion as everyone else.

@ddni
Thank you :)

@zzd10h

Star Wars video works well in 480p webm
The video that you posted, doesn`t load

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:


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
As said to ddni earlier,
-try to delete your Qt:home/.config/smtube/yt.js and retry the SMTube video.
-do you use "-vo comp_yuv2" ?

@TommySammy @LiveForIt

What about this ?

"p96_pip fixes (to gather more amigans to this bounty)
New feanor ffmpeg integration
64Bit fix
Transferring of bounty will happens after beta-tests and before public release
OpenSource"

I didn't follow the discussion but my comments below:

- Implementing menus in mplayer

Low priority. i.e. it could be postponed to another bounty if the first one succeeds.

- Drag and Drop

AFAIK, it should be done in 1 hour or less. Ain't it just an intuition flag to make the window an appwindow and to reveive the "dropped file" event?

- Install script

Useless. Amigans will take care of that.

- Adding Screenshotdir and EXTPATTERN

Could you explain? It means nothing to me so I cannot get interested to that and contribute

- AmiUpdate support

Same as install script.

- New feanor ffmpeg integration

That's the interesting part. Go for it!

- 64Bit fix

what does it mean?

@Elwood

Movie files bigger then 4gb?

@Elwood

Quote:

Large file support AFAIK.

On AmigaOS this means changing off_t to _off64_t, struct stat to struct stat64 and many of the file i/o functions to their 64-bit counterparts (fopen() to fopen64(), stat() to stat64(), etc.).

@tommy
Quote:

- Install script : waste of time and only complicate the thigs. Everyone can unpack archive and run from whatever place he want.

- AmiUpdate support : waste of time as well, as its not the programm which will have offten updates which need to deliver via amiupdate. Classic new-version release are enough for sure.

All what is need it there:

Quote:

All the other parts (imho) not worth of worry.

@kas1e

Check mail