-- fixed bug in Odyssey with WebP rendering being in blue color (Cairo expect ARGB, no needs for byteswap) (c) Petrol. Also, rebuild with newer libWebP v1.1.0 -- major PNG decoding changes: 1). Odyssey compiled with 1.6.37 instead of old 1.2.50 libpng + necessary changes in Odyssey's code 2). added APNG (animated png) support. Code taken from today's WebKit source code and adapted to our version + added .apng mime-type as well. Changes applied: https://trac.webkit.org/changeset/181553/webkit https://trac.webkit.org/changeset/194503/webkit For test visit https://en.wikipedia.org/wiki/APNG and see if animation works -- Ouch! The current version of Cairo we use till now didn't use Semaphores as expected, but pthreads instead ! Removed pthreads usage in favor of os4 semaphores. That theoretically can bring some speed and may have some impact on MediaPlayer. Also recompiled Cairo with libpng16 as well (but it still old version of cairo, some more work should be done before updating it) -- actual build dates for $VER: everywhere (version, aboutbox, and about.html) -- fix "download-font" script by adding --no-check-certificates to wget (c) khayoz
All updates are on github, so if morphos guys will be not that stubborn they can just copy+paste apng related parts. Probabaly if they have issues with webp then our fix can fits into to. Updated not only odyssey's code, but also SDK (new cairo lib/includes, new libpng lib/includes), so if you will build things from github, then SDK update are must and whole rebuild of whole Odyssey from scratch are must 100% (as it use cairo in all the places, and if you will keep old objects compiled with old cairo includes, it will then bring all sort of bugs). So fresh full recompilation with whole update of SDK are must.
Just did some quick testing of APNG's and webm videos. All worked quite well. Did a google search on animated PNG graphics and play many of the APNG files that came up in the search without any problems.
Found a couple of websites to test the embedded webm playback. The good old Buck Bunny embedded webm video can be found here:https://www.webmfiles.org/demo-files/
360p plays great with the X1000. 480p starts to struggle a bit. The Webm videos I tried so far seem to work great! This sitle also allows switching to vp9 format and they play but they are much more prossesor intensive so the sound can get lost.
Can i just replace the new version over the older one?
I tried that and received a lot of crashes. I then kept beta3 on its original directory and copied the key preferences files over from beta2 and it runs very stable. Even playing a lot of videos.
@joeled Better fresh install all the time, that will save us from all kind of possible issues which may happens because of different lbraries and their new/old config files. Different fontconfig caches, .db files, fonts libs, and co, everything can be cause of issues. So fresh install is must.
@ktadd In case with beta3 there was added new filetype/mimetype, so if you has for example some manually added things in prefs, then new binary may cause issues yep, as things shifts/changes. Better all the time fresh install for sure.
Would it be possible to upload your RC's to github instead? That way it would be in it s central place and people wouldn't have to remember your personal webspace
@raziel Those "betas" just for ppls in that thread, nothing which will be placed anywhere after "r5" will be ready. I just made them so those who in interest can just test it if nothing got broken in process.
You don't need to remember any place where is it, it only just for easy download (and from amiga itself too, as from github it will be hard to download from our browsers). Once r5 will be ready, then it will be on our central "os4depot" place :)
@ kas1e Thanks for the new beta 03 it's getting faster. Now the links pointing to Youtube on sites like EAB etc. also work well.
I wanted to ask if it was possible in some way, to add spoffing to the following user-agent: Mozilla / 5.0 (Nintendo WiiU) AppleWebKit / 534.52 (KTTML, like Gecko) NX / {Version No} NintendoBrowser / {Version No} .US
Or even more recent
In my example I can modify the user-agent with the following line to the user-startup
; BEGIN OWB SETENV OWB_USER_AGENT "Mozilla/5.0 (Nintendo WiiU) AppleWebKit/534.52 (KTTML, like Gecko) NX/{Version No} NintendoBrowser/{Version No}.US" ; END OWB
but with this Beta 03 version it seems to slow down the browser, therefore I had to eliminate it from the user-startup.
Currently in my experience it seems the fastest user agent for Odyssey.
I'm probably wrong, but it seems to be faster for the 4.1FE update1.
Thanks for a possible reply.
Do you consider my comment unnecessary if it is not in line with the current project.
@Raziel Right, its comments didnt works in github's tickets, just messed it a bit with downloads. Maybe i can use github later too for downloads indeed.
@white So you mean add latest Nintendo WiiU user-agent ? ok, will do so, one more agent should't do any harm.
Now i start to wonder which user-agent you spoof with?
I can (also) comment to existing github bug tracker items just fine.
I cannot 1) create new bug tracker items (i can reach the items "editor window", but the "Post" button never appears). Have to use a PC for that. 2) edit my own comments/items. The "Edit" option (from the "..." menu) does nothing on a mouse click. 3) add smileys/reactions to posts (well, i can, but the smilies to choose from aren't displayed - they are shown as rectangles/boxes, so i don't know what i'm choosing). Seems to be some kind of unsupported gfx format.
The above are all, as far as i understand, unsupported features in css/html/javascript, so nothing we can do about, unless we get a newer webkit version (i think)
I m spoofing with IPad 13.2.3 for now, since all the others have problems with one or more sites. Even this one i have to switch back to Odyssey, if i want to attach something to an email on my providers site...
But the Dashboard of Transifex website still not, apparently it doesn't work in all versions now, including the public OWB on OS4Depot Probably they did some changes very recently and that changes are no more compatible with our old webkit .. don't know really