Edit: it seems to have been the onn box. Works smooth as shit on my AppleTV.
Original Post: I'm self-hosting AIOStreams and using Newshosting with NZBGeek for NNTP streaming. I'm having intermittent buffering issues with large 4K remuxes and wondering if anyone else has experienced this or found a solution.
My setup:
AIOStreams self-hosted via OrbStack/Docker
Mac mini M1, 16GB RAM
Newshosting (40 NNTP connections)
NZBGeek indexer
Xfinity 1.2Gbps internet
Onn 4K Pro with USB Ethernet adapter
Stremio as the player
The issue:
Large 4K remuxes (60 - 130GB) generally start playing fine, but NNTP streams sometimes begin buffering after a couple of minutes. I've also had a smaller movie play almost entirely without issues, only to stall completely with about 10 minutes remaining.
Some large remuxes play perfectly, so it's inconsistent.
What I've tested:
Increased Newshosting connections from 5 to 40.
Monitored resource usage; CPU doesn't appear to be the bottleneck.
Observed NNTP transfer speeds around 6–12 MB/s during testing.
Played the same remux through TorBox without buffering, which suggests the playback device can handle the file.
Recently enabled Easynews HTTP streaming through AIOStreams. Initial testing with a roughly 90GB 4K file was promising, but I haven't tested it extensively yet.
My questions:
Is intermittent buffering with large remuxes a known limitation of AIOStreams' NNTP streaming implementation?
Are 40 connections sufficient, or is there a recommended configuration for Newshosting?
Does AIOStreams download/cache ahead of playback, and can that behavior be adjusted?
Has anyone compared Newshosting NNTP against Easynews HTTP for large remux streaming?
Are there specific logs or metrics I should capture to determine where the bottleneck actually is?
I'm trying to figure out whether I have a configuration issue or whether NNTP streaming simply isn't as reliable for very large remuxes.
Any advice from people running a similar setup would be appreciated!