[...] I have no idea of the technical details [...]
The channel and service use a different (but existing) hostname (www.apple.com) to do the requests and we're in luck that this same server also serves content for trailers.apple.com. By setting the HTTP 'Host' header we tell the server that we are visiting trailers.apple.com, even though we use www as domain/for DNS.
The channel and service use a different (but existing) hostname (www.apple.com) to do the requests and we're in luck that this same server also serves content for trailers.apple.com. By setting the HTTP 'Host' header we tell the server that we are visiting trailers.apple.com, even though we use www as domain/for DNS.
Yeah Roidy Tom about two seconds of looking at the code to figure out what you had done :)
It is one of those things that is "obvious" AFTER the fact, but for now still a little sprinkle of magic ;)
It's great to have AMT back but is anyone else having buffering issues on this channel? It loads the first 6 seconds fast and then plays, buffers, plays, buffers, plays, buffers..... to the end.
This is on 1 Gbps wired network with 1 Gbps fiber access. No other channel has this issue.
It's great to have AMT back but is anyone else having buffering issues on this channel? It loads the first 6 seconds fast and then plays, buffers, plays, buffers, plays, buffers..... to the end.
This is on 1 Gbps wired network with 1 Gbps fiber access. No other channel has this issue.
No issues here.
If you are getting buffering change your DNS in settings.cfg from 8.8.8.8 to your ISP's.
Using Google does not effect most users but it does confuse content delivery networks as to your location. It can lead to you being server content from the other side of the globe rather than locally, being on a 1TB connection will not help you if you have crappy routes between you an Akamai in the USA.
Thanks for the suggestion but that produces the same result as using 8.8.8.8. The odd thing is that it does not happen on CNET, Khan, Twit, Nerdist, Reddit, etc., channels that are all coming from the US to me here in Japan. It is only the Apple Movie Trailers where the buffering issue happens.
No issues here.
If you are getting buffering change your DNS in settings.cfg from 8.8.8.8 to your ISP's.
Using Google does not effect most users but it does confuse content delivery networks as to your location. It can lead to you being server content from the other side of the globe rather than locally, being on a 1TB connection will not help you if you have crappy routes between you an Akamai in the USA.
Just another data point—when I play the same trailer on the Mac using PMS 9.8.4 beta, the buffering occurs at the exact same points as when played on the Apple TV2 (12 s, 43 s, 1:23 s in the case of Gravity trailer 2).
Not sure what to deduce from that.
Thanks for the suggestion but that produces the same result as using 8.8.8.8. The odd thing is that it does not happen on CNET, Khan, Twit, Nerdist, Reddit, etc., channels that are all coming from the US to me here in Japan. It is only the Apple Movie Trailers where the buffering issue happens.
Has anyone resolved this for osx server running its own WebSerever and DNS ? previously with Trailers running on http requests it was simple. Now I believe you need to setup the web server to redirect port 443 requests to PlexConnect. Should use the generated certificate I guess?
I should mention that PlexConnect is running on Mountain Lion Server with DNS and Web Server.
