Jamcast

Hi Jambo,

Thanks for stopping by to report this. Sorry for your troubles.

I wonder if there's something about the tracks that it is stopping at that is causing the issue? Can you confirm an consistencies with when playback stops -- does it always stop at the same song(s)?

If you think there's a trend there, note what songs are problematic and paste your medialog.txt to http://pastebin.org and share the link here so I can take a look at what's going on. The Soundbridge isn't a fussy device so I'm assuming right now that this is going to be media-related.

Thanks!

Sorry for the delay in getting back to you, and thanks for your attention to this problem. Jamcast is working pretty well, but regularly seems unable to locate the next song in a list. This does not appear to the the song file itself, as I can directly select the song from a list and it will play through the soundbridge. Per your suggestion, I've pasted an excerpt, with an editorial comment at the point I most recently experienced the problem, at the following link.

http://pastebin.org/66772

Thanks again for your help!

-Jambo

Finally, I've posted and excerpt from the upnplog that shows activity between 18:34 and 18:36, when I most recently encountered the problem. Thanks!


http://pastebin.org/66782

Hi Scott. Checking the Windows event log, I see that Jamcast throws the following warning message about once or twice every minute while I'm streaming music:

http://pastebin.org/67581

Also, very near in time to the song skipping problem I've described, I receive the following errors on the Windows Event Log from Perflib. I don't know if it's Jamcast related, but I thought I send it along, just in case.

http://pastebin.org/67584

Hey Jambo,

How about the log message here: http://pastebin.org/67581

Do you see any correlation between that error and the song skipping behavior? This error message I believe would cause exactly what we're seeing.

What device is at 10.0.0.1, is that a router? Jamcast is attempting to acquire its MAC address via an ARP request and is receiving the following error:



Possible network configuration issue?

Thanks!

Awesome Jambo, thanks for reporting back. Don't let Jamcast off the hook so easy (although I appreciate it!), but in my opinion operations shouldn't be so heavily tied to MAC address resolution. There was a point in the past where the MAC address was important to Jamcast in terms of device identification, but that has changed over time as MAC addy's are no good for uniqueness in more advanced networking configurations since you can't resolve a device's MAC address when it's more than 1 hop away.

Anyhow, I'm really glad you got it worked out. Please stop by if you have any further questions.

Thanks!

Hey Jambo,

Is it the same error, with the same IP address?

Check the upnplog.txt for references to that IP, see if you can identify it.

Does that IP even fall within your subnet, or is it totally unexpected?

Let's see if we can't attack it from both angles, I want to make sure it's not a Jamcast bug. Thinking about it more, the error makes sense only if it's the Soundbridge; if the device at that endpoint is unrelated to the Soundbridge, I'd expect you to still see errors in the event log but playback would be uninterrupted.


Thanks!

Hi Jambo,

Let's circle back real quick and make sure we're still going down a reasonable path. Are you still getting the same error messages in the event log regarding the same IP address, and are they coinciding with the playback stops?

If you do a ipconfig /all from the command line, are there perhaps any interfaces that you weren't aware of that would fall into that 10.x.x.x subnet?

Also, if you could paste your entire medialog.txt to http://pastebin.org, I'll sift thru that for clues.

I'd really like to figure this one out, so I'm not giving up yet.

Thanks!

Hi Jambo,

Thanks for providing these logfiles. I see no reference to that 10. address anywhere. I'm embarrassed to admit that I'm pretty baffled by this issue; it makes no sense -- where is that IP coming from?

This whole problem is because Jamcast can't resolve the MAC address, which as I mentioned earlier is not as important as it once was. So, I'm going to made some adjustments to code so this problem doesn't manifest itself into a playback issue.

Hang in there, I should have a new build out in a couple of days with this change. I might run it by you first before I post it, if you don't mind...

Thanks!

Hey Jambo,

You're welcome. I've got that change implemented and will get a build over to you later today.

I agree with you, I went back thru this thread last night in its entirety and from what you've reported I don't see much correlation either. Nonetheless, we might as well try this fix and see if it reveals new information. If nothing else, we may discover more about where the 10.0.0.1 address is coming from.

If you've got some time, you might look more into the possibility of intermittent network drops. I acknowledge what you said regarding Firefly working fine, but am trying to be thorough. A decent preliminary test would be to ping the Soundbridge from the PC while Jamcast is running, and watching for communication problems like so:



Another thing you can try is a Wireshark capture (wireshark.org) during Jamcast playback, which will capture the problem in a network trace. If you're feeling spry, this is a really good diagnostic and you can save off the capture file and email it to me for analysis. That capture would show us whether or not there's a request for the next track coming from the Soundbridge and how/if Jamcast is responding. Remember, we never saw requests in the medialog.txt for those problematic tracks, which to me means either the request never happened or Jamcast encountered a fairly obscure problem before it was able to write to the log.

The other thing as you mentioned is that Firefly doesn't use the same protocol as Jamcast, which leaves open the (albeit slim) possibility that the Soundbridge has an issue, in which case I'd recommend for the sake of being thorough doing a factory reset on the device and bringing the firmware updates back up to current (I believe this is possible on the Soundbridge).

Anyhow, thanks for your persistence and hopefully in the end we'll square this away.

Thanks!