@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
@all Question : should we have by default in prefs/media all options being set to ON, instead as it now, when only fastseeking and mp4 is enabled ?
Those options when off, mean that when you click on those formats, they didn't plays in browser but bring you save-as requester to download it instead. But imho, the other way around expected to be defaul : everything enabled, and if one wish, he disable it.
So question, should i just enable them all by default ?
Question : should we have by default in prefs/media all options being set to ON
I vote all on since they seem to be working well. Are there issues on slower systems than the X1000 or X5000? People with slower systems might answer differently if they have issues.
@ktadd But then, if you visit a page with video, you probabaly want to watch it ? And without let's say enabled webm, or ogg, you will have no ability to do so. But if you didn't visit those video pages, then it does not matter if things for media on or off, it will be the same by speed of odyssey usage.
In end, those options still will be there of course, and anyone will have a wish to not have video/audio played in browser can disable it easyly.
I just fear, some ppls unpack it, run, and then just didn't have working video/audio in some parts think "damn crap, odyssey can't play them", and they surely will not thing that to have working video/audio, they need to enabled those options (which in all other browsers everywhere just default thing).
@ktadd Also what make me curious : i tested video of webp which you point out on (that with Lava one), and there i can choice any format : webp, vp8 and vp9 too, and all works. But in prefs/media we have string "WebM (VP8) support", but then , should't it be "WebP (VP8,VP9) support" instead ?
Also what make me curious : i tested video of webp which you point out on (that with Lava one), and there i can choice any format : webp, vp8 and vp9 too, and all works. But in prefs/media we have string "WebM (VP8) support", but then , should't it be "WebP (VP8,VP9) support" instead ?
VP9 Codec is the successor to VP8 and was released in 2017. Since we can play it, go ahead and add it.
If it supports "new" webp modes, maybe due 'cos you updated webp support, just changing the string in catalog/cd/ct to "WebP (VP8,VP9) support" will be nice.
I tried yotube on my SAM460ex it crawls, but doesn't freeze/crash as on your system, I'm using bultin sound sm502 (IIRC).
Will try yhat web page with webp video and see what happens.
THX everyone testing and kas1e to take time to update Odyssey, thx!!!!
Found a good HTML5 Video/Audio test page with many different containers formats and video/audio codecs. Says it's mainly for Crome and Firefox so spoofing as those might help. Webm also supports a newer codec AV1 but we are not able to play it. You might even get a crash while trying to.
Probably for you localisation in OS are broken, and Mar translate to some Tue, if that Tue dind't mean Mar in italian
Right, abbreviation of the letters for the day and the name of the month are the same in italian, also the order of the month/number of day is inverted in english compared to what it will be in italian so this probably can lead to some confusion :)
What wrong about reusing the old but very standard scheme for the date ? like: 16.03.2020
What wrong about reusing the old but very standard scheme for the date ?
That just need properly done stuff: need to create version.c , which will be always compiled does not matter if other files touched or not (so compilation date will be taken from every compile) , and that in turn mean needs to change a bit CMakefiles and some other stuff so makefiles for odyssey (at least for the amiga parts) will be generated with that force-to-compile version.c file with necessary flag to provide date.
That all easy, just boring stuff which can be done later, and instead i just use inbuild __DATE__ macro of GCC which have that format you see now