[sbthomas]

The paste seems to be marked as private. There should be an option to make it public.

[arztonyou]

Sorry about that. It should work now.


http://pastebin.com/dY2nJ9jt

[hoopsdavis]

Does http stream to other kodi setups throughout the house and would the remote kodi show channels in the guide?

If so, how do I go about setting this up?

[krustyreturns]

@arztonyou, sorry for the delay. I checked the log you posted and I don't see any messages there where you try to start a live stream. Maybe try it again? Restart swmc, then try to play a live or recorded show with your firetv and http streaming enabled.

[krustyreturns]

@hoopsdavis,

Enabling http for streaming with kodi, is only an alternative to sending the stream data by using shared network folders (the default case). Whether the channels show up (channel list or epg) is separate; this data is sent over a socket connection between the kodi addon and serverwmc.

I think I need more info on what the problem is you are trying to solve.

[arztonyou]

Krusty,

I didn't see anything either in the previous log to indicate a live stream, so I've done some further testing with my FireTV stick and live tv. I'm going to paste a few relevant snippets from kodi logs of the fireTV stick. It seems like it might either be a setting that I need to change in setting up MXPlayer or a communication issue between kodi on the stick and serverwmc. If you want a full kodi log or another serverwmc log, let me know.

Without MXPlayer, I can successfully play the http: stream (but with audio/video sync issues), but with MXPlayer enabled, it seems to get stuck on the pvr:\\ listing for the channel.


http://pastebin.com/WMg3jC3d

[hoopsdavis]

@hoopsdavis,

Enabling http for streaming with kodi, is only an alternative to sending the stream data by using shared network folders (the default case). Whether the channels show up (channel list or epg) is separate; this data is sent over a socket connection between the kodi addon and serverwmc.

I think I need more info on what the problem is you are trying to solve.

The reason I'm asking, the solution I had before with sending the stream using the shared folders and having 2 pvr.wmc addons on the remote device. Using the 2 pvr.wmc I was able to have the local digital channels and the remote QAM channels with the 2nd pvr.wmc addon enabled and configured.

Now I'm unable get 2 pvr.wmc addons to enable.

[krustyreturns]

@arztonyou I really think this is a kodi thing too. All we do is send the http urls for streaming to kodi (in http mode) we have no control over what kodi hands to the player.

@hoopsdavis,

What changed when the two addons quit loading? From your previous post it seemed that you thought the new version of swmc caused it (which would be a head scratcher if that's true).

[scarecrow420]

Loading multiple pvr addons in XBMC is always a but sketchy, there is a timing gap where if only 1 addon has loaded Kodi doesn't wait for the other, so perhaps you just have to try starting up a number of times until you jag having both addons loaded?

[hoopsdavis]

@hoopsdavis,

What changed when the two addons quit loading? From your previous post it seemed that you thought the new version of swmc caused it (which would be a head scratcher if that's true).

Krusty, the only thing that's changes was the addition of the latest addon.

Once I upgraded to the latest ServerWMC-1199, I was unable to get the remote streaming to work.
This is the streaming I've used in the past, you and I worked on and off for days getting this working properly.

On my remote HTPC I've run two pwvr-wmc addons, one providing channels from the local tuner and the other providing the OTA channels from the Remote HTPC.
It seems since the latest version of ServerWMC, I'm unable to get the remote streams to work. I reverted back to the previous build of ServerWMC.

I haven't worked on it much, but I'll look more into it this weekend.

[krustyreturns]

Interesting, so reverting back to the old serverwmc was ALL you had to do to get your two serverwmc setup to work again? Not sure how I managed to mess that up (but I don't doubt it's true). When you have time to work on it, send me your 1199 swmc log after a failed attempt at starting a live stream in this configuration.

[heheitme]

It enables swmc to send all the data to the client using a http urls rather than relying on network shares, this was required to support plex clients. I also experimented using this mode with kodi, and it works, but streams are not seek-able currently and FF and RW don't work, but I think we can address this in a later version. Although net shares work fine, so I am not sure what the point is other than it's interesting.

Also it obviously enables swmc to serve web pages, so I made a first cut at having it serve a simple status page for swmc (similar to the status tab in the app). This enables remote machines to check the state of swmc without having to login to the server machine. If there are other web page ideas people would like to see, let me know. Like timers, recordings, or a way to schedule recordings, etc.

Lastly it enables players like vlc (actually maybe only vlc, since that's all I tried) to remotely watch recorded tv and live tv using urls. I don't know whether this is useful either, but its cool that it works.

How do you get it to play longer than a few minutes with VLC? when I put in the URL in VLC it starts playing the channel and works great until I see this in the logs:

PurgeAndUpdateClients> 'testClient^' disconnecting, due to inactivity.

Is there another parameter or something I need to add in order for ServerWMC to not think I have disconnected?

VLC Network URL: http://WMCPC:9180/serverwmc.stream/Strea...ID=1305743

[krustyreturns]

Good catch, that's might be a bug when using vlc at the player - I need to review the code to know for sure. In the meantime, a workaround will be to change the interval swmc uses to check for inactive clients. Change this setting in serverwmc's settings:

<ClientInactiveIntervalMIN>10</ClientInactiveIntervalMIN>

by default it is 10 minutes. Set it for something much larger and this problem should go away (until the new interval runs out). You'll need to restart swmc for the change to take effect.

[heheitme]

Thank you so much!! This is awesome!!

[krustyreturns]

You're welcome. You also might find the command StreamChannelNumber easier to use than StreamChannelByID, since it lets you specify the channel number rather then the cumbersome wmc channel ID. The syntax is:

http://WMCPC:9180/serverwmc.stream/Strea...Number=812

substitute '812' for the channel you want