2024-08-16, 03:59 PM
(This post was last modified: 2024-08-16, 04:04 PM by TheDreadPirate. Edited 2 times in total.)
Can you share the full media info for this file? Click the copy button then paste in a code block.
Are you willing to try setting up iPerf on your to see what your actual client-to-client speeds are? The server runs on your Mac, the client on your phone or whatever remote WiFi client.
Your speeds tests may report super high speeds (I'm jealous with my 40Mbps Comcast upload), but something else may be going on. Since it is direct playing, the issue is either the network or the client's ability to play the file. Since it happens on multiple remote clients, that don't have issues locally, that leads me to believe there is something going on with your Internet connection and may not be anything in your control.
I just remembered something. A Canadian user found out that their ISP did do some sort of traffic throttling for video and using a VPN to hide the kind of traffic got around that. Another thing to try.
You can also try setting up a reverse proxy, setting up HTTPS (you can use your DynDNS address for legit certs), and using a non-standard HTTPS port. Sometimes ISPs throttle strictly based on the port. Maybe AT&T is throttling 8096? IDK.
Are you willing to try setting up iPerf on your to see what your actual client-to-client speeds are? The server runs on your Mac, the client on your phone or whatever remote WiFi client.
Your speeds tests may report super high speeds (I'm jealous with my 40Mbps Comcast upload), but something else may be going on. Since it is direct playing, the issue is either the network or the client's ability to play the file. Since it happens on multiple remote clients, that don't have issues locally, that leads me to believe there is something going on with your Internet connection and may not be anything in your control.
I just remembered something. A Canadian user found out that their ISP did do some sort of traffic throttling for video and using a VPN to hide the kind of traffic got around that. Another thing to try.
You can also try setting up a reverse proxy, setting up HTTPS (you can use your DynDNS address for legit certs), and using a non-standard HTTPS port. Sometimes ISPs throttle strictly based on the port. Maybe AT&T is throttling 8096? IDK.