TheBoxMan Wrote:I might actually test and tweak this tomorrow to see if I can do it
XBMC to XBMC on *different* xboxes (I have three in my house).
I.e. one xbox streaming it to another.
I'm sure the problem will likely be, as you've suggested, entirely related to running both on the xbox.
XBMC to another XBMC will work fine.
There's actually more to the problem than I described - it's more about calling the stream from within the script. If I autoexec the server, I can then manually add the correct URL to the playlist, and XBMC will play it. However, if I try to play the exact same URL from within my frontend script, the server stops accept()ing connections until the play attempt is cancelled.
Weirder, if I have say, the search dialog up, the server stops accepting connections too, until the search dialog is closed. It's like certain dialogs (including the progress dialog XBMC launches at the start of a stream) block the server script's accept() call.
I'm starting to think I've missed some close() calls, as XBMC makes half a dozen GET and HEAD requests when it starts streaming an MP4 (it grabs the very end of the file in one of them) and the first couple of requests usually succeed, and only then does it block.
TheBoxMan Wrote:Would it potentially be helpful to have the script running the server call a plugin which tries to stream from the xbox? (that's to say the script isn't sreaming from itself) or is the problem likely to still extant due to the fact that it's using the same python interpreter??
Same difference. I've tried both with the exact same results (adding server to autoexec.py versus just starting it from the script)
I'm not sure how XBMC forks off Python processes, so that could well be an element of this issue given that the problem is most obvious when running the server script and the frontend script simultaneously.