kod wrote:bandwidth is never released - so this tells me that's still being served somewhere in the background?
Your debug.log shows this to be the case, a new instance of rtmpdump is launching every time you click an item but failing to be killed when you press stop. Each instance (judging from its messages) seems to be healthy, connected to espn, and streaming to pms continuously, even after pressing stop. Windows Task manager should show multiple instances of rtmpdump.exe running, which is of course why your bandwidth is getting eaten up (you can kill the process there by right-click, btw, instead of shutting down pms). Failure to kill a subprocess is a longstanding issue with pms (probably rooted in java itself), so I don't know of any fixes. But I agree this is all a separate issue.
The logs seem otherwise normal, and why you don't see anything isn't clear. As I mentioned in my case, whether in ubuntu or Windows, all three methods (espn.com/XBMC/Jumpy) either work or fail together. I've tested multiple times over the past 2 days and haven't yet had a session where jumpy behaved differently from the other two. Once espn.com bumped me claiming my ISP wasn't authorized (I'm on fios as opposed to fios-tv) but later on things were working normally again. I still think that the flakiness is on the espn.com side, they may be tinkering with authorization, etc.
The other possibility is that the underlying rtmpdump/librtmp support, which is different between XBMC and SHB is somehow causing this, but it seems unlikely since I tested on SHB-43 same as you (i.e. we're both using the same version of rtmpdump) and it works for me (intermittently anyway).
The only suggestion I can offer is to comment out rtmpdump.force in PMS.conf with a '#' at the start of the line:
- Code: Select all
#rtmpdump.force = true
in which case ffmpeg (with its own built-in librtmp) will get launched instead of standalone rtmpdump and may give you different results bandwidth-wise at least.
kod wrote:took two snap shots
Redundant unless you also restart pms, since the second set of logs include everything in the first set

.
EDIT 1: Another longshot, but you could also try this
- replace extras\bin\rtmpdump.exe with rtmpdump.exe from here.
- then enable rtmpdump.force in PMS.conf again and restart pms.
EDIT 2: It's also possible to make PMS-SHB's librtmp support identical to xbmc:
- first make a backup copy of extras\\bin to simplify undoing this later.
- replace extras\bin\rtmpdump.exe with the one in here:
- copy librtmp.dll, libeay32.dll, libssl32.dll from XBMC\system to extras\bin (this will overwrite the existing libeay32.dll).
- then enable rtmpdump.force in PMS.conf again and restart pms.