Use Channels-DVR as a tuner for Emby

[racameron]

Which client is that? Guide2Go?

[Edwin_Perez]

That is EMBY

[ZeroFux]

@tmm1 Sorry to bring this back up months later. Can you tell me where the json files are located? I was able to get to get Plex to recognize ChannelsDVR via xTeVe via the channels.m3u file, but now I’m working on the guide data. Currently, I’m downloading east/west guides from schedulesdirect.org and picking which one I want to use in the xTeVe interface, but it might just be easier to play around with the json file since channels already has all the data needed.

Does channels have the ability (or hack available) to export the guide to an XML file?

[crackers8199]

@ZeroFux

Does channels have the ability (or hack available) to export the guide to an XML file?

it doesn't, but the channel mapper i'm writing will. i ended up writing a parser to convert the json guide data that the DVR outputs into XMLTV, but ended up not needing it thanks to the awesome feature the devs added in which gives us the ability to map channel to guide in the playlist itself. i already had the code written though when i figured that out, so i figured i might as well just leave it there in case someone else needs / wants to use it.

i should have it ready at some point this week, perhaps as soon as tonight.

[ZeroFux]

Can you share your parser with me? I'm using xTeVe and that needs the playlist and XML to be separate files.

[crackers8199]

yup, i'm going to put it up on github once i have it fully ready to go. that's why i said i think i'll have it ready perhaps as early as tonight.

[ZeroFux]

Oh thank you!! I misunderstood your post. I thought you said you stopped development. On the parser because the devs deployed something you could use instead. My bad!

Also, do you remember the post about the feature the devs provided? I want to read up on the discussion.

[mike_here]

@ZeroFux

Oh thank you!! I misunderstood your post. I thought you said you stopped development. On the parser because the devs deployed something you could use instead. My bad!

I stopped development on the parser I created once the Devs changed the m3u from Channels to better work with Emby.

@crackers8199 has created a new parser that he'll release soon. This is a long post and easy to confuse the conversations.

[crackers8199]

i stopped working on the parser because i realized that i could use the feature they provided for auto mapping, but i had already written most of it at that point. it works, it's just that their mapping is better so i am using that. i left the code there because it works and there's no reason to remove it when someone might find it useful, even though i'm not using it at the moment...

here's the other discussion on m3u playlists.

BETA: Custom Channels via M3U Playlists

Thanks - you have essentially the same thing that I have. My RTSP path works fine in VLC, including the audio, so like you said, there must be something different with the WyzeCams than the cams you have. I was curious if you put something else in the text config for the audio piece, but that does not appear to be the case. Thanks for the info. You helped me confirm that I set it up correctly since your setup is virtually the same as mine and yours works with a different brand of camera.

[crackers8199]

here's the thread on my mapping app, that includes the XMLTV output.

Remapping channel numbers

i know the devs are crazy busy, and they've mentioned a few times now when many of us have asked for the ability to do this that it's on their agenda...but they don't know when (and probably not anytime soon). so, i decided to work this out on my own to give us all the ability to do so until they get a chance to do it themselves... enjoy!

[jdroberto]

@tmm1

http://x.x.x.x:8089/devices/TVE-Cox/channels.m3u

Is there a more complete list of how to access various services? Sling, etc. I noticed for example Locast isn't as simple as TVE-Locast/ you need to include the region# after the word Locast. Any chance there's a guide/list of all supported devices?

[mike_here]

In the web admin find the list of sources. Click on the source you want the ID. In the upper left hand of the screen it is listed on the second line. For example Cox (TVE-Cox). What's inside ( ) is the ID.

[jdroberto]

Thanks for the response. When I click the EDIT button on any source, then I find what you're mentioning. that's helpful!

[Thomas_Andrews1]

any way to use the m3u remotely? As in server is at my house and I want to use m3u list and app at my moms? tried using the my.channels.net:8089 where "my.channels.net" is your server code and no luck

[Edwin_Perez]

You would have to use your external IP ... I believe not the local IP in your M3U.

[tmm1]

It's not possible to do that without a VPN.

[Thomas_Andrews1]

gotcha! thanks

[AtoZ0to9]

How might I go about exporting to m3u file to use elsewhere?

[RyzenBeast]

@tmm1

As far as guide data.. you could pull it from the DVR I guess, but it's in a json format that would need some massaging before it could be used with other software.

Any advancement here? I'm not getting very good guide data.

[racameron]

Channels can now natively export its guide as XMLTV: GET /devices/ANY/guide/xmltv. You can also replace ANY with the DeviceID of a specific tuner/source in the path. The endpoint additionally can take 2 parameters: start, expressed in epoch time, for when the guide data should begin; and duration, expressed in seconds, for how much guide data to export.