Project

General

Profile

Forums » General »

4.1-1785~g264b4ec - don't mapping channels

Added by David jrm over 8 years ago

Hi

For Info.
It seems that mapping channel functionality is not working in above build. I have tried with a clean install and outcome is the same... muxes are detected, services as well, but no way to map channels. I have back to previous 4.1-1777~gff9dab0 and there works OK.

Rgds
David


Replies (7)

RE: 4.1-1785~g264b4ec - don't mapping channels - Added by David jrm over 8 years ago

The same still happening with 4.1.1797

Could someone take a look on this?

Thanks

RE: 4.1-1785~g264b4ec - don't mapping channels - Added by David jrm over 8 years ago

When a service is mapped manually to a channel and tvheadend is restarted, then the change is not retained so service back to no chamnel associated. If you try to use the channel mapping button it still not working

RE: 4.1-1785~g264b4ec - don't mapping channels - Added by David jrm over 8 years ago

is this being experienced by someone? or just me? :(

RE: 4.1-1785~g264b4ec - don't mapping channels - Added by Mark Clarkstone over 8 years ago

You may want to run tvheadend in debug mode to see what is causing the problem..

e.g. something like..

sudo -u hts /usr/bin/tvheadend -c /home/hts/.hts/tvheadend --debug all --trace all --logfile /home/hts/debug.log

Warning this will output a lot of info both in terminal and to the log file..

RE: 4.1-1785~g264b4ec - don't mapping channels - Added by Guillaume DC over 8 years ago

Hi all,

same issue here. But I didn't have time to check logs because of hungry clients :) I reinstalled stable version

RE: 4.1-1785~g264b4ec - don't mapping channels - Added by David jrm over 8 years ago

I will try to debug on weekend. What I have seen so far is that not only channel mapping is affected but also when the application service is restarted take aprox 1 minute to back while with previous git it is just 1-2 seconds so definitely something has changed

RE: 4.1-1785~g264b4ec - don't mapping channels - Added by David jrm over 8 years ago

I can confirm that current git resolve the above 2 issues.:)

    (1-7/7)