@tlosm

Overlay is also supported on Radeon 9000 pro (overlay is implemented for all supported radeon models).

Anyway, maybe your particular video only gives 240p, but the default resolution is 360p h264, and you can also choose higher resolutions and format if you need.

@kas1e

The player is mostly generic and doesn't have any particular requirements, except for the overlay mode that uses a couple "cgx5" extensions. But in fact, the main requirement there is to be able to attach a video layer at given coordinates in the window (its area is the webview, not the whole window). But anyway, if it can't be done, a real fullscreen mode could also be implemented instead. That's just minor implementation details.

@kas1e

1 & 2. 5k euros is for opening the browser including media player.

3. swfdec could be opened as well, but it's a different thing, and anyway, it won't give you flash 9.0+.

4. The current version of odyssey relies on shared libraries versions of cairo, pixman, fontconfig, and i can't open that, since it's not even my work.

That said, all these libraries are mainly recompilations with minor tweaks (the actual work was about making them shared libraries):
- Cairo needs almost nothing (semaphore implementation, about 4 lines of code).
- Pixman just needs runtime altivec detection (3 lines of code?).
- Fontconfig just needs a couple changes for amiga paths. - I've already given you the necessary code to make Curl multithreaded, but for some reason you couldn't make it work in OS4. Maybe a thread-safety issue in OS4 bsdsocket?

I can always give my old changes of cairo, pixman and fontconfig if needed, but if you already have issues with such simple things, the rest will be hard to port...

5. Regarding the integration of OS4 and AROS in the code, well, considering the changes are VERY minor, they can as well be kept as patches, anyway. This is also what i do for MorphOS changes when merging, you know.
Keep in mind i have much more work each time i synchronize webkit to a current version. The OS4 and AROS (and MorphOS for that matter) changes are located mainly in a layer that doesn't change often, so all amiga* patches will happily apply.

6. My experience tells me that coding isn't supposed to be easy. Either you deal with all the required steps or you just don't do it. Don't expect everything will be done for you.

@TSK

I didn't see you questioning TW bounty that was bigger and yet doesn't quite match users expectations. Funny!

@vox

Quote:

I don't know what you mean with "normal" firefox, but the same behaviour is exposed when only HTML5 is enabled and Flash is disabled.

For instance, when subscribed to the HTML5 program, this link http://www.youtube.com/watch?v=hUoJBerFDsA will tell Adoble Flash plugin is needed.

This is especially stupid because in fact, the html5 player is actually running the video behind this message! You can hear that in odyssey. In my script (which i need to update), i bypass this by deleting/hiding this silly message.

In any case, Odyssey works just as well as Chrome or Firefox when it comes to Youtube in HTML5 mode (and even better when scripts are enabled).

@Fairdinkem

For your information, Youtube's HTML5 support is rather buggy for ALL platforms: just disable flash on firefox or chrome and use HTML5 instead, you'll see:
- sometimes the video is not available as HTML5 (which is why i wrote a script for this: it retrieves direct links and creates a builtin HTML5 player)
- sometimes the video is said unavailable, while it IS actually available
Sometimes Youtube insist on using Flash even though HTML5 is available (worse, the HTML5 playback begins for a couple seconds, and then they cover the video with their "you don't have Flash" stupid message). My script also try to deal with this, but it's not that easy
- Youtube fullscreen mode sucks, which is why i wrote a userscript to deal with it, where i enabled overlay mode when fullscreen button is pressed.

All in all, Youtube is really buggy, and the scripts i wrote are workarounds if you want, but it would be the same for TW or any browser not having Flash... At least, with the 2 userscripts i wrote plus swfdec plugin installed, 99% of Youtube videos work nice and fast (and NO, they don't play through swfdec... swfdec is only needed to shut up youtube when they think it's smart to enforce Flash. I replace the flash element with html5 video just after).

This is sad, because the HTML5 media implementation is entirely compatible, but we are forced to use tricks because of Youtube bugs... Fortunately there are many other sites working without the need for scripts like dailymotion, vimeo and many others.
Also, you're mistaken about Odyssey using MPlayer in overlay mode.
It's embedded in Odyssey. It's a standalone player, and it certainly doesn't need mplayer at all. You might have noticed similarities with MPlayer controls in overlay mode, maybe? Well, it's not surprising considering i also develop MPlayer...


@tlsom

Pressing the fullscreen button enables the overlay mode (until Youtube breaks it, then i have to update the script again).
You can also unsubscribe from Youtube's HTML5 program. That way the builtin HTML5 player should kick in more frequently instead of Youtube's buggy player, and you just have to press fullscreen button or contextmenu -> fullscreen to enable overlay mode.

@ChrisH

The 5k euros would be for a current version of webkit (i.e october 2013) and HTML5 media.

But if noone is interested, well, not my problem... :)

@tlosm

You're really bad at benchmarks you know... Or you're being very dishonest. I'm not sure...

You didn't even enable the overlay/fullscreen mode in odyssey, so video display is done through software cairo, which is rather slow, but still enough on a mac mini (even if cpu usage is close to 100%). But with overlay enabled, it would be like 30% cpu usage on a mac mini. Thanks for your totally irrelevant benchmark !
For the record, i use the same display routine in OWB as in my MPlayer port when overlay is enabled, and it's about as fast. On my G5 setup, in OWB, i can play 720p stuff at 50% cpu load and 1080p when bitrate isn't too high.

Then, you compare that against OS4 playing this video in MPlayer... Totally bogus comparison. In this case, also use MPlayer under MorphOS (oh but sorry, it's faster, you probably didn't want to show that...). Alternatively, if you want to be fair on a browser basis, don't compare against a standalone video player, and play this video with Timberworlf (but i know, 1fps isn't very impressive).

@smf

Quote:

Er, i beg your pardon? First this is very rude, and then, where and to whom could i have stolen mediaplayer sources for a web browser running on MorphOS, exactly? Stealing myself In a parallel universe where i would already have written it? Or in the future, maybe? Be serious please.

Just FYI there's no other implementation of a working HTML5 audio/video player on any amigaos-like, except for TimberWolf (if one can call that working, of course, because watching 1fps videos isn't very enjoyable IMO).

The media players implementations in the other main browsers are either already opensource:
- Firefox (unusable crap).
- Chrome (relies heavily on Chrome framework). Faster to rewrite your own player.
- gstreamer for webkit gtk (way too bloated). Ditto.

or closed:
- apple quicktime framework for webkit mac build
- windows media thing for webkit win build

So as you can see, there's really nothing to "steal"...

@tlosm
So what? That's not a lot in the real world, and it definitely took me quite some work to implement it.

Raise a bounty with about 5k euros, and i'll consider opening html media support. :)

@kas1e

Just for the record, Odyssey is already in a versioning system, and that's MorphOS CVS. I just don't want to maintain two different branches of it.

And really, the amigaos4 diffs are really minimal, small enough that they can be kept in small patches that apply to any given snaphot i could provide.

Odyssey is also not merged in WebKit official tree because (assuming it would be accepted) it would just be too much work dealing with a project of that kind, much more than simply applying patches whenever i feel like doing so.

That being said, each time i merge WebKit (about every month, latest is from June 2013), it's quite some work. I generally get 20-50MB diffs, depending on WebKit project activity, with a couple dozens of conflcts, new API changes to deal with, new implementations, new generic bugs to iron out and so on...

So it really doesn't compare to the amigaos4 diffs. These ones mostly apply to the morphos part and this one i don't change in a major way so often, so it won't conflict a lot. It's really the easy part...

As for which of Reaction or MUI OWB is the best, well, the feature list is self-explanatory i think... If the font look is poor, that's because the fontconfig default config file has probably not been supplied or set correctly in the OWB OS4 archive (like bad kerning or antialiasing, or poor choice of fonts). Speedwise, it's faster in scrolling for design reasons, and network access is just as fast since it's based on the very same curl backend (and if the os4 port had a working curl threaded implementation, it would be entirely non-blocking as well, like on MorphOS). Odyssey 1.9 is old for sure, but on MorphOS it was stable (like a couple weeks uptime...), so i would look elsewhere about this kind of issues.

There's no reason to have new scripts, since the old ones work just fine... :)

@Severin

With OWB, there's no file cache, so the image is only stored in memory cache, in raw format, and it has to be downloaded again (or encoded).

On the other hand, you can use "copy image" context menu item, which copies the content in IFF format to the clipboard, without redownloading anything.

Dopus5 is just much more than Dopus4. I used it a long time as workbench replacement since it was released, because it offered much more than workbench. But it would have to be modernized in several aspects, now (icon support, 64bits support, small gliches here and there).

Good idea. The dl filename itself should be more explicit, using title, but it's not doable in a href link, it seems (unless HTML5 extended this).

Anyway, you all might be interested in another userscript i found, that works almost out of the box (it was originally written for GreaseMonkey and chrome).

Here is what it looks like:
http://fabportnawak.free.fr/temp/youtubedl.png

I'll upload on my owb/scripts/ dir after a few cleanups.

Here it is:
http://fabportnawak.free.fr/owb/scripts/YouTube_EZDownload.js

MPlayer (and anything using ffmpeg) can play WebM, provided it's less than 1.5 year old or so.

If kas1e updates MPlayer, you should have WebM working.

@RNS-AMiGA-Club

And why exactly do you think a webkit-based browser is less modern and complex than Firefox?

WebKit is more compliant than Firefox in about every HTML5 test out there, and it's also significantly faster.

As for the browser UI itself, OWB might not offer everything FireFox gives (though you should really better check twice), but unlike FireFox, OWB still comes by default with AdBlock, userscripts (same as greasemonkey), WebInspector (like FireBug) and several other things, and following amigaos standards and technologies.

This "Mozilla is a technology and is much more than a browser" argument is a bit empty to me... Where are all those XUL applications that will benefit AmigaOS, exactly?

There is much more than video and audio to HTML5, and the difference between HTML4 and HTML5 is really quite big :

mathml
canvas
new elements
many new form types
drag'n'drop
application cache
iframe stuff
geolocation
webgl
websockets
xml http requests v2
file read/write apis
session storage
local storage
indexeddb
notifications
workers
and probably more..

Anyway, having video support without javascript is a bit pointless. Most sites don't use the plain video element as-is and they're almost always heavily scripted to have their own UI (like youtube, vimeo, dailymotion and so on).

It's however possible to extract direct links and display the video in a plain html5 video element, but for this, javascript is again the easiest way to go (i wrote some extension in OWB to do this when HTML5 mode is not available for some videos in YouTube, for instance).

@TSK

Unless it was disabled or broken, MPlayer (MUI) supports supports multiple WB arguments. So it should really work already.

And it also handles a file selection drop from workbench/ambient/whatever over the video and playlist windows (in the last case, it just enqueues and doesn't automatically play the first file of the selection).

I can't comment about old OWB version anymore, but links are not supposed to be underlined, given the code of this site... And they're indeed not underlined in OWB nor Firefox, for instance.

style.css:6

a {color: #432; text-decoration: none; font-weight: normal; background-color: transparent;}
a:hover {color: #ff6600;}

The site explicitely prevents links from being underlined. Odyssey/OWB allows to set any default css styles you want by creating progdir:resource/userstylesheet.css file, but it won't override the site one. I might create some userstylesheet manager like i did for userscripts at some point, though, to customize any site you want.

@ktadd

The rexx port of MPlayer was implemented in MorphOS port in the first place in 2006, and it was opensource already, so there was no need to create incompatible commands later in the OS4 port. And as said above, all mplayer internal commands are accessible if needed, plus the ones i added.

If you need additional ones, you can always tell me what you need.

About gui/command line:
There's the GUI mode (which also accepts all the standard mplayer command line options). GUI mode is triggered by different ways: -gui 1 in CLI mode, or GUI tooltype in MPlayer icon in Workbench mode.

In non GUI mode, two possibilities:
You run mplayer without any (wb)argument in Workbench mode, then it will display a requester, which is rather wanted.
You run mplayer without any argument in CLI mode, then it will just show help, as intended.

And let's repeat it: the GUI is integrated, but it's just an additional mode that doesn't interfere at all with command line options or config file, it works along with them.

@328gts

Ah, but it's a bit utopic to hope thousands and thousands new users will come (back) to our platforms, anyway (be it OS4, MorphOS or AROS). But since MorphOS is available for macs, the progress has been steady, and we regularly see new users.

Regarding OS4 and its current HW situation, i agree supporting macs would hurt Acube and AEon, because let's face it, people may like new shiny machines, but when you can find cheaper and more (or as) powerful, the choice might be slightly different.