Tvheadend

at the moment tvheadend is not so good at handling large numbers of channels. You really need to edit the channels manually via the GUI or write something that can edit the JSON files where the result is stored. (look in the .hts directory for the json files). The closest thing that comes to "bouquets" is the TAGs options. Each channel can be assigned one or multiple tags that can be used as a filter in various other screens. See the documentation for more details around tags.

My (personal) recommendation would be to only add those transponders and channels that you are really interested in (most likely to watch and/or record from) and do not use tvheadend for "casual zapping" along all the available channels, other solutions are better suited for that task at the moment.

There is a project to rework the way tvheadend handles this, but it is not yet thought out extensively.

Hein

Thanks for the reply. I read about tags, and in fact it's the closest thing to bouquets. Anyway, it means, tvheadend is not for me yet... Unfortunately, I'm the guy who likes to jump over the channel list...

Sad, because actually there is nothing developed yet (or I haven't met anything), which would be good enough for DVB-S/S2 management. The only software I know, which is perfect for channels management is Enigma (open source). It probably doesn't allow to implement, but maybe the way it works may give some ideas? Maybe this is a way to go - to look at Enigma? It allows to store thousands of channels, timeshifting, manual recording, playing, etc. and it's working on much worse hardware, than any personal HTPC built nowadays with powerful CPUs & GPUs and huge RAM.

well, you can always use both. Have a tvheadend server sitting in a cabinet that is happily recording shows for you and have an STB sitting next to your TV that you use if you want to zap around channels. The server can have 3 tuners so there is hardly any change of conflicts in the recordings, and your STB is using a single tuner. Using 4 quad LNB's and a switch gives you the best of both worlds.

The idea was to have "all-in-one". The only thing I was thinking was to get something to: play music (which actually STB can do), watch pictures (this is a bit of problem fo STB if the pics are bigger size) and watch 1080p movies (mkv and ts work on STB, but that's all) and of course watch live tv (this is what STB was made for).
I thought I will replace STB with something more powerful, but I think I should have wait a bit more.

I know I shouldn't ask about it here, but VDR has mainly support in German, and I don't know it so good... Do you know if VDR can support a big number of channels, ot it is similar situation?

I would love to see a better way to manage channels also.
Just stating " make your own editor " is not the answer we are looking for as not all people are skilled in programming.
I find it strange that you can make an excellent backend but forgot usability for the day to day user.
It should have been in the plans when this project was taken over.

1. Make a stable backend server.
2. Output information in the best usable way possible.

point 1 is greatly achieved (it is the most stable TV server around atm )
point 2 even if we would disable the "not so often used sat's" ( which is a strange comment in it self ) we still have loads of channels that need to be edited ( channels numbering /moving into [selfmade]groups adding/removing channels )
Also using a file-format different from the rest won't help.

as i said in previous post, why not go with the format OpenPLI uses ( .XML ), what to gain ?
1. Uniform file format, interchangeable with other projects like OpenPLI.
2. Big support group making tools for every platform (Win/Linux/osX)
3. Many tools for editing, which work very very good.
4. Pre-made listing downloadable from the web.