Tvheadend

Hi.
conf_migrate.py not support iptvservices folder.
150 channels will add by hand again- need a lot of time. :(
Maybe has some solution?

thanks

But I have a friend, who uses the Sundtek USB DVB-C Adapter. I works fine also, but after every tvheadend restart he gets a new card with a strange cardID.
1. card: (null)/??/0000:0001
2. card: (null)/+??/0000:0001
3. card: (null)/K??/0000:0001
4. card: (null)/{??/0000:0001

TVheadend and the USB SundTek Adapter are running on a Raspberry Pi. And it works, except the issue with these never ending new adapters

It seems that TVheadend fails to get the BUS Adress, right? If you need more data, I could get it.

Same Problem here .... What can we do??

Guys,

I am aware of the problem I've just not had a chance to look into it.

Adam

Thanks Adam ... I'll deactivate hte sundtek Adapter in the meantime...

Just updated to latest beta. When I edit network and save I get:

2013-12-29 14:52:12.762 settings: Unable to create dir "/home/hts/.hts/tvheadend/input/linuxdvb/networks/474a59a6d88242b2b3b66f1eacf2210a/muxes/4ebece0a866dda1a6f69252b03f68297": Permission denied
2013-12-29 14:52:12.762 settings: Unable to create dir "/home/hts/.hts/tvheadend/input/linuxdvb/networks/474a59a6d88242b2b3b66f1eacf2210a/muxes/4852caa4c730293975e8523333d37772": Permission denied
2013-12-29 14:52:12.763 settings: Unable to create dir "/home/hts/.hts/tvheadend/input/linuxdvb/networks/474a59a6d88242b2b3b66f1eacf2210a/muxes/33d1f6e15fc3c5a3e262a25f36fb12c0": Permission denied
2013-12-29 14:52:12.763 settings: Unable to create dir "/home/hts/.hts/tvheadend/input/linuxdvb/networks/474a59a6d88242b2b3b66f1eacf2210a/muxes/7323bf0e9990036d6ba49196ad321f91": Permission denied

Great work

I set up a raspberry pi with the current trunk version and it works almost fine.
Some notice:
- I miss the old "use ServiceID as channel number" option or a way to set the order of channels on server side for playlists.
- Switching between channels seems to slower a bit. I use separate tuners for each muxes (1 network = 1 mux = 1 tuner). With the old revisions this setup garanteed instant switching. Maybe current "keep fe open" is not fully implemented.

I'm wondering how far the the stable release is the actual trunk version? Is it just a bug-fixing process missing (but it looks not so bad) or there are other features comming?

Thanks all for this great piece of software!

Mario,

At this stage there is no intention to develop any significant new features. It'll mostly be bug fixing, tinkering and possible if someone else develops a cool new feature and submits a PR I might consider it.

Adam

Adam Sutton wrote:

At this stage there is no intention to develop any significant new features. It'll mostly be bug fixing, tinkering and possible if someone else develops a cool new feature and submits a PR I might consider it.

Thank you for the quick answer. How stable is the actual code, in your opinion? Much work?

I've been running it since just before Xmas, given that up to then I'd been running a 3.4 build (maybe some minor updates) from about the same time last year, that should tell you what you need to know

Of course there is a tendency for things to work better on my own system than others, since if stuff breaks on mine I have greater visibility and I always fix it quickly, but quite a few people have been running it for some time now.

I'd always recommend backing up config, and potentially running a local test copy if you're really paranoid, before switching over.

Adam

I thought I would try this again. I tried it again from scratch(building the latest from git) and I still had the same problem. This is using a cubox with a DiBcom 7000PC : DVB-T and Montage Technology DS3000/TS2020 : DVB-S. The problem was the dvb-s found services but the second tuner(dvb-t) I enabled did not.

I tried it using the migration script and both tuners are working fine now. Although when I try and view a programme that is on at the moment the 'play now' button does not show up. If I play the channels from the services tab using vlc they work ok.

I have still kept all previous configs and build but I might keep this version running for while and see what happens.

Cheers

Matthew

Wait, so if I have a HDHomeRun Dual that has two tuners, then I'd map both tuners to the same network since they have the exact same muxes and services?

I tried that originally and I couldn't watch anything while the DVR recorded something with the 1st tuner. I'll turn on debug and see if I can see exactly what it's doing, but can you confirm that I'm supposed to map both tuners to the same network?

Thanks!
Tony

Adam Sutton wrote:

John Törnblom

1. You can map channels/services in multiple ways:

a. from channels page, you can hit map and it will try and auto-map all services.
b. Or for existing channels you can double click the services cell for that channel and manually select teh services to map.

c. from the services page, you can hit map. If you have any selected services, it will map just those. If you don't have anything selected it will map all.
d. And you can also manually map by double clicking the channels cell to map to a specific set of channels.

2. With the new UI (and it's far from perfect) you can now both sort and filter most both columns (sorting is limited to a single column). Double click on a heading to sort (and again to reverse the sort). To filter, hover over the heading and click little drop down arrow, select filter and enter appropriate info.

The "Services" tab includes a "Network" column, and the filter is regexp based (you can also enter basic string match). So you can enter say "5w" if that's what the network name is and that's all you'll get. Then select and map, one shortcoming atm, is that you can't use the "map all" option. As it ignores the filtering (that's unlikely to change anytime soon, my UI skills are not good).

3. You have no direct control over which services are available on which tuners, this is fundamental to the concept of a single service within a network (to remove duplication and simplify multi-tuner setups). This is only marginally different from pre-merge, in that you could choose not to map a specific tuners values to a channel. This was done to keep things simple and it was decided this was an unusual requirement.

Having said that, its not impossible to achieve, its just that you end up having to fall back to a configuration that is much more like the previous way of doing things. You will basically have to set-up a network for each tuner, you will presumably end up with the same muxes in each (though you have the choice not to do this) and then you can choose which services to map to channels. Just make sure you name your networks sensibly so you can clearly identify what you need to select from.

4. Already explained this is perfectly possible.

So far you've not managed to list anything not possible. Only one thing that may, if you have very particular requirements, end up being no better off than in the old framework.

Adam

I can't see this mentioned anywhere, so why not ask. Does TVHeadend now officially support hot adding and removing of USB tuners? I just plugged in a USB DVB-S tuner into a computer with TVH running. CPU usage shot up for a couple of minutes (it's not the fastest of machines) and when it settled, a refresh of the TVH web config page showed that tuner present. No restart of the service needed. Pulling the same tuner out however did not lead to it being removed from the list of available tuners, but neither did it crash the whole computer. Maybe I needed to wait longer.

In the new configuration where are the channel names stored ? they used to be stored in the channel file in the channels folder.
I made a utility that converts all the channels from tvheadend into xml files, so that I can view the streams on my smart tv.
I just updated to the latest build, and have set everything up again. But I can get where the streams are, but the channel names are no longer available.

Can you tell me how the channel names are stored ?Thanks

Channel names are taken from the corresponding services unless redefined.

So, the only record of names you have is in

/home/hts/.hts/tvheadend/input/linuxdvb/networks/<id>/muxes/<id>/services/<id>

Unless you rename something, in which case the new name will be stored in

/home/hts/.hts/tvheadend/channel/<id>

Prof Yaffle wrote:

Channel names are taken from the corresponding services unless redefined.

So, the only record of names you have is in

/home/hts/.hts/tvheadend/input/linuxdvb/networks/<id>/muxes/<id>/services/<id>

Unless you rename something, in which case the new name will be stored in

/home/hts/.hts/tvheadend/channel/<id>

Legend thanks.

Have a look at this script to see how the author identified channels and matched them to icons - might give you some clues.

https://tvheadend.org/boards/4/topics/10563

i realy like the update you have done with separat pages for muxes, so its possible to use gui now for config mux and services. with over 4500 entrys the old way with everything in 1 list made tvheadend crash..

I think you can un-pin this thread now