bas-t / ffdecsawrapper

FFdecsa empowered softcam for MythTV
GNU General Public License v3.0
17 stars 9 forks source link

26-Oct-2014 commits stop ffdecsawrapper tuning #32

Closed fe31nz closed 9 years ago

fe31nz commented 9 years ago

Mythbuntu 14.04, MythTV 0.27-fixes

There was a new kernel today, so I did apt-get dist-upgrade to install it and then ran tbsinstall as usual. But after rebooting, when I tried to use LiveTV to tune to any ffdecsawrapper channel, mythbackend logged that it had sent the tuning command but the channel never tuned. So I edited tbsinstall to add this line just after the "cd ffdecsawrapper" line:

git checkout 2bd9a7e820eb2aaf10209c6a876fa5d8365c94eb

That takes me back to the code before the commits of 26-Oct-2014. With that fix, running tbsinstall builds a version of ffdecsawrapper that again works for me. So it looks like something in those commits seriously broke ffdecsawrapper on my system.

bas-t commented 9 years ago

What version of the linux kernel do you run now? And please pastebin a log with those failures, I've got nothing to analise now.

My guess is that 202c69b06f037c7e053b188d38142c817e56f897 and 24525c4b2db0a037675a73aa4eab73936871a054 are to blame.

However, I need those commits to be able to tune reliable using linux-3.18-rc1/2 and using opensource drivers for TBS6281/6285 (https://github.com/bas-t/tbs6281-5-intree). I tested these commits for backwards compatability with linux-3.16.6

Bear in mind that the official TBS drivers are always broken to some extent.

Also, official TBS drivers are incompatible with linux-3.18. I reported that to TBS and as a result, the drivers will be updated in the next few days/weeks

If nothing of this will solve your problems, I will update the tbsinstall script to use the 'stable' branch of FFdecsawrapper unless set otherwise. As it is now, you can run ./tbsinstall --ffbranch=stable to get the same result.

fe31nz commented 9 years ago

The new kernel I was installing is Mythbuntu 3.13.0-39. I also rebooted back to my next older kernel (3.13.0-37) and tried the latest ffdecsawrapper there, and it did not work either.

When I was having the problem, I was in a bit of a hurry to get it all working again as I only had 90 minutes to do the updates before the next recording started, and it was the middle of the night. So I did not spend any time collecting logs. I just checked now and the ffdecsawrapper.log file has been overwritten. I do have mythbackend.log, but I can not see much of interest in it - it basically just says "TuningSignalCheck: Still waiting. Will timeout..." but maybe there is something of interest that you can spot. I have put a file containing some of that log on my web server:

http://www.jsw.gen.nz/mythtv/tuning27_failed.log

It shows tuning LiveTV on DVB-T tuner [1] which works, then switching to a decrypted DVB-S tuner [27] which never tunes. My recollection of ffdecsawrapper.log at the same time is similar - it saw the tuning command, then there was nothing after that. Comparing my memory to what I can see in today's ffdecsawrapper.log, I think what I saw was:

CHANNEL: Clearing tuning cache due to switch cmd CHANNEL: Tuning frontend (new)

and then nothing after that. But we really need a proper log to be sure.

As I am going away over the weekend, I will likely not be able to do any further testing until Tuesday or Wednesday. When I do, what level of debug should I set for ffdecsawrapper?

bas-t commented 9 years ago

Fixed in ecb0463949b153093011753c5b7b56e207c42a98, please test.