MickJT-MPlayer

@MickJT

Why not use 1.01, 1.02 etc.?

@Raziel

Quote:

Because If his goal is amiga compliant versioning, then those aren't either.

VERSION.REVISION

where VERSION and REVISION are whole numbers starting from 1 with no leading zeros

eg

1.1 4.5 2.10 3.11

but not

1.0 0.9 1.0.1 etc

Sorry about 1.0 then too :) .. but I don't think I need to retroactively call that one something different in the changelog, otherwise I'd then have to bump the revision even further, not to mention cause confusion referring to 1.0.1 as 1.2, and 1.0 as 1.1.

@MickJT
What's the benefit of your port of MPlayer, compared to the other ones? (e.g. LiveForIt) More up-to-date source code?

edit:
Seems like it adds support for SSL streaming (as now required by YouTube). Anything else?

@ChrisH

That's pretty much it, and other minor things noted in the changelog. Also see #25.

@MickJT
Going by #25, you included LiveForIt's enhancements? So it should be about as fast as his version?

(Actually yours seems very slightly faster, going by one brief test.)

@ChrisH

Yes it should have everything from his builds too. The reason I drew your attention post #25 was that I originally was just going to replace afxgroup's version, but by request, I didn't :) So yeah, just "more up to date" is the primary goal.

What does this mean:
"[mov,mp4,m4a,3gp,3g2,mj2 @ 0x5586b4c0]Protocol name not provided, cannot determine if input is local or a network protocol, buffers and access patterns cannot be configured optimally without knowing the protocol"

I don't know whether the default buffer without -cache would be fine for SSL with "optimal pattern". Hopefully this SSL madness will end in the name of saving energy.

Putting " quotation marks around the resource, like "https:
did not make a difference.

How might the player accept keyboard events when not doing video? Is that possible in just Shell?