Tvheadend

1. Once you have the services, have you mapped them to channels

2. In Configuration -> DVB Inputs -> Services, each service has a 'play' link. Right-click and save as...

2.0 If you're lucky, your system will recognise the file type and launch a plugin. If you're not, you need to rename it.

2.1 Look at the file - it's text - it's either m3u or xspf. Rename the file accordingly.

2.2 Double-click to launch your default media player, or load into VLC directly and play

3. Once you've mapped channels, you have a similar 'play' link in Configuration -> Channels/EPG -> Channels

Thanks for the quick response.

So, I did as instructed and the save as step. "00b3ae5a78de90cca94cadfde6baf2b2" is the filename from the play link of "http://10.0.0.49:9981/play/stream/service/00b3ae5a78de90cca94cadfde6baf2b2?title=%20%2F%20". I did this for three other listed services.

Anyway, so I don't see the extension listed.

I opened up both VLC, Rhythmbox, and Videos (Ubuntu 14.04 default app). None of them were able to open the stream.

VLC asked for login credentials. It gave me the same error as above.

I'm running "HTS Tvheadend 3.9.1084~gf72733f~precise" which is the latest on the unstable PPA.

If I grab one of my streams and save the file, then open it in a text editor, I get this:

<?xml version="1.0" encoding="UTF-8"?>
<playlist version="1" xmlns="http://xspf.org/ns/0/">
  <trackList>
     <track>
       <title>BBC One HD / BSkyB</title>
       <location>http://xxx.xxx.xxx.xxx:9981/stream/service/cd786c55a30644dd9a931226b4bdc443</location>
     </track>
  </trackList>
</playlist>

That's an xspf file, so renaming the file to cd786c55a30644dd9a931226b4bdc443.xspf and double-clicking and it opens in VLC. I don't remember the m3u format, but it should start with #EXTM3U (or, simply, "it's not like the above" - if it's not xspf, it's m3u).

Now, the fact you're being prompted suggests that you've got an access control issue. You need a rule that's something like 'user: *, password: *, 10.0.0.0/24, Streaming: <tick>" - basically, give unauthenticated streaming rights to anything on your LAN segment.

I have a user setup as stream / 12345 and it has all rights provided. I restarted TVHeadend's process to be safe. Still no-go for whatever reason.

I tried the file you described and still the same result.

<playlist version="1" xmlns="http://xspf.org/ns/0/">
<trackList>
<track>
<title>unknown</title>
<location>http://10.0.0.49:9981/play/stream/service/00b3ae5a78de90cca94cadfde6baf2b2&lt;/location>
</track>
</trackList>
</playlist>

Now to be clear, none of my "Services" are mapped. I'm trying to find out what they are and then attempt to name them.

So, I'm attaching some screenshots to try and be sure my setup is proper under the latest build.

Only oddity I see is that the Networks page has an empty drop-down for Networks under the adapter. And, I cannot type in the Networks name and save it. I try over and over and it won't ever give me an option to select.

That oddity... can you show me screenshots of Configuration -> DVB Inputs -> Networks and a similar screenshot of an adapter config, please?

Did you migrate your config from 3.4/3.5? I can't recall if it's automated now, but you did have to run a specific script to shift to the new DVB code.

Yeah, I tried uploading all the screenshots. I noticed it went bonkers just now lol. To make life simpler, I think, I added it in a post here: https://plus.google.com/117949361368315100519/posts/WJJNVecEVtR

I came from 3.4.x (stable PPA) to this version in the unstable PPA.

I'm unaware of a script and am fine just starting fresh.

I'm genuinely not sure what to make of that. Maybe having a network name = adapter name is the problem... although where you've got that adapter name from defeats me - I presume you've changed it from a default "Wibble Blob : DVB-T #0"-style entry. That's straw-clutching territory, though.

Migration script (if it's needed, I genuinely don't know and it looks like you're mostly there) is here:

https://tvheadend.org/boards/5/topics/9792

Let me ponder when it's today instead of the small hours of tomorrow :-)

Nope, no epiphany this morning. I'm guessing that this is ATSC, so I'm out of my depth, not having such things on this side of the water. All I can suggest is either trying the script to migrate an old config from backup, or else trash it and start again - detect the adapter, set up the network, tie the two together, add muxes, scan.

Much easier to start over, agreed. So, I purged and reinstalled through the unstable PPA.

Everything actually worked nearly instantaneously from afar. I cannot confirm that the channels work, but I mean it literally did the mapping and everything just fine which it wouldn't do before.

I'll venture a guess and say old junk was clogging up the new system. Yeah, I know that's an intelligent description!

I'll know about channel functionality later today or tomorrow depending on time...

I do have tickets to a KISS & Def Leppard concert tonight, so that may cause a delay. lol!

Okay, so it works with VLC now. Only negative is with Plex. lol. PROGRESS!

THANK YOU SO MUCH!