So far, all of your suggestions work great.

The only thing I do notice is something that is quite nitpciky. So, I have videos that open with Emotion and I have an RX 560 and no matter what the quality of the video, every so often there is a .3 / .5s delay in video - a very slight freeze that is hardly noticeable. I am wondering if anyone else sees this?

I repeat: it is nitpicky.

I also see it in vidoes that are played over my NAS share or even if the videos are copied to a local partition and played.

My version of Emotion is:

I also have Frameskip set to Disabled.
===

This seems to be something specific to Emotion. When I use DVPlayer I do not see this hardly-noticeable freeze.

Has anyone tried opening YouTube (etc) videos directly with DVPlayer?

@DigitalDesings
Anyway to grab hold of one of the backgrounds right now? Perhaps with an annoying watermark that would only be removed with purchase? I like the BG.

@Maijestro
@HunoPPC
I am interested in this exact error. I am attempting a game port where I have the same error.

Since this is coming from HunoPPC I am surprised to see this error because I was always under the impression that he was using GCC 4 - but this must not be the case for this game.

This error happens due to GCC 8 and above. In that version, different threading methods were created such as "single" and "native". The whole point of building with the flag "athread=native" means that when you finally link your binary file, "gthr-native.o" (I cannot remember exactly the name of the object file) gets linked in and provides the selected threading implementation. This is never an issue with static linking. The issue comes when there is a binary that relies on something that requires those native methods and when they are linked dynamically. There is no such "gthr-native.so" file.

I am wondering if you found a work-around?

For anyone wanting to view this with limited browser capability:

http://tellusregio.duckdns.org:32470/ ... eme%20pack%20brochure.png

Possible to have something more appropriate instead of MS share point?

Thanks.

===

EDIT: See http://tellusregio.duckdns.org:32470/ ... eme%20pack%20brochure.png

@Maijestro

Did you get it working?

This is the most Amigaworld topic that I have come across yet.

Can you report an issue with a small reproducible at https://github.com/AmigaLabs/adtools/issues.

I thought newlib did have that. But I cannot remember. If it does, you can just call the newlib one ?

Might be worth noting that it seems to be appending the same path multiple times.

It seems that way, exactly.

@MickJT

It is fixed, as described later on in the post. The library in Odyssey must match the one in Emotion.

Strange. I follwed the guide.

1. Reboot computer. Directly run:


This works.

2. Reboot computer. Open Odyssey and go to "https://aiostreams.amiga-projects.net/invidious/search" and search for the same video. Right click, go to Video (which is the label I gave)

This results in an "IO error" from Emotion.

If I do 1. then 2. then 2. works.

Here are my settings:
https://freeimage.host/i/d82bTS1

===

Why am I getting an "IO Error"?

===

As for the above question directly above... I notice:
https://freeimage.host/i/d83TCzJ

I copied the avformat2.library to the Odyssey/LIBS directory and now it seems to work. The picture shows the situation before I copied the library over.

Thanks. I updated my initial post, linking to the subsequent two posts. If you can keep them up-to-date, that would be grand.

TL;DR : https://www.amigans.net/modules/publisher/item.php?itemid=26

===
All the following is before the articles section was established at Amigans.net.
===
Welcome to the definitive thread on how to achieve streaming videos on the internet using our AmigaOne machines. I just had the idea to create this thread that is hopefully easily find-able; others have already done the hard work - from the people talking about how to configure it, to the people who have provided the tools to make it all work. To those, thank you lots.

TL;DR:
See: https://www.amigans.net/modules/newbb/ ... id=150331#forumpost150331

And,

See: https://www.amigans.net/modules/newbb/ ... id=150332#forumpost150332

===

Issues:

IO Error?
See: https://www.amigans.net/modules/newbb/ ... id=150345#forumpost150345

===

I will try to keep this up-to-date.

Right. Because you had one of the assumed libs.

The installation script makes assumptions about the libraries it can find on your system, otherwise it just fails in such a manor. The error message is hardly useful either - but that is probably from the AmiUpdate tools.

I had to manually copy over a library file into Libs/AmiSSL to "trick" the installer into upgrading to 5.17.

I had to copy any one of those libraries to the directory that it failed to open.

On my X1000, the update of AmiSSL 5.17 fails. The log message says:

I see in Snoopy a successful opening of the amisslmaster.library and then constant failures when trying to open further libraries and find resident:

I am not sure if the above is the source of the failure.

===

This is also leading to a failure to update to IBrowse 30.8 - since it appears to be trying to do the same thing with AmiSSL in the background when trying to update that.

Click the link again at the top. Switched ports.

@MartinW
I have a fairly stable 2.7.18 version right now - which is the last version; including argparse and collections as expected.

I would like to introduce a blog about using my AmigaOne as my daily driver.
rjd324's AmigaOne Daily Driver Blog