| LinHES Forums http://forum.linhes.org/ |
|
| Mythtv 30 released http://forum.linhes.org/viewtopic.php?f=17&t=24818 |
Page 2 of 3 |
| Author: | brfransen [ Wed Feb 20, 2019 11:45 am ] |
| Post subject: | Re: Mythtv 30 released |
Kodi 18.1 and a new build of mythtv v30 are up. So is a new mythinstall so LinHES settings should work again. |
|
| Author: | knappster [ Wed Feb 20, 2019 8:23 pm ] |
| Post subject: | Re: Mythtv 30 released |
Cool. I will try to perform the update this weekend. One thing I noticed after upgrading to 30 was that a bunch of deleted channels reappeared. I deleted them again and they reappeared again, presumably after mythfilldatabase ran. The only thing that I have been able to come up with is that the command was previously set to Code: mythfilldatabase --remove-new-channels and that it reset to default Code: mythfilldatabase . I've updated the command in mythtv-setup and I'm just waiting for it to run again to see if the deleted channels stay deleted this time...
|
|
| Author: | brfransen [ Thu Feb 21, 2019 6:47 am ] |
| Post subject: | Re: Mythtv 30 released |
I updated one of my boxes to 30 last night and it didn't drop the args I was using for mythfilldatabase so that is curious. It shouldn't matter but what grabber are you using? |
|
| Author: | knappster [ Thu Feb 21, 2019 8:12 pm ] |
| Post subject: | Re: Mythtv 30 released |
I'm using SchedulesDirect. I've gone back to a backup and extracted the mythconverg database. I can see that the MythFillDatabasePath was just 'mythfilldatabase'. So it is a false alarm. The field did not change, but for some reason after upgrading it downloaded channels from SchedulesDirect that I had deleted long ago. After I changed the field to 'mythfilldatabase --remove-new-channels' this has not happened again. The only side effect is that I no get a mythfilldatabase log. To be honest, a couple years ago I got rid of cable and I've been using antennas since then. I've got multiple HDHomeruns and antennas and I'm trying to only have specific channels on specific antennas based on the towers that they pick up the best. Since SchedulesDirect does not allow you to create duplicate lineups from the same zip code and antenna, I may still have some lingering links to the cable listing so I have not deleted it. I may be better off biting the bullet and deleting all of my tuners and video sources on the backend and trying to start from scratch. I think I could probably have one listing for all tuners and then from the backend "Channels" menu delete any that I don't want each tuner to tune. |
|
| Author: | knappster [ Thu Feb 21, 2019 9:39 pm ] |
| Post subject: | Re: Mythtv 30 released |
Shortly after my last post the backend crashed and tried to restart. It seems that it didnt initialize properly and when I tried to start from the command line, it acted like it was already running. When I killed the process it restarted correctly. At the time it crashed I was watching a recording in kodi. The last message in the backend log was that it was running a metadata lookup job. No segfault message this time. I saw some errors in the commflag log around the time of the crash, but I don't know which was the chicken or the egg. I have not installed the updated build, but plan to tomorrow evening and hopefully it will stabilize the backend. |
|
| Author: | brfransen [ Fri Feb 22, 2019 7:24 am ] |
| Post subject: | Re: Mythtv 30 released |
If you rework your SD listings it would be a good time to transition to the xmltv grabber if you are still using the direct data grabber. I think the mythtv devs are talking about removing the direct data grabber in one of the next releases. |
|
| Author: | knappster [ Sat Feb 23, 2019 5:17 am ] |
| Post subject: | Re: Mythtv 30 released |
Thanks for the heads up on the grabber. It is listed on mine as "North America (SchedulesDirect.org) (Internal)" Last time I looked at this there were a tiny fraction of options from what I see now. Is "Schedules Direct JSON API (xmltv)" the correct option? I saw several other packages (including nvidia drivers) updated when I performed the update last night. I thought about cherry picking certain items but figured I would cause more harm than good. I performed a full update and everything appears to have gone smoothly. Since there was a major version update on the nvidia drivers, I am going to test VDPAU on mythfrontend yet again to see if the driver update will resolve my problems. Kodi 18 works well in my limited testing. The only caveat is that I had already built a newer inputstream.adaptive and pvr.mythtv package. I'm not sure if you have a netflix or amazon prime subscription, but both addons are working and I suspect that they would work just fine with the inputstream adaptive in the repository. Both are available on github, but at times you may have to dig through different forks or comments in the issues to overcome problems that crop up. I also noticed a Sling TV addon was recently created, but I do not have a subscription to it and I don't have any immediate plans to. I really enjoy having everything running on my LinHES box using LIRC. Things have come a long way since I was just barely able to get Hulu to play video using the linux flash plugin many years ago... |
|
| Author: | knappster [ Sat Feb 23, 2019 6:02 am ] |
| Post subject: | Re: Mythtv 30 released |
Didn't have to wait long to find out that VDPAU is still broken for me in mythfrontend: 2019-02-23T05:56:37.011260-06:00 mythfrontend[6488]: E Decoder mythplayer.cpp:3847 (DecoderGetFrame) Player(0): Decoder timed out waiting for free video buffers. I'll continue to use kodi as my frontend and hope that this mystery goes away when nvdec becomes available... |
|
| Author: | brfransen [ Sat Feb 23, 2019 4:37 pm ] |
| Post subject: | Re: Mythtv 30 released |
North America (SchedulesDirect.org) (Internal) is Direct Data. I am using "Multinational (Schedules Direct JSON web services with SQLite DB) (xmltv)". There is a section in the wiki about transition from Direct Data to xmltv: https://www.mythtv.org/wiki/XMLTV#Sched ... rect_Setup I have just rebuilt both pvr.mythtv and inputstream for 18.1. If you could test them that would be great. I don't have subs to test either. I did have to change your PKGBUILD for pvr.mythtv as the install didn't put the install files in the correct place for some reason. You can see in the repo what I had to change to get it to pkg up correctly. Also can you confirm that my 18.1 build had LIRC working for you? |
|
| Author: | knappster [ Sat Feb 23, 2019 5:06 pm ] |
| Post subject: | Re: Mythtv 30 released |
Good news: Kodi 18.1 package works with LIRC Inputstream package works with Netflix and Amazon Prime Pvr.mythtv package is working with mythtv. I was unable to compare the PKGBUILD files but it just worked. I plan to tackle the schedulesdirect stuff next weekend. Let me know if there is anything else that I can do to help. |
|
| Author: | knappster [ Wed Feb 27, 2019 8:51 pm ] |
| Post subject: | Re: Mythtv 30 released |
brfransen, have you been experiencing any mythbackend stability issues since upgrading? There was a recording scheduled to start tonight and mythbackend went unresponsive about the time it started. This is at least the 3rd backend problem I've had since upgrading to 30. mythbackend ran at about 15% CPU usage for over an hour until I killed it and it restarted. I've posted the backend log on pastebin and the last log was at about 19:00 when the recording started. https://pastebin.com/y1A2UJhB I finally killed it a little over an hour later and it restarted. I'm hoping that I can troubleshoot this without needing to revert back to my v29 backup. I'll post the log to mythtv forums as well to see if they have any suggestions. P.S., I am on your build 30.0-2 and have not updated to 30.0-3 yet. |
|
| Author: | brfransen [ Thu Feb 28, 2019 9:23 am ] |
| Post subject: | Re: Mythtv 30 released |
My backend has been rock solid. No change in that area from 29. |
|
| Author: | knappster [ Thu Feb 28, 2019 6:38 pm ] |
| Post subject: | Re: Mythtv 30 released |
That is positive. Are you using metadata lookup? I turned it off last night after my issue since it was the last thing logged. I plan on upgrading again and increasing verbosity of the backend log this weekend, too. Edit: I also went back into mythtv-setup and found that there is a separate field for the grabber arguments. So Code: mythfilldatabase is in the field for the command and Code: --remove-new-channels in the arguments. It is now logging mythfilldatabase again. I intend to rework this over the weekend anyway. I saw that in github master they removed the direct data grabber as you alluded to...
|
|
| Author: | brfransen [ Fri Mar 01, 2019 8:55 am ] |
| Post subject: | Re: Mythtv 30 released |
I do run metadata lookups and they are working. |
|
| Author: | knappster [ Tue Mar 05, 2019 6:51 am ] |
| Post subject: | Re: Mythtv 30 released |
I disabled metadata lookup last week and updated to mythtv 30.0-3 over the weekend. I didnt change the mythtv launch to debug log level, ive just been manually setting it after it wakes up in the morning. Well, wouldnt you know it... The backend stopped respondibg immediately this morning. I attempted to change to debug logging and it could not because the backend was unresponsive. The last few lines before restarting it we're: Code: 2019-03-05T06:16:15.164370-06:00 mythbackend[1901]: I MythSocketThread(51) mainserver.cpp:7928 (connectionClosed) Monitor sock(560a317d4ea0) 'linhes' disconnected
2019-03-05T06:16:21.472683-06:00 mythbackend[1901]: I Scheduler scheduler.c 2019-03-05T06:16:15.164370-06:00 mythbackend[1901]: I MythSocketThread(51) mainserver.cpp:7928 (connectionClosed) Monitor sock(560a317d4ea0) 'linhes' disconnected 2019-03-05T06:16:21.472683-06:00 mythbackend[1901]: I Scheduler scheduler.cpp:2472 (HandleReschedule) Scheduled 123 items in 8.5 = 7.84 match + 0.41 check + 0.21 place 2019-03-05T06:16:21.572674-06:00 mythbackend[1901]: I MythSocketThread(46) mainserver.cpp:7980 (connectionClosed) Control sock(560a317d4ea0) disconnected 2019-03-05T06:16:21.572735-06:00 mythbackend[1901]: I Scheduler scheduler.cpp:5684 (WasStartedAutomatically) Close to auto-start time, AUTO-Startup assumed 2019-03-05T06:16:21.572794-06:00 mythbackend[1901]: I Scheduler scheduler.cpp:5692 (WasStartedAutomatically) Close to MythFillDB suggested run time, AUTO-Startup to fetch guide data? 2019-03-05T06:16:21.572840-06:00 mythbackend[1901]: I Scheduler scheduler.cpp:2530 (HandleRunSchedulerStartup) Scheduler: AUTO-Startup assumed |
|
| Page 2 of 3 | All times are UTC - 6 hours |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|