(Solutions only) XM or Sirius Login issue - error: unable to connect to login site.

Quote:

---

Originally Posted by db220

I'm trying to run the xm tuner. I get it loaded and it logs in but then I get a looping message that says "A problem occurred while playing your channel. Attempting to retune in 10 seconds" over and over. Has anyone seen this and know how to fix it?

---

Thats the automatic player retune kicking in. It happens if your stream is disconnected for any reason. (XM streams time out after 24 hours or so of continuous playback, player limitations aside.) It was added in XMTuner 0.6. You'll want to investigate why your connection to the stream is being broken.

Quote:

---

Originally Posted by Columbo4Life

Hi everyone,

I have a question regarding the workaround. When I run XMtuner and I'm locked in but don't play a channel it still counts as running the server I guess (it says so in the program window). Now when it tries to fetch a stream through replayAV it only works with the last channel I played (e.g. Shade45 on the corresponding url). Other recordings on other channels won't work and show me the following error:

Incoming stream request for XM60 - THE HIGHWAY
Playing SIRIUS 60 - The Highway
Sirius Internet Radio Error - Unknown Error
Error fetching stream for SIRIUS 60 - THE HIGHWAY

Does anyone have an idea what's wrong or is it just not possible to record another stream than the last played. I think it should be that it fetches every stream since it is running as a service.

Best,
MJ

---

You are correct. The XMTuner Server is running if the counter on the log tab is moving. The player is "extra" in this case. Whenever a request for a stream URL comes in, XMTuner does the fetch. The problem in this case is for some reason XMTuner is not getting back the stream page from SiriusXM. Unknown error is a bit vague, but unfortunately so is the SXM system.

Oh, and there is full documentation on the stream URL format here
http://wiki.xmtuner.net/wiki/XMTuner...erface#Streams
These do not change and are a constant as long as SXM doesn't start changing channel numbers around.

Quote:

---

Originally Posted by CharlieSummers

S
Admittedly I am running the service and not the player application so I can't speak to any possible differences there (the same team programmed both, so other than the abstracted layer that handles the service requirements or player section I can't imagine the programming would be different between the two "flavors"), but I can't duplicate the problem some people here seem to be experiencing even letting the thing sit idle for better than a day and a half, so I can only suggest that the problem is not specifically within XM Tuner or Replay A/V, but rather there's something else at play on a few people's machines that aren't affecting the majority of others.

The one oddity I noticed from the screen dumps is that XM Tuner is losing the stream exactly thirty-seconds after commencing - this doesn't appear "random," at all at least in those screen dumps, but solidly consistent (one instance alone is 31-seconds)...does this happen when just playing back through the XM Tuner player, only when attempting a recording through Replay A/V, or any time?

---

The only difference between XMTuner and the XMTunerService is the lack of the UI elements and therefore all the built-in player functions and so forth. XMTunerService is designed to be used for UPnP players that need background support. There is no back-end code differences, they share the same code - otherwise maintaining both would be painful. This timeout has been reported before but it occurs for some people and I have not been reliably able to reproduce it and track down a cause. It was as if XMTuner itself loses the ability to make connections out. Since Timeout means exactly that, it attempted to connect to SXM and failed to reach a server.

The 30-second issue you're seeing is the default timeout XMTuner has for making a connection. It tries to reach sirius/xmradio.com and waits 30 seconds before it fails out, and you get the follow-up message.

Restarting the service or application has been reported to correct this. Generally XMTuner itself isnt intended to be run for long-periods of time, but there should be no problems doing so. Scripting something to restart the service would work-around the problem - its not an elegant solution though.

Quote:

---

Originally Posted by Kurto2021

it's probably because it doesn't want to record the 60's channel.

I wonder if it may be a 64 bit issue...mine is up and working and it is 32 bit

---

Its not, I've reproduced it, just not reliably, on 64-bit systems, even using a 64-bit version of XMTuner.

Quote:

---

Originally Posted by CharlieSummers

I'm mildly annoyed at XM Tuner myself, but this time because of the goofy way it handles logs. Every time you restart the service (and, I assume, the application, although they are different log files) it wipes out the old data.
(*sigh*)

---

Sorry about that. I'll fix it so it rotates logs in the next version.

Quote:

---

Originally Posted by CharlieSummers

Not really. You log into SiriusXM, then request a stream. That stream comes from Akamai with a completely different URI that contains an authentication "cookie," which gets passed on by XM Tuner to the requester (WMP, Replay A/V, whatever) who then opens it. XM Tuner maintains the connection to SiriusXM, so the next incoming request gets a new akamaistream.net URI complete with new authentication cookie. I assume this is how XM Tuner can allow multiple recordings, or even multiple computers, to play/record different streams..

---

Correct. XMTuner maintains the information about the session and does its best to keep it alive, however, it periodically polls and will notice if its been forced out and relogin needs to occur, "Relogin needed/completed". The logic for this may need to be more robust, but it generally works.

I have been using the xmTuner server workaround with Sirius since introduced with no issues or incidents. I actually kind of like it better as i'm getting clear recordings with no perceptible dropouts. I usually record other non sirius streams so it wasn't too big of an issue to switch. Server is running on an AMD 64 bit PC w/ 4 gig ram. One wish would be that the Server shuts down after "x" mins of non recording. And would activate when the stream was requested.

Quote:

---

Originally Posted by dj_paige

I am not using Windows 7 Firewall. I am using AVG Internet Security firewall, but maybe I should test things out by turning off AVG and turning on Windows 7 firewall.

---

I tried tonight to do an unattended recording using Windows 7 Firewall enabled, after shutting off the AVG Internet Security Firewall. Same results. Could not record, same errors, the XM Tuner Service says operation has timed out. So, I guess the problem is not the specific firewall I am using. Will try again tonight with no router. I am not willing to try doing this with no firewall enabled.

First, let me mention it's nice to see someone involved with XM Tuner development here...it's a little depressing that our discussion here is a bit more...robust...than that on the Sourceforge forum dedicated to XM Tuner, though.

Quote:

---

Originally Posted by psychoticwolf

Generally XMTuner itself isnt intended to be run for long-periods of time, but there should be no problems doing so.

---

Um...one would assume a service would be designed to be run for long periods of time...i.e. the entire time the computer is operating. I know what you meant, though, since XM Tuner really wasn't designed to be a 24/7 adjunct to Replay A/V, instead designed to make it easier to listen to XM or Sirius online at your desk.

Still, the ability for my daughter to listen to country music on her netbook while my wife listens to Doctor Radio on her laptop while I record The Bob Edwards Show in my office is seriously beyond cool, so even if Applian patched Replay A/V tomorrow I'd continue using XM Tuner as the back-end. (Aside: I looked for a "tip jar" to support XM Tuner's development and didn't see one. Pointer would be appreciated.)

Quote:

---

Originally Posted by psychoticwolf

Sorry about that. I'll fix it so it rotates logs in the next version.

---

Heck, I'd be fine with it just "letting it roll," but that would cause no end of grief for the app/service display window, not to mention those who don't routinely clear log files having...issues...with wondering where all the disk space went.

Quote:

---

Originally Posted by jtschinkel

I actually kind of like it better as i'm getting clear recordings with no perceptible dropouts.

---

Really? You're clearly not recording XMPR (133/196); the dropouts are every bit as frequent as they have been, requiring me to manually edit every day's BES to "fix" them. (But then, I'm anal about "complete" shows.) SiriusXM couldn't feed solid data to Akamai if their life depended on it.

Quote:

---

Originally Posted by jtschinkel

One wish would be that the Server shuts down after "x" mins of non recording. And would activate when the stream was requested.

---

If, "the server shut down," it could never reactivate, since nothing would be listening. I think you are suggesting XM Tuner log-out of SiriusXM while continuing to run the server, and log-in as necessary.

Problem I see with that is if you re-loaded the XM Tuner web page, it would have old artist/song/album data, as I assume it would have to log-in to retrieve that data. And that would (depending on usage) cause a boatload of log-in/log-off cycles. But since a developer's here and much better equipped to handle this, I should shut up now.

Quote:

---

Originally Posted by dj_paige

Will try again tonight with no router. I am not willing to try doing this with no firewall enabled.

---

Er, no, certainly not...I wouldn't run without the hardware firewall in the router, frankly. I was musing out loud because of the issues I had with the Windows7 firewall being a bit more...particular...than earlier versions. I also noted that it wasn't likely to be a firewall issue since it did work for 50-some minutes before it died, though, so I probably shouldn't have thought out loud about the firewall.

Okay, I will not run without the router. Another recording failed to start on time today. When I realized it hadn't started on time, I re-started the XMTuner service, but I missed recording over an hour of the show. After 2 years of enjoying Replay A/V and its reliability in recording XM Radio, this is very frustrating. I too am glad that the developer of XMTuner is working on it and commenting.

Perhaps now that Carmelo Anthony has been traded, this will fix the problem. :D