Odyssey 1.23 progress: r5 RC2

After having played a YouTube video with Odyssey

I can confirm this weird behaviour with Emotion after having played a video with Odyssey : sometimes Emotion crashes when trying to play the video and sometimes after having played it.

Along with the GrimReaper, I got an Emotion window with this :



And the associated crashlog : https://amiga-ng.org/resources/CrashLo ... d_2020-06-05_04-15-33.txt

@Samo
Quote:

If you remember there already ticket for http://muidev.de/ticket/401. You even wrote something in as well.

@K-L
It looks like something weird happen with ffmpeg shared libraries. Most possible it Odyssey trash something which cause that, or it can be something with ffmpeg libs itself.

But sadly if it just "sometime", we then can't normally debug it :(

@Kas1e

Not sometimes. It took me some time to understand why Emotion was crashing on a regular basis and sometimes not (white's message put me on the right way to the problem since he has the same behaviour).

It is crashing if I have been using Odyssey's media player just before using Emotion.

It can be reproduced each time.

@kas1e

Right, i was completely forgot it .. it was 18 month ago
So it means that one was reproducible even in old version 1.23 on os4depot

@Thread

Could someone check YouTube with Odyssey (to be sure I am not the only one with the proble)? It seems the page cannot be displayed anymore (doesn't work either with Odyssey 1.26 on MorphOS).

Google must have changed something.

When trying to play a video directly from Google, YouTube video is played but there is no possibility to switch to fullscreen.

@K-L
@All
I have tried Odyssey (OS4.1FE) beta 07
If I close the Odyssey window when I watch a video on youtube and leave the requester open, the Emotion player works perfectly.
But if I completely exit Odyssey the Emotion player crashes
I hope it will be useful in some way, Thanks again for the work dedicated to Odyssey.

I leave the video if it can be useful:
https://www.youtube.com/watch?v=v_aLqSFvFu4

@K-L

Seems so

Try to Spoof as IPAD and see if it works.

@Thread

Well, now that we have fullscreen enabled for YouTube video, YouTube doesn't work anymore with Odyssey (no matter what you spoof with).

Too bad.

And even if you acces a video directly with its link you won't be able to switch to fullscreen and enjoy acceleration.

Edited : ah, you can switch to fullscreen if you access a video directly. You just have to right click on the vido and select "switch to fullscreen".

@K-L
Quote:
Youtube still works fine for me using Odyssey Beta 07. Sometimes it takes me to a screen that says your browser is outdated and will not be supported soon but I can click on a continue button and it takes me to the YouTube page. Has a warning at the top about outdated browser but works fine. Videos play in full screen fine as well.

Maybe try deleting your YouTube Cookies before loading the page. When playing with spoofing I have ended up with things not working and YouTube seems to use a cookies to remember your settings so things won't work again until you clear the cookies. Mine works with the user agent set to Odyssey.

@All
It just time come and youtube start their changes they says about months ago. Just not in all countries changes immediately take place, but soon or later everyone will have the same issues K-L have.

What we can do there currently, it's to find out ways how to workaround it for future. Maybe some new youtube scripts need to be written which can handle that issues, etc. They surely should't abandon iPad, etc support too soon, so probabaly we firstly need to find correct spoofing and then maybe some new youtube scripts.

@kas1e

Actually, there seems to be a JS error when loading YouTube' site. I don't think spoofing will help

@K-L
Youtube go more modern route not for every device. At least not for IPAD (mean it use some older JS route). That why spoofing will help at least to render something.

@kas1e
Hello there. When you compiled Odyssey with gcc-10 did you have some issues like below?

@Walkero
Of course, I wrote about them in another thread as "enum" warnings. But as it just a warning, not a big deal. At least Odyssey compiled with GCC 10.1.0 works the same good as with 8.4.0.

I hope there will be some other small fixes in Odyssey pretty soon, one from Javier (in the spoofing area), and then can release beta08 compiled with gcc10

Thanks for your reply. I just wanted to be sure that you had that as well, and that's not a problem of my setup.
In my case, though, they are counted as errors and not warnings.

Also, do you plan to compile it against latest MUI?


Update:
I did a few changes that remove those issues, although I am not sure yet for the impact:

line 202 at /odyssey-r155188-1.23/Source/WebKit/OrigynWebBrowser/Api/MorphOS/mui.h

change to



line 120 at /odyssey-r155188-1.23/Source/WebKit/OrigynWebBrowser/Api/MorphOS/classes.h

change to



line 202 at /odyssey-r155188-1.23/Source/WebKit/OrigynWebBrowser/Api/MorphOS/mui.h

change to



With the above changes I managed to compile Odyssey just fine, and seems to work so far I tested them. But as I said, as I am not that familiar with the code, those changes need your review.

@walkero
Quote:

Already, over latest mui, over latest pthreads, over latest gcc and over latest newlib :)

Thanks Roman for the great work. Keep it up.

@kas1e

Lot of time passed since beta 7, any chance in finishing to update the remaining dependencies and then try porting OWB 1.25 ?
Even just updating the dependencies would be cool, some sites start asking for new certs etc ..

Updating root CA certs doesn't require updating the source code, heck it doesn't even require you to rebuild the app from source.

@samo79
@kas1e

I'd like to know too.

My email provider changed its website and now I'm not able to access it with Odyssey anymore.

Since there aren't any actively developed Mail apps anymore either it's going to be complicated to use email from the miggy.