From stephen_agent at jsw.gen.nz  Fri Mar  1 03:12:54 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Fri, 01 Mar 2019 16:12:54 +1300
Subject: [mythtv-users] No DVB-C channels anymore
In-Reply-To: <20190228T191320.GA.26f44.stse@fsing.rootsland.net>
References: <20190228T183358.GA.590a9.stse@fsing.rootsland.net>
 <CAMwtTBBSOjs+EpEHAYTi-8YgGL046fwzyWkh4SRqu7RwHYxxQg@mail.gmail.com>
 <20190228T191320.GA.26f44.stse@fsing.rootsland.net>
Message-ID: <lh8h7edrmm31fbi2fu5tidbu1aga3ehs9c@4ax.com>

On Thu, 28 Feb 2019 19:14:32 +0100, you wrote:

>On Do, Feb 28, 2019 at 01:09:50 -0500, Daryl McDonald wrote:
>>> I?m wondering why the subtype is T2. The card can DVB-C and -T, but
>>> I can?t change the type. I don?t know if this is the problem.
>>May be a dumb question, but have you tried changing it with the east
>>arrow? (while card type is highlighted)
>
>Yes, I tried, but I can?t highlight this field. It is always skipped.
>
>Shade and sweet water!
>
>	Stephan

Do you have any software from Digital Devices to use with that card?
It may have the ability to set the tuner type.

From aristide at free-it.ch  Fri Mar  1 07:39:02 2019
From: aristide at free-it.ch (Yann Lehmann)
Date: Fri, 1 Mar 2019 08:39:02 +0100
Subject: [mythtv-users] No DVB-C channels anymore
In-Reply-To: <20190228T183358.GA.590a9.stse@fsing.rootsland.net>
References: <20190228T183358.GA.590a9.stse@fsing.rootsland.net>
Message-ID: <13586cd7-ae45-bf50-a83a-bd908d08a3ae@free-it.ch>

Am 28.02.2019 um 18:50 schrieb Stephan Seitz:
> 
> Since we had some changes here in the cable network (the analogue
> channels were remove here in Germany), I tried a complete scan, but
> Myhttv isn?t finding anything anymore.
> 
>

Did you let it enough time to achieve ? I had a Digital Device dual
DVB-C adapter and it needed a very long time (IIRW over an hour) to do a
full scan from MythTV.

From dheianevans at gmail.com  Sat Mar  2 01:22:18 2019
From: dheianevans at gmail.com (Ian Evans)
Date: Fri, 1 Mar 2019 20:22:18 -0500
Subject: [mythtv-users] Hauppauge WinTV-quadHD TV Tuner Card 1609 and
 mulrirec
In-Reply-To: <70649f7e-314b-b2a0-1178-5b74cfb1e286@gmail.com>
References: <mailman.167.1551290038.1689.mythtv-users@mythtv.org>
 <70649f7e-314b-b2a0-1178-5b74cfb1e286@gmail.com>
Message-ID: <CABiY0=hE+z7RWFKnLHcJVpQ_h_ubCFOGEYBEVC0MK2WWeTRXaQ@mail.gmail.com>

On Thu, Feb 28, 2019, 5:53 PM Barry Martin, <barry3martin at gmail.com> wrote:

>
> Hi Ian!
>
> MythTV can do multirec and record multiple stations on the same frequency
> using only one tuner?
>
> Thanks for asking the question (and to others for replying) ? was
> something I assumed but, well, you know about assuming! <g> I was happy to
> see verified multiple recordings could be done. Also a congrats to you for
> snagging part of my subject title so others could find but realize a
> tangential thread.
>
>
>
Thanks. Though you don't know how much it hurt when I hit Send and realized
the subject line said "mulrirec" instead of "multirec". Big thumbs on the
phone.

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190301/fa3fbe15/attachment.html>

From jan.ceuleers at gmail.com  Sat Mar  2 08:57:41 2019
From: jan.ceuleers at gmail.com (Jan Ceuleers)
Date: Sat, 2 Mar 2019 09:57:41 +0100
Subject: [mythtv-users] mythtv-setup crash when adding new storage group
Message-ID: <cac289c9-68da-9aca-4272-578d42a30b79@gmail.com>

Hi

I have just added two new disks to my backend and wanted to add them to
the storage groups in mythtv-setup. However, mythtv-setup crashes when
doing that.

The directories I'm trying to add are /mnt/disk7/mythtv/ and
/mnt/disk8/mythtv/

I have verified that the mythtv user is able to write to those directories.

# mythbackend --version
Please attach all output as a file in bug reports.
MythTV Version : v29.1
MythTV Branch :
Network Protocol : 91
Library API : 29.20180316-1
QT Version : 5.5.1
Options compiled in:
 linux profile use_hidesyms using_alsa using_oss using_pulse
using_pulseoutput using_backend using_bindings_perl
using_bindings_python using_bindings_php using_crystalhd using_dvb
using_firewire using_frontend using_hdhomerun using_vbox using_ceton
using_hdpvr using_ivtv using_joystick_menu using_libcec using_libcrypto
using_libdns_sd using_libfftw3 using_libxml2 using_lirc using_mheg
using_opengl using_opengl_video using_opengl_themepainter using_qtwebkit
using_qtscript using_qtdbus using_taglib using_v4l2 using_x11
using_xrandr using_xv using_profiletype using_systemd_notify
using_systemd_journal using_bindings_perl using_bindings_python
using_bindings_php using_freetype2 using_mythtranscode using_opengl
using_vaapi using_vdpau using_ffmpeg_threads using_mheg using_libass
using_libxml2 using_libmp3lame


I'm afraid I've gone ahead and added them to the database manually now...

Jan

From jan.ceuleers at gmail.com  Sat Mar  2 10:19:29 2019
From: jan.ceuleers at gmail.com (Jan Ceuleers)
Date: Sat, 2 Mar 2019 11:19:29 +0100
Subject: [mythtv-users] MythTV miscalculates the amount of free disk space
Message-ID: <762d3af4-7a04-f48c-afb5-9ed8d6ecf71f@gmail.com>

All,

In my previous message I talked about problems encountered while adding
new disks (storage groups). Having now done that, by adding them
manually to the database (while all mythtv processes were down) I would
like to report another problem.

The two new disks are completely identical to each other: same size
SSDs, the ext4 filesystems have been created within seconds of one
another, both contain only a mythtv directory in the filesystem root,
and the disks are otherwise empty.

According to mythweb, the backend thinks that the two new disks are in
fact one and the same disk - see Drive #3 in the following:

Disk Usage Details:
  MythTV Drive #1:
    Directories: dracor:/mnt/disk4/mythtv, dracor:/mnt/disk4/mythtv/livetv
    Total Space: 3,755,457 MB
    Space Used: 3,605,479 MB
    Space Free: 149,977 MB
  MythTV Drive #2:
    Directory: dracor:/mnt/disk5/mythtv
    Total Space: 3,755,457 MB
    Space Used: 3,609,826 MB
    Space Free: 145,630 MB
  MythTV Drive #3:
    Directories: dracor:/mnt/disk7/mythtv, dracor:/mnt/disk8/mythtv
    Total Space: 1,877,665 MB
    Space Used: 95,469 MB
    Space Free: 1,782,196 MB
  MythTV Drive #4:
    Directory: fe4:/mnt/disk6/mythtv
    Total Space: 840,342 MB
    Space Used: 805,131 MB
    Space Free: 35,211 MB

Weird.

Jan

From veehexx at zoho.com  Sat Mar  2 11:21:40 2019
From: veehexx at zoho.com (Tim Draper)
Date: Sat, 02 Mar 2019 11:21:40 +0000
Subject: [mythtv-users] missing keybinds on some FE's
Message-ID: <1693e227421.f1de53c2173359.4083304163391863266@zoho.com>

i've a number of FE's in my mythtv deployment and i've just come to upgrade the last one to v30.

TOGGLEBOOKMARK keybind has reset to null on all the other FE's i've upgraded so i've gone in to rebind it on this last FE, via mythweb interface. It's missing - simply not there. 

Also noticed a missing jumppoint on those that miss TOGGLEBOOKMARK; 'Live TV In Guide'. There could be more discrepencies but TOGGLEBOOKMARK is the one i specifically need.



Over the years i've accumulated a number of other FE names that remain in the db and appears half of them have TOGGLEBOOKMARK keybind, and half don't. There doesnt appear to be any consistency between those that do and don't.



is there a way to fix? worth a bug report? or shall i dig out the info on how to remove an FE from the DB and start again?





thanks,

Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190302/b16f8084/attachment.html>

From mythtv at sky.com  Sat Mar  2 11:39:01 2019
From: mythtv at sky.com (Paul Harrison)
Date: Sat, 2 Mar 2019 11:39:01 +0000
Subject: [mythtv-users] mythtv-setup crash when adding new storage group
In-Reply-To: <cac289c9-68da-9aca-4272-578d42a30b79@gmail.com>
References: <cac289c9-68da-9aca-4272-578d42a30b79@gmail.com>
Message-ID: <99b48986-70b7-64a8-dff2-c5037a569ef1@sky.com>

On 02/03/2019 08:57, Jan Ceuleers wrote:

> Hi
>
> I have just added two new disks to my backend and wanted to add them to
> the storage groups in mythtv-setup. However, mythtv-setup crashes when
> doing that.
>
> The directories I'm trying to add are /mnt/disk7/mythtv/ and
> /mnt/disk8/mythtv/
>
> I have verified that the mythtv user is able to write to those directories.
>
> # mythbackend --version
> Please attach all output as a file in bug reports.
> MythTV Version : v29.1
> MythTV Branch :
> Network Protocol : 91
> Library API : 29.20180316-1
> QT Version : 5.5.1
> Options compiled in:
>  linux profile use_hidesyms using_alsa using_oss using_pulse
> using_pulseoutput using_backend using_bindings_perl
> using_bindings_python using_bindings_php using_crystalhd using_dvb
> using_firewire using_frontend using_hdhomerun using_vbox using_ceton
> using_hdpvr using_ivtv using_joystick_menu using_libcec using_libcrypto
> using_libdns_sd using_libfftw3 using_libxml2 using_lirc using_mheg
> using_opengl using_opengl_video using_opengl_themepainter using_qtwebkit
> using_qtscript using_qtdbus using_taglib using_v4l2 using_x11
> using_xrandr using_xv using_profiletype using_systemd_notify
> using_systemd_journal using_bindings_perl using_bindings_python
> using_bindings_php using_freetype2 using_mythtranscode using_opengl
> using_vaapi using_vdpau using_ffmpeg_threads using_mheg using_libass
> using_libxml2 using_libmp3lame
>
>
> I'm afraid I've gone ahead and added them to the database manually now...
>
> Jan


Unfortunately unless something is easy to reproduce just saying
something is broken is no use to the devs. You need to provide some logs
or better still a backtrace of the crash.


Paul H.


From jan.ceuleers at gmail.com  Sat Mar  2 11:58:48 2019
From: jan.ceuleers at gmail.com (Jan Ceuleers)
Date: Sat, 2 Mar 2019 12:58:48 +0100
Subject: [mythtv-users] MythTV miscalculates the amount of free disk
 space
In-Reply-To: <bf6a3d79-c50f-ee57-b9e7-f6c32bb07744@sky.com>
References: <762d3af4-7a04-f48c-afb5-9ed8d6ecf71f@gmail.com>
 <bf6a3d79-c50f-ee57-b9e7-f6c32bb07744@sky.com>
Message-ID: <52be7619-49ac-a215-d7eb-778c14d67733@gmail.com>

On 02/03/2019 12:36, Paul Harrison wrote:
> Since both drives are empty and otherwise identical, mythbackend can't
> tell them apart. For all it knows the mounts point to the exact same
> drive. Until there is content on one or both of the drives it's unable
> to tell them apart.

Thanks Paul.

Sounds like a bug to me though. I thought that the backend verified it
could write to each storage group by creating temporary files, so if
that's correct it would also be an opportunity for it to find out
whether directories it thinks are the same are in fact.

From jan.ceuleers at gmail.com  Sat Mar  2 12:00:41 2019
From: jan.ceuleers at gmail.com (Jan Ceuleers)
Date: Sat, 2 Mar 2019 13:00:41 +0100
Subject: [mythtv-users] mythtv-setup crash when adding new storage group
In-Reply-To: <99b48986-70b7-64a8-dff2-c5037a569ef1@sky.com>
References: <cac289c9-68da-9aca-4272-578d42a30b79@gmail.com>
 <99b48986-70b7-64a8-dff2-c5037a569ef1@sky.com>
Message-ID: <f5c8936c-72b7-e024-f2fb-1631e5af90d8@gmail.com>

On 02/03/2019 12:39, Paul Harrison wrote:
> Unfortunately unless something is easy to reproduce just saying
> something is broken is no use to the devs. You need to provide some logs
> or better still a backtrace of the crash.

Yes, I'm aware of that, thank you. And I would have done if there were
log entries or a backtrace.

From hikavdh at gmail.com  Sat Mar  2 12:11:03 2019
From: hikavdh at gmail.com (Hika van den Hoven)
Date: Sat, 2 Mar 2019 13:11:03 +0100
Subject: [mythtv-users] MythTV miscalculates the amount of free disk
 space
In-Reply-To: <52be7619-49ac-a215-d7eb-778c14d67733@gmail.com>
References: <762d3af4-7a04-f48c-afb5-9ed8d6ecf71f@gmail.com> 
 <bf6a3d79-c50f-ee57-b9e7-f6c32bb07744@sky.com>
 <52be7619-49ac-a215-d7eb-778c14d67733@gmail.com>
Message-ID: <469697700.20190302131103@gmail.com>

Hoi Jan,

Saturday, March 2, 2019, 12:58:48 PM, you wrote:

> On 02/03/2019 12:36, Paul Harrison wrote:
>> Since both drives are empty and otherwise identical, mythbackend can't
>> tell them apart. For all it knows the mounts point to the exact same
>> drive. Until there is content on one or both of the drives it's unable
>> to tell them apart.

> Thanks Paul.

> Sounds like a bug to me though. I thought that the backend verified it
> could write to each storage group by creating temporary files, so if
> that's correct it would also be an opportunity for it to find out
> whether directories it thinks are the same are in fact.

Also they will have different IDs!


Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens


From stephen_agent at jsw.gen.nz  Sat Mar  2 12:34:10 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Sun, 03 Mar 2019 01:34:10 +1300
Subject: [mythtv-users] MythTV miscalculates the amount of free disk
 space
In-Reply-To: <762d3af4-7a04-f48c-afb5-9ed8d6ecf71f@gmail.com>
References: <762d3af4-7a04-f48c-afb5-9ed8d6ecf71f@gmail.com>
Message-ID: <jstk7elvcplpq7mjh9tt0e7e4v68f5j77h@4ax.com>

On Sat, 2 Mar 2019 11:19:29 +0100, you wrote:

>All,
>
>In my previous message I talked about problems encountered while adding
>new disks (storage groups). Having now done that, by adding them
>manually to the database (while all mythtv processes were down) I would
>like to report another problem.
>
>The two new disks are completely identical to each other: same size
>SSDs, the ext4 filesystems have been created within seconds of one
>another, both contain only a mythtv directory in the filesystem root,
>and the disks are otherwise empty.
>
>According to mythweb, the backend thinks that the two new disks are in
>fact one and the same disk - see Drive #3 in the following:
>
>Disk Usage Details:
>  MythTV Drive #1:
>    Directories: dracor:/mnt/disk4/mythtv, dracor:/mnt/disk4/mythtv/livetv
>    Total Space: 3,755,457 MB
>    Space Used: 3,605,479 MB
>    Space Free: 149,977 MB
>  MythTV Drive #2:
>    Directory: dracor:/mnt/disk5/mythtv
>    Total Space: 3,755,457 MB
>    Space Used: 3,609,826 MB
>    Space Free: 145,630 MB
>  MythTV Drive #3:
>    Directories: dracor:/mnt/disk7/mythtv, dracor:/mnt/disk8/mythtv
>    Total Space: 1,877,665 MB
>    Space Used: 95,469 MB
>    Space Free: 1,782,196 MB
>  MythTV Drive #4:
>    Directory: fe4:/mnt/disk6/mythtv
>    Total Space: 840,342 MB
>    Space Used: 805,131 MB
>    Space Free: 35,211 MB
>
>Weird.
>
>Jan

Are you sure that you have your fstab lines correct for those two
drives?  If you did a copy and paste on the lines, maybe you did not
change everything correctly in the second one and it is actually also
pointing to the first drive.  MythTV would see that and list both
mount points as being on the same drive.

From jan.ceuleers at gmail.com  Sat Mar  2 12:48:10 2019
From: jan.ceuleers at gmail.com (Jan Ceuleers)
Date: Sat, 2 Mar 2019 13:48:10 +0100
Subject: [mythtv-users] MythTV miscalculates the amount of free disk
 space
In-Reply-To: <jstk7elvcplpq7mjh9tt0e7e4v68f5j77h@4ax.com>
References: <762d3af4-7a04-f48c-afb5-9ed8d6ecf71f@gmail.com>
 <jstk7elvcplpq7mjh9tt0e7e4v68f5j77h@4ax.com>
Message-ID: <44053768-9981-5a8e-59f5-7e48b53b46e7@gmail.com>

On 02/03/2019 13:34, Stephen Worthington wrote:
> Are you sure that you have your fstab lines correct for those two
> drives?  If you did a copy and paste on the lines, maybe you did not
> change everything correctly in the second one and it is actually also
> pointing to the first drive.  MythTV would see that and list both
> mount points as being on the same drive.

# cat /etc/fstab | grep disk[78]
UUID=29f6e1a5-8a03-4b08-a8f4-b1e6ab4d752a	/mnt/disk7	ext4
defaults,noatime,nodiratime,barrier=0,commit=60	0	2
UUID=46e701c6-091c-4aee-bc44-f1fbf6a84bae	/mnt/disk8	ext4
defaults,noatime,nodiratime,barrier=0,commit=60	0	2



From johnpilk222 at gmail.com  Sat Mar  2 14:09:19 2019
From: johnpilk222 at gmail.com (John Pilkington)
Date: Sat, 2 Mar 2019 14:09:19 +0000
Subject: [mythtv-users] Active EIT data collection gives some defective
 recordings; passive scanning not working.
Message-ID: <cdb83736-2fb6-89f0-df76-bb6da3063daf@gmail.com>

I posted about this last year on the dev list and have just encountered 
it again.  I'm using DVB-T in the UK with one PCI single-tuner card and 
a twin-tuner USB bevice, running master.

https://lists.gt.net/mythtv/dev/618967

Last year I found that, during my post-processing of recordings from the 
USB device, project-x often reported missing sync bytes and/or packets 
out-of-order.  Although it applied its best corrections, some defects 
were still noticeable.  They seemed less frequent when I stopped active 
EIT scanning with the USB tuners, using only the PCI card.

Recently the number of defects rose again.  I may well have made changes 
during mythtv-setup, trees may be growing further into my line of sight, 
or perhaps there might be confusion between the numbering sequences of 
real and virtual tuners;  I haven't really looked for that.

I tried disabling active scanning on *all* tuners.  I had understood 
that passive scanning would continue to collect EIT data, for all muxes, 
as long as some recordings were being made - but yesterday only 2 days 
had data and late-edits that might have been expected hadn't been done. 
Things recovered after re-enabling active scanning by the PCI card only.

John P

From stephen_agent at jsw.gen.nz  Sat Mar  2 16:04:41 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Sun, 03 Mar 2019 05:04:41 +1300
Subject: [mythtv-users] Active EIT data collection gives some defective
 recordings; passive scanning not working.
In-Reply-To: <cdb83736-2fb6-89f0-df76-bb6da3063daf@gmail.com>
References: <cdb83736-2fb6-89f0-df76-bb6da3063daf@gmail.com>
Message-ID: <vm6l7eds403faivj642nkolv98hbojmfaf@4ax.com>

On Sat, 2 Mar 2019 14:09:19 +0000, you wrote:

>I posted about this last year on the dev list and have just encountered 
>it again.  I'm using DVB-T in the UK with one PCI single-tuner card and 
>a twin-tuner USB bevice, running master.
>
>https://lists.gt.net/mythtv/dev/618967
>
>Last year I found that, during my post-processing of recordings from the 
>USB device, project-x often reported missing sync bytes and/or packets 
>out-of-order.  Although it applied its best corrections, some defects 
>were still noticeable.  They seemed less frequent when I stopped active 
>EIT scanning with the USB tuners, using only the PCI card.
>
>Recently the number of defects rose again.  I may well have made changes 
>during mythtv-setup, trees may be growing further into my line of sight, 
>or perhaps there might be confusion between the numbering sequences of 
>real and virtual tuners;  I haven't really looked for that.
>
>I tried disabling active scanning on *all* tuners.  I had understood 
>that passive scanning would continue to collect EIT data, for all muxes, 
>as long as some recordings were being made - but yesterday only 2 days 
>had data and late-edits that might have been expected hadn't been done. 
>Things recovered after re-enabling active scanning by the PCI card only.
>
>John P

I have never heard of a passive EIT scanning option.  The only way EIT
scanning works that I know of is to take over a tuner temporarily.  In
theory, it would be possible to get a tuner that is recording to also
receive the EIT data at the same time, but I do not think MythTV does
that.  However, I thought that use of a tuner for EIT reception gave
way automatically when the tuner was needed for a recording, and
started again automatically afterwards.

When I was using USB tuners, I found that they were less reliable than
PCI or PCIe tuners, due to the way the USB cables work.  I had USB
tuners stop working when the cables were disturbed, or after a while
when there was force on the cable from the weight of the cable or
tuner.  The rate of such problems occurring seemed to be associated
with the USB socket on the PC - some were much worse than others, so I
always thought that such sockets were a slightly looser fit, and the
cable could then move so that eventually one or more pins stopped
making proper contact.  I got better reliability when I changed to
using USB cables that had a tighter fit.  And on my mother's MythTV
box, I have one USB tuner that never causes problems that way at all.

However, I never had bad recordings caused by USB problems.  What
happened was that the USB tuners always worked, or did not work.  They
did not appear to be working, but give bad recordings.  On occasion, I
would have a USB tuner stop in the middle of a recording, but I never
had bad data or missing data in a recording that did not stop.

My recommendations for using USB tuners:

1) Use close fitting USB cables.
2) Make sure that the tuner is flat on a surface and not putting its
weight on the USB cable.  If necessary, put something underneath the
tuner to support it higher so that the weight is off the cable.  Or
use a longer USB cable.  Make sure the aerial cable into the USB tuner
is not pulling on the tuner.  I have not tried this, but it might be a
good idea to tape down the aerial and USB cables to the surface you
have the tuners on.
3) Make sure the tuners and cables are not going to be bumped (eg when
dusting or vacuuming).  Bumping the aerial cable bumps the tuner also.
4) Make sure the cat is not allowed anywhere near the USB tuners. Kids
are a bad idea also.

My ultimate solution for greatest reliability was to change to using
PCIe tuners.  I bought an 8 tuner DVB-T2 PCIe tuner card and an 8
tuner DVB-S2 tuner card.  They have both been completely reliable,
even though the DVB-T2 card is actually running externally to the PC
on the end of a PCIe x1 extender cable (which is actually a USB 3
cable).  I had to do that due to the only remaining PCIe slot being
under the heatsink of my silent Nvidia card.

There is another way to do EIT EPG grabbing, which is the way I used
to do it.  I ran a script external to MythTV that once a day grabbed
the EIT data and saved it as an XMLTV file.  Then mythfilldatabase was
run to read the XMLTV data.  That also allowed me to do extra
processing on the EIT data before running mythfilldatabase - for
example, to remove the obnoxious "All New" that is often put on the
front of the subtitle data here.  I have since had to change to using
the OpenTV data from my satellite provider, as their EIT data stopped
providing full coverage of all their channels.  But that works in a
similar manner, with the EPG script running a program that grabs a
tuner and collects the OpenTV data and stores it as an XMLTV file.

The downside of using external EPG collection like that is that you
need to be able to use a tuner when MythTV is not using it.  The easy
way to do that is to simply have a spare tuner that is not assigned to
MythTV, which is what I am now able to do due to having 8 of each sort
of tuner.  But it is possible to work out when MythTV is not going to
be recording, and how long the gap in recordings will be, and then use
a tuner when there is a large enough gap for the EIT data to be fully
collected.  It should only take a few minutes at most to collect all
the EIT data.  I wrote a Python program that tells me when there are
gaps in my recording schedule.  It is on my web server here:

http://www.jsw.gen.nz/mythtv/gaps

So you could use it to work out a safe time to run EIT collection.
Note that the gaps program does not see the extra time at the end of
recordings that is added by mythbackend from the "RecordOverTime"
setting.  That setting is normally 60 seconds and no-one usually
changes it, so you need to allow an extra minute beyond what the gaps
program says is when all the recordings will be finished.  Similarly,
it does not see the extra time at the start of the next recording from
the "RecordPreRoll" setting, again normally 60 seconds.

External EIT data collection is done use software such as epgsnoop:

https://launchpad.net/epgsnoop

Where there is MHEG5 EPG data (such as here in New Zealand where it is
the official source of DVB-T free-to-air EPG data), that can be
collected using mhegepgsnoop:

https://sourceforge.net/projects/mhegepgsnooppy

On Windows, there is the EPGCollector program which handles EIT,
MHEG5, OpenTV and several other similar EPG data formats:

https://sourceforge.net/projects/epgcollector

From lindbladjonatan at gmail.com  Sat Mar  2 16:32:19 2019
From: lindbladjonatan at gmail.com (Jonatan Lindblad)
Date: Sat, 2 Mar 2019 17:32:19 +0100
Subject: [mythtv-users] MythTV miscalculates the amount of free disk
 space
In-Reply-To: <52be7619-49ac-a215-d7eb-778c14d67733@gmail.com>
References: <762d3af4-7a04-f48c-afb5-9ed8d6ecf71f@gmail.com>
 <bf6a3d79-c50f-ee57-b9e7-f6c32bb07744@sky.com>
 <52be7619-49ac-a215-d7eb-778c14d67733@gmail.com>
Message-ID: <b8497955-eb21-2a57-f066-3851fd376a4f@gmail.com>

Den 2019-03-02 kl. 12:58, skrev Jan Ceuleers:
> On 02/03/2019 12:36, Paul Harrison wrote:
>> Since both drives are empty and otherwise identical, mythbackend can't
>> tell them apart. For all it knows the mounts point to the exact same
>> drive. Until there is content on one or both of the drives it's unable
>> to tell them apart.
> 
> Thanks Paul.
> 
> Sounds like a bug to me though. I thought that the backend verified it
> could write to each storage group by creating temporary files, so if
> that's correct it would also be an opportunity for it to find out
> whether directories it thinks are the same are in fact.

Nope, it is not a bug.  See this thread for example https://lists.gt.net/mythtv/users/280821#280821

Cheers
Jonatan

From jan.ceuleers at gmail.com  Sat Mar  2 16:38:06 2019
From: jan.ceuleers at gmail.com (Jan Ceuleers)
Date: Sat, 2 Mar 2019 17:38:06 +0100
Subject: [mythtv-users] MythTV miscalculates the amount of free disk
 space
In-Reply-To: <b8497955-eb21-2a57-f066-3851fd376a4f@gmail.com>
References: <762d3af4-7a04-f48c-afb5-9ed8d6ecf71f@gmail.com>
 <bf6a3d79-c50f-ee57-b9e7-f6c32bb07744@sky.com>
 <52be7619-49ac-a215-d7eb-778c14d67733@gmail.com>
 <b8497955-eb21-2a57-f066-3851fd376a4f@gmail.com>
Message-ID: <a8f805f3-3cdd-f102-167b-3bde91f568a4@gmail.com>

On 02/03/2019 17:32, Jonatan Lindblad wrote:
> Den 2019-03-02 kl. 12:58, skrev Jan Ceuleers:
>> On 02/03/2019 12:36, Paul Harrison wrote:
>>> Since both drives are empty and otherwise identical, mythbackend can't
>>> tell them apart. For all it knows the mounts point to the exact same
>>> drive. Until there is content on one or both of the drives it's unable
>>> to tell them apart.
>>
>> Thanks Paul.
>>
>> Sounds like a bug to me though. I thought that the backend verified it
>> could write to each storage group by creating temporary files, so if
>> that's correct it would also be an opportunity for it to find out
>> whether directories it thinks are the same are in fact.
> 
> Nope, it is not a bug.  See this thread for example https://lists.gt.net/mythtv/users/280821#280821

Thanks Jonathan. Now that a recording has been stored on one of these
new disks the backend does indeed recognise the disks as separate.

Still looks like a bug to me though, even if it works as designed.

Anyway, case closed - thanks.

From barry3martin at gmail.com  Sat Mar  2 17:15:57 2019
From: barry3martin at gmail.com (Barry Martin)
Date: Sat, 2 Mar 2019 11:15:57 -0600
Subject: [mythtv-users] Hauppauge WinTV-quadHD TV Tuner Card 1609 and
 mulrirec
In-Reply-To: <mailman.189.1551527934.1689.mythtv-users@mythtv.org>
References: <mailman.189.1551527934.1689.mythtv-users@mythtv.org>
Message-ID: <d46391db-e53d-1213-cb8a-a762bb2a0d04@gmail.com>


Hi Per!


> I've been using the quadHD since late 2015 and it is one of the best tuners
> I've ever had!

In hindsight it could sound like an advertisement but that is pretty 
much the kind of first-hand information I like: ?it works great? - 
so-so. ?It works great compared to? will perk my ears. Or eyes. Others? 
antenna considerations, signal transmission and loss, etc., are all good 
reminders. And I did learn more about antenna gain and beam width.

Anyway, the 1609 does sound like it resolve most of my reception issues 
? another step in the right direction!

Thanks to all!

Barry

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190302/70ec392e/attachment.html>

From barry3martin at gmail.com  Sat Mar  2 17:16:57 2019
From: barry3martin at gmail.com (Barry Martin)
Date: Sat, 2 Mar 2019 11:16:57 -0600
Subject: [mythtv-users] Hauppauge WinTV-quadHD TV Tuner Card 1609 and
 mulrirec
In-Reply-To: <mailman.189.1551527934.1689.mythtv-users@mythtv.org>
References: <mailman.189.1551527934.1689.mythtv-users@mythtv.org>
Message-ID: <47ac518b-e663-9c06-3a4f-78c2c46bf48b@gmail.com>


Hi Ian!


> Thanks. Though you don't know how much it hurt when I hit Send and realized
> the subject line said "mulrirec" instead of "multirec". Big thumbs on the
> phone.

Gee, and here I thought you did that spelling on purpose to have 
uniqueness in your title!

Barry

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190302/20a63527/attachment.html>

From pb.mythtv at gmail.com  Sat Mar  2 17:31:24 2019
From: pb.mythtv at gmail.com (Peter Bennett)
Date: Sat, 2 Mar 2019 12:31:24 -0500
Subject: [mythtv-users] missing keybinds on some FE's
In-Reply-To: <1693e227421.f1de53c2173359.4083304163391863266@zoho.com>
References: <1693e227421.f1de53c2173359.4083304163391863266@zoho.com>
Message-ID: <8b8e3c09-df25-130c-7045-153eeb21bf4d@gmail.com>



On 3/2/19 6:21 AM, Tim Draper wrote:
> i've a number of FE's in my mythtv deployment and i've just come to 
> upgrade the last one to v30.
> TOGGLEBOOKMARK keybind has reset to null on all the other FE's i've 
> upgraded so i've gone in to rebind it on this last FE, via mythweb 
> interface. It's missing - simply not there.
> Also noticed a missing jumppoint on those that miss TOGGLEBOOKMARK; 
> 'Live TV In Guide'. There could be more discrepencies but 
> TOGGLEBOOKMARK is the one i specifically need.
>
> Over the years i've accumulated a number of other FE names that remain 
> in the db and appears half of them have TOGGLEBOOKMARK keybind, and 
> half don't. There doesnt appear to be any consistency between those 
> that do and don't.
>
> is there a way to fix? worth a bug report? or shall i dig out the info 
> on how to remove an FE from the DB and start again?
>
>
> thanks,
> Tim
>
>
> _______________________________________________
>
TOGGLEBOOKMARK is a new feature with V30, so you won't find it in V29. 
There is also a new key assignment SETBOOKMARK. The difference is 
SETBOOKMARK always sets a bookmark even if already set.

There is no default setting for these keys so on a new frontend, they 
must be explicitly assigned. Previously the select key (space/enter) was 
always used to set bookmarks with no ability to change space/enter to 
something else, so now there is flexibility on the use of space and enter.

Key assignments should not disappear from a frontend once set.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190302/366864ae/attachment.html>

From jsbien at mimuw.edu.pl  Sat Mar  2 17:51:14 2019
From: jsbien at mimuw.edu.pl (Janusz S. =?utf-8?Q?Bie=C5=84?=)
Date: Sat, 02 Mar 2019 18:51:14 +0100
Subject: [mythtv-users] missing keybinds on some FE's
In-Reply-To: <8b8e3c09-df25-130c-7045-153eeb21bf4d@gmail.com> (Peter Bennett's
 message of "Sat, 2 Mar 2019 12:31:24 -0500")
References: <1693e227421.f1de53c2173359.4083304163391863266@zoho.com>
 <8b8e3c09-df25-130c-7045-153eeb21bf4d@gmail.com>
Message-ID: <86tvglxizx.fsf@mimuw.edu.pl>

On Sat, Mar 02 2019 at 12:31 -05, Peter Bennett wrote:

[...]

> TOGGLEBOOKMARK is a new feature with V30, so you won't find it in
> V29.

But Space was toggling the bookmark, if I remember well.

> There is also a new key assignment SETBOOKMARK. The difference is
> SETBOOKMARK always sets a bookmark even if already set.

Am I right that there is no CLEARBOOKMARK or something equivalent?

Best regards

Janusz

-- 
             ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

From jfabernathy at gmail.com  Sat Mar  2 18:06:21 2019
From: jfabernathy at gmail.com (James Abernathy)
Date: Sat, 2 Mar 2019 13:06:21 -0500
Subject: [mythtv-users] adding HDHR to system
In-Reply-To: <be82fc21-029f-ee87-be24-ca2c6135f0ec@gmail.com>
References: <be82fc21-029f-ee87-be24-ca2c6135f0ec@gmail.com>
Message-ID: <37e2f44e-bbd7-0557-d933-f3c8ba8183b4@gmail.com>


On 2/26/19 5:55 PM, Jim Abernathy wrote:
> Last project was eliminating my HDHR Quatro and replacing it with a 
> Hauppauge WinTV Quad.
>
> That is complete and I'm using XMLTV sdjson_sqlite grabber.? At this 
> point I'm stable, but on occasions I'm recording on all 4 channels of 
> the WinTV and thought about adding the Quatro back for Live TV only.
>
> I can use the HDHomerun Viewer to watch live tv on the Quatro, but 
> it's not integrated with Mythtv.
>
> So my question is can I add the Quatro back into mythtv using the 
> Blackbox external recorder, mythhdhrrecorder, and still use my exiting 
> EPG database I setup for the WinTV using tv_grab_zz_sdjson_sqlite. I 
> don't want to screw up my exiting recordings or pending recordings. 
> Can I setup the mythtvhdhrrecorder to use my existing SD XMLTV source 
> or do I have to have a new video source just for the mythhdhrrecorder???
>
> Jim A
>
I did some experimenting and I found that you can NOT just add a 
mythhdhrrecorder tuner and have it use the existing Video Source used by 
other tuners (WinTV QuadHD). It fails on open.

So my question: Is there a requirement that each Capture Card have its 
own separate Video Source defined even if each Video Source is using 
SchedulesDirect XMLTV sdjson grabber_sqlite? My assumption is a 4 tuner 
card would use the same video source for all 4 tuners. Possibly if you 
had 2 exact same model Capture Cards then they they might use the same 
Video Source.

Are there any hard and fast rules on when you can use the same video 
source??

Jim A



From oliver.greg at gmail.com  Sat Mar  2 18:29:28 2019
From: oliver.greg at gmail.com (Greg Oliver)
Date: Sat, 2 Mar 2019 12:29:28 -0600
Subject: [mythtv-users] adding HDHR to system
In-Reply-To: <37e2f44e-bbd7-0557-d933-f3c8ba8183b4@gmail.com>
References: <be82fc21-029f-ee87-be24-ca2c6135f0ec@gmail.com>
 <37e2f44e-bbd7-0557-d933-f3c8ba8183b4@gmail.com>
Message-ID: <CAF4tN+_thH394km7JfYGYpx1_91Rqd93ZfM4dkMNkS8WwrDEgA@mail.gmail.com>

On Sat, Mar 2, 2019 at 12:07 PM James Abernathy <jfabernathy at gmail.com>
wrote:

> On 2/26/19 5:55 PM, Jim Abernathy wrote:
> > Last project was eliminating my HDHR Quatro and replacing it with a
> > Hauppauge WinTV Quad.
> >
> > That is complete and I'm using XMLTV sdjson_sqlite grabber.  At this
> > point I'm stable, but on occasions I'm recording on all 4 channels of
> > the WinTV and thought about adding the Quatro back for Live TV only.
> >
> > I can use the HDHomerun Viewer to watch live tv on the Quatro, but
> > it's not integrated with Mythtv.
> >
> > So my question is can I add the Quatro back into mythtv using the
> > Blackbox external recorder, mythhdhrrecorder, and still use my exiting
> > EPG database I setup for the WinTV using tv_grab_zz_sdjson_sqlite. I
> > don't want to screw up my exiting recordings or pending recordings.
> > Can I setup the mythtvhdhrrecorder to use my existing SD XMLTV source
> > or do I have to have a new video source just for the mythhdhrrecorder???
> >
> > Jim A
> >
> I did some experimenting and I found that you can NOT just add a
> mythhdhrrecorder tuner and have it use the existing Video Source used by
> other tuners (WinTV QuadHD). It fails on open.
>
> So my question: Is there a requirement that each Capture Card have its
> own separate Video Source defined even if each Video Source is using
> SchedulesDirect XMLTV sdjson grabber_sqlite? My assumption is a 4 tuner
> card would use the same video source for all 4 tuners. Possibly if you
> had 2 exact same model Capture Cards then they they might use the same
> Video Source.
>
> Are there any hard and fast rules on when you can use the same video
> source??
>
> Jim A

There must be something else going on there because I have done exactly
what you describe several times.

I have 3 lineups - one for OTA US (zipcode), 1 for DirecTV and 1 for
uVerse.  I can bind the OTA lineup to any number of cards/HDHRs
simultaneously without issue.  Is there anything else in the log when you
fire the backend back up?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190302/eeb69059/attachment.html>

From jfabernathy at gmail.com  Sat Mar  2 18:40:43 2019
From: jfabernathy at gmail.com (James Abernathy)
Date: Sat, 2 Mar 2019 13:40:43 -0500
Subject: [mythtv-users] adding HDHR to system
In-Reply-To: <CAF4tN+_thH394km7JfYGYpx1_91Rqd93ZfM4dkMNkS8WwrDEgA@mail.gmail.com>
References: <be82fc21-029f-ee87-be24-ca2c6135f0ec@gmail.com>
 <37e2f44e-bbd7-0557-d933-f3c8ba8183b4@gmail.com>
 <CAF4tN+_thH394km7JfYGYpx1_91Rqd93ZfM4dkMNkS8WwrDEgA@mail.gmail.com>
Message-ID: <b37e0a8e-900c-af07-a15b-0f2631f75c1c@gmail.com>


On 3/2/19 1:29 PM, Greg Oliver wrote:
> On Sat, Mar 2, 2019 at 12:07 PM James Abernathy <jfabernathy at gmail.com 
> <mailto:jfabernathy at gmail.com>> wrote:
>
>     On 2/26/19 5:55 PM, Jim Abernathy wrote:
>     > Last project was eliminating my HDHR Quatro and replacing it with a
>     > Hauppauge WinTV Quad.
>     >
>     > That is complete and I'm using XMLTV sdjson_sqlite grabber.? At
>     this
>     > point I'm stable, but on occasions I'm recording on all 4
>     channels of
>     > the WinTV and thought about adding the Quatro back for Live TV only.
>     >
>     > I can use the HDHomerun Viewer to watch live tv on the Quatro, but
>     > it's not integrated with Mythtv.
>     >
>     > So my question is can I add the Quatro back into mythtv using the
>     > Blackbox external recorder, mythhdhrrecorder, and still use my
>     exiting
>     > EPG database I setup for the WinTV using
>     tv_grab_zz_sdjson_sqlite. I
>     > don't want to screw up my exiting recordings or pending recordings.
>     > Can I setup the mythtvhdhrrecorder to use my existing SD XMLTV
>     source
>     > or do I have to have a new video source just for the
>     mythhdhrrecorder???
>     >
>     > Jim A
>     >
>     I did some experimenting and I found that you can NOT just add a
>     mythhdhrrecorder tuner and have it use the existing Video Source
>     used by
>     other tuners (WinTV QuadHD). It fails on open.
>
>     So my question: Is there a requirement that each Capture Card have
>     its
>     own separate Video Source defined even if each Video Source is using
>     SchedulesDirect XMLTV sdjson grabber_sqlite? My assumption is a 4
>     tuner
>     card would use the same video source for all 4 tuners. Possibly if
>     you
>     had 2 exact same model Capture Cards then they they might use the
>     same
>     Video Source.
>
>     Are there any hard and fast rules on when you can use the same video
>     source??
>
>     Jim A
>
> There must be something else going on there because I have done 
> exactly what you describe several times.
>
> I have 3 lineups - one for OTA US (zipcode), 1 for DirecTV and 1 for 
> uVerse. I can bind the OTA lineup to any number of cards/HDHRs 
> simultaneously without issue.? Is there anything else in the log when 
> you fire the backend back up?


I think this issue is specific to using the Blackbox external recorder, 
mythhdhrrecorder. I went back and add the HDHR as HDHR tuners and just 
created Input Connections for these tuners using the existing SD video 
source and it worked fine.

So I guess if I want to use the mythhdhrrecorder for it's TCP/IP usage 
of the HDHR, then I'll have to rebuild from the ground up and define one 
video source for the tuners on mythhdhrrecorder and one for the 
hauppauge WinTV quad.

Which I will not do, so I'll stuck the what I have.

Jim A


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190302/a88c25fb/attachment.html>

From pb.mythtv at gmail.com  Sat Mar  2 20:33:08 2019
From: pb.mythtv at gmail.com (Peter Bennett)
Date: Sat, 2 Mar 2019 15:33:08 -0500
Subject: [mythtv-users] missing keybinds on some FE's
In-Reply-To: <86tvglxizx.fsf@mimuw.edu.pl>
References: <1693e227421.f1de53c2173359.4083304163391863266@zoho.com>
 <8b8e3c09-df25-130c-7045-153eeb21bf4d@gmail.com>
 <86tvglxizx.fsf@mimuw.edu.pl>
Message-ID: <ba11e67c-2700-3cc4-3f08-0818ba7157ad@gmail.com>



On 3/2/19 12:51 PM, Janusz S. Bie? wrote:
> Am I right that there is no CLEARBOOKMARK or something equivalent?
If you press M (menu) while in the recording list and a recording is 
selected, if there is a bookmark it shows a "Clear bookmark" option.

From david at istwok.net  Sat Mar  2 21:06:32 2019
From: david at istwok.net (David Engel)
Date: Sat, 2 Mar 2019 15:06:32 -0600
Subject: [mythtv-users] adding HDHR to system
In-Reply-To: <b37e0a8e-900c-af07-a15b-0f2631f75c1c@gmail.com>
References: <be82fc21-029f-ee87-be24-ca2c6135f0ec@gmail.com>
 <37e2f44e-bbd7-0557-d933-f3c8ba8183b4@gmail.com>
 <CAF4tN+_thH394km7JfYGYpx1_91Rqd93ZfM4dkMNkS8WwrDEgA@mail.gmail.com>
 <b37e0a8e-900c-af07-a15b-0f2631f75c1c@gmail.com>
Message-ID: <20190302210632.GA4807@opus.istwok.net>

On Sat, Mar 02, 2019 at 01:40:43PM -0500, James Abernathy wrote:
> 
> On 3/2/19 1:29 PM, Greg Oliver wrote:
> > On Sat, Mar 2, 2019 at 12:07 PM James Abernathy <jfabernathy at gmail.com
> > <mailto:jfabernathy at gmail.com>> wrote:
> > 
> >     On 2/26/19 5:55 PM, Jim Abernathy wrote:
> >     > Last project was eliminating my HDHR Quatro and replacing it with a
> >     > Hauppauge WinTV Quad.
> >     >
> >     > That is complete and I'm using XMLTV sdjson_sqlite grabber.? At
> >     this
> >     > point I'm stable, but on occasions I'm recording on all 4
> >     channels of
> >     > the WinTV and thought about adding the Quatro back for Live TV only.
> >     >
> >     > I can use the HDHomerun Viewer to watch live tv on the Quatro, but
> >     > it's not integrated with Mythtv.
> >     >
> >     > So my question is can I add the Quatro back into mythtv using the
> >     > Blackbox external recorder, mythhdhrrecorder, and still use my
> >     exiting
> >     > EPG database I setup for the WinTV using
> >     tv_grab_zz_sdjson_sqlite. I
> >     > don't want to screw up my exiting recordings or pending recordings.
> >     > Can I setup the mythtvhdhrrecorder to use my existing SD XMLTV
> >     source
> >     > or do I have to have a new video source just for the
> >     mythhdhrrecorder???
> >     >
> >     > Jim A
> >     >
> >     I did some experimenting and I found that you can NOT just add a
> >     mythhdhrrecorder tuner and have it use the existing Video Source
> >     used by
> >     other tuners (WinTV QuadHD). It fails on open.
> > 
> >     So my question: Is there a requirement that each Capture Card have
> >     its
> >     own separate Video Source defined even if each Video Source is using
> >     SchedulesDirect XMLTV sdjson grabber_sqlite? My assumption is a 4
> >     tuner
> >     card would use the same video source for all 4 tuners. Possibly if
> >     you
> >     had 2 exact same model Capture Cards then they they might use the
> >     same
> >     Video Source.
> > 
> >     Are there any hard and fast rules on when you can use the same video
> >     source??
> > 
> >     Jim A
> > 
> > There must be something else going on there because I have done exactly
> > what you describe several times.
> > 
> > I have 3 lineups - one for OTA US (zipcode), 1 for DirecTV and 1 for
> > uVerse. I can bind the OTA lineup to any number of cards/HDHRs
> > simultaneously without issue.? Is there anything else in the log when
> > you fire the backend back up?
> 
> 
> I think this issue is specific to using the Blackbox external recorder,
> mythhdhrrecorder. I went back and add the HDHR as HDHR tuners and just
> created Input Connections for these tuners using the existing SD video
> source and it worked fine.
> 
> So I guess if I want to use the mythhdhrrecorder for it's TCP/IP usage of
> the HDHR, then I'll have to rebuild from the ground up and define one video
> source for the tuners on mythhdhrrecorder and one for the hauppauge WinTV
> quad.
> 
> Which I will not do, so I'll stuck the what I have.

mythhdhrrecorder only supports tuning by virtual channel number.  Your
Hauppauge WinTV almost certainly only supports tuning by
frequency/program tuning so it can't share the same videosource with
mythhdhrrecorder.  The internal, HDHR recorder supports both virtual
channel number and frequency/program tuning so it can share the same
videosource with your Hauppauge WinTV.

David
-- 
David Engel
david at istwok.net

From jfabernathy at gmail.com  Sat Mar  2 21:13:52 2019
From: jfabernathy at gmail.com (James Abernathy)
Date: Sat, 2 Mar 2019 16:13:52 -0500
Subject: [mythtv-users] adding HDHR to system
In-Reply-To: <20190302210632.GA4807@opus.istwok.net>
References: <be82fc21-029f-ee87-be24-ca2c6135f0ec@gmail.com>
 <37e2f44e-bbd7-0557-d933-f3c8ba8183b4@gmail.com>
 <CAF4tN+_thH394km7JfYGYpx1_91Rqd93ZfM4dkMNkS8WwrDEgA@mail.gmail.com>
 <b37e0a8e-900c-af07-a15b-0f2631f75c1c@gmail.com>
 <20190302210632.GA4807@opus.istwok.net>
Message-ID: <CANFv2Ek5hg2M0wsAFLE7tMgWqwbodEx-VmyS3OO0wVTpBmwOQg@mail.gmail.com>

On Sat, Mar 2, 2019, 4:07 PM David Engel <david at istwok.net> wrote:

> On Sat, Mar 02, 2019 at 01:40:43PM -0500, James Abernathy wrote:
> >
> > On 3/2/19 1:29 PM, Greg Oliver wrote:
> > > On Sat, Mar 2, 2019 at 12:07 PM James Abernathy <jfabernathy at gmail.com
> > > <mailto:jfabernathy at gmail.com>> wrote:
> > >
> > >     On 2/26/19 5:55 PM, Jim Abernathy wrote:
> > >     > Last project was eliminating my HDHR Quatro and replacing it
> with a
> > >     > Hauppauge WinTV Quad.
> > >     >
> > >     > That is complete and I'm using XMLTV sdjson_sqlite grabber.  At
> > >     this
> > >     > point I'm stable, but on occasions I'm recording on all 4
> > >     channels of
> > >     > the WinTV and thought about adding the Quatro back for Live TV
> only.
> > >     >
> > >     > I can use the HDHomerun Viewer to watch live tv on the Quatro,
> but
> > >     > it's not integrated with Mythtv.
> > >     >
> > >     > So my question is can I add the Quatro back into mythtv using the
> > >     > Blackbox external recorder, mythhdhrrecorder, and still use my
> > >     exiting
> > >     > EPG database I setup for the WinTV using
> > >     tv_grab_zz_sdjson_sqlite. I
> > >     > don't want to screw up my exiting recordings or pending
> recordings.
> > >     > Can I setup the mythtvhdhrrecorder to use my existing SD XMLTV
> > >     source
> > >     > or do I have to have a new video source just for the
> > >     mythhdhrrecorder???
> > >     >
> > >     > Jim A
> > >     >
> > >     I did some experimenting and I found that you can NOT just add a
> > >     mythhdhrrecorder tuner and have it use the existing Video Source
> > >     used by
> > >     other tuners (WinTV QuadHD). It fails on open.
> > >
> > >     So my question: Is there a requirement that each Capture Card have
> > >     its
> > >     own separate Video Source defined even if each Video Source is
> using
> > >     SchedulesDirect XMLTV sdjson grabber_sqlite? My assumption is a 4
> > >     tuner
> > >     card would use the same video source for all 4 tuners. Possibly if
> > >     you
> > >     had 2 exact same model Capture Cards then they they might use the
> > >     same
> > >     Video Source.
> > >
> > >     Are there any hard and fast rules on when you can use the same
> video
> > >     source??
> > >
> > >     Jim A
> > >
> > > There must be something else going on there because I have done exactly
> > > what you describe several times.
> > >
> > > I have 3 lineups - one for OTA US (zipcode), 1 for DirecTV and 1 for
> > > uVerse. I can bind the OTA lineup to any number of cards/HDHRs
> > > simultaneously without issue.  Is there anything else in the log when
> > > you fire the backend back up?
> >
> >
> > I think this issue is specific to using the Blackbox external recorder,
> > mythhdhrrecorder. I went back and add the HDHR as HDHR tuners and just
> > created Input Connections for these tuners using the existing SD video
> > source and it worked fine.
> >
> > So I guess if I want to use the mythhdhrrecorder for it's TCP/IP usage of
> > the HDHR, then I'll have to rebuild from the ground up and define one
> video
> > source for the tuners on mythhdhrrecorder and one for the hauppauge WinTV
> > quad.
> >
> > Which I will not do, so I'll stuck the what I have.
>
> mythhdhrrecorder only supports tuning by virtual channel number.  Your
> Hauppauge WinTV almost certainly only supports tuning by
> frequency/program tuning so it can't share the same videosource with
> mythhdhrrecorder.  The internal, HDHR recorder supports both virtual
> channel number and frequency/program tuning so it can share the same
> videosource with your Hauppauge WinTV.
>
> David
> --
> David Engel
> david at istwok.net
>
>
> Thanks for the explanation. Makes sense.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190302/bd2f447e/attachment.html>

From km at mathcs.emory.edu  Sat Mar  2 21:44:57 2019
From: km at mathcs.emory.edu (Ken Mandelberg)
Date: Sat, 2 Mar 2019 16:44:57 -0500
Subject: [mythtv-users] Daily mythfilldatabase fails after conversion to
 XMLTV
Message-ID: <522ace10-5870-6d50-0d94-b3cced1f7eb9@mathcs.emory.edu>

I recently converted from DataDirect to XMLTV. If I run mythfilldatabase 
by hand it works. But the daily version fails. The backend log shows

2019-03-02 08:14:18.077579 D [1475/1475] CoreContext 
backendhousekeeper.cpp:686 (DoCheckRun) - MythFillDatabase scheduled to 
run at Sat Mar 2 13:18:31 2019 GMT.

and then the  status page shows

Last mythfilldatabase run started on Sat Mar 2, 8:19 AM and ended on Sat 
Mar 2, 8:19 AM. FAILED: XMLTV grabber returned error code 1.
Suggested next mythfilldatabase run: Sun Mar 3, 8:19 AM.
There's guide data until 2019-03-21 01:30:00 (19 days).
DataDirect Status: Unavailable with SD JSON XMLTV

There is no obvious log for mythfilldatabase itself or the grabber.

My first thought is PATH. The grabbers are in /usr/bin and the build is 
is in /usr/local (I build the trunk). Since everything else works, I 
don't think its the execution PATH. Maybe its some library thats in my 
login environment but not in myths daemon.

Thoughts?

From stse+mythtv at fsing.rootsland.net  Sat Mar  2 21:46:08 2019
From: stse+mythtv at fsing.rootsland.net (Stephan Seitz)
Date: Sat, 2 Mar 2019 22:46:08 +0100
Subject: [mythtv-users] No DVB-C channels anymore
In-Reply-To: <13586cd7-ae45-bf50-a83a-bd908d08a3ae@free-it.ch>
References: <20190228T183358.GA.590a9.stse@fsing.rootsland.net>
 <13586cd7-ae45-bf50-a83a-bd908d08a3ae@free-it.ch>
Message-ID: <20190302T224441.GA.ee586.stse@fsing.rootsland.net>

On Fr, M?r 01, 2019 at 08:39:02 +0100, Yann Lehmann wrote:
>Did you let it enough time to achieve ? I had a Digital Device dual

Well, MythTV said it had finished scanning without finding any channels.

I tried every scan option.

Shade and sweet water!

	Stephan

-- 
| Public Keys: http://fsing.rootsland.net/~stse/keys.html |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3545 bytes
Desc: not available
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190302/0423c10e/attachment.p7s>

From david at istwok.net  Sat Mar  2 21:54:13 2019
From: david at istwok.net (David Engel)
Date: Sat, 2 Mar 2019 15:54:13 -0600
Subject: [mythtv-users] Daily mythfilldatabase fails after conversion to
 XMLTV
In-Reply-To: <522ace10-5870-6d50-0d94-b3cced1f7eb9@mathcs.emory.edu>
References: <522ace10-5870-6d50-0d94-b3cced1f7eb9@mathcs.emory.edu>
Message-ID: <20190302215413.GA15621@opus.istwok.net>

On Sat, Mar 02, 2019 at 04:44:57PM -0500, Ken Mandelberg wrote:
> I recently converted from DataDirect to XMLTV. If I run mythfilldatabase by
> hand it works. But the daily version fails. The backend log shows
> 
> 2019-03-02 08:14:18.077579 D [1475/1475] CoreContext
> backendhousekeeper.cpp:686 (DoCheckRun) - MythFillDatabase scheduled to run
> at Sat Mar 2 13:18:31 2019 GMT.
> 
> and then the  status page shows
> 
> Last mythfilldatabase run started on Sat Mar 2, 8:19 AM and ended on Sat Mar
> 2, 8:19 AM. FAILED: XMLTV grabber returned error code 1.
> Suggested next mythfilldatabase run: Sun Mar 3, 8:19 AM.
> There's guide data until 2019-03-21 01:30:00 (19 days).
> DataDirect Status: Unavailable with SD JSON XMLTV
> 
> There is no obvious log for mythfilldatabase itself or the grabber.
> 
> My first thought is PATH. The grabbers are in /usr/bin and the build is is
> in /usr/local (I build the trunk). Since everything else works, I don't
> think its the execution PATH. Maybe its some library thats in my login
> environment but not in myths daemon.
> 
> Thoughts?

Add "system" to your backend --verbose logging.

David
-- 
David Engel
david at istwok.net

From keemllib at gmail.com  Sat Mar  2 21:58:23 2019
From: keemllib at gmail.com (Bill Meek)
Date: Sat, 2 Mar 2019 15:58:23 -0600
Subject: [mythtv-users] Daily mythfilldatabase fails after conversion to
 XMLTV
In-Reply-To: <522ace10-5870-6d50-0d94-b3cced1f7eb9@mathcs.emory.edu>
References: <522ace10-5870-6d50-0d94-b3cced1f7eb9@mathcs.emory.edu>
Message-ID: <346b9af4-033b-e38b-92ca-5b3a05bbaca9@gmail.com>

On 3/2/19 3:44 PM, Ken Mandelberg wrote:
> 
> There?is?no?obvious?log?for?mythfilldatabase?itself?or?the?grabber.

curl -H Accept:application/json localhost:6544/Myth/GetSetting?Key=MythFillDatabasePath\&HostName=_GLOBAL_

See what the above returns on the backend. It should be exactly: mythfilldatabase,
not a full path name (or you can just fire up mythtv-setup and look there.)

If that allows the mythfilldatabase.log (or whatever logging choice you've made),
then try: mythbackend --setverbose xmltv.

-- 
Bill

From allen.p.edwards at gmail.com  Sat Mar  2 21:58:56 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Sat, 2 Mar 2019 13:58:56 -0800
Subject: [mythtv-users] Can't get my projector to work with Myth
Message-ID: <CAH8UtKOMT3uQXme1cK3d8JoK7S-Ta4abnkoEsTaHFQzyc1cW-g@mail.gmail.com>

Someone must know the answer to this really fast.

Myth has HDMI output connected to a TV at 1080 according to the TV. I want
to connect to my projector that is capable of a 1080 input.  I also have a
small monitor connected to Myth via RGB input but it also has a DVI input.
The cable to the projector is DVI but the projector is HDMI.

I inserted an audio stripper box so that my cables would work and with that
box I can play Myth into the TV just fine. I can connect and disconnect and
everything is happy. Myth is setup to not auto detect the monitor as that
caused all kind of problems. Maybe that is the problem but if I enable
whatever the hell that function is called, I just get black TV screen
because when the TV is turned off, Myth disconnects and never reconnects.

Bottom line is that if I insert the projector or monitor DVI cable into the
audio stripper instead of the TV, I get nothing.

I don't understand why the computer doesn't just output its signal and the
Projector detect it and display it.

I look in xorg.conf (is this still the right file? Probably not...) and I
see my monitor which is identified as a samsung, and the tv, which is not
identified so why should it care?. It has an output listed as 1920x1080
which the projector supports.

The goal is to be able to unplug the TV and plug in the projector and watch
the Oscars, or any other significant show on the big screen occasionally.
Normally the Projector is hooked up to a DVD player. I guess I could get a
new preamp that switched HDMI but that is a huge expense for something we
would only want to do a few times per year.

Anyone know what I should do?

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190302/0bc515af/attachment.html>

From dizygotheca at ntlworld.com  Sat Mar  2 23:35:19 2019
From: dizygotheca at ntlworld.com (Roger Siddons)
Date: Sat, 2 Mar 2019 23:35:19 +0000
Subject: [mythtv-users] Active EIT data collection gives some defective
 recordings; passive scanning not working.
In-Reply-To: <vm6l7eds403faivj642nkolv98hbojmfaf@4ax.com>
References: <cdb83736-2fb6-89f0-df76-bb6da3063daf@gmail.com>
 <vm6l7eds403faivj642nkolv98hbojmfaf@4ax.com>
Message-ID: <20190302233519.0b3cc657@compaq>

On Sun, 03 Mar 2019 05:04:41 +1300
Stephen Worthington <stephen_agent at jsw.gen.nz> wrote:

> On Sat, 2 Mar 2019 14:09:19 +0000, you wrote:
> 
> >Recently the number of defects rose again.  

Most likely the recent weather
https://www.a516digital.com/2019/02/as-weather-disrupts-tv-reception.html

> >I tried disabling active scanning on *all* tuners.  I had understood 
> >that passive scanning would continue to collect EIT data, for all
> >muxes, as long as some recordings were being made 

I thought passive scanning only updates the mux (possibly
channel) of the recording. I'd expect to see 7 days for your popular
channels/muxes and eventually 0 for infrequent ones.

EIT might be cross-channel but that doesn't mean Myth uses it.
Otherwise why does the active scanner cycle through all channels ?

> > They seemed less frequent when I stopped active 
> > EIT scanning with the USB tuners, using only the PCI card.

Good move. I believe the option actually starts a new scanner on the
tuner rather than allowing the *solitary* scanner to use the tuner.
(Years ago there were issues with multiple scanners
conflicting/interfering, particularly on lower-quality dual USB tuners).

There's no reason to ever run more than 1 scanner on a video
source. "New" EIT data is frequent and the scheduler gets repeatedly
re-run pointlessly, which won't help your loads.

> In
> theory, it would be possible to get a tuner that is recording to also
> receive the EIT data at the same time, but I do not think MythTV does
> that.  

It does. 
http://lists.mythtv.org/pipermail/mythtv-users/2012-March/330012.html 

> However, I thought that use of a tuner for EIT reception gave
> way automatically when the tuner was needed for a recording, and
> started again automatically afterwards.
> 

Active scanning will stop and give up its tuner for recording or
shutdown.


From stephen_agent at jsw.gen.nz  Sun Mar  3 02:03:08 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Sun, 03 Mar 2019 15:03:08 +1300
Subject: [mythtv-users] Can't get my projector to work with Myth
In-Reply-To: <CAH8UtKOMT3uQXme1cK3d8JoK7S-Ta4abnkoEsTaHFQzyc1cW-g@mail.gmail.com>
References: <CAH8UtKOMT3uQXme1cK3d8JoK7S-Ta4abnkoEsTaHFQzyc1cW-g@mail.gmail.com>
Message-ID: <pmbm7e1u2mmam8t659n0ch7o5rv6qt655f@4ax.com>

On Sat, 2 Mar 2019 13:58:56 -0800, you wrote:

>Someone must know the answer to this really fast.
>
>Myth has HDMI output connected to a TV at 1080 according to the TV. I want
>to connect to my projector that is capable of a 1080 input.  I also have a
>small monitor connected to Myth via RGB input but it also has a DVI input.
>The cable to the projector is DVI but the projector is HDMI.
>
>I inserted an audio stripper box so that my cables would work and with that
>box I can play Myth into the TV just fine. I can connect and disconnect and
>everything is happy.

>Myth is setup to not auto detect the monitor as that
>caused all kind of problems. Maybe that is the problem but if I enable
>whatever the hell that function is called, I just get black TV screen
>because when the TV is turned off, Myth disconnects and never reconnects.

The problem of disconnection when the TV is off has a number of
different solutions, most of which have been mentioned on this list at
some time.  Your solution may not be the best one, as you do need to
detect the video device when it changes to something else. Suppressing
the DPMS screen blanking works for some people, and so does killing
one piece of software that I forget the name of.

>Bottom line is that if I insert the projector or monitor DVI cable into the
>audio stripper instead of the TV, I get nothing.

I am not familiar with audio strippers, but I presume that they will
have to decode the HDMI data, and do a digital to analogue conversion
of the audio data to analogue outputs.  I would have thought that they
would pass through the full HDMI data to the HDMI output, still
including the audio data.  But because of HDCP, they will have to
fully decode and re-encode the data, and unless that is done properly,
they may interfere with the normal detection of the video device.  So
I would recommend trying to connect without the stripper in place and
make that work before adding it back in again.  And I am not sure you
actually need the stripper.  Most PCs have a builtin sound card on the
motherboard with audio outputs.  You could be using that to send sound
to your amplifier.  That is what I do - I have the sound card set up
to send S/PDIF audio to my DAC which does the digital to analogue
conversion and sends it to my amplifier.  You can set things up so
that the audio is sent to both the sound card and to the HDMI audio
outputs at the same time.

>I don't understand why the computer doesn't just output its signal and the
>Projector detect it and display it.

The signal needs to be correct for the video device.  A signal that
works with the TV is not necessarily going to work with the projector.
Normally, when a new video device is connected, X will fetch the ID
and EDID data from the device and use that to determine the correct
format for the output data to the device.  It logs what it does, so
there may be information about your problem in your Xorg.?.log files.
Complicating matters is the problem that many video devices actually
send EDID data that is not completely correct, and that can then lead
to the need to override that bad data with xorg.conf settings.  The
fact that it "just works" with your TV simply means that you got lucky
and your TV works well.  Your projector may not be as good.

One thing to try is to shut down the MythTV box and plug in the
projector and boot using it only (no TV or monitor connected, no audio
splitter).  You should get the BIOS screens on the projector, and then
hopefully the PC will boot up properly and detect the projector and
work with it.  Then you can check the Xorg.0.log file and see what
works with the projector.  Repeat with the TV only, and compare the
two Xorg.0.log files and see what is different.

>I look in xorg.conf (is this still the right file? Probably not...) and I
>see my monitor which is identified as a samsung, and the tv, which is not
>identified so why should it care?. It has an output listed as 1920x1080
>which the projector supports.

Yes, xorg.conf is still normally the right place.  But you have not
told us what Linux distro you are using, or what your video card is.
Both matter in sorting out video output problems.  In the worst case,
you may need to have separate manually created sections in xorg.conf
for each of your video devices that specifies how to talk to them.

>The goal is to be able to unplug the TV and plug in the projector and watch
>the Oscars, or any other significant show on the big screen occasionally.
>Normally the Projector is hooked up to a DVD player. I guess I could get a
>new preamp that switched HDMI but that is a huge expense for something we
>would only want to do a few times per year.

And a new pre-amp would not necessarily fix the problem anyway.

>Anyone know what I should do?
>
>Allen

From allen.p.edwards at gmail.com  Sun Mar  3 04:42:03 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Sat, 2 Mar 2019 20:42:03 -0800
Subject: [mythtv-users] Can't get my projector to work with Myth
In-Reply-To: <pmbm7e1u2mmam8t659n0ch7o5rv6qt655f@4ax.com>
References: <CAH8UtKOMT3uQXme1cK3d8JoK7S-Ta4abnkoEsTaHFQzyc1cW-g@mail.gmail.com>
 <pmbm7e1u2mmam8t659n0ch7o5rv6qt655f@4ax.com>
Message-ID: <CAH8UtKOhuRFhFcL-ddQ-LSsfLUsZA+oLnTGmCbxjgPtY35JJfg@mail.gmail.com>

On Sat, Mar 2, 2019 at 6:03 PM Stephen Worthington <stephen_agent at jsw.gen.nz>
wrote:

> On Sat, 2 Mar 2019 13:58:56 -0800, you wrote:
>
> >Someone must know the answer to this really fast.
> >
> >Myth has HDMI output connected to a TV at 1080 according to the TV. I want
> >to connect to my projector that is capable of a 1080 input.  I also have a
> >small monitor connected to Myth via RGB input but it also has a DVI input.
> >The cable to the projector is DVI but the projector is HDMI.
> >
> >I inserted an audio stripper box so that my cables would work and with
> that
> >box I can play Myth into the TV just fine. I can connect and disconnect
> and
> >everything is happy.
>
> >Myth is setup to not auto detect the monitor as that
> >caused all kind of problems. Maybe that is the problem but if I enable
> >whatever the hell that function is called, I just get black TV screen
> >because when the TV is turned off, Myth disconnects and never reconnects.
>
> The problem of disconnection when the TV is off has a number of
> different solutions, most of which have been mentioned on this list at
> some time.  Your solution may not be the best one, as you do need to
> detect the video device when it changes to something else. Suppressing
> the DPMS screen blanking works for some people, and so does killing
> one piece of software that I forget the name of.
>
> >Bottom line is that if I insert the projector or monitor DVI cable into
> the
> >audio stripper instead of the TV, I get nothing.
>
> I am not familiar with audio strippers, but I presume that they will
> have to decode the HDMI data, and do a digital to analogue conversion
> of the audio data to analogue outputs.  I would have thought that they
> would pass through the full HDMI data to the HDMI output, still
> including the audio data.  But because of HDCP, they will have to
> fully decode and re-encode the data, and unless that is done properly,
> they may interfere with the normal detection of the video device.  So
> I would recommend trying to connect without the stripper in place and
> make that work before adding it back in again.  And I am not sure you
> actually need the stripper.  Most PCs have a builtin sound card on the
> motherboard with audio outputs.  You could be using that to send sound
> to your amplifier.  That is what I do - I have the sound card set up
> to send S/PDIF audio to my DAC which does the digital to analogue
> conversion and sends it to my amplifier.  You can set things up so
> that the audio is sent to both the sound card and to the HDMI audio
> outputs at the same time.
>
> >I don't understand why the computer doesn't just output its signal and the
> >Projector detect it and display it.
>
> The signal needs to be correct for the video device.  A signal that
> works with the TV is not necessarily going to work with the projector.
> Normally, when a new video device is connected, X will fetch the ID
> and EDID data from the device and use that to determine the correct
> format for the output data to the device.  It logs what it does, so
> there may be information about your problem in your Xorg.?.log files.
> Complicating matters is the problem that many video devices actually
> send EDID data that is not completely correct, and that can then lead
> to the need to override that bad data with xorg.conf settings.  The
> fact that it "just works" with your TV simply means that you got lucky
> and your TV works well.  Your projector may not be as good.
>
> One thing to try is to shut down the MythTV box and plug in the
> projector and boot using it only (no TV or monitor connected, no audio
> splitter).  You should get the BIOS screens on the projector, and then
> hopefully the PC will boot up properly and detect the projector and
> work with it.  Then you can check the Xorg.0.log file and see what
> works with the projector.  Repeat with the TV only, and compare the
> two Xorg.0.log files and see what is different.
>
> >I look in xorg.conf (is this still the right file? Probably not...) and I
> >see my monitor which is identified as a samsung, and the tv, which is not
> >identified so why should it care?. It has an output listed as 1920x1080
> >which the projector supports.
>
> Yes, xorg.conf is still normally the right place.  But you have not
> told us what Linux distro you are using, or what your video card is.
> Both matter in sorting out video output problems.  In the worst case,
> you may need to have separate manually created sections in xorg.conf
> for each of your video devices that specifies how to talk to them.
>
> >The goal is to be able to unplug the TV and plug in the projector and
> watch
> >the Oscars, or any other significant show on the big screen occasionally.
> >Normally the Projector is hooked up to a DVD player. I guess I could get a
> >new preamp that switched HDMI but that is a huge expense for something we
> >would only want to do a few times per year.
>
> And a new pre-amp would not necessarily fix the problem anyway.
>
> >Anyone know what I should do?
> >
> >Allen
>

I think the problem is that I misread the specification on the projector.
While it says that it does 1080p, the maximum data rate is 1280x720 so the
1080p must be with an analog input.  Same with the monitor. It has a native
resolution of 1280 x 1024.  Per the recommendation of everyone here, I set
the TV up from my initial setup of 1280x720 to 1920x1280 when I upgraded to
Mythbuntu-16.

Option         "metamodes" "VGA-0: nvidia-auto-select +0+0, HDMI-0:
1920x1080 +1280+0"

When I was running Mythbuntu-8 which drove the projector and the TV just
fine, I had everything set to 1280x720 as that is all the TV signal is
anyway.

So now I have to decide if I want to use the TV at 1920x1080 or downres so
I can use the projector a few times a year or find some way to have the
computer auto detect without turning the TV black. I believe there was also
an issue with the Sony sending bad EDID data. I just read something about
auto detecting 1360x768 instead of something useful.  Might be a different
model but I recall there was an issue. Maybe there is a way to have X pick
between 1280x720 and 1920x1024???

The video card is "GeForce GTX 750 Ti"

Well, I think I am at least understanding why it doesn't work.

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190302/77affd57/attachment.html>

From johnpilk222 at gmail.com  Sun Mar  3 11:53:16 2019
From: johnpilk222 at gmail.com (John Pilkington)
Date: Sun, 3 Mar 2019 11:53:16 +0000
Subject: [mythtv-users] Can't get my projector to work with Myth
In-Reply-To: <CAH8UtKOhuRFhFcL-ddQ-LSsfLUsZA+oLnTGmCbxjgPtY35JJfg@mail.gmail.com>
References: <CAH8UtKOMT3uQXme1cK3d8JoK7S-Ta4abnkoEsTaHFQzyc1cW-g@mail.gmail.com>
 <pmbm7e1u2mmam8t659n0ch7o5rv6qt655f@4ax.com>
 <CAH8UtKOhuRFhFcL-ddQ-LSsfLUsZA+oLnTGmCbxjgPtY35JJfg@mail.gmail.com>
Message-ID: <e6f51d3c-357a-43af-ad5c-e81a14ddad81@gmail.com>

On 03/03/2019 04:42, Allen Edwards wrote:

> I think the problem is that I misread the specification on the 
> projector.? While it says that it does 1080p, the maximum data rate is 
> 1280x720 so the 1080p must be with an analog input.? Same with the 
> monitor. It has a native resolution of 1280 x 1024.? Per the 
> recommendation of everyone here, I set the TV up from my initial setup 
> of 1280x720 to 1920x1280 when I upgraded to Mythbuntu-16.
> 
> Option? ? ? ? ?"metamodes" "VGA-0: nvidia-auto-select +0+0, HDMI-0: 
> 1920x1080 +1280+0"

My box running Fedora 28  with a GT710 has

Option "metamodes" "HDMI-0: 1920x1080_50 +1680+0, VGA-0: 1680x1050_60 +0+0"

The TV appears physically to the right of the 1680x1050 monitor.

I have my default mythfrontend on the monitor under kde, set to 
windowed, 1024x576 +64+64, started from a konsole tab as  "mythfrontend"

To get display on the TV I quit that instance and run "mythfrontend -nw 
--geometry 1920x1080+1680+0" from the konsole tab.

In master there is a newish aspect-ratio problem with this arrangement; 
I don't think it affects fixes.  DLNA and Firestick 4k are both ok.

Sound is almost always via hdmi and the tv, although I do have a default 
combined ALSA virtual device.

I'm not sure how this would convert to a mythbuntu-derived environment: 
in kubuntu I don't run any myth services, and run mythbackend, 
mythfrontend.real from konsole tabs, as above.

If you tweak a few of the numbers (and can't find a better solution) 
this might work for you.

John P

> 
> When I was running Mythbuntu-8 which drove the projector and the TV just 
> fine, I had everything set to 1280x720 as that is all the TV signal is 
> anyway.
> 
> So now I have to decide if I want to use the TV at 1920x1080 or downres 
> so I can use the projector a few times a year or find some way to have 
> the computer auto detect without turning the TV black. I believe there 
> was also an issue with the Sony sending bad EDID data. I just read 
> something about auto detecting 1360x768 instead of something useful.  
> Might be a different model but I recall there was an issue. Maybe there 
> is a way to have X pick between 1280x720 and 1920x1024???
> 
> The video card is "GeForce GTX 750 Ti"
> 
> Well, I think I am at least understanding why it doesn't work.
> 
> Allen
> 
> 
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
> 


From acstadt at stadt.ca  Sun Mar  3 13:20:48 2019
From: acstadt at stadt.ca (Andrew Stadt)
Date: Sun, 3 Mar 2019 08:20:48 -0500
Subject: [mythtv-users] Can't get my projector to work with Myth
In-Reply-To: <CAH8UtKOhuRFhFcL-ddQ-LSsfLUsZA+oLnTGmCbxjgPtY35JJfg@mail.gmail.com>
References: <CAH8UtKOMT3uQXme1cK3d8JoK7S-Ta4abnkoEsTaHFQzyc1cW-g@mail.gmail.com>
 <pmbm7e1u2mmam8t659n0ch7o5rv6qt655f@4ax.com>
 <CAH8UtKOhuRFhFcL-ddQ-LSsfLUsZA+oLnTGmCbxjgPtY35JJfg@mail.gmail.com>
Message-ID: <983fb542-f7ed-7d36-e26a-08559f93d92a@stadt.ca>

On 2019-03-02 11:42 p.m., Allen Edwards wrote:
> <snipped>
> I think the problem is that I misread the specification on the 
> projector.? While it says that it does 1080p, the maximum data rate is 
> 1280x720 so the 1080p must be with an analog input.? Same with the 
> monitor. It has a native resolution of 1280 x 1024.? Per the 
> recommendation of everyone here, I set the TV up from my initial setup 
> of 1280x720 to 1920x1280 when I upgraded to Mythbuntu-16.
>
> Option? ? ? ? ?"metamodes" "VGA-0: nvidia-auto-select +0+0, HDMI-0: 
> 1920x1080 +1280+0"
>
> When I was running Mythbuntu-8 which drove the projector and the TV 
> just fine, I had everything set to 1280x720 as that is all the TV 
> signal is anyway.
>
> So now I have to decide if I want to use the TV at 1920x1080 or 
> downres so I can use the projector a few times a year or find some way 
> to have the computer auto detect without turning the TV black. I 
> believe there was also an issue with the Sony sending bad EDID data. I 
> just read something about auto detecting 1360x768 instead of something 
> useful.? Might be a different model but I recall there was an issue. 
> Maybe there is a way to have X pick between 1280x720 and 1920x1024???
>
> The video card is "GeForce GTX 750 Ti"
>
> Well, I think I am at least understanding why it doesn't work.
>
> Allen
>
I don't think I ever set up a frontend where I hadn't had to tweak the 
xorg.conf for the specific screen ( monitor, tv, projector, etc ) at 
least a little ( ok, the Android frontend on my Shield went surprisingly 
easy ).

Whether it be dealing with overscan, underscan, adjusting mode lines for 
some specific resolutions/frame rates, or dealing with an older xorg 
that couldn't handle the device not being there when it came out of 
suspension, bad EDIDs, etc.

The issue is that these adjustments are generally specific to that 
device and don't just work for all of them.

For one of my frontends, which has a primary output device (TV), and a 
secondary I only use a few times a year (Projector), I ended up creating 
an xorg.conf which has two SERVERLAYOUT sections, each of those two 
sections specify their own DEVICE, SCREEN and MONITOR sections.

Most of the time, my frontend auto logs in the myth user, and 
automatically starts "startx --layout TV". For the couple times a year I 
use the projector, I logout then, log in manually, and "startx --layout 
PROJECTOR".

FWIW: I tweaked the xorg.conf for the separate devices individually, 
till I had everything the way I wanted it for that output device, and 
then combined them, makes testing a lot easier as well.

Of course none of this solves your immediate issue, just a suggestion on 
how you can run both configs going forward when you do get it working. 
Stephan Worthington already gave some pretty good advice in that category.

Andrew.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190303/a92880a2/attachment.html>

From johnpilk222 at gmail.com  Sun Mar  3 14:29:54 2019
From: johnpilk222 at gmail.com (John Pilkington)
Date: Sun, 3 Mar 2019 14:29:54 +0000
Subject: [mythtv-users] Active EIT data collection gives some defective
 recordings; passive scanning not working.
In-Reply-To: <20190302233519.0b3cc657@compaq>
References: <cdb83736-2fb6-89f0-df76-bb6da3063daf@gmail.com>
 <vm6l7eds403faivj642nkolv98hbojmfaf@4ax.com> <20190302233519.0b3cc657@compaq>
Message-ID: <3800d9d8-d20a-c282-4681-4bd8a5af3b7e@gmail.com>

On 02/03/2019 23:35, Roger Siddons wrote:
> On Sun, 03 Mar 2019 05:04:41 +1300
> Stephen Worthington <stephen_agent at jsw.gen.nz> wrote:
> 
>> On Sat, 2 Mar 2019 14:09:19 +0000, you wrote:
>>
>>> Recently the number of defects rose again.
> 
> Most likely the recent weather
> https://www.a516digital.com/2019/02/as-weather-disrupts-tv-reception.html
> 
>>> I tried disabling active scanning on *all* tuners.  I had understood
>>> that passive scanning would continue to collect EIT data, for all
>>> muxes, as long as some recordings were being made
> 
> I thought passive scanning only updates the mux (possibly
> channel) of the recording. I'd expect to see 7 days for your popular
> channels/muxes and eventually 0 for infrequent ones.
> 
> EIT might be cross-channel but that doesn't mean Myth uses it.
> Otherwise why does the active scanner cycle through all channels ?
> 
>>> They seemed less frequent when I stopped active
>>> EIT scanning with the USB tuners, using only the PCI card.
> 
> Good move. I believe the option actually starts a new scanner on the
> tuner rather than allowing the *solitary* scanner to use the tuner.
> (Years ago there were issues with multiple scanners
> conflicting/interfering, particularly on lower-quality dual USB tuners).
> 
> There's no reason to ever run more than 1 scanner on a video
> source. "New" EIT data is frequent and the scheduler gets repeatedly
> re-run pointlessly, which won't help your loads.
> 
>> In
>> theory, it would be possible to get a tuner that is recording to also
>> receive the EIT data at the same time, but I do not think MythTV does
>> that.
> 
> It does.
> http://lists.mythtv.org/pipermail/mythtv-users/2012-March/330012.html
> 
>> However, I thought that use of a tuner for EIT reception gave
>> way automatically when the tuner was needed for a recording, and
>> started again automatically afterwards.
 >
 > Active scanning will stop and give up its tuner for recording or
 > shutdown.
 >

Thanks to Roger and Stephen for their thoughts.

EIT has worked fine for me, for years, and still does.  I was hoping to 
find a reason for the recent increase in decoding error-rate, and 
Roger's link is a possible, together with others that I mentioned, and 
the spectrum-clearance program; my BBC mux seems better than itv/Ch4, 
but I tend to steer them to different devices anyway.

I suppose I might have missed some other setting, but my source for 
belief in 'passive scanning' looked fairly robust; it's at the end of 
the thread I quoted earlier...

https://lists.gt.net/mythtv/dev/619014#619014

Cheers,

John P


From allen.p.edwards at gmail.com  Sun Mar  3 15:53:40 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Sun, 3 Mar 2019 07:53:40 -0800
Subject: [mythtv-users] Can't get my projector to work with Myth
In-Reply-To: <983fb542-f7ed-7d36-e26a-08559f93d92a@stadt.ca>
References: <CAH8UtKOMT3uQXme1cK3d8JoK7S-Ta4abnkoEsTaHFQzyc1cW-g@mail.gmail.com>
 <pmbm7e1u2mmam8t659n0ch7o5rv6qt655f@4ax.com>
 <CAH8UtKOhuRFhFcL-ddQ-LSsfLUsZA+oLnTGmCbxjgPtY35JJfg@mail.gmail.com>
 <983fb542-f7ed-7d36-e26a-08559f93d92a@stadt.ca>
Message-ID: <CAH8UtKOT7uZoj68_pBbPcTx_=4Ug3N7CmtsQsJbWFdQWhLZnJw@mail.gmail.com>

On Sun, Mar 3, 2019 at 5:21 AM Andrew Stadt <acstadt at stadt.ca> wrote:

> On 2019-03-02 11:42 p.m., Allen Edwards wrote:
>
> <snipped>
>
> I think the problem is that I misread the specification on the projector.
> While it says that it does 1080p, the maximum data rate is 1280x720 so the
> 1080p must be with an analog input.  Same with the monitor. It has a native
> resolution of 1280 x 1024.  Per the recommendation of everyone here, I set
> the TV up from my initial setup of 1280x720 to 1920x1280 when I upgraded to
> Mythbuntu-16.
>
> Option         "metamodes" "VGA-0: nvidia-auto-select +0+0, HDMI-0:
> 1920x1080 +1280+0"
>
> When I was running Mythbuntu-8 which drove the projector and the TV just
> fine, I had everything set to 1280x720 as that is all the TV signal is
> anyway.
>
> So now I have to decide if I want to use the TV at 1920x1080 or downres so
> I can use the projector a few times a year or find some way to have the
> computer auto detect without turning the TV black. I believe there was also
> an issue with the Sony sending bad EDID data. I just read something about
> auto detecting 1360x768 instead of something useful.  Might be a different
> model but I recall there was an issue. Maybe there is a way to have X pick
> between 1280x720 and 1920x1024???
>
> The video card is "GeForce GTX 750 Ti"
>
> Well, I think I am at least understanding why it doesn't work.
>
> Allen
>
>
> I don't think I ever set up a frontend where I hadn't had to tweak the
> xorg.conf for the specific screen ( monitor, tv, projector, etc ) at least
> a little ( ok, the Android frontend on my Shield went surprisingly easy ).
>
> Whether it be dealing with overscan, underscan, adjusting mode lines for
> some specific resolutions/frame rates, or dealing with an older xorg that
> couldn't handle the device not being there when it came out of suspension,
> bad EDIDs, etc.
>
> The issue is that these adjustments are generally specific to that device
> and don't just work for all of them.
>
> For one of my frontends, which has a primary output device (TV), and a
> secondary I only use a few times a year (Projector), I ended up creating an
> xorg.conf which has two SERVERLAYOUT sections, each of those two sections
> specify their own DEVICE, SCREEN and MONITOR sections.
>
> Most of the time, my frontend auto logs in the myth user, and
> automatically starts "startx --layout TV". For the couple times a year I
> use the projector, I logout then, log in manually, and "startx --layout
> PROJECTOR".
>
> FWIW: I tweaked the xorg.conf for the separate devices individually, till
> I had everything the way I wanted it for that output device, and then
> combined them, makes testing a lot easier as well.
>
> Of course none of this solves your immediate issue, just a suggestion on
> how you can run both configs going forward when you do get it working.
> Stephan Worthington already gave some pretty good advice in that category.
>
> Andrew.
>
Let me explain what I did for the last decade.  I had a VGA display which
is a small Samsung monitor.  For the other I had a 1080x720 output to a DVI
splitter which went to the TV and the Projector.  The splitter faked the
HDCP data so that a source like a DVD player thought there was only one
device connected.  I would play whatever I wanted and it would show up on
whichever display was on. That was on Mythbuntu8 with an old slow video
card but it worked fine.  That system died. There was no problem having the
same setting for both the TV and the Projector and in fact Myth had no idea
there were two displays connected to the single DVI port.  This DVI
splitter was quite expensive and violated the HDCP standard, which is why
it worked.  I originally bought it so that my new DVD player would work
with my old projector that had no HDCP so without this device, I could no
longer watch DVDs once my old DVD player died. That projector died and I
bought the Panasonic.  Point is, Myth worked fine with a single setup and
two displays on the DVI port and one on the RGB port.

New system is Mythbuntu 16 and the video old card is too slow.  I got lots
of tearing. Big step backward.  A friend gave me the 750 ti card and now I
am using HDMI and get digital sound into the TV.  Can't go back to the old
setup because in the process of doing something I fried the audio decoder I
was using to get audio to the TV.  Anyway, I am happy with the hdmi into
the TV so that is good.

That is the history.  The goal now is to be able to unplug the TV and plug
in the Projector and have it work. The obvious solution is to change
 Option   "metamodes" "VGA-0: nvidia-auto-select +0+0, HDMI-0: 1920x1080
+1280+0"
to
 Option   "metamodes" "VGA-0: nvidia-auto-select +0+0, HDMI-0: 1280x720
+1280+0"

It is not at all clear to me what benefit I am getting from using 1920x1080
on 1280x720 source material but someone on this list convinced me to do it
that way and it works well so I would prefer not to change.

What I wonder is, would X figure it out if I did something like this?
Option "metamodes" "VGA-0: nvidia-auto-select +0+0, HDMI-0: 1280x720,
1920x1080 +1280+0"
or maybe it has to be this
Option "metamodes" "VGA-0: nvidia-auto-select +0+0, HDMI-0:
1920x1080,1280x720  +1280+0"

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190303/9e157667/attachment-0001.html>

From john.baab at gmail.com  Sun Mar  3 16:24:01 2019
From: john.baab at gmail.com (john.baab at gmail.com)
Date: Sun, 3 Mar 2019 11:24:01 -0500
Subject: [mythtv-users] Shield TV Video Settings
Message-ID: <CAOfiuiwD2TDR3Sjb-NQTYxUAn4ct3nWiBamdEW_RQLquix3b4w@mail.gmail.com>

What settings is everyone using on their Shield TVs?  My content is
mainly from US based HDHomerun CC's.  A large majority of my channels
are h264 now, but I still have a few mpeg2 ones sticking around.

The recommended settings on the wiki didn't work well for the mpeg2 content:
https://www.mythtv.org/wiki/Android

So I ended up going with a modified version of the 2nd entry:
Decoder: Android MediaCodec decoder
Video Render: opengl
Deinterlacers: Disabled

My understanding is that the MediaCodec automagically deinterlaces,
and I saw some studdering with deinterlacers enabled.  I haven't had a
chance to compare the different opengl options to see if one works
better than the other.

From pb.mythtv at gmail.com  Sun Mar  3 16:40:43 2019
From: pb.mythtv at gmail.com (Peter Bennett)
Date: Sun, 3 Mar 2019 11:40:43 -0500
Subject: [mythtv-users] Shield TV Video Settings
In-Reply-To: <CAOfiuiwD2TDR3Sjb-NQTYxUAn4ct3nWiBamdEW_RQLquix3b4w@mail.gmail.com>
References: <CAOfiuiwD2TDR3Sjb-NQTYxUAn4ct3nWiBamdEW_RQLquix3b4w@mail.gmail.com>
Message-ID: <fc728d52-f65c-1466-fe57-b26876e1c793@gmail.com>



On 3/3/19 11:24 AM, john.baab at gmail.com wrote:
> What settings is everyone using on their Shield TVs?  My content is
> mainly from US based HDHomerun CC's.  A large majority of my channels
> are h264 now, but I still have a few mpeg2 ones sticking around.
>
> The recommended settings on the wiki didn't work well for the mpeg2 content:
> https://www.mythtv.org/wiki/Android
>
> So I ended up going with a modified version of the 2nd entry:
> Decoder: Android MediaCodec decoder
> Video Render: opengl
> Deinterlacers: Disabled
>
> My understanding is that the MediaCodec automagically deinterlaces,
> and I saw some studdering with deinterlacers enabled.  I haven't had a
> chance to compare the different opengl options to see if one works
> better than the other.
> _______________________________________________
>
This may be the same problem that Mark Spieth found on h264 interlaced 
content from Australia. The mediacodec decoder is getting confused 
between interlaced and progressive and continuously flipping between the 
two. I don't yet know the cause, but it seems to work much better to use 
standard (software) decoder in this case.



From veehexx at zoho.com  Sun Mar  3 16:52:36 2019
From: veehexx at zoho.com (Tim Draper)
Date: Sun, 03 Mar 2019 16:52:36 +0000
Subject: [mythtv-users] missing keybinds on some FE's
In-Reply-To: <8b8e3c09-df25-130c-7045-153eeb21bf4d@gmail.com>
References: <1693e227421.f1de53c2173359.4083304163391863266@zoho.com>
 <8b8e3c09-df25-130c-7045-153eeb21bf4d@gmail.com>
Message-ID: <1694477c92c.e732e2aa230234.1169973653178678098@zoho.com>




---- On Sat, 02 Mar 2019 17:31:24 +0000 Peter Bennett <pb.mythtv at gmail.com> wrote ----

 > 
 > 
 > On 3/2/19 6:21 AM, Tim Draper wrote:
 > 
 > TOGGLEBOOKMARK is a new feature with V30, so you won't find it in     V29. There is also a new key assignment SETBOOKMARK. The difference     is SETBOOKMARK always sets a bookmark even if already set.
 >  
 >  There is no default setting for these keys so on a new frontend,     they must be explicitly assigned. Previously the select key     (space/enter) was always used to set bookmarks with no ability to     change space/enter to something else, so now there is flexibility on     the use of space and enter.
 >  
 >  Key assignments should not disappear from a frontend once set.     _______________________________________________ 
 
definately was toggling on v29. anyway, since you've said TOGGLEBOOKMARK is a new option that appears on v30 FE's it looks like i might need to check my FE names. Since my original post i found that you can goto 'setup > edit keys' on the FE and change from there. TOGGLEBOOKMARK is set and now seems to be working. Looks like i might have some of my FE names to skew as mythweb isnt showing what i'm expecting to see. An FE name i thought was an old testing one has been updated so seems to actually be active.




From glenb at glenb.us  Sun Mar  3 17:24:26 2019
From: glenb at glenb.us (glen)
Date: Sun, 03 Mar 2019 09:24:26 -0800
Subject: [mythtv-users] Shield TV Video Settings
In-Reply-To: <fc728d52-f65c-1466-fe57-b26876e1c793@gmail.com>
References: <CAOfiuiwD2TDR3Sjb-NQTYxUAn4ct3nWiBamdEW_RQLquix3b4w@mail.gmail.com>
 <fc728d52-f65c-1466-fe57-b26876e1c793@gmail.com>
Message-ID: <067759f52769e25aff4713bf916c815177dc2c67.camel@glenb.us>

On Sun, 2019-03-03 at 11:40 -0500, Peter Bennett wrote:
> On 3/3/19 11:24 AM, john.baab at gmail.com wrote:
> > What settings is everyone using on their Shield TVs?  My content
> > ismainly from US based HDHomerun CC's.  A large majority of my
> > channelsare h264 now, but I still have a few mpeg2 ones sticking
> > around.
> > The recommended settings on the wiki didn't work well for the mpeg2
> > content:https://www.mythtv.org/wiki/Android
> > 
> > So I ended up going with a modified version of the 2nd
> > entry:Decoder: Android MediaCodec decoderVideo Render:
> > openglDeinterlacers: Disabled
> > My understanding is that the MediaCodec automagically
> > deinterlaces,and I saw some studdering with deinterlacers
> > enabled.  I haven't had achance to compare the different opengl
> > options to see if one worksbetter than the
> > other._______________________________________________
> This may be the same problem that Mark Spieth found on h264
> interlaced content from Australia. The mediacodec decoder is getting
> confused between interlaced and progressive and continuously flipping
> between the two. I don't yet know the cause, but it seems to work
> much better to use standard (software) decoder in this case.
> 
> _______________________________________________mythtv-users mailing 
> listmythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

i have same/similar issue on shield on h264. the mpeg2 is great with
mediacodec. on h264 mainly from hdpvr after a while the playback will
stutter badly, if i exit the playback and restart it is fine. this is
generally around 20minute mark. and i agree it does not happen on
opengl high quality with any deinterlacer. yet the same codec delpoyed
by kodi (on the shield) on the same content does not display the issue.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190303/4049ed83/attachment.html>

From jfabernathy at gmail.com  Sun Mar  3 19:48:15 2019
From: jfabernathy at gmail.com (James Abernathy)
Date: Sun, 3 Mar 2019 14:48:15 -0500
Subject: [mythtv-users] Shield TV Video Settings
In-Reply-To: <067759f52769e25aff4713bf916c815177dc2c67.camel@glenb.us>
References: <CAOfiuiwD2TDR3Sjb-NQTYxUAn4ct3nWiBamdEW_RQLquix3b4w@mail.gmail.com>
 <fc728d52-f65c-1466-fe57-b26876e1c793@gmail.com>
 <067759f52769e25aff4713bf916c815177dc2c67.camel@glenb.us>
Message-ID: <0F44A610-255F-4D11-8CC1-73F2B786D53D@gmail.com>


> On Mar 3, 2019, at 12:24 PM, glen <glenb at glenb.us> wrote:
> 
> On Sun, 2019-03-03 at 11:40 -0500, Peter Bennett wrote:
>> 
>> On 3/3/19 11:24 AM, 
>> john.baab at gmail.com
>>  <mailto:john.baab at gmail.com> wrote:
>>> What settings is everyone using on their Shield TVs?  My content is
>>> mainly from US based HDHomerun CC's.  A large majority of my channels
>>> are h264 now, but I still have a few mpeg2 ones sticking around.
>>> 
>>> The recommended settings on the wiki didn't work well for the mpeg2 content:
>>> https://www.mythtv.org/wiki/Android
>>>  <https://www.mythtv.org/wiki/Android>
>>> 
>>> So I ended up going with a modified version of the 2nd entry:
>>> Decoder: Android MediaCodec decoder
>>> Video Render: opengl
>>> Deinterlacers: Disabled
>>> 
>>> My understanding is that the MediaCodec automagically deinterlaces,
>>> and I saw some studdering with deinterlacers enabled.  I haven't had a
>>> chance to compare the different opengl options to see if one works
>>> better than the other.
>>> _______________________________________________
>>> 
>> This may be the same problem that Mark Spieth found on h264 interlaced 
>> content from Australia. The mediacodec decoder is getting confused 
>> between interlaced and progressive and continuously flipping between the 
>> two. I don't yet know the cause, but it seems to work much better to use 
>> standard (software) decoder in this case.
>> 
>> 
>> 
> 
> i have same/similar issue on shield on h264. the mpeg2 is great with mediacodec. on h264 mainly from hdpvr after a 
> while the playback will stutter badly, if i exit the playback and restart it is fine. this is generally around 20
> minute mark. and i agree it does not happen on opengl high quality with any deinterlacer. yet the same codec delpoyed 
> by kodi (on the shield) on the same content does not display the issue.
With my mpeg2 OTA recordings I use the the Android Shield TV wiki settings. But the quality of the video seems to vary depending on the program. 

From my testing, I think the Shield TV has it?s own problems. It depends on app.  Prime Video has a jumping problem every few seconds. It?s minor but depending on the scene and program it?s annoying. Sling TV does not have this issue. Mythtv does not have this problem on most programs.

If anyone have the pilot of The Enemy Within (NBC 2/25/2019), the opening has the main character walking toward the camera and a bicycle crossing right to left.  In that scene the bike seems to jump across the screen every second. This also happens on Kodi 18 on the shield tv. It does not happen on a Ubuntu desktop with an Nvidia GT710 GFX card.

i think there are a lot of interactions between the UHD TV settings, the Shield TV settings and Mythtv settings. If I get it right for one program, it?s a little off on another.

Jim A


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190303/4138ed9b/attachment.html>

From mtdean at thirdcontact.com  Mon Mar  4 12:02:06 2019
From: mtdean at thirdcontact.com (Michael T. Dean)
Date: Mon, 4 Mar 2019 07:02:06 -0500
Subject: [mythtv-users] MythTV miscalculates the amount of free disk
 space
In-Reply-To: <a8f805f3-3cdd-f102-167b-3bde91f568a4@gmail.com>
References: <762d3af4-7a04-f48c-afb5-9ed8d6ecf71f@gmail.com>
 <bf6a3d79-c50f-ee57-b9e7-f6c32bb07744@sky.com>
 <52be7619-49ac-a215-d7eb-778c14d67733@gmail.com>
 <b8497955-eb21-2a57-f066-3851fd376a4f@gmail.com>
 <a8f805f3-3cdd-f102-167b-3bde91f568a4@gmail.com>
Message-ID: <5C7D13BE.9040503@thirdcontact.com>

On 03/02/2019 11:38 AM, Jan Ceuleers wrote:
> On 02/03/2019 17:32, Jonatan Lindblad wrote:
>> Den 2019-03-02 kl. 12:58, skrev Jan Ceuleers:
>>> On 02/03/2019 12:36, Paul Harrison wrote:
>>>> Since both drives are empty and otherwise identical, mythbackend can't
>>>> tell them apart. For all it knows the mounts point to the exact same
>>>> drive. Until there is content on one or both of the drives it's unable
>>>> to tell them apart.
>>> Thanks Paul.
>>>
>>> Sounds like a bug to me though. I thought that the backend verified it
>>> could write to each storage group by creating temporary files, so if
>>> that's correct it would also be an opportunity for it to find out
>>> whether directories it thinks are the same are in fact.
>> Nope, it is not a bug.  See this thread for example https://lists.gt.net/mythtv/users/280821#280821
> Thanks Jonathan. Now that a recording has been stored on one of these
> new disks the backend does indeed recognise the disks as separate.
>
> Still looks like a bug to me though, even if it works as designed.
>
> Anyway, case closed - thanks.

Patches for a new feature that can distinguish the disks are gladly 
accepted.  We'd love to see how you solve the problem.

You can't use the disk ID's--not every backend has direct file system 
access (some see the same file system via NFS, some via CIFS, some via 
...).  You can't use a temporary file written to see if it exists on 
both (some users have multiple different directories on the same file 
system in different Storage Groups and some users have multiple network 
shares on the same file system all with no common directory available 
within both directory structures).  You can't use any approach that 
requires testing or flagging or ... at setup because Storage Groups can 
change outside of MythTV (directory names stay the same but the volumes 
mounted in those locations change). I'm sure there are many other varied 
use cases that your patch will include ingenious methods for reliably 
distinguishing the differences between various configurations of file 
systems/mounts.

In the end, we decided that it's not a problem as the user can see all 
the storage outside of MythTV and the false negative test for uniqueness 
(thinking 2 different file systems are the same) is only likely to occur 
with new, empty disks (meaning lots of storage available) and that a 
false positive test for uniqueness would be significantly worse than a 
false negative--i.e. it's much better that we say, "You only have 4TB 
available," and you're later happily surprised to see that you have a 
full 8TB available than to say, "You have 1GB available," when you 
actually have lots more and you're not-happily surprised to see that 
MythTV started deleting shows in the auto-expiration list to make room 
for new recordings even though you had plenty.

I will agree that it makes it difficult for the user to see if his 2 
new, identical disks were properly recognized by MythTV after changing 
around the settings, but I don't have an answer for how to handle all 
the varied configurations that can exist.  The only approach that's ever 
been proposed that is guaranteed to work is to go back to the 
pre-Storage-Groups approach of having a single directory into which all 
recordings are written, but that's not my preferred solution.

Mike

From km at mathcs.emory.edu  Mon Mar  4 14:27:45 2019
From: km at mathcs.emory.edu (Ken Mandelberg)
Date: Mon, 4 Mar 2019 09:27:45 -0500
Subject: [mythtv-users] Subject: Re: Daily mythfilldatabase fails after
 conversion to XMLTV
In-Reply-To: <92e48761-3887-049c-d793-4724e18f24c7@gmail.com>
References: <CAKGL=YKayEOKc3WmraK4MH+OCOMhCJkL_yQB8H6oPSKBsxjUUw@mail.gmail.com>
 <92e48761-3887-049c-d793-4724e18f24c7@gmail.com>
Message-ID: <c465827d-40c7-5f8a-7ad6-1f3e5ed3c8ae@mathcs.emory.edu>

Removing the full path had two effects. First, as suggested I get 
mythfilldatabase logs.

Second, now mythfilldatabase actually runs initiated from the backend. 
In fact too much. It runs over and over again, unsuccessful each time, 
leaving a new log once a minute.

That log shows failure with

2019-03-04 09:06:07.517937 I [7142/7142] CoreContext filldata.cpp:584 
(Run) - Found 666 channels for source 3 which use grabber
2019-03-04 09:06:07.518476 I [7142/7150] SystemSignalManager 
mythsystemunix.cpp:497 (run) - Starting process signal handler
2019-03-04 09:06:07.518494 I [7142/7151] SystemIOHandlerR 
mythsystemunix.cpp:92 (run) - Starting IO manager (read)
2019-03-04 09:06:07.518554 I [7142/7149] SystemManager 
mythsystemunix.cpp:271 (run) - Starting process manager
2019-03-04 09:06:07.521057 I [7142/7152] SystemIOHandlerW 
mythsystemunix.cpp:92 (run) - Starting IO manager (write)
2019-03-04 09:06:08.570470 E [7142/7142] CoreContext filldata.cpp:613 
(Run) - tv_grab_zz_sdjson_sqlite? --capabilities failed or we timed out 
waiting. You may need to upgrade your xmltv grabber
2019-03-04 09:06:08.570540 E [7142/7142] CoreContext filldata.cpp:929 
(Run) - Grabbing XMLTV data using tv_grab_zz_sdjson_sqlite is not 
supported. You may need to upgrade to the latest version of XMLTV.
2019-03-04 09:06:10.711251 N [7142/7142] CoreContext main.cpp:436 (main) 
- Data fetching complete.


For reference:
$ /var/log/mythtv$ tv_grab_zz_sdjson_sqlite --version
XMLTV module version 0.5.70
This is tv_grab_zz_sdjson_sqlite version 1.4, 2017/06/19 16:15:28

Remember mythfilldatabase runs properly from the command line as me.

I'm wondering if the issue is that it runs as mythtv from the backend, 
and mythtv does not actually have a home directory. If so, beyond 
creating one, does it need to be populated in some way.



Bill Meek wrote on 3/3/19 12:23 PM:
> On 3/3/19 10:11 AM, Ken Mandelberg wrote:
>> Bill
>>
>> curl -H Accept:application/json
>> localhost:6544/Myth/GetSetting?Key=MythFillDatabasePath\&HostName=_GLOBAL_ 
>>
>>
>> gives
>>
>> {"String": "\/usr\/local\/bin\/mythfilldatabase"}
>>
>> Is that wrong? /usr/local/bin/mythfilldatabase is the correct path that
>> works by hand.
>
> Hi,
>
> The full path will prevent logging, see Mike's response here:
>
> ??? https://code.mythtv.org/trac/ticket/12169
>
> Change it to: mythfilldatabase
>


From jan.ceuleers at gmail.com  Mon Mar  4 16:20:32 2019
From: jan.ceuleers at gmail.com (Jan Ceuleers)
Date: Mon, 4 Mar 2019 17:20:32 +0100
Subject: [mythtv-users] MythTV miscalculates the amount of free disk
 space
In-Reply-To: <5C7D13BE.9040503@thirdcontact.com>
References: <762d3af4-7a04-f48c-afb5-9ed8d6ecf71f@gmail.com>
 <bf6a3d79-c50f-ee57-b9e7-f6c32bb07744@sky.com>
 <52be7619-49ac-a215-d7eb-778c14d67733@gmail.com>
 <b8497955-eb21-2a57-f066-3851fd376a4f@gmail.com>
 <a8f805f3-3cdd-f102-167b-3bde91f568a4@gmail.com>
 <5C7D13BE.9040503@thirdcontact.com>
Message-ID: <7d3f6648-3a73-e9a4-473c-d787d0a47da9@gmail.com>

On 04/03/2019 13:02, Michael T. Dean wrote:
> Patches for a new feature that can distinguish the disks are gladly
> accepted.? We'd love to see how you solve the problem.

Mike, thanks for your response.

I see the logic behind the approach, noting that its shortcomings are
minor and fail "safely" as you pointed out.

You are correct that it is probably not possible to do better without
incurring a severe performance penalty. What I think would work would be
to write a large-ish temporary file to each storage group and observe
the amount of free space in each of the others, both before the file is
created, once it exists, and again once it is deleted. I think that if
all three tests yield the same amount of free space between a pair of
directories this would be a pretty conclusive indication that they
belong to the same filesystem.

It would still suffer from "interference" by non-MythTV processes that
also write to those filesystems. So the problem is probably too minor to
try and improve on the current situation.

Thanks, Jan

From keemllib at gmail.com  Mon Mar  4 19:05:15 2019
From: keemllib at gmail.com (Bill Meek)
Date: Mon, 4 Mar 2019 13:05:15 -0600
Subject: [mythtv-users] Subject: Re: Daily mythfilldatabase fails after
 conversion to XMLTV
In-Reply-To: <c465827d-40c7-5f8a-7ad6-1f3e5ed3c8ae@mathcs.emory.edu>
References: <CAKGL=YKayEOKc3WmraK4MH+OCOMhCJkL_yQB8H6oPSKBsxjUUw@mail.gmail.com>
 <92e48761-3887-049c-d793-4724e18f24c7@gmail.com>
 <c465827d-40c7-5f8a-7ad6-1f3e5ed3c8ae@mathcs.emory.edu>
Message-ID: <3cfd0e1f-ee0c-e8ac-a9b7-667c11d40bad@gmail.com>

On 3/4/19 8:27 AM, Ken Mandelberg wrote:
> Removing the full path had two effects. First, as suggested I get mythfilldatabase?logs.
> 
> Second, now mythfilldatabase actually runs initiated from the backend. In fact too much. It runs over and over again, unsuccessful each time, 
> leaving?a?new?log?once?a?minute.

Never saw that. May need to dump the housekeeping table and a setting.

     SELECT * FROM housekeeping WHERE tag = 'MythFillDB';
     SELECT * FROM settings WHERE value = 'MythFillSuggestedRunTime';

> That?log?shows?failure?with
> 
> 2019-03-04 09:06:07.517937 I [7142/7142] CoreContext filldata.cpp:584 (Run)?-?Found?666?channels?for?source?3?which?use?grabber
> 2019-03-04 09:06:07.518476 I [7142/7150] SystemSignalManager mythsystemunix.cpp:497?(run)?-?Starting?process?signal?handler
> 2019-03-04 09:06:07.518494 I [7142/7151] SystemIOHandlerR mythsystemunix.cpp:92?(run)?-?Starting?IO?manager?(read)
> 2019-03-04 09:06:07.518554 I [7142/7149] SystemManager mythsystemunix.cpp:271?(run)?-?Starting?process?manager
> 2019-03-04 09:06:07.521057 I [7142/7152] SystemIOHandlerW mythsystemunix.cpp:92?(run)?-?Starting?IO?manager?(write)
> 2019-03-04 09:06:08.570470 E [7142/7142] CoreContext filldata.cpp:613 (Run) - tv_grab_zz_sdjson_sqlite? --capabilities failed or we timed out 
> waiting.?You?may?need?to?upgrade?your?xmltv?grabber
> 2019-03-04 09:06:08.570540 E [7142/7142] CoreContext filldata.cpp:929 (Run) - Grabbing XMLTV data using tv_grab_zz_sdjson_sqlite is not 
> supported.?You?may?need?to?upgrade?to?the?latest?version?of?XMLTV.
> 2019-03-04 09:06:10.711251 N [7142/7142] CoreContext main.cpp:436 (main) -?Data?fetching?complete.
> 
> 
> For?reference:
> $?/var/log/mythtv$?tv_grab_zz_sdjson_sqlite?--version
> XMLTV?module?version?0.5.70
> This?is?tv_grab_zz_sdjson_sqlite?version?1.4,?2017/06/19?16:15:28
> 
> Remember?mythfilldatabase?runs?properly?from?the?command?line?as?me.
> 
> I'm wondering if the issue is that it runs as mythtv from the backend, and mythtv does not actually have a home directory. If so, beyond 
> creating?one,?does?it?need?to?be?populated?in?some?way.

User mythtv may not have a HOME, but you must have a configuration directory.

The full log would tell you which configuration directory is in play. Look for the line:

   Using configuration directory = ......

You likely used the: --config-file $HOME/.mythtv/<your source name>.xmltv
from the Wiki.

Copy the config-file, into MythTV's configuration directory
and point the database to your existing one. Like:

   database=/home/<yourself>/.xmltv/SchedulesDirect.<name you picked>

I recall that creating a symbolic link didn't work. A hard link may, but
I didn't test it.

User mythtv must have read/write permissions on the DB file and maybe its
directory. You get to test the directory part.

-- 
Bill

From davidkrainess at yahoo.com  Mon Mar  4 19:36:58 2019
From: davidkrainess at yahoo.com (David Krainess)
Date: Mon, 4 Mar 2019 19:36:58 +0000 (UTC)
Subject: [mythtv-users] State of VDPAU
References: <1328593502.8420778.1551728218558.ref@mail.yahoo.com>
Message-ID: <1328593502.8420778.1551728218558@mail.yahoo.com>

Hi all,
For version 30, this is in the release notes:
   
   - Hardware accelerated H.265/HEVC decoding with VDPAU is not available any more for Nvidia users. (This feature may come back in MythTV 31 with the NVDEC extension. In the meantime OpenGL playback is recommended for H.265/HEVC playback. Another option is to stay with MythTV 29, perhaps with the patch in?#13211, if surround sound is used, e.g. for German DVB T2 HD.)

I'm in North America, terrestrial, does this impact me?? I'm thinking of upgrading to 30 and using VDPAU on older desktops (circa 2007, GeForce 8500GT) in the house.? I'm thinking I'm OK, don't even think I ever heard of HEVC, but checking with this group.
Also, I purchased an Intel G4560 for $60 awhile ago, and I was very surprised the on CPU video seems to run MythTV flawlessly in 1080P.? ?I remember when VDPAU first came out, it was a pretty big deal and really helped out, but now I'm wondering if VDPAU is even relevant anymore with technological advancements in low end on chip/board video.? Or maybe VDPAU is helpful for newer standards, 4K and above.??
Thoughts on the state of VDPAU?
Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190304/2ad6690f/attachment.html>

From stephen_agent at jsw.gen.nz  Tue Mar  5 02:09:19 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Tue, 05 Mar 2019 15:09:19 +1300
Subject: [mythtv-users] State of VDPAU
In-Reply-To: <1328593502.8420778.1551728218558@mail.yahoo.com>
References: <1328593502.8420778.1551728218558.ref@mail.yahoo.com>
 <1328593502.8420778.1551728218558@mail.yahoo.com>
Message-ID: <iolr7e54pte9ifs41qf3b3tf61pdr8au8s@4ax.com>

On Mon, 4 Mar 2019 19:36:58 +0000 (UTC), you wrote:

>Hi all,
>For version 30, this is in the release notes:
>   
>   - Hardware accelerated H.265/HEVC decoding with VDPAU is not available any more for Nvidia users. (This feature may come back in MythTV 31 with the NVDEC extension. In the meantime OpenGL playback is recommended for H.265/HEVC playback. Another option is to stay with MythTV 29, perhaps with the patch in?#13211, if surround sound is used, e.g. for German DVB T2 HD.)
>
>I'm in North America, terrestrial, does this impact me?? I'm thinking of upgrading to 30 and using VDPAU on older desktops (circa 2007, GeForce 8500GT) in the house.? I'm thinking I'm OK, don't even think I ever heard of HEVC, but checking with this group.
>Also, I purchased an Intel G4560 for $60 awhile ago, and I was very surprised the on CPU video seems to run MythTV flawlessly in 1080P.? ?I remember when VDPAU first came out, it was a pretty big deal and really helped out, but now I'm wondering if VDPAU is even relevant anymore with technological advancements in low end on chip/board video.? Or maybe VDPAU is helpful for newer standards, 4K and above.??
>Thoughts on the state of VDPAU?
>Dave

It is pretty unlikely that you will be receiving H.265 in North
America yet.  It is being broadcast on DVB-S2 in Europe for 4K
broadcasts, and Japan is using it for 4K and 8K.  But until you start
getting 4K, it is not likely to be a problem for you.  With downloaded
and streamed video, there is more of that in H.265, again usually for
4K video, but you can usually choose a lesser version in H.264 to use,
if necessary.  If your CPU is good enough, then you can just get it to
play H.265 for you.  My AMD FX-4100 CPU (quad core 3.6 GHz) is easily
capable of that, although I have only tried it on 1080 H.265 files as
I do not have any 4K capable screens.

The thing to remember in any case is that your Nvidia GPU will only be
capable of doing H.265 if it is a fairly recent one.  My GT220 is far
too old to be able to do H.265, so for quite a while I was playing
downloaded H.265 files without realising that mythfrontend was falling
back to using the CPU to do that.  Your 8500GTs are certainly not
capable of H.265, so there is no impact at all in upgrading to v30 on
them.

From km at mathcs.emory.edu  Tue Mar  5 03:57:36 2019
From: km at mathcs.emory.edu (Ken Mandelberg)
Date: Mon, 4 Mar 2019 22:57:36 -0500
Subject: [mythtv-users] Subject: Re: Daily mythfilldatabase fails after
 conversion to XMLTV
In-Reply-To: <3cfd0e1f-ee0c-e8ac-a9b7-667c11d40bad@gmail.com>
References: <CAKGL=YKayEOKc3WmraK4MH+OCOMhCJkL_yQB8H6oPSKBsxjUUw@mail.gmail.com>
 <92e48761-3887-049c-d793-4724e18f24c7@gmail.com>
 <c465827d-40c7-5f8a-7ad6-1f3e5ed3c8ae@mathcs.emory.edu>
 <3cfd0e1f-ee0c-e8ac-a9b7-667c11d40bad@gmail.com>
Message-ID: <d8b23e3c-b29d-b286-5cca-05dccc10ae92@mathcs.emory.edu>

Bill Meek wrote on 3/4/19 2:05 PM:
>
> User mythtv may not have a HOME, but you must have a configuration 
> directory.
>
> The full log would tell you which configuration directory is in play. 
> Look for the line:
>
> ? Using configuration directory = ......
>
> You likely used the: --config-file $HOME/.mythtv/<your source name>.xmltv
> from the Wiki.
>
> Copy the config-file, into MythTV's configuration directory
> and point the database to your existing one. Like:
>
> ? database=/home/<yourself>/.xmltv/SchedulesDirect.<name you picked>
>
> I recall that creating a symbolic link didn't work. A hard link may, but
> I didn't test it.
>
> User mythtv must have read/write permissions on the DB file and maybe its
> directory. You get to test the directory part.
>
I believe I have the config and permissions setup correctly now. Still 
no luck on the grab. Here is the whole log


2019-03-04 22:44:04.337839 C [25094/25094] thread_unknown 
mythcommandlineparser.cpp:2603 (ConfigureLogging) - mythfilldatabase 
version: master [v31-Pre-119-g4089bf1ff0-dirty] www.mythtv.org
2019-03-04 22:44:04.337864 C [25094/25094] thread_unknown 
mythcommandlineparser.cpp:2605 (ConfigureLogging) - Qt version: compile: 
5.9.5, runtime: 5.9.5
2019-03-04 22:44:04.337871 N [25094/25094] thread_unknown 
mythcommandlineparser.cpp:2607 (ConfigureLogging) - Enabled verbose 
msgs:? general xmltv
2019-03-04 22:44:04.337951 N [25094/25094] thread_unknown 
logging.cpp:727 (logStart) - Setting Log Level to LOG_DEBUG
2019-03-04 22:44:04.349124 I [25094/25097] Logger logging.cpp:289 (run) 
- Added logging to the console
2019-03-04 22:44:04.349831 I [25094/25094] thread_unknown 
signalhandling.cpp:194 (SetHandlerPrivate) - Setup Interrupt handler
2019-03-04 22:44:04.349858 I [25094/25094] thread_unknown 
signalhandling.cpp:194 (SetHandlerPrivate) - Setup Terminated handler
2019-03-04 22:44:04.349876 I [25094/25094] thread_unknown 
signalhandling.cpp:194 (SetHandlerPrivate) - Setup Segmentation fault 
handler
2019-03-04 22:44:04.349893 I [25094/25094] thread_unknown 
signalhandling.cpp:194 (SetHandlerPrivate) - Setup Aborted handler
2019-03-04 22:44:04.349910 I [25094/25094] thread_unknown 
signalhandling.cpp:194 (SetHandlerPrivate) - Setup Bus error handler
2019-03-04 22:44:04.349928 I [25094/25094] thread_unknown 
signalhandling.cpp:194 (SetHandlerPrivate) - Setup Floating point 
exception handler
2019-03-04 22:44:04.349946 I [25094/25094] thread_unknown 
signalhandling.cpp:194 (SetHandlerPrivate) - Setup Illegal instruction 
handler
2019-03-04 22:44:04.349967 I [25094/25094] thread_unknown 
signalhandling.cpp:194 (SetHandlerPrivate) - Setup Real-time signal 0 
handler
2019-03-04 22:44:04.349986 I [25094/25094] thread_unknown 
signalhandling.cpp:194 (SetHandlerPrivate) - Setup Hangup handler
2019-03-04 22:44:04.350138 N [25094/25094] thread_unknown 
mythdirs.cpp:203 (InitializeMythDirs) - Using runtime prefix = /usr/local
2019-03-04 22:44:04.350149 N [25094/25094] thread_unknown 
mythdirs.cpp:205 (InitializeMythDirs) - Using configuration directory = 
/root/.mythtv
2019-03-04 22:44:04.350157 D [25094/25094] thread_unknown 
mythdirs.cpp:207 (InitializeMythDirs) - appbindir???????? = /usr/local/bin/
2019-03-04 22:44:04.350164 D [25094/25094] thread_unknown 
mythdirs.cpp:208 (InitializeMythDirs) - sharedir????????? = 
/usr/local/share/mythtv/
2019-03-04 22:44:04.350172 D [25094/25094] thread_unknown 
mythdirs.cpp:209 (InitializeMythDirs) - libdir??????????? = 
/usr/local/lib/mythtv/
2019-03-04 22:44:04.350180 D [25094/25094] thread_unknown 
mythdirs.cpp:210 (InitializeMythDirs) - themedir????????? = 
/usr/local/share/mythtv/themes/
2019-03-04 22:44:04.350189 D [25094/25094] thread_unknown 
mythdirs.cpp:211 (InitializeMythDirs) - pluginsdir??????? = 
/usr/local/lib/mythtv/plugins/
2019-03-04 22:44:04.350197 D [25094/25094] thread_unknown 
mythdirs.cpp:212 (InitializeMythDirs) - translationsdir?? = 
/usr/local/share/mythtv/i18n/
2019-03-04 22:44:04.350205 D [25094/25094] thread_unknown 
mythdirs.cpp:213 (InitializeMythDirs) - filtersdir??????? = 
/usr/local/lib/mythtv/filters/
2019-03-04 22:44:04.350214 D [25094/25094] thread_unknown 
mythdirs.cpp:214 (InitializeMythDirs) - cachedir????????? = 
/root/.mythtv/cache
2019-03-04 22:44:04.350222 D [25094/25094] thread_unknown 
mythdirs.cpp:215 (InitializeMythDirs) - remotecachedir??? = 
/root/.mythtv/cache/remotecache
2019-03-04 22:44:04.350230 D [25094/25094] thread_unknown 
mythdirs.cpp:216 (InitializeMythDirs) - themebasecachedir = 
/root/.mythtv/cache/themecache
2019-03-04 22:44:04.350239 D [25094/25094] thread_unknown 
mythdirs.cpp:217 (InitializeMythDirs) - thumbnaildir????? = 
/root/.mythtv/cache/thumbnails
2019-03-04 22:44:04.350347 I [25094/25094] CoreContext 
mythcorecontext.cpp:272 (Init) - Assumed character encoding: en_US.UTF-8
2019-03-04 22:44:04.350347 I [25094/25096] LogForward 
loggingserver.cpp:129 (FileLogger) - Added logging to 
/var/log/mythtv/mythfilldatabase.20190305034404.25094.log
2019-03-04 22:44:04.350792 I [25094/25094] CoreContext 
mythcontext.cpp:632 (LoadDatabaseSettings) - Empty LocalHostName. This 
is typical.
2019-03-04 22:44:04.350806 I [25094/25094] CoreContext 
mythcontext.cpp:641 (LoadDatabaseSettings) - Using a profile name of: 
'maclinux' (Usually the same as this host's name.)
2019-03-04 22:44:04.350963 I [25094/25094] CoreContext 
mythcontext.cpp:891 (TestDBconnection) - Start up testing connections. 
DB localhost, BE , attempt 0, status dbAwake, Delay: 2000
2019-03-04 22:44:04.350983 D [25094/25094] CoreContext 
portchecker.cpp:76 (checkPort) - PortChecker::checkPort(): host 
localhost port 3306 timeLimit 1000 linkLocalOnly 0
2019-03-04 22:44:04.851852 D [25094/25094] CoreContext 
portchecker.cpp:192 (checkPort) - PortChecker::checkPort(): socket state 1
2019-03-04 22:44:05.352648 D [25094/25094] CoreContext 
portchecker.cpp:192 (checkPort) - PortChecker::checkPort(): socket state 3
2019-03-04 22:44:05.363975 D [25094/25094] CoreContext 
portchecker.cpp:76 (checkPort) - PortChecker::checkPort(): host 
localhost port 3306 timeLimit 30000 linkLocalOnly 1
2019-03-04 22:44:05.370399 D [25094/25094] CoreContext 
mythcontext.cpp:516 (FindDatabase) - FindDatabase() - Success!
2019-03-04 22:44:05.370493 D [25094/25094] CoreContext 
portchecker.cpp:76 (checkPort) - PortChecker::checkPort(): host 
localhost port 3306 timeLimit 30000 linkLocalOnly 1
2019-03-04 22:44:05.372556 N [25094/25094] CoreContext 
mythcorecontext.cpp:1780 (InitLocale) - Setting QT default locale to en_US
2019-03-04 22:44:05.372572 I [25094/25094] CoreContext 
mythcorecontext.cpp:1813 (SaveLocaleDefaults) - Current locale en_US
2019-03-04 22:44:05.372631 N [25094/25094] CoreContext 
mythlocale.cpp:122 (LoadDefaultsFromXML) - Reading locale defaults from 
/usr/local/share/mythtv//locales/en_us.xml
2019-03-04 22:44:05.382209 I [25094/25094] CoreContext 
mythtranslation.cpp:64 (load) - Loading en_us translation for module 
mythfrontend
2019-03-04 22:44:05.384422 I [25094/25094] CoreContext 
schemawizard.cpp:116 (Compare) - Current MythTV Schema Version 
(DBSchemaVer): 1350
2019-03-04 22:44:05.388154 I [25094/25094] CoreContext 
mythcorecontext.cpp:451 (ConnectCommandSocket) - 
MythCoreContext::ConnectCommandSocket(): Connecting to backend server: 
192.168.10.10:6543 (try 1 of 1)
2019-03-04 22:44:05.390530 I [25094/25094] CoreContext 
mythcorecontext.cpp:1677 (CheckProtoVersion) - 
MythCoreContext::CheckProtoVersion(): Using protocol version 91 BuzzOff
2019-03-04 22:44:05.392217 I [25094/25094] CoreContext main.cpp:313 
(main) - Opening blocking connection to master backend
2019-03-04 22:44:07.549958 I [25094/25094] CoreContext filldata.cpp:570 
(Run) - Updating source #3 (zap1) with grabber tv_grab_zz_sdjson_sqlite
2019-03-04 22:44:07.551085 I [25094/25094] CoreContext filldata.cpp:584 
(Run) - Found 666 channels for source 3 which use grabber
2019-03-04 22:44:07.557980 I [25094/25102] SystemSignalManager 
mythsystemunix.cpp:497 (run) - Starting process signal handler
2019-03-04 22:44:07.558129 I [25094/25101] SystemManager 
mythsystemunix.cpp:271 (run) - Starting process manager
2019-03-04 22:44:07.558330 I [25094/25103] SystemIOHandlerR 
mythsystemunix.cpp:92 (run) - Starting IO manager (read)
2019-03-04 22:44:07.558408 I [25094/25104] SystemIOHandlerW 
mythsystemunix.cpp:92 (run) - Starting IO manager (write)
2019-03-04 22:44:08.660926 E [25094/25094] CoreContext filldata.cpp:613 
(Run) - tv_grab_zz_sdjson_sqlite? --capabilities failed or we timed out 
waiting. You may need to upgrade your xmltv grabber
2019-03-04 22:44:08.660972 E [25094/25094] CoreContext filldata.cpp:929 
(Run) - Grabbing XMLTV data using tv_grab_zz_sdjson_sqlite is not 
supported. You may need to upgrade to the latest version of XMLTV.
2019-03-04 22:44:10.822169 N [25094/25094] CoreContext main.cpp:436 
(main) - Data fetching complete.
2019-03-04 22:44:10.822207 I [25094/25094] CoreContext main.cpp:444 
(main) - Adjusting program database end times.
2019-03-04 22:44:10.824841 I [25094/25094] CoreContext main.cpp:450 
(main) -???? 0 replacements made
2019-03-04 22:44:10.824849 I [25094/25094] CoreContext main.cpp:452 
(main) - Marking generic episodes.
2019-03-04 22:44:13.839503 I [25094/25094] CoreContext main.cpp:464 
(main) -???? Found 0
2019-03-04 22:44:13.839515 I [25094/25094] CoreContext main.cpp:467 
(main) - Extending non-unique programids with multiple parts.
2019-03-04 22:44:14.194406 I [25094/25094] CoreContext main.cpp:518 
(main) -???? Found 0
2019-03-04 22:44:14.194417 I [25094/25094] CoreContext main.cpp:520 
(main) - Fixing missing original airdates.
2019-03-04 22:44:16.508229 I [25094/25094] CoreContext main.cpp:535 
(main) -???? Found 0 with programids
2019-03-04 22:44:16.509219 I [25094/25094] CoreContext main.cpp:555 
(main) -???? Found 0 without programids
2019-03-04 22:44:16.509239 I [25094/25094] CoreContext main.cpp:559 
(main) - Marking repeats.
2019-03-04 22:44:16.825388 I [25094/25094] CoreContext main.cpp:573 
(main) -???? Found 0
2019-03-04 22:44:16.825401 I [25094/25094] CoreContext main.cpp:575 
(main) - Unmarking new episode rebroadcast repeats.
2019-03-04 22:44:19.054360 I [25094/25094] CoreContext main.cpp:585 
(main) -???? Found 0
2019-03-04 22:44:25.277194 I [25094/25094] CoreContext main.cpp:594 
(main) - Marking episode first showings.
2019-03-04 22:44:35.562457 I [25094/25094] CoreContext main.cpp:628 
(main) -???? Found 120555
2019-03-04 22:44:35.562469 I [25094/25094] CoreContext main.cpp:630 
(main) - Marking episode last showings.
2019-03-04 22:44:45.963662 I [25094/25094] CoreContext main.cpp:664 
(main) -???? Found 120076
2019-03-04 22:44:46.043002 I [25094/25094] CoreContext main.cpp:691 
(main) -
===============================================================
| Attempting to contact the master backend for rescheduling.? |
| If the master is not running, rescheduling will happen when |
| the master backend is restarted.??????????????????????????? |
===============================================================
2019-03-04 22:44:46.044160 N [25094/25094] CoreContext main.cpp:701 
(main) - mythfilldatabase run complete.
2019-03-04 22:44:46.044228 I [25094/25094] CoreContext 
mythcontext.cpp:1663 (~MythContext) - Waiting for threads to exit.


From keemllib at gmail.com  Tue Mar  5 04:30:35 2019
From: keemllib at gmail.com (Bill Meek)
Date: Mon, 4 Mar 2019 22:30:35 -0600
Subject: [mythtv-users] Subject: Re: Daily mythfilldatabase fails after
 conversion to XMLTV
In-Reply-To: <d8b23e3c-b29d-b286-5cca-05dccc10ae92@mathcs.emory.edu>
References: <CAKGL=YKayEOKc3WmraK4MH+OCOMhCJkL_yQB8H6oPSKBsxjUUw@mail.gmail.com>
 <92e48761-3887-049c-d793-4724e18f24c7@gmail.com>
 <c465827d-40c7-5f8a-7ad6-1f3e5ed3c8ae@mathcs.emory.edu>
 <3cfd0e1f-ee0c-e8ac-a9b7-667c11d40bad@gmail.com>
 <d8b23e3c-b29d-b286-5cca-05dccc10ae92@mathcs.emory.edu>
Message-ID: <f1072cd9-d802-6ca1-467b-6f1313d36448@gmail.com>

On 3/4/19 9:57 PM, Ken Mandelberg wrote:
> I believe I have the config and permissions setup correctly now. Still no?luck?on?the?grab.?Here?is?the?whole?log
...
 > 2019-03-04 22:44:04.350149 N [25094/25094] thread_unknown mythdirs.cpp:205 (InitializeMythDirs) - Using configuration directory = /root/.mythtv
...
 > 2019-03-04 22:44:08.660926 E [25094/25094] CoreContext filldata.cpp:613 (Run) - tv_grab_zz_sdjson_sqlite  --capabilities failed or we timed 
out waiting. You may need to upgrade your xmltv grabber
...

OK, same error, but I see the backend is running as root. The command runs
for about 1 second, so the timeout part of the error message isn't likely.

I'd try running the failing command as the root user. Mine looks like this:

$ sudo --set-home --login --user=root # Not sure of PATH used by your init system...
# tv_grab_zz_sdjson_sqlite --capabilities
baseline
manualconfig
preferredmethod
lineups
apiconfig

Or, could it be as easy as having the grabber installed in a directory not
in root's $PATH...

-- 
Bill

From stse+mythtv at fsing.rootsland.net  Tue Mar  5 09:57:23 2019
From: stse+mythtv at fsing.rootsland.net (Stephan Seitz)
Date: Tue, 5 Mar 2019 10:57:23 +0100
Subject: [mythtv-users] No DVB-C channels anymore
In-Reply-To: <lh8h7edrmm31fbi2fu5tidbu1aga3ehs9c@4ax.com>
References: <20190228T183358.GA.590a9.stse@fsing.rootsland.net>
 <CAMwtTBBSOjs+EpEHAYTi-8YgGL046fwzyWkh4SRqu7RwHYxxQg@mail.gmail.com>
 <20190228T191320.GA.26f44.stse@fsing.rootsland.net>
 <lh8h7edrmm31fbi2fu5tidbu1aga3ehs9c@4ax.com>
Message-ID: <20190305T105436.GA.06780.stse@fsing.rootsland.net>

On Fr, M?r 01, 2019 at 04:12:54 +1300, Stephen Worthington wrote:
>Do you have any software from Digital Devices to use with that card?

No, the only software from Digital Devices is for Windows.

I will ask Digital Devices for advice.

Shade and sweet water!

	Stephan

-- 
| Public Keys: http://fsing.rootsland.net/~stse/keys.html |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3545 bytes
Desc: not available
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190305/c8295bbc/attachment.p7s>

From clueo8 at yahoo.com  Tue Mar  5 18:25:31 2019
From: clueo8 at yahoo.com (Tim)
Date: Tue, 5 Mar 2019 18:25:31 +0000 (UTC)
Subject: [mythtv-users] Shield TV mythfrontend issue
In-Reply-To: <1b74b430-d5b8-f6d2-a2a8-4d17d0627130@laity.ca>
References: <44bcf4fb-164b-d915-0763-437a8d320176@gmail.com>
 <1b74b430-d5b8-f6d2-a2a8-4d17d0627130@laity.ca>
Message-ID: <1526738294.480409.1551810331154@mail.yahoo.com>

 On 2/20/2019 3:38 PM, Jim Abernathy wrote:
> So I'm running mythfrontend-20190216-arm64-v30.0-19-g5100ef5870e.apk on 
> my Shield TV and watching a recorded problem that works well with 
> automatic commercial detection.
> 
> What I noticed was after a skip of 3-4 minutes there was a slight 
> jerkiness. The characters were in correct lip sync, but as a character 
> shook her head to indicate "no" the action was like the head moved at 
> less FPS than normal. The head movement looked like a series of still 
> frames but over the proper time for the movement. As they talked they 
> were in lip sync.
> 
> So I backed up the recording 15 seconds and then paused it for 2 seconds 
> before playing.? This time the picture and lip sync were perfect.
> 
> So at least for me I find that big skips in time mess things up a little 
> and I have to pause for a very short time to fix them. I have not tested 
> this on another mythfrontend. The only other one I have is a Core i7 
> with a Nvidia GT710.? Kodi on a RP3 B+ doesn't have this issue.
> 
> Jim A

I've noticed the audio getting off sync on mythfrontend-20181124-arm64-v30-Pre-983-gca71c59e61a.apk as well when jumping through commercials and came to the same conclusion that pausing and un-pausing gets it back into sync... I just updated my shield to the latest?mythfrontend-20190216-arm64-v30.0-19-g5100ef5870e.apk remotely, will have to test that one out tonight.  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190305/943e5e14/attachment-0001.html>

From km at mathcs.emory.edu  Tue Mar  5 18:49:06 2019
From: km at mathcs.emory.edu (Ken Mandelberg)
Date: Tue, 5 Mar 2019 13:49:06 -0500
Subject: [mythtv-users] Daily mythfilldatabase fails after conversion to
 XMLTV
In-Reply-To: <f1072cd9-d802-6ca1-467b-6f1313d36448@gmail.com>
References: <CAKGL=YKayEOKc3WmraK4MH+OCOMhCJkL_yQB8H6oPSKBsxjUUw@mail.gmail.com>
 <92e48761-3887-049c-d793-4724e18f24c7@gmail.com>
 <c465827d-40c7-5f8a-7ad6-1f3e5ed3c8ae@mathcs.emory.edu>
 <3cfd0e1f-ee0c-e8ac-a9b7-667c11d40bad@gmail.com>
 <d8b23e3c-b29d-b286-5cca-05dccc10ae92@mathcs.emory.edu>
 <f1072cd9-d802-6ca1-467b-6f1313d36448@gmail.com>
Message-ID: <fd95775e-77f8-7a34-c6e0-fda452f3abcf@mathcs.emory.edu>

Bill, thanks for the help.

In the end I frontended mythfilldatabase with strace so I could follow 
it through to the grabber.

What I was missing was /root/.xmltv.? I had misunderstood and thought 
the database path in the mythtv config file in /root/.mythtv which 
pointed into my $HOME/.xmltv was sufficient.

A symbolic link from $HOME/.xmltv to /root was all I needed. Its now 
working properly.

Ken


From klaas.de.waal at gmail.com  Tue Mar  5 23:04:20 2019
From: klaas.de.waal at gmail.com (Klaas de Waal)
Date: Wed, 6 Mar 2019 00:04:20 +0100
Subject: [mythtv-users] No DVB-C channels anymore
In-Reply-To: <20190305T105436.GA.06780.stse@fsing.rootsland.net>
References: <20190228T183358.GA.590a9.stse@fsing.rootsland.net>
 <CAMwtTBBSOjs+EpEHAYTi-8YgGL046fwzyWkh4SRqu7RwHYxxQg@mail.gmail.com>
 <20190228T191320.GA.26f44.stse@fsing.rootsland.net>
 <lh8h7edrmm31fbi2fu5tidbu1aga3ehs9c@4ax.com>
 <20190305T105436.GA.06780.stse@fsing.rootsland.net>
Message-ID: <CANcAQaM+wPVurLYUZnTwMLWerq2CyMOp+zT4s_spsCcvaKhk8w@mail.gmail.com>

On Tue, Mar 5, 2019 at 10:58 AM Stephan Seitz
<stse+mythtv at fsing.rootsland.net> wrote:
>
> On Fr, M?r 01, 2019 at 04:12:54 +1300, Stephen Worthington wrote:
> >Do you have any software from Digital Devices to use with that card?
>
> No, the only software from Digital Devices is for Windows.
>
> I will ask Digital Devices for advice.
>
> Shade and sweet water!
>
>         Stephan


Have not tried it yet myself but it should be possible to use the
dvb5-fe-tool from linuxtv.org to set the tuner to DVB-C (or -T or -S)
before starting mythtv.

Groetjes,
Klaas

From jam at tigger.ws  Wed Mar  6 00:28:50 2019
From: jam at tigger.ws (James Linder)
Date: Wed, 6 Mar 2019 08:28:50 +0800
Subject: [mythtv-users] mac osx
In-Reply-To: <mailman.15.1551810343.1604.mythtv-users@mythtv.org>
References: <mailman.15.1551810343.1604.mythtv-users@mythtv.org>
Message-ID: <077516E5-1CD5-4C88-B6A6-C1BA3688240F@tigger.ws>

Hi All

Sourceforge and macports do not have apps older than 0.28
A while ago I found a 29 dmg (macs install mechanism)
Frontend (backend is linux) crashes often enough to be irritating so I decided to build a recent fixes, that I can trouble shoot.

Is is very difficult? Why has nobody built a version?

I have a complete development environment including QT, can do macports etc. I built my backend making good use of anisable. Before I venture where it seems that nobody dares tread is there any advice I should heed?

Thanks
James

PS I did not post to the dev list, but any devs reading this ... please comment

From ctreleaven at cogeco.ca  Wed Mar  6 01:23:44 2019
From: ctreleaven at cogeco.ca (Craig Treleaven)
Date: Tue, 5 Mar 2019 20:23:44 -0500
Subject: [mythtv-users] mac osx
In-Reply-To: <077516E5-1CD5-4C88-B6A6-C1BA3688240F@tigger.ws>
References: <mailman.15.1551810343.1604.mythtv-users@mythtv.org>
 <077516E5-1CD5-4C88-B6A6-C1BA3688240F@tigger.ws>
Message-ID: <077386AE-FBA6-467A-938F-379F69895280@cogeco.ca>

> On Mar 5, 2019, at 7:28 PM, James Linder <jam at tigger.ws> wrote:
> 
> Hi All
> 
> Sourceforge and macports do not have apps older than 0.28
> A while ago I found a 29 dmg (macs install mechanism)
> Frontend (backend is linux) crashes often enough to be irritating so I decided to build a recent fixes, that I can trouble shoot.
> 
> Is is very difficult? Why has nobody built a version?
> 
> I have a complete development environment including QT, can do macports etc. I built my backend making good use of anisable. Before I venture where it seems that nobody dares tread is there any advice I should heed?
> 
> Thanks
> James
> 
> PS I did not post to the dev list, but any devs reading this ... please comment

https://forum.mythtv.org/viewtopic.php?f=26&t=2216&start=60#p14335

Craig



From lists at the-pearsons.co.uk  Wed Mar  6 05:33:14 2019
From: lists at the-pearsons.co.uk (=?utf-8?Q?Dave_Pearson_=28Lists=29?=)
Date: Wed, 6 Mar 2019 05:33:14 +0000
Subject: [mythtv-users] mac osx
Message-ID: <kcis.C6CA94810E1B41A3852D9833943F0813@0ca469df22c5>

Have you tried the Frointend from here:

https://www.mythtv.org/wiki/MythTV_on_Mac_OS_X#Pre-built_Downloads



I've been using a MythFrontend on my Mac for a long time and don't suffer any crashes.?



Regards,

Dave.

-----Original message-----
From: James Linder?<jam at tigger.ws>
Sent: Wednesday 6th March 2019 0:29
To: mythtv-users at mythtv.org
Subject: [mythtv-users] mac osx


Hi All

Sourceforge and macports do not have apps older than 0.28
A while ago I found a 29 dmg (macs install mechanism)
Frontend (backend is linux) crashes often enough to be irritating so I decided to build a recent fixes, that I can trouble shoot.

Is is very difficult? Why has nobody built a version?

I have a complete development environment including QT, can do macports etc. I built my backend making good use of anisable. Before I venture where it seems that nobody dares tread is there any advice I should heed?

Thanks
James

PS I did not post to the dev list, but any devs reading this ... please comment
_______________________________________________
mythtv-users mailing list
mythtv-users at mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190306/e33c8cf1/attachment.html>

From mythtv at hambone.e4ward.com  Wed Mar  6 13:53:07 2019
From: mythtv at hambone.e4ward.com (Jerry)
Date: Wed, 6 Mar 2019 08:53:07 -0500
Subject: [mythtv-users] Problem with v30 Rpmfusion RPMS
Message-ID: <CAO_Sck7=jMG5uA_Ux1JyQmdiKF3a5cOJt-XrmOLCwVMLO4cdPA@mail.gmail.com>

I upgraded this morning and I could not add my HDHomerun tuner.  The option
was missing from mythtv-setup.  I looked at the SPEC file but didn't see a
reference to any HDHomerun libraries.  I also did not see any reference to
those libraries for the Debian compile instructions, so maybe that's not
the issue.

I just wanted to give a heads-up in case anyone else needs a HDHomerun in
their setup.  I went back to my old v29 version for the time being.

In case the below output matters, I have included it here.  I posted this
also to the RPMFusion bugzilla.

$ mythbackend --version
Please attach all output as a file in bug reports.
MythTV Version : v30.0-v30.0-15-gb774c4140b
MythTV Branch : fixes/30
Network Protocol : 91
Library API : 30.20181231-1
QT Version : 5.11.3
Options compiled in:
 linux debug use_hidesyms using_alsa using_jack using_oss using_pulse
using_pulseoutput using_backend using_bdjava using_bindings_perl
using_bindings_python using_bindings_php using_crystalhd using_dvb
using_firewire using_frontend using_vbox using_ceton using_hdpvr using_ivtv
using_joystick_menu using_libcec using_libcrypto using_libdns_sd
using_libfftw3 using_libxml2 using_lirc using_mheg using_opengl
using_opengl_video using_opengl_themepainter using_qtwebkit using_qtscript
using_qtdbus using_taglib using_v4l2 using_x11 using_xnvctrl
using_xnvctrl_external using_libbluray_external using_xrandr using_xv
using_debugtype using_systemd_notify using_systemd_journal using_bdjava
using_bindings_perl using_bindings_python using_bindings_php
using_fontconfig using_freetype2 using_mythtranscode using_opengl
using_vaapi using_vaapi2 using_vdpau using_ffmpeg_threads using_mheg
using_libass using_libxml2 using_libmp3lame

Thanks,
Jerry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190306/a46bd32a/attachment.html>

From hobbes1069 at gmail.com  Wed Mar  6 14:12:46 2019
From: hobbes1069 at gmail.com (Richard Shaw)
Date: Wed, 6 Mar 2019 08:12:46 -0600
Subject: [mythtv-users] Problem with v30 Rpmfusion RPMS
In-Reply-To: <CAO_Sck7=jMG5uA_Ux1JyQmdiKF3a5cOJt-XrmOLCwVMLO4cdPA@mail.gmail.com>
References: <CAO_Sck7=jMG5uA_Ux1JyQmdiKF3a5cOJt-XrmOLCwVMLO4cdPA@mail.gmail.com>
Message-ID: <CAN3TeO3EpxbOBRP6Q+9XLz36J03LeDCYrt2LjCCXyR8Do6HOog@mail.gmail.com>

On Wed, Mar 6, 2019 at 7:54 AM Jerry <mythtv at hambone.e4ward.com> wrote:

> I upgraded this morning and I could not add my HDHomerun tuner.  The
> option was missing from mythtv-setup.  I looked at the SPEC file but didn't
> see a reference to any HDHomerun libraries.  I also did not see any
> reference to those libraries for the Debian compile instructions, so maybe
> that's not the issue.
>

I'll double check..  I had some issues with python-requests-cache (python 2
package was dropped from rawhide and had to be readded) and I had gone down
the rabbit hole trying to work around it and ended up doing a git reset.
They used to bundle the HDHR library and dropped that in v30 but I might
have missed readding it to the build requirements.

Thanks,
Richard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190306/24ee67b5/attachment.html>

From johnpilk222 at gmail.com  Wed Mar  6 16:39:29 2019
From: johnpilk222 at gmail.com (John Pilkington)
Date: Wed, 6 Mar 2019 16:39:29 +0000
Subject: [mythtv-users] Segfault in Frontend master: Previously Recorded
Message-ID: <7cc9efaf-6283-195f-2333-93842b2e99a6@gmail.com>

I have what feels like a new segfault in frontend master, reproducible 
in F28, el7 and Firestick 4k.  F28 says it has created a core dump, el7 
reports and exits quickly, Firestick (20190224) needs a device restart.

Code 1, PID 8, UID 0, Value 0 in F28, 0xXXXXXX in el7

The steps to reproduce are ones that I have used quite often in el7, 
rarely in F28 and only in today's test on the Firestick.

Manage Recordings > Schedule Recordings > Programme Guide > highlight a 
recording that has not been previously recorded.

E > Schedule Info > Previously Recorded

No recording found, press right or left arrow

'Loading' popup appears and segfault follows.  If recordings were 
identified, it lists them, and will continue on command.

In F28 a file appears briefly in /tmp.  I've looked at the Debug wiki 
but hope the steps above might point to the cause of the problem.

John P






From mythtv at blandford.net  Wed Mar  6 16:45:09 2019
From: mythtv at blandford.net (Michael)
Date: Wed, 6 Mar 2019 09:45:09 -0700
Subject: [mythtv-users] Problem with v30 Rpmfusion RPMS
In-Reply-To: <CAO_Sck7=jMG5uA_Ux1JyQmdiKF3a5cOJt-XrmOLCwVMLO4cdPA@mail.gmail.com>
References: <CAO_Sck7=jMG5uA_Ux1JyQmdiKF3a5cOJt-XrmOLCwVMLO4cdPA@mail.gmail.com>
Message-ID: <c44bc853-9c3a-747f-9056-a89cb930f0b4@blandford.net>

On 3/6/19 6:53 AM, Jerry wrote:
> I upgraded this morning and I could not add my HDHomerun tuner.? The 
> option was missing from mythtv-setup.? I looked at the SPEC file but 
> didn't see a reference to any HDHomerun libraries.? I also did not see 
> any reference to those libraries for the Debian compile instructions, 
> so maybe that's not the issue.
>
> I just wanted to give a heads-up in case anyone else needs a HDHomerun 
> in their setup.? I went back to my old v29 version for the time being.
>
> In case the below output matters, I have included it here.? I posted 
> this also to the RPMFusion bugzilla.
>

I had upgraded to the packages from testing a few days ago and noticed I 
had no shows in my upcoming recording schedule and rolled back.??? After 
seeing your note today, I tried upgrading again.?? I see the same 
issue.? Looking through the backend logs, I see:


019-03-06 09:40:19.752247 E [32044/32044] CoreContext 
recorders/channelbase.cpp:789 (CreateChannel) - ChannelBase: 
CreateChannel() Error:
HDHOMERUN card configured on video device 103CA949,
but MythTV was not compiled with HDHOMERUN support.

Recompile MythTV with HDHOMERUN support or remove the card
from the configuration and restart MythTV.

2019-03-06 09:40:19.752253 E [32044/32044] CoreContext 
main_helpers.cpp:205 (setupTVs) - Problem with capture cards. Card 1 
failed init


So, it does look like the rpmfusion packages are missing HDHOMERUN support.


I will roll back for now.


Michael



From pb.mythtv at gmail.com  Wed Mar  6 17:59:11 2019
From: pb.mythtv at gmail.com (Peter Bennett)
Date: Wed, 6 Mar 2019 12:59:11 -0500
Subject: [mythtv-users] Segfault in Frontend master: Previously Recorded
In-Reply-To: <7cc9efaf-6283-195f-2333-93842b2e99a6@gmail.com>
References: <7cc9efaf-6283-195f-2333-93842b2e99a6@gmail.com>
Message-ID: <8e7cfbfb-3eeb-5956-62fd-821156c6a81a@gmail.com>



On 3/6/19 11:39 AM, John Pilkington wrote:
> I have what feels like a new segfault in frontend master, reproducible 
> in F28, el7 and Firestick 4k.? F28 says it has created a core dump, 
> el7 reports and exits quickly, Firestick (20190224) needs a device 
> restart.
>
> Code 1, PID 8, UID 0, Value 0 in F28, 0xXXXXXX in el7
>
> The steps to reproduce are ones that I have used quite often in el7, 
> rarely in F28 and only in today's test on the Firestick.
>
> Manage Recordings > Schedule Recordings > Programme Guide > highlight 
> a recording that has not been previously recorded.
>
> E > Schedule Info > Previously Recorded
>
> No recording found, press right or left arrow
>
> 'Loading' popup appears and segfault follows.? If recordings were 
> identified, it lists them, and will continue on command.
>
> In F28 a file appears briefly in /tmp.? I've looked at the Debug wiki 
> but hope the steps above might point to the cause of the problem.
>
> John P
>
>
>
>
>
It looks like a bug with the previously recorded list changes.? I will 
take a look at it.

Peter

From mythtv at hambone.e4ward.com  Wed Mar  6 18:32:31 2019
From: mythtv at hambone.e4ward.com (Jerry)
Date: Wed, 6 Mar 2019 13:32:31 -0500
Subject: [mythtv-users] Problem with v30 Rpmfusion RPMS
In-Reply-To: <c44bc853-9c3a-747f-9056-a89cb930f0b4@blandford.net>
References: <CAO_Sck7=jMG5uA_Ux1JyQmdiKF3a5cOJt-XrmOLCwVMLO4cdPA@mail.gmail.com>
 <c44bc853-9c3a-747f-9056-a89cb930f0b4@blandford.net>
Message-ID: <CAO_Sck6FC_v0EGvZj9J_=A6wKn4im13kaVRwDh3xsL--Nbt0GA@mail.gmail.com>

If you add this line to the mythtv.spec file:

BuildRequires:  hdhomerun-devel

in the section where the other build requirements are listed, and rebuild
the RPMs with mock or with rpmbuild, you can fix it yourself.

I tried to document the rpm building process in this thread if you're
interested.  Richard said he is rebuilding the packages with hdhomerun
support, so you could just wait a few days and grab them from testing as
well.

https://lists.gt.net/mythtv/users/617567?search_string=mock;#617567

Just remember to add one to the build number so yours don't get overwritten
by the ones that are in RPMFusion.

If you need any of those files, like the mock file that has both rpmfusion
and the fedora repositories included, let me know and I'll send it to you.
I think the one I have posted there is for F28 but you can migrate it to
F29.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190306/3651de5a/attachment.html>

From johnpilk222 at gmail.com  Wed Mar  6 19:03:50 2019
From: johnpilk222 at gmail.com (John Pilkington)
Date: Wed, 6 Mar 2019 19:03:50 +0000
Subject: [mythtv-users] Segfault in Frontend master: Previously Recorded
In-Reply-To: <8e7cfbfb-3eeb-5956-62fd-821156c6a81a@gmail.com>
References: <7cc9efaf-6283-195f-2333-93842b2e99a6@gmail.com>
 <8e7cfbfb-3eeb-5956-62fd-821156c6a81a@gmail.com>
Message-ID: <f5face81-5e05-2847-5eca-12584db6bf7c@gmail.com>

On 06/03/2019 17:59, Peter Bennett wrote:
> 

>> E > Schedule Info > Previously Recorded
>>
>> No recording found, press right or left arrow
>>
>> 'Loading' popup appears and segfault follows.? If recordings were 
>> identified, it lists them, and will continue on command.
>>
> It looks like a bug with the previously recorded list changes.? I will 
> take a look at it.
> 
> Peter

Thank you.  It works properly with Escape.  Perhaps I've always used that.

John


From veehexx at zoho.com  Wed Mar  6 19:24:44 2019
From: veehexx at zoho.com (Tim Draper)
Date: Wed, 06 Mar 2019 19:24:44 +0000
Subject: [mythtv-users] git master 0e7e57f commit - livetv?
Message-ID: <16954762a44.11a048d9478619.7927489630634130750@zoho.com>

probably one for peter in reguard to this: https://github.com/MythTV/mythtv/commit/0e7e57f9c2eb0e2c4f47dcb30788a4e54d6808ba

would this affect stuttering in livetv? I was watching HD livetv (BBC2 HD i think) last night as it was very stuttery.  pause&resume didnt fix but recording and playing the recording gave smooth playback.

if it does cover livetv, any immediate plans to commit to the fixes/30 branch?

thanks, Tim


From pb.mythtv at gmail.com  Wed Mar  6 20:17:22 2019
From: pb.mythtv at gmail.com (Peter Bennett)
Date: Wed, 6 Mar 2019 15:17:22 -0500
Subject: [mythtv-users] git master 0e7e57f commit - livetv?
In-Reply-To: <16954762a44.11a048d9478619.7927489630634130750@zoho.com>
References: <16954762a44.11a048d9478619.7927489630634130750@zoho.com>
Message-ID: <e7e34976-60c2-75fe-cbae-9decdf1853f6@gmail.com>



On 3/6/19 2:24 PM, Tim Draper wrote:
> probably one for peter in reguard to this: https://github.com/MythTV/mythtv/commit/0e7e57f9c2eb0e2c4f47dcb30788a4e54d6808ba
>
> would this affect stuttering in livetv? I was watching HD livetv (BBC2 HD i think) last night as it was very stuttery.  pause&resume didnt fix but recording and playing the recording gave smooth playback.
>
> if it does cover livetv, any immediate plans to commit to the fixes/30 branch?
>
> thanks, Tim
>
>

Try running mythfrontend with -v playback. See if you see messages like 
this repeated many times. If so this should fix it. Otherwise, probably not.

AFD: Selected FPS is 50 (avg 25 codec 0 container 90000 estimated 50)
AFD: avFPS(50) != seqFPS(25)
Player(1): SetFrameInterval ps:1 scan:3
VidOutGL: InputChanged(1920,1080,1.77778) H.264 MEDIACODEC->H.264 MEDIACODEC
DispInfo: rate:59.9401 h:1080 w:1920 xdpi:213 ydpi:213
Player(1): ClearAfterSeek(1)
Player(1): LoadFilters(''..) -> 0x0
Player(1): detectInterlace(Detect Scan, Interlaced Scan, 25, 1080) 
->Interlaced Scan

If there are no complaints or problems reported I will move it to v30 in 
a week or so.

Peter

From hobbes1069 at gmail.com  Wed Mar  6 22:09:56 2019
From: hobbes1069 at gmail.com (Richard Shaw)
Date: Wed, 6 Mar 2019 16:09:56 -0600
Subject: [mythtv-users] Problem with v30 Rpmfusion RPMS
In-Reply-To: <CAO_Sck7=jMG5uA_Ux1JyQmdiKF3a5cOJt-XrmOLCwVMLO4cdPA@mail.gmail.com>
References: <CAO_Sck7=jMG5uA_Ux1JyQmdiKF3a5cOJt-XrmOLCwVMLO4cdPA@mail.gmail.com>
Message-ID: <CAN3TeO3GhcYMVnMwbHnpRh9m_iWVVVbjeuftq59-RTBK=Si8LQ@mail.gmail.com>

Packages are built, just need to wait for them to be pushed.

http://koji.rpmfusion.org/koji/packageinfo?packageID=162

Thanks,
Richard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190306/7f44f2e5/attachment.html>

From jaham at gmx.net  Wed Mar  6 22:47:03 2019
From: jaham at gmx.net (Jan Hambrecht)
Date: Wed, 06 Mar 2019 23:47:03 +0100
Subject: [mythtv-users] No DVB-C channels anymore
In-Reply-To: <20190228T183358.GA.590a9.stse@fsing.rootsland.net>
References: <20190228T183358.GA.590a9.stse@fsing.rootsland.net>
Message-ID: <2453204.rat3DMXqDE@delle>

Am Donnerstag, 28. Februar 2019, 18:50:14 CET schrieb Stephan Seitz:
> I?m wondering why the subtype is T2. The card can DVB-C and -T, but
> I can?t change the type. I don?t know if this is the problem.
> 
> I checked all cables, they are fine.
> 
> I don?t have any other DVB-C devices so I can?t do further tests.
> 
> Has anyone an idea?

If you are on myth v30 then ticket #13014 might be relevant.
See https://code.mythtv.org/trac/ticket/13014 for details, comment #9 is the 
interesting thing regarding the latest release.

Ciao Jan



From johnpilk222 at gmail.com  Wed Mar  6 22:58:36 2019
From: johnpilk222 at gmail.com (John Pilkington)
Date: Wed, 6 Mar 2019 22:58:36 +0000
Subject: [mythtv-users] Segfault in Frontend master: Previously Recorded
In-Reply-To: <8e7cfbfb-3eeb-5956-62fd-821156c6a81a@gmail.com>
References: <7cc9efaf-6283-195f-2333-93842b2e99a6@gmail.com>
 <8e7cfbfb-3eeb-5956-62fd-821156c6a81a@gmail.com>
Message-ID: <06e6bf84-3df5-e4e3-79b9-e17018648bc8@gmail.com>

On 06/03/2019 17:59, Peter Bennett wrote:
> 

>> E > Schedule Info > Previously Recorded
>>
>> No recording found, press right or left arrow
>>
>> 'Loading' popup appears and segfault follows.? If recordings were 
>> identified, it lists them, and will continue on command.
>>
> It looks like a bug with the previously recorded list changes.? I will 
> take a look at it.
> 
> Peter

Thank you.  It works properly with Escape.  Perhaps I've always used that.
-------------

This is now https://code.mythtv.org/trac/ticket/13421

John P



From allen.p.edwards at gmail.com  Wed Mar  6 23:56:02 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Wed, 6 Mar 2019 15:56:02 -0800
Subject: [mythtv-users] Can't get my projector to work with Myth --
 Solved
In-Reply-To: <CAH8UtKOT7uZoj68_pBbPcTx_=4Ug3N7CmtsQsJbWFdQWhLZnJw@mail.gmail.com>
References: <CAH8UtKOMT3uQXme1cK3d8JoK7S-Ta4abnkoEsTaHFQzyc1cW-g@mail.gmail.com>
 <pmbm7e1u2mmam8t659n0ch7o5rv6qt655f@4ax.com>
 <CAH8UtKOhuRFhFcL-ddQ-LSsfLUsZA+oLnTGmCbxjgPtY35JJfg@mail.gmail.com>
 <983fb542-f7ed-7d36-e26a-08559f93d92a@stadt.ca>
 <CAH8UtKOT7uZoj68_pBbPcTx_=4Ug3N7CmtsQsJbWFdQWhLZnJw@mail.gmail.com>
Message-ID: <CAH8UtKN65vkAwRpWEqQ_8mcJHQAX-w9hNDV+Un=qmwx4ur752A@mail.gmail.com>

I got the projector working. The issue was the resolution and a more
powerful 5 volt supply to the HDMI audio stripper.

What I did was changed xorg.conf to add a second metamodes line as follows

    Option         "metamodes" "VGA-0: nvidia-auto-select +0+0, HDMI-0:
1920x1080  +1280+0"
    Option         "metamodes" "VGA-0: nvidia-auto-select +0+0, HDMI-0:
1280x720  +1280+0"

Then I connect the projector and enter xrandr -s 0
Then to switch back to the TV, I connect it and enter xrandr -s 0. I find
it strange that the same command selects 1080p when the TV is connected and
720p when the projector is connected. I do need to issue the command to
switch to 720p when I plug in the projector.

I would have thought I would need to enter xrandr -s 1 for one of these
cases but I guess with the projector it just rejects the first option and
the second one becomes -s 0.

It is a bit strange that I cannot switch to the 720p mode with the TV
connected but if I issue xrandr -s 1 the TV is just disconnected from the
desktop and myth moves to the Samsung. To get it back on the TV, I need to
do xrandr -s 0 and close and open Myth to get it to show up in the correct
location.

If I comment out the 1080p line, the TV will work in 720p so there is
clearly something I don't understand about how X is dealing with this.  But
it works so that is the important part.

It would be nice to have an HDMI switch so I don't have to switch the
cables but that is the next step.

Thanks all for your help.

Allen

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190306/bf2c2067/attachment.html>

From mythtv at blandford.net  Thu Mar  7 17:15:33 2019
From: mythtv at blandford.net (Michael)
Date: Thu, 7 Mar 2019 10:15:33 -0700
Subject: [mythtv-users] Problem with v30 Rpmfusion RPMS
In-Reply-To: <CAN3TeO3GhcYMVnMwbHnpRh9m_iWVVVbjeuftq59-RTBK=Si8LQ@mail.gmail.com>
References: <CAO_Sck7=jMG5uA_Ux1JyQmdiKF3a5cOJt-XrmOLCwVMLO4cdPA@mail.gmail.com>
 <CAN3TeO3GhcYMVnMwbHnpRh9m_iWVVVbjeuftq59-RTBK=Si8LQ@mail.gmail.com>
Message-ID: <c0aef8b2-1d9b-08d0-70c2-e3e54f123f4f@blandford.net>

On 3/6/19 3:09 PM, Richard Shaw wrote:
> Packages are built, just need to wait for them to be pushed.
>
> http://koji.rpmfusion.org/koji/packageinfo?packageID=162
>


I downloaded the packages from Koji and upgraded.?? They seem to 
identify the tuner now and I can watch live TV.


I will test further today.


Michael



From jam at tigger.ws  Fri Mar  8 04:44:24 2019
From: jam at tigger.ws (James Linder)
Date: Fri, 8 Mar 2019 12:44:24 +0800
Subject: [mythtv-users] mail stopped
Message-ID: <EAA1649C-28EE-4EA2-87F3-501EC5DACE51@tigger.ws>

Gday all. My mail digest stopped on 3 March, but other mail is good

Either 
The user mail digest faltered
Or
My mythtv-users setup has failed.

If anybody reads this normally would you kindly reply saying little or nothing, then I?ll check my settings. If no one replies I assume mythtv-users is broken

If I get 10 000 replies then I deserve it. I promise to bin them with no futher action ie I?ll NOT harvest addresses or any such aweful abuse!

Thanks james

PS as soon as I get any reply I shall answer this saying thanks so everyone can say ?done'

From allen.p.edwards at gmail.com  Fri Mar  8 05:02:52 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Thu, 7 Mar 2019 21:02:52 -0800
Subject: [mythtv-users] mail stopped
In-Reply-To: <EAA1649C-28EE-4EA2-87F3-501EC5DACE51@tigger.ws>
References: <EAA1649C-28EE-4EA2-87F3-501EC5DACE51@tigger.ws>
Message-ID: <CAH8UtKP7UGjLo=DFqZNWj3C==5cqr7SGZiqpQ18DhLy49N-Pwg@mail.gmail.com>

Little

On Thu, Mar 7, 2019 at 8:44 PM James Linder <jam at tigger.ws> wrote:

> Gday all. My mail digest stopped on 3 March, but other mail is good
>
> Either
> The user mail digest faltered
> Or
> My mythtv-users setup has failed.
>
> If anybody reads this normally would you kindly reply saying little or
> nothing, then I?ll check my settings. If no one replies I assume
> mythtv-users is broken
>
> If I get 10 000 replies then I deserve it. I promise to bin them with no
> futher action ie I?ll NOT harvest addresses or any such aweful abuse!
>
> Thanks james
>
> PS as soon as I get any reply I shall answer this saying thanks so
> everyone can say ?done'
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190307/35978612/attachment.html>

From Marius.schrecker at lyse.net  Fri Mar  8 05:07:16 2019
From: Marius.schrecker at lyse.net (Marius.schrecker at lyse.net)
Date: Fri, 08 Mar 2019 06:07:16 +0100
Subject: [mythtv-users] mail stopped
References: <EAA1649C-28EE-4EA2-87F3-501EC5DACE51@tigger.ws>
 <CAH8UtKP7UGjLo=DFqZNWj3C==5cqr7SGZiqpQ18DhLy49N-Pwg@mail.gmail.com>
Message-ID: <-jijd4ftcu6k7ueb5f9ryyyet-bglhqom3fydo1dueda2c7rxd-2zjws3-9cam0-ub52h1-mfa0xtu17vzwfgkmr7-aakjlu-pgpzea3w85ww-p80lti-sev2uz-l0kiofddu17n-x8cbocd608wv-fqq63y.1552021636812@email.android.com>

An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190308/612b4206/attachment-0001.html>

From jam at tigger.ws  Fri Mar  8 05:11:11 2019
From: jam at tigger.ws (James Linder)
Date: Fri, 8 Mar 2019 13:11:11 +0800
Subject: [mythtv-users] mail stopped
In-Reply-To: <mailman.39.1552021626.1604.mythtv-users@mythtv.org>
References: <mailman.39.1552021626.1604.mythtv-users@mythtv.org>
Message-ID: <8BA1DC7C-40AE-4F76-894C-CA135DD7A9A0@tigger.ws>

Thanks
I received the first digest in a week
Thanks
James

From jam at tigger.ws  Fri Mar  8 05:50:37 2019
From: jam at tigger.ws (James Linder)
Date: Fri, 8 Mar 2019 13:50:37 +0800
Subject: [mythtv-users] mac osx
In-Reply-To: <mailman.39.1552021626.1604.mythtv-users@mythtv.org>
References: <mailman.39.1552021626.1604.mythtv-users@mythtv.org>
Message-ID: <87708C36-B4E7-4687-B7A9-F9AC4A25616A@tigger.ws>



> On 8 Mar 2019, at 1:07 pm, mythtv-users-request at mythtv.org wrote:
> 
> Have you tried the Frointend from here:
> 
> https://www.mythtv.org/wiki/MythTV_on_Mac_OS_X#Pre-built_Downloads

I am about to. Ive been using

MythFrontend-OSX-29-fixes.zip

[Haycorn] /Users/jam [122]% /Applications/MythFrontend.app/Contents/MacOS/MythFrontend --version
Please attach all output as a file in bug reports.
MythTV Version : v30-Pre
MythTV Branch :
Network Protocol : 91
Library API : 30.20170212-1
QT Version : 5.5.1
Options compiled in:
 profile using_corevideo using_backend using_bindings_php using_darwin using_firewire using_frontend using_hdhomerun using_vbox using_ceton using_libdns_sd using_mheg using_opengl using_opengl_video using_opengl_themepainter using_qtwebkit using_qtscript using_qtdbus using_taglib using_profiletype using_appleremote using_bindings_php using_freetype2 using_mythtranscode using_opengl using_ffmpeg_threads using_mheg using_libmp3lame

> 
> I've been using a MythFrontend on my Mac for a long time and don't suffer any crashes.?
> 

The irritating thing: I use it with High Sierra on my mid 2011 iMac 27 where is is rock sold and never falters

I use it on my (new) mac book (also High Sierra)  where it often crashes on menu->scan (5 times in 15 min, then not for hours). I do get crash reports that (I?ve not yet studied in detail) but the seem to show QT stuff in the trace back

Lets see the dmg from sourceforge
James

From jam at tigger.ws  Fri Mar  8 05:35:15 2019
From: jam at tigger.ws (James Linder)
Date: Fri, 8 Mar 2019 13:35:15 +0800
Subject: [mythtv-users] mac osx
In-Reply-To: <mailman.39.1552021626.1604.mythtv-users@mythtv.org>
References: <mailman.39.1552021626.1604.mythtv-users@mythtv.org>
Message-ID: <845B19AF-41D9-4429-9CA5-4B0AFD28BC15@tigger.ws>



> On 8 Mar 2019, at 1:07 pm, mythtv-users-request at mythtv.org wrote:
> 
>> Sourceforge and macports do not have apps older than 0.28
>> A while ago I found a 29 dmg (macs install mechanism)
>> Frontend (backend is linux) crashes often enough to be irritating so I decided to build a recent fixes, that I can trouble shoot.
>> 
>> Is is very difficult? Why has nobody built a version?
>> 
>> I have a complete development environment including QT, can do macports etc. I built my backend making good use of anisable. Before I venture where it seems that nobody dares tread is there any advice I should heed?
>> 
>> Thanks
>> James
>> 
>> PS I did not post to the dev list, but any devs reading this ... please comment
> 
> https://forum.mythtv.org/viewtopic.php?f=26&t=2216&start=60#p14335

Craig thanks; ouch!
I?ll do some fiddling to see how myth runs in a VM first.
James

From allen.p.edwards at gmail.com  Fri Mar  8 06:45:16 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Thu, 7 Mar 2019 22:45:16 -0800
Subject: [mythtv-users] CTRL-ALT-BACKSPACE
Message-ID: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>

I upgraded from Mythbuntu8 to mythbuntu18. X just froze and we used to use
CTRL-ALT-BS but I know it has been removed.

I have been Googling this and found that this was replaced by
AysRq-rightAlt-K but that doesn't work. Then I found a nice gui checkbox
that restored it but that isn't there.  I found several different files I
could create, all different, and the instructions below that look like they
might work but I don't want to blow up the system so can someone tell me if
this is correct for Mythbuntu 18? (I modified it slightly to use nano).
Basically I found almost a dozen ways to enable this in xfce but they were
all different.  In the past very bad things happened when I just followed
online instructions.  That is why I am asking for help

Thanks,

Allen

Enable the key combination Ctrl+Alt+Backspace

   1.

   Open the Terminal and run sudo nano /etc/default/keyboard
   2.

   Find the line:
   XKBOPTIONS=""
   3.

   Replace it with:
   XKBOPTIONS="terminate:ctrl_alt_bksp"
   4.

   Save the modified file and close it.
   5.

   Reboot your computer to take affect.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190307/dafe94f8/attachment.html>

From jsbien at mimuw.edu.pl  Fri Mar  8 07:17:52 2019
From: jsbien at mimuw.edu.pl (Janusz S. =?utf-8?Q?Bie=C5=84?=)
Date: Fri, 08 Mar 2019 08:17:52 +0100
Subject: [mythtv-users] Web Frontend stopped working yesterday
Message-ID: <865zstomvz.fsf@mimuw.edu.pl>


As my Internet provider again changed my IP and I no longer use a MythTV
frontend on another computer, I set the backend IP to 127.0.0.1. I made
also some system upgrades, which did not change MythTV but perhaps some
libraries used. I don't remember any other intentional changes.

Frontend works, Web frontend does not:

Firefox can?t establish a connection to the server at localhost:6544.

Nmap doesn't show the port 6544:

--8<---------------cut here---------------start------------->8---
Starting Nmap 7.70 ( https://nmap.org ) at 2019-03-08 07:28 CET
Nmap scan report for localhost (127.0.0.1)
Host is up (0.000092s latency).
Other addresses for localhost (not scanned): ::1
Not shown: 994 closed ports
PORT     STATE SERVICE
22/tcp   open  ssh
25/tcp   open  smtp
80/tcp   open  http
631/tcp  open  ipp
3306/tcp open  mysql
6543/tcp open  mythtv
--8<---------------cut here---------------end--------------->8---

An attempt to connect to

http://localhost:6543/

just gives the message "Waiting for localhost..."

MythTV is version 30.0-dmo3 on Debian testing.

Best regards

Janusz

P.S. I notice another probably unrelated problem: backend stopped at
night for some unknown reason.

-- 
             ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

From stephen_agent at jsw.gen.nz  Fri Mar  8 11:16:20 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Sat, 09 Mar 2019 00:16:20 +1300
Subject: [mythtv-users] CTRL-ALT-BACKSPACE
In-Reply-To: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
Message-ID: <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>

On Thu, 7 Mar 2019 22:45:16 -0800, you wrote:

>I upgraded from Mythbuntu8 to mythbuntu18. X just froze and we used to use
>CTRL-ALT-BS but I know it has been removed.
>
>I have been Googling this and found that this was replaced by
>AysRq-rightAlt-K but that doesn't work. Then I found a nice gui checkbox
>that restored it but that isn't there.  I found several different files I
>could create, all different, and the instructions below that look like they
>might work but I don't want to blow up the system so can someone tell me if
>this is correct for Mythbuntu 18? (I modified it slightly to use nano).
>Basically I found almost a dozen ways to enable this in xfce but they were
>all different.  In the past very bad things happened when I just followed
>online instructions.  That is why I am asking for help
>
>Thanks,
>
>Allen
>
>Enable the key combination Ctrl+Alt+Backspace
>
>   1.
>
>   Open the Terminal and run sudo nano /etc/default/keyboard
>   2.
>
>   Find the line:
>   XKBOPTIONS=""
>   3.
>
>   Replace it with:
>   XKBOPTIONS="terminate:ctrl_alt_bksp"
>   4.
>
>   Save the modified file and close it.
>   5.
>
>   Reboot your computer to take affect.

If you are using lightdm (as I do with Xubuntu 18), then log in from a
terminal (Alt-F1) or ssh and do "sudo systemctl restart lightdm" to
restart X.  That works pretty well for me, so I did not investigate
any further the various keystroke options.

From jam at tigger.ws  Fri Mar  8 11:41:23 2019
From: jam at tigger.ws (jam at tigger.ws)
Date: Fri, 8 Mar 2019 19:41:23 +0800
Subject: [mythtv-users] mac osx
Message-ID: <BFE36B8F-DAD0-4258-BDE2-BB792471260E@tigger.ws>

OT but relevant in a round about way
Craig your post references

<quote>
For the last 4-5 weeks, I've been back to plugging away at MythTV 29.x on macOS. Starting with MoisiePants pull request, I got the code to build successfully. So I resurrected my Parallels VM's for testing. Unfortunately, mythfrontend would crash hard at launch each and every time. I thought it might be a bug in the Parallels virtual environment (or just that it gets an odd-size screen). So I borrowed my wife's little-used MacBook Pro (late 2011). After a few small adventures setting up the build environment, it built successfully there too. mythfrontend did not _crash_ on launch--but only the top-left quarter of the screen was being properly displayed.
</quote>

Reading between the lines I opine you are running linux on yout mac

    So I resurrected my Parallels VM's for testing

Parallels are anal about the license fine print: They would not let you install a osx VM on non apple hardware

    So I borrowed my wife's little-used MacBook Pro 

implies that your native machine is not OSX. If true then 

Is a parallels VM a good build environment.
If not what is your build environment.
Are gdb or whatever-their-debugger?s-called not enough to exactly pinpoint the error(s)?
What do you do about heat? I find apple?s sleeping unused cores much cooler than linux?s throttling them.

Thanks
James

From darylangela at gmail.com  Fri Mar  8 12:10:20 2019
From: darylangela at gmail.com (Daryl McDonald)
Date: Fri, 8 Mar 2019 07:10:20 -0500
Subject: [mythtv-users] mail stopped
In-Reply-To: <8BA1DC7C-40AE-4F76-894C-CA135DD7A9A0@tigger.ws>
References: <mailman.39.1552021626.1604.mythtv-users@mythtv.org>
 <8BA1DC7C-40AE-4F76-894C-CA135DD7A9A0@tigger.ws>
Message-ID: <CAMwtTBDnN+=N8q-GE9JW+0FgW9S6xKO1t5e55Pay5kuDdK4oCg@mail.gmail.com>

Or nothing

On Fri, Mar 8, 2019, 12:23 AM James Linder <jam at tigger.ws> wrote:

> Thanks
> I received the first digest in a week
> Thanks
> James
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190308/7202512f/attachment.html>

From jharbestonus at gmail.com  Fri Mar  8 13:34:07 2019
From: jharbestonus at gmail.com (Jay Harbeston (ISeePeople))
Date: Fri, 8 Mar 2019 08:34:07 -0500
Subject: [mythtv-users] Mac osx
Message-ID: <EE8C6838-A887-476B-9D0E-381DEA180D79@gmail.com>

Starting a new thread as the original thread got hosed by the mail stopped thread causing them to be threaded together:



<quote>
For the last 4-5 weeks, I've been back to plugging away at MythTV 29.x on macOS. Starting with MoisiePants pull request, I got the code to build successfully. So I resurrected my Parallels VM's for testing. Unfortunately, mythfrontend would crash hard at launch each and every time. I thought it might be a bug in the Parallels virtual environment (or just that it gets an odd-size screen). So I borrowed my wife's little-used MacBook Pro (late 2011). After a few small adventures setting up the build environment, it built successfully there too. mythfrontend did not _crash_ on launch--but only the top-left quarter of the screen was being properly displayed.
</quote>

I am using (v30-Pre) on my iMac machine. When I do ?version, I get the following:

./MythFrontend --version
Please attach all output as a file in bug reports.
MythTV Version : v30-Pre
MythTV Branch : 
Network Protocol : 91
Library API : 30.20170212-1
QT Version : 5.5.1
Options compiled in:
 profile using_corevideo using_backend using_bindings_php using_darwin using_firewire using_frontend using_hdhomerun using_vbox using_ceton using_libdns_sd using_mheg using_opengl using_opengl_video using_opengl_themepainter using_qtwebkit using_qtscript using_qtdbus using_taglib using_profiletype using_appleremote using_bindings_php using_freetype2 using_mythtranscode using_opengl using_ffmpeg_threads using_mheg using_libmp3lame

This version works OK with my v29 backend, though it is only on infrequently and doesn?t get a ?soaking? test.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190308/4c1321a6/attachment.html>

From ctreleaven at cogeco.ca  Fri Mar  8 13:47:20 2019
From: ctreleaven at cogeco.ca (Craig Treleaven)
Date: Fri, 8 Mar 2019 08:47:20 -0500
Subject: [mythtv-users] mac osx
In-Reply-To: <BFE36B8F-DAD0-4258-BDE2-BB792471260E@tigger.ws>
References: <BFE36B8F-DAD0-4258-BDE2-BB792471260E@tigger.ws>
Message-ID: <B373A141-B811-4F64-B7CE-8A270A95A119@cogeco.ca>

> On Mar 8, 2019, at 6:41 AM, jam at tigger.ws wrote:
> 
> OT but relevant in a round about way
> Craig your post references
> 
> <quote>
> For the last 4-5 weeks, I've been back to plugging away at MythTV 29.x on macOS. Starting with MoisiePants pull request, I got the code to build successfully. So I resurrected my Parallels VM's for testing. Unfortunately, mythfrontend would crash hard at launch each and every time. I thought it might be a bug in the Parallels virtual environment (or just that it gets an odd-size screen). So I borrowed my wife's little-used MacBook Pro (late 2011). After a few small adventures setting up the build environment, it built successfully there too. mythfrontend did not _crash_ on launch--but only the top-left quarter of the screen was being properly displayed.
> </quote>
> 
> Reading between the lines I opine you are running linux on yout mac
> 

No.  The host and guest are both MacOS but different versions.  I started this when I wanted to build the all-in-one installer on an older OS version but test installation on a new version.

Craig

From ctreleaven at cogeco.ca  Fri Mar  8 14:01:18 2019
From: ctreleaven at cogeco.ca (Craig Treleaven)
Date: Fri, 8 Mar 2019 09:01:18 -0500
Subject: [mythtv-users] Mac osx
In-Reply-To: <EE8C6838-A887-476B-9D0E-381DEA180D79@gmail.com>
References: <EE8C6838-A887-476B-9D0E-381DEA180D79@gmail.com>
Message-ID: <AD074E36-840A-4D13-9084-EC282D021571@cogeco.ca>

> On Mar 8, 2019, at 8:34 AM, Jay Harbeston (ISeePeople) <jharbestonus at gmail.com> wrote:
> 
> Starting a new thread as the original thread got hosed by the mail stopped thread causing them to be threaded together:
> 
> 
> 
> <quote>
> For the last 4-5 weeks, I've been back to plugging away at MythTV 29.x on macOS. Starting with MoisiePants pull request, I got the code to build successfully. So I resurrected my Parallels VM's for testing. Unfortunately, mythfrontend would crash hard at launch each and every time. I thought it might be a bug in the Parallels virtual environment (or just that it gets an odd-size screen). So I borrowed my wife's little-used MacBook Pro (late 2011). After a few small adventures setting up the build environment, it built successfully there too. mythfrontend did not _crash_ on launch--but only the top-left quarter of the screen was being properly displayed.
> </quote>
> 
> I am using (v30-Pre) on my iMac machine. When I do ?version, I get the following:
> 
> ./MythFrontend --version
> Please attach all output as a file in bug reports.
> MythTV Version : v30-Pre
> MythTV Branch : 
> Network Protocol : 91
> Library API : 30.20170212-1
> QT Version : 5.5.1
> Options compiled in:
>  profile using_corevideo using_backend using_bindings_php using_darwin using_firewire using_frontend using_hdhomerun using_vbox using_ceton using_libdns_sd using_mheg using_opengl using_opengl_video using_opengl_themepainter using_qtwebkit using_qtscript using_qtdbus using_taglib using_profiletype using_appleremote using_bindings_php using_freetype2 using_mythtranscode using_opengl using_ffmpeg_threads using_mheg using_libmp3lame
> 
> This version works OK with my v29 backend, though it is only on infrequently and doesn?t get a ?soaking? test.

That is a now-elderly version of Qt.  Which version of MacOS are you running?

I know that others have gotten working versions of Myth v29 on OS X but it isn?t a slam dunk.  As my forum post says, different Qt versions ONLY work on certain MacOS versions.  Recent MacOS versions must use recent Qt releases.  In my testing, those combinations failed in a number of ways.  I am unwilling to package Myth v29 through MacPorts with those kinds of limitations.  That would inevitably lead to more support demands than I?m able?or even willing?to provide.

Craig
The MacPorts Guy


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190308/53648a79/attachment.html>

From jharbestonus at gmail.com  Fri Mar  8 14:08:33 2019
From: jharbestonus at gmail.com (Jay Harbeston)
Date: Fri, 8 Mar 2019 09:08:33 -0500
Subject: [mythtv-users] Mac osx
In-Reply-To: <AD074E36-840A-4D13-9084-EC282D021571@cogeco.ca>
References: <EE8C6838-A887-476B-9D0E-381DEA180D79@gmail.com>
 <AD074E36-840A-4D13-9084-EC282D021571@cogeco.ca>
Message-ID: <4137CA2A-EC02-47FC-A34A-A4AFF9182DD7@gmail.com>



> On Mar 8, 2019, at 9:01 AM, Craig Treleaven <ctreleaven at cogeco.ca> wrote:
> 
>> On Mar 8, 2019, at 8:34 AM, Jay Harbeston (ISeePeople) <jharbestonus at gmail.com <mailto:jharbestonus at gmail.com>> wrote:
>> 
>> Starting a new thread as the original thread got hosed by the mail stopped thread causing them to be threaded together:
>> 
>> 
>> 
>> <quote>
>> For the last 4-5 weeks, I've been back to plugging away at MythTV 29.x on macOS. Starting with MoisiePants pull request, I got the code to build successfully. So I resurrected my Parallels VM's for testing. Unfortunately, mythfrontend would crash hard at launch each and every time. I thought it might be a bug in the Parallels virtual environment (or just that it gets an odd-size screen). So I borrowed my wife's little-used MacBook Pro (late 2011). After a few small adventures setting up the build environment, it built successfully there too. mythfrontend did not _crash_ on launch--but only the top-left quarter of the screen was being properly displayed.
>> </quote>
>> 
>> I am using (v30-Pre) on my iMac machine. When I do ?version, I get the following:
>> 
>> ./MythFrontend --version
>> Please attach all output as a file in bug reports.
>> MythTV Version : v30-Pre
>> MythTV Branch : 
>> Network Protocol : 91
>> Library API : 30.20170212-1
>> QT Version : 5.5.1
>> Options compiled in:
>>  profile using_corevideo using_backend using_bindings_php using_darwin using_firewire using_frontend using_hdhomerun using_vbox using_ceton using_libdns_sd using_mheg using_opengl using_opengl_video using_opengl_themepainter using_qtwebkit using_qtscript using_qtdbus using_taglib using_profiletype using_appleremote using_bindings_php using_freetype2 using_mythtranscode using_opengl using_ffmpeg_threads using_mheg using_libmp3lame
>> 
>> This version works OK with my v29 backend, though it is only on infrequently and doesn?t get a ?soaking? test.
> 
> That is a now-elderly version of Qt.  Which version of MacOS are you running?
> 
> I know that others have gotten working versions of Myth v29 on OS X but it isn?t a slam dunk.  As my forum post says, different Qt versions ONLY work on certain MacOS versions.  Recent MacOS versions must use recent Qt releases.  In my testing, those combinations failed in a number of ways.  I am unwilling to package Myth v29 through MacPorts with those kinds of limitations.  That would inevitably lead to more support demands than I?m able?or even willing?to provide.
> 



I have a mid 2011 27 inch iMac running High Sierra.

Regards.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190308/22debdfc/attachment.html>

From allen.p.edwards at gmail.com  Fri Mar  8 15:17:37 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Fri, 8 Mar 2019 07:17:37 -0800
Subject: [mythtv-users] CTRL-ALT-BACKSPACE
In-Reply-To: <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
Message-ID: <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>

On Fri, Mar 8, 2019 at 3:16 AM Stephen Worthington <stephen_agent at jsw.gen.nz>
wrote:

> On Thu, 7 Mar 2019 22:45:16 -0800, you wrote:
>
> >I upgraded from Mythbuntu8 to mythbuntu18. X just froze and we used to use
> >CTRL-ALT-BS but I know it has been removed.
> >
> >I have been Googling this and found that this was replaced by
> >AysRq-rightAlt-K but that doesn't work. Then I found a nice gui checkbox
> >that restored it but that isn't there.  I found several different files I
> >could create, all different, and the instructions below that look like
> they
> >might work but I don't want to blow up the system so can someone tell me
> if
> >this is correct for Mythbuntu 18? (I modified it slightly to use nano).
> >Basically I found almost a dozen ways to enable this in xfce but they were
> >all different.  In the past very bad things happened when I just followed
> >online instructions.  That is why I am asking for help
> >
> >Thanks,
> >
> >Allen
> >
> >Enable the key combination Ctrl+Alt+Backspace
> >
> >   1.
> >
> >   Open the Terminal and run sudo nano /etc/default/keyboard
> >   2.
> >
> >   Find the line:
> >   XKBOPTIONS=""
> >   3.
> >
> >   Replace it with:
> >   XKBOPTIONS="terminate:ctrl_alt_bksp"
> >   4.
> >
> >   Save the modified file and close it.
> >   5.
> >
> >   Reboot your computer to take affect.
>
> If you are using lightdm (as I do with Xubuntu 18), then log in from a
> terminal (Alt-F1) or ssh and do "sudo systemctl restart lightdm" to
> restart X.  That works pretty well for me, so I did not investigate
> any further the various keystroke options.
>
> Thank you for the suggestion but it doesn't solve the problem.

While the lightdm command worked on a test this morning, the system was not
hung up so not sure if it would have worked last night.

The issue last night was that Myth was frozen and the cursor was off.  In
spite of no cursor, I was able to open system logoff command and click
Logoff but Myth would not close and prevented X from closing.  The logoff
attempt was met with a message "Myth is not responding do you want force a
close, Y/N" or something like that but it did not respond to a "Y" from the
keyboard so I was unable to logoff and had to use the power button.  The
power button did not fully turn off the computer and I had to do a long
press to force the computer to shut off.  Basically a hot mess. With
Mythbuntu-8 this would happen one or two times a year and the simple key
sequence would restart X and all was good.  My wife could do it without
calling me down to issue some system commands.

Even if that worked, CTRL-ALT-Backspace is a lot easier to use.  By the
way, Alt-F1 does not bring up a terminal window on my system for some
reason.

What I need is something like CTRL-ALT-Backspace, or the SysRq-Alt-K (which
did not work) so that my wife can restart X.  While I appreciate knowing
about the systemctl command, it is not "wife friendly" at least in the case
of my wife. The power button would be an option but it interrupts
recordings and even it didn't really work last night,  I needed the long
press.

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190308/3de52b5d/attachment.html>

From allen.p.edwards at gmail.com  Fri Mar  8 15:32:10 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Fri, 8 Mar 2019 07:32:10 -0800
Subject: [mythtv-users] CTRL-ALT-BACKSPACE
In-Reply-To: <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
Message-ID: <CAH8UtKMzjNrAe6HaT_xTT8bN01JBNddv9uHorUpa_TA4Je7sWA@mail.gmail.com>

On Fri, Mar 8, 2019 at 7:17 AM Allen Edwards <allen.p.edwards at gmail.com>
wrote:

>
>
> On Fri, Mar 8, 2019 at 3:16 AM Stephen Worthington <
> stephen_agent at jsw.gen.nz> wrote:
>
>> On Thu, 7 Mar 2019 22:45:16 -0800, you wrote:
>>
>> >I upgraded from Mythbuntu8 to mythbuntu18. X just froze and we used to
>> use
>> >CTRL-ALT-BS but I know it has been removed.
>> >
>> >I have been Googling this and found that this was replaced by
>> >AysRq-rightAlt-K but that doesn't work. Then I found a nice gui checkbox
>> >that restored it but that isn't there.  I found several different files I
>> >could create, all different, and the instructions below that look like
>> they
>> >might work but I don't want to blow up the system so can someone tell me
>> if
>> >this is correct for Mythbuntu 18? (I modified it slightly to use nano).
>> >Basically I found almost a dozen ways to enable this in xfce but they
>> were
>> >all different.  In the past very bad things happened when I just followed
>> >online instructions.  That is why I am asking for help
>> >
>> >Thanks,
>> >
>> >Allen
>> >
>> >Enable the key combination Ctrl+Alt+Backspace
>> >
>> >   1.
>> >
>> >   Open the Terminal and run sudo nano /etc/default/keyboard
>> >   2.
>> >
>> >   Find the line:
>> >   XKBOPTIONS=""
>> >   3.
>> >
>> >   Replace it with:
>> >   XKBOPTIONS="terminate:ctrl_alt_bksp"
>> >   4.
>> >
>> >   Save the modified file and close it.
>> >   5.
>> >
>> >   Reboot your computer to take affect.
>>
>> If you are using lightdm (as I do with Xubuntu 18), then log in from a
>> terminal (Alt-F1) or ssh and do "sudo systemctl restart lightdm" to
>> restart X.  That works pretty well for me, so I did not investigate
>> any further the various keystroke options.
>>
>> Thank you for the suggestion but it doesn't solve the problem.
>
> While the lightdm command worked on a test this morning, the system was
> not hung up so not sure if it would have worked last night.
>
> The issue last night was that Myth was frozen and the cursor was off.  In
> spite of no cursor, I was able to open system logoff command and click
> Logoff but Myth would not close and prevented X from closing.  The logoff
> attempt was met with a message "Myth is not responding do you want force a
> close, Y/N" or something like that but it did not respond to a "Y" from the
> keyboard so I was unable to logoff and had to use the power button.  The
> power button did not fully turn off the computer and I had to do a long
> press to force the computer to shut off.  Basically a hot mess. With
> Mythbuntu-8 this would happen one or two times a year and the simple key
> sequence would restart X and all was good.  My wife could do it without
> calling me down to issue some system commands.
>
> Even if that worked, CTRL-ALT-Backspace is a lot easier to use.  By the
> way, Alt-F1 does not bring up a terminal window on my system for some
> reason.
>
> What I need is something like CTRL-ALT-Backspace, or the SysRq-Alt-K
> (which did not work) so that my wife can restart X.  While I appreciate
> knowing about the systemctl command, it is not "wife friendly" at least in
> the case of my wife. The power button would be an option but it interrupts
> recordings and even it didn't really work last night,  I needed the long
> press.
>
> Allen
>

PS.  My wife reports that after my test she started watching her morning
show and after 4 minutes another instance of MythFrontend came on the
screen so she saw the myth menus.  She clicked on her show again and now
she had two instances of the show playing so they were talking over each
other.  I closed Myth in the normal way but there was a message that I had
not seen before about did I want to close myth showing up on the second
screen.  Very strange.  Not sure if that was left over from last night,
from the systemctl test, or if my computer is failing and this is another
symptom. I did accidently flip the wrong circuit breaker that shut it down
yesterday morning but it worked fine last night until it froze and it
worked fine after the restart last night as well.

 Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190308/7cc1c7ef/attachment.html>

From mkbloke at gmail.com  Fri Mar  8 15:41:24 2019
From: mkbloke at gmail.com (Ian Cameron)
Date: Fri, 8 Mar 2019 15:41:24 +0000
Subject: [mythtv-users] CTRL-ALT-BACKSPACE
In-Reply-To: <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
Message-ID: <CAC+xXWOG_yErT_YgwE472vBiYjFzMvt1SR3ZZvJm4swKmaG=QQ@mail.gmail.com>

It would appear, as far as I can see, that the information you have found
is correct for Ubuntu like systems.  The worst that is likely to happen is
that you try it and it doesn't work, in which case you can just edit
/etc/default/keyboard again and put it back to how it was, i.e. with
XKBOPTIONS="".

The other xorg config option that can affect this is the DontZap option,
which will cause it to ignore the terminate signal, but on my 16.04 LTS
installation this does not appear to have been used, so I suspect it won't
be in your xorg.conf file(s) either, unless you have added it yourself.

Cheers, Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190308/17d53a21/attachment.html>

From allen.p.edwards at gmail.com  Fri Mar  8 16:09:24 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Fri, 8 Mar 2019 08:09:24 -0800
Subject: [mythtv-users] CTRL-ALT-BACKSPACE
In-Reply-To: <CAC+xXWOG_yErT_YgwE472vBiYjFzMvt1SR3ZZvJm4swKmaG=QQ@mail.gmail.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
 <CAC+xXWOG_yErT_YgwE472vBiYjFzMvt1SR3ZZvJm4swKmaG=QQ@mail.gmail.com>
Message-ID: <CAH8UtKMA-65vJgC5MezGoU9GkVhtzvXxc2PxUyqezhh5fEg_WQ@mail.gmail.com>

On Fri, Mar 8, 2019 at 7:41 AM Ian Cameron <mkbloke at gmail.com> wrote:

> It would appear, as far as I can see, that the information you have found
> is correct for Ubuntu like systems.  The worst that is likely to happen is
> that you try it and it doesn't work, in which case you can just edit
> /etc/default/keyboard again and put it back to how it was, i.e. with
> XKBOPTIONS="".
>
> The other xorg config option that can affect this is the DontZap option,
> which will cause it to ignore the terminate signal, but on my 16.04 LTS
> installation this does not appear to have been used, so I suspect it won't
> be in your xorg.conf file(s) either, unless you have added it yourself.
>
> Cheers, Ian
>

That is reassuring Ian, thank you.  But I sure hope someone has done this
and can tell me if it works for sure.  I have been Googling this and there
are so many opinions such as the DontZap fixes listed followed by other
ways of doing this none of which seem to be on my system.  There is one
that suggests adding setxkbmap -option terminate:ctrl_alt_bksp through the
Applications Autostart of the gui. But the poster said it should just be a
checkbox and it wasn't so I am not inclined to add it manually without
confirmation from someone here.

I got some auto-upload of some error log and then a Chrome window opened
asking me to login to an account I don't have after trying the other
suggestion this morning. Or maybe it was unrelated and a result of some
other problem. But this is the reason I really hate trying things. I have
destroyed half a day on occasion trying something I found on the web or
suggestions that are not for my exact configuration.

If I don't get a reply from someone who has enabled CTRL-Alt-Backspace with
a Mythbuntu-18 system I will try what I posted as you are suggesting.

Why they decided to delete this functionality is beyond stupid.

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190308/63a86d03/attachment-0001.html>

From oliver.greg at gmail.com  Fri Mar  8 16:25:15 2019
From: oliver.greg at gmail.com (Greg Oliver)
Date: Fri, 8 Mar 2019 10:25:15 -0600
Subject: [mythtv-users] CTRL-ALT-BACKSPACE
In-Reply-To: <CAH8UtKMA-65vJgC5MezGoU9GkVhtzvXxc2PxUyqezhh5fEg_WQ@mail.gmail.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
 <CAC+xXWOG_yErT_YgwE472vBiYjFzMvt1SR3ZZvJm4swKmaG=QQ@mail.gmail.com>
 <CAH8UtKMA-65vJgC5MezGoU9GkVhtzvXxc2PxUyqezhh5fEg_WQ@mail.gmail.com>
Message-ID: <CAF4tN+9YAv-JumMCn2ohJg0D+-WbWgg3YTJf1FyPw_odoh_vwA@mail.gmail.com>

On Fri, Mar 8, 2019 at 10:11 AM Allen Edwards <allen.p.edwards at gmail.com>
wrote:

> On Fri, Mar 8, 2019 at 7:41 AM Ian Cameron <mkbloke at gmail.com> wrote:
>
>> It would appear, as far as I can see, that the information you have found
>> is correct for Ubuntu like systems.  The worst that is likely to happen is
>> that you try it and it doesn't work, in which case you can just edit
>> /etc/default/keyboard again and put it back to how it was, i.e. with
>> XKBOPTIONS="".
>>
>> The other xorg config option that can affect this is the DontZap option,
>> which will cause it to ignore the terminate signal, but on my 16.04 LTS
>> installation this does not appear to have been used, so I suspect it won't
>> be in your xorg.conf file(s) either, unless you have added it yourself.
>>
>> Cheers, Ian
>>
>
> That is reassuring Ian, thank you.  But I sure hope someone has done this
> and can tell me if it works for sure.  I have been Googling this and there
> are so many opinions such as the DontZap fixes listed followed by other
> ways of doing this none of which seem to be on my system.  There is one
> that suggests adding setxkbmap -option terminate:ctrl_alt_bksp through the
> Applications Autostart of the gui. But the poster said it should just be a
> checkbox and it wasn't so I am not inclined to add it manually without
> confirmation from someone here.
>
> I got some auto-upload of some error log and then a Chrome window opened
> asking me to login to an account I don't have after trying the other
> suggestion this morning. Or maybe it was unrelated and a result of some
> other problem. But this is the reason I really hate trying things. I have
> destroyed half a day on occasion trying something I found on the web or
> suggestions that are not for my exact configuration.
>
> If I don't get a reply from someone who has enabled CTRL-Alt-Backspace
> with a Mythbuntu-18 system I will try what I posted as you are suggesting.
>
> Why they decided to delete this functionality is beyond stupid.
>
> Allen
>
>
While in an X or Wayland environment, pressing CTRL+ALF+Fn4 should get you
out of X and into a console in terminal Fx.  I am unsure since BACKSPACE
does not work if it will though - still worth a try.

-Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190308/926912bf/attachment.html>

From stephen_agent at jsw.gen.nz  Fri Mar  8 16:53:54 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Sat, 09 Mar 2019 05:53:54 +1300
Subject: [mythtv-users] CTRL-ALT-BACKSPACE
In-Reply-To: <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
Message-ID: <mc458eppr7ac2mn6aqfeuefvn19ku9r1kd@4ax.com>

On Fri, 8 Mar 2019 07:17:37 -0800, you wrote:

>On Fri, Mar 8, 2019 at 3:16 AM Stephen Worthington <stephen_agent at jsw.gen.nz>
>wrote:
>
>> On Thu, 7 Mar 2019 22:45:16 -0800, you wrote:
>>
>> >I upgraded from Mythbuntu8 to mythbuntu18. X just froze and we used to use
>> >CTRL-ALT-BS but I know it has been removed.
>> >
>> >I have been Googling this and found that this was replaced by
>> >AysRq-rightAlt-K but that doesn't work. Then I found a nice gui checkbox
>> >that restored it but that isn't there.  I found several different files I
>> >could create, all different, and the instructions below that look like
>> they
>> >might work but I don't want to blow up the system so can someone tell me
>> if
>> >this is correct for Mythbuntu 18? (I modified it slightly to use nano).
>> >Basically I found almost a dozen ways to enable this in xfce but they were
>> >all different.  In the past very bad things happened when I just followed
>> >online instructions.  That is why I am asking for help
>> >
>> >Thanks,
>> >
>> >Allen
>> >
>> >Enable the key combination Ctrl+Alt+Backspace
>> >
>> >   1.
>> >
>> >   Open the Terminal and run sudo nano /etc/default/keyboard
>> >   2.
>> >
>> >   Find the line:
>> >   XKBOPTIONS=""
>> >   3.
>> >
>> >   Replace it with:
>> >   XKBOPTIONS="terminate:ctrl_alt_bksp"
>> >   4.
>> >
>> >   Save the modified file and close it.
>> >   5.
>> >
>> >   Reboot your computer to take affect.
>>
>> If you are using lightdm (as I do with Xubuntu 18), then log in from a
>> terminal (Alt-F1) or ssh and do "sudo systemctl restart lightdm" to
>> restart X.  That works pretty well for me, so I did not investigate
>> any further the various keystroke options.
>>
>> Thank you for the suggestion but it doesn't solve the problem.
>
>While the lightdm command worked on a test this morning, the system was not
>hung up so not sure if it would have worked last night.
>
>The issue last night was that Myth was frozen and the cursor was off.  In
>spite of no cursor, I was able to open system logoff command and click
>Logoff but Myth would not close and prevented X from closing.  The logoff
>attempt was met with a message "Myth is not responding do you want force a
>close, Y/N" or something like that but it did not respond to a "Y" from the
>keyboard so I was unable to logoff and had to use the power button.  The
>power button did not fully turn off the computer and I had to do a long
>press to force the computer to shut off.  Basically a hot mess. With
>Mythbuntu-8 this would happen one or two times a year and the simple key
>sequence would restart X and all was good.  My wife could do it without
>calling me down to issue some system commands.

That sounds like just a mythfrontend lockup, rather than X locking up
completely.  If you already have a window running a terminal in the
background when it happens, you should be able to just do Alt-Tab as
many times as necessary to get to that terminal.  Then from there do:

ps -e | grep mythfrontend

to find the PID for mythfrontend (or mythfrontend.real if it is
Ubuntu).  Then kill that process:

sudo kill <pid>

You usually need to do that command twice to actually kill
mythfrontend.  Or if mythfrontend is completely locked up, then you
may need to use:

sudo kill -9 <pid>

If you are running the XFCE desktop (Xubuntu), then you should also be
able to do Ctrl-Esc to bring up a menu where you can run a terminal
window from, or Ctrl-Alt-T to open a terminal window.  Or you can use
Ctrl-Alt-F1 to open a terminal directly in full screen mode.

WARNING: After a bad shutdown like using the power off button or after
a power failure, you need to check all your filesystems on all
partitions - there is a reasonable chance that any filesystem that had
a write in progress at the time of the shutdown will be corrupt
somewhere.  The fsck checks done automatically at boot time will
likely not find and fix such corruption.  You must a full "fsck -C -f
/dev/<partition id>" on all partitions that were mounted at the time,
and then that should fix any errors.  If you see any errors that
needed fixing, then run the command again on that partition as many
times as necessary until it runs without any errors to be fixed.
Failing to do this allows the corruption of the filesystem to remain
in place, and if any writes take place to corrupt files or corrupt
filesystem tables, then the corruption will likely spread and make the
partition unusable and unfixable - you can lose your entire system.

You can do fsck repairs like this by booting from a live DVD or live
USB, or from another bootable partition that has the same or later
version of the filesystem drivers and fsck programs.  I do this by
having a second bootable partition on my SSD, which has a script to do
all the fsck commands.  Booting from the normal boot partition in
repair mode is not able to do an fsck on the boot partition itself,
but can be used once the boot partition has been fixed to run fsck on
all the other partitions.

After you have clean filesystems, you then need to do a full check and
repair on the mythconverg database.  If it was being written to at the
time of the bad shutdown, any tables that were being modified at the
time may be crashed.  If a recording was in progress, typically the
recordedseek table will be crashed.  Unfortunately, when mythbackend
tries to record and it then writes to recordedseek, if the table is
crashed, all you get is some error messages in the mythbackend.log
file.  It appears that mythbackend is recording happily, when all the
time the writes to recordedseek are failing.  This does not stop a
recording from succeeding, but on playback there will be problems.  It
is possible to fix recordedseek, then use the "mythcommflag --rebuild"
command to add the correct recordedseek table entries for a recording
where this happens, but it is much better to fix the database before
that.  And if any table other than recordedseek is crashed, the
consequences are usually worse - if you write to other crashed tables,
you can corrupt the table completely to where it is unrepairable, and
that can mean you lose the entire database.  Fortunately, crashes of
other tables are rare.  To check and repair the database, run the
optimize_mythdb script.  It is here in Ubuntu:

/usr/share/doc/mythtv-backend/contrib/maintenance/optimize_mythdb.pl

That script should also be being run from /etc/cron.daily to prevent
any problems with database corruption.  Database corruption does
happen occasionally due to minor software bugs, and unless you are
running optimize_mythdb regularly to fix that corruption, it can and
usually will spread and eat your database.

>Even if that worked, CTRL-ALT-Backspace is a lot easier to use.  By the
>way, Alt-F1 does not bring up a terminal window on my system for some
>reason.

Sorry, I mis-typed that.  It is Ctrl-Alt-F1 for a terminal.

>What I need is something like CTRL-ALT-Backspace, or the SysRq-Alt-K (which
>did not work) so that my wife can restart X.  While I appreciate knowing
>about the systemctl command, it is not "wife friendly" at least in the case
>of my wife. The power button would be an option but it interrupts
>recordings and even it didn't really work last night,  I needed the long
>press.

The power button is not a good option at all, due to the possible loss
of files, whole partitions, the database, or the entire system.  It
should only be used as a last resort, and must be followed by the full
check and fix procedure as above.

>Allen

From allen.p.edwards at gmail.com  Fri Mar  8 17:36:34 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Fri, 8 Mar 2019 09:36:34 -0800
Subject: [mythtv-users] CTRL-ALT-BACKSPACE
In-Reply-To: <mc458eppr7ac2mn6aqfeuefvn19ku9r1kd@4ax.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
 <mc458eppr7ac2mn6aqfeuefvn19ku9r1kd@4ax.com>
Message-ID: <CAH8UtKN64enW_46mYe-v84CzWex5Rf0Ze88yqVmMGM9J4yoVVg@mail.gmail.com>

On Fri, Mar 8, 2019 at 8:54 AM Stephen Worthington <stephen_agent at jsw.gen.nz>
wrote:

> On Fri, 8 Mar 2019 07:17:37 -0800, you wrote:
>
> >On Fri, Mar 8, 2019 at 3:16 AM Stephen Worthington <
> stephen_agent at jsw.gen.nz>
> >wrote:
> >
> >> On Thu, 7 Mar 2019 22:45:16 -0800, you wrote:
> >>
> >> >I upgraded from Mythbuntu8 to mythbuntu18. X just froze and we used to
> use
> >> >CTRL-ALT-BS but I know it has been removed.
> >> >
> >> >I have been Googling this and found that this was replaced by
> >> >AysRq-rightAlt-K but that doesn't work. Then I found a nice gui
> checkbox
> >> >that restored it but that isn't there.  I found several different
> files I
> >> >could create, all different, and the instructions below that look like
> >> they
> >> >might work but I don't want to blow up the system so can someone tell
> me
> >> if
> >> >this is correct for Mythbuntu 18? (I modified it slightly to use nano).
> >> >Basically I found almost a dozen ways to enable this in xfce but they
> were
> >> >all different.  In the past very bad things happened when I just
> followed
> >> >online instructions.  That is why I am asking for help
> >> >
> >> >Thanks,
> >> >
> >> >Allen
> >> >
> >> >Enable the key combination Ctrl+Alt+Backspace
> >> >
> >> >   1.
> >> >
> >> >   Open the Terminal and run sudo nano /etc/default/keyboard
> >> >   2.
> >> >
> >> >   Find the line:
> >> >   XKBOPTIONS=""
> >> >   3.
> >> >
> >> >   Replace it with:
> >> >   XKBOPTIONS="terminate:ctrl_alt_bksp"
> >> >   4.
> >> >
> >> >   Save the modified file and close it.
> >> >   5.
> >> >
> >> >   Reboot your computer to take affect.
> >>
> >> If you are using lightdm (as I do with Xubuntu 18), then log in from a
> >> terminal (Alt-F1) or ssh and do "sudo systemctl restart lightdm" to
> >> restart X.  That works pretty well for me, so I did not investigate
> >> any further the various keystroke options.
> >>
> >> Thank you for the suggestion but it doesn't solve the problem.
> >
> >While the lightdm command worked on a test this morning, the system was
> not
> >hung up so not sure if it would have worked last night.
> >
> >The issue last night was that Myth was frozen and the cursor was off.  In
> >spite of no cursor, I was able to open system logoff command and click
> >Logoff but Myth would not close and prevented X from closing.  The logoff
> >attempt was met with a message "Myth is not responding do you want force a
> >close, Y/N" or something like that but it did not respond to a "Y" from
> the
> >keyboard so I was unable to logoff and had to use the power button.  The
> >power button did not fully turn off the computer and I had to do a long
> >press to force the computer to shut off.  Basically a hot mess. With
> >Mythbuntu-8 this would happen one or two times a year and the simple key
> >sequence would restart X and all was good.  My wife could do it without
> >calling me down to issue some system commands.
>
> That sounds like just a mythfrontend lockup, rather than X locking up
> completely.  If you already have a window running a terminal in the
> background when it happens, you should be able to just do Alt-Tab as
> many times as necessary to get to that terminal.  Then from there do:
>
> ps -e | grep mythfrontend
>
> to find the PID for mythfrontend (or mythfrontend.real if it is
> Ubuntu).  Then kill that process:
>
> sudo kill <pid>
>
> You usually need to do that command twice to actually kill
> mythfrontend.  Or if mythfrontend is completely locked up, then you
> may need to use:
>
> sudo kill -9 <pid>
>
> If you are running the XFCE desktop (Xubuntu), then you should also be
> able to do Ctrl-Esc to bring up a menu where you can run a terminal
> window from, or Ctrl-Alt-T to open a terminal window.  Or you can use
> Ctrl-Alt-F1 to open a terminal directly in full screen mode.
>
> WARNING: After a bad shutdown like using the power off button or after
> a power failure, you need to check all your filesystems on all
> partitions - there is a reasonable chance that any filesystem that had
> a write in progress at the time of the shutdown will be corrupt
> somewhere.  The fsck checks done automatically at boot time will
> likely not find and fix such corruption.  You must a full "fsck -C -f
> /dev/<partition id>" on all partitions that were mounted at the time,
> and then that should fix any errors.  If you see any errors that
> needed fixing, then run the command again on that partition as many
> times as necessary until it runs without any errors to be fixed.
> Failing to do this allows the corruption of the filesystem to remain
> in place, and if any writes take place to corrupt files or corrupt
> filesystem tables, then the corruption will likely spread and make the
> partition unusable and unfixable - you can lose your entire system.
>
> You can do fsck repairs like this by booting from a live DVD or live
> USB, or from another bootable partition that has the same or later
> version of the filesystem drivers and fsck programs.  I do this by
> having a second bootable partition on my SSD, which has a script to do
> all the fsck commands.  Booting from the normal boot partition in
> repair mode is not able to do an fsck on the boot partition itself,
> but can be used once the boot partition has been fixed to run fsck on
> all the other partitions.
>
> After you have clean filesystems, you then need to do a full check and
> repair on the mythconverg database.  If it was being written to at the
> time of the bad shutdown, any tables that were being modified at the
> time may be crashed.  If a recording was in progress, typically the
> recordedseek table will be crashed.  Unfortunately, when mythbackend
> tries to record and it then writes to recordedseek, if the table is
> crashed, all you get is some error messages in the mythbackend.log
> file.  It appears that mythbackend is recording happily, when all the
> time the writes to recordedseek are failing.  This does not stop a
> recording from succeeding, but on playback there will be problems.  It
> is possible to fix recordedseek, then use the "mythcommflag --rebuild"
> command to add the correct recordedseek table entries for a recording
> where this happens, but it is much better to fix the database before
> that.  And if any table other than recordedseek is crashed, the
> consequences are usually worse - if you write to other crashed tables,
> you can corrupt the table completely to where it is unrepairable, and
> that can mean you lose the entire database.  Fortunately, crashes of
> other tables are rare.  To check and repair the database, run the
> optimize_mythdb script.  It is here in Ubuntu:
>
> /usr/share/doc/mythtv-backend/contrib/maintenance/optimize_mythdb.pl
>
> That script should also be being run from /etc/cron.daily to prevent
> any problems with database corruption.  Database corruption does
> happen occasionally due to minor software bugs, and unless you are
> running optimize_mythdb regularly to fix that corruption, it can and
> usually will spread and eat your database.
>
> >Even if that worked, CTRL-ALT-Backspace is a lot easier to use.  By the
> >way, Alt-F1 does not bring up a terminal window on my system for some
> >reason.
>
> Sorry, I mis-typed that.  It is Ctrl-Alt-F1 for a terminal.
>
> >What I need is something like CTRL-ALT-Backspace, or the SysRq-Alt-K
> (which
> >did not work) so that my wife can restart X.  While I appreciate knowing
> >about the systemctl command, it is not "wife friendly" at least in the
> case
> >of my wife. The power button would be an option but it interrupts
> >recordings and even it didn't really work last night,  I needed the long
> >press.
>
> The power button is not a good option at all, due to the possible loss
> of files, whole partitions, the database, or the entire system.  It
> should only be used as a last resort, and must be followed by the full
> check and fix procedure as above.
>
> >Allen


Funny (sort of).  If you read the reason that CTRL-ALT-Backspace was
removed it said that most users use the power button.  I believe the power
button is set to just close Linux in a  nice controlled way.  Pressing and
holding the button like I did last night is like a power off and I only did
that when I was positive the system was quiet and hung up.

That said, I did flip the breaker and that clearly did a power off. It was
a comedy of errors that caused this. I accidently put my stove into Self
Clean and I could not stop it so flipped the breaker for what I thought was
the stove but was actually the upstairs power distribution panel which also
feeds Myth to get it on the same power as the projector.  Anyway, now I am
concerned about my filesystem.

I have one drive, sdb1 so I am assuming that is what I need to check. Not
sure if I have a bootable DVD but I am sure I need to leave now so will try
and figure it out when I return.

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190308/ad285b96/attachment.html>

From barry3martin at gmail.com  Fri Mar  8 17:46:46 2019
From: barry3martin at gmail.com (Barry Martin)
Date: Fri, 8 Mar 2019 11:46:46 -0600
Subject: [mythtv-users] Can't get my projector to work with Myth - HDMI
 Switch
In-Reply-To: <mailman.39.1552021626.1604.mythtv-users@mythtv.org>
References: <mailman.39.1552021626.1604.mythtv-users@mythtv.org>
Message-ID: <0fa8418c-c2bf-fedb-5d40-90516bef594e@gmail.com>


Allen:
> It would be nice to have an HDMI switch so I don't have to switch the
> cables but that is the next step.

A couple things come to mind with my use of HDMI switches around here.? 
Main one is if using a Raspberry Pi the RPi sometimes doesn't see the 
final HDMI device (i.e. TV) fast enough and switches to its composite 
video output and stays there until rebooted.? There is a simple fix to 
the boot configuration file.

The switches won't work without a 5v (?) input, which is usually snagged 
from an HDMI input; you may need an external DC Input, so either another 
wall wart or a charging adapter with multiple 2A outputs.? (Thinking up 
here where I have an RPi and HDMI switch, both need power.)

My switches (so limited experience) will automatically switch to the 
last active device -- maybe better phrased 'latest activated input'.? If 
you power up your BluRay player the switch will automatically switch to 
that input, which isn't bad unless you're watching a different input.? 
That's happened once in over a year here.

I have found it handy to have an HDMI coupler for troubleshooting, that 
way can take out the switch, connect the two male ends of the cable 
together.? (I get mine from an out-of-country source at around 50? each.)

Barry


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190308/d0606773/attachment.html>

From allen.p.edwards at gmail.com  Fri Mar  8 18:16:28 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Fri, 8 Mar 2019 10:16:28 -0800
Subject: [mythtv-users] Can't get my projector to work with Myth - HDMI
 Switch
In-Reply-To: <0fa8418c-c2bf-fedb-5d40-90516bef594e@gmail.com>
References: <mailman.39.1552021626.1604.mythtv-users@mythtv.org>
 <0fa8418c-c2bf-fedb-5d40-90516bef594e@gmail.com>
Message-ID: <CAH8UtKP=WyHeb60rKdbMnCbV9y9wAvohVHx2qsQx1X90KCJipw@mail.gmail.com>

On Fri, Mar 8, 2019, 9:47 AM Barry Martin <barry3martin at gmail.com> wrote:

>
> Allen:
>
> It would be nice to have an HDMI switch so I don't have to switch the
> cables but that is the next step.
>
> A couple things come to mind with my use of HDMI switches around here.
> Main one is if using a Raspberry Pi the RPi sometimes doesn't see the final
> HDMI device (i.e. TV) fast enough and switches to its composite video
> output and stays there until rebooted.  There is a simple fix to the boot
> configuration file.
>
> The switches won't work without a 5v (?) input, which is usually snagged
> from an HDMI input; you may need an external DC Input, so either another
> wall wart or a charging adapter with multiple 2A outputs.  (Thinking up
> here where I have an RPi and HDMI switch, both need power.)
>
> My switches (so limited experience) will automatically switch to the last
> active device -- maybe better phrased 'latest activated input'.  If you
> power up your BluRay player the switch will automatically switch to that
> input, which isn't bad unless you're watching a different input.  That's
> happened once in over a year here.
>
> I have found it handy to have an HDMI coupler for troubleshooting, that
> way can take out the switch, connect the two male ends of the cable
> together.  (I get mine from an out-of-country source at around 50? each.)
>
> I need two outputs and one input and a switch not a splitter but the
Amazon reviews make me think they will not work with my 30 feet cable to
the projector.

>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190308/5bca7e49/attachment.html>

From jon.s.boehm at gmail.com  Fri Mar  8 19:35:24 2019
From: jon.s.boehm at gmail.com (Jon Boehm)
Date: Fri, 8 Mar 2019 11:35:24 -0800
Subject: [mythtv-users] Can't get my projector to work with Myth - HDMI
 Switch
In-Reply-To: <CAH8UtKP=WyHeb60rKdbMnCbV9y9wAvohVHx2qsQx1X90KCJipw@mail.gmail.com>
References: <mailman.39.1552021626.1604.mythtv-users@mythtv.org>
 <0fa8418c-c2bf-fedb-5d40-90516bef594e@gmail.com>
 <CAH8UtKP=WyHeb60rKdbMnCbV9y9wAvohVHx2qsQx1X90KCJipw@mail.gmail.com>
Message-ID: <CAL7eZUXsBR7jcBPRbo7-Kn+y5aatWcbJbWLaWNctPDKrxQ7rzQ@mail.gmail.com>

I have a monoprice HDMI splitter that I've been using for years with no
problem.   It takes the input from my receiver and sends the output to both
my TV and projector at the same time.  So far, not issue with my Nvidia
shield getting confused but when I used a Linux frontend I had to direct
connect the projector once and download the edid.bin file.  Then I had to
enter this into the xorg.conf like this

Option         "CustomEDID"   //MORE STUFF HERE

That's not a one line fix but is a start for googling more information.

Jon

On Fri, Mar 8, 2019 at 10:18 AM Allen Edwards <allen.p.edwards at gmail.com>
wrote:

>
>
> On Fri, Mar 8, 2019, 9:47 AM Barry Martin <barry3martin at gmail.com> wrote:
>
>>
>> Allen:
>>
>> It would be nice to have an HDMI switch so I don't have to switch the
>> cables but that is the next step.
>>
>> A couple things come to mind with my use of HDMI switches around here.
>> Main one is if using a Raspberry Pi the RPi sometimes doesn't see the final
>> HDMI device (i.e. TV) fast enough and switches to its composite video
>> output and stays there until rebooted.  There is a simple fix to the boot
>> configuration file.
>>
>> The switches won't work without a 5v (?) input, which is usually snagged
>> from an HDMI input; you may need an external DC Input, so either another
>> wall wart or a charging adapter with multiple 2A outputs.  (Thinking up
>> here where I have an RPi and HDMI switch, both need power.)
>>
>> My switches (so limited experience) will automatically switch to the last
>> active device -- maybe better phrased 'latest activated input'.  If you
>> power up your BluRay player the switch will automatically switch to that
>> input, which isn't bad unless you're watching a different input.  That's
>> happened once in over a year here.
>>
>> I have found it handy to have an HDMI coupler for troubleshooting, that
>> way can take out the switch, connect the two male ends of the cable
>> together.  (I get mine from an out-of-country source at around 50? each.)
>>
>> I need two outputs and one input and a switch not a splitter but the
> Amazon reviews make me think they will not work with my 30 feet cable to
> the projector.
>
>>
>> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190308/90642262/attachment.html>

From allen.p.edwards at gmail.com  Fri Mar  8 19:40:09 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Fri, 8 Mar 2019 11:40:09 -0800
Subject: [mythtv-users] CTRL-ALT-BACKSPACE
In-Reply-To: <CAH8UtKN64enW_46mYe-v84CzWex5Rf0Ze88yqVmMGM9J4yoVVg@mail.gmail.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
 <mc458eppr7ac2mn6aqfeuefvn19ku9r1kd@4ax.com>
 <CAH8UtKN64enW_46mYe-v84CzWex5Rf0Ze88yqVmMGM9J4yoVVg@mail.gmail.com>
Message-ID: <CAH8UtKN0CfTSFJmrMfHd_4r5BGwEmGpU=pinX9P+oEBoyFPn6g@mail.gmail.com>

Stephen,

I ran the command on /dev/sdb1 and it made its 5 passes and gave a
summary.  It was very quick. I am used to fsck taking hours to run. I
didn't time it but I would say under a minute.  At the time of day I killed
the power, Myth wasn't doing anything that I know of. The last show we
record was over more than an hour before. I used a clonezella bootable DVD
and exited to a command prompt to do the test.

On the CTRL-ALT-Backspace, I guess I am just going to try some things.
Entering commands on a terminal to either shut down Myth or X is not what I
am looking for.  If I could have a key sequence that killed just
mythfrontend that would be even better but killing X is fine.
CTRL-ALT-Backspace is probably faster than opening a terminal, finding a
pid and killing it and a lot more wife friendly.  Full disclosure:  I am
talking about my wife only, not commenting on the ability of woman in
general.  My daughter could handle it.

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190308/46b92f4b/attachment.html>

From vincent.mcintyre at gmail.com  Sat Mar  9 00:33:49 2019
From: vincent.mcintyre at gmail.com (Vincent McIntyre)
Date: Sat, 9 Mar 2019 11:33:49 +1100
Subject: [mythtv-users] mythmusic & filesystem permissions
Message-ID: <20190309003348.GA8898@ubuntu.windy>

Hi all

(ubuntu 16.04, 29.1+fixes.201902191821.8f37aa3~ubuntu16.04.1)

I have a strange issue with permissions.
I think I need more logging info, but read on and let me know what
you think.


I was trying to rescan a CD that I already had in my collection.
I removed the directory and rescanned ('scan for new music').
Then inserted the CD and ran 'import cd' as normal.

It scans the first track (creates the album subdir below the right
artist, and the first track in a .flac) and then stops with this popup:

"The encoder failed to create the file.
 Do you have write permissions for the music directory?"


In the log I get

Mar  9 11:15:27 mtv mythbackend: mythbackend[2868]: I ProcessRequest mainserver.cpp:1738 (HandleAnnounce) MainServer: MainServer::ANN Playback
Mar  9 11:15:27 mtv mythbackend: mythbackend[2868]: I ProcessRequest mainserver.cpp:1743 (HandleAnnounce) MainServer: adding: mtv(24c5650) as a client (events: 0)
Mar  9 11:15:27 mtv mythbackend: mythbackend[2868]: W ProcessRequest ringbuffer.cpp:700 (Start) RingBuf(/var/lib/mythtv/music//My_Friend_the_Chocolate_Cake/My_Friend_the_Chocolate_Cake/01-A_Midlife_s_Tale.flac): Not starting read ahead thread, this is a write only RingBuffer
Mar  9 11:15:27 mtv mythbackend: mythbackend[2868]: I MythSocketThread(72) mainserver.cpp:7674 (connectionClosed) Playback sock(24c5650) 'mtv' disconnected
Mar  9 11:15:27 mtv mythbackend: mythbackend[2868]: I MythSocketThread(74) mainserver.cpp:7712 (connectionClosed) FileTransfer sock(25f9f00) disconnected


Retrying the rip gives the same result.

On my system the backend runs as user 'mythtv'.
The frontend runs as 'frontend'. Both are in the 'mythtv' group.

$ ls -l /var/lib/mythtv/music//My_Friend_the_Chocolate_Cake/
total 23280
-rw-r--r-- 1 mythtv mythtv 23835694 Mar  9 11:13 01-A_Midlife_s_Tale.flac

$ ls -ld /var/lib/mythtv/music//My_Friend_the_Chocolate_Cake
drwxr-sr-x 3 mythtv mythtv 4096 Mar  9 11:13 /var/lib/mythtv/music//My_Friend_the_Chocolate_Cake/

$ ls -ld /var/lib/mythtv/music
drwxrwsr-x 277 mythtv mythtv 20480 Mar  9 11:13 /var/lib/mythtv/music/
$ ls -ld /var/lib/mythtv/
drwxrwsr-x 17 mythtv mythtv 4096 Jun  2  2018 /var/lib/mythtv/

I do have other directories in the music storage group but they
have the same permissions and are unused.

So everything looks in order.
How can I get more logging out of the ripping process?

One other clue. The new file is one byte shorter than the old one.
The file name changed (a typo was corrected in the upstream metadata)
This is the entry in the tar file backup I made.

-rw-r--r-- mythtv/mythtv 23835695 2011-09-03 11:00 My_Friend_the_Chocolate_Cake/My_Friend_the_Chocolate_Cake/01-A_Midwife_s_Tale.flac

Kind regards
Vince

From Larry.Finger at lwfinger.net  Sat Mar  9 01:32:43 2019
From: Larry.Finger at lwfinger.net (Larry Finger)
Date: Fri, 8 Mar 2019 19:32:43 -0600
Subject: [mythtv-users] Fwd:  mythmusic & filesystem permissions
In-Reply-To: <CAP71bdXT4moKCh16omE9GG=o-z7gqDXoj6qiT7p8DnmEvDNn2g@mail.gmail.com>
References: <20190309003348.GA8898@ubuntu.windy>
 <CAP71bdXT4moKCh16omE9GG=o-z7gqDXoj6qiT7p8DnmEvDNn2g@mail.gmail.com>
Message-ID: <f6a6f70b-1efc-23ac-2d0b-88b3f161b646@lwfinger.net>

From: *Vincent McIntyre* <vincent.mcintyre at gmail.com
> <mailto:vincent.mcintyre at gmail.com>>
> Date: Fri, Mar 8, 2019 at 6:34 PM
> Subject: [mythtv-users] mythmusic & filesystem permissions
> To: <mythtv-users at lists.mythtv.org <mailto:mythtv-users at lists.mythtv.org>>
> 
> 
> Hi all
> 
> (ubuntu 16.04, 29.1+fixes.201902191821.8f37aa3~ubuntu16.04.1)
> 
> I have a strange issue with permissions.
> I think I need more logging info, but read on and let me know what
> you think.
> 
> 
> I was trying to rescan a CD that I already had in my collection.
> I removed the directory and rescanned ('scan for new music').
> Then inserted the CD and ran 'import cd' as normal.
> 
> It scans the first track (creates the album subdir below the right
> artist, and the first track in a .flac) and then stops with this popup:
> 
> "The encoder failed to create the file.
>  ?Do you have write permissions for the music directory?"

I cannot help with the diagnosis of this error, but I can confirm that it 
exists. I am running a self-compiled 0.29-patches from the git repo, and I see 
exactly the same error. Most of the music that I want in MythMusic was scanned 
before this problem happened, but I am currently unable to add any new music - 
your situation exactly.

I had not been sufficiently motivated to actually look at error messages as the 
problem is low on my TODO list.

The following log message looks suspicious:

 > Mar  9 11:15:27 mtv mythbackend: mythbackend[2868]: W ProcessRequest 
ringbuffer.cpp:700 (Start) RingBuf(/var/lib/mythtv/music 
//My_Friend_the_Chocolate_Cake/My_Friend_the_Chocolate_Cake/01-A_Midlife_s_Tale.flac): 
Not starting read ahead thread, this is a write only RingBuffer

A write only RingBuffer seems strange. If you cannot read it, why write it in 
the first place?

Larry


From stephen_agent at jsw.gen.nz  Sat Mar  9 02:57:13 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Sat, 09 Mar 2019 15:57:13 +1300
Subject: [mythtv-users] CTRL-ALT-BACKSPACE
In-Reply-To: <CAH8UtKN0CfTSFJmrMfHd_4r5BGwEmGpU=pinX9P+oEBoyFPn6g@mail.gmail.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
 <mc458eppr7ac2mn6aqfeuefvn19ku9r1kd@4ax.com>
 <CAH8UtKN64enW_46mYe-v84CzWex5Rf0Ze88yqVmMGM9J4yoVVg@mail.gmail.com>
 <CAH8UtKN0CfTSFJmrMfHd_4r5BGwEmGpU=pinX9P+oEBoyFPn6g@mail.gmail.com>
Message-ID: <lda68e9mgcbjblhasnd26gob31df4b02fa@4ax.com>

On Fri, 8 Mar 2019 11:40:09 -0800, you wrote:

>Stephen,
>
>I ran the command on /dev/sdb1 and it made its 5 passes and gave a
>summary.  It was very quick. I am used to fsck taking hours to run. I
>didn't time it but I would say under a minute.  At the time of day I killed
>the power, Myth wasn't doing anything that I know of. The last show we
>record was over more than an hour before. I used a clonezella bootable DVD
>and exited to a command prompt to do the test.

It looks like you were right and it was mostly shut down at the time -
good news.  But you still need to make sure to check the database
also.

Fsck processing time tends to be proportional to the number of files
on a partition.  So if you have a huge collection of 100,000 photo
files, then it will take a fair bit longer.

>On the CTRL-ALT-Backspace, I guess I am just going to try some things.
>Entering commands on a terminal to either shut down Myth or X is not what I
>am looking for.  If I could have a key sequence that killed just
>mythfrontend that would be even better but killing X is fine.
>CTRL-ALT-Backspace is probably faster than opening a terminal, finding a
>pid and killing it and a lot more wife friendly.  Full disclosure:  I am
>talking about my wife only, not commenting on the ability of woman in
>general.  My daughter could handle it.
>
>Allen

One alternative is to use lirc to assign a button on your remote to
kill mythfrontend.real.  Lirc can be set up to run scripts using
irexec.  The script would do a ps -e and find any running copies of
mythbackend.real and kill them.  Then the mythfrontend script would
see that mythfrontend.real had died and would restart it.

From jam at tigger.ws  Sat Mar  9 03:13:21 2019
From: jam at tigger.ws (James Linder)
Date: Sat, 9 Mar 2019 11:13:21 +0800
Subject: [mythtv-users] Web Frontend stopped working yesterday
In-Reply-To: <mailman.41.1552061384.1604.mythtv-users@mythtv.org>
References: <mailman.41.1552061384.1604.mythtv-users@mythtv.org>
Message-ID: <F6B5415D-4566-44D1-BA9C-3626A3C16A51@tigger.ws>



> On 9 Mar 2019, at 12:09 am, mythtv-users-request at mythtv.org wrote:
> 
> 
> As my Internet provider again changed my IP and I no longer use a MythTV
> frontend on another computer, I set the backend IP to 127.0.0.1. I made
> also some system upgrades, which did not change MythTV but perhaps some
> libraries used. I don't remember any other intentional changes.
> 
> Frontend works, Web frontend does not:
> 
> Firefox can?t establish a connection to the server at localhost:6544.
> 
> Nmap doesn't show the port 6544:
> 
> --8<---------------cut here---------------start------------->8---
> Starting Nmap 7.70 ( https://nmap.org ) at 2019-03-08 07:28 CET
> Nmap scan report for localhost (127.0.0.1)
> Host is up (0.000092s latency).
> Other addresses for localhost (not scanned): ::1
> Not shown: 994 closed ports
> PORT     STATE SERVICE
> 22/tcp   open  ssh
> 25/tcp   open  smtp
> 80/tcp   open  http
> 631/tcp  open  ipp
> 3306/tcp open  mysql
> 6543/tcp open  mythtv
> --8<---------------cut here---------------end--------------->8---
> 
> An attempt to connect to
> 
> http://localhost:6543/
> 
> just gives the message "Waiting for localhost..."
> 
> MythTV is version 30.0-dmo3 on Debian testing.
> 
> Best regards
> 
> Janusz
> 
> P.S. I notice another probably unrelated problem: backend stopped at
> night for some unknown reason.

There is a delightful TV (BBC) series by Michael Mosley called ?Trust me I?m a Doctor?.
Likewise. There is much in your question ?

Do typical network setup. You do not need a modem firewall unless you have windows machines. (1)

ISP ??? typically phone line ?? [Modem router] ?? [Backend] ?? [Optional front ends] ?? [other machines] ??

Select an IP for your network; typically 10.x.y.z or 192.168.x.y (2) (3)

Never change frontend or backend addresses. You may use 127.0.0.1 to talk to the same machine. (4)
EF a frontend / backend /database on the same machine may use 127.0.0.1 to talk to one another.

now:
No matter what your ISP does he cannot affect your myth machines
Noone on the internet can fiddle with your mythtv (5)(6)
IPV6 changes some of the rules

This does not answer why you can?t talk to yourself. I assume that is buried in the info you did not give
How (and why) does your ISP have anything to do with your myth machines (or your network IP)
What firewalls (and why) are you running. Firewalling 127.0.0.1 is frankly daft.






1. The modem firewall?s ONLY purpose is to stop window machines that have been virused calling OUT
   Your modem does NAT and noone on the internet can call into your machines
      Internet routers may not route private IPs eg 10.x.y.z 192.168.x.y (and class B?s
   Even if your router gets hacked, reboot restores all files.

2. Every modem I?ve encountered *can* set their own IP

3. 127.0.0.1 is the loopback address, you cannot use it as a network address.

4. Ofcourse you can and it?s easy but not trivial to deal with

5. You can arrange internet access. A ssh tunnel is a good option
   http://tigger.ws/wiki/index.php5?title=Port_Forward
   but there are password solutions with server options on your modem

6. Now none of your machines (on a trusted network ie you trust everyone) need a firewall (1)


James

From allen.p.edwards at gmail.com  Sat Mar  9 04:12:09 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Fri, 8 Mar 2019 20:12:09 -0800
Subject: [mythtv-users] CTRL-ALT-BACKSPACE
In-Reply-To: <CAH8UtKN0CfTSFJmrMfHd_4r5BGwEmGpU=pinX9P+oEBoyFPn6g@mail.gmail.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
 <mc458eppr7ac2mn6aqfeuefvn19ku9r1kd@4ax.com>
 <CAH8UtKN64enW_46mYe-v84CzWex5Rf0Ze88yqVmMGM9J4yoVVg@mail.gmail.com>
 <CAH8UtKN0CfTSFJmrMfHd_4r5BGwEmGpU=pinX9P+oEBoyFPn6g@mail.gmail.com>
Message-ID: <CAH8UtKMMy59LdC75G_QVu-K-1QvbJ+OJQbfaX6ogDCpGszj-Kw@mail.gmail.com>

I am almost there.  Just two problem.

Editing  /etc/default/keyboard to
XKBOPTIONS="terminate:ctrl_alt_bksp"
This made CTRL-ALT-BS restart X almost.

The almost is that there is still a logon prompt.  I googled this to death
and found tons of answers that did not work.  That problem is that even
after I disabled passwords for my username, it still has the login prompt
so I have to hit ENTER to start X. I could live with this if I have to.

The other problem is that sometimes (half my tries so far) I end up with
two instances of mythfrontend and when we start a show, we hear an echo in
the voices as I guess both are running. This one is much more difficult to
live with.  I can see two instances in top as well as a (2) on the taskbar.

Allen

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190308/4cd481a5/attachment-0001.html>

From shredder83 at gmail.com  Sat Mar  9 04:53:59 2019
From: shredder83 at gmail.com (Robert Birch)
Date: Fri, 8 Mar 2019 21:53:59 -0700
Subject: [mythtv-users] Lirc Remote Config File
Message-ID: <5A197990-001A-4D69-8E2E-E50F4E7171C7@gmail.com>

I wonder if someone can help me.

I have two Dish VIP722 STBs. I need to find a lirc config file for change the remote code to channel 6.

The lirc file on lirc.org <http://lirc.org/> that has all the different channels in it, doesn?t work for me. I don?t have an IR Receiver (only change the channels with lirc) so I can?t create my own.

Does anyone have a working file?

Thanks,
Shredder83
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190308/ea5603a2/attachment.html>

From mkbloke at gmail.com  Sat Mar  9 04:54:09 2019
From: mkbloke at gmail.com (Ian Cameron)
Date: Sat, 9 Mar 2019 04:54:09 +0000
Subject: [mythtv-users] Web Frontend stopped working yesterday
In-Reply-To: <F6B5415D-4566-44D1-BA9C-3626A3C16A51@tigger.ws>
References: <mailman.41.1552061384.1604.mythtv-users@mythtv.org>
 <F6B5415D-4566-44D1-BA9C-3626A3C16A51@tigger.ws>
Message-ID: <CAC+xXWOhuwR11oHGmt0ri5NnSVUfEsp2owA5uMk9hMN7i3Ca6A@mail.gmail.com>

On Sat, 9 Mar 2019 at 03:14, James Linder <jam at tigger.ws> wrote:

> > On 9 Mar 2019, at 12:09 am, mythtv-users-request at mythtv.org wrote:
> > Nmap doesn't show the port 6544:
>

Try:

sudo netstat -anp | grep myth

to see the ports the back-end is listening on.

Cheers, Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/e7a5d385/attachment.html>

From mkbloke at gmail.com  Sat Mar  9 05:00:36 2019
From: mkbloke at gmail.com (Ian Cameron)
Date: Sat, 9 Mar 2019 05:00:36 +0000
Subject: [mythtv-users] CTRL-ALT-BACKSPACE
In-Reply-To: <CAH8UtKMMy59LdC75G_QVu-K-1QvbJ+OJQbfaX6ogDCpGszj-Kw@mail.gmail.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
 <mc458eppr7ac2mn6aqfeuefvn19ku9r1kd@4ax.com>
 <CAH8UtKN64enW_46mYe-v84CzWex5Rf0Ze88yqVmMGM9J4yoVVg@mail.gmail.com>
 <CAH8UtKN0CfTSFJmrMfHd_4r5BGwEmGpU=pinX9P+oEBoyFPn6g@mail.gmail.com>
 <CAH8UtKMMy59LdC75G_QVu-K-1QvbJ+OJQbfaX6ogDCpGszj-Kw@mail.gmail.com>
Message-ID: <CAC+xXWMqmtPDPcwRBRX90fBBdq1TiLoBfsAgCzXD1uqR8UdAEg@mail.gmail.com>

On Sat, 9 Mar 2019 at 04:13, Allen Edwards <allen.p.edwards at gmail.com>
wrote:

> The almost is that there is still a logon prompt.  I googled this to death
> and found tons of answers that did not work.  That problem is that even
> after I disabled passwords for my username, it still has the login prompt
> so I have to hit ENTER to start X. I could live with this if I have to.
>

What desktop environment are you using?

Under Gnome, you can go into User Accounts, click Unlock in the top right
hand corner of the window, then for your account, set Automatic Login to on.

The other problem is that sometimes (half my tries so far) I end up with
> two instances of mythfrontend and when we start a show, we hear an echo in
> the voices as I guess both are running. This one is much more difficult to
> live with.  I can see two instances in top as well as a (2) on the taskbar.
>

No idea on that, sorry.

Cheers, Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/165be927/attachment.html>

From allen.p.edwards at gmail.com  Sat Mar  9 05:46:56 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Fri, 8 Mar 2019 21:46:56 -0800
Subject: [mythtv-users] CTRL-ALT-BACKSPACE
In-Reply-To: <CAC+xXWMqmtPDPcwRBRX90fBBdq1TiLoBfsAgCzXD1uqR8UdAEg@mail.gmail.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
 <mc458eppr7ac2mn6aqfeuefvn19ku9r1kd@4ax.com>
 <CAH8UtKN64enW_46mYe-v84CzWex5Rf0Ze88yqVmMGM9J4yoVVg@mail.gmail.com>
 <CAH8UtKN0CfTSFJmrMfHd_4r5BGwEmGpU=pinX9P+oEBoyFPn6g@mail.gmail.com>
 <CAH8UtKMMy59LdC75G_QVu-K-1QvbJ+OJQbfaX6ogDCpGszj-Kw@mail.gmail.com>
 <CAC+xXWMqmtPDPcwRBRX90fBBdq1TiLoBfsAgCzXD1uqR8UdAEg@mail.gmail.com>
Message-ID: <CAH8UtKPETMJvemwZAzWgORg7X2zAsX5nyAQFV5Q4JYaP7A51iA@mail.gmail.com>

On Fri, Mar 8, 2019 at 9:01 PM Ian Cameron <mkbloke at gmail.com> wrote:

> On Sat, 9 Mar 2019 at 04:13, Allen Edwards <allen.p.edwards at gmail.com>
> wrote:
>
>> The almost is that there is still a logon prompt.  I googled this to
>> death and found tons of answers that did not work.  That problem is that
>> even after I disabled passwords for my username, it still has the login
>> prompt so I have to hit ENTER to start X. I could live with this if I have
>> to.
>>
>
> What desktop environment are you using?
>
> Under Gnome, you can go into User Accounts, click Unlock in the top right
> hand corner of the window, then for your account, set Automatic Login to on.
>
> The other problem is that sometimes (half my tries so far) I end up with
>> two instances of mythfrontend and when we start a show, we hear an echo in
>> the voices as I guess both are running. This one is much more difficult to
>> live with.  I can see two instances in top as well as a (2) on the taskbar.
>>
>
> No idea on that, sorry.
>
> Cheers, Ian
>
>
I guess I deleted too much of the first text I wrote.  I do have autostart
set and when I power up Myth starts without any prompt. I only get the
prompt on restart from my new CTRL-ALT-Backspace key sequence.

I have read instructions to go into the power-manager and unclick "lock
screen when going from suspend/hibernate"  But I do not have power-manager
installed and the last time I installed something from a Google search
suggestion it took half a day to get my system back where it worked so I
wasn't going to go there without some confirmation that it was still
relevant for Mythbuntu 16. I may have said 18 earlier but that was an error.

I assume that the power-manager is some frontend for a command I need to
change in some config file but I can't find reference to where or what it
is. I don't even know if that is the issue as I am not really coming out of
hibernate but rather restarting X.

Mythbunty has xfce.

I set autologon when I installed Myth and checked that it was set here

*dad at NewMyth:~$ more /etc/lightdm/lightdm.conf*
*[SeatDefaults]*
*user-session=mythbuntu*
*allow-guest=false*
*#autologin-user=*
*[Seat:*]*
*autologin-guest=false*
*autologin-user=dad*
*autologin-user-timeout=0*

In case it is relevant, I have the screensaver disabled.

Allen


On the double instance of Myth.  I just repeated it and was able to close
one instance just like you close Myth and then there was just one.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190308/ddd94267/attachment.html>

From jsbien at mimuw.edu.pl  Sat Mar  9 06:17:13 2019
From: jsbien at mimuw.edu.pl (Janusz S. =?utf-8?Q?Bie=C5=84?=)
Date: Sat, 09 Mar 2019 07:17:13 +0100
Subject: [mythtv-users] Web Frontend stopped working yesterday
References: <mailman.41.1552061384.1604.mythtv-users@mythtv.org>
 <F6B5415D-4566-44D1-BA9C-3626A3C16A51@tigger.ws>
 <CAC+xXWOhuwR11oHGmt0ri5NnSVUfEsp2owA5uMk9hMN7i3Ca6A@mail.gmail.com>
Message-ID: <86r2bgshau.fsf@mimuw.edu.pl>

On Sat, Mar 09 2019 at  4:54 +00, Ian Cameron wrote:
> On Sat, 9 Mar 2019 at 03:14, James Linder <jam at tigger.ws> wrote:
>
>  > On 9 Mar 2019, at 12:09 am, mythtv-users-request at mythtv.org wrote:
>  > Nmap doesn't show the port 6544:
>
> Try:
>
> sudo netstat -anp | grep myth
>
> to see the ports the back-end is listening on.



--8<---------------cut here---------------start------------->8---
tcp        0      0 0.0.0.0:6543            0.0.0.0:*               LISTEN      1241/mythbackend    
tcp        0      0 192.168.0.4:37086       192.168.0.2:65001       ESTABLISHED 1241/mythbackend    
tcp6       0      0 :::6543                 :::*                    LISTEN      1241/mythbackend    
udp        0      0 0.0.0.0:53352           0.0.0.0:*                           1241/mythbackend    
unix  3      [ ]         STREAM     CONNECTED     1468747  1241/mythbackend     
unix  2      [ ]         STREAM     CONNECTED     379355   1241/mythbackend     
unix  3      [ ]         STREAM     CONNECTED     32895    1241/mythbackend     
unix  3      [ ]         STREAM     CONNECTED     29589    1241/mythbackend     
unix  3      [ ]         STREAM     CONNECTED     29588    1241/mythbackend     
unix  3      [ ]         STREAM     CONNECTED     31785    1241/mythbackend     
unix  2      [ ]         STREAM     CONNECTED     31851    1241/mythbackend     
unix  3      [ ]         STREAM     CONNECTED     32680    1241/mythbackend     
unix  3      [ ]         STREAM     CONNECTED     31854    1241/mythbackend     
unix  3      [ ]         STREAM     CONNECTED     31570    1241/mythbackend 
--8<---------------cut here---------------end--------------->8---

As I said before:

the Web frontend port 6544 is not open at all,

an attempt to connect to the open port 6543 takes forever.

>
> Cheers, Ian

On Sat, Mar 09 2019 at 11:13 +08, James Linder wrote:

[...]

> 1. The modem firewall?s ONLY purpose is to stop window machines that have been virused calling OUT
>    Your modem does NAT and noone on the internet can call into your machines
>       Internet routers may not route private IPs eg 10.x.y.z 192.168.x.y (and class B?s
>    Even if your router gets hacked, reboot restores all files.

Irrelevant.

> 2. Every modem I?ve encountered *can* set their own IP

Which IP? Anyway mine cannot.

>
> 3. 127.0.0.1 is the loopback address, you cannot use it as a network address.

Of course I can.
>
> 4. Ofcourse you can and it?s easy but not trivial to deal with

???

At http://127.0.0.1/ there is just Apache2 Debian Default Page.

>
> 5. You can arrange internet access. A ssh tunnel is a good option
>    http://tigger.ws/wiki/index.php5?title=Port_Forward
>    but there are password solutions with server options on your modem

Irrelevant. Tunnel to what???

>
> 6. Now none of your machines (on a trusted network ie you trust everyone) need a firewall (1)

Irrelevant.

Best regards

Janusz

-- 
             ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

From mkbloke at gmail.com  Sat Mar  9 06:22:06 2019
From: mkbloke at gmail.com (Ian Cameron)
Date: Sat, 9 Mar 2019 06:22:06 +0000
Subject: [mythtv-users] CTRL-ALT-BACKSPACE
In-Reply-To: <CAH8UtKPETMJvemwZAzWgORg7X2zAsX5nyAQFV5Q4JYaP7A51iA@mail.gmail.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
 <mc458eppr7ac2mn6aqfeuefvn19ku9r1kd@4ax.com>
 <CAH8UtKN64enW_46mYe-v84CzWex5Rf0Ze88yqVmMGM9J4yoVVg@mail.gmail.com>
 <CAH8UtKN0CfTSFJmrMfHd_4r5BGwEmGpU=pinX9P+oEBoyFPn6g@mail.gmail.com>
 <CAH8UtKMMy59LdC75G_QVu-K-1QvbJ+OJQbfaX6ogDCpGszj-Kw@mail.gmail.com>
 <CAC+xXWMqmtPDPcwRBRX90fBBdq1TiLoBfsAgCzXD1uqR8UdAEg@mail.gmail.com>
 <CAH8UtKPETMJvemwZAzWgORg7X2zAsX5nyAQFV5Q4JYaP7A51iA@mail.gmail.com>
Message-ID: <CAC+xXWNnoCBww4hN=SKG8-b53ZzwQHmfczzKAUMvdrXKTMMtEw@mail.gmail.com>

On Sat, 9 Mar 2019 at 05:48, Allen Edwards <allen.p.edwards at gmail.com>
wrote:

> I guess I deleted too much of the first text I wrote.  I do have autostart
> set and when I power up Myth starts without any prompt. I only get the
> prompt on restart from my new CTRL-ALT-Backspace key sequence.
>

>From what I can see, this is designed-in behaviour on the part of LightDM,
as per:

https://bugs.launchpad.net/lightdm/+bug/1396824

The solution there is probably your best bet for trying next, i.e. adding:

display-stopped-script=pkill lightdm

to the SeatDefaults section of lightdm.conf

Cheers, Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/501504c0/attachment.html>

From mkbloke at gmail.com  Sat Mar  9 06:48:04 2019
From: mkbloke at gmail.com (Ian Cameron)
Date: Sat, 9 Mar 2019 06:48:04 +0000
Subject: [mythtv-users] Web Frontend stopped working yesterday
In-Reply-To: <86r2bgshau.fsf@mimuw.edu.pl>
References: <mailman.41.1552061384.1604.mythtv-users@mythtv.org>
 <F6B5415D-4566-44D1-BA9C-3626A3C16A51@tigger.ws>
 <CAC+xXWOhuwR11oHGmt0ri5NnSVUfEsp2owA5uMk9hMN7i3Ca6A@mail.gmail.com>
 <86r2bgshau.fsf@mimuw.edu.pl>
Message-ID: <CAC+xXWOk9cg+4Hct1Muz4RLw-+ZLo09Cs+zmeGUFpLJcaNSc-A@mail.gmail.com>

On Sat, 9 Mar 2019 at 06:18, Janusz S. Bie? <jsbien at mimuw.edu.pl> wrote:

> the Web frontend port 6544 is not open at all,
>
> an attempt to connect to the open port 6543 takes forever.
>

Strange.

Some of these may seem obvious, but off the top of my head, I would:

Check IP and port number configurations in mythtv-setup - stop the back-end
first and start again after running mythtv-setup using systemctl.
Check that only one instance of the back-end is running at a given time via
ps -ef output information.
Check that nothing else is using port 6544 via netstat -anp output
information.
Enable logging on the back-end and start looking through the logs generated
to see if the cause of the problem can be found there.

Cheers, Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/de8b792a/attachment.html>

From jsbien at mimuw.edu.pl  Sat Mar  9 07:20:06 2019
From: jsbien at mimuw.edu.pl (Janusz S. =?utf-8?Q?Bie=C5=84?=)
Date: Sat, 09 Mar 2019 08:20:06 +0100
Subject: [mythtv-users] Web Frontend works again (was: Web Frontend stopped
 working yesterday)
In-Reply-To: <CAC+xXWOk9cg+4Hct1Muz4RLw-+ZLo09Cs+zmeGUFpLJcaNSc-A@mail.gmail.com>
 (Ian Cameron's message of "Sat, 9 Mar 2019 06:48:04 +0000")
References: <mailman.41.1552061384.1604.mythtv-users@mythtv.org>
 <F6B5415D-4566-44D1-BA9C-3626A3C16A51@tigger.ws>
 <CAC+xXWOhuwR11oHGmt0ri5NnSVUfEsp2owA5uMk9hMN7i3Ca6A@mail.gmail.com>
 <86r2bgshau.fsf@mimuw.edu.pl>
 <CAC+xXWOk9cg+4Hct1Muz4RLw-+ZLo09Cs+zmeGUFpLJcaNSc-A@mail.gmail.com>
Message-ID: <86a7i4qztl.fsf_-_@mimuw.edu.pl>


I would not call the problem "solved" because I still don't why it
didn't worked earlier and why it works now :-)

On Sat, Mar 09 2019 at  6:48 +00, Ian Cameron wrote:
> On Sat, 9 Mar 2019 at 06:18, Janusz S. Bie? <jsbien at mimuw.edu.pl> wrote:
>
>  the Web frontend port 6544 is not open at all,
>
>  an attempt to connect to the open port 6543 takes forever.
>
> Strange.
>
> Some of these may seem obvious, but off the top of my head, I would:
>
> Check IP and port number configurations in mythtv-setup - stop the
> back-end first and start again after running mythtv-setup using
> systemctl.

I understood mythtv-setup stops and restarts the backend and I relied on
it. Looks like restarting it with systemctl helped.

> Check that only one instance of the back-end is running at a given time via ps -ef output information.
> Check that nothing else is using port 6544 via netstat -anp output information.
> Enable logging on the back-end and start looking through the logs generated to see if the cause of the problem can be found there.

I will store your suggestions in case the problem reappear in the
future.

Thank you very much for your help.

Janusz

P.S. A comment to James Linder: I made a mental shortcut and you
misunderstood me. The modem used temporarily by me doesn't allow to
control IPs assigned to the local network, so the IP of my computer
changes from time to time, e.g. after rebooting.

-- 
             ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

From mkbloke at gmail.com  Sat Mar  9 07:40:29 2019
From: mkbloke at gmail.com (Ian Cameron)
Date: Sat, 9 Mar 2019 07:40:29 +0000
Subject: [mythtv-users] Web Frontend works again (was: Web Frontend
 stopped working yesterday)
In-Reply-To: <86a7i4qztl.fsf_-_@mimuw.edu.pl>
References: <mailman.41.1552061384.1604.mythtv-users@mythtv.org>
 <F6B5415D-4566-44D1-BA9C-3626A3C16A51@tigger.ws>
 <CAC+xXWOhuwR11oHGmt0ri5NnSVUfEsp2owA5uMk9hMN7i3Ca6A@mail.gmail.com>
 <86r2bgshau.fsf@mimuw.edu.pl>
 <CAC+xXWOk9cg+4Hct1Muz4RLw-+ZLo09Cs+zmeGUFpLJcaNSc-A@mail.gmail.com>
 <86a7i4qztl.fsf_-_@mimuw.edu.pl>
Message-ID: <CAC+xXWN4xZMz3EtSGGmnQteHqyFnAf8r3LyZaWFsDmOKH-F-qw@mail.gmail.com>

On Sat, 9 Mar 2019 at 07:20, Janusz S. Bie? <jsbien at mimuw.edu.pl> wrote:

> I would not call the problem "solved" because I still don't why it
> didn't worked earlier and why it works now :-)
>

Good to hear, more or less!

I understood mythtv-setup stops and restarts the backend and I relied on
> it. Looks like restarting it with systemctl helped.
>

It kind of can, but it doesn't play nicely with systemctl usually, so I
always recommend issuing the systemctl stop/start commands manually
before/after running mythtv-setup.

What would help solve this would be the inclusion of a wrapper script by
the package maintainers that executes the necessary 'sudo systemctl'
commands before/after executing the real mythtv-setup binary.

Cheers, Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/731d5958/attachment.html>

From jsbien at mimuw.edu.pl  Sat Mar  9 07:57:53 2019
From: jsbien at mimuw.edu.pl (Janusz S. =?utf-8?Q?Bie=C5=84?=)
Date: Sat, 09 Mar 2019 08:57:53 +0100
Subject: [mythtv-users] Web Frontend works again
In-Reply-To: <CAC+xXWN4xZMz3EtSGGmnQteHqyFnAf8r3LyZaWFsDmOKH-F-qw@mail.gmail.com>
 (Ian Cameron's message of "Sat, 9 Mar 2019 07:40:29 +0000")
References: <mailman.41.1552061384.1604.mythtv-users@mythtv.org>
 <F6B5415D-4566-44D1-BA9C-3626A3C16A51@tigger.ws>
 <CAC+xXWOhuwR11oHGmt0ri5NnSVUfEsp2owA5uMk9hMN7i3Ca6A@mail.gmail.com>
 <86r2bgshau.fsf@mimuw.edu.pl>
 <CAC+xXWOk9cg+4Hct1Muz4RLw-+ZLo09Cs+zmeGUFpLJcaNSc-A@mail.gmail.com>
 <86a7i4qztl.fsf_-_@mimuw.edu.pl>
 <CAC+xXWN4xZMz3EtSGGmnQteHqyFnAf8r3LyZaWFsDmOKH-F-qw@mail.gmail.com>
Message-ID: <86lg1opji6.fsf@mimuw.edu.pl>

On Sat, Mar 09 2019 at  7:40 +00, Ian Cameron wrote:
> On Sat, 9 Mar 2019 at 07:20, Janusz S. Bie? <jsbien at mimuw.edu.pl> wrote:
>
>  I would not call the problem "solved" because I still don't why it
>  didn't worked earlier and why it works now :-)
>
> Good to hear, more or less!
>
>  I understood mythtv-setup stops and restarts the backend and I relied on
>  it. Looks like restarting it with systemctl helped.
>
> It kind of can, but it doesn't play nicely with systemctl usually, so
> I always recommend issuing the systemctl stop/start commands manually
> before/after running mythtv-setup.

I think now my change of IP was not actually stored, partially because
of my careless. When exiting mythtv-setup it complains

   You have a Video Storage Group, but have not set up all Image
   Group...Do you want to get back and fix the problem?

I consider it irrelevant and select

  No. I know what I am doing.

but the program hangs and I simply kill it. I have the feeling it used
to work for years and perhaps it stopped now.

Best regards

Janusz

-- 
             ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

From stephen_agent at jsw.gen.nz  Sat Mar  9 08:30:23 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Sat, 09 Mar 2019 21:30:23 +1300
Subject: [mythtv-users] Web Frontend works again (was: Web Frontend
 stopped working yesterday)
In-Reply-To: <86a7i4qztl.fsf_-_@mimuw.edu.pl>
References: <mailman.41.1552061384.1604.mythtv-users@mythtv.org>
 <F6B5415D-4566-44D1-BA9C-3626A3C16A51@tigger.ws>
 <CAC+xXWOhuwR11oHGmt0ri5NnSVUfEsp2owA5uMk9hMN7i3Ca6A@mail.gmail.com>
 <86r2bgshau.fsf@mimuw.edu.pl>
 <CAC+xXWOk9cg+4Hct1Muz4RLw-+ZLo09Cs+zmeGUFpLJcaNSc-A@mail.gmail.com>
 <86a7i4qztl.fsf_-_@mimuw.edu.pl>
Message-ID: <8jt68e1m0u529b11n0oinl5eafe1fjh89i@4ax.com>

On Sat, 09 Mar 2019 08:20:06 +0100, you wrote:

>I understood mythtv-setup stops and restarts the backend and I relied on
>it. Looks like restarting it with systemctl helped.

No.  As of systemd, the commands inside MythTV do not normally work to
shut down and restart mythbackend.  The default stop command is
"killall mythbackend", which might work.  The default start command is
"mythbackend", which definitely will not work correctly.  So you
really need to manually stop mythbackend before running mythtv-setup:

sudo systemctl stop mythtv-backend

and after closing mythtv-setup, restart mythbackend:

sudo systemctl start mythtv-backend

It should be possible to write an sudoer helper script that could be
used to start and stop mythbackend using systemctl and then change the
commands inside MythTV (and in the mythtv-setup script that runs
mythtv-setup.real) to use that script.  The devs have not got around
to looking at that, so if I find the time I think I will.

So the reason you had problems with web frontend was probably that
mythbackend had not been shut down when you ran mythtv-setup, and it
would not have seen the setup changes you had made.  Or that
mythbackend had been shut down, but was started up not using systemctl
and found either no config file, or the wrong config file.

From mkbloke at gmail.com  Sat Mar  9 08:36:32 2019
From: mkbloke at gmail.com (Ian Cameron)
Date: Sat, 9 Mar 2019 08:36:32 +0000
Subject: [mythtv-users] Web Frontend works again
In-Reply-To: <86lg1opji6.fsf@mimuw.edu.pl>
References: <mailman.41.1552061384.1604.mythtv-users@mythtv.org>
 <F6B5415D-4566-44D1-BA9C-3626A3C16A51@tigger.ws>
 <CAC+xXWOhuwR11oHGmt0ri5NnSVUfEsp2owA5uMk9hMN7i3Ca6A@mail.gmail.com>
 <86r2bgshau.fsf@mimuw.edu.pl>
 <CAC+xXWOk9cg+4Hct1Muz4RLw-+ZLo09Cs+zmeGUFpLJcaNSc-A@mail.gmail.com>
 <86a7i4qztl.fsf_-_@mimuw.edu.pl>
 <CAC+xXWN4xZMz3EtSGGmnQteHqyFnAf8r3LyZaWFsDmOKH-F-qw@mail.gmail.com>
 <86lg1opji6.fsf@mimuw.edu.pl>
Message-ID: <CAC+xXWNkO25UMqc9E67Hey5yshZSPzUq66Cuq34yzCresWAOmg@mail.gmail.com>

On Sat, 9 Mar 2019 at 07:57, Janusz S. Bie? <jsbien at mimuw.edu.pl> wrote:

> On Sat, Mar 09 2019 at  7:40 +00, Ian Cameron wrote:
> > On Sat, 9 Mar 2019 at 07:20, Janusz S. Bie? <jsbien at mimuw.edu.pl> wrote:
> >  I understood mythtv-setup stops and restarts the backend and I relied on
> >  it. Looks like restarting it with systemctl helped.
> >
> > It kind of can, but it doesn't play nicely with systemctl usually, so
> > I always recommend issuing the systemctl stop/start commands manually
> > before/after running mythtv-setup.
>
> I think now my change of IP was not actually stored, partially because
> of my careless. When exiting mythtv-setup it complains
>

>    You have a Video Storage Group, but have not set up all Image
>    Group...Do you want to get back and fix the problem?
>
> I consider it irrelevant and select
>
>   No. I know what I am doing.
>
> but the program hangs and I simply kill it. I have the feeling it used
> to work for years and perhaps it stopped now.
>

That seems a likely problem, regarding the IP address change not getting
stored if you had to kill it.

Cheers, Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/73c08c2f/attachment.html>

From stephen_agent at jsw.gen.nz  Sat Mar  9 08:40:25 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Sat, 09 Mar 2019 21:40:25 +1300
Subject: [mythtv-users] Web Frontend works again
In-Reply-To: <86lg1opji6.fsf@mimuw.edu.pl>
References: <mailman.41.1552061384.1604.mythtv-users@mythtv.org>
 <F6B5415D-4566-44D1-BA9C-3626A3C16A51@tigger.ws>
 <CAC+xXWOhuwR11oHGmt0ri5NnSVUfEsp2owA5uMk9hMN7i3Ca6A@mail.gmail.com>
 <86r2bgshau.fsf@mimuw.edu.pl>
 <CAC+xXWOk9cg+4Hct1Muz4RLw-+ZLo09Cs+zmeGUFpLJcaNSc-A@mail.gmail.com>
 <86a7i4qztl.fsf_-_@mimuw.edu.pl>
 <CAC+xXWN4xZMz3EtSGGmnQteHqyFnAf8r3LyZaWFsDmOKH-F-qw@mail.gmail.com>
 <86lg1opji6.fsf@mimuw.edu.pl>
Message-ID: <odu68el3nvngk2tjcaes1ucluc8tcmbnsh@4ax.com>

On Sat, 09 Mar 2019 08:57:53 +0100, you wrote:

>I think now my change of IP was not actually stored, partially because
>of my careless. When exiting mythtv-setup it complains
>
>   You have a Video Storage Group, but have not set up all Image
>   Group...Do you want to get back and fix the problem?
>
>I consider it irrelevant and select
>
>  No. I know what I am doing.
>
>but the program hangs and I simply kill it. I have the feeling it used
>to work for years and perhaps it stopped now.

Mythtv-setup now stores changes section by section (as of
version0.28?).  So when you go into one section of the setup menu,
then exit it again, you get the option to save or discard the changes
you made while in that section.  When you come to exiting completely
from mythtv-setup, you have already exited from the section where you
were making changes and it will have stored them (or discarded them if
you told it to do that).  So when you get the message about problems
with the storage groups, all the changes you made will have been
stored already.

When you say it hangs on exit, you need to be bit more specific.  Does
the GUI screen of mythtv-setup.real go away?  If so, then the "hang"
was probably happening in the mythtv-setup script that is wrapped
around mythtv-setup.real.  If the GUI screen was still showing when it
hung, then the problem is in mythtv-setup.real.  There are some things
that can make it take a long time to do things, so next time it does
that, it would be an idea just to go away and come back in 10 minutes
of so and see if it did eventually exit.  And also, you can look at
the /var/log/mythtv/mythtv-setup.log file and see what might be
happening.  In any case, killing mythtv-setup at that point would not
prevent it from having saved all your changes.

From jsbien at mimuw.edu.pl  Sat Mar  9 08:55:03 2019
From: jsbien at mimuw.edu.pl (Janusz S. =?utf-8?Q?Bie=C5=84?=)
Date: Sat, 09 Mar 2019 09:55:03 +0100
Subject: [mythtv-users] Web Frontend works again
In-Reply-To: <odu68el3nvngk2tjcaes1ucluc8tcmbnsh@4ax.com> (Stephen
 Worthington's message of "Sat, 09 Mar 2019 21:40:25 +1300")
References: <mailman.41.1552061384.1604.mythtv-users@mythtv.org>
 <F6B5415D-4566-44D1-BA9C-3626A3C16A51@tigger.ws>
 <CAC+xXWOhuwR11oHGmt0ri5NnSVUfEsp2owA5uMk9hMN7i3Ca6A@mail.gmail.com>
 <86r2bgshau.fsf@mimuw.edu.pl>
 <CAC+xXWOk9cg+4Hct1Muz4RLw-+ZLo09Cs+zmeGUFpLJcaNSc-A@mail.gmail.com>
 <86a7i4qztl.fsf_-_@mimuw.edu.pl>
 <CAC+xXWN4xZMz3EtSGGmnQteHqyFnAf8r3LyZaWFsDmOKH-F-qw@mail.gmail.com>
 <86lg1opji6.fsf@mimuw.edu.pl>
 <odu68el3nvngk2tjcaes1ucluc8tcmbnsh@4ax.com>
Message-ID: <861s3gpguw.fsf@mimuw.edu.pl>

On Sat, Mar 09 2019 at 21:40 +13, Stephen Worthington wrote:

[...]

> Mythtv-setup now stores changes section by section (as of
> version0.28?).  So when you go into one section of the setup menu,
> then exit it again, you get the option to save or discard the changes
> you made while in that section.  When you come to exiting completely
> from mythtv-setup, you have already exited from the section where you
> were making changes and it will have stored them (or discarded them if
> you told it to do that).  So when you get the message about problems
> with the storage groups, all the changes you made will have been
> stored already.

This explains why at least sometimes my procedure worked.

>
> When you say it hangs on exit, you need to be bit more specific.  Does
> the GUI screen of mythtv-setup.real go away?  If so, then the "hang"
> was probably happening in the mythtv-setup script that is wrapped
> around mythtv-setup.real.  If the GUI screen was still showing when it
> hung, then the problem is in mythtv-setup.real.

I guess now it was unsuccesfully trying to restart the backend which was
probably still running. When the backend is stopped with systemctl I
exit the setup without any problem.

BTW, I use

systemctl stop mythbackend
systemctl start mythbackend

(no hyphen).

Best regards

Janusz

-- 
             ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

From mkbloke at gmail.com  Sat Mar  9 08:56:34 2019
From: mkbloke at gmail.com (Ian Cameron)
Date: Sat, 9 Mar 2019 08:56:34 +0000
Subject: [mythtv-users] Web Frontend works again
In-Reply-To: <odu68el3nvngk2tjcaes1ucluc8tcmbnsh@4ax.com>
References: <mailman.41.1552061384.1604.mythtv-users@mythtv.org>
 <F6B5415D-4566-44D1-BA9C-3626A3C16A51@tigger.ws>
 <CAC+xXWOhuwR11oHGmt0ri5NnSVUfEsp2owA5uMk9hMN7i3Ca6A@mail.gmail.com>
 <86r2bgshau.fsf@mimuw.edu.pl>
 <CAC+xXWOk9cg+4Hct1Muz4RLw-+ZLo09Cs+zmeGUFpLJcaNSc-A@mail.gmail.com>
 <86a7i4qztl.fsf_-_@mimuw.edu.pl>
 <CAC+xXWN4xZMz3EtSGGmnQteHqyFnAf8r3LyZaWFsDmOKH-F-qw@mail.gmail.com>
 <86lg1opji6.fsf@mimuw.edu.pl> <odu68el3nvngk2tjcaes1ucluc8tcmbnsh@4ax.com>
Message-ID: <CAC+xXWPx0uTeDpqVNs23=idV_rM4E70-JVQRGnxN3soOw5H38A@mail.gmail.com>

On Sat, 9 Mar 2019 at 08:41, Stephen Worthington <stephen_agent at jsw.gen.nz>
wrote:

> Mythtv-setup now stores changes section by section (as of
> version0.28?).  So when you go into one section of the setup menu,
> then exit it again, you get the option to save or discard the changes
> you made while in that section.  When you come to exiting completely
> from mythtv-setup, you have already exited from the section where you
> were making changes and it will have stored them (or discarded them if
> you told it to do that).  So when you get the message about problems
> with the storage groups, all the changes you made will have been
> stored already.
>

Good to know.  I'm on 0.28, but I haven't actually run mythtv-setup for
quite some time now!

Cheers, Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/c066b823/attachment.html>

From kenkyee at yahoo.com  Sat Mar  9 11:11:54 2019
From: kenkyee at yahoo.com (Ken Yee)
Date: Sat, 9 Mar 2019 11:11:54 +0000 (UTC)
Subject: [mythtv-users] 1 min recordings
References: <1311569455.2006670.1552129914913.ref@mail.yahoo.com>
Message-ID: <1311569455.2006670.1552129914913@mail.yahoo.com>

Has anyone seen this before?Tried rebooting everything including the hdhr quad tuner.Tried deleting all tuners and going through the set up process again.Watching TV works fine.I'm puzzled....
Thanks,Ken
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/95a10c7c/attachment.html>

From support at drdos.info  Sat Mar  9 12:39:51 2019
From: support at drdos.info (Doug Lytle)
Date: Sat, 9 Mar 2019 07:39:51 -0500
Subject: [mythtv-users] 1 min recordings
In-Reply-To: <1311569455.2006670.1552129914913@mail.yahoo.com>
References: <1311569455.2006670.1552129914913.ref@mail.yahoo.com>
 <1311569455.2006670.1552129914913@mail.yahoo.com>
Message-ID: <sig.097141c85f.fccff4ae-f2a1-1666-03f9-b4601cd98eee@drdos.info>

On 3/9/19 6:11 AM, Ken Yee wrote:
> Has anyone seen this before?

Myth Backend logs during a recording would be helpful,

Doug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/3079d695/attachment.html>

From barry3martin at gmail.com  Sat Mar  9 15:16:22 2019
From: barry3martin at gmail.com (Barry Martin)
Date: Sat, 9 Mar 2019 09:16:22 -0600
Subject: [mythtv-users] Can't get my projector to work with Myth - HDMI
 Switch
In-Reply-To: <mailman.45.1552104747.1604.mythtv-users@mythtv.org>
References: <mailman.45.1552104747.1604.mythtv-users@mythtv.org>
Message-ID: <6ca03b1e-bac6-2c23-cb74-d1d8734748f5@gmail.com>

Hi Allen!


>>> The switches won't work without a 5v (?) input, which is usually snagged
>>> from an HDMI input; you may need an external DC Input, so either another
>>> wall wart or a charging adapter with multiple 2A outputs.  (Thinking up
>>> here where I have an RPi and HDMI switch, both need power.)
>> I need two outputs and one input and a switch not a splitter but the
> Amazon reviews make me think they will not work with my 30 feet cable to
> the projector.

I'm thinking (read "guessing') this is a "YYMV" situation: quality of 
the cable and the switch, input sensitivity of the projector, etc.?? 
HDMI.org ( https://www.hdmi.org/installers/longcablelengths.aspx ) may 
give your some information.? ...Somewhere when trying to find some other 
information I did see about HDMI cable runs could be up to 50' though 
the cable length in stores was commonly 25'

Here for 'longer' runs I have used the 'booster' HDMI cables; not sure 
how far we can go without getting That Look from the moderators but I 
have purchased from Amazon the 15' length of "Monoprice 109169 Active 
Select Series" and it resolved a problem with a deteriorating signal 
into a 5-output HDMI switch.? ...Must have been due to the video card in 
that computer as another computer in the same cabinet did not need a 
special cable.

The amplified cable uses "RedMere Technology" if that helps any. The 
cable is marked as to which end gets plugged into the computer and which 
to the monitor (to your projector).

HTH!

Barry














-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/27edbf29/attachment.html>

From stephen_agent at jsw.gen.nz  Sat Mar  9 15:49:37 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Sun, 10 Mar 2019 04:49:37 +1300
Subject: [mythtv-users] Can't get my projector to work with Myth - HDMI
 Switch
In-Reply-To: <6ca03b1e-bac6-2c23-cb74-d1d8734748f5@gmail.com>
References: <mailman.45.1552104747.1604.mythtv-users@mythtv.org>
 <6ca03b1e-bac6-2c23-cb74-d1d8734748f5@gmail.com>
Message-ID: <itn78edn36f75cjetkv2c5ajhi1a45gbjm@4ax.com>

On Sat, 9 Mar 2019 09:16:22 -0600, you wrote:

>Hi Allen!
>
>
>>>> The switches won't work without a 5v (?) input, which is usually snagged
>>>> from an HDMI input; you may need an external DC Input, so either another
>>>> wall wart or a charging adapter with multiple 2A outputs.  (Thinking up
>>>> here where I have an RPi and HDMI switch, both need power.)
>>> I need two outputs and one input and a switch not a splitter but the
>> Amazon reviews make me think they will not work with my 30 feet cable to
>> the projector.
>
>I'm thinking (read "guessing') this is a "YYMV" situation: quality of 
>the cable and the switch, input sensitivity of the projector, etc.?? 
>HDMI.org ( https://www.hdmi.org/installers/longcablelengths.aspx ) may 
>give your some information.? ...Somewhere when trying to find some other 
>information I did see about HDMI cable runs could be up to 50' though 
>the cable length in stores was commonly 25'
>
>Here for 'longer' runs I have used the 'booster' HDMI cables; not sure 
>how far we can go without getting That Look from the moderators but I 
>have purchased from Amazon the 15' length of "Monoprice 109169 Active 
>Select Series" and it resolved a problem with a deteriorating signal 
>into a 5-output HDMI switch.? ...Must have been due to the video card in 
>that computer as another computer in the same cabinet did not need a 
>special cable.
>
>The amplified cable uses "RedMere Technology" if that helps any. The 
>cable is marked as to which end gets plugged into the computer and which 
>to the monitor (to your projector).
>
>HTH!
>
>Barry

For longer runs, it is best to get the optical HDMI cables, where
there is an optical transducer at each end powered from the HDMI port,
and an optical fibre between them.  That is also better for the latest
HDMI 2.1 specification, where the bit rates are getting so high that
electrical signaling is getting problematical.

From allen.p.edwards at gmail.com  Sat Mar  9 15:56:32 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Sat, 9 Mar 2019 07:56:32 -0800
Subject: [mythtv-users] Can't get my projector to work with Myth - HDMI
 Switch
In-Reply-To: <6ca03b1e-bac6-2c23-cb74-d1d8734748f5@gmail.com>
References: <mailman.45.1552104747.1604.mythtv-users@mythtv.org>
 <6ca03b1e-bac6-2c23-cb74-d1d8734748f5@gmail.com>
Message-ID: <CAH8UtKNfyFd8WQoecYjj4mkJOaPbvcVjSthAozbGmdV0vB+APw@mail.gmail.com>

On Sat, Mar 9, 2019 at 7:16 AM Barry Martin <barry3martin at gmail.com> wrote:

> Hi Allen!
>
>
> The switches won't work without a 5v (?) input, which is usually snagged
> from an HDMI input; you may need an external DC Input, so either another
> wall wart or a charging adapter with multiple 2A outputs.  (Thinking up
> here where I have an RPi and HDMI switch, both need power.)
>
> I need two outputs and one input and a switch not a splitter but the
>
> Amazon reviews make me think they will not work with my 30 feet cable to
> the projector.
>
> I'm thinking (read "guessing') this is a "YYMV" situation: quality of the
> cable and the switch, input sensitivity of the projector, etc.   HDMI.org
> (   https://www.hdmi.org/installers/longcablelengths.aspx ) may give your
> some information.  ...Somewhere when trying to find some other information
> I did see about HDMI cable runs could be up to 50' though the cable length
> in stores was commonly 25'
>
> Here for 'longer' runs I have used the 'booster' HDMI cables; not sure how
> far we can go without getting That Look from the moderators but I have
> purchased from Amazon the 15' length of "Monoprice 109169 Active Select
> Series" and it resolved a problem with a deteriorating signal into a
> 5-output HDMI switch.  ...Must have been due to the video card in that
> computer as another computer in the same cabinet did not need a special
> cable.
>
> The amplified cable uses "RedMere Technology" if that helps any.  The
> cable is marked as to which end gets plugged into the computer and which to
> the monitor (to your projector).
>
> HTH!
>
> Barry
>
The cable is probably more like 40 feet but it is a very good cable.  I
just measured the OD and it is half an inch or about twice the diameter of
a cheap HDMI cable. I have used this cable with this projector for at least
10 years and it works fine. It is important to drive it with enough power.
I have a splitter that I used to use that I am sure will drive it if I see
issues.  That splitter is a DVI splitter. If I wanted to go back to driving
the TV with 720p I would put it back in and see if it passed audio. At this
point, I will just move the cables manually unless someone knows of a
switch that will work.  We don't use the projector for Myth very often
anyway.

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/2da37ca7/attachment.html>

From allen.p.edwards at gmail.com  Sat Mar  9 17:46:50 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Sat, 9 Mar 2019 09:46:50 -0800
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <CAC+xXWNnoCBww4hN=SKG8-b53ZzwQHmfczzKAUMvdrXKTMMtEw@mail.gmail.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
 <mc458eppr7ac2mn6aqfeuefvn19ku9r1kd@4ax.com>
 <CAH8UtKN64enW_46mYe-v84CzWex5Rf0Ze88yqVmMGM9J4yoVVg@mail.gmail.com>
 <CAH8UtKN0CfTSFJmrMfHd_4r5BGwEmGpU=pinX9P+oEBoyFPn6g@mail.gmail.com>
 <CAH8UtKMMy59LdC75G_QVu-K-1QvbJ+OJQbfaX6ogDCpGszj-Kw@mail.gmail.com>
 <CAC+xXWMqmtPDPcwRBRX90fBBdq1TiLoBfsAgCzXD1uqR8UdAEg@mail.gmail.com>
 <CAH8UtKPETMJvemwZAzWgORg7X2zAsX5nyAQFV5Q4JYaP7A51iA@mail.gmail.com>
 <CAC+xXWNnoCBww4hN=SKG8-b53ZzwQHmfczzKAUMvdrXKTMMtEw@mail.gmail.com>
Message-ID: <CAH8UtKPi8+RreKdm1oR+hx+j9A86PP4sb5xyStxETjM1WCGv5Q@mail.gmail.com>

Ian, thanks. That fixed the login problem but maybe there is another bug.

I still am getting multiple mythfrontend.real running after CTRL-ALT-BS.
That is really strange. I did CTRL-ALT-BS ten times and had 9 instances of
mythfrontend running. Looks like mythfrontend.real either is not killed or
restarts after it is killed

lightdm.conf now looks like this

*dad at NewMyth:~$ more /etc/lightdm/lightdm.conf*
*[SeatDefaults]*
*display-stopped-script=pkill lightdm*
*user-session=mythbuntu*
*allow-guest=false*
*#autologin-user=*
*[Seat:*]*
*autologin-guest=false*
*autologin-user=dad*
*autologin-user-timeout=0*

I am running 28.2+fixes

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/8556d798/attachment.html>

From mtusers at dorscm.wakeful.net  Sat Mar  9 19:02:38 2019
From: mtusers at dorscm.wakeful.net (Matt Dorsch)
Date: Sat, 9 Mar 2019 14:02:38 -0500
Subject: [mythtv-users] HDHomeRun card type removed?
Message-ID: <CAFWmYv0wo7jtF68dxuriibE-bXttaJhTwLzYj9ztpvuR8K0LYw@mail.gmail.com>

Howdy,

I just upgraded to mythtv-backend-30.0-1.20190214gitb774c4140b.fc29.x86_64
on a Fedora 29 system. It appears to no longer recognize the HDHomeRun card
type. I've been using HDHomeRuns with this MythTV backend installation for
7 years.

>From the backend log:
--------------------------------------------------
2019-03-09 13:21:16.136535 E [5166/5166] CoreContext
recorders/channelbase.cpp:789 (CreateChannel) - ChannelBase:
CreateChannel() Error:
HDHOMERUN card configured on video device 10207E74,
but MythTV was not compiled with HDHOMERUN support.

Recompile MythTV with HDHOMERUN support or remove the card
from the configuration and restart MythTV.

2019-03-09 13:21:16.136570 E [5166/5166] CoreContext main_helpers.cpp:205
(setupTVs) - Problem with capture cards. Card 1 failed init
---------------------------------------------------

If I go into mythtv backend setup and try to add a new card, no card type
contains the text "HDHOMERUN".

Is this a build mistake, or do I need to switch tuners or DVR software?

I built and installed the latest libhdhomerun.so from source.

Thanks,
Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/78220899/attachment.html>

From stse+mythtv at fsing.rootsland.net  Sat Mar  9 19:47:03 2019
From: stse+mythtv at fsing.rootsland.net (Stephan Seitz)
Date: Sat, 9 Mar 2019 20:47:03 +0100
Subject: [mythtv-users] No DVB-C channels anymore
In-Reply-To: <2453204.rat3DMXqDE@delle>
References: <20190228T183358.GA.590a9.stse@fsing.rootsland.net>
 <2453204.rat3DMXqDE@delle>
Message-ID: <20190309T204458.GA.3b40d.stse@fsing.rootsland.net>

On Mi, M?r 06, 2019 at 11:47:03 +0100, Jan Hambrecht wrote:
>If you are on myth v30 then ticket #13014 might be relevant.
>See https://code.mythtv.org/trac/ticket/13014 for details, comment #9 is the
>interesting thing regarding the latest release.

Thank you very much! Yes, that?s the problem. Together with the patch and 
the dvb-fe-tools I have DVB-C channels again.

Shade and sweet water!

	Stephan


-- 
| Public Keys: http://fsing.rootsland.net/~stse/keys.html |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3545 bytes
Desc: not available
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/41caf7de/attachment.p7s>

From johnpilk222 at gmail.com  Sat Mar  9 19:58:06 2019
From: johnpilk222 at gmail.com (John Pilkington)
Date: Sat, 9 Mar 2019 19:58:06 +0000
Subject: [mythtv-users] HDHomeRun card type removed?
In-Reply-To: <CAFWmYv0wo7jtF68dxuriibE-bXttaJhTwLzYj9ztpvuR8K0LYw@mail.gmail.com>
References: <CAFWmYv0wo7jtF68dxuriibE-bXttaJhTwLzYj9ztpvuR8K0LYw@mail.gmail.com>
Message-ID: <ee1f05bf-cf36-f63a-a16f-c4c2195b52f5@gmail.com>

On 09/03/2019 19:02, Matt Dorsch wrote:
> Howdy,
> 
> I just upgraded to 
> mythtv-backend-30.0-1.20190214gitb774c4140b.fc29.x86_64 on a Fedora 29 
> system. It appears to no longer recognize the HDHomeRun card type. I've 
> been using HDHomeRuns with this MythTV backend installation for 7 years.
> 

This may now be out-of-date, but it's in the archive

  http://lists.mythtv.org/pipermail/mythtv-users/2019-March/399786.html

John P

From allen.p.edwards at gmail.com  Sat Mar  9 20:00:01 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Sat, 9 Mar 2019 12:00:01 -0800
Subject: [mythtv-users] CTRL-ALT-BACKSPACE
In-Reply-To: <CAC+xXWNnoCBww4hN=SKG8-b53ZzwQHmfczzKAUMvdrXKTMMtEw@mail.gmail.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
 <mc458eppr7ac2mn6aqfeuefvn19ku9r1kd@4ax.com>
 <CAH8UtKN64enW_46mYe-v84CzWex5Rf0Ze88yqVmMGM9J4yoVVg@mail.gmail.com>
 <CAH8UtKN0CfTSFJmrMfHd_4r5BGwEmGpU=pinX9P+oEBoyFPn6g@mail.gmail.com>
 <CAH8UtKMMy59LdC75G_QVu-K-1QvbJ+OJQbfaX6ogDCpGszj-Kw@mail.gmail.com>
 <CAC+xXWMqmtPDPcwRBRX90fBBdq1TiLoBfsAgCzXD1uqR8UdAEg@mail.gmail.com>
 <CAH8UtKPETMJvemwZAzWgORg7X2zAsX5nyAQFV5Q4JYaP7A51iA@mail.gmail.com>
 <CAC+xXWNnoCBww4hN=SKG8-b53ZzwQHmfczzKAUMvdrXKTMMtEw@mail.gmail.com>
Message-ID: <CAH8UtKP=VaS+uwMCDKJE9e_Nk1Q3VOybzg6arwoL3NWkfje9fA@mail.gmail.com>

On Fri, Mar 8, 2019 at 10:22 PM Ian Cameron <mkbloke at gmail.com> wrote:

> On Sat, 9 Mar 2019 at 05:48, Allen Edwards <allen.p.edwards at gmail.com>
> wrote:
>
>> I guess I deleted too much of the first text I wrote.  I do have
>> autostart set and when I power up Myth starts without any prompt. I only
>> get the prompt on restart from my new CTRL-ALT-Backspace key sequence.
>>
>
> From what I can see, this is designed-in behaviour on the part of LightDM,
> as per:
>
> https://bugs.launchpad.net/lightdm/+bug/1396824
>
> The solution there is probably your best bet for trying next, i.e. adding:
>
> display-stopped-script=pkill lightdm
>
> to the SeatDefaults section of lightdm.conf
>
> Cheers, Ian
>

I changed the subject line in my replay so maybe that started a new
thread.  Just wanted to reply in this thread and say thanks that fixed the
logon problem but I still have the multiple instances of mythfrontene.real
running.

Almost every time I do my CTRL-ALT-BS test without me killing myth I get a
new instance of mythfrontend.real.  I did 10 tests and had 9 mythfrontends
running.

The other thread has more information. If I violated protocol, I apologize.
I wasn't sure what was best.

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/ccd4203b/attachment.html>

From hobbes1069 at gmail.com  Sat Mar  9 20:14:37 2019
From: hobbes1069 at gmail.com (Richard Shaw)
Date: Sat, 9 Mar 2019 14:14:37 -0600
Subject: [mythtv-users] HDHomeRun card type removed?
In-Reply-To: <CAFWmYv0wo7jtF68dxuriibE-bXttaJhTwLzYj9ztpvuR8K0LYw@mail.gmail.com>
References: <CAFWmYv0wo7jtF68dxuriibE-bXttaJhTwLzYj9ztpvuR8K0LYw@mail.gmail.com>
Message-ID: <CAN3TeO28Vvz6+sKE42jvWfidhKjqY9+KPnWmkiqCqqezxwqJsQ@mail.gmail.com>

On Sat, Mar 9, 2019 at 1:04 PM Matt Dorsch <mtusers at dorscm.wakeful.net>
wrote:

> Howdy,
>
> I just upgraded to mythtv-backend-30.0-1.20190214gitb774c4140b.fc29.x86_64
> on a Fedora 29 system. It appears to no longer recognize the HDHomeRun card
> type. I've been using HDHomeRuns with this MythTV backend installation for
> 7 years.
>

It was an oops on my end. There were a number of changes with v30 and the
hdhomerun library is no longer bundled as of v30. The current packages at
RPM Fusion are now fixed.

Thanks,
Richard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/da52b5cc/attachment.html>

From mtusers at dorscm.wakeful.net  Sat Mar  9 20:34:47 2019
From: mtusers at dorscm.wakeful.net (Matt Dorsch)
Date: Sat, 9 Mar 2019 15:34:47 -0500
Subject: [mythtv-users] HDHomeRun card type removed?
In-Reply-To: <CAN3TeO28Vvz6+sKE42jvWfidhKjqY9+KPnWmkiqCqqezxwqJsQ@mail.gmail.com>
References: <CAFWmYv0wo7jtF68dxuriibE-bXttaJhTwLzYj9ztpvuR8K0LYw@mail.gmail.com>
 <CAN3TeO28Vvz6+sKE42jvWfidhKjqY9+KPnWmkiqCqqezxwqJsQ@mail.gmail.com>
Message-ID: <CAFWmYv0gh_e5F9WYZgTKW91K2h_9pEv=kv7BXcD6BiUtsnsPEA@mail.gmail.com>

Yes, that was it. Apologies for duplicating Jerry's question from
Wednesday: I tried including the site: feature in the web search, but
neither duckduckgo nor google have scanned the mythtv-users archive since
then.

Thanks!
Matt

On Sat, Mar 9, 2019 at 3:14 PM Richard Shaw <hobbes1069 at gmail.com> wrote:

> On Sat, Mar 9, 2019 at 1:04 PM Matt Dorsch <mtusers at dorscm.wakeful.net>
> wrote:
>
>> Howdy,
>>
>> I just upgraded to
>> mythtv-backend-30.0-1.20190214gitb774c4140b.fc29.x86_64 on a Fedora 29
>> system. It appears to no longer recognize the HDHomeRun card type. I've
>> been using HDHomeRuns with this MythTV backend installation for 7 years.
>>
>
> It was an oops on my end. There were a number of changes with v30 and the
> hdhomerun library is no longer bundled as of v30. The current packages at
> RPM Fusion are now fixed.
>
> Thanks,
> Richard
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/e987cd37/attachment.html>

From allen.p.edwards at gmail.com  Sat Mar  9 21:20:42 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Sat, 9 Mar 2019 13:20:42 -0800
Subject: [mythtv-users] CTRL-ALT-BACKSPACE
In-Reply-To: <lda68e9mgcbjblhasnd26gob31df4b02fa@4ax.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
 <mc458eppr7ac2mn6aqfeuefvn19ku9r1kd@4ax.com>
 <CAH8UtKN64enW_46mYe-v84CzWex5Rf0Ze88yqVmMGM9J4yoVVg@mail.gmail.com>
 <CAH8UtKN0CfTSFJmrMfHd_4r5BGwEmGpU=pinX9P+oEBoyFPn6g@mail.gmail.com>
 <lda68e9mgcbjblhasnd26gob31df4b02fa@4ax.com>
Message-ID: <CAH8UtKPWM+JD4h40m0io8JKST6hnRbSfJBrjnKNzNbj0W6BA6g@mail.gmail.com>

On Fri, Mar 8, 2019 at 6:57 PM Stephen Worthington <stephen_agent at jsw.gen.nz>
wrote:

> One alternative is to use lirc to assign a button on your remote to
> kill mythfrontend.real.  Lirc can be set up to run scripts using
> irexec.  The script would do a ps -e and find any running copies of
> mythbackend.real and kill them.  Then the mythfrontend script would
> see that mythfrontend.real had died and would restart it.
>

Stephen
I have tried this without success.  Here is what I did.
1) I modified a key definition to run irexec and change a key definition to
escape
2) I verified that the key was now the escape key
3) I changed the config action to "killall mythfrontend.real"
4) The key did nothing. Myth did not close and the pid did not change
5) I copied the config action to a terminal and it killed mythfrontend

By the way, myth does not restart when I kill it.

This is not exactly what you told me to do but it seemed like it should
work.

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/dc50c89e/attachment.html>

From allen.p.edwards at gmail.com  Sat Mar  9 22:17:50 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Sat, 9 Mar 2019 14:17:50 -0800
Subject: [mythtv-users] CTRL-ALT-BACKSPACE
In-Reply-To: <CAH8UtKPWM+JD4h40m0io8JKST6hnRbSfJBrjnKNzNbj0W6BA6g@mail.gmail.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
 <mc458eppr7ac2mn6aqfeuefvn19ku9r1kd@4ax.com>
 <CAH8UtKN64enW_46mYe-v84CzWex5Rf0Ze88yqVmMGM9J4yoVVg@mail.gmail.com>
 <CAH8UtKN0CfTSFJmrMfHd_4r5BGwEmGpU=pinX9P+oEBoyFPn6g@mail.gmail.com>
 <lda68e9mgcbjblhasnd26gob31df4b02fa@4ax.com>
 <CAH8UtKPWM+JD4h40m0io8JKST6hnRbSfJBrjnKNzNbj0W6BA6g@mail.gmail.com>
Message-ID: <CAH8UtKNk46ouEep7EB7RcL_SNMiTLpuQ+cBGgCtKzwtu+CwLaw@mail.gmail.com>

Correction: What I did was verify that I could change a key and test it,
then put an action that I verified would kill mythfrontend in and set the
key to irexec. Didn't do anything.

On Sat, Mar 9, 2019 at 1:20 PM Allen Edwards <allen.p.edwards at gmail.com>
wrote:

>
>
> On Fri, Mar 8, 2019 at 6:57 PM Stephen Worthington <
> stephen_agent at jsw.gen.nz> wrote:
>
>> One alternative is to use lirc to assign a button on your remote to
>> kill mythfrontend.real.  Lirc can be set up to run scripts using
>> irexec.  The script would do a ps -e and find any running copies of
>> mythbackend.real and kill them.  Then the mythfrontend script would
>> see that mythfrontend.real had died and would restart it.
>>
>
>
Stephen
I have tried this without success.  Here is what I did.
1) I modified a key config action to escape
2) I verified that the key was now the escape key
3) I  modified the same key definition to run irexec and changed the config
action to "killall mythfrontend.real"
4) The key did nothing. Myth did not close and the pid did not change
5) I copied the config action to a terminal and it killed mythfrontend

By the way, myth does not restart when I kill it.

This is not exactly what you told me to do but it seemed like it should
work.

Allen
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/c6c7e694/attachment.html>

From allen.p.edwards at gmail.com  Sat Mar  9 23:01:27 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Sat, 9 Mar 2019 15:01:27 -0800
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <CAH8UtKPi8+RreKdm1oR+hx+j9A86PP4sb5xyStxETjM1WCGv5Q@mail.gmail.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
 <mc458eppr7ac2mn6aqfeuefvn19ku9r1kd@4ax.com>
 <CAH8UtKN64enW_46mYe-v84CzWex5Rf0Ze88yqVmMGM9J4yoVVg@mail.gmail.com>
 <CAH8UtKN0CfTSFJmrMfHd_4r5BGwEmGpU=pinX9P+oEBoyFPn6g@mail.gmail.com>
 <CAH8UtKMMy59LdC75G_QVu-K-1QvbJ+OJQbfaX6ogDCpGszj-Kw@mail.gmail.com>
 <CAC+xXWMqmtPDPcwRBRX90fBBdq1TiLoBfsAgCzXD1uqR8UdAEg@mail.gmail.com>
 <CAH8UtKPETMJvemwZAzWgORg7X2zAsX5nyAQFV5Q4JYaP7A51iA@mail.gmail.com>
 <CAC+xXWNnoCBww4hN=SKG8-b53ZzwQHmfczzKAUMvdrXKTMMtEw@mail.gmail.com>
 <CAH8UtKPi8+RreKdm1oR+hx+j9A86PP4sb5xyStxETjM1WCGv5Q@mail.gmail.com>
Message-ID: <CAH8UtKMWhPZq_bqniouSj3OGWbrAQUs-Lqo2R4UTJwMrodn9fQ@mail.gmail.com>

On Sat, Mar 9, 2019 at 9:46 AM Allen Edwards <allen.p.edwards at gmail.com>
wrote:

> Ian, thanks. That fixed the login problem but maybe there is another bug.
>
> I still am getting multiple mythfrontend.real running after CTRL-ALT-BS.
> That is really strange. I did CTRL-ALT-BS ten times and had 9 instances of
> mythfrontend running. Looks like mythfrontend.real either is not killed or
> restarts after it is killed
>
> lightdm.conf now looks like this
>
> *dad at NewMyth:~$ more /etc/lightdm/lightdm.conf*
> *[SeatDefaults]*
> *display-stopped-script=pkill lightdm*
> *user-session=mythbuntu*
> *allow-guest=false*
> *#autologin-user=*
> *[Seat:*]*
> *autologin-guest=false*
> *autologin-user=dad*
> *autologin-user-timeout=0*
>
> I am running 28.2+fixes
>
> Allen
>

I did CTRL-ALT-BS twice so that there were three instances of mythfrontend
running.
I looked in the log and I see three of these lines differing only by
timestamp.  There are some lines before and after but all three of these
look to happen fairly quickly.
*Mar  9 13:53:45 NewMyth mythfrontend.real: mythfrontend[3221]: C
thread_unknown mythcommandlineparser.cpp:2599 (ConfigureLogging)
mythfrontend version: fixes/0.28 [v0.28.2-6-g9031599] www.mythtv.org
<http://www.mythtv.org>*

For whatever reason, mythfrontend is getting started one more time than it
was last time.  Whatever is responsible for starting myth is not getting
killed when I kill X.

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/740e6ee8/attachment.html>

From mkbloke at gmail.com  Sun Mar 10 00:34:30 2019
From: mkbloke at gmail.com (Ian Cameron)
Date: Sun, 10 Mar 2019 00:34:30 +0000
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <CAH8UtKMWhPZq_bqniouSj3OGWbrAQUs-Lqo2R4UTJwMrodn9fQ@mail.gmail.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
 <mc458eppr7ac2mn6aqfeuefvn19ku9r1kd@4ax.com>
 <CAH8UtKN64enW_46mYe-v84CzWex5Rf0Ze88yqVmMGM9J4yoVVg@mail.gmail.com>
 <CAH8UtKN0CfTSFJmrMfHd_4r5BGwEmGpU=pinX9P+oEBoyFPn6g@mail.gmail.com>
 <CAH8UtKMMy59LdC75G_QVu-K-1QvbJ+OJQbfaX6ogDCpGszj-Kw@mail.gmail.com>
 <CAC+xXWMqmtPDPcwRBRX90fBBdq1TiLoBfsAgCzXD1uqR8UdAEg@mail.gmail.com>
 <CAH8UtKPETMJvemwZAzWgORg7X2zAsX5nyAQFV5Q4JYaP7A51iA@mail.gmail.com>
 <CAC+xXWNnoCBww4hN=SKG8-b53ZzwQHmfczzKAUMvdrXKTMMtEw@mail.gmail.com>
 <CAH8UtKPi8+RreKdm1oR+hx+j9A86PP4sb5xyStxETjM1WCGv5Q@mail.gmail.com>
 <CAH8UtKMWhPZq_bqniouSj3OGWbrAQUs-Lqo2R4UTJwMrodn9fQ@mail.gmail.com>
Message-ID: <CAC+xXWO+PuLxdv=dA6phSdYxMGVKHy92NzZ4UQjVopQGV8wndg@mail.gmail.com>

On Sat, 9 Mar 2019 at 23:03, Allen Edwards <allen.p.edwards at gmail.com>
wrote:

>
>
> On Sat, Mar 9, 2019 at 9:46 AM Allen Edwards <allen.p.edwards at gmail.com>
> wrote:
>
>> I still am getting multiple mythfrontend.real running after CTRL-ALT-BS.
>> That is really strange. I did CTRL-ALT-BS ten times and had 9 instances of
>> mythfrontend running. Looks like mythfrontend.real either is not killed or
>> restarts after it is killed
>>
>> lightdm.conf now looks like this
>>
>> *dad at NewMyth:~$ more /etc/lightdm/lightdm.conf*
>> *[SeatDefaults]*
>> *display-stopped-script=pkill lightdm*
>> *user-session=mythbuntu*
>> *allow-guest=false*
>> *#autologin-user=*
>> *[Seat:*]*
>> *autologin-guest=false*
>> *autologin-user=dad*
>> *autologin-user-timeout=0*
>>
>> I am running 28.2+fixes
>>
>> Allen
>>
>
> I did CTRL-ALT-BS twice so that there were three instances of mythfrontend
> running.
> I looked in the log and I see three of these lines differing only by
> timestamp.  There are some lines before and after but all three of these
> look to happen fairly quickly.
> *Mar  9 13:53:45 NewMyth mythfrontend.real: mythfrontend[3221]: C
> thread_unknown mythcommandlineparser.cpp:2599 (ConfigureLogging)
> mythfrontend version: fixes/0.28 [v0.28.2-6-g9031599] www.mythtv.org
> <http://www.mythtv.org>*
>
> For whatever reason, mythfrontend is getting started one more time than it
> was last time.  Whatever is responsible for starting myth is not getting
> killed when I kill X.
>

I guess the solution will be to test whether or not it's already running
before trying to start it.

Assuming that it's launched via a wrapper called mythfrontend that is in
located in a system bin directory accessible via $PATH, but appears in ps
output as mythfrontend.real, the following will test to see if it's already
running and start it if not:

bash -c "ps -ef | grep '[m]ythfrontend\.real' 2>&1 > /dev/null || exec
mythfrontend"

The question now is where to put the above.  I don't have a Mythbuntu
installation to look at, but if you can locate where the front-end is
started from and replace it with the above, then hopefully that will fix
things.

Cheers, Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190310/071d5a92/attachment.html>

From allen.p.edwards at gmail.com  Sun Mar 10 00:53:55 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Sat, 9 Mar 2019 16:53:55 -0800
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <CAC+xXWO+PuLxdv=dA6phSdYxMGVKHy92NzZ4UQjVopQGV8wndg@mail.gmail.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
 <mc458eppr7ac2mn6aqfeuefvn19ku9r1kd@4ax.com>
 <CAH8UtKN64enW_46mYe-v84CzWex5Rf0Ze88yqVmMGM9J4yoVVg@mail.gmail.com>
 <CAH8UtKN0CfTSFJmrMfHd_4r5BGwEmGpU=pinX9P+oEBoyFPn6g@mail.gmail.com>
 <CAH8UtKMMy59LdC75G_QVu-K-1QvbJ+OJQbfaX6ogDCpGszj-Kw@mail.gmail.com>
 <CAC+xXWMqmtPDPcwRBRX90fBBdq1TiLoBfsAgCzXD1uqR8UdAEg@mail.gmail.com>
 <CAH8UtKPETMJvemwZAzWgORg7X2zAsX5nyAQFV5Q4JYaP7A51iA@mail.gmail.com>
 <CAC+xXWNnoCBww4hN=SKG8-b53ZzwQHmfczzKAUMvdrXKTMMtEw@mail.gmail.com>
 <CAH8UtKPi8+RreKdm1oR+hx+j9A86PP4sb5xyStxETjM1WCGv5Q@mail.gmail.com>
 <CAH8UtKMWhPZq_bqniouSj3OGWbrAQUs-Lqo2R4UTJwMrodn9fQ@mail.gmail.com>
 <CAC+xXWO+PuLxdv=dA6phSdYxMGVKHy92NzZ4UQjVopQGV8wndg@mail.gmail.com>
Message-ID: <CAH8UtKMdnh3EVCRqe+UQ9BV5Akc+8VZ9MD4Pn-REx5yqGaLBaA@mail.gmail.com>

On Sat, Mar 9, 2019 at 4:35 PM Ian Cameron <mkbloke at gmail.com> wrote:

> On Sat, 9 Mar 2019 at 23:03, Allen Edwards <allen.p.edwards at gmail.com>
> wrote:
>
>>
>>
>> On Sat, Mar 9, 2019 at 9:46 AM Allen Edwards <allen.p.edwards at gmail.com>
>> wrote:
>>
>>> I still am getting multiple mythfrontend.real running after
>>> CTRL-ALT-BS.  That is really strange. I did CTRL-ALT-BS ten times and had 9
>>> instances of mythfrontend running. Looks like mythfrontend.real either is
>>> not killed or restarts after it is killed
>>>
>>> lightdm.conf now looks like this
>>>
>>> *dad at NewMyth:~$ more /etc/lightdm/lightdm.conf*
>>> *[SeatDefaults]*
>>> *display-stopped-script=pkill lightdm*
>>> *user-session=mythbuntu*
>>> *allow-guest=false*
>>> *#autologin-user=*
>>> *[Seat:*]*
>>> *autologin-guest=false*
>>> *autologin-user=dad*
>>> *autologin-user-timeout=0*
>>>
>>> I am running 28.2+fixes
>>>
>>> Allen
>>>
>>
>> I did CTRL-ALT-BS twice so that there were three instances of
>> mythfrontend running.
>> I looked in the log and I see three of these lines differing only by
>> timestamp.  There are some lines before and after but all three of these
>> look to happen fairly quickly.
>> *Mar  9 13:53:45 NewMyth mythfrontend.real: mythfrontend[3221]: C
>> thread_unknown mythcommandlineparser.cpp:2599 (ConfigureLogging)
>> mythfrontend version: fixes/0.28 [v0.28.2-6-g9031599] www.mythtv.org
>> <http://www.mythtv.org>*
>>
>> For whatever reason, mythfrontend is getting started one more time than
>> it was last time.  Whatever is responsible for starting myth is not getting
>> killed when I kill X.
>>
>
> I guess the solution will be to test whether or not it's already running
> before trying to start it.
>
> Assuming that it's launched via a wrapper called mythfrontend that is in
> located in a system bin directory accessible via $PATH, but appears in ps
> output as mythfrontend.real, the following will test to see if it's already
> running and start it if not:
>
> bash -c "ps -ef | grep '[m]ythfrontend\.real' 2>&1 > /dev/null || exec
> mythfrontend"
>
> The question now is where to put the above.  I don't have a Mythbuntu
> installation to look at, but if you can locate where the front-end is
> started from and replace it with the above, then hopefully that will fix
> things.
>
> Cheers, Ian
>

I have been reading scripts all day trying to find where that happens.  I
assume there is somewhere I can look and find what script is actually
called.  Any idea where that is?

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/6c729f4e/attachment.html>

From jam at tigger.ws  Sun Mar 10 00:55:45 2019
From: jam at tigger.ws (James Linder)
Date: Sun, 10 Mar 2019 08:55:45 +0800
Subject: [mythtv-users] Web Frontend stopped working yesterday
In-Reply-To: <mailman.48.1552146592.1604.mythtv-users@mythtv.org>
References: <mailman.48.1552146592.1604.mythtv-users@mythtv.org>
Message-ID: <A6570CDE-DC7D-4CCC-993D-951FC1F337E8@tigger.ws>



> On 9 Mar 2019, at 11:49 pm, mythtv-users-request at mythtv.org wrote:
> 
>> 6. Now none of your machines (on a trusted network ie you trust everyone) need a firewall (1)
> 
> Irrelevant.
> 

Janusz

unless you describe your setup the best attempts to help you are doomed.
For example no usual setup would have the ISP able to change the IP of your myth machines.
For you either
The www server part of mythbackend is not running
or
firewalls are preventing you from seeing the server
in which case the whole firewall concern is not irrelevant.

I think that you are being secretive about your setup and agressive to offers of help. Sorry you feel that way
James 

From stephen_agent at jsw.gen.nz  Sun Mar 10 02:38:47 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Sun, 10 Mar 2019 15:38:47 +1300
Subject: [mythtv-users] CTRL-ALT-BACKSPACE
In-Reply-To: <CAH8UtKNk46ouEep7EB7RcL_SNMiTLpuQ+cBGgCtKzwtu+CwLaw@mail.gmail.com>
References: <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
 <mc458eppr7ac2mn6aqfeuefvn19ku9r1kd@4ax.com>
 <CAH8UtKN64enW_46mYe-v84CzWex5Rf0Ze88yqVmMGM9J4yoVVg@mail.gmail.com>
 <CAH8UtKN0CfTSFJmrMfHd_4r5BGwEmGpU=pinX9P+oEBoyFPn6g@mail.gmail.com>
 <lda68e9mgcbjblhasnd26gob31df4b02fa@4ax.com>
 <CAH8UtKPWM+JD4h40m0io8JKST6hnRbSfJBrjnKNzNbj0W6BA6g@mail.gmail.com>
 <CAH8UtKNk46ouEep7EB7RcL_SNMiTLpuQ+cBGgCtKzwtu+CwLaw@mail.gmail.com>
Message-ID: <foq88e5milg1bhl2cq2gj93bd4f59079e6@4ax.com>

On Sat, 9 Mar 2019 14:17:50 -0800, you wrote:

>On Sat, Mar 9, 2019 at 1:20 PM Allen Edwards <allen.p.edwards at gmail.com>
>wrote:
>
>>
>>
>> On Fri, Mar 8, 2019 at 6:57 PM Stephen Worthington <
>> stephen_agent at jsw.gen.nz> wrote:
>>
>>> One alternative is to use lirc to assign a button on your remote to
>>> kill mythfrontend.real.  Lirc can be set up to run scripts using
>>> irexec.  The script would do a ps -e and find any running copies of
>>> mythbackend.real and kill them.  Then the mythfrontend script would
>>> see that mythfrontend.real had died and would restart it.
>>>
>>
>>
>Stephen
>I have tried this without success.  Here is what I did.
>1) I modified a key config action to escape
>2) I verified that the key was now the escape key
>3) I  modified the same key definition to run irexec and changed the config
>action to "killall mythfrontend.real"
>4) The key did nothing. Myth did not close and the pid did not change
>5) I copied the config action to a terminal and it killed mythfrontend
>
>By the way, myth does not restart when I kill it.
>
>This is not exactly what you told me to do but it seemed like it should
>work.

>Correction: What I did was verify that I could change a key and test it,
>then put an action that I verified would kill mythfrontend in and set the
>key to irexec. Didn't do anything.

Lirc runs irexec, not a key setting in MythTV.  In /home/<mythfrontend
user>, you should find a file .lircrc that looks something like this:

root at mypvr:/home/stephen# cat .lircrc
#Custom lircrc generated via mythbuntu-lirc-generator
#All application specific lircrc files are within ~/.lirc
include ~/.lirc/mythtv
include ~/.lirc/mplayer
include ~/.lirc/xine
include ~/.lirc/vlc
include ~/.lirc/xmame
include ~/.lirc/xmess
include ~/.lirc/totem
include ~/.lirc/elisa
include ~/.lirc/irexec

That is the file that lirc loads by default to set up all its
keystrokes.  By convention, a separate file is used for the setup for
each program that uses lirc, but the actual specification of the
programs is done on the "prog =" lines inside those files, so you can
mix setting for different programs in one lirc config file if you
like.  My remote is using the devinput driver, so for a lirc key
config to do anything, it needs a "remote = devinput" line.  Here are
the first three key configs in my /home/stephen/.lirc/mythtv file:

begin
    remote = devinput
    prog = mythtv
             # Guide key
    button = KEY_EPG
#    config = S
    config = Ctrl+Alt+G
    repeat = 0
    delay = 0
end

begin
    remote = devinput
    prog = mythtv
    button = KEY_EXIT
    config = Escape
    repeat = 0
    delay = 0
end

begin
    remote = devinput
    prog = mythtv
    button = KEY_OK
    config = Return
    repeat = 0
    delay = 0
end

begin
    remote = devinput
    prog = mythtv
    button = KEY_RIGHT
    config = Right
    repeat = 1
    delay = 1
end

So what the first one of those does is to say that when lirc receives
a KEY_EPG input from the devinput driver, then if the program with the
lirc name "mythtv" is attached to lirc at the time, it should send a
Ctrl-Alt-G keystroke to that program.  Then inside mythfrontend (which
is running with the lirc name "mythtv"), it will receive the
Ctrl-Alt-G keystroke, look up its keystroke configs from the database
and see that (in my setup) it should jump directly to the Programme
Guide:

MariaDB [mythconverg]> select * from jumppoints where keylist like
'%alt+g%';
+---------------+-------------+------------+----------+
| destination   | description | keylist    | hostname |
+---------------+-------------+------------+----------+
| Program Guide | NULL        | Ctrl+Alt+G | mypvr    |
+---------------+-------------+------------+----------+
1 row in set (0.00 sec)


Here is an example with irexec:

begin
    remote = devinput
    prog = irexec
    button = KEY_YELLOW
    config = echo "This is the Yellow key"
    repeat = 0
    delay = 0
end

What that does is when a KEY_YELLOW (teletext key) keystroke is
received from the devinput driver, then if irexec is running and
attached to lirc, then send irexec the keys in the "config =" line. So
irexec will receive a line of text containing the echo command, which
it will then execute.  For this to do anything, you need to be running
irexec in the background as the same user that mythfrontend runs from.
I think you said you are running Ubuntu 16.04, so the best way to run
irexxec there is from systemd.  But the lirc package in 16.04 does not
set that up for you.  In 18.04 the package installs a
/lib/systemd/system/irexec.service file for you to modify to make this
work:

root at mypvr:/lib/systemd/system# cat irexec.service
[Unit]
Documentation=man:irexec(1)
Documentation=http://lirc.org/html/configure.html
Documentation=http://lirc.org/html/configure.html#lircrc_format
Description=Handle events from IR remotes decoded by lircd(8)

[Service]
; user=lirc
; group=lirc

; Hardening opts, see systemd.exec(5).  Doesn't add much unless
; not running as root. If these are applicable or not depends on
; what commands irexec.lircrc invokes.
;
; NoNewPrivileges=true
; MemoryDenyWriteExecute=true
; PrivateTmp=true
; ProtectHome=true
; ProtectSystem=full


Type=simple
ExecStart=/usr/bin/irexec /etc/lirc/irexec.lircrc

[Install]
WantedBy=multi-user.target

So what you need to do is to install an irexec.service file for your
system.  The easy way to do that now (as long as the 16.04 systemd
version is late enough, which I think it is), is to run this command:

sudo systemctl --full edit irexec.service

I have never used the --full option before, so I do not know what it
will do if the original irexec.service file is not present, so if you
get an error with that command, remove the --full option.  The command
should open your default system editor with the correct irexec.service
file open, which should be empty in your case.  Paste in this text
with the name of your mythfrontend user subsituted in two places:

[Unit]
Documentation=man:irexec(1)
Documentation=http://lirc.org/html/configure.html
Documentation=http://lirc.org/html/configure.html#lircrc_format
Description=Handle events from IR remotes decoded by lircd(8)

[Service]
user=<your mythfronted user>
group=mythtv

; Hardening opts, see systemd.exec(5).  Doesn't add much unless
; not running as root. If these are applicable or not depends on
; what commands irexec.lircrc invokes.
;
; NoNewPrivileges=true
; MemoryDenyWriteExecute=true
; PrivateTmp=true
; ProtectHome=true
; ProtectSystem=full


Type=simple
ExecStart=/usr/bin/irexec /home/<your mythfrontend user>/.lirc/irexec

[Install]
WantedBy=multi-user.target

Save that and exit from the editor.  Then run these commands:

sudo systemctl enable irexec.service
sudo systemctl start irexec.service
sudo systemctl status irexec.service

The status command should show irexec has started and is running.  If
that has not worked, then you will need to fix whatever errors the log
output shows.

Then you can edit the /home/<your mythfrontend user>/.lirc/irexec file
to put in the commands you want to be able to run from remote buttons.
Each time you change that file, you need to do this command to restart
irexec so it re-reads the config file:

sudo systemctl restart irexec.service

If you want to save a little typing, ".service" is what systemctl
defaults to if the unit type is left off, so you can shorten the
systemctl commands like this:

sudo systemctl restart irexec

To test if irexec is working properly, set it up with a echo command
like my example, then open a terminal on X and press the remote button
to execute the irexec echo command.  You should see the echo text
appear in the terminal window.  Once that is working, you can try the
"killall mythfrontend.real" command.

The last time I have actually used irexec like this was in 14.04, so I
have never actually tested the above setup via systemd.  So there
could be a bug or two.

From mythtv at cain.id.au  Sun Mar 10 02:51:05 2019
From: mythtv at cain.id.au (myth tv)
Date: Sun, 10 Mar 2019 13:51:05 +1100
Subject: [mythtv-users] Trying Nvshield android package,
 unsuccessfully. Pointers needed.
In-Reply-To: <CAEh=wVGkWirQa2+j-QXwp3z1-TKdgPEoiQnCf-Y=QL0v=JqYUw@mail.gmail.com>
References: <CAEh=wVHc6uce5PSnYCDiCjK6+S=kBTpUSQa_93nfhWr-ENk96g@mail.gmail.com>
 <b955dc16-0cb9-701d-daab-a07aabeba07a@gmail.com>
 <CAEh=wVEFa=X4kkK__hRqc0wFUzinCo5eSi=oZRDtoaKKixvrYg@mail.gmail.com>
 <b4c2ee44-1fb3-ec5d-8e72-5b594d3b3879@gmail.com>
 <CAEh=wVH2d+RAirr=gvwr3wSjqui4inAdYfKchzj=mhPhkk2iwA@mail.gmail.com>
 <CAEh=wVHoTiuxSpG4e=4UBy8p44fKEwqUyVBSAcfgJE=yCFbvpA@mail.gmail.com>
 <CAEh=wVFB9nmkDyu49fVj97xs7=4NRF5G-pD-P_y+-C1RMo3aXg@mail.gmail.com>
 <eec2d4b4-30c3-b93a-1772-eee91eb1eff9@gmail.com>
 <CAEh=wVGuCQ3DUVsL1f=cpjjouPuvFvMmowM2_zWKLXReCh=1EQ@mail.gmail.com>
 <0fbbdfe8-77c0-2ba3-195b-5fd853d225ee@gmail.com>
 <CAEh=wVG4EiHxQ7-LWeTdj04SG-zcW-4JRdqVtAM83Y9Z3E27hA@mail.gmail.com>
 <CAEh=wVFW+AMC7vbC1KdgsXJOAQwhNbuaqnqS0uXPH5KanuZ90w@mail.gmail.com>
 <39c32fe8-37c5-32a1-5f4f-b4d98c74bb74@gmail.com>
 <CAEh=wVFM2RpWG=BLURs-eEiuZqFrWcPtHAxRb6WD1b71e+sjSg@mail.gmail.com>
 <CAEh=wVGzrEMaH4Pz-E5=ifdQk5LUhMOL6w7EmBFVhRTUsKo-Hg@mail.gmail.com>
 <4423ce21-7cd0-ecbd-cb19-91ca5fa5ffdb@gmail.com>
 <CAEh=wVGkWirQa2+j-QXwp3z1-TKdgPEoiQnCf-Y=QL0v=JqYUw@mail.gmail.com>
Message-ID: <CAJuCSZWLzxMM618NsUBBeW2DU8-Mcqhfd-4PdaUw8FVmpsuz9A@mail.gmail.com>

Hi,

I was wondering whether you resolved the Shield vs mysql 5.7 issues.
Looking through the thread, it seems I am experiencing somewhat similar
issues with random hangs from Shield connected to mythbackend server
running mysql 5.7. (Ubuntu 18.04)
Other remote frontends don't have an issue nor does the frontend running on
the same PC as the master backend.
Hangs seem to be related to mysql errors in the shields adb log.
Did you change to mariadb? or was it a hardware issue?

Andrew


On Mon, Jan 14, 2019 at 6:31 AM Kris J <kris.jensen.knj at gmail.com> wrote:

>
>>
>>
>> I just tried 'mythbackend --setverbose network', issued from a terminal
>> wih the backend already running, and looked at the backend log while
>> skipping around the frontend menus.  Lots of this sort of thing that
>> might perhaps be informative...   But not to me...
>>
>> MythCoreContext::dispatch  MythEvent : SYSTEM_EVENT SCREEN_TYPE_CREATED
>> targetscreen SENDER androidname
>>
>> John (with only one P)
>>
>>
>>
>
> I will try that.
> Thank you.
>
> However a Quick update:
> Seems my network switch needed a reboot, doing that cleared many but not
> all errors.
> Running a new temporary cable along the floor also helped. So I need to
> redo that cable run as well.
>
> And It seems my mysql server is slightly mis-configured. Still read up on
> that.
> That said. I'm waiting until I fix the cabling and have a clean mysql
> error log, for now.
>
> Thank you all for the pointers.
> Kris.
>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190310/98b8393f/attachment.html>

From allen.p.edwards at gmail.com  Sun Mar 10 03:25:02 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Sat, 9 Mar 2019 19:25:02 -0800
Subject: [mythtv-users] CTRL-ALT-BACKSPACE
In-Reply-To: <foq88e5milg1bhl2cq2gj93bd4f59079e6@4ax.com>
References: <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
 <mc458eppr7ac2mn6aqfeuefvn19ku9r1kd@4ax.com>
 <CAH8UtKN64enW_46mYe-v84CzWex5Rf0Ze88yqVmMGM9J4yoVVg@mail.gmail.com>
 <CAH8UtKN0CfTSFJmrMfHd_4r5BGwEmGpU=pinX9P+oEBoyFPn6g@mail.gmail.com>
 <lda68e9mgcbjblhasnd26gob31df4b02fa@4ax.com>
 <CAH8UtKPWM+JD4h40m0io8JKST6hnRbSfJBrjnKNzNbj0W6BA6g@mail.gmail.com>
 <CAH8UtKNk46ouEep7EB7RcL_SNMiTLpuQ+cBGgCtKzwtu+CwLaw@mail.gmail.com>
 <foq88e5milg1bhl2cq2gj93bd4f59079e6@4ax.com>
Message-ID: <CAH8UtKMgULgg3Ft39W1AtwK2jBos=hHY+e2OqVdJKtD_qUMvOg@mail.gmail.com>

On Sat, Mar 9, 2019 at 6:39 PM Stephen Worthington <stephen_agent at jsw.gen.nz>
wrote:

> On Sat, 9 Mar 2019 14:17:50 -0800, you wrote:
>
> >On Sat, Mar 9, 2019 at 1:20 PM Allen Edwards <allen.p.edwards at gmail.com>
> >wrote:
> >
> >>
> >>
> >> On Fri, Mar 8, 2019 at 6:57 PM Stephen Worthington <
> >> stephen_agent at jsw.gen.nz> wrote:
> >>
> >>> One alternative is to use lirc to assign a button on your remote to
> >>> kill mythfrontend.real.  Lirc can be set up to run scripts using
> >>> irexec.  The script would do a ps -e and find any running copies of
> >>> mythbackend.real and kill them.  Then the mythfrontend script would
> >>> see that mythfrontend.real had died and would restart it.
> >>>
> >>
> >>
> >Stephen
> >I have tried this without success.  Here is what I did.
> >1) I modified a key config action to escape
> >2) I verified that the key was now the escape key
> >3) I  modified the same key definition to run irexec and changed the
> config
> >action to "killall mythfrontend.real"
> >4) The key did nothing. Myth did not close and the pid did not change
> >5) I copied the config action to a terminal and it killed mythfrontend
> >
> >By the way, myth does not restart when I kill it.
> >
> >This is not exactly what you told me to do but it seemed like it should
> >work.
>
> >Correction: What I did was verify that I could change a key and test it,
> >then put an action that I verified would kill mythfrontend in and set the
> >key to irexec. Didn't do anything.
>
> Lirc runs irexec, not a key setting in MythTV.  In /home/<mythfrontend
> user>, you should find a file .lircrc that looks something like this:
>
> root at mypvr:/home/stephen# cat .lircrc
> #Custom lircrc generated via mythbuntu-lirc-generator
> #All application specific lircrc files are within ~/.lirc
> include ~/.lirc/mythtv
> include ~/.lirc/mplayer
> include ~/.lirc/xine
> include ~/.lirc/vlc
> include ~/.lirc/xmame
> include ~/.lirc/xmess
> include ~/.lirc/totem
> include ~/.lirc/elisa
> include ~/.lirc/irexec
>
> That is the file that lirc loads by default to set up all its
> keystrokes.  By convention, a separate file is used for the setup for
> each program that uses lirc, but the actual specification of the
> programs is done on the "prog =" lines inside those files, so you can
> mix setting for different programs in one lirc config file if you
> like.  My remote is using the devinput driver, so for a lirc key
> config to do anything, it needs a "remote = devinput" line.  Here are
> the first three key configs in my /home/stephen/.lirc/mythtv file:
>
> begin
>     remote = devinput
>     prog = mythtv
>              # Guide key
>     button = KEY_EPG
> #    config = S
>     config = Ctrl+Alt+G
>     repeat = 0
>     delay = 0
> end
>
> begin
>     remote = devinput
>     prog = mythtv
>     button = KEY_EXIT
>     config = Escape
>     repeat = 0
>     delay = 0
> end
>
> begin
>     remote = devinput
>     prog = mythtv
>     button = KEY_OK
>     config = Return
>     repeat = 0
>     delay = 0
> end
>
> begin
>     remote = devinput
>     prog = mythtv
>     button = KEY_RIGHT
>     config = Right
>     repeat = 1
>     delay = 1
> end
>
> So what the first one of those does is to say that when lirc receives
> a KEY_EPG input from the devinput driver, then if the program with the
> lirc name "mythtv" is attached to lirc at the time, it should send a
> Ctrl-Alt-G keystroke to that program.  Then inside mythfrontend (which
> is running with the lirc name "mythtv"), it will receive the
> Ctrl-Alt-G keystroke, look up its keystroke configs from the database
> and see that (in my setup) it should jump directly to the Programme
> Guide:
>
> MariaDB [mythconverg]> select * from jumppoints where keylist like
> '%alt+g%';
> +---------------+-------------+------------+----------+
> | destination   | description | keylist    | hostname |
> +---------------+-------------+------------+----------+
> | Program Guide | NULL        | Ctrl+Alt+G | mypvr    |
> +---------------+-------------+------------+----------+
> 1 row in set (0.00 sec)
>
>
> Here is an example with irexec:
>
> begin
>     remote = devinput
>     prog = irexec
>     button = KEY_YELLOW
>     config = echo "This is the Yellow key"
>     repeat = 0
>     delay = 0
> end
>
> What that does is when a KEY_YELLOW (teletext key) keystroke is
> received from the devinput driver, then if irexec is running and
> attached to lirc, then send irexec the keys in the "config =" line. So
> irexec will receive a line of text containing the echo command, which
> it will then execute.  For this to do anything, you need to be running
> irexec in the background as the same user that mythfrontend runs from.
> I think you said you are running Ubuntu 16.04, so the best way to run
> irexxec there is from systemd.  But the lirc package in 16.04 does not
> set that up for you.  In 18.04 the package installs a
> /lib/systemd/system/irexec.service file for you to modify to make this
> work:
>
> root at mypvr:/lib/systemd/system# cat irexec.service
> [Unit]
> Documentation=man:irexec(1)
> Documentation=http://lirc.org/html/configure.html
> Documentation=http://lirc.org/html/configure.html#lircrc_format
> Description=Handle events from IR remotes decoded by lircd(8)
>
> [Service]
> ; user=lirc
> ; group=lirc
>
> ; Hardening opts, see systemd.exec(5).  Doesn't add much unless
> ; not running as root. If these are applicable or not depends on
> ; what commands irexec.lircrc invokes.
> ;
> ; NoNewPrivileges=true
> ; MemoryDenyWriteExecute=true
> ; PrivateTmp=true
> ; ProtectHome=true
> ; ProtectSystem=full
>
>
> Type=simple
> ExecStart=/usr/bin/irexec /etc/lirc/irexec.lircrc
>
> [Install]
> WantedBy=multi-user.target
>
> So what you need to do is to install an irexec.service file for your
> system.  The easy way to do that now (as long as the 16.04 systemd
> version is late enough, which I think it is), is to run this command:
>
> sudo systemctl --full edit irexec.service
>
> I have never used the --full option before, so I do not know what it
> will do if the original irexec.service file is not present, so if you
> get an error with that command, remove the --full option.  The command
> should open your default system editor with the correct irexec.service
> file open, which should be empty in your case.  Paste in this text
> with the name of your mythfrontend user subsituted in two places:
>
> [Unit]
> Documentation=man:irexec(1)
> Documentation=http://lirc.org/html/configure.html
> Documentation=http://lirc.org/html/configure.html#lircrc_format
> Description=Handle events from IR remotes decoded by lircd(8)
>
> [Service]
> user=<your mythfronted user>
> group=mythtv
>
> ; Hardening opts, see systemd.exec(5).  Doesn't add much unless
> ; not running as root. If these are applicable or not depends on
> ; what commands irexec.lircrc invokes.
> ;
> ; NoNewPrivileges=true
> ; MemoryDenyWriteExecute=true
> ; PrivateTmp=true
> ; ProtectHome=true
> ; ProtectSystem=full
>
>
> Type=simple
> ExecStart=/usr/bin/irexec /home/<your mythfrontend user>/.lirc/irexec
>
> [Install]
> WantedBy=multi-user.target
>
> Save that and exit from the editor.  Then run these commands:
>
> sudo systemctl enable irexec.service
> sudo systemctl start irexec.service
> sudo systemctl status irexec.service
>
> The status command should show irexec has started and is running.  If
> that has not worked, then you will need to fix whatever errors the log
> output shows.
>
> Then you can edit the /home/<your mythfrontend user>/.lirc/irexec file
> to put in the commands you want to be able to run from remote buttons.
> Each time you change that file, you need to do this command to restart
> irexec so it re-reads the config file:
>
> sudo systemctl restart irexec.service
>
> If you want to save a little typing, ".service" is what systemctl
> defaults to if the unit type is left off, so you can shorten the
> systemctl commands like this:
>
> sudo systemctl restart irexec
>
> To test if irexec is working properly, set it up with a echo command
> like my example, then open a terminal on X and press the remote button
> to execute the irexec echo command.  You should see the echo text
> appear in the terminal window.  Once that is working, you can try the
> "killall mythfrontend.real" command.
>
> The last time I have actually used irexec like this was in 14.04, so I
> have never actually tested the above setup via systemd.  So there
> could be a bug or two.
> _______________________________________________
>

Thanks Stemphen for the detailed explanation.  I see now that the edit I
did is not working because the users are different. I also see I would need
to make quite a few modifications. Seeing all that and your last sentence I
think I will focus on getting Myth to startup without adding instances of
itself every time there is a restart. I spent most of today trying to
figure that out. I have a lead from Ian but don't know what starts myth so
can't go further.  I found a shell script that looks like it would start it
but it is from 2007 so I am dubious.

This thread has forked and I guess that is my fault. The fork has a
different subject line so it should be pretty clear.  Did you see that if I
do CTRL-ALT-BS 10 times I got 9 instances of mythfrontend running? Whatever
is starting myth is not noticing that it is already running.

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/7e39eff9/attachment.html>

From mkbloke at gmail.com  Sun Mar 10 04:44:44 2019
From: mkbloke at gmail.com (Ian Cameron)
Date: Sun, 10 Mar 2019 04:44:44 +0000
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <CAH8UtKMdnh3EVCRqe+UQ9BV5Akc+8VZ9MD4Pn-REx5yqGaLBaA@mail.gmail.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
 <mc458eppr7ac2mn6aqfeuefvn19ku9r1kd@4ax.com>
 <CAH8UtKN64enW_46mYe-v84CzWex5Rf0Ze88yqVmMGM9J4yoVVg@mail.gmail.com>
 <CAH8UtKN0CfTSFJmrMfHd_4r5BGwEmGpU=pinX9P+oEBoyFPn6g@mail.gmail.com>
 <CAH8UtKMMy59LdC75G_QVu-K-1QvbJ+OJQbfaX6ogDCpGszj-Kw@mail.gmail.com>
 <CAC+xXWMqmtPDPcwRBRX90fBBdq1TiLoBfsAgCzXD1uqR8UdAEg@mail.gmail.com>
 <CAH8UtKPETMJvemwZAzWgORg7X2zAsX5nyAQFV5Q4JYaP7A51iA@mail.gmail.com>
 <CAC+xXWNnoCBww4hN=SKG8-b53ZzwQHmfczzKAUMvdrXKTMMtEw@mail.gmail.com>
 <CAH8UtKPi8+RreKdm1oR+hx+j9A86PP4sb5xyStxETjM1WCGv5Q@mail.gmail.com>
 <CAH8UtKMWhPZq_bqniouSj3OGWbrAQUs-Lqo2R4UTJwMrodn9fQ@mail.gmail.com>
 <CAC+xXWO+PuLxdv=dA6phSdYxMGVKHy92NzZ4UQjVopQGV8wndg@mail.gmail.com>
 <CAH8UtKMdnh3EVCRqe+UQ9BV5Akc+8VZ9MD4Pn-REx5yqGaLBaA@mail.gmail.com>
Message-ID: <CAC+xXWOdHLsK8=sJO2oo3eF16O32KtA8pJOKjPRAxyPKLA1NTg@mail.gmail.com>

On Sun, 10 Mar 2019 at 00:55, Allen Edwards <allen.p.edwards at gmail.com>
wrote

> I have been reading scripts all day trying to find where that happens.  I
> assume there is somewhere I can look and find what script is actually
> called.  Any idea where that is?
>

I don't, but we can try to find out.  Assuming your home directory is
/home/dad, try:

grep -r mythfrontend /etc /usr/share /home/dad 2> /dev/null

and paste-bin the output.

Hopefully that will help.

Cheers, Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190310/e0ec7f15/attachment.html>

From allen.p.edwards at gmail.com  Sun Mar 10 05:23:46 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Sat, 9 Mar 2019 21:23:46 -0800
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <CAC+xXWOdHLsK8=sJO2oo3eF16O32KtA8pJOKjPRAxyPKLA1NTg@mail.gmail.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
 <mc458eppr7ac2mn6aqfeuefvn19ku9r1kd@4ax.com>
 <CAH8UtKN64enW_46mYe-v84CzWex5Rf0Ze88yqVmMGM9J4yoVVg@mail.gmail.com>
 <CAH8UtKN0CfTSFJmrMfHd_4r5BGwEmGpU=pinX9P+oEBoyFPn6g@mail.gmail.com>
 <CAH8UtKMMy59LdC75G_QVu-K-1QvbJ+OJQbfaX6ogDCpGszj-Kw@mail.gmail.com>
 <CAC+xXWMqmtPDPcwRBRX90fBBdq1TiLoBfsAgCzXD1uqR8UdAEg@mail.gmail.com>
 <CAH8UtKPETMJvemwZAzWgORg7X2zAsX5nyAQFV5Q4JYaP7A51iA@mail.gmail.com>
 <CAC+xXWNnoCBww4hN=SKG8-b53ZzwQHmfczzKAUMvdrXKTMMtEw@mail.gmail.com>
 <CAH8UtKPi8+RreKdm1oR+hx+j9A86PP4sb5xyStxETjM1WCGv5Q@mail.gmail.com>
 <CAH8UtKMWhPZq_bqniouSj3OGWbrAQUs-Lqo2R4UTJwMrodn9fQ@mail.gmail.com>
 <CAC+xXWO+PuLxdv=dA6phSdYxMGVKHy92NzZ4UQjVopQGV8wndg@mail.gmail.com>
 <CAH8UtKMdnh3EVCRqe+UQ9BV5Akc+8VZ9MD4Pn-REx5yqGaLBaA@mail.gmail.com>
 <CAC+xXWOdHLsK8=sJO2oo3eF16O32KtA8pJOKjPRAxyPKLA1NTg@mail.gmail.com>
Message-ID: <CAH8UtKPJ7WidsEN9+X6mv6RSS_7+8TOv7zxEB=-g6GMT5CpKFA@mail.gmail.com>

On Sat, Mar 9, 2019 at 8:45 PM Ian Cameron <mkbloke at gmail.com> wrote:

> On Sun, 10 Mar 2019 at 00:55, Allen Edwards <allen.p.edwards at gmail.com>
> wrote
>
>> I have been reading scripts all day trying to find where that happens.  I
>> assume there is somewhere I can look and find what script is actually
>> called.  Any idea where that is?
>>
>
> I don't, but we can try to find out.  Assuming your home directory is
> /home/dad, try:
>
> grep -r mythfrontend /etc /usr/share /home/dad 2> /dev/null
>
> and paste-bin the output.
>
> Hopefully that will help.
>
> Cheers, Ian
>
>
That is an interesting service.  I guess you do learn something every day.

https://pastebin.com/wpge3BMs

I thought the most likely candidate was this one but I was put off by the
date of 2007
/usr/share/mythtv/mythfrontend.sh

https://pastebin.com/yE6mautf

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190309/3989f3cd/attachment.html>

From mkbloke at gmail.com  Sun Mar 10 06:22:28 2019
From: mkbloke at gmail.com (Ian Cameron)
Date: Sun, 10 Mar 2019 06:22:28 +0000
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <CAH8UtKPJ7WidsEN9+X6mv6RSS_7+8TOv7zxEB=-g6GMT5CpKFA@mail.gmail.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
 <mc458eppr7ac2mn6aqfeuefvn19ku9r1kd@4ax.com>
 <CAH8UtKN64enW_46mYe-v84CzWex5Rf0Ze88yqVmMGM9J4yoVVg@mail.gmail.com>
 <CAH8UtKN0CfTSFJmrMfHd_4r5BGwEmGpU=pinX9P+oEBoyFPn6g@mail.gmail.com>
 <CAH8UtKMMy59LdC75G_QVu-K-1QvbJ+OJQbfaX6ogDCpGszj-Kw@mail.gmail.com>
 <CAC+xXWMqmtPDPcwRBRX90fBBdq1TiLoBfsAgCzXD1uqR8UdAEg@mail.gmail.com>
 <CAH8UtKPETMJvemwZAzWgORg7X2zAsX5nyAQFV5Q4JYaP7A51iA@mail.gmail.com>
 <CAC+xXWNnoCBww4hN=SKG8-b53ZzwQHmfczzKAUMvdrXKTMMtEw@mail.gmail.com>
 <CAH8UtKPi8+RreKdm1oR+hx+j9A86PP4sb5xyStxETjM1WCGv5Q@mail.gmail.com>
 <CAH8UtKMWhPZq_bqniouSj3OGWbrAQUs-Lqo2R4UTJwMrodn9fQ@mail.gmail.com>
 <CAC+xXWO+PuLxdv=dA6phSdYxMGVKHy92NzZ4UQjVopQGV8wndg@mail.gmail.com>
 <CAH8UtKMdnh3EVCRqe+UQ9BV5Akc+8VZ9MD4Pn-REx5yqGaLBaA@mail.gmail.com>
 <CAC+xXWOdHLsK8=sJO2oo3eF16O32KtA8pJOKjPRAxyPKLA1NTg@mail.gmail.com>
 <CAH8UtKPJ7WidsEN9+X6mv6RSS_7+8TOv7zxEB=-g6GMT5CpKFA@mail.gmail.com>
Message-ID: <CAC+xXWNKfgQGJhJb4TA327Ow1gTb9HgKw5EJ_e5ibtW1u9UKFw@mail.gmail.com>

On Sun, 10 Mar 2019 at 05:25, Allen Edwards <allen.p.edwards at gmail.com>
wrote:

>
>
> On Sat, Mar 9, 2019 at 8:45 PM Ian Cameron <mkbloke at gmail.com> wrote:
>
> https://pastebin.com/wpge3BMs
>

Thanks.

There is something I haven't checked with you yet.  When you first boot the
system, you are automatically logged in to LightDM, but then, do you start
the front-end manually, or is it started automatically at that point?

I thought the most likely candidate was this one but I was put off by the
> date of 2007
> /usr/share/mythtv/mythfrontend.sh
>
> https://pastebin.com/yE6mautf
>

You're right, it does restart the front-end in the event of a crash.  I'm
just trying to work out what starts that wrapper.

Cheers, Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190310/7e5c2e1a/attachment.html>

From mkbloke at gmail.com  Sun Mar 10 06:42:08 2019
From: mkbloke at gmail.com (Ian Cameron)
Date: Sun, 10 Mar 2019 06:42:08 +0000
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <CAC+xXWNKfgQGJhJb4TA327Ow1gTb9HgKw5EJ_e5ibtW1u9UKFw@mail.gmail.com>
References: <CAH8UtKM0onii=2uZMsJ4gzyN_aNOPJD03QfHf2gScjVhANt56Q@mail.gmail.com>
 <9cj48etbunl4g9e1ftl4fndaf0hf1kphif@4ax.com>
 <CAH8UtKNhUOZZaRthgv8_TCVE=NsgNis5_g3_EZi+dhxD3jr4gA@mail.gmail.com>
 <mc458eppr7ac2mn6aqfeuefvn19ku9r1kd@4ax.com>
 <CAH8UtKN64enW_46mYe-v84CzWex5Rf0Ze88yqVmMGM9J4yoVVg@mail.gmail.com>
 <CAH8UtKN0CfTSFJmrMfHd_4r5BGwEmGpU=pinX9P+oEBoyFPn6g@mail.gmail.com>
 <CAH8UtKMMy59LdC75G_QVu-K-1QvbJ+OJQbfaX6ogDCpGszj-Kw@mail.gmail.com>
 <CAC+xXWMqmtPDPcwRBRX90fBBdq1TiLoBfsAgCzXD1uqR8UdAEg@mail.gmail.com>
 <CAH8UtKPETMJvemwZAzWgORg7X2zAsX5nyAQFV5Q4JYaP7A51iA@mail.gmail.com>
 <CAC+xXWNnoCBww4hN=SKG8-b53ZzwQHmfczzKAUMvdrXKTMMtEw@mail.gmail.com>
 <CAH8UtKPi8+RreKdm1oR+hx+j9A86PP4sb5xyStxETjM1WCGv5Q@mail.gmail.com>
 <CAH8UtKMWhPZq_bqniouSj3OGWbrAQUs-Lqo2R4UTJwMrodn9fQ@mail.gmail.com>
 <CAC+xXWO+PuLxdv=dA6phSdYxMGVKHy92NzZ4UQjVopQGV8wndg@mail.gmail.com>
 <CAH8UtKMdnh3EVCRqe+UQ9BV5Akc+8VZ9MD4Pn-REx5yqGaLBaA@mail.gmail.com>
 <CAC+xXWOdHLsK8=sJO2oo3eF16O32KtA8pJOKjPRAxyPKLA1NTg@mail.gmail.com>
 <CAH8UtKPJ7WidsEN9+X6mv6RSS_7+8TOv7zxEB=-g6GMT5CpKFA@mail.gmail.com>
 <CAC+xXWNKfgQGJhJb4TA327Ow1gTb9HgKw5EJ_e5ibtW1u9UKFw@mail.gmail.com>
Message-ID: <CAC+xXWO+wC9KLJ2ZvE+tApouceZzvM4-KjaL9Zsy1ZvpN186Cg@mail.gmail.com>

On Sun, 10 Mar 2019 at 06:22, Ian Cameron <mkbloke at gmail.com> wrote:

> You're right, it does restart the front-end in the event of a crash.  I'm
> just trying to work out what starts that wrapper.
>

What is the output of:

ls -la /home/dad/.config/autostart

by the way?

I suspect if you ran the initial set-up at some point in the past, there
might be a symlink in there pointing to
/usr/share/applications/mythtv.desktop.

Cheers, Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190310/68540fb4/attachment.html>

From stephen_agent at jsw.gen.nz  Sun Mar 10 06:54:50 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Sun, 10 Mar 2019 19:54:50 +1300
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <CAC+xXWNKfgQGJhJb4TA327Ow1gTb9HgKw5EJ_e5ibtW1u9UKFw@mail.gmail.com>
References: <CAH8UtKMWhPZq_bqniouSj3OGWbrAQUs-Lqo2R4UTJwMrodn9fQ@mail.gmail.com>
 <CAC+xXWO+PuLxdv=dA6phSdYxMGVKHy92NzZ4UQjVopQGV8wndg@mail.gmail.com>
 <CAH8UtKMdnh3EVCRqe+UQ9BV5Akc+8VZ9MD4Pn-REx5yqGaLBaA@mail.gmail.com>
 <CAC+xXWOdHLsK8=sJO2oo3eF16O32KtA8pJOKjPRAxyPKLA1NTg@mail.gmail.com>
 <CAH8UtKPJ7WidsEN9+X6mv6RSS_7+8TOv7zxEB=-g6GMT5CpKFA@mail.gmail.com>
 <CAC+xXWNKfgQGJhJb4TA327Ow1gTb9HgKw5EJ_e5ibtW1u9UKFw@mail.gmail.com>
Message-ID: <slb98edipn0ke1396aeqkhrfi3virr7a3h@4ax.com>

On Sun, 10 Mar 2019 06:22:28 +0000, you wrote:

>On Sun, 10 Mar 2019 at 05:25, Allen Edwards <allen.p.edwards at gmail.com>
>wrote:
>
>>
>>
>> On Sat, Mar 9, 2019 at 8:45 PM Ian Cameron <mkbloke at gmail.com> wrote:
>>
>> https://pastebin.com/wpge3BMs
>>
>
>Thanks.
>
>There is something I haven't checked with you yet.  When you first boot the
>system, you are automatically logged in to LightDM, but then, do you start
>the front-end manually, or is it started automatically at that point?
>
>I thought the most likely candidate was this one but I was put off by the
>> date of 2007
>> /usr/share/mythtv/mythfrontend.sh
>>
>> https://pastebin.com/yE6mautf
>>
>
>You're right, it does restart the front-end in the event of a crash.  I'm
>just trying to work out what starts that wrapper.
>
>Cheers, Ian

On Ubuntu, /usr/bin/mythfrontend.real is run from the
/usr/bin/mythfrontend script (which is a link to
/usr/share/mythtv/mythfrontend.sh now in 18.04).  So editing
/usr/share/mythtv/mythfrontend.sh to make it check for any already
running copies of mythfrontend.real should fix this problem, without
having to find out where /usr/bin/mythfrontend script gets run from.

As I understand it, Alan's system is Ubuntu 16.04 running XFCE,
although I am not sure if it was installed as Xubuntu or Mythbuntu
originally, or has had XFCE installed on top of a normal Ubuntu.  On
my mother's MythTV box, which is still Ubuntu 16.04, originally
installed from Mythbuntu a large number of versions ago and upgraded
continuously since, the XFCE startup applications can be found here:

XFCE main menu (Ctrl-Esc, if you have fixed that to work) > Settings >
Session and Startup > Application Autostart > MythTV Frontend.

Clicking on the Edit button reveals that this runs:
  mythfrontend --service

I think that I have in the past found the file that those settings are
stored in, but at the moment it has escaped me again.  It is not in
any obvious place.

Looking at the contents of /usr/bin/mythfrontend, the first line of
code is this:

pidof mythfrontend.real 2>&1 >/dev/null && wmctrl -a "MythTV Frontend"
2>/dev/null && exit 0

Which should make the script exit if mythfrontend.real is already
running, and prevent multiple copies from being run.

From mkbloke at gmail.com  Sun Mar 10 08:23:09 2019
From: mkbloke at gmail.com (Ian Cameron)
Date: Sun, 10 Mar 2019 08:23:09 +0000
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <slb98edipn0ke1396aeqkhrfi3virr7a3h@4ax.com>
References: <CAH8UtKMWhPZq_bqniouSj3OGWbrAQUs-Lqo2R4UTJwMrodn9fQ@mail.gmail.com>
 <CAC+xXWO+PuLxdv=dA6phSdYxMGVKHy92NzZ4UQjVopQGV8wndg@mail.gmail.com>
 <CAH8UtKMdnh3EVCRqe+UQ9BV5Akc+8VZ9MD4Pn-REx5yqGaLBaA@mail.gmail.com>
 <CAC+xXWOdHLsK8=sJO2oo3eF16O32KtA8pJOKjPRAxyPKLA1NTg@mail.gmail.com>
 <CAH8UtKPJ7WidsEN9+X6mv6RSS_7+8TOv7zxEB=-g6GMT5CpKFA@mail.gmail.com>
 <CAC+xXWNKfgQGJhJb4TA327Ow1gTb9HgKw5EJ_e5ibtW1u9UKFw@mail.gmail.com>
 <slb98edipn0ke1396aeqkhrfi3virr7a3h@4ax.com>
Message-ID: <CAC+xXWORW8RagQCZ98H_0MYm8mZMPg0_Gr-f1_c1TuhXw1tqxg@mail.gmail.com>

Hi Stephen,

Many thanks for your detailed and useful reply.  Hopefully Allen can
investigate some of the options regarding the window manager information
you have given.

I must say, I did think your solution of killing mythfrontend via the
remote to be a good and elegant one.  Given that a remote is nearly always
to hand, it's about as user-friendly as it could be.  So far, we have gone
down this rabbit hole a bit - the question now is whether to go further
down it or give up...

Here is what I think is happening:

On Sun, 10 Mar 2019 at 06:56, Stephen Worthington <stephen_agent at jsw.gen.nz>
wrote:

> Looking at the contents of /usr/bin/mythfrontend, the first line of
> code is this:
>
> pidof mythfrontend.real 2>&1 >/dev/null && wmctrl -a "MythTV Frontend"
> 2>/dev/null && exit 0
>
> Which should make the script exit if mythfrontend.real is already
> running, and prevent multiple copies from being run.
>

Having sorted out the ctrl-alt-backspace issue, we moved on to sorting out
the automatic log in to LightDM after a ctrl-alt-backspace issue.  I think
the solution to the automatic log in issue is what is making the shell
script above fail, likely wmctrl returns false, so the wrapper does not
exit...

Clicking on the Edit button reveals that this runs:
>   mythfrontend --service
>

 ...so where I was going with this was to ultimately suggest running
mythfrontend without the --service option, which bypasses the automatic
restart functionality.  Obviously, a disadvantage of that would be that if
mythfrontend crashes and exits, no automatic restart would be performed and
I guess the "user-friendly" way to deal with that would become
ctrl-alt-backspace...

Cheers, Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190310/6a563e9a/attachment.html>

From stephen_agent at jsw.gen.nz  Sun Mar 10 08:48:26 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Sun, 10 Mar 2019 21:48:26 +1300
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <CAC+xXWORW8RagQCZ98H_0MYm8mZMPg0_Gr-f1_c1TuhXw1tqxg@mail.gmail.com>
References: <CAC+xXWO+PuLxdv=dA6phSdYxMGVKHy92NzZ4UQjVopQGV8wndg@mail.gmail.com>
 <CAH8UtKMdnh3EVCRqe+UQ9BV5Akc+8VZ9MD4Pn-REx5yqGaLBaA@mail.gmail.com>
 <CAC+xXWOdHLsK8=sJO2oo3eF16O32KtA8pJOKjPRAxyPKLA1NTg@mail.gmail.com>
 <CAH8UtKPJ7WidsEN9+X6mv6RSS_7+8TOv7zxEB=-g6GMT5CpKFA@mail.gmail.com>
 <CAC+xXWNKfgQGJhJb4TA327Ow1gTb9HgKw5EJ_e5ibtW1u9UKFw@mail.gmail.com>
 <slb98edipn0ke1396aeqkhrfi3virr7a3h@4ax.com>
 <CAC+xXWORW8RagQCZ98H_0MYm8mZMPg0_Gr-f1_c1TuhXw1tqxg@mail.gmail.com>
Message-ID: <0ji98elqkapt7bjuuetnortq4riha9rv51@4ax.com>

On Sun, 10 Mar 2019 08:23:09 +0000, you wrote:

>Hi Stephen,
>
>Many thanks for your detailed and useful reply.  Hopefully Allen can
>investigate some of the options regarding the window manager information
>you have given.
>
>I must say, I did think your solution of killing mythfrontend via the
>remote to be a good and elegant one.  Given that a remote is nearly always
>to hand, it's about as user-friendly as it could be.  So far, we have gone
>down this rabbit hole a bit - the question now is whether to go further
>down it or give up...
>
>Here is what I think is happening:
>
>On Sun, 10 Mar 2019 at 06:56, Stephen Worthington <stephen_agent at jsw.gen.nz>
>wrote:
>
>> Looking at the contents of /usr/bin/mythfrontend, the first line of
>> code is this:
>>
>> pidof mythfrontend.real 2>&1 >/dev/null && wmctrl -a "MythTV Frontend"
>> 2>/dev/null && exit 0
>>
>> Which should make the script exit if mythfrontend.real is already
>> running, and prevent multiple copies from being run.
>>
>
>Having sorted out the ctrl-alt-backspace issue, we moved on to sorting out
>the automatic log in to LightDM after a ctrl-alt-backspace issue.  I think
>the solution to the automatic log in issue is what is making the shell
>script above fail, likely wmctrl returns false, so the wrapper does not
>exit...

I think it should be exiting if it sees a zero result from the pidof
command.  So maybe it should be changed to something like this:

pidof mythfrontend.real 2>&1 >/dev/null
pidof_retcode=$?
if [ $pidof_retcode==0 ]; then
  wmctrl -a "MythTV Frontend" 2>/dev/null
  wmctrl_retcode=$?
else
  wmctrl_retcode=1
fi
if [ pidof_retcode==0 || wmctrl_retcode==0 ]; then
  exit 0
fi

From mkbloke at gmail.com  Sun Mar 10 11:08:36 2019
From: mkbloke at gmail.com (Ian Cameron)
Date: Sun, 10 Mar 2019 11:08:36 +0000
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <0ji98elqkapt7bjuuetnortq4riha9rv51@4ax.com>
References: <CAC+xXWO+PuLxdv=dA6phSdYxMGVKHy92NzZ4UQjVopQGV8wndg@mail.gmail.com>
 <CAH8UtKMdnh3EVCRqe+UQ9BV5Akc+8VZ9MD4Pn-REx5yqGaLBaA@mail.gmail.com>
 <CAC+xXWOdHLsK8=sJO2oo3eF16O32KtA8pJOKjPRAxyPKLA1NTg@mail.gmail.com>
 <CAH8UtKPJ7WidsEN9+X6mv6RSS_7+8TOv7zxEB=-g6GMT5CpKFA@mail.gmail.com>
 <CAC+xXWNKfgQGJhJb4TA327Ow1gTb9HgKw5EJ_e5ibtW1u9UKFw@mail.gmail.com>
 <slb98edipn0ke1396aeqkhrfi3virr7a3h@4ax.com>
 <CAC+xXWORW8RagQCZ98H_0MYm8mZMPg0_Gr-f1_c1TuhXw1tqxg@mail.gmail.com>
 <0ji98elqkapt7bjuuetnortq4riha9rv51@4ax.com>
Message-ID: <CAC+xXWMqELDa5fzcmWKeWBCJwVCbK+XQbhoE669CTyZzpjkQGQ@mail.gmail.com>

On Sun, 10 Mar 2019 at 08:50, Stephen Worthington <stephen_agent at jsw.gen.nz>
wrote:

> I think it should be exiting if it sees a zero result from the pidof
> command.  So maybe it should be changed to something like this:
>
> pidof mythfrontend.real 2>&1 >/dev/null
> pidof_retcode=$?
> if [ $pidof_retcode==0 ]; then
>   wmctrl -a "MythTV Frontend" 2>/dev/null
>   wmctrl_retcode=$?
> else
>   wmctrl_retcode=1
> fi
> if [ pidof_retcode==0 || wmctrl_retcode==0 ]; then
>   exit 0
> fi
>

Thank you, that looks great.

It did cross my mind to change the logic there, but I was wary about the
idea of going even further down the hole.  Having thought about it a bit
more, I think if Allen tests this by modifying the in situ mythfrontend.sh
(after making a back-up for quick reversal, if necessary) and finds it
solves the problem, then you (or I, if you would prefer not to spend the
time doing it), can submit this as a patch to the mythbuntu team, which. if
accepted, will mean a future upgrade won't cause him any issues.

Thanks again.

Cheers, Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190310/67c1a9df/attachment.html>

From jam at tigger.ws  Sun Mar 10 11:14:54 2019
From: jam at tigger.ws (James Linder)
Date: Sun, 10 Mar 2019 19:14:54 +0800
Subject: [mythtv-users] transcode
Message-ID: <C9E05CAA-4C10-4C4F-B08C-C7B76C3C9C60@tigger.ws>

Hi

since mythtranscode does not handle h264 I?ve been trying to use mythffmpeg.
The best I can gather via google is

ffmpeg -i "test.avi" -c:v libx264 -crf 20 -c:a aac -strict -2 ?test.mp4"

mythffmpeg does not accept crf option. This is a quality setting.

I will explore native ffmpeg, but are there any ideas of doing lossless cuts (which you can?t do) with the native  tools.
Shotcut works well but it is a pain to do the cuts, and a pain to automate it. (maybe you can but I cannot find any doco)

Thanks
James

From jharbestonus at gmail.com  Sun Mar 10 14:13:50 2019
From: jharbestonus at gmail.com (Jay Harbeston)
Date: Sun, 10 Mar 2019 10:13:50 -0400
Subject: [mythtv-users] transcode
In-Reply-To: <C9E05CAA-4C10-4C4F-B08C-C7B76C3C9C60@tigger.ws>
References: <C9E05CAA-4C10-4C4F-B08C-C7B76C3C9C60@tigger.ws>
Message-ID: <A6AB70D7-3B50-408D-8E0B-70B2C3C77EFA@gmail.com>



> On Mar 10, 2019, at 7:14 AM, James Linder <jam at tigger.ws> wrote:
> 
> Hi
> 
> since mythtranscode does not handle h264 I?ve been trying to use mythffmpeg.
> The best I can gather via google is
> 
> ffmpeg -i "test.avi" -c:v libx264 -crf 20 -c:a aac -strict -2 ?test.mp4?
> 

I use the following shell to cut mp4 ts files using the cutlist generated from editing in mythfrontend:

https://pastebin.com/SkMT2BRe <https://pastebin.com/SkMT2BRe>

It uses the passwd info from /etc/mythtv/config.xml. there is a temp directory used that can be changed as well as the directory where the recordings live.

I then create a user job using the following for the execute field:

/usr/local/bin/ffcut.sh %DIR% %CHANID% %STARTTIMEUTC% >> /tmp/ffcut.log

You will need to tweak the next line(line29 of the shell) depending on how you use mysql or mariadb:

basename=`mysql --login-path=local -N "${dbname}" <<-EOF


Regards.




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190310/bb067047/attachment.html>

From pb.mythtv at gmail.com  Sun Mar 10 14:17:57 2019
From: pb.mythtv at gmail.com (Peter Bennett)
Date: Sun, 10 Mar 2019 10:17:57 -0400
Subject: [mythtv-users] Trying Nvshield android package,
 unsuccessfully. Pointers needed.
In-Reply-To: <CAJuCSZWLzxMM618NsUBBeW2DU8-Mcqhfd-4PdaUw8FVmpsuz9A@mail.gmail.com>
References: <CAEh=wVHc6uce5PSnYCDiCjK6+S=kBTpUSQa_93nfhWr-ENk96g@mail.gmail.com>
 <CAEh=wVH2d+RAirr=gvwr3wSjqui4inAdYfKchzj=mhPhkk2iwA@mail.gmail.com>
 <CAEh=wVHoTiuxSpG4e=4UBy8p44fKEwqUyVBSAcfgJE=yCFbvpA@mail.gmail.com>
 <CAEh=wVFB9nmkDyu49fVj97xs7=4NRF5G-pD-P_y+-C1RMo3aXg@mail.gmail.com>
 <eec2d4b4-30c3-b93a-1772-eee91eb1eff9@gmail.com>
 <CAEh=wVGuCQ3DUVsL1f=cpjjouPuvFvMmowM2_zWKLXReCh=1EQ@mail.gmail.com>
 <0fbbdfe8-77c0-2ba3-195b-5fd853d225ee@gmail.com>
 <CAEh=wVG4EiHxQ7-LWeTdj04SG-zcW-4JRdqVtAM83Y9Z3E27hA@mail.gmail.com>
 <CAEh=wVFW+AMC7vbC1KdgsXJOAQwhNbuaqnqS0uXPH5KanuZ90w@mail.gmail.com>
 <39c32fe8-37c5-32a1-5f4f-b4d98c74bb74@gmail.com>
 <CAEh=wVFM2RpWG=BLURs-eEiuZqFrWcPtHAxRb6WD1b71e+sjSg@mail.gmail.com>
 <CAEh=wVGzrEMaH4Pz-E5=ifdQk5LUhMOL6w7EmBFVhRTUsKo-Hg@mail.gmail.com>
 <4423ce21-7cd0-ecbd-cb19-91ca5fa5ffdb@gmail.com>
 <CAEh=wVGkWirQa2+j-QXwp3z1-TKdgPEoiQnCf-Y=QL0v=JqYUw@mail.gmail.com>
 <CAJuCSZWLzxMM618NsUBBeW2DU8-Mcqhfd-4PdaUw8FVmpsuz9A@mail.gmail.com>
Message-ID: <3bb13d57-869b-abdd-26a1-5409d1fb1163@gmail.com>



On 3/9/19 9:51 PM, myth tv wrote:
> Hi,
>
> I was wondering whether you resolved the Shield vs mysql 5.7 issues.
> Looking through the thread, it seems I am experiencing somewhat 
> similar issues with random hangs from Shield connected to mythbackend 
> server running mysql 5.7. (Ubuntu 18.04)
> Other remote frontends don't have an issue nor does the frontend 
> running on the same PC as the master backend.
> Hangs seem to be related to mysql errors in the shields adb log.
> Did you change to mariadb? or was it a hardware issue?
>
> Andrew
I am not aware of any mysql problems with Shield. Can you paste the 
error messages into the email? I am using Mariadb 10.1 with no problems.

When does it hang? During playback or other times?

From jharbestonus at gmail.com  Sun Mar 10 14:36:14 2019
From: jharbestonus at gmail.com (Jay Harbeston (ISeePeople))
Date: Sun, 10 Mar 2019 10:36:14 -0400
Subject: [mythtv-users] Metadata lookup ignoring ttvdb.conf for some programs
Message-ID: <9C22B609-2D6B-4676-B8B9-4DD40FD28F1A@gmail.com>


I am having some issues with metadata lookup. I am using the ttvdb.conf file to define Magnum P.I. as well as The Good Doctor, and it appears that the value in ttvdb.conf is being ignored. I believe I have the Names entered correctly in ttvdb.conf as the lookup for these series was working fine a few weeks ago.. 
 
Also, If I edit the metadata for the Magnum P.I. episode, and put in the correct value in the inet ref field, and do a manual metadata lookup from the jobs menu it will get the right information.

Looking at the metadata logs, I did not see a reference to the ttvdb value that I put in ttvdb.conf prior to hard coding the value in the inetref field.

Does the inetref value need to be added to the record table? It is currently blank.

Any pointers to fix this?  

Regards.

From allen.p.edwards at gmail.com  Sun Mar 10 16:50:51 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Sun, 10 Mar 2019 09:50:51 -0700
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <CAC+xXWMqELDa5fzcmWKeWBCJwVCbK+XQbhoE669CTyZzpjkQGQ@mail.gmail.com>
References: <CAC+xXWO+PuLxdv=dA6phSdYxMGVKHy92NzZ4UQjVopQGV8wndg@mail.gmail.com>
 <CAH8UtKMdnh3EVCRqe+UQ9BV5Akc+8VZ9MD4Pn-REx5yqGaLBaA@mail.gmail.com>
 <CAC+xXWOdHLsK8=sJO2oo3eF16O32KtA8pJOKjPRAxyPKLA1NTg@mail.gmail.com>
 <CAH8UtKPJ7WidsEN9+X6mv6RSS_7+8TOv7zxEB=-g6GMT5CpKFA@mail.gmail.com>
 <CAC+xXWNKfgQGJhJb4TA327Ow1gTb9HgKw5EJ_e5ibtW1u9UKFw@mail.gmail.com>
 <slb98edipn0ke1396aeqkhrfi3virr7a3h@4ax.com>
 <CAC+xXWORW8RagQCZ98H_0MYm8mZMPg0_Gr-f1_c1TuhXw1tqxg@mail.gmail.com>
 <0ji98elqkapt7bjuuetnortq4riha9rv51@4ax.com>
 <CAC+xXWMqELDa5fzcmWKeWBCJwVCbK+XQbhoE669CTyZzpjkQGQ@mail.gmail.com>
Message-ID: <CAH8UtKOHCfM43E_jH16Fm_VBcYnM0=5E+jKJg+F7+G0yMUokdQ@mail.gmail.com>

Hi Ian and Stephen,

You guys were busy as I slept so I am creating a single response.

As to what I am running this is what I know

*dad at NewMyth:~$ lsb_release -a*
*No LSB modules are available.*
*Distributor ID: Ubuntu*
*Description:    Ubuntu 16.04.1 LTS*
*Release:        16.04*
*Codename:       xenial*


*dad at NewMyth:~$ apt-cache policy mythtv*
*mythtv:*
*  Installed: 2:0.28.2+fixes.20180827.9031599-0ubuntu0mythbuntu2*
*  Candidate: 2:0.28.2+fixes.20180827.9031599-0ubuntu0mythbuntu2*
*  Version table:*
* *** 2:0.28.2+fixes.20180827.9031599-0ubuntu0mythbuntu2 500*
*        500 http://ppa.launchpad.net/mythbuntu/0.28/ubuntu
<http://ppa.launchpad.net/mythbuntu/0.28/ubuntu> xenial/main i386 Packages*
*        100 /var/lib/dpkg/status*
*     2:0.28.0+fixes.20160413.15cf421-0ubuntu2 500*
*        500 http://us.archive.ubuntu.com/ubuntu
<http://us.archive.ubuntu.com/ubuntu> xenial/multiverse i386 Packages*


And to Ian's question:

*dad at NewMyth:~$ ls -la /home/dad/.config/autostart*
*total 16*
*drwxrwxr-x  2 dad dad 4096 Oct 14 09:22 .*
*drwxrwxr-x 12 dad dad 4096 Feb 24 17:14 ..*
*lrwxrwxrwx  1 dad dad   38 Aug 25  2018 mythtv.desktop ->
/usr/share/applications/mythtv.desktop*
*-rw-rw-r--  1 dad dad   30 Oct 14 09:19 pulseaudio.desktop*
*-rw-rw-r--  1 dad dad   29 Oct 14 09:22 xfsettingsd.desktop*


I must say, I did think your solution of killing mythfrontend via the
remote to be a good and elegant one.  Given that a remote is nearly always
to hand, it's about as user-friendly as it could be.  So far, we have gone
down this rabbit hole a bit - the question now is whether to go further
down it or give up...

For a number of reasons having to do with what we are used to, the
difficulty of programming and using the remote, and the unknowns of
changing the lirc code, I prefer to continue on the CTRL-ALT-BS question as
I think we are very close to a solution with all the thought you two have
put into this. It could also be of benefit to others if a good solution is
found.

ultimately suggest running mythfrontend without the --service option

If Myth is being run by that script from 2007 that doesn't even run
correctly I must ask does myth still crash often enough that the auto
restart is necessary?  This seems like a super easy solution unless the
underlying program crashes constantly. BTW, I tested it and it works.

Of course, I may not know if this script is restarting myth but I doubt it
as we can see that it does't work.  The crashes I get of myth are freeze
up.  Still possible I would not know but worth thought as if the script
really is 12 years old then perhaps it is solving a problem that is no
longer a problem.

Clicking on the Edit button reveals that this runs:
*  mythfrontend --service*

Correct. What is your opinion on how important the --service is at this
point? That script is really old if the comments are correct.

If the --service option is necessary am I correct that the suggestion is to
change this line

*pidof mythfrontend.real 2>&1 >/dev/null && wmctrl -a "MythTV Frontend"
2>/dev/null && exit 0*

To this

*pidof mythfrontend.real 2>&1 >/dev/null*
*pidof_retcode=$?*
*if [ $pidof_retcode==0 ]; then*
*  wmctrl -a "MythTV Frontend" 2>/dev/null*
*  wmctrl_retcode=$?*
*else*
*  wmctrl_retcode=1*
*fi*
*if [ pidof_retcode==0 || wmctrl_retcode==0 ]; then*
*  exit 0*
*fi*

By the way, *pidof mythfrontend.real *returns 3524 (the pid) and *wmctrl -a
"MythTV Frontend"  *doesn't return anything at least on a terminal but I
think that is normal.

What I think is going on is that X closes mythfrontend.real but does not
close the service.  Then when X opens again and checks if myth is running
the service has not had time to get its version of myth running so the pid
returns null or 0. This happens so fast and all the services start versions
of myth before the pid is valid. One key is that when I do CTRL-ALT-BS I
don't always get a new instance, just 80-90% of the time.  This says to me
there is a timing component to the problem.  My computer is much faster
with the new RAM and my guess is that mostly all the services are busy
starting an instance of myth before a pid is established. Perhaps what is
needed as the first line of the script is a delay.

I will test the proposed script changes when I hear from you that I
understand it correctly and continue to think it is a good idea. Until
then, I am running mythfrontend without the service option. My gut says
that is the best solution anyway.   That script is just too old. I don't
trust it and doubt that it is necessary any longer.

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190310/31c7baad/attachment.html>

From kris.jensen.knj at gmail.com  Sun Mar 10 17:11:44 2019
From: kris.jensen.knj at gmail.com (Kris J)
Date: Sun, 10 Mar 2019 13:11:44 -0400
Subject: [mythtv-users] Trying Nvshield android package,
 unsuccessfully. Pointers needed.
In-Reply-To: <3bb13d57-869b-abdd-26a1-5409d1fb1163@gmail.com>
References: <CAEh=wVHc6uce5PSnYCDiCjK6+S=kBTpUSQa_93nfhWr-ENk96g@mail.gmail.com>
 <CAEh=wVH2d+RAirr=gvwr3wSjqui4inAdYfKchzj=mhPhkk2iwA@mail.gmail.com>
 <CAEh=wVHoTiuxSpG4e=4UBy8p44fKEwqUyVBSAcfgJE=yCFbvpA@mail.gmail.com>
 <CAEh=wVFB9nmkDyu49fVj97xs7=4NRF5G-pD-P_y+-C1RMo3aXg@mail.gmail.com>
 <eec2d4b4-30c3-b93a-1772-eee91eb1eff9@gmail.com>
 <CAEh=wVGuCQ3DUVsL1f=cpjjouPuvFvMmowM2_zWKLXReCh=1EQ@mail.gmail.com>
 <0fbbdfe8-77c0-2ba3-195b-5fd853d225ee@gmail.com>
 <CAEh=wVG4EiHxQ7-LWeTdj04SG-zcW-4JRdqVtAM83Y9Z3E27hA@mail.gmail.com>
 <CAEh=wVFW+AMC7vbC1KdgsXJOAQwhNbuaqnqS0uXPH5KanuZ90w@mail.gmail.com>
 <39c32fe8-37c5-32a1-5f4f-b4d98c74bb74@gmail.com>
 <CAEh=wVFM2RpWG=BLURs-eEiuZqFrWcPtHAxRb6WD1b71e+sjSg@mail.gmail.com>
 <CAEh=wVGzrEMaH4Pz-E5=ifdQk5LUhMOL6w7EmBFVhRTUsKo-Hg@mail.gmail.com>
 <4423ce21-7cd0-ecbd-cb19-91ca5fa5ffdb@gmail.com>
 <CAEh=wVGkWirQa2+j-QXwp3z1-TKdgPEoiQnCf-Y=QL0v=JqYUw@mail.gmail.com>
 <CAJuCSZWLzxMM618NsUBBeW2DU8-Mcqhfd-4PdaUw8FVmpsuz9A@mail.gmail.com>
 <3bb13d57-869b-abdd-26a1-5409d1fb1163@gmail.com>
Message-ID: <CAEh=wVGSE7nt-fHFYDTws-6+ePHb3-hV5VTzqcC9zPTBT13dNA@mail.gmail.com>

On Sun, Mar 10, 2019 at 10:18 AM Peter Bennett <pb.mythtv at gmail.com> wrote:

>
>
> On 3/9/19 9:51 PM, myth tv wrote:
> > Hi,
> >
> > I was wondering whether you resolved the Shield vs mysql 5.7 issues.
> > Looking through the thread, it seems I am experiencing somewhat
> > similar issues with random hangs from Shield connected to mythbackend
> > server running mysql 5.7. (Ubuntu 18.04)
> > Other remote frontends don't have an issue nor does the frontend
> > running on the same PC as the master backend.
> > Hangs seem to be related to mysql errors in the shields adb log.
> > Did you change to mariadb? or was it a hardware issue?
> >
> > Andrew
> I am not aware of any mysql problems with Shield. Can you paste the
> error messages into the email? I am using Mariadb 10.1 with no problems.
>
> When does it hang? During playback or other times?
> _______________________________________________
>
>
Hi The O.P.
No I did not remedy the issue. Tried for a week tweaking database setting
did not help. And then I got side tracked, and a bit frustrated.
To many things to do around the house ATM so this is on the very back
burner.

=/

Kris.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190310/bcb0bff0/attachment.html>

From allen.p.edwards at gmail.com  Sun Mar 10 19:49:14 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Sun, 10 Mar 2019 12:49:14 -0700
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <CAH8UtKOHCfM43E_jH16Fm_VBcYnM0=5E+jKJg+F7+G0yMUokdQ@mail.gmail.com>
References: <CAC+xXWO+PuLxdv=dA6phSdYxMGVKHy92NzZ4UQjVopQGV8wndg@mail.gmail.com>
 <CAH8UtKMdnh3EVCRqe+UQ9BV5Akc+8VZ9MD4Pn-REx5yqGaLBaA@mail.gmail.com>
 <CAC+xXWOdHLsK8=sJO2oo3eF16O32KtA8pJOKjPRAxyPKLA1NTg@mail.gmail.com>
 <CAH8UtKPJ7WidsEN9+X6mv6RSS_7+8TOv7zxEB=-g6GMT5CpKFA@mail.gmail.com>
 <CAC+xXWNKfgQGJhJb4TA327Ow1gTb9HgKw5EJ_e5ibtW1u9UKFw@mail.gmail.com>
 <slb98edipn0ke1396aeqkhrfi3virr7a3h@4ax.com>
 <CAC+xXWORW8RagQCZ98H_0MYm8mZMPg0_Gr-f1_c1TuhXw1tqxg@mail.gmail.com>
 <0ji98elqkapt7bjuuetnortq4riha9rv51@4ax.com>
 <CAC+xXWMqELDa5fzcmWKeWBCJwVCbK+XQbhoE669CTyZzpjkQGQ@mail.gmail.com>
 <CAH8UtKOHCfM43E_jH16Fm_VBcYnM0=5E+jKJg+F7+G0yMUokdQ@mail.gmail.com>
Message-ID: <CAH8UtKNXkyVoVj2wEZeVEF+c1N7NwOTvnk7Y5AxUcpBF6cTijw@mail.gmail.com>

On Sun, Mar 10, 2019 at 9:50 AM Allen Edwards <allen.p.edwards at gmail.com>
wrote:

> Hi Ian and Stephen,
>
> You guys were busy as I slept so I am creating a single response.
>
> As to what I am running this is what I know
>
> *dad at NewMyth:~$ lsb_release -a*
> *No LSB modules are available.*
> *Distributor ID: Ubuntu*
> *Description:    Ubuntu 16.04.1 LTS*
> *Release:        16.04*
> *Codename:       xenial*
>
>
> *dad at NewMyth:~$ apt-cache policy mythtv*
> *mythtv:*
> *  Installed: 2:0.28.2+fixes.20180827.9031599-0ubuntu0mythbuntu2*
> *  Candidate: 2:0.28.2+fixes.20180827.9031599-0ubuntu0mythbuntu2*
> *  Version table:*
> * *** 2:0.28.2+fixes.20180827.9031599-0ubuntu0mythbuntu2 500*
> *        500 http://ppa.launchpad.net/mythbuntu/0.28/ubuntu
> <http://ppa.launchpad.net/mythbuntu/0.28/ubuntu> xenial/main i386 Packages*
> *        100 /var/lib/dpkg/status*
> *     2:0.28.0+fixes.20160413.15cf421-0ubuntu2 500*
> *        500 http://us.archive.ubuntu.com/ubuntu
> <http://us.archive.ubuntu.com/ubuntu> xenial/multiverse i386 Packages*
>
>
> And to Ian's question:
>
> *dad at NewMyth:~$ ls -la /home/dad/.config/autostart*
> *total 16*
> *drwxrwxr-x  2 dad dad 4096 Oct 14 09:22 .*
> *drwxrwxr-x 12 dad dad 4096 Feb 24 17:14 ..*
> *lrwxrwxrwx  1 dad dad   38 Aug 25  2018 mythtv.desktop ->
> /usr/share/applications/mythtv.desktop*
> *-rw-rw-r--  1 dad dad   30 Oct 14 09:19 pulseaudio.desktop*
> *-rw-rw-r--  1 dad dad   29 Oct 14 09:22 xfsettingsd.desktop*
>
>
> I must say, I did think your solution of killing mythfrontend via the
> remote to be a good and elegant one.  Given that a remote is nearly always
> to hand, it's about as user-friendly as it could be.  So far, we have gone
> down this rabbit hole a bit - the question now is whether to go further
> down it or give up...
>
> For a number of reasons having to do with what we are used to, the
> difficulty of programming and using the remote, and the unknowns of
> changing the lirc code, I prefer to continue on the CTRL-ALT-BS question as
> I think we are very close to a solution with all the thought you two have
> put into this. It could also be of benefit to others if a good solution is
> found.
>
> ultimately suggest running mythfrontend without the --service option
>
> If Myth is being run by that script from 2007 that doesn't even run
> correctly I must ask does myth still crash often enough that the auto
> restart is necessary?  This seems like a super easy solution unless the
> underlying program crashes constantly. BTW, I tested it and it works.
>
> Of course, I may not know if this script is restarting myth but I doubt it
> as we can see that it does't work.  The crashes I get of myth are freeze
> up.  Still possible I would not know but worth thought as if the script
> really is 12 years old then perhaps it is solving a problem that is no
> longer a problem.
>
> Clicking on the Edit button reveals that this runs:
> *  mythfrontend --service*
>
> Correct. What is your opinion on how important the --service is at this
> point? That script is really old if the comments are correct.
>
> If the --service option is necessary am I correct that the suggestion is
> to change this line
>
> *pidof mythfrontend.real 2>&1 >/dev/null && wmctrl -a "MythTV Frontend"
> 2>/dev/null && exit 0*
>
> To this
>
> *pidof mythfrontend.real 2>&1 >/dev/null*
> *pidof_retcode=$?*
> *if [ $pidof_retcode==0 ]; then*
> *  wmctrl -a "MythTV Frontend" 2>/dev/null*
> *  wmctrl_retcode=$?*
> *else*
> *  wmctrl_retcode=1*
> *fi*
> *if [ pidof_retcode==0 || wmctrl_retcode==0 ]; then*
> *  exit 0*
> *fi*
>
> By the way, *pidof mythfrontend.real *returns 3524 (the pid) and *wmctrl
> -a "MythTV Frontend"  *doesn't return anything at least on a terminal but
> I think that is normal.
>
> What I think is going on is that X closes mythfrontend.real but does not
> close the service.  Then when X opens again and checks if myth is running
> the service has not had time to get its version of myth running so the pid
> returns null or 0. This happens so fast and all the services start versions
> of myth before the pid is valid. One key is that when I do CTRL-ALT-BS I
> don't always get a new instance, just 80-90% of the time.  This says to me
> there is a timing component to the problem.  My computer is much faster
> with the new RAM and my guess is that mostly all the services are busy
> starting an instance of myth before a pid is established. Perhaps what is
> needed as the first line of the script is a delay.
>
> I will test the proposed script changes when I hear from you that I
> understand it correctly and continue to think it is a good idea. Until
> then, I am running mythfrontend without the service option. My gut says
> that is the best solution anyway.   That script is just too old. I don't
> trust it and doubt that it is necessary any longer.
>
> Allen
>
>
As I said, eliminating the --service from the autostart edit solved the
problem. I have now tried some edits on the script.

Adding delay to  /usr/share/mythtv/mythfrontend.sh makes it so I only get
two instances of mythfrontend instead of one more for every restart. That
says to me there are two mechanisms and adding the delay cured one of them.
Recall that previously when I did ten restarts I had nine instances of
mythfrontend running. I thought this was interesting data so wanted to
share it.  It might help in figuring out what is going on as we descend
further down the rabbit hole.

Changing the first line to the suggestion in bold above and keeping the
delay (sleep 1) in was the same as keeping the old code.  I would get 2
instances of mythfrontend regardless of how many times I did a reset.  That
does not surprise me as the way I read it, it does the same thing as the
single line.  The single line relies on the property that the expression is
evaluated from left to right and only does the next test if the first one
passes.  It is very clever but also very hard to read.  The suggested edit
is easier to read but I think does the same thing.

I have reverted back to not running mythfrontend as a service. I continue
to feel this is the best solution.  That script is old and is basically a
hack to solve a problem that I would hope is no longer there. But I will
find out since I am running without it as a service.

There are two possible paths now.  One is to do nothing and see if myth
crashes and needed the autostart. The other is to continue down the rabbit
hole and try and solve the problem with the script.  My preference is to
continue the search for a solution to the script's issues but I do not feel
strongly one way or the other.

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190310/caa586a5/attachment.html>

From colonius at free.fr  Sun Mar 10 20:14:27 2019
From: colonius at free.fr (Klaus Becker)
Date: Sun, 10 Mar 2019 21:14:27 +0100
Subject: [mythtv-users] recordings too short
Message-ID: <64e73148-3c30-e5ec-75af-d242e22718c0@free.fr>

Hi,

my recordings often end before the real end of episodes, it's quite 
frustrating.

However my default recording rule says to add 30 min to recording time. 
I can no more find where to configure default or personal recording rules.

any idea ?

bye

Klaus

From allen.p.edwards at gmail.com  Sun Mar 10 21:59:19 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Sun, 10 Mar 2019 14:59:19 -0700
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <CAH8UtKNXkyVoVj2wEZeVEF+c1N7NwOTvnk7Y5AxUcpBF6cTijw@mail.gmail.com>
References: <CAC+xXWO+PuLxdv=dA6phSdYxMGVKHy92NzZ4UQjVopQGV8wndg@mail.gmail.com>
 <CAH8UtKMdnh3EVCRqe+UQ9BV5Akc+8VZ9MD4Pn-REx5yqGaLBaA@mail.gmail.com>
 <CAC+xXWOdHLsK8=sJO2oo3eF16O32KtA8pJOKjPRAxyPKLA1NTg@mail.gmail.com>
 <CAH8UtKPJ7WidsEN9+X6mv6RSS_7+8TOv7zxEB=-g6GMT5CpKFA@mail.gmail.com>
 <CAC+xXWNKfgQGJhJb4TA327Ow1gTb9HgKw5EJ_e5ibtW1u9UKFw@mail.gmail.com>
 <slb98edipn0ke1396aeqkhrfi3virr7a3h@4ax.com>
 <CAC+xXWORW8RagQCZ98H_0MYm8mZMPg0_Gr-f1_c1TuhXw1tqxg@mail.gmail.com>
 <0ji98elqkapt7bjuuetnortq4riha9rv51@4ax.com>
 <CAC+xXWMqELDa5fzcmWKeWBCJwVCbK+XQbhoE669CTyZzpjkQGQ@mail.gmail.com>
 <CAH8UtKOHCfM43E_jH16Fm_VBcYnM0=5E+jKJg+F7+G0yMUokdQ@mail.gmail.com>
 <CAH8UtKNXkyVoVj2wEZeVEF+c1N7NwOTvnk7Y5AxUcpBF6cTijw@mail.gmail.com>
Message-ID: <CAH8UtKPUayeJnW=Hhi1FemhDD2E2bRpiz+1toee8hsOzB+=+pg@mail.gmail.com>

On Sun, Mar 10, 2019 at 12:49 PM Allen Edwards <allen.p.edwards at gmail.com>
wrote:

> On Sun, Mar 10, 2019 at 9:50 AM Allen Edwards <allen.p.edwards at gmail.com>
> wrote:
>
>> Hi Ian and Stephen,
>>
>> You guys were busy as I slept so I am creating a single response.
>>
>> As to what I am running this is what I know
>>
>> *dad at NewMyth:~$ lsb_release -a*
>> *No LSB modules are available.*
>> *Distributor ID: Ubuntu*
>> *Description:    Ubuntu 16.04.1 LTS*
>> *Release:        16.04*
>> *Codename:       xenial*
>>
>>
>> *dad at NewMyth:~$ apt-cache policy mythtv*
>> *mythtv:*
>> *  Installed: 2:0.28.2+fixes.20180827.9031599-0ubuntu0mythbuntu2*
>> *  Candidate: 2:0.28.2+fixes.20180827.9031599-0ubuntu0mythbuntu2*
>> *  Version table:*
>> * *** 2:0.28.2+fixes.20180827.9031599-0ubuntu0mythbuntu2 500*
>> *        500 http://ppa.launchpad.net/mythbuntu/0.28/ubuntu
>> <http://ppa.launchpad.net/mythbuntu/0.28/ubuntu> xenial/main i386 Packages*
>> *        100 /var/lib/dpkg/status*
>> *     2:0.28.0+fixes.20160413.15cf421-0ubuntu2 500*
>> *        500 http://us.archive.ubuntu.com/ubuntu
>> <http://us.archive.ubuntu.com/ubuntu> xenial/multiverse i386 Packages*
>>
>>
>> And to Ian's question:
>>
>> *dad at NewMyth:~$ ls -la /home/dad/.config/autostart*
>> *total 16*
>> *drwxrwxr-x  2 dad dad 4096 Oct 14 09:22 .*
>> *drwxrwxr-x 12 dad dad 4096 Feb 24 17:14 ..*
>> *lrwxrwxrwx  1 dad dad   38 Aug 25  2018 mythtv.desktop ->
>> /usr/share/applications/mythtv.desktop*
>> *-rw-rw-r--  1 dad dad   30 Oct 14 09:19 pulseaudio.desktop*
>> *-rw-rw-r--  1 dad dad   29 Oct 14 09:22 xfsettingsd.desktop*
>>
>>
>> I must say, I did think your solution of killing mythfrontend via the
>> remote to be a good and elegant one.  Given that a remote is nearly always
>> to hand, it's about as user-friendly as it could be.  So far, we have gone
>> down this rabbit hole a bit - the question now is whether to go further
>> down it or give up...
>>
>> For a number of reasons having to do with what we are used to, the
>> difficulty of programming and using the remote, and the unknowns of
>> changing the lirc code, I prefer to continue on the CTRL-ALT-BS question as
>> I think we are very close to a solution with all the thought you two have
>> put into this. It could also be of benefit to others if a good solution is
>> found.
>>
>> ultimately suggest running mythfrontend without the --service option
>>
>> If Myth is being run by that script from 2007 that doesn't even run
>> correctly I must ask does myth still crash often enough that the auto
>> restart is necessary?  This seems like a super easy solution unless the
>> underlying program crashes constantly. BTW, I tested it and it works.
>>
>> Of course, I may not know if this script is restarting myth but I doubt
>> it as we can see that it does't work.  The crashes I get of myth are freeze
>> up.  Still possible I would not know but worth thought as if the script
>> really is 12 years old then perhaps it is solving a problem that is no
>> longer a problem.
>>
>> Clicking on the Edit button reveals that this runs:
>> *  mythfrontend --service*
>>
>> Correct. What is your opinion on how important the --service is at this
>> point? That script is really old if the comments are correct.
>>
>> If the --service option is necessary am I correct that the suggestion is
>> to change this line
>>
>> *pidof mythfrontend.real 2>&1 >/dev/null && wmctrl -a "MythTV Frontend"
>> 2>/dev/null && exit 0*
>>
>> To this
>>
>> *pidof mythfrontend.real 2>&1 >/dev/null*
>> *pidof_retcode=$?*
>> *if [ $pidof_retcode==0 ]; then*
>> *  wmctrl -a "MythTV Frontend" 2>/dev/null*
>> *  wmctrl_retcode=$?*
>> *else*
>> *  wmctrl_retcode=1*
>> *fi*
>> *if [ pidof_retcode==0 || wmctrl_retcode==0 ]; then*
>> *  exit 0*
>> *fi*
>>
>> By the way, *pidof mythfrontend.real *returns 3524 (the pid) and *wmctrl
>> -a "MythTV Frontend"  *doesn't return anything at least on a terminal
>> but I think that is normal.
>>
>> What I think is going on is that X closes mythfrontend.real but does not
>> close the service.  Then when X opens again and checks if myth is running
>> the service has not had time to get its version of myth running so the pid
>> returns null or 0. This happens so fast and all the services start versions
>> of myth before the pid is valid. One key is that when I do CTRL-ALT-BS I
>> don't always get a new instance, just 80-90% of the time.  This says to me
>> there is a timing component to the problem.  My computer is much faster
>> with the new RAM and my guess is that mostly all the services are busy
>> starting an instance of myth before a pid is established. Perhaps what is
>> needed as the first line of the script is a delay.
>>
>> I will test the proposed script changes when I hear from you that I
>> understand it correctly and continue to think it is a good idea. Until
>> then, I am running mythfrontend without the service option. My gut says
>> that is the best solution anyway.   That script is just too old. I don't
>> trust it and doubt that it is necessary any longer.
>>
>> Allen
>>
>>
> As I said, eliminating the --service from the autostart edit solved the
> problem. I have now tried some edits on the script.
>
> Adding delay to  /usr/share/mythtv/mythfrontend.sh makes it so I only get
> two instances of mythfrontend instead of one more for every restart. That
> says to me there are two mechanisms and adding the delay cured one of them.
> Recall that previously when I did ten restarts I had nine instances of
> mythfrontend running. I thought this was interesting data so wanted to
> share it.  It might help in figuring out what is going on as we descend
> further down the rabbit hole.
>
> Changing the first line to the suggestion in bold above and keeping the
> delay (sleep 1) in was the same as keeping the old code.  I would get 2
> instances of mythfrontend regardless of how many times I did a reset.  That
> does not surprise me as the way I read it, it does the same thing as the
> single line.  The single line relies on the property that the expression is
> evaluated from left to right and only does the next test if the first one
> passes.  It is very clever but also very hard to read.  The suggested edit
> is easier to read but I think does the same thing.
>
> I have reverted back to not running mythfrontend as a service. I continue
> to feel this is the best solution.  That script is old and is basically a
> hack to solve a problem that I would hope is no longer there. But I will
> find out since I am running without it as a service.
>
> There are two possible paths now.  One is to do nothing and see if myth
> crashes and needed the autostart. The other is to continue down the rabbit
> hole and try and solve the problem with the script.  My preference is to
> continue the search for a solution to the script's issues but I do not feel
> strongly one way or the other.
>
> Allen
>

I added a 10 second delay and the problem is gone, no duplicate instances
of myth. Maybe 3 seconds would work but definitely a race condition.  Other
than the delay, the code is the same as original.

In fairness to the code, my test is not real life.  Typically if I were to
do a CTRL-ALT-BS it would be because myth was frozen or missing. I don't
know that I ever did a CTRL-ALT-BS just as a test with Myth running. The
timing might be different and the service might be killed faster if it is
actually frozen. Or maybe I am wrong and this really is an issue.  Either
way, it should not keep piling on instances of mythfrontend.  But at least
I think we know what is going on now.

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190310/d982f5d2/attachment.html>

From johnpilk222 at gmail.com  Sun Mar 10 23:57:15 2019
From: johnpilk222 at gmail.com (John Pilkington)
Date: Sun, 10 Mar 2019 23:57:15 +0000
Subject: [mythtv-users] recordings too short
In-Reply-To: <64e73148-3c30-e5ec-75af-d242e22718c0@free.fr>
References: <64e73148-3c30-e5ec-75af-d242e22718c0@free.fr>
Message-ID: <6a306ac2-0ad0-9052-279e-e50b8e2442d8@gmail.com>

On 10/03/2019 20:14, Klaus Becker wrote:
> Hi,
> 
> my recordings often end before the real end of episodes, it's quite 
> frustrating.
> 
> However my default recording rule says to add 30 min to recording time. 
> I can no more find where to configure default or personal recording rules.
> 
> any idea ?
> 
> bye
> 
> Klaus

Your default recording rule will apply only to recordings which you have 
scheduled after the default was set.  I use start 2 min early, end 4 min 
late, but those offsets aren't always enough.  You can edit them 
individually by selecting the recording and pressing the Edit key, 
probably E, at any time before the recording ends.

The default rule is edited from

Frontend > Manage Recordings > Recording Rules  > Default(Template)

HTH

John



From hikavdh at gmail.com  Mon Mar 11 00:21:09 2019
From: hikavdh at gmail.com (Hika van den Hoven)
Date: Mon, 11 Mar 2019 01:21:09 +0100
Subject: [mythtv-users] recordings too short
In-Reply-To: <64e73148-3c30-e5ec-75af-d242e22718c0@free.fr>
References: <64e73148-3c30-e5ec-75af-d242e22718c0@free.fr>
Message-ID: <363775082.20190311012109@gmail.com>

Hoi Klaus,

Sunday, March 10, 2019, 9:14:27 PM, you wrote:

> Hi,

> my recordings often end before the real end of episodes, it's quite 
> frustrating.

> However my default recording rule says to add 30 min to recording time.
> I can no more find where to configure default or personal recording rules.

> any idea ?

> bye

> Klaus

To general add recording time before or after a show look at
Setup -> Video -> General
and then the fourth page (Advanced)
This extra time will only be added if it does not interfere with
another recording.


Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens


From stephen_agent at jsw.gen.nz  Mon Mar 11 02:31:07 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Mon, 11 Mar 2019 15:31:07 +1300
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <CAH8UtKPUayeJnW=Hhi1FemhDD2E2bRpiz+1toee8hsOzB+=+pg@mail.gmail.com>
References: <slb98edipn0ke1396aeqkhrfi3virr7a3h@4ax.com>
 <CAC+xXWORW8RagQCZ98H_0MYm8mZMPg0_Gr-f1_c1TuhXw1tqxg@mail.gmail.com>
 <0ji98elqkapt7bjuuetnortq4riha9rv51@4ax.com>
 <CAC+xXWMqELDa5fzcmWKeWBCJwVCbK+XQbhoE669CTyZzpjkQGQ@mail.gmail.com>
 <CAH8UtKOHCfM43E_jH16Fm_VBcYnM0=5E+jKJg+F7+G0yMUokdQ@mail.gmail.com>
 <CAH8UtKNXkyVoVj2wEZeVEF+c1N7NwOTvnk7Y5AxUcpBF6cTijw@mail.gmail.com>
 <CAH8UtKPUayeJnW=Hhi1FemhDD2E2bRpiz+1toee8hsOzB+=+pg@mail.gmail.com>
Message-ID: <vafb8epf2t7qa7s2ncev7ebovq25edn0ls@4ax.com>

On Sun, 10 Mar 2019 14:59:19 -0700, you wrote:

>I added a 10 second delay and the problem is gone, no duplicate instances
>of myth. Maybe 3 seconds would work but definitely a race condition.  Other
>than the delay, the code is the same as original.
>
>In fairness to the code, my test is not real life.  Typically if I were to
>do a CTRL-ALT-BS it would be because myth was frozen or missing. I don't
>know that I ever did a CTRL-ALT-BS just as a test with Myth running. The
>timing might be different and the service might be killed faster if it is
>actually frozen. Or maybe I am wrong and this really is an issue.  Either
>way, it should not keep piling on instances of mythfrontend.  But at least
>I think we know what is going on now.
>
>Allen

Using a delay to fix a race condition is usually a bad idea -
something happens which changes the timing, such as a bit of swapping
going on, and then the problem is back again.

Unfortunately, mythfrontend does die quite often for me.  The usual
cause is playing a downloaded video file.  I have quite a few that it
can not handle, and either it dies, or locks up and I have to kill it.
Some of the deaths leave behind "assert failed" messages.  But if you
do not normally play such files, then mythfrontend can be very
reliable and not need the wrapper script.

It looks like the wrapper script needs to be able to detect that the
script itself is still running and to exit if it can see another copy
of itself.  This should work to do that:

pid=$(ps -ef | grep '/bin/sh /usr/bin/mythfrontend --service' | grep
-v grep | awk '{print $2}')
if [ ${#pid} -ne 0 ]; then
    exit 0
fi

From allen.p.edwards at gmail.com  Mon Mar 11 02:55:51 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Sun, 10 Mar 2019 19:55:51 -0700
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <vafb8epf2t7qa7s2ncev7ebovq25edn0ls@4ax.com>
References: <slb98edipn0ke1396aeqkhrfi3virr7a3h@4ax.com>
 <CAC+xXWORW8RagQCZ98H_0MYm8mZMPg0_Gr-f1_c1TuhXw1tqxg@mail.gmail.com>
 <0ji98elqkapt7bjuuetnortq4riha9rv51@4ax.com>
 <CAC+xXWMqELDa5fzcmWKeWBCJwVCbK+XQbhoE669CTyZzpjkQGQ@mail.gmail.com>
 <CAH8UtKOHCfM43E_jH16Fm_VBcYnM0=5E+jKJg+F7+G0yMUokdQ@mail.gmail.com>
 <CAH8UtKNXkyVoVj2wEZeVEF+c1N7NwOTvnk7Y5AxUcpBF6cTijw@mail.gmail.com>
 <CAH8UtKPUayeJnW=Hhi1FemhDD2E2bRpiz+1toee8hsOzB+=+pg@mail.gmail.com>
 <vafb8epf2t7qa7s2ncev7ebovq25edn0ls@4ax.com>
Message-ID: <CAH8UtKNS9pT2M4GZ2CEVh=mUDDvS4UdXZF7CCZ1f5hCAg+HfAw@mail.gmail.com>

I agree. Will try your new script tomorrow. Races are nasty and the best
way to deal with them is to "fix" the race.  That is a pun. Sorry about the
top post but......

Allen

On Sun, Mar 10, 2019, 7:31 PM Stephen Worthington <stephen_agent at jsw.gen.nz>
wrote:

> On Sun, 10 Mar 2019 14:59:19 -0700, you wrote:
>
> >I added a 10 second delay and the problem is gone, no duplicate instances
> >of myth. Maybe 3 seconds would work but definitely a race condition.
> Other
> >than the delay, the code is the same as original.
> >
> >In fairness to the code, my test is not real life.  Typically if I were to
> >do a CTRL-ALT-BS it would be because myth was frozen or missing. I don't
> >know that I ever did a CTRL-ALT-BS just as a test with Myth running. The
> >timing might be different and the service might be killed faster if it is
> >actually frozen. Or maybe I am wrong and this really is an issue.  Either
> >way, it should not keep piling on instances of mythfrontend.  But at least
> >I think we know what is going on now.
> >
> >Allen
>
> Using a delay to fix a race condition is usually a bad idea -
> something happens which changes the timing, such as a bit of swapping
> going on, and then the problem is back again.
>
> Unfortunately, mythfrontend does die quite often for me.  The usual
> cause is playing a downloaded video file.  I have quite a few that it
> can not handle, and either it dies, or locks up and I have to kill it.
> Some of the deaths leave behind "assert failed" messages.  But if you
> do not normally play such files, then mythfrontend can be very
> reliable and not need the wrapper script.
>
> It looks like the wrapper script needs to be able to detect that the
> script itself is still running and to exit if it can see another copy
> of itself.  This should work to do that:
>
> pid=$(ps -ef | grep '/bin/sh /usr/bin/mythfrontend --service' | grep
> -v grep | awk '{print $2}')
> if [ ${#pid} -ne 0 ]; then
>     exit 0
> fi
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190310/455e3269/attachment.html>

From jam at tigger.ws  Mon Mar 11 03:53:32 2019
From: jam at tigger.ws (James Linder)
Date: Mon, 11 Mar 2019 11:53:32 +0800
Subject: [mythtv-users] transcode
In-Reply-To: <mailman.55.1552227483.1604.mythtv-users@mythtv.org>
References: <mailman.55.1552227483.1604.mythtv-users@mythtv.org>
Message-ID: <44869BD3-B7FC-43FA-819F-59FFFA5CF3D0@tigger.ws>



> On 10 Mar 2019, at 10:18 pm, mythtv-users-request at mythtv.org wrote:
> 
>> Hi
>> 
>> since mythtranscode does not handle h264 I?ve been trying to use mythffmpeg.
>> The best I can gather via google is
>> 
>> ffmpeg -i "test.avi" -c:v libx264 -crf 20 -c:a aac -strict -2 ?test.mp4?
>> 
> 
> I use the following shell to cut mp4 ts files using the cutlist generated from editing in mythfrontend:
> 
> https://pastebin.com/SkMT2BRe <https://pastebin.com/SkMT2BRe>
> 
> It uses the passwd info from /etc/mythtv/config.xml. there is a temp directory used that can be changed as well as the directory where the recordings live.
> 
> I then create a user job using the following for the execute field:
> 
> /usr/local/bin/ffcut.sh %DIR% %CHANID% %STARTTIMEUTC% >> /tmp/ffcut.log
> 
> You will need to tweak the next line(line29 of the shell) depending on how you use mysql or mariadb:
> 
> basename=`mysql --login-path=local -N "${dbname}" <<-EOF

Jay very interesting

Instead of diving into the DB this is an easy way to get the cutlist

    cutlist=`mythutil --getcutlist -q -q --video $srcname | sed -s s/Cutlist://`

Likewise

    mythutil --setcutlist $cutlist --video $TMPNAME

but I often have sub-second glitches (eg a flash of the last commercial

Do your tools have artifacts (1 good run does not prove that all runs are good)
Once I have cutlist?d the tmp file I mythtranscode.

Part of my hastle is massaging video for a Samsung uPnP. Eg the TV will play mpg files. It will not play a container called x.mpg but renaming it .avi and it will play. It also accepts mp4, but I've yet to try re-naminhq

James

From johnpilk222 at gmail.com  Mon Mar 11 10:12:53 2019
From: johnpilk222 at gmail.com (John Pilkington)
Date: Mon, 11 Mar 2019 10:12:53 +0000
Subject: [mythtv-users] transcode
In-Reply-To: <44869BD3-B7FC-43FA-819F-59FFFA5CF3D0@tigger.ws>
References: <mailman.55.1552227483.1604.mythtv-users@mythtv.org>
 <44869BD3-B7FC-43FA-819F-59FFFA5CF3D0@tigger.ws>
Message-ID: <9fc7e8a4-a8ac-0565-4146-3b29bbd4dd1e@gmail.com>

On 11/03/2019 03:53, James Linder wrote:
> 
> 
>> On 10 Mar 2019, at 10:18 pm, mythtv-users-request at mythtv.org wrote:
>>
>>> Hi
>>>
>>> since mythtranscode does not handle h264 I?ve been trying to use mythffmpeg.
>>> The best I can gather via google is
>>>
>>> ffmpeg -i "test.avi" -c:v libx264 -crf 20 -c:a aac -strict -2 ?test.mp4?
>>>
>>
>> I use the following shell to cut mp4 ts files using the cutlist generated from editing in mythfrontend:
>>
>> https://pastebin.com/SkMT2BRe <https://pastebin.com/SkMT2BRe>
>>
>> It uses the passwd info from /etc/mythtv/config.xml. there is a temp directory used that can be changed as well as the directory where the recordings live.
>>
>> I then create a user job using the following for the execute field:
>>
>> /usr/local/bin/ffcut.sh %DIR% %CHANID% %STARTTIMEUTC% >> /tmp/ffcut.log
>>
>> You will need to tweak the next line(line29 of the shell) depending on how you use mysql or mariadb:
>>
>> basename=`mysql --login-path=local -N "${dbname}" <<-EOF
> 
> Jay very interesting
> 
> Instead of diving into the DB this is an easy way to get the cutlist
> 
>      cutlist=`mythutil --getcutlist -q -q --video $srcname | sed -s s/Cutlist://`
> 
> Likewise
> 
>      mythutil --setcutlist $cutlist --video $TMPNAME
> 
> but I often have sub-second glitches (eg a flash of the last commercial
> 
> Do your tools have artifacts (1 good run does not prove that all runs are good)
> Once I have cutlist?d the tmp file I mythtranscode.
> 
> Part of my hastle is massaging video for a Samsung uPnP. Eg the TV will play mpg files. It will not play a container called x.mpg but renaming it .avi and it will play. It also accepts mp4, but I've yet to try re-naminhq
> 
> James

IIRC the cutlist works in frame numbers and ffmpeg needs milliseconds. 
Seektables store frame number, byte offset and time offset for every 
keyframe.  Much recent dev activity has been aimed at rationalising the 
way that playback uses this sort of info.

Last year I spent some effort on an h264 cutting script, mythTScut, 
which is on the wiki.  I haven't made recordings in that format 
recently, but the ones I still have that I processed with it play quite 
well.  ISTR that you tried it and wanted something different, but it 
might have some wrinkles that would help.

Cheers,

John P




From allen.p.edwards at gmail.com  Mon Mar 11 16:41:08 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Mon, 11 Mar 2019 09:41:08 -0700
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <vafb8epf2t7qa7s2ncev7ebovq25edn0ls@4ax.com>
References: <slb98edipn0ke1396aeqkhrfi3virr7a3h@4ax.com>
 <CAC+xXWORW8RagQCZ98H_0MYm8mZMPg0_Gr-f1_c1TuhXw1tqxg@mail.gmail.com>
 <0ji98elqkapt7bjuuetnortq4riha9rv51@4ax.com>
 <CAC+xXWMqELDa5fzcmWKeWBCJwVCbK+XQbhoE669CTyZzpjkQGQ@mail.gmail.com>
 <CAH8UtKOHCfM43E_jH16Fm_VBcYnM0=5E+jKJg+F7+G0yMUokdQ@mail.gmail.com>
 <CAH8UtKNXkyVoVj2wEZeVEF+c1N7NwOTvnk7Y5AxUcpBF6cTijw@mail.gmail.com>
 <CAH8UtKPUayeJnW=Hhi1FemhDD2E2bRpiz+1toee8hsOzB+=+pg@mail.gmail.com>
 <vafb8epf2t7qa7s2ncev7ebovq25edn0ls@4ax.com>
Message-ID: <CAH8UtKPiWUWQGFh8OjbpVkvodh6XDaHUqCUJDh=Qmengww4WdQ@mail.gmail.com>

On Sun, Mar 10, 2019 at 7:31 PM Stephen Worthington <
stephen_agent at jsw.gen.nz> wrote:

> On Sun, 10 Mar 2019 14:59:19 -0700, you wrote:
>
> >I added a 10 second delay and the problem is gone, no duplicate instances
> >of myth. Maybe 3 seconds would work but definitely a race condition.
> Other
> >than the delay, the code is the same as original.
> >
> >In fairness to the code, my test is not real life.  Typically if I were to
> >do a CTRL-ALT-BS it would be because myth was frozen or missing. I don't
> >know that I ever did a CTRL-ALT-BS just as a test with Myth running. The
> >timing might be different and the service might be killed faster if it is
> >actually frozen. Or maybe I am wrong and this really is an issue.  Either
> >way, it should not keep piling on instances of mythfrontend.  But at least
> >I think we know what is going on now.
> >
> >Allen
>
> Using a delay to fix a race condition is usually a bad idea -
> something happens which changes the timing, such as a bit of swapping
> going on, and then the problem is back again.
>
> Unfortunately, mythfrontend does die quite often for me.  The usual
> cause is playing a downloaded video file.  I have quite a few that it
> can not handle, and either it dies, or locks up and I have to kill it.
> Some of the deaths leave behind "assert failed" messages.  But if you
> do not normally play such files, then mythfrontend can be very
> reliable and not need the wrapper script.
>
> It looks like the wrapper script needs to be able to detect that the
> script itself is still running and to exit if it can see another copy
> of itself.  This should work to do that:
>
> pid=$(ps -ef | grep '/bin/sh /usr/bin/mythfrontend --service' | grep
> -v grep | awk '{print $2}')
> if [ ${#pid} -ne 0 ]; then
>     exit 0
> fi
> _______________________________________________
>
> I do not understand why this does not work but I am no script expert so I
am not sure what exactly is going on with ${#pid} and how that relates to
the initial pid. Perhaps there is a $ missing or misplaced on the first
line?  I did run some tests.

*dad at NewMyth:~$ ps -ef | grep '/bin/sh /usr/bin/mythfrontend --service' |
grep -v grep*
*dad       2310     1  0 09:17 ?        00:00:00 /bin/sh
/usr/bin/mythfrontend --service*
*dad       2605     1  0 09:17 ?        00:00:00 /bin/sh
/usr/bin/mythfrontend --service*
*dad       2961  2939  0 09:17 ?        00:00:00 /bin/sh
/usr/bin/mythfrontend --service*

And

*dad at NewMyth:~$ ps -ef | grep '/bin/sh /usr/bin/mythfrontend --service' |
grep -v grep | awk '{print $2}'*
*2310*
*2605*
*2961*

For now I will just run mythfrontend without the --service option.  That
should be fine for my needs. I am still willing to troubleshoot this if you
think that would be useful so let me know.

I wish to thank both Stephen and Ian for your help.

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190311/c8c34a84/attachment.html>

From colonius at free.fr  Mon Mar 11 16:59:10 2019
From: colonius at free.fr (Klaus Becker)
Date: Mon, 11 Mar 2019 17:59:10 +0100
Subject: [mythtv-users] recordings too short
In-Reply-To: <363775082.20190311012109@gmail.com>
References: <64e73148-3c30-e5ec-75af-d242e22718c0@free.fr>
 <363775082.20190311012109@gmail.com>
Message-ID: <64672cb4-3eca-d967-885b-fd8aad4142ed@free.fr>



Le 11/03/2019 ? 01:21, Hika van den Hoven a ?crit?:
> Hoi Klaus,
> 
> Sunday, March 10, 2019, 9:14:27 PM, you wrote:
> 
>> Hi,
> 
>> my recordings often end before the real end of episodes, it's quite
>> frustrating.
> 
>> However my default recording rule says to add 30 min to recording time.
>> I can no more find where to configure default or personal recording rules.
> 
>> any idea ?
> 
>> bye
> 
>> Klaus
> 
> To general add recording time before or after a show look at
> Setup -> Video -> General
> and then the fourth page (Advanced)

Ok, thanks. I set my values to try if my problem will disapperar.

But what's the difference with John's answer:

"The default rule is edited from
Frontend > Manage Recordings > Recording Rules  > Default(Template)"?

Klaus


> This extra time will only be added if it does not interfere with
> another recording.

of course

> 
> 
> Tot mails,
>    Hika                            mailto:hikavdh at gmail.com




From johnpilk222 at gmail.com  Mon Mar 11 17:22:41 2019
From: johnpilk222 at gmail.com (John Pilkington)
Date: Mon, 11 Mar 2019 17:22:41 +0000
Subject: [mythtv-users] recordings too short
In-Reply-To: <64672cb4-3eca-d967-885b-fd8aad4142ed@free.fr>
References: <64e73148-3c30-e5ec-75af-d242e22718c0@free.fr>
 <363775082.20190311012109@gmail.com>
 <64672cb4-3eca-d967-885b-fd8aad4142ed@free.fr>
Message-ID: <b022355b-a46b-2b57-4221-fc001be86f9b@gmail.com>

On 11/03/2019 16:59, Klaus Becker wrote:
> 
> 
> Le 11/03/2019 ? 01:21, Hika van den Hoven a ?crit?:
>> Hoi Klaus,
>>
>> Sunday, March 10, 2019, 9:14:27 PM, you wrote:
>>
>>> Hi,
>>
>>> my recordings often end before the real end of episodes, it's quite
>>> frustrating.
>>
>>> However my default recording rule says to add 30 min to recording time.
>>> I can no more find where to configure default or personal recording 
>>> rules.
>>
>>> any idea ?
>>
>>> bye
>>
>>> Klaus
>>
>> To general add recording time before or after a show look at
>> Setup -> Video -> General
>> and then the fourth page (Advanced)
> 
> Ok, thanks. I set my values to try if my problem will disapperar.
> 
> But what's the difference with John's answer:
> 
> "The default rule is edited from
> Frontend > Manage Recordings > Recording Rules? > Default(Template)"?
> 
> Klaus

I think one was called hard padding and the other soft.  A search might 
help.  They used to behave in subtly different ways.  ISTR that Hika's 
was intended mainly to give time for hardware to wake up, and I have 0 
in both of those places.

John
> 
>> This extra time will only be added if it does not interfere with
>> another recording.
> 
> of course
> 
>>
>>
>> Tot mails,
>> ?? Hika??????????????????????????? mailto:hikavdh at gmail.com
> 
> 
> 
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org


From thom.j.harris at gmail.com  Mon Mar 11 19:45:25 2019
From: thom.j.harris at gmail.com (Tom Harris)
Date: Mon, 11 Mar 2019 12:45:25 -0700
Subject: [mythtv-users] Switching from SchedulesDirect to EIT
Message-ID: <CAAme0OZ4VDWLszMsv+c3ox8r2d1qVsNKE8J=R=V5sz5kdw_xxg@mail.gmail.com>

My MythTV usage is now entirely for broadcast OTA channels, and I was
attempting to switch my guide data to be EIT sourced.   But, I haven't had
any luck in retrieving guide data.   Is there some trick to using EIT?

I'm on MythTV 0.28, and my tuner is an HDHomeRun Prime

- I changed the schedule source in mythtv-setup
- I marker the channels "useonairguide" in mythweb settings.

I guess mythfilldatabase isn't used for EIT?   When I run it, it exits
quickly and one of the lines output is:  "2019-03-11 12:38:10.572008 I
Source 1 configured to use only the broadcasted guide data. Skipping."

I do see backend log entries which appear to be trying to retrieve EIT data:
mythbackend.log:Mar 11 12:38:00 mythbackend: mythbackend[4306]: I EIT
eitcache.cpp:99 (delete_in_db) EITCache: Deleting old cache entries from
the database
mythbackend.log:Mar 11 12:38:00 mythbackend: mythbackend[4306]: I
TVRecEvent eitscanner.cpp:205 (StartPassiveScan) EITScanner (1): Started
passive scan.
mythbackend.log:Mar 11 12:39:17  mythbackend: mythbackend[4306]: I EIT
eitscanner.cpp:143 (run) EITScanner (5): Now looking for EIT data on
multiplex of channel 702
mythbackend.log:Mar 11 12:39:17  mythbackend: mythbackend[4306]: I EIT
eitcache.cpp:411 (PruneOldEntries) EITCache: Pruning all entries that ended
before UTC 2019-03-10T19:43:43Z
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190311/a96aaa63/attachment.html>

From johnpilk222 at gmail.com  Mon Mar 11 20:17:15 2019
From: johnpilk222 at gmail.com (John Pilkington)
Date: Mon, 11 Mar 2019 20:17:15 +0000
Subject: [mythtv-users] Switching from SchedulesDirect to EIT
In-Reply-To: <CAAme0OZ4VDWLszMsv+c3ox8r2d1qVsNKE8J=R=V5sz5kdw_xxg@mail.gmail.com>
References: <CAAme0OZ4VDWLszMsv+c3ox8r2d1qVsNKE8J=R=V5sz5kdw_xxg@mail.gmail.com>
Message-ID: <a8a691b4-858a-90ee-1578-71512d117401@gmail.com>

On 11/03/2019 19:45, Tom Harris wrote:
> My MythTV usage is now entirely for broadcast OTA channels, and I was 
> attempting to switch my guide data to be EIT sourced.? ?But, I haven't 
> had any luck in retrieving guide data.? ?Is there some trick to using EIT?
> 
> I'm on MythTV 0.28, and my tuner is an HDHomeRun Prime
> 
> - I changed the schedule source in mythtv-setup
> - I marker the channels "useonairguide" in mythweb settings.

First, have you seen https://www.mythtv.org/wiki/EIT ?

Latest edit is nearly 4 years old, so treat with caution.

In the UK, using dvb-t, each tuner has a 'use for active EIT scan' box. 
I don't know if this applies to HomeRun hardware, but I recently found 
that I needed to have that enabled for one, and preferably only one, tuner.

John P

> 
> I guess mythfilldatabase isn't used for EIT?? ?When I run it, it exits 
> quickly and one of the lines output is:? "2019-03-11 12:38:10.572008 I  
> Source 1 configured to use only the broadcasted guide data. Skipping."
> 
> I do see backend log entries which appear to be trying to retrieve EIT data:
> mythbackend.log:Mar 11 12:38:00 mythbackend: mythbackend[4306]: I EIT 
> eitcache.cpp:99 (delete_in_db) EITCache: Deleting old cache entries from 
> the database
> mythbackend.log:Mar 11 12:38:00 mythbackend: mythbackend[4306]: I 
> TVRecEvent eitscanner.cpp:205 (StartPassiveScan) EITScanner (1): Started 
> passive scan.
> mythbackend.log:Mar 11 12:39:17? mythbackend: mythbackend[4306]: I EIT 
> eitscanner.cpp:143 (run) EITScanner (5): Now looking for EIT data on 
> multiplex of channel 702
> mythbackend.log:Mar 11 12:39:17? mythbackend: mythbackend[4306]: I EIT 
> eitcache.cpp:411 (PruneOldEntries) EITCache: Pruning all entries that 
> ended before UTC 2019-03-10T19:43:43Z


From hikavdh at gmail.com  Mon Mar 11 21:28:23 2019
From: hikavdh at gmail.com (Hika van den Hoven)
Date: Mon, 11 Mar 2019 22:28:23 +0100
Subject: [mythtv-users] recordings too short
In-Reply-To: <b022355b-a46b-2b57-4221-fc001be86f9b@gmail.com>
References: <64e73148-3c30-e5ec-75af-d242e22718c0@free.fr> 
 <363775082.20190311012109@gmail.com>
 <64672cb4-3eca-d967-885b-fd8aad4142ed@free.fr>
 <b022355b-a46b-2b57-4221-fc001be86f9b@gmail.com>
Message-ID: <978150086.20190311222823@gmail.com>

Hoi Klaus,

Monday, March 11, 2019, 6:22:41 PM, you wrote:

> On 11/03/2019 16:59, Klaus Becker wrote:
>> 
>> 
>> Le 11/03/2019 ? 01:21, Hika van den Hoven a ?crit?:
>>> Hoi Klaus,
>>>
>>> Sunday, March 10, 2019, 9:14:27 PM, you wrote:
>>>
>>>> Hi,
>>>
>>>> my recordings often end before the real end of episodes, it's quite
>>>> frustrating.
>>>
>>>> However my default recording rule says to add 30 min to recording time.
>>>> I can no more find where to configure default or personal recording 
>>>> rules.
>>>
>>>> any idea ?
>>>
>>>> bye
>>>
>>>> Klaus
>>>
>>> To general add recording time before or after a show look at
>>> Setup -> Video -> General
>>> and then the fourth page (Advanced)
>> 
>> Ok, thanks. I set my values to try if my problem will disapperar.
>> 
>> But what's the difference with John's answer:
>> 
>> "The default rule is edited from
>> Frontend > Manage Recordings > Recording Rules? > Default(Template)"?
>> 
>> Klaus

> I think one was called hard padding and the other soft.  A search might
> help.  They used to behave in subtly different ways.  ISTR that Hika's
> was intended mainly to give time for hardware to wake up, and I have 0
> in both of those places.

> John

The effective difference is that this setting applies to each and
every rule and that you through this setting can change pre-roll and
after-roll without having to change every single rule. You can here
also give for instance sports an extra after-roll. You could do this
and more in a template, but templates only apply to rules created
AFTER the creation/change of the rule. This is the only place to
collectively manage some rule behavior.
The only other way is through SQL strait onto the database, which in
general is not advised. 

Another difference is that this pre/after-roll always has the lowest
priority, while a pre/after-role inside a rule shares the priority of
that rule. 

Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens


From mythtv at cain.id.au  Tue Mar 12 04:23:49 2019
From: mythtv at cain.id.au (myth tv)
Date: Tue, 12 Mar 2019 15:23:49 +1100
Subject: [mythtv-users] Trying Nvshield android package,
 unsuccessfully. Pointers needed.
In-Reply-To: <CAEh=wVGSE7nt-fHFYDTws-6+ePHb3-hV5VTzqcC9zPTBT13dNA@mail.gmail.com>
References: <CAEh=wVHc6uce5PSnYCDiCjK6+S=kBTpUSQa_93nfhWr-ENk96g@mail.gmail.com>
 <CAEh=wVH2d+RAirr=gvwr3wSjqui4inAdYfKchzj=mhPhkk2iwA@mail.gmail.com>
 <CAEh=wVHoTiuxSpG4e=4UBy8p44fKEwqUyVBSAcfgJE=yCFbvpA@mail.gmail.com>
 <CAEh=wVFB9nmkDyu49fVj97xs7=4NRF5G-pD-P_y+-C1RMo3aXg@mail.gmail.com>
 <eec2d4b4-30c3-b93a-1772-eee91eb1eff9@gmail.com>
 <CAEh=wVGuCQ3DUVsL1f=cpjjouPuvFvMmowM2_zWKLXReCh=1EQ@mail.gmail.com>
 <0fbbdfe8-77c0-2ba3-195b-5fd853d225ee@gmail.com>
 <CAEh=wVG4EiHxQ7-LWeTdj04SG-zcW-4JRdqVtAM83Y9Z3E27hA@mail.gmail.com>
 <CAEh=wVFW+AMC7vbC1KdgsXJOAQwhNbuaqnqS0uXPH5KanuZ90w@mail.gmail.com>
 <39c32fe8-37c5-32a1-5f4f-b4d98c74bb74@gmail.com>
 <CAEh=wVFM2RpWG=BLURs-eEiuZqFrWcPtHAxRb6WD1b71e+sjSg@mail.gmail.com>
 <CAEh=wVGzrEMaH4Pz-E5=ifdQk5LUhMOL6w7EmBFVhRTUsKo-Hg@mail.gmail.com>
 <4423ce21-7cd0-ecbd-cb19-91ca5fa5ffdb@gmail.com>
 <CAEh=wVGkWirQa2+j-QXwp3z1-TKdgPEoiQnCf-Y=QL0v=JqYUw@mail.gmail.com>
 <CAJuCSZWLzxMM618NsUBBeW2DU8-Mcqhfd-4PdaUw8FVmpsuz9A@mail.gmail.com>
 <3bb13d57-869b-abdd-26a1-5409d1fb1163@gmail.com>
 <CAEh=wVGSE7nt-fHFYDTws-6+ePHb3-hV5VTzqcC9zPTBT13dNA@mail.gmail.com>
Message-ID: <CAJuCSZW_6MTEN=iPgbv-Fg5fd1qFPrGsGn-R2yB8dL+=dMhskw@mail.gmail.com>

On Mon, Mar 11, 2019 at 4:12 AM Kris J <kris.jensen.knj at gmail.com> wrote:
>
> >On Sun, Mar 10, 2019 at 10:18 AM Peter Bennett <pb.mythtv at gmail.com> wrote:
>> On 3/9/19 9:51 PM, myth tv wrote:
>> > Hi,
>> >
>> > I was wondering whether you resolved the Shield vs mysql 5.7 issues.
>> > Looking through the thread, it seems I am experiencing somewhat
>> > similar issues with random hangs from Shield connected to mythbackend
>> > server running mysql 5.7. (Ubuntu 18.04)
>> > Other remote frontends don't have an issue nor does the frontend
>> > running on the same PC as the master backend.
>> > Hangs seem to be related to mysql errors in the shields adb log.
>> > Did you change to mariadb? or was it a hardware issue?
>> >
>> > Andrew
>> I am not aware of any mysql problems with Shield. Can you paste the
>> error messages into the email? I am using Mariadb 10.1 with no problems.
>>
>> When does it hang? During playback or other times?
>> _______________________________________________
>>
Peter, mythfrontend hangs randomly. Can take 3 minutes or 300 minutes.
Can be with watching recordings or even while still in the menu.

Below is the log from the shield (filtered for mfe) from mythfrontend
startup at 20:40:58 until the freeze at 21:46:06
(There is no specific error in the log at the time it freezes.)

03-10 20:40:58.864 15002 15025 W mythfrontend: (null):0 ((null)):
Could not create collator: 4
03-10 20:40:58.918 15002 15029 I mfe     : TV::TV::TV()(): Creating TV object
03-10 20:40:58.918 15002 15029 I mfe     : Suspending idle timer
03-10 20:40:58.918 15002 15029 I mfe     : TV::bool TV::Init(bool)():
Created TvPlayWindow.
03-10 20:40:58.919 15002 15029 I mfe     : TV::void
TV::HandleStateChange(PlayerContext*, PlayerContext*)(): Attempting to
change from None to WatchingPreRecorded
03-10 20:40:59.119 15002 15029 I mfe     : AOSLES: Native Rate 44100
03-10 20:40:59.120 15002 15029 I mfe     : AudioPlayer: Enabling Audio
03-10 20:40:59.420 15002 15029 I mfe     : AFD: codec MP2 has 2 channels
03-10 20:40:59.420 15002 15029 I mfe     : AFD: Opened codec
0x235399f500, id(MP2) type(Audio)
03-10 20:40:59.420 15002 15029 I mfe     : AFD: Using ffmpeg for video decoding
03-10 20:40:59.421 15002 15029 I mfe     : AFD: Opened codec
0x235399fa00, id(MPEG2VIDEO) type(Video)
03-10 20:40:59.421 15002 15029 I mfe     : AOBase: Resampling from 48
kHz to 44 kHz with quality medium
03-10 20:40:59.421 15002 15029 I mfe     : AOBase: Opening audio
device 'OpenSLES:' ch 2(2) sr 44100 sf signed 16 bit reenc 0
03-10 20:40:59.722 15002 15029 I mfe     : DispInfo: rate:59.9401
h:1080 w:1920 xdpi:213 ydpi:213
03-10 20:40:59.722 15002 15029 I mfe     : GLVid: Using 'opengl' for
OpenGL video type
03-10 20:40:59.823 15002 15029 E mfe     : MythFontProperties: Failed
to load 'DejaVu Sans', got 'Roboto' instead
03-10 20:40:59.823 15002 15029 E mfe     :
Location: /data/user/0/org.mythtv.mythfrontend/files/themes/Mythbuntu/osd.xml
@ 5
03-10 20:40:59.823 15002 15029 E mfe     :                      Name:
'medium'  Type: 'fontdef'
03-10 20:40:59.823 15002 15029 E mfe     : MythFontProperties: Failed
to load 'DejaVu Sans', got 'Roboto' instead
03-10 20:40:59.823 15002 15029 E mfe     :
Location: /data/user/0/org.mythtv.mythfrontend/files/themes/Mythbuntu/osd.xml
@ 9
03-10 20:40:59.823 15002 15029 E mfe     :                      Name:
'file'    Type: 'fontdef'
03-10 20:40:59.823 15002 15029 I mfe     : DispInfo: rate:59.9401
h:1080 w:1920 xdpi:213 ydpi:213
03-10 20:40:59.824 15002 15029 I mfe     : DispInfo: rate:59.9401
h:1080 w:1920 xdpi:213 ydpi:213
03-10 20:40:59.824 15002 15029 I mfe     : Player(0): Video timing
method: USleep with busy wait
03-10 20:40:59.824 15002 15029 I mfe     : TV::bool
TV::StartPlayer(PlayerContext*, PlayerContext*, TVState)(): Created
player.
03-10 20:40:59.824 15002 15029 I mfe     : TV::void
TV::HandleStateChange(PlayerContext*, PlayerContext*)(): Changing from
None to WatchingPreRecorded
03-10 20:40:59.824 15002 15029 E mfe     : AFD: Unknown audio decoding error
03-10 20:40:59.824 15002 15029 E mfe     : DB Error (Selecting
channel/dtv_multiplex):
03-10 20:40:59.824 15002 15029 E mfe     : Query was:
03-10 20:40:59.824 15002 15029 E mfe     : SELECT sourceid FROM
channel WHERE chanid = ?
03-10 20:40:59.824 15002 15029 E mfe     : Bindings were:
03-10 20:40:59.824 15002 15029 E mfe     : :CHANID=7002
03-10 20:40:59.824 15002 15029 E mfe     : Driver error was [2/2000]:
03-10 20:40:59.824 15002 15029 E mfe     : QMYSQL3: Unable to execute statement
03-10 20:40:59.824 15002 15029 E mfe     : Database error was:
03-10 20:40:59.824 15002 15029 E mfe     : Unknown MySQL error
03-10 20:40:59.824 15002 15029 I mfe     : TV::void
TV::HandleStateChange(PlayerContext*, PlayerContext*)(): Main UI
disabled.
03-10 20:40:59.824 15002 15029 I mfe     : TV::static bool
TV::StartTV(ProgramInfo*, uint, const ChannelInfoList&)(): Entering
main playback loop.
03-10 20:40:59.824 15002 15029 I mfe     : ScreenSaverAndroid: disable
03-10 20:40:59.825 15002 15029 I mfe     : ScreenSaverAndroid: disable 1
03-10 20:40:59.825 15002 15029 I mfe     : MySQL reconnected successfully
03-10 20:40:59.925 15002 15029 I mfe     : MythCodecContext: Disabled
hardware decoder based deinterlacer.
03-10 20:40:59.925 15002 15029 I mfe     : Player(0): Waited 102ms for
video buffers AAAAAAAAAAAAAAAAAAAAAAAAAAAAAuLP
03-10 20:41:00.025 15002 15029 I mfe     : Player(0): Waited 206ms for
video buffers uAAAAAAAAAAAAAAAAAAAAAAAAAAAAuLP
03-10 20:41:00.126 15002 15029 I mfe     : Player(0): Waited 309ms for
video buffers UUuUULuAAAAAAAAAAAAAAAAAAAAAAUUP
03-10 20:41:01.027 15002 15029 I mfe     : TV::void
TV::HandleStateChange(PlayerContext*, PlayerContext*)(): Attempting to
change from WatchingPreRecorded to None
03-10 20:41:01.128 15002 15029 I mfe     : TV::void
TV::HandleStateChange(PlayerContext*, PlayerContext*)(): Changing from
WatchingPreRecorded to None
03-10 20:41:01.128 15002 15029 I mfe     : TV::static bool
TV::StartTV(ProgramInfo*, uint, const ChannelInfoList&)(): Exiting
main playback loop.
03-10 20:41:01.128 15002 15029 I mfe     : ScreenSaverAndroid: restore
03-10 20:41:01.128 15002 15029 I mfe     : ScreenSaverAndroid: restore 1
03-10 20:41:01.128 15002 15029 I mfe     : Resuming idle timer
03-10 20:41:33.069 15002 15029 I mfe     : TV::TV::TV()(): Creating TV object
03-10 20:41:33.069 15002 15029 I mfe     : Suspending idle timer
03-10 20:41:33.070 15002 15029 I mfe     : TV::bool TV::Init(bool)():
Created TvPlayWindow.
03-10 20:41:33.170 15002 15029 I mfe     : TV::void
TV::HandleStateChange(PlayerContext*, PlayerContext*)(): Attempting to
change from None to WatchingPreRecorded
03-10 20:41:33.274 15002 15029 I mfe     : AOSLES: Native Rate 44100
03-10 20:41:33.274 15002 15029 I mfe     : AudioPlayer: Enabling Audio
03-10 20:41:33.575 15002 15029 I mfe     : AFD: codec MP2 has 2 channels
03-10 20:41:33.575 15002 15029 I mfe     : AFD: Opened codec
0x2353a08300, id(MP2) type(Audio)
03-10 20:41:33.575 15002 15029 I mfe     : AFD: Using ffmpeg for video decoding
03-10 20:41:33.575 15002 15029 I mfe     : AFD: Opened codec
0x2353a07e00, id(MPEG2VIDEO) type(Video)
03-10 20:41:33.575 15002 15029 I mfe     : AOBase: Resampling from 48
kHz to 44 kHz with quality medium
03-10 20:41:33.576 15002 15029 I mfe     : AOBase: Opening audio
device 'OpenSLES:' ch 2(2) sr 44100 sf signed 16 bit reenc 0
03-10 20:41:34.277 15002 15029 I mfe     : DispInfo: rate:59.9401
h:1080 w:1920 xdpi:213 ydpi:213
03-10 20:41:34.277 15002 15029 I mfe     : GLVid: Using 'opengl' for
OpenGL video type
03-10 20:41:34.479 15002 15029 E mfe     : MythFontProperties: Failed
to load 'DejaVu Sans', got 'Roboto' instead
03-10 20:41:34.479 15002 15029 E mfe     :
Location: /data/user/0/org.mythtv.mythfrontend/files/themes/Mythbuntu/osd.xml
@ 5
03-10 20:41:34.479 15002 15029 E mfe     :                      Name:
'medium'  Type: 'fontdef'
03-10 20:41:34.479 15002 15029 E mfe     : MythFontProperties: Failed
to load 'DejaVu Sans', got 'Roboto' instead
03-10 20:41:34.479 15002 15029 E mfe     :
Location: /data/user/0/org.mythtv.mythfrontend/files/themes/Mythbuntu/osd.xml
@ 9
03-10 20:41:34.479 15002 15029 E mfe     :                      Name:
'file'    Type: 'fontdef'
03-10 20:41:34.479 15002 15029 I mfe     : DispInfo: rate:59.9401
h:1080 w:1920 xdpi:213 ydpi:213
03-10 20:41:34.579 15002 15029 I mfe     : DispInfo: rate:59.9401
h:1080 w:1920 xdpi:213 ydpi:213
03-10 20:41:34.579 15002 15029 I mfe     : Player(1): Video timing
method: USleep with busy wait
03-10 20:41:34.580 15002 15029 I mfe     : TV::bool
TV::StartPlayer(PlayerContext*, PlayerContext*, TVState)(): Created
player.
03-10 20:41:34.580 15002 15029 I mfe     : TV::void
TV::HandleStateChange(PlayerContext*, PlayerContext*)(): Changing from
None to WatchingPreRecorded
03-10 20:41:34.580 15002 15029 E mfe     : AFD: Unknown audio decoding error
03-10 20:41:34.580 15002 15029 I mfe     : TV::void
TV::HandleStateChange(PlayerContext*, PlayerContext*)(): Main UI
disabled.
03-10 20:41:34.580 15002 15029 I mfe     : TV::static bool
TV::StartTV(ProgramInfo*, uint, const ChannelInfoList&)(): Entering
main playback loop.
03-10 20:41:34.580 15002 15029 I mfe     : ScreenSaverAndroid: disable
03-10 20:41:34.581 15002 15029 I mfe     : ScreenSaverAndroid: disable 1
03-10 20:41:34.581 15002 15029 I mfe     : MythCodecContext: Disabled
hardware decoder based deinterlacer.
03-10 20:41:34.681 15002 15029 I mfe     : Player(1): Waited 105ms for
video buffers AAAAAAAAAAAAAAAAAAAAAAAAAAAAuLLP
03-10 20:41:34.781 15002 15029 I mfe     : Player(1): Waited 209ms for
video buffers ULAAAAAAAAAAAAAAAAAAAAAAAAAAUuAP
03-10 20:41:34.882 15002 15029 I mfe     : Player(1): Waited 313ms for
video buffers UUUUuUULAAAAAAAAAAAAAAAAAAAAUUAP
03-10 20:41:52.999 15002 15029 I mfe     : Running HouseKeeperTask
'HardwareProfiler'.
03-10 20:41:52.999 15002 15029 I mfe     : HouseKeeperTask
'HardwareProfiler' Failed.
03-10 20:59:47.956 15002 15029 E mfe     : DB Error (Error in
JobQueue::GetJobs(), Unable to query list of Jobs in Queue.):
03-10 20:59:47.956 15002 15029 E mfe     : Query was:
03-10 20:59:47.956 15002 15029 E mfe     : SELECT j.id, j.chanid,
j.starttime, j.inserttime, j.type, j.cmds, j.flags, j.status,
j.statustime, j.hostname, j.args, j.comment, r.endtime, j.schedruntime
FROM jobqueue j LEFT JOIN recorded r   ON j.chanid = r.chanid AND
j.starttime = r.starttime ORDER BY j.schedruntime, j.id;
03-10 20:59:47.956 15002 15029 E mfe     : Driver error was [2/2000]:
03-10 20:59:47.956 15002 15029 E mfe     : QMYSQL3: Unable to execute statement
03-10 20:59:47.956 15002 15029 E mfe     : Database error was:
03-10 20:59:47.956 15002 15029 E mfe     : Unknown MySQL error
03-10 21:00:07.976 15002 15029 I mfe     : MySQL reconnected successfully
03-10 21:06:08.139 15002 15029 E mfe     : DB Error (Error in
JobQueue::GetJobs(), Unable to query list of Jobs in Queue.):
03-10 21:06:08.139 15002 15029 E mfe     : Query was:
03-10 21:06:08.139 15002 15029 E mfe     : SELECT j.id, j.chanid,
j.starttime, j.inserttime, j.type, j.cmds, j.flags, j.status,
j.statustime, j.hostname, j.args, j.comment, r.endtime, j.schedruntime
FROM jobqueue j LEFT JOIN recorded r   ON j.chanid = r.chanid AND
j.starttime = r.starttime ORDER BY j.schedruntime, j.id;
03-10 21:06:08.139 15002 15029 E mfe     : Driver error was [2/2000]:
03-10 21:06:08.139 15002 15029 E mfe     : QMYSQL3: Unable to execute statement
03-10 21:06:08.139 15002 15029 E mfe     : Database error was:
03-10 21:06:08.139 15002 15029 E mfe     : Unknown MySQL error
03-10 21:06:28.159 15002 15029 I mfe     : MySQL reconnected successfully
03-10 21:07:08.099 15002 15029 E mfe     : DB Error (Error in
JobQueue::GetJobs(), Unable to query list of Jobs in Queue.):
03-10 21:07:08.099 15002 15029 E mfe     : Query was:
03-10 21:07:08.099 15002 15029 E mfe     : SELECT j.id, j.chanid,
j.starttime, j.inserttime, j.type, j.cmds, j.flags, j.status,
j.statustime, j.hostname, j.args, j.comment, r.endtime, j.schedruntime
FROM jobqueue j LEFT JOIN recorded r   ON j.chanid = r.chanid AND
j.starttime = r.starttime ORDER BY j.schedruntime, j.id;
03-10 21:07:08.099 15002 15029 E mfe     : Driver error was [2/2000]:
03-10 21:07:08.099 15002 15029 E mfe     : QMYSQL3: Unable to execute statement
03-10 21:07:08.099 15002 15029 E mfe     : Database error was:
03-10 21:07:08.099 15002 15029 E mfe     : Unknown MySQL error
03-10 21:08:08.160 15002 15029 E mfe     : DB Error (Error in
JobQueue::GetJobs(), Unable to query list of Jobs in Queue.):
03-10 21:08:08.160 15002 15029 E mfe     : Query was:
03-10 21:08:08.160 15002 15029 E mfe     : SELECT j.id, j.chanid,
j.starttime, j.inserttime, j.type, j.cmds, j.flags, j.status,
j.statustime, j.hostname, j.args, j.comment, r.endtime, j.schedruntime
FROM jobqueue j LEFT JOIN recorded r   ON j.chanid = r.chanid AND
j.starttime = r.starttime ORDER BY j.schedruntime, j.id;
03-10 21:08:08.160 15002 15029 E mfe     : Driver error was [2/2000]:
03-10 21:08:08.160 15002 15029 E mfe     : QMYSQL3: Unable to execute statement
03-10 21:08:08.160 15002 15029 E mfe     : Database error was:
03-10 21:08:08.160 15002 15029 E mfe     : Unknown MySQL error
03-10 21:09:27.040 15002 15029 I mfe     : Player(1): Waited 104ms for
video buffers AAAAAAAAAAAAuAAAAAALAALAAAAAAAAP
03-10 21:09:27.140 15002 15029 I mfe     : Player(1): Waited 208ms for
video buffers AAAAAAAAAAAAuAAAAAALAALAAAAAAAAP
03-10 21:09:27.240 15002 15029 I mfe     : Player(1): Waited 312ms for
video buffers AAAAAAAAAAAAUAUuAULUAAAAAUAAAAAP
03-10 21:09:27.341 15002 15029 I mfe     : Player(1): Waited 416ms for
video buffers AAAAAAAAAAAAUAUUAUUUUuAULUAAAUUP
03-10 21:09:28.442 15002 15029 E mfe     : AFD: Unknown audio decoding error
03-10 21:09:28.543 15002 15029 I mfe     : Player(1): Waited 105ms for
video buffers AAAAAALAALAUuAAAAAAAAAAAAAAAAAAP
03-10 21:09:28.643 15002 15029 I mfe     : Player(1): Waited 209ms for
video buffers AAAAAAuAAAAUUALAAAAAAAAAAAAAAAAP
03-10 21:09:28.743 15002 15029 I mfe     : Player(1): To see more
buffering messages use -v playback
03-10 21:09:32.047 15002 15029 E mfe     : AFD: Unknown audio decoding error
03-10 21:09:33.749 15002 15029 E mfe     : AFD: Unknown audio decoding error
03-10 21:09:35.050 15002 15029 E mfe     : AFD: Unknown audio decoding error
03-10 21:09:35.050 15002 15029 E mfe     : AFD: Unknown audio decoding error
03-10 21:46:06.745 15002 15029 I mfe     : ScreenSaverAndroid: restore

>
> Hi The O.P.
> No I did not remedy the issue. Tried for a week tweaking database setting did not help. And then I got side tracked, and a bit frustrated.
> To many things to do around the house ATM so this is on the very back burner.
>
> =/
>
> Kris.
>
Kris, thanks for the update.

Andrew

From thom.j.harris at gmail.com  Tue Mar 12 04:49:07 2019
From: thom.j.harris at gmail.com (Tom Harris)
Date: Mon, 11 Mar 2019 21:49:07 -0700
Subject: [mythtv-users] Switching from SchedulesDirect to EIT
In-Reply-To: <a8a691b4-858a-90ee-1578-71512d117401@gmail.com>
References: <CAAme0OZ4VDWLszMsv+c3ox8r2d1qVsNKE8J=R=V5sz5kdw_xxg@mail.gmail.com>
 <a8a691b4-858a-90ee-1578-71512d117401@gmail.com>
Message-ID: <CAAme0Obffx_jSGT8+PdMDrKgOwvuD66dpogqBo-0REsD1u=9fg@mail.gmail.com>

On Mon, Mar 11, 2019 at 1:17 PM John Pilkington <johnpilk222 at gmail.com>
wrote:

> On 11/03/2019 19:45, Tom Harris wrote:
> > My MythTV usage is now entirely for broadcast OTA channels, and I was
> > attempting to switch my guide data to be EIT sourced.   But, I haven't
> > had any luck in retrieving guide data.   Is there some trick to using
> EIT?
> >
> > I'm on MythTV 0.28, and my tuner is an HDHomeRun Prime
> >
> > - I changed the schedule source in mythtv-setup
> > - I marker the channels "useonairguide" in mythweb settings.
>
> First, have you seen https://www.mythtv.org/wiki/EIT ?
>
> Latest edit is nearly 4 years old, so treat with caution.
>

Yeah, that's one of the sources of EIT info I was using, and I have my
video source set to
"Listings grabber: Transmitted guide data only (EIT)" as it describes
there.  But, in my setup screens, I don't see any options for active vs
passive scans.

In the UK, using dvb-t, each tuner has a 'use for active EIT scan' box.
> I don't know if this applies to HomeRun hardware, but I recently found
> that I needed to have that enabled for one, and preferably only one, tuner.
>

I have tweaked all the settings I could find.   But, no luck.
I have read other reports of EIT usage with HDhomerun devices, but I'm
beginning to doubt it.   It's a QAM (cable) device, and maybe the EIT data
is not mirrored into the cable transmission.

In any case, I decided to not mess with it and just renewed schedulesdirect
instead.



>
> John P
>
> >
> > I guess mythfilldatabase isn't used for EIT?   When I run it, it exits
> > quickly and one of the lines output is:  "2019-03-11 12:38:10.572008 I
> > Source 1 configured to use only the broadcasted guide data. Skipping."
> >
> > I do see backend log entries which appear to be trying to retrieve EIT
> data:
> > mythbackend.log:Mar 11 12:38:00 mythbackend: mythbackend[4306]: I EIT
> > eitcache.cpp:99 (delete_in_db) EITCache: Deleting old cache entries from
> > the database
> > mythbackend.log:Mar 11 12:38:00 mythbackend: mythbackend[4306]: I
> > TVRecEvent eitscanner.cpp:205 (StartPassiveScan) EITScanner (1): Started
> > passive scan.
> > mythbackend.log:Mar 11 12:39:17  mythbackend: mythbackend[4306]: I EIT
> > eitscanner.cpp:143 (run) EITScanner (5): Now looking for EIT data on
> > multiplex of channel 702
> > mythbackend.log:Mar 11 12:39:17  mythbackend: mythbackend[4306]: I EIT
> > eitcache.cpp:411 (PruneOldEntries) EITCache: Pruning all entries that
> > ended before UTC 2019-03-10T19:43:43Z
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190311/571f0668/attachment.html>

From mwedel at sonic.net  Tue Mar 12 05:09:15 2019
From: mwedel at sonic.net (Mark Wedel)
Date: Mon, 11 Mar 2019 22:09:15 -0700
Subject: [mythtv-users] Switching from SchedulesDirect to EIT
In-Reply-To: <CAAme0Obffx_jSGT8+PdMDrKgOwvuD66dpogqBo-0REsD1u=9fg@mail.gmail.com>
References: <CAAme0OZ4VDWLszMsv+c3ox8r2d1qVsNKE8J=R=V5sz5kdw_xxg@mail.gmail.com>
 <a8a691b4-858a-90ee-1578-71512d117401@gmail.com>
 <CAAme0Obffx_jSGT8+PdMDrKgOwvuD66dpogqBo-0REsD1u=9fg@mail.gmail.com>
Message-ID: <ec9c35ad-c93f-72fa-4ac9-9ef9d1c92a83@sonic.net>

On 03/11/2019 09:49 PM, Tom Harris wrote:
> 
<snip>
> I have tweaked all the settings I could find.? ?But, no luck.
> I have read other reports of EIT usage with HDhomerun devices, but I'm beginning 
> to doubt it.? ?It's a QAM (cable) device, and maybe the EIT data is not mirrored 
> into the cable transmission.
> 
> In any case, I decided to not mess with it and just renewed schedulesdirect instead.

When first setting up, I used EIT data (getting it via OTA).  It mostly worked, 
but the quality of the data was inferior to schedulesdirect.

Thins like episode ids, air dates, descriptions just were not as good.  I'm not 
sure, but SD seems to 'standardize' the data no matter what channel is 
broadcasting it (so if show A is on channel 2, and repeated sometime later on 
channel 3, it will be properly marked as a dupe), where is with EIT, there may 
be differences so that reshowing may be considered different and thus re-recorded.

In the end, I realized the nominal charge for SD was well worth the improved 
quality of the data (you get what you pay for, I suppose)


From stephen_agent at jsw.gen.nz  Tue Mar 12 10:52:05 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Tue, 12 Mar 2019 23:52:05 +1300
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <CAH8UtKPiWUWQGFh8OjbpVkvodh6XDaHUqCUJDh=Qmengww4WdQ@mail.gmail.com>
References: <0ji98elqkapt7bjuuetnortq4riha9rv51@4ax.com>
 <CAC+xXWMqELDa5fzcmWKeWBCJwVCbK+XQbhoE669CTyZzpjkQGQ@mail.gmail.com>
 <CAH8UtKOHCfM43E_jH16Fm_VBcYnM0=5E+jKJg+F7+G0yMUokdQ@mail.gmail.com>
 <CAH8UtKNXkyVoVj2wEZeVEF+c1N7NwOTvnk7Y5AxUcpBF6cTijw@mail.gmail.com>
 <CAH8UtKPUayeJnW=Hhi1FemhDD2E2bRpiz+1toee8hsOzB+=+pg@mail.gmail.com>
 <vafb8epf2t7qa7s2ncev7ebovq25edn0ls@4ax.com>
 <CAH8UtKPiWUWQGFh8OjbpVkvodh6XDaHUqCUJDh=Qmengww4WdQ@mail.gmail.com>
Message-ID: <583f8eth3gbkffs0cnq5n2e8ladobmh5lo@4ax.com>

On Mon, 11 Mar 2019 09:41:08 -0700, you wrote:

>On Sun, Mar 10, 2019 at 7:31 PM Stephen Worthington <
>stephen_agent at jsw.gen.nz> wrote:
>
>> On Sun, 10 Mar 2019 14:59:19 -0700, you wrote:
>>
>> >I added a 10 second delay and the problem is gone, no duplicate instances
>> >of myth. Maybe 3 seconds would work but definitely a race condition.
>> Other
>> >than the delay, the code is the same as original.
>> >
>> >In fairness to the code, my test is not real life.  Typically if I were to
>> >do a CTRL-ALT-BS it would be because myth was frozen or missing. I don't
>> >know that I ever did a CTRL-ALT-BS just as a test with Myth running. The
>> >timing might be different and the service might be killed faster if it is
>> >actually frozen. Or maybe I am wrong and this really is an issue.  Either
>> >way, it should not keep piling on instances of mythfrontend.  But at least
>> >I think we know what is going on now.
>> >
>> >Allen
>>
>> Using a delay to fix a race condition is usually a bad idea -
>> something happens which changes the timing, such as a bit of swapping
>> going on, and then the problem is back again.
>>
>> Unfortunately, mythfrontend does die quite often for me.  The usual
>> cause is playing a downloaded video file.  I have quite a few that it
>> can not handle, and either it dies, or locks up and I have to kill it.
>> Some of the deaths leave behind "assert failed" messages.  But if you
>> do not normally play such files, then mythfrontend can be very
>> reliable and not need the wrapper script.
>>
>> It looks like the wrapper script needs to be able to detect that the
>> script itself is still running and to exit if it can see another copy
>> of itself.  This should work to do that:
>>
>> pid=$(ps -ef | grep '/bin/sh /usr/bin/mythfrontend --service' | grep
>> -v grep | awk '{print $2}')
>> if [ ${#pid} -ne 0 ]; then
>>     exit 0
>> fi
>> _______________________________________________
>>
>> I do not understand why this does not work but I am no script expert so I
>am not sure what exactly is going on with ${#pid} and how that relates to
>the initial pid. Perhaps there is a $ missing or misplaced on the first
>line?  I did run some tests.
>
>*dad at NewMyth:~$ ps -ef | grep '/bin/sh /usr/bin/mythfrontend --service' |
>grep -v grep*
>*dad       2310     1  0 09:17 ?        00:00:00 /bin/sh
>/usr/bin/mythfrontend --service*
>*dad       2605     1  0 09:17 ?        00:00:00 /bin/sh
>/usr/bin/mythfrontend --service*
>*dad       2961  2939  0 09:17 ?        00:00:00 /bin/sh
>/usr/bin/mythfrontend --service*
>
>And
>
>*dad at NewMyth:~$ ps -ef | grep '/bin/sh /usr/bin/mythfrontend --service' |
>grep -v grep | awk '{print $2}'*
>*2310*
>*2605*
>*2961*
>
>For now I will just run mythfrontend without the --service option.  That
>should be fine for my needs. I am still willing to troubleshoot this if you
>think that would be useful so let me know.
>
>I wish to thank both Stephen and Ian for your help.
>
>Allen

$(#pid} is the number of characters in the $pid string.  If there are
any copies of mythfrontend running, then the $pid string should be a
list of the PIDs for those copies (actually, a list of the PIDs of the
bash tasks running those copies of the scripts).  So if there are no
other copies of mythfrontend running, $pid should be an empty string,
and ${#pid} should be 0.  I tested it using this script (t1.sh):

#!/bin/bash
pid=$(ps -ef | grep '/bin/sh /usr/bin/mythfrontend --service' | grep
-v grep | awk '{print $2}')
echo $pid
echo ${#pid}
if [ ${#pid} -ne 0 ]; then
    echo "pid != 0"
fi

On my MythTV box, it displays the "pid != 0" string whenever it finds
a copy of the mythfrontend script running.  If I add an extraneous
character to the grep string (eg an extra d on the end of
"mythfrontend", it gets no matches and continues on to the end of the
script without doing the echo.

From allen.p.edwards at gmail.com  Tue Mar 12 14:30:49 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Tue, 12 Mar 2019 07:30:49 -0700
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <583f8eth3gbkffs0cnq5n2e8ladobmh5lo@4ax.com>
References: <0ji98elqkapt7bjuuetnortq4riha9rv51@4ax.com>
 <CAC+xXWMqELDa5fzcmWKeWBCJwVCbK+XQbhoE669CTyZzpjkQGQ@mail.gmail.com>
 <CAH8UtKOHCfM43E_jH16Fm_VBcYnM0=5E+jKJg+F7+G0yMUokdQ@mail.gmail.com>
 <CAH8UtKNXkyVoVj2wEZeVEF+c1N7NwOTvnk7Y5AxUcpBF6cTijw@mail.gmail.com>
 <CAH8UtKPUayeJnW=Hhi1FemhDD2E2bRpiz+1toee8hsOzB+=+pg@mail.gmail.com>
 <vafb8epf2t7qa7s2ncev7ebovq25edn0ls@4ax.com>
 <CAH8UtKPiWUWQGFh8OjbpVkvodh6XDaHUqCUJDh=Qmengww4WdQ@mail.gmail.com>
 <583f8eth3gbkffs0cnq5n2e8ladobmh5lo@4ax.com>
Message-ID: <CAH8UtKPMTTLJK0XbUSCJsbL5bpbGJ2ykTQuZpwndcjtRStSOzw@mail.gmail.com>

On Tue, Mar 12, 2019 at 3:53 AM Stephen Worthington <
stephen_agent at jsw.gen.nz> wrote:

> On Mon, 11 Mar 2019 09:41:08 -0700, you wrote:
>
> >On Sun, Mar 10, 2019 at 7:31 PM Stephen Worthington <
> >stephen_agent at jsw.gen.nz> wrote:
> >
> >> On Sun, 10 Mar 2019 14:59:19 -0700, you wrote:
> >>
> >> >I added a 10 second delay and the problem is gone, no duplicate
> instances
> >> >of myth. Maybe 3 seconds would work but definitely a race condition.
> >> Other
> >> >than the delay, the code is the same as original.
> >> >
> >> >In fairness to the code, my test is not real life.  Typically if I
> were to
> >> >do a CTRL-ALT-BS it would be because myth was frozen or missing. I
> don't
> >> >know that I ever did a CTRL-ALT-BS just as a test with Myth running.
> The
> >> >timing might be different and the service might be killed faster if it
> is
> >> >actually frozen. Or maybe I am wrong and this really is an issue.
> Either
> >> >way, it should not keep piling on instances of mythfrontend.  But at
> least
> >> >I think we know what is going on now.
> >> >
> >> >Allen
> >>
> >> Using a delay to fix a race condition is usually a bad idea -
> >> something happens which changes the timing, such as a bit of swapping
> >> going on, and then the problem is back again.
> >>
> >> Unfortunately, mythfrontend does die quite often for me.  The usual
> >> cause is playing a downloaded video file.  I have quite a few that it
> >> can not handle, and either it dies, or locks up and I have to kill it.
> >> Some of the deaths leave behind "assert failed" messages.  But if you
> >> do not normally play such files, then mythfrontend can be very
> >> reliable and not need the wrapper script.
> >>
> >> It looks like the wrapper script needs to be able to detect that the
> >> script itself is still running and to exit if it can see another copy
> >> of itself.  This should work to do that:
> >>
> >> pid=$(ps -ef | grep '/bin/sh /usr/bin/mythfrontend --service' | grep
> >> -v grep | awk '{print $2}')
> >> if [ ${#pid} -ne 0 ]; then
> >>     exit 0
> >> fi
> >> _______________________________________________
> >>
> >> I do not understand why this does not work but I am no script expert so
> I
> >am not sure what exactly is going on with ${#pid} and how that relates to
> >the initial pid. Perhaps there is a $ missing or misplaced on the first
> >line?  I did run some tests.
> >
> >*dad at NewMyth:~$ ps -ef | grep '/bin/sh /usr/bin/mythfrontend --service' |
> >grep -v grep*
> >*dad       2310     1  0 09:17 ?        00:00:00 /bin/sh
> >/usr/bin/mythfrontend --service*
> >*dad       2605     1  0 09:17 ?        00:00:00 /bin/sh
> >/usr/bin/mythfrontend --service*
> >*dad       2961  2939  0 09:17 ?        00:00:00 /bin/sh
> >/usr/bin/mythfrontend --service*
> >
> >And
> >
> >*dad at NewMyth:~$ ps -ef | grep '/bin/sh /usr/bin/mythfrontend --service' |
> >grep -v grep | awk '{print $2}'*
> >*2310*
> >*2605*
> >*2961*
> >
> >For now I will just run mythfrontend without the --service option.  That
> >should be fine for my needs. I am still willing to troubleshoot this if
> you
> >think that would be useful so let me know.
> >
> >I wish to thank both Stephen and Ian for your help.
> >
> >Allen
>
> $(#pid} is the number of characters in the $pid string.  If there are
> any copies of mythfrontend running, then the $pid string should be a
> list of the PIDs for those copies (actually, a list of the PIDs of the
> bash tasks running those copies of the scripts).  So if there are no
> other copies of mythfrontend running, $pid should be an empty string,
> and ${#pid} should be 0.  I tested it using this script (t1.sh):
>
> #!/bin/bash
> pid=$(ps -ef | grep '/bin/sh /usr/bin/mythfrontend --service' | grep
> -v grep | awk '{print $2}')
> echo $pid
> echo ${#pid}
> if [ ${#pid} -ne 0 ]; then
>     echo "pid != 0"
> fi
>
> On my MythTV box, it displays the "pid != 0" string whenever it finds
> a copy of the mythfrontend script running.  If I add an extraneous
> character to the grep string (eg an extra d on the end of
> "mythfrontend", it gets no matches and continues on to the end of the
> script without doing the echo.
> _______________________________________________
>
> I have not tested it yet but I think the problem I had was I copied and
pasted the script you wrote without changes and the word wrap that put a
return between grep and -v grep would generate an error.  I tested the
components of it but put it all on one line when I did that and did not
realize that the script would not run as posted.  Pretty stupid mistake on
my part.

Your script as it came across the email
pid=$(ps -ef | grep '/bin/sh /usr/bin/mythfrontend --service' | grep
-v grep | awk '{print $2}')
if [ ${#pid} -ne 0 ]; then
    exit 0
fi

A corrected version
pid=$(ps -ef | grep '/bin/sh /usr/bin/mythfrontend --service' | grep -v
grep | awk '{print $2}')
if [ ${#pid} -ne 0 ]; then
    exit 0
fi

I would be shocked if this did not work but can't test it now.

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190312/ab130c41/attachment.html>

From jharbestonus at gmail.com  Tue Mar 12 15:03:50 2019
From: jharbestonus at gmail.com (Jay Harbeston)
Date: Tue, 12 Mar 2019 11:03:50 -0400
Subject: [mythtv-users] Switching from SchedulesDirect to EIT
In-Reply-To: <ec9c35ad-c93f-72fa-4ac9-9ef9d1c92a83@sonic.net>
References: <CAAme0OZ4VDWLszMsv+c3ox8r2d1qVsNKE8J=R=V5sz5kdw_xxg@mail.gmail.com>
 <a8a691b4-858a-90ee-1578-71512d117401@gmail.com>
 <CAAme0Obffx_jSGT8+PdMDrKgOwvuD66dpogqBo-0REsD1u=9fg@mail.gmail.com>
 <ec9c35ad-c93f-72fa-4ac9-9ef9d1c92a83@sonic.net>
Message-ID: <87FC77A9-AC81-4B98-A280-923B9F727E73@gmail.com>



> On Mar 12, 2019, at 1:09 AM, Mark Wedel <mwedel at sonic.net> wrote:
> 
> On 03/11/2019 09:49 PM, Tom Harris wrote:
> <snip>
>> I have tweaked all the settings I could find.   But, no luck.
>> I have read other reports of EIT usage with HDhomerun devices, but I'm beginning to doubt it.   It's a QAM (cable) device, and maybe the EIT data is not mirrored into the cable transmission.
>> In any case, I decided to not mess with it and just renewed schedulesdirect instead.
> 
> When first setting up, I used EIT data (getting it via OTA).  It mostly worked, but the quality of the data was inferior to schedulesdirect.
> 
> Thins like episode ids, air dates, descriptions just were not as good.  I'm not sure, but SD seems to 'standardize' the data no matter what channel is broadcasting it (so if show A is on channel 2, and repeated sometime later on channel 3, it will be properly marked as a dupe), where is with EIT, there may be differences so that reshowing may be considered different and thus re-recorded.
> 
> In the end, I realized the nominal charge for SD was well worth the improved quality of the data (you get what you pay for, I suppose)
> 


From what I have found when using EIT OTA, sometimes there is a description, sometimes not, whereas using SD nearly always gives a description. 

Also, I never get subtitle or season / episode over OTA.

I use EIT OTA only for experimentation on a separate mythtv from my standard mythtv.

I am using OTA as above from North Carolina.  Your mileage may vary depending on where you are.  SD is worth the $25 / year for good data.

Regards,

From allen.p.edwards at gmail.com  Tue Mar 12 15:15:41 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Tue, 12 Mar 2019 08:15:41 -0700
Subject: [mythtv-users] Switching from SchedulesDirect to EIT
In-Reply-To: <87FC77A9-AC81-4B98-A280-923B9F727E73@gmail.com>
References: <CAAme0OZ4VDWLszMsv+c3ox8r2d1qVsNKE8J=R=V5sz5kdw_xxg@mail.gmail.com>
 <a8a691b4-858a-90ee-1578-71512d117401@gmail.com>
 <CAAme0Obffx_jSGT8+PdMDrKgOwvuD66dpogqBo-0REsD1u=9fg@mail.gmail.com>
 <ec9c35ad-c93f-72fa-4ac9-9ef9d1c92a83@sonic.net>
 <87FC77A9-AC81-4B98-A280-923B9F727E73@gmail.com>
Message-ID: <CAH8UtKNr-=Dc7uKqOaUNeHOp3GLT4DMLtD3qeTFsy7KZxJ1S9A@mail.gmail.com>

With the switchover from Mythbuntu8 to Mythbuntu16 recently I initially had
SD and EIT on.  The EIT would erase all the good stuff on my schedules and
I would lose a week or more of data. Switching EIT off fixed it.

The other thing I love about SD is when I walk through Costco and the Dish
network guys ask how much I pay for TV I can say $25 a year. I love the
reactions. It is definitely worth the small fee.

Allen

On Tue, Mar 12, 2019 at 8:04 AM Jay Harbeston <jharbestonus at gmail.com>
wrote:

>
>
> > On Mar 12, 2019, at 1:09 AM, Mark Wedel <mwedel at sonic.net> wrote:
> >
> > On 03/11/2019 09:49 PM, Tom Harris wrote:
> > <snip>
> >> I have tweaked all the settings I could find.   But, no luck.
> >> I have read other reports of EIT usage with HDhomerun devices, but I'm
> beginning to doubt it.   It's a QAM (cable) device, and maybe the EIT data
> is not mirrored into the cable transmission.
> >> In any case, I decided to not mess with it and just renewed
> schedulesdirect instead.
> >
> > When first setting up, I used EIT data (getting it via OTA).  It mostly
> worked, but the quality of the data was inferior to schedulesdirect.
> >
> > Thins like episode ids, air dates, descriptions just were not as good.
> I'm not sure, but SD seems to 'standardize' the data no matter what channel
> is broadcasting it (so if show A is on channel 2, and repeated sometime
> later on channel 3, it will be properly marked as a dupe), where is with
> EIT, there may be differences so that reshowing may be considered different
> and thus re-recorded.
> >
> > In the end, I realized the nominal charge for SD was well worth the
> improved quality of the data (you get what you pay for, I suppose)
> >
>
>
> From what I have found when using EIT OTA, sometimes there is a
> description, sometimes not, whereas using SD nearly always gives a
> description.
>
> Also, I never get subtitle or season / episode over OTA.
>
> I use EIT OTA only for experimentation on a separate mythtv from my
> standard mythtv.
>
> I am using OTA as above from North Carolina.  Your mileage may vary
> depending on where you are.  SD is worth the $25 / year for good data.
>
> Regards,
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190312/d0ba2682/attachment-0001.html>

From allen.p.edwards at gmail.com  Tue Mar 12 20:28:48 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Tue, 12 Mar 2019 13:28:48 -0700
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <CAH8UtKPMTTLJK0XbUSCJsbL5bpbGJ2ykTQuZpwndcjtRStSOzw@mail.gmail.com>
References: <0ji98elqkapt7bjuuetnortq4riha9rv51@4ax.com>
 <CAC+xXWMqELDa5fzcmWKeWBCJwVCbK+XQbhoE669CTyZzpjkQGQ@mail.gmail.com>
 <CAH8UtKOHCfM43E_jH16Fm_VBcYnM0=5E+jKJg+F7+G0yMUokdQ@mail.gmail.com>
 <CAH8UtKNXkyVoVj2wEZeVEF+c1N7NwOTvnk7Y5AxUcpBF6cTijw@mail.gmail.com>
 <CAH8UtKPUayeJnW=Hhi1FemhDD2E2bRpiz+1toee8hsOzB+=+pg@mail.gmail.com>
 <vafb8epf2t7qa7s2ncev7ebovq25edn0ls@4ax.com>
 <CAH8UtKPiWUWQGFh8OjbpVkvodh6XDaHUqCUJDh=Qmengww4WdQ@mail.gmail.com>
 <583f8eth3gbkffs0cnq5n2e8ladobmh5lo@4ax.com>
 <CAH8UtKPMTTLJK0XbUSCJsbL5bpbGJ2ykTQuZpwndcjtRStSOzw@mail.gmail.com>
Message-ID: <CAH8UtKPT-28-jWDUPPm7N2E1eog0dCdRB48KOERqNx-vtnGcwg@mail.gmail.com>

On Tue, Mar 12, 2019 at 7:30 AM Allen Edwards <allen.p.edwards at gmail.com>
wrote:

>
>
> On Tue, Mar 12, 2019 at 3:53 AM Stephen Worthington <
> stephen_agent at jsw.gen.nz> wrote:
>
>> On Mon, 11 Mar 2019 09:41:08 -0700, you wrote:
>>
>> >On Sun, Mar 10, 2019 at 7:31 PM Stephen Worthington <
>> >stephen_agent at jsw.gen.nz> wrote:
>> >
>> >> On Sun, 10 Mar 2019 14:59:19 -0700, you wrote:
>> >>
>> >> >I added a 10 second delay and the problem is gone, no duplicate
>> instances
>> >> >of myth. Maybe 3 seconds would work but definitely a race condition.
>> >> Other
>> >> >than the delay, the code is the same as original.
>> >> >
>> >> >In fairness to the code, my test is not real life.  Typically if I
>> were to
>> >> >do a CTRL-ALT-BS it would be because myth was frozen or missing. I
>> don't
>> >> >know that I ever did a CTRL-ALT-BS just as a test with Myth running.
>> The
>> >> >timing might be different and the service might be killed faster if
>> it is
>> >> >actually frozen. Or maybe I am wrong and this really is an issue.
>> Either
>> >> >way, it should not keep piling on instances of mythfrontend.  But at
>> least
>> >> >I think we know what is going on now.
>> >> >
>> >> >Allen
>> >>
>> >> Using a delay to fix a race condition is usually a bad idea -
>> >> something happens which changes the timing, such as a bit of swapping
>> >> going on, and then the problem is back again.
>> >>
>> >> Unfortunately, mythfrontend does die quite often for me.  The usual
>> >> cause is playing a downloaded video file.  I have quite a few that it
>> >> can not handle, and either it dies, or locks up and I have to kill it.
>> >> Some of the deaths leave behind "assert failed" messages.  But if you
>> >> do not normally play such files, then mythfrontend can be very
>> >> reliable and not need the wrapper script.
>> >>
>> >> It looks like the wrapper script needs to be able to detect that the
>> >> script itself is still running and to exit if it can see another copy
>> >> of itself.  This should work to do that:
>> >>
>> >> pid=$(ps -ef | grep '/bin/sh /usr/bin/mythfrontend --service' | grep
>> >> -v grep | awk '{print $2}')
>> >> if [ ${#pid} -ne 0 ]; then
>> >>     exit 0
>> >> fi
>> >> _______________________________________________
>> >>
>> >> I do not understand why this does not work but I am no script expert
>> so I
>> >am not sure what exactly is going on with ${#pid} and how that relates to
>> >the initial pid. Perhaps there is a $ missing or misplaced on the first
>> >line?  I did run some tests.
>> >
>> >*dad at NewMyth:~$ ps -ef | grep '/bin/sh /usr/bin/mythfrontend --service'
>> |
>> >grep -v grep*
>> >*dad       2310     1  0 09:17 ?        00:00:00 /bin/sh
>> >/usr/bin/mythfrontend --service*
>> >*dad       2605     1  0 09:17 ?        00:00:00 /bin/sh
>> >/usr/bin/mythfrontend --service*
>> >*dad       2961  2939  0 09:17 ?        00:00:00 /bin/sh
>> >/usr/bin/mythfrontend --service*
>> >
>> >And
>> >
>> >*dad at NewMyth:~$ ps -ef | grep '/bin/sh /usr/bin/mythfrontend --service'
>> |
>> >grep -v grep | awk '{print $2}'*
>> >*2310*
>> >*2605*
>> >*2961*
>> >
>> >For now I will just run mythfrontend without the --service option.  That
>> >should be fine for my needs. I am still willing to troubleshoot this if
>> you
>> >think that would be useful so let me know.
>> >
>> >I wish to thank both Stephen and Ian for your help.
>> >
>> >Allen
>>
>> $(#pid} is the number of characters in the $pid string.  If there are
>> any copies of mythfrontend running, then the $pid string should be a
>> list of the PIDs for those copies (actually, a list of the PIDs of the
>> bash tasks running those copies of the scripts).  So if there are no
>> other copies of mythfrontend running, $pid should be an empty string,
>> and ${#pid} should be 0.  I tested it using this script (t1.sh):
>>
>> #!/bin/bash
>> pid=$(ps -ef | grep '/bin/sh /usr/bin/mythfrontend --service' | grep
>> -v grep | awk '{print $2}')
>> echo $pid
>> echo ${#pid}
>> if [ ${#pid} -ne 0 ]; then
>>     echo "pid != 0"
>> fi
>>
>> On my MythTV box, it displays the "pid != 0" string whenever it finds
>> a copy of the mythfrontend script running.  If I add an extraneous
>> character to the grep string (eg an extra d on the end of
>> "mythfrontend", it gets no matches and continues on to the end of the
>> script without doing the echo.
>> _______________________________________________
>>
>> I have not tested it yet but I think the problem I had was I copied and
> pasted the script you wrote without changes and the word wrap that put a
> return between grep and -v grep would generate an error.  I tested the
> components of it but put it all on one line when I did that and did not
> realize that the script would not run as posted.  Pretty stupid mistake on
> my part.
>
> Your script as it came across the email
> pid=$(ps -ef | grep '/bin/sh /usr/bin/mythfrontend --service' | grep
> -v grep | awk '{print $2}')
> if [ ${#pid} -ne 0 ]; then
>     exit 0
> fi
>
> A corrected version
> pid=$(ps -ef | grep '/bin/sh /usr/bin/mythfrontend --service' | grep -v
> grep | awk '{print $2}')
> if [ ${#pid} -ne 0 ]; then
>     exit 0
> fi
>
> I would be shocked if this did not work but can't test it now.
>
> Allen
>
>
>
I put these lines in the beginning of /usr/share/mythtv/mythfrontend.sh

*pid=$(ps -ef | grep '/bin/sh /usr/bin/mythfrontend --service' | grep -v
grep | awk '{print $2}')*
*if [ ${#pid} -ne 0 ]; then*
*    exit 0*
*fi*

Myth would not start at power up or on a CTRL-ALT-BS.   I cannot find my
error.

Back to no *--service* option

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190312/00960d47/attachment.html>

From support at drdos.info  Tue Mar 12 20:41:01 2019
From: support at drdos.info (Doug Lytle)
Date: Tue, 12 Mar 2019 16:41:01 -0400 (EDT)
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <CAH8UtKPT-28-jWDUPPm7N2E1eog0dCdRB48KOERqNx-vtnGcwg@mail.gmail.com>
References: <0ji98elqkapt7bjuuetnortq4riha9rv51@4ax.com>
 <CAH8UtKNXkyVoVj2wEZeVEF+c1N7NwOTvnk7Y5AxUcpBF6cTijw@mail.gmail.com>
 <CAH8UtKPUayeJnW=Hhi1FemhDD2E2bRpiz+1toee8hsOzB+=+pg@mail.gmail.com>
 <vafb8epf2t7qa7s2ncev7ebovq25edn0ls@4ax.com>
 <CAH8UtKPiWUWQGFh8OjbpVkvodh6XDaHUqCUJDh=Qmengww4WdQ@mail.gmail.com>
 <583f8eth3gbkffs0cnq5n2e8ladobmh5lo@4ax.com>
 <CAH8UtKPMTTLJK0XbUSCJsbL5bpbGJ2ykTQuZpwndcjtRStSOzw@mail.gmail.com>
 <CAH8UtKPT-28-jWDUPPm7N2E1eog0dCdRB48KOERqNx-vtnGcwg@mail.gmail.com>
Message-ID: <sig.39746496bc.924068897.2879.1552423261728.JavaMail.zimbra@drdos.info>

I find it easier to use pidof

I'm using bash:

if [ ! "$(pidof mythfrontend)" ]                                                                                                                                                                                                                                               
then                                                                                                                                                                                                                                                                           
        echo "Mythfrontend is not started. Starting Mythfrontend..."                                                                                                                                                                                                           
        sleep 3                                                                                                                                                                                                                                                                
        DISPLAY=:0 xset -dpms                                                                                                                                                                                                                                                  
        ulimit -c unlimited                                                                                                                                                                                                                                                    
        DISPLAY=:0 mythfrontend --syslog local7 -q 2>&1 &                                                                                                                                                                                                                      
else                                                                                                                                                                                                                                                                           
        echo "Mythfrontend is already started."                                                                                                                                                                                                                                
                                                                                                                                                                                                                                                                               
fi

Doug

From veehexx at zoho.com  Tue Mar 12 20:51:45 2019
From: veehexx at zoho.com (Tim Draper)
Date: Tue, 12 Mar 2019 20:51:45 +0000
Subject: [mythtv-users] git master 0e7e57f commit - livetv?
In-Reply-To: <e7e34976-60c2-75fe-cbae-9decdf1853f6@gmail.com>
References: <16954762a44.11a048d9478619.7927489630634130750@zoho.com>
 <e7e34976-60c2-75fe-cbae-9decdf1853f6@gmail.com>
Message-ID: <16973abfa06.10b6409d9322712.5609019069326271649@zoho.com>

---- On Wed, 06 Mar 2019 20:17:22 +0000 Peter Bennett <pb.mythtv at gmail.com> wrote ----
 > Try running mythfrontend with -v playback. See if you see messages like 
 > this repeated many times. If so this should fix it. Otherwise, probably not. 
 >  
 > AFD: Selected FPS is 50 (avg 25 codec 0 container 90000 estimated 50) 
 > AFD: avFPS(50) != seqFPS(25) 
 > Player(1): SetFrameInterval ps:1 scan:3 
 > VidOutGL: InputChanged(1920,1080,1.77778) H.264 MEDIACODEC->H.264 MEDIACODEC 
 > DispInfo: rate:59.9401 h:1080 w:1920 xdpi:213 ydpi:213 
 > Player(1): ClearAfterSeek(1) 
 > Player(1): LoadFilters(''..) -> 0x0 
 > Player(1): detectInterlace(Detect Scan, Interlaced Scan, 25, 1080) 
 > ->Interlaced Scan 
 >  
 > If there are no complaints or problems reported I will move it to v30 in 
 > a week or so. 

wasn't my problem it seems, but using -v playback has shown "...Pause to allow live tv catch up...." multiple times a second when i get the stuttering.

I'm playing around with the deinterlacers as they have caused various minor but annoying playback issues in the past. currently on vaapi2/hw-gl options as the hw-va methods always had pros & cons depending on what i'm watching.


From jam at tigger.ws  Tue Mar 12 23:11:17 2019
From: jam at tigger.ws (jam at tigger.ws)
Date: Wed, 13 Mar 2019 07:11:17 +0800
Subject: [mythtv-users] HDhomerun quad
Message-ID: <53AA18AE-B076-4CD1-AC55-49F6708D7090@tigger.ws>

Hi ? this may be useful information if you are considering HDhome run.

I don?t think it plays nicely with myth.
I?ve had mostly good results in the weeks since I purchased it.

last night my regular schedule failed and my ?Watch Recordings? looked like this:

x Q&A	                		03/11	9:37 PM
x Q&A             			03/11	9:37 PM
x Media Watch              		03/11	9:21 PM
x Media Watch            		03/11	9:21 PM
x FourCorners             		03/11	8:35 PM
x FourCorners              		03/11	8:35 PM
x FourCorners           		03/11	8:35 PM
x FourCorners           		03/11	8:34 PM
x FourCorners               		03/11	8:35 PM
x FourCorners             		03/11	8:34 PM
x Predator               		03/11	8:30 PM
x Predator              		03/11	8:30 PM
x Michael Mosley: Trust Me I?m A Doctor	03/11	8:29 PM
x Michael Mosley: Trust Me I?m A Doctor	03/11	8:29 PM
  Michael Mosley: Trust Me I?m A Doctor	03/11	8:29 PM

When the single recording ended I used VLC to watch each channel.
I then scheduled 4 programs to record (immediatly).
All 4 recorded.

Splunking the logs gave some hints:

2019-03-11 20:29:37.272508 E [11966/11977] TVRecEvent recorders/hdhrstreamhandler.cpp:481 (TunerSet) - HDHRSH(12
51AA81-0): DeviceSet(channel auto:184500000): ERROR: resource locked by 192.168.5.61
2019-03-11 20:29:37.272515 E [11966/11977] TVRecEvent recorders/dtvchannel.cpp:311 (SetChannelByString) - DTVChan[5](1251AA81-0): SetChannelByString(30): Tuning to frequency.
2019-03-11 20:29:37.274398 E [11966/11977] TVRecEvent dtvmultiplex.cpp:246 (ParseDVB_S_and_C) - DTVMux: Invalid symbol rate parameter '0', aborting.
2019-03-11 20:29:37.274435 E [11966/11977] TVRecEvent recorders/dtvchannel.cpp:300 (SetChannelByString) - DTVChan[5](1251AA81-0): SetChannelByString(30): Failed to initialize multiplex options
2019-03-11 20:29:37.274450 E [11966/11977] TVRecEvent tv_rec.cpp:3743 (TuningFrequency) - TVRec[5]: Failed to set channel to 30. Reverting to kState_None
2019-03-11 20:29:37.274473 I [11966/11977] TVRecEvent tv_rec.cpp:1090 (HandleStateChange) - TVRec[5]: Changing from RecordingOnly to None
2019-03-11 20:29:37.298281 I [11966/11966] CoreContext scheduler.cpp:735 (UpdateRecStatus) - Updating status for "Michael Mosley: Trust Me, I'm A Doctor" on cardid [5] (Tuning => Recorder Failed)
2019-03-11 20:29:37.299695 E [11966/11977] TVRecEvent recorders/hdhrstreamhandler.cpp:481 (TunerSet) - HDHRSH(1251AA81-0): DeviceSet(channel none): ERROR: resource locked by 192.168.5.61
2019-03-11 20:29:37.299757 E [11966/11989] Scheduler scheduler.cpp:798 (ChangeRecordingEnd) - Failed to change end time on card 5 to 2019-03-11T13:28:38Z
2019-03-11 20:29:37.312319 I [11966/11989] Scheduler scheduler.cpp:2461 (HandleReschedule) - 
Reschedule interrupted, will retry
2019-03-11 20:29:37.312402 I [11966/11989] Scheduler scheduler.cpp:2357 (HandleReschedule) - Reschedule requested for CHECK -9 541 0 UpdateRecStatus2 | Michael Mosley: Trust Me, I'm A Doctor |  | Michael Mosley finds out whether a glass of wine can protect your blood vessels from the harmful effects of junk food. Giles Yeo sets out to test home breathalyser kits. | perth.sbshd.sbs.au/948351
2019-03-11 20:29:37.313282 I [11966/11989] Scheduler scheduler.cpp:2357 (HandleReschedule) - Reschedule requested for PLACE Interrupted
2019-03-11 20:29:37.341695 I [11966/11989] Scheduler scheduler.cpp:2470 (HandleReschedule) - Scheduled 60 itemsmythbackend.20190310101333.11966.log lines 9396-9409/10187 93%packet_write_wait: Connection to 192.168.5.33 port 22: Broken pipe

I reverted to my Haupague dual USB tuner. All seems to be working correctly. I ordered a second dual USB tuner. If anybody wants an Australian HDhomerun make me an offer (mail me) and it is yours.

Cheers
James

From jam at tigger.ws  Tue Mar 12 23:49:08 2019
From: jam at tigger.ws (jam at tigger.ws)
Date: Wed, 13 Mar 2019 07:49:08 +0800
Subject: [mythtv-users] Switching from SchedulesDirect to EIT
In-Reply-To: <mailman.73.1552403769.1604.mythtv-users@mythtv.org>
References: <mailman.73.1552403769.1604.mythtv-users@mythtv.org>
Message-ID: <E97CE7AF-A850-4D7F-8988-D97D0E079632@tigger.ws>



> On 12 Mar 2019, at 11:16 pm, mythtv-users-request at mythtv.org wrote:
> 
>> On 03/11/2019 09:49 PM, Tom Harris wrote:
>> <snip>
>>> I have tweaked all the settings I could find.   But, no luck.
>>> I have read other reports of EIT usage with HDhomerun devices, but I'm beginning to doubt it.   It's a QAM (cable) device, and maybe the EIT data is not mirrored into the cable transmission.
>>> In any case, I decided to not mess with it and just renewed schedulesdirect instead.
>> 
>> When first setting up, I used EIT data (getting it via OTA).  It mostly worked, but the quality of the data was inferior to schedulesdirect.
>> 
>> Thins like episode ids, air dates, descriptions just were not as good.  I'm not sure, but SD seems to 'standardize' the data no matter what channel is broadcasting it (so if show A is on channel 2, and repeated sometime later on channel 3, it will be properly marked as a dupe), where is with EIT, there may be differences so that reshowing may be considered different and thus re-recorded.
>> 
>> In the end, I realized the nominal charge for SD was well worth the improved quality of the data (you get what you pay for, I suppose)
>> 
> 
> 
> From what I have found when using EIT OTA, sometimes there is a description, sometimes not, whereas using SD nearly always gives a description. 
> 
> Also, I never get subtitle or season / episode over OTA.
> 
> I use EIT OTA only for experimentation on a separate mythtv from my standard mythtv.
> 
> I am using OTA as above from North Carolina.  Your mileage may vary depending on where you are.  SD is worth the $25 / year for good data.

In Australia the EPG and it?s data are mandated by the regulator and it is better than the oz grabbler shepard being more upto date.
Using hDhomerun with 1 channel [x] to get EPG data BUT the EPG gatherer does take HOURS to get all the data.
I?ve never bothered to check the EPG process but if I turn ON my samsung TV then select program guide the data is all there including one channel that is never filled out (WTV) by mythtv and one channel that is mostly blank (Viceland HD). Perhaps the TV gathers data secretly when turned off.

James


From stephen_agent at jsw.gen.nz  Wed Mar 13 01:10:01 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Wed, 13 Mar 2019 14:10:01 +1300
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <sig.39746496bc.924068897.2879.1552423261728.JavaMail.zimbra@drdos.info>
References: <CAH8UtKPUayeJnW=Hhi1FemhDD2E2bRpiz+1toee8hsOzB+=+pg@mail.gmail.com>
 <vafb8epf2t7qa7s2ncev7ebovq25edn0ls@4ax.com>
 <CAH8UtKPiWUWQGFh8OjbpVkvodh6XDaHUqCUJDh=Qmengww4WdQ@mail.gmail.com>
 <583f8eth3gbkffs0cnq5n2e8ladobmh5lo@4ax.com>
 <CAH8UtKPMTTLJK0XbUSCJsbL5bpbGJ2ykTQuZpwndcjtRStSOzw@mail.gmail.com>
 <CAH8UtKPT-28-jWDUPPm7N2E1eog0dCdRB48KOERqNx-vtnGcwg@mail.gmail.com>
 <sig.39746496bc.924068897.2879.1552423261728.JavaMail.zimbra@drdos.info>
Message-ID: <6plg8et56ou1agij2r39q5mh4av9qisk0s@4ax.com>

On Tue, 12 Mar 2019 16:41:01 -0400 (EDT), you wrote:

>I find it easier to use pidof
>
>I'm using bash:
>
>if [ ! "$(pidof mythfrontend)" ]                                                                                                                                                                                                                                               
>then                                                                                                                                                                                                                                                                           
>        echo "Mythfrontend is not started. Starting Mythfrontend..."                                                                                                                                                                                                           
>        sleep 3                                                                                                                                                                                                                                                                
>        DISPLAY=:0 xset -dpms                                                                                                                                                                                                                                                  
>        ulimit -c unlimited                                                                                                                                                                                                                                                    
>        DISPLAY=:0 mythfrontend --syslog local7 -q 2>&1 &                                                                                                                                                                                                                      
>else                                                                                                                                                                                                                                                                           
>        echo "Mythfrontend is already started."                                                                                                                                                                                                                                
>                                                                                                                                                                                                                                                                               
>fi
>
>Doug

Using "pidof mythfrontend" will only find tasks called "mythfrontend".
There are no such tasks in Ubuntu, where the mythfrontend executable
file is renamed to "mythfrontend.real" and is run from a bash script
named "mythfrontend".  The task name for the bash script is "bash",
not "mythfrontend", so "pidof mythfrontend" will not find it either.
Hence I assume you can not be running Ubuntu.

From support at drdos.info  Wed Mar 13 01:39:51 2019
From: support at drdos.info (Doug Lytle)
Date: Tue, 12 Mar 2019 21:39:51 -0400
Subject: [mythtv-users] CTRL-ALT-BACKSPACE -> multiple instances of
 mythfrontend
In-Reply-To: <6plg8et56ou1agij2r39q5mh4av9qisk0s@4ax.com>
References: <CAH8UtKPUayeJnW=Hhi1FemhDD2E2bRpiz+1toee8hsOzB+=+pg@mail.gmail.com>
 <vafb8epf2t7qa7s2ncev7ebovq25edn0ls@4ax.com>
 <CAH8UtKPiWUWQGFh8OjbpVkvodh6XDaHUqCUJDh=Qmengww4WdQ@mail.gmail.com>
 <583f8eth3gbkffs0cnq5n2e8ladobmh5lo@4ax.com>
 <CAH8UtKPMTTLJK0XbUSCJsbL5bpbGJ2ykTQuZpwndcjtRStSOzw@mail.gmail.com>
 <CAH8UtKPT-28-jWDUPPm7N2E1eog0dCdRB48KOERqNx-vtnGcwg@mail.gmail.com>
 <sig.39746496bc.924068897.2879.1552423261728.JavaMail.zimbra@drdos.info>
 <6plg8et56ou1agij2r39q5mh4av9qisk0s@4ax.com>
Message-ID: <sig.5975a7792b.e499cb07-504b-2c09-d7c7-637cba00ddd3@drdos.info>

On 3/12/19 9:10 PM, Stephen Worthington wrote:
> The task name for the bash script is "bash",
> not "mythfrontend", so "pidof mythfrontend" will not find it either.
> Hence I assume you can not be running Ubuntu.

Debian and I compile from source,

Doug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190312/129e1405/attachment.html>

From klaas.de.waal at gmail.com  Wed Mar 13 11:30:03 2019
From: klaas.de.waal at gmail.com (Klaas de Waal)
Date: Wed, 13 Mar 2019 12:30:03 +0100
Subject: [mythtv-users] Switching from SchedulesDirect to EIT
In-Reply-To: <E97CE7AF-A850-4D7F-8988-D97D0E079632@tigger.ws>
References: <mailman.73.1552403769.1604.mythtv-users@mythtv.org>
 <E97CE7AF-A850-4D7F-8988-D97D0E079632@tigger.ws>
Message-ID: <CANcAQaMy9cg=nEyxx7vuHpxzN1nQ9=Tre9FqAS0BMuYaxsp+zw@mail.gmail.com>

On Wed, 13 Mar 2019 at 00:49, jam at tigger.ws <jam at tigger.ws> wrote:
>
>
>
> > On 12 Mar 2019, at 11:16 pm, mythtv-users-request at mythtv.org wrote:
> >
> >> On 03/11/2019 09:49 PM, Tom Harris wrote:
> >> <snip>
> >>> I have tweaked all the settings I could find.   But, no luck.
> >>> I have read other reports of EIT usage with HDhomerun devices, but I'm beginning to doubt it.   It's a QAM (cable) device, and maybe the EIT data is not mirrored into the cable transmission.
> >>> In any case, I decided to not mess with it and just renewed schedulesdirect instead.
> >>
> >> When first setting up, I used EIT data (getting it via OTA).  It mostly worked, but the quality of the data was inferior to schedulesdirect.
> >>
> >> Thins like episode ids, air dates, descriptions just were not as good.  I'm not sure, but SD seems to 'standardize' the data no matter what channel is broadcasting it (so if show A is on channel 2, and repeated sometime later on channel 3, it will be properly marked as a dupe), where is with EIT, there may be differences so that reshowing may be considered different and thus re-recorded.
> >>
> >> In the end, I realized the nominal charge for SD was well worth the improved quality of the data (you get what you pay for, I suppose)
> >>
> >
> >
> > From what I have found when using EIT OTA, sometimes there is a description, sometimes not, whereas using SD nearly always gives a description.
> >
> > Also, I never get subtitle or season / episode over OTA.
> >
> > I use EIT OTA only for experimentation on a separate mythtv from my standard mythtv.
> >
> > I am using OTA as above from North Carolina.  Your mileage may vary depending on where you are.  SD is worth the $25 / year for good data.
>
> In Australia the EPG and it?s data are mandated by the regulator and it is better than the oz grabbler shepard being more upto date.
> Using hDhomerun with 1 channel [x] to get EPG data BUT the EPG gatherer does take HOURS to get all the data.
> I?ve never bothered to check the EPG process but if I turn ON my samsung TV then select program guide the data is all there including one channel that is never filled out (WTV) by mythtv and one channel that is mostly blank (Viceland HD). Perhaps the TV gathers data secretly when turned off.
>
MythTV stores the EPG data into a database and that is a
compute-intensive process. MythTV processes only a fraction of the
information that is coming in to prevent recording failures due to
lack of processor resources. MythTV uses 5 minutes to receive all the
guide data from one transport stream. After 5 minutes the next
transport stream is tuned, so if you have 20 transport streams it can
take 100 minutes before all EPG data is received.  My TV does not have
the guide data immediately after power-on but within a minute all the
guide data is there. The TV stores the guide data only in memory so
that can be really quick. AFAIK, depending on the provider, it can be
that a transport stream carries only the guide data for the programs
on that transport stream or that it carries the guide data for all
transports. MythTV takes the conservative approach and scans all
transport streams. However, there is definitely room for improvement,
I would like MythTV to be as fast as my TV in picking up guide data.

Groetjes,
Klaas.

From jharbestonus at gmail.com  Wed Mar 13 13:16:57 2019
From: jharbestonus at gmail.com (Jay Harbeston)
Date: Wed, 13 Mar 2019 09:16:57 -0400
Subject: [mythtv-users] HDhomerun quad
In-Reply-To: <53AA18AE-B076-4CD1-AC55-49F6708D7090@tigger.ws>
References: <53AA18AE-B076-4CD1-AC55-49F6708D7090@tigger.ws>
Message-ID: <74A402AA-B968-43F3-85FF-12BD2FA0539F@gmail.com>



> On Mar 12, 2019, at 7:11 PM, jam at tigger.ws wrote:
> 
> Hi ? this may be useful information if you are considering HDhome run.
> 
> I don?t think it plays nicely with myth.
> I?ve had mostly good results in the weeks since I purchased it.
> 
> last night my regular schedule failed and my ?Watch Recordings? looked like this:
> 
> x Q&A	                		03/11	9:37 PM
> x Q&A             			03/11	9:37 PM
> x Media Watch              		03/11	9:21 PM
> x Media Watch            		03/11	9:21 PM
> x FourCorners             		03/11	8:35 PM
> x FourCorners              		03/11	8:35 PM
> x FourCorners           		03/11	8:35 PM
> x FourCorners           		03/11	8:34 PM
> x FourCorners               		03/11	8:35 PM
> x FourCorners             		03/11	8:34 PM
> x Predator               		03/11	8:30 PM
> x Predator              		03/11	8:30 PM
> x Michael Mosley: Trust Me I?m A Doctor	03/11	8:29 PM
> x Michael Mosley: Trust Me I?m A Doctor	03/11	8:29 PM
>  Michael Mosley: Trust Me I?m A Doctor	03/11	8:29 PM
> 
> When the single recording ended I used VLC to watch each channel.
> I then scheduled 4 programs to record (immediatly).
> All 4 recorded.
> 
> Splunking the logs gave some hints:
> 
> 2019-03-11 20:29:37.272508 E [11966/11977] TVRecEvent recorders/hdhrstreamhandler.cpp:481 (TunerSet) - HDHRSH(12
> 51AA81-0): DeviceSet(channel auto:184500000): ERROR: resource locked by 192.168.5.61

The line above looks like the problem.  Something else in your house is using the tuner and has it locked.  Mythtv expects to OWN the tuners.


> 2019-03-11 20:29:37.272515 E [11966/11977] TVRecEvent recorders/dtvchannel.cpp:311 (SetChannelByString) - DTVChan[5](1251AA81-0): SetChannelByString(30): Tuning to frequency.
> 2019-03-11 20:29:37.274398 E [11966/11977] TVRecEvent dtvmultiplex.cpp:246 (ParseDVB_S_and_C) - DTVMux: Invalid symbol rate parameter '0', aborting.
> 2019-03-11 20:29:37.274435 E [11966/11977] TVRecEvent recorders/dtvchannel.cpp:300 (SetChannelByString) - DTVChan[5](1251AA81-0): SetChannelByString(30): Failed to initialize multiplex options
> 2019-03-11 20:29:37.274450 E [11966/11977] TVRecEvent tv_rec.cpp:3743 (TuningFrequency) - TVRec[5]: Failed to set channel to 30. Reverting to kState_None
> 2019-03-11 20:29:37.274473 I [11966/11977] TVRecEvent tv_rec.cpp:1090 (HandleStateChange) - TVRec[5]: Changing from RecordingOnly to None
> 2019-03-11 20:29:37.298281 I [11966/11966] CoreContext scheduler.cpp:735 (UpdateRecStatus) - Updating status for "Michael Mosley: Trust Me, I'm A Doctor" on cardid [5] (Tuning => Recorder Failed)
> 2019-03-11 20:29:37.299695 E [11966/11977] TVRecEvent recorders/hdhrstreamhandler.cpp:481 (TunerSet) - HDHRSH(1251AA81-0): DeviceSet(channel none): ERROR: resource locked by 192.168.5.61


Same thing as above:  The line above looks like the problem.  Something else in your house is using the tuner and has it locked.  

Mythtv expects to OWN the tuners, just like it would if you used usb tuners.



> 2019-03-11 20:29:37.299757 E [11966/11989] Scheduler scheduler.cpp:798 (ChangeRecordingEnd) - Failed to change end time on card 5 to 2019-03-11T13:28:38Z
> 2019-03-11 20:29:37.312319 I [11966/11989] Scheduler scheduler.cpp:2461 (HandleReschedule) - 
> Reschedule interrupted, will retry
> 2019-03-11 20:29:37.312402 I [11966/11989] Scheduler scheduler.cpp:2357 (HandleReschedule) - Reschedule requested for CHECK -9 541 0 UpdateRecStatus2 | Michael Mosley: Trust Me, I'm A Doctor |  | Michael Mosley finds out whether a glass of wine can protect your blood vessels from the harmful effects of junk food. Giles Yeo sets out to test home breathalyser kits. | perth.sbshd.sbs.au/948351
> 2019-03-11 20:29:37.313282 I [11966/11989] Scheduler scheduler.cpp:2357 (HandleReschedule) - Reschedule requested for PLACE Interrupted
> 2019-03-11 20:29:37.341695 I [11966/11989] Scheduler scheduler.cpp:2470 (HandleReschedule) - Scheduled 60 itemsmythbackend.20190310101333.11966.log lines 9396-9409/10187 93%packet_write_wait: Connection to 192.168.5.33 port 22: Broken pipe
> 
> I reverted to my Haupague dual USB tuner. All seems to be working correctly. I ordered a second dual USB tuner. If anybody wants an Australian HDhomerun make me an offer (mail me) and it is yours.
> 
> Cheers
> James
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190313/d7e8edc1/attachment.html>

From jfabernathy at gmail.com  Wed Mar 13 13:27:11 2019
From: jfabernathy at gmail.com (James Abernathy)
Date: Wed, 13 Mar 2019 09:27:11 -0400
Subject: [mythtv-users] mythfrontend on Nvidia Shield
Message-ID: <3cdc06f0-c4d6-dd15-db1d-762a4970dbed@gmail.com>

First off, the Shield TV is a great FE platform.? However, I still have 
a minor issue that annoys me. Luckily there is a fix of sorts.

In the last few days I've received updates on mythtv to version v30 
fixes (2:30.0+fixes.201903101906.60cfb7c~ubuntu18.04.1
).

My mythfrontend on Shield tv is 30.0-28....? However, I also received an 
update to the Nvidia console yesterday as well and it's fixed a few things.

So mythfrontend on the Shield TV has one remaining issue as I see it. I 
generally watch recorded OTA mpeg2 programs with too many commercials. 
So I skip ahead and backup a lot.? At the end of each 
skip-ahead-a-few-minutes/back-up-a-few-seconds operation, I find I still 
have a lip sync problem.? It's off just enough to make me think I'm 
watching a dubbed foreign film, or very drunk.

It's easily fixed by pausing a second and the hitting play again.

Is there a setting in the frontend that would do the equivalent of that 
for me?

This is not major issue, but I live to find problems and fix them. :-)

Jim A



From uid000 at gmail.com  Wed Mar 13 17:47:37 2019
From: uid000 at gmail.com (Zach Cutlip)
Date: Wed, 13 Mar 2019 10:47:37 -0700
Subject: [mythtv-users] lircd unreliable after Ubuntu upgrade 16.04 > 18.04
Message-ID: <CACxx4MRv5dmSpqtQgovfwKwnpbVAjpWTh7w0HUCEu8x_s=0SQQ@mail.gmail.com>

Hello,

After upgrading my MythTV setup from Ubuntu 16.04 (lirc 0.9.0) to
Ubuntu 18.04 (lirc 0.10.0), and jumping through various hoops to get
lircd working again, I'm finding it to be very unreliable.

Lircd, my remote, and my IR receiver worked beautifully before the
upgrade, and was buttery smooth for years. Now, it does work, but
seems to miss a lot of commands. It will respond smoothly to, say, 8
or 10 commands, and then miss the next 10 or 15 commands. I don't see
any correlation between specific remote commands and responsiveness.
I'm using the exact same remote config as before. I've also tested
running lircd manually with debug/trace output. I don't see anything
in the output other than confirmation of lircd failing to decode
commands as I press buttons.

Any suggestions, or things to try?

Thanks,
Zach

From allen.p.edwards at gmail.com  Wed Mar 13 18:05:23 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Wed, 13 Mar 2019 11:05:23 -0700
Subject: [mythtv-users] lircd unreliable after Ubuntu upgrade 16.04 >
 18.04
In-Reply-To: <CACxx4MRv5dmSpqtQgovfwKwnpbVAjpWTh7w0HUCEu8x_s=0SQQ@mail.gmail.com>
References: <CACxx4MRv5dmSpqtQgovfwKwnpbVAjpWTh7w0HUCEu8x_s=0SQQ@mail.gmail.com>
Message-ID: <CAH8UtKMKmCZNU02CRSTYrt08SKDj3RANYVy-tS1zaXA7PGBbpA@mail.gmail.com>

On Wed, Mar 13, 2019 at 10:48 AM Zach Cutlip <uid000 at gmail.com> wrote:

> Hello,
>
> After upgrading my MythTV setup from Ubuntu 16.04 (lirc 0.9.0) to
> Ubuntu 18.04 (lirc 0.10.0), and jumping through various hoops to get
> lircd working again, I'm finding it to be very unreliable.
>
> Lircd, my remote, and my IR receiver worked beautifully before the
> upgrade, and was buttery smooth for years. Now, it does work, but
> seems to miss a lot of commands. It will respond smoothly to, say, 8
> or 10 commands, and then miss the next 10 or 15 commands. I don't see
> any correlation between specific remote commands and responsiveness.
> I'm using the exact same remote config as before. I've also tested
> running lircd manually with debug/trace output. I don't see anything
> in the output other than confirmation of lircd failing to decode
> commands as I press buttons.
>
> Any suggestions, or things to try?
>
> Thanks,
> Zach
> _______________________________________________
>
> I got the reply below to one of my questions about lircd. I do not know if
this is still valid and it sounds worse than what you are seeing.  I am
using 16.04 so it is not an issue I have dealt with. I had other issues
which required me to kill lircd and then restart because of the HDHR I was
using.
*killall lircd*
*lircd -H udp -d 5000*

Anyway, here is the replay that was part of troubleshooting my problem

Allen
***********************************************************************************









*lirc in 16.04 is a quite old version (0.9.0).  The version in 18.04
is0.10.0, and its Python configuration tools are badly broken - clearlyno
one ever tested them.  They can not find their libraries and crashwhen
run.  I believe lircd itself is fine, and if the config files canbe
manually created it will work.  And it is rather more capable than0.9.0.
But I have not actually verified that as I have not upgradedany of my
running systems to 18.04.1 yet.So your choice of 16.04 is fortuitous - you
need a working lirc, and*
*18.04 does not have one yet. *
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190313/eb0a99bb/attachment.html>

From pb.mythtv at gmail.com  Wed Mar 13 18:54:21 2019
From: pb.mythtv at gmail.com (Peter Bennett)
Date: Wed, 13 Mar 2019 14:54:21 -0400
Subject: [mythtv-users] mythfrontend on Nvidia Shield
In-Reply-To: <3cdc06f0-c4d6-dd15-db1d-762a4970dbed@gmail.com>
References: <3cdc06f0-c4d6-dd15-db1d-762a4970dbed@gmail.com>
Message-ID: <064f08c6-096b-5532-bfb0-e3a412be4218@gmail.com>



On 3/13/19 9:27 AM, James Abernathy wrote:
> First off, the Shield TV is a great FE platform.? However, I still 
> have a minor issue that annoys me. Luckily there is a fix of sorts.
>
> In the last few days I've received updates on mythtv to version v30 
> fixes (2:30.0+fixes.201903101906.60cfb7c~ubuntu18.04.1
> ).
>
> My mythfrontend on Shield tv is 30.0-28....? However, I also received 
> an update to the Nvidia console yesterday as well and it's fixed a few 
> things.
>
> So mythfrontend on the Shield TV has one remaining issue as I see it. 
> I generally watch recorded OTA mpeg2 programs with too many 
> commercials. So I skip ahead and backup a lot.? At the end of each 
> skip-ahead-a-few-minutes/back-up-a-few-seconds operation, I find I 
> still have a lip sync problem.? It's off just enough to make me think 
> I'm watching a dubbed foreign film, or very drunk.
>
> It's easily fixed by pausing a second and the hitting play again.
>
> Is there a setting in the frontend that would do the equivalent of 
> that for me?
>
> This is not major issue, but I live to find problems and fix them. :-)
>
> Jim A
>

Try Settings -> Video -> Playback -> Advanced Playback Settings. Make 
sure AVSync2 is checked then set ANSync2 -> audio correction. The 
default value is 10. This should? fix lip sync within a short time after 
a skip. A higher value will resync lips quicker but could cause jitter 
at other times. A low value will take longer to resync but may improve 
smoothness of playback in general. However is all cases the sync should 
come back eventually.

Another possibility - check Settings -> Video -> Playback -> General 
Playback -> Enable Music Choice. Disable this unless you are watching 
music choice channels. In some cases having this enabled could cause 
loss of synchronization.

Peter

From jfabernathy at gmail.com  Wed Mar 13 19:13:25 2019
From: jfabernathy at gmail.com (James Abernathy)
Date: Wed, 13 Mar 2019 15:13:25 -0400
Subject: [mythtv-users] mythfrontend on Nvidia Shield
In-Reply-To: <064f08c6-096b-5532-bfb0-e3a412be4218@gmail.com>
References: <3cdc06f0-c4d6-dd15-db1d-762a4970dbed@gmail.com>
 <064f08c6-096b-5532-bfb0-e3a412be4218@gmail.com>
Message-ID: <CANFv2EkXoFRasz7_nWKOFMxNWA+767Pk2BiwvHeRRHii7C6E3A@mail.gmail.com>

On Wed, Mar 13, 2019, 2:56 PM Peter Bennett <pb.mythtv at gmail.com> wrote:

>
>
> On 3/13/19 9:27 AM, James Abernathy wrote:
> > First off, the Shield TV is a great FE platform.  However, I still
> > have a minor issue that annoys me. Luckily there is a fix of sorts.
> >
> > In the last few days I've received updates on mythtv to version v30
> > fixes (2:30.0+fixes.201903101906.60cfb7c~ubuntu18.04.1
> > ).
> >
> > My mythfrontend on Shield tv is 30.0-28....  However, I also received
> > an update to the Nvidia console yesterday as well and it's fixed a few
> > things.
> >
> > So mythfrontend on the Shield TV has one remaining issue as I see it.
> > I generally watch recorded OTA mpeg2 programs with too many
> > commercials. So I skip ahead and backup a lot.  At the end of each
> > skip-ahead-a-few-minutes/back-up-a-few-seconds operation, I find I
> > still have a lip sync problem.  It's off just enough to make me think
> > I'm watching a dubbed foreign film, or very drunk.
> >
> > It's easily fixed by pausing a second and the hitting play again.
> >
> > Is there a setting in the frontend that would do the equivalent of
> > that for me?
> >
> > This is not major issue, but I live to find problems and fix them. :-)
> >
> > Jim A
> >
>
> Try Settings -> Video -> Playback -> Advanced Playback Settings. Make
> sure AVSync2 is checked then set ANSync2 -> audio correction. The
> default value is 10. This should  fix lip sync within a short time after
> a skip. A higher value will resync lips quicker but could cause jitter
> at other times. A low value will take longer to resync but may improve
> smoothness of playback in general. However is all cases the sync should
> come back eventually.
>
> Another possibility - check Settings -> Video -> Playback -> General
> Playback -> Enable Music Choice. Disable this unless you are watching
> music choice channels. In some cases having this enabled could cause
> loss of synchronization.
>
> Peter
>

My settings are just as you described.

I'll monitor how long it takes to resync.

Jim  A

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190313/2af19fdc/attachment-0001.html>

From leamas.alec at gmail.com  Wed Mar 13 20:24:18 2019
From: leamas.alec at gmail.com (Alec Leamas)
Date: Wed, 13 Mar 2019 21:24:18 +0100
Subject: [mythtv-users] lircd unreliable after Ubuntu upgrade 16.04 >
 18.04
In-Reply-To: <CAH8UtKMKmCZNU02CRSTYrt08SKDj3RANYVy-tS1zaXA7PGBbpA@mail.gmail.com>
References: <CACxx4MRv5dmSpqtQgovfwKwnpbVAjpWTh7w0HUCEu8x_s=0SQQ@mail.gmail.com>
 <CAH8UtKMKmCZNU02CRSTYrt08SKDj3RANYVy-tS1zaXA7PGBbpA@mail.gmail.com>
Message-ID: <2122734e-b02b-0c70-6e30-f3e534920673@gmail.com>

On 13/03/19 19:05, Allen Edwards wrote:
> 
> 
> 
> On Wed, Mar 13, 2019 at 10:48 AM Zach Cutlip <uid000 at gmail.com
> <mailto:uid000 at gmail.com>> wrote:
> 
>     Hello,
> 
>     After upgrading my MythTV setup from Ubuntu 16.04 (lirc 0.9.0) to
>     Ubuntu 18.04 (lirc 0.10.0), and jumping through various hoops to get
>     lircd working again, I'm finding it to be very unreliable.
> 
>     Any suggestions, or things to try?


Most likely an upgrade problem. The upgrade to 0.9.0 requires manual
intervention [1]

Cheers!
--alec


[1] https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1791409

From jfabernathy at gmail.com  Wed Mar 13 21:35:21 2019
From: jfabernathy at gmail.com (James Abernathy)
Date: Wed, 13 Mar 2019 17:35:21 -0400
Subject: [mythtv-users] mythfrontend on Nvidia Shield
In-Reply-To: <064f08c6-096b-5532-bfb0-e3a412be4218@gmail.com>
References: <3cdc06f0-c4d6-dd15-db1d-762a4970dbed@gmail.com>
 <064f08c6-096b-5532-bfb0-e3a412be4218@gmail.com>
Message-ID: <e191cb0c-c1ea-0b32-b270-034430860709@gmail.com>


On 3/13/19 2:54 PM, Peter Bennett wrote:
>
>
> Try Settings -> Video -> Playback -> Advanced Playback Settings. Make 
> sure AVSync2 is checked then set ANSync2 -> audio correction. The 
> default value is 10. This should? fix lip sync within a short time 
> after a skip. A higher value will resync lips quicker but could cause 
> jitter at other times. A low value will take longer to resync but may 
> improve smoothness of playback in general. However is all cases the 
> sync should come back eventually.
>
> Another possibility - check Settings -> Video -> Playback -> General 
> Playback -> Enable Music Choice. Disable this unless you are watching 
> music choice channels. In some cases having this enabled could cause 
> loss of synchronization.
>
> Peter

Another thing. I just watched a program where the automatic commercial 
skip worked good enough that I didn't do any manual skipping. The lip 
sync was good after the automatic skips, but in one of the scenes a few 
second after a commercial the actor was saying no and shaking his head 
side to side. The lips were in sync, but head motions was a little jerky 
like it was filmed at 15 fps. I backed the program up 30 seconds, paused 
for a few seconds and then let it run.? The video was fine with perfect 
lip sync and no jerky head motion.

Jim A


From jam at tigger.ws  Thu Mar 14 00:38:05 2019
From: jam at tigger.ws (James Linder)
Date: Thu, 14 Mar 2019 08:38:05 +0800
Subject: [mythtv-users] HDhomerun quad
In-Reply-To: <mailman.83.1552504424.1604.mythtv-users@mythtv.org>
References: <mailman.83.1552504424.1604.mythtv-users@mythtv.org>
Message-ID: <1BACC62D-6B31-4EDB-BF7F-EC195C570357@tigger.ws>



> On 14 Mar 2019, at 3:13 am, mythtv-users-request at mythtv.org wrote:
> 
>> Hi ? this may be useful information if you are considering HDhome run.
>> 
>> I don?t think it plays nicely with myth.
>> I?ve had mostly good results in the weeks since I purchased it.
>> 
>> last night my regular schedule failed and my ?Watch Recordings? looked like this:
>> 
>> x Q&A	                		03/11	9:37 PM
>> x Q&A             			03/11	9:37 PM
>> x Media Watch              		03/11	9:21 PM
>> x Media Watch            		03/11	9:21 PM
>> x FourCorners             		03/11	8:35 PM
>> x FourCorners              		03/11	8:35 PM
>> x FourCorners           		03/11	8:35 PM
>> x FourCorners           		03/11	8:34 PM
>> x FourCorners               		03/11	8:35 PM
>> x FourCorners             		03/11	8:34 PM
>> x Predator               		03/11	8:30 PM
>> x Predator              		03/11	8:30 PM
>> x Michael Mosley: Trust Me I?m A Doctor	03/11	8:29 PM
>> x Michael Mosley: Trust Me I?m A Doctor	03/11	8:29 PM
>> Michael Mosley: Trust Me I?m A Doctor	03/11	8:29 PM
>> 
>> When the single recording ended I used VLC to watch each channel.
>> I then scheduled 4 programs to record (immediatly).
>> All 4 recorded.
>> 
>> Splunking the logs gave some hints:
>> 
>> 2019-03-11 20:29:37.272508 E [11966/11977] TVRecEvent recorders/hdhrstreamhandler.cpp:481 (TunerSet) - HDHRSH(12
>> 51AA81-0): DeviceSet(channel auto:184500000): ERROR: resource locked by 192.168.5.61
> 
> The line above looks like the problem.  Something else in your house is using the tuner and has it locked.  Mythtv expects to OWN the tuners.

The eureka moment did not last!
192.168.5.61 is my laptop and I had never used the tuners other-than-myth.
AFTER this I used VLC to view each channel (which worked)
AFTER that I recorded 4 channels (which also worked)

Clearly *something* happened, just not sure what.
We are auld farts and I absolutely guarentee my wife is blameless.
James

From stephen_agent at jsw.gen.nz  Thu Mar 14 02:27:31 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Thu, 14 Mar 2019 15:27:31 +1300
Subject: [mythtv-users] lircd unreliable after Ubuntu upgrade 16.04 >
 18.04
In-Reply-To: <2122734e-b02b-0c70-6e30-f3e534920673@gmail.com>
References: <CACxx4MRv5dmSpqtQgovfwKwnpbVAjpWTh7w0HUCEu8x_s=0SQQ@mail.gmail.com>
 <CAH8UtKMKmCZNU02CRSTYrt08SKDj3RANYVy-tS1zaXA7PGBbpA@mail.gmail.com>
 <2122734e-b02b-0c70-6e30-f3e534920673@gmail.com>
Message-ID: <32ej8ep7qdun3u0vi1mop9dkrt923gm8co@4ax.com>

On Wed, 13 Mar 2019 21:24:18 +0100, you wrote:

>On 13/03/19 19:05, Allen Edwards wrote:
>> 
>> 
>> 
>> On Wed, Mar 13, 2019 at 10:48 AM Zach Cutlip <uid000 at gmail.com
>> <mailto:uid000 at gmail.com>> wrote:
>> 
>>     Hello,
>> 
>>     After upgrading my MythTV setup from Ubuntu 16.04 (lirc 0.9.0) to
>>     Ubuntu 18.04 (lirc 0.10.0), and jumping through various hoops to get
>>     lircd working again, I'm finding it to be very unreliable.
>> 
>>     Any suggestions, or things to try?
>
>
>Most likely an upgrade problem. The upgrade to 0.9.0 requires manual
>intervention [1]
>
>Cheers!
>--alec
>
>
>[1] https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1791409

The lirc package as installed by 18.04 is broken.  There are a number
of problems with it, but the one that is most obvious is that
lirc-setup does not work at all (it can not find required library .so
files).  Your problem sounds like one of the other problems, which is
that it sets up systemd to run lircmd, lirc-uinput and irexec as
daemons, but does not set up valid configuration for those daemons. So
they run in the background and one (I think it is lircd-uinput) steals
keystrokes from the main lirc daemon.  So try running these commands
and see if it fixes your problem: 

sudo systemctl stop lircmd
sudo systemctl stop lirc-uinput
sudo systemctl stop irexec
sudo systemctl disable lircmd
sudo systemctl disable lirc-uinput
sudo systemctl disable irexec

Alternatively, if you want to fix all the problems I found in 18.04's
lirc package, you can download and run the script I wrote:

http://www.jsw.gen.nz/mythtv/lirc-ubuntu-18.04-install.sh

It fixes lirc-setup, the above problems and probably a few more I have
forgotten about.  It needs to be run with sudo or as root.  I am a bit
surprised that your lirc is working at all - the 16.04 to 18.04
upgrade does not normally produce a working lirc setup, so you must
have done a lot of manual configuration.

From oliver.greg at gmail.com  Thu Mar 14 20:46:44 2019
From: oliver.greg at gmail.com (Greg Oliver)
Date: Thu, 14 Mar 2019 15:46:44 -0500
Subject: [mythtv-users] Multi-tenant type of setup
Message-ID: <CAF4tN+-TxM8XW4KeRWs_jF4yNFb84zxsaujhb1XKcT7Mj9aBjQ@mail.gmail.com>

Hi,

I was wondering if anyone has successfully setup MythTV to be a typee of
multi-tenant setup.  2 cases:

1.  Same household, multiple viewers - same recording.  A good way to keep
user 1 from deleting recordings before they are viewed by all - anyone ever
come up with a design for this?

2.  Different Households - 1 backend (case 1 still applies as well).
Recording Groups can keep them separate with views, but still #1 would
apply and step on each other here.

Anyone have something similar working with good results?

TiA,

Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190314/9844a9cd/attachment.html>

From uid000 at gmail.com  Thu Mar 14 21:38:00 2019
From: uid000 at gmail.com (Zach Cutlip)
Date: Thu, 14 Mar 2019 14:38:00 -0700
Subject: [mythtv-users] lircd unreliable after Ubuntu upgrade 16.04 >
 18.04
In-Reply-To: <32ej8ep7qdun3u0vi1mop9dkrt923gm8co@4ax.com>
References: <CACxx4MRv5dmSpqtQgovfwKwnpbVAjpWTh7w0HUCEu8x_s=0SQQ@mail.gmail.com>
 <CAH8UtKMKmCZNU02CRSTYrt08SKDj3RANYVy-tS1zaXA7PGBbpA@mail.gmail.com>
 <2122734e-b02b-0c70-6e30-f3e534920673@gmail.com>
 <32ej8ep7qdun3u0vi1mop9dkrt923gm8co@4ax.com>
Message-ID: <CACxx4MS9X8dvpVCnbS-QyP5hVCJFC3ADQBaQ4d4m=z2_2RFxZQ@mail.gmail.com>

On Wed, Mar 13, 2019 at 7:29 PM Stephen Worthington
<stephen_agent at jsw.gen.nz> wrote:
>
> On Wed, 13 Mar 2019 21:24:18 +0100, you wrote:
>
> >On 13/03/19 19:05, Allen Edwards wrote:
> >>
> >>
> >>
> >> On Wed, Mar 13, 2019 at 10:48 AM Zach Cutlip <uid000 at gmail.com
> >> <mailto:uid000 at gmail.com>> wrote:
> >>
> >>     Hello,
> >>
> >>     After upgrading my MythTV setup from Ubuntu 16.04 (lirc 0.9.0) to
> >>     Ubuntu 18.04 (lirc 0.10.0), and jumping through various hoops to get
> >>     lircd working again, I'm finding it to be very unreliable.
> >>
> >>     Any suggestions, or things to try?
> >
> >
> >Most likely an upgrade problem. The upgrade to 0.9.0 requires manual
> >intervention [1]
> >
> >Cheers!
> >--alec
> >
> >
> >[1] https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1791409
>
> The lirc package as installed by 18.04 is broken.  There are a number
> of problems with it, but the one that is most obvious is that
> lirc-setup does not work at all (it can not find required library .so
> files).  Your problem sounds like one of the other problems, which is
> that it sets up systemd to run lircmd, lirc-uinput and irexec as
> daemons, but does not set up valid configuration for those daemons. So
> they run in the background and one (I think it is lircd-uinput) steals
> keystrokes from the main lirc daemon.  So try running these commands
> and see if it fixes your problem:
>
> sudo systemctl stop lircmd
> sudo systemctl stop lirc-uinput
> sudo systemctl stop irexec
> sudo systemctl disable lircmd
> sudo systemctl disable lirc-uinput
> sudo systemctl disable irexec
>
> Alternatively, if you want to fix all the problems I found in 18.04's
> lirc package, you can download and run the script I wrote:
>
> http://www.jsw.gen.nz/mythtv/lirc-ubuntu-18.04-install.sh
>
> It fixes lirc-setup, the above problems and probably a few more I have
> forgotten about.  It needs to be run with sudo or as root.  I am a bit
> surprised that your lirc is working at all - the 16.04 to 18.04
> upgrade does not normally produce a working lirc setup, so you must
> have done a lot of manual configuration.

Hi Stephen,

You are right; I didn't have a working lirc setup at all after
upgrade. I had to troubleshoot quite a bit to get it working again
even to the degree that it is.

I don't think any of these are running:

 $ ps -ef | grep -E 'lircmd|lircd-uinput|irexec'
knath    12295 11492  0 14:24 pts/1    00:00:00 grep -E
lircmd|lircd-uinput|irexec
$ ps -ef | grep lirc
root     12435     1  0 14:29 ?        00:00:00 /usr/sbin/lircd --nodaemon

I stopped & disabled the services just in case though.

Is there anything else I can check, or diagnosis I can do?

Here's my lirc_options.conf if it helps:

[lircd]
nodaemon        = False
# driver          = devinput
driver          = default
# device          = auto
device          = /dev/lirc0
output          = /var/run/lirc/lircd
pidfile         = /var/run/lirc/lircd.pid
plugindir       = /usr/lib/i386-linux-gnu/lirc/plugins
permission      = 666
allow-simulate  = No
repeat-max      = 600
#effective-user =
#listen         = [address:]port
#connect        = host[:port]
#loglevel       = 6
#release        = true
#release_suffix = _EVUP
#logfile        = ...
#driver-options = ...

[lircmd]
uinput          = False
nodaemon        = False

# [modinit]
# code = /usr/sbin/modprobe lirc_serial
# code1 = /usr/bin/setfacl -m g:lirc:rw /dev/uinput
# code2 = ...


# [lircd-uinput]
# add-release-events = False
# release-timeout    = 200
# release-suffix     = _EVUP

And here's the start to my lircd remote definition, which has always
worked perfectly until now:

begin remote

  name  Tivo_S2
  bits           32
  flags SPACE_ENC|CONST_LENGTH
  eps            20
  aeps          200

  header       9000  4500
  one           562  1687
  zero          562   562
  ptrail        562
  repeat       9000  2250
  gap          108000
  min_repeat      1
  toggle_bit      0

  frequency    38000

      begin codes
          TIVO                     0x00000000A10CE00F
          TV_POWER                 0x00000000A10C0807
          TV_INPUT                 0x00000000A10C2C03
          WINDOW                   0x00000000A10C220D
          LIVE_TV                  0x00000000A10C8807
          INFO                     0x00000000A10CC807
          GUIDE                    0x00000000A10C6C03
          UP                       0x00000000A10C2807
          LEFT                     0x00000000A10CE807
          RIGHT                    0x00000000A10CA807
          DOWN                     0x00000000A10C6807






-- 
:wq!

From linux at thehobsons.co.uk  Thu Mar 14 21:48:35 2019
From: linux at thehobsons.co.uk (Simon Hobson)
Date: Thu, 14 Mar 2019 21:48:35 +0000
Subject: [mythtv-users] Multi-tenant type of setup
In-Reply-To: <CAF4tN+-TxM8XW4KeRWs_jF4yNFb84zxsaujhb1XKcT7Mj9aBjQ@mail.gmail.com>
References: <CAF4tN+-TxM8XW4KeRWs_jF4yNFb84zxsaujhb1XKcT7Mj9aBjQ@mail.gmail.com>
Message-ID: <A861EA27-01C3-4E73-AF5B-1B99B62AA211@thehobsons.co.uk>

Greg Oliver <oliver.greg at gmail.com> wrote:

> I was wondering if anyone has successfully setup MythTV to be a typee of multi-tenant setup.  2 cases:
> 
> 1.  Same household, multiple viewers - same recording.  A good way to keep user 1 from deleting recordings before they are viewed by all - anyone ever come up with a design for this?
> 
> 2.  Different Households - 1 backend (case 1 still applies as well).  Recording Groups can keep them separate with views, but still #1 would apply and step on each other here.
> 
> Anyone have something similar working with good results?

AFAIK there is nothing to handle either of these cases. There was a thread some time ago here (IIRC it was several years) where it was discussed - discussing ways to make the system multi-user. IIRC there were thoughts along the lines of having a watched flag per user - so each user that flagged the recording rule as "theirs" would need to flag the recording as watched for it to be "watched." I suspect that such functionality is likely to be a long time coming as it's major chnages to the system and the underlying database schema - and it needs devs with the skills, motivation, and time to do it.


From oliver.greg at gmail.com  Thu Mar 14 22:05:49 2019
From: oliver.greg at gmail.com (Greg Oliver)
Date: Thu, 14 Mar 2019 17:05:49 -0500
Subject: [mythtv-users] Multi-tenant type of setup
In-Reply-To: <A861EA27-01C3-4E73-AF5B-1B99B62AA211@thehobsons.co.uk>
References: <CAF4tN+-TxM8XW4KeRWs_jF4yNFb84zxsaujhb1XKcT7Mj9aBjQ@mail.gmail.com>
 <A861EA27-01C3-4E73-AF5B-1B99B62AA211@thehobsons.co.uk>
Message-ID: <CAF4tN+8jqxdTuQgxDFj0O0iRCbowkx2cCXvnXCRS+OpY2w9M6A@mail.gmail.com>

On Thu, Mar 14, 2019 at 4:49 PM Simon Hobson <linux at thehobsons.co.uk> wrote:

> Greg Oliver <oliver.greg at gmail.com> wrote:
>
> > I was wondering if anyone has successfully setup MythTV to be a typee of
> multi-tenant setup.  2 cases:
> >
> > 1.  Same household, multiple viewers - same recording.  A good way to
> keep user 1 from deleting recordings before they are viewed by all - anyone
> ever come up with a design for this?
> >
> > 2.  Different Households - 1 backend (case 1 still applies as well).
> Recording Groups can keep them separate with views, but still #1 would
> apply and step on each other here.
> >
> > Anyone have something similar working with good results?
>
> AFAIK there is nothing to handle either of these cases. There was a thread
> some time ago here (IIRC it was several years) where it was discussed -
> discussing ways to make the system multi-user. IIRC there were thoughts
> along the lines of having a watched flag per user - so each user that
> flagged the recording rule as "theirs" would need to flag the recording as
> watched for it to be "watched." I suspect that such functionality is likely
> to be a long time coming as it's major chnages to the system and the
> underlying database schema - and it needs devs with the skills, motivation,
> and time to do it.
>

Yeah, I knew it was not really feasible from the default system definitions
and design specs, but there are a lot of people here who have been running
it much longer than I (over 10 year user), so I was just chumming the water
to see what others have done to combat this (if anything).

It might just be easiest to have an education moment for the other side to
honor the watched flags, but I am not really a API user, so I need to see
what options are there as far as marking watched, etc..

The other household I am referring to uses Kodi to watch MythTV, so I need
to investigate further my options and come up with a plan.

-Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190314/3234213d/attachment.html>

From digitalaudiorock at gmail.com  Thu Mar 14 22:18:24 2019
From: digitalaudiorock at gmail.com (Tom Dexter)
Date: Thu, 14 Mar 2019 18:18:24 -0400
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
Message-ID: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>

I had a REALLY odd one this week, and I'm not sure what this is all about:

I have two HDHomeRun Connect HDHR4-2US units. They've both been
connected to an 8 port switch I have for a long time. I expressly had
them on the switch so as to avoid having them dependent on the router.

On Monday I had several recordings fail. At that point I noticed that
the back of one HDHR was flashing red (no network connection). When I
tried to power it off and on it would get a link for a few seconds and
then drop it, and go to the blinking red status. I verified that the
switch port and cable were OK by connecting other devices and they all
worked OK. At that point I naturally figured that the HDHR, or the NIC
in it, must have died, so I ordered another. I actually ordered two
because 6th Ave Electronics (via Newegg) had them for $58 and free
shipping which is way cheaper than I generally see them.

They arrived today and when I hooked one up...SAME issue...drops the
link and flashes red after a few seconds...almost went ballistic. What
I found was that both the new one and the old one I thought was dead,
work perfectly connected to my router, but fail connected to ANY port
on the switch.

To make this even stranger, I now have a laptop of mine connected to
one of the same ports on that switch and it's working flawlessly. In
fact, my other (older) HDHR is working connected to the switch as it
always has.

I have no idea what to make of that at all. I can only think that
maybe the switch is going bad(?) and the requirements of the HDHR to
maintain a link are more restrictive than other devices?? Sort of
crazy. Any opinions would be welcome.

Tom

From oliver.greg at gmail.com  Thu Mar 14 22:29:00 2019
From: oliver.greg at gmail.com (Greg Oliver)
Date: Thu, 14 Mar 2019 17:29:00 -0500
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
Message-ID: <CAF4tN+-5Bf=2XQY9HDqpDgAckL7V3t83XVqE937Da4AowTqwvA@mail.gmail.com>

On Thu, Mar 14, 2019 at 5:19 PM Tom Dexter <digitalaudiorock at gmail.com>
wrote:

> I had a REALLY odd one this week, and I'm not sure what this is all about:
>
> I have two HDHomeRun Connect HDHR4-2US units. They've both been
> connected to an 8 port switch I have for a long time. I expressly had
> them on the switch so as to avoid having them dependent on the router.
>
> On Monday I had several recordings fail. At that point I noticed that
> the back of one HDHR was flashing red (no network connection). When I
> tried to power it off and on it would get a link for a few seconds and
> then drop it, and go to the blinking red status. I verified that the
> switch port and cable were OK by connecting other devices and they all
> worked OK. At that point I naturally figured that the HDHR, or the NIC
> in it, must have died, so I ordered another. I actually ordered two
> because 6th Ave Electronics (via Newegg) had them for $58 and free
> shipping which is way cheaper than I generally see them.
>
> They arrived today and when I hooked one up...SAME issue...drops the
> link and flashes red after a few seconds...almost went ballistic. What
> I found was that both the new one and the old one I thought was dead,
> work perfectly connected to my router, but fail connected to ANY port
> on the switch.
>
> To make this even stranger, I now have a laptop of mine connected to
> one of the same ports on that switch and it's working flawlessly. In
> fact, my other (older) HDHR is working connected to the switch as it
> always has.
>
> I have no idea what to make of that at all. I can only think that
> maybe the switch is going bad(?) and the requirements of the HDHR to
> maintain a link are more restrictive than other devices?? Sort of
> crazy. Any opinions would be welcome.
>
> Tom
>

Did you put the new power supplies in place, or use the older ones to power
the new units?  Just like the HD-PVR units, the wall-warts are the issue
over 90% of the time it seems.  I do not have a single Hauppage or
SiliconDust PS in place any longer (3x HDHR units and 2x HD-PVR units) -
they have *all* failed on me.

The HDPVRs seem to fail 100% with no warning.  The HDHRs at least give
tuning delays for a few days (in my case) where I had time to swap them
(recordings remain in yellow in Mythfrontend, but still fully viewable).

I but variable voltage units now - they cost a few bucks more, but even the
ones I used previously to replace the originals were failing sometimes, so
I figure my time is worth more than the price difference.

Anyhow, long-winded answer, but make sure you put the new PS on the units :)

-greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190314/9a92cff1/attachment.html>

From philledwards at gmail.com  Thu Mar 14 22:34:38 2019
From: philledwards at gmail.com (Phill Edwards)
Date: Fri, 15 Mar 2019 09:34:38 +1100
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <CAF4tN+-5Bf=2XQY9HDqpDgAckL7V3t83XVqE937Da4AowTqwvA@mail.gmail.com>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
 <CAF4tN+-5Bf=2XQY9HDqpDgAckL7V3t83XVqE937Da4AowTqwvA@mail.gmail.com>
Message-ID: <CAE2RtTMcZDYmEM5mBwfFXX=oUNCJPJJL-dUWvveSM62ns1O4uA@mail.gmail.com>

>
>
>> Did you put the new power supplies in place, or use the older ones to
> power the new units?  Just like the HD-PVR units, the wall-warts are the
> issue over 90% of the time it seems.  I do not have a single Hauppage or
> SiliconDust PS in place any longer (3x HDHR units and 2x HD-PVR units) -
> they have *all* failed on me.
>
> The HDPVRs seem to fail 100% with no warning.  The HDHRs at least give
> tuning delays for a few days (in my case) where I had time to swap them
> (recordings remain in yellow in Mythfrontend, but still fully viewable).
>
> I but variable voltage units now - they cost a few bucks more, but even
> the ones I used previously to replace the originals were failing sometimes,
> so I figure my time is worth more than the price difference.
>
> Anyhow, long-winded answer, but make sure you put the new PS on the units
> :)
>

Hi Greg, are you saying that the power supplies that come with the new
HDHR4s are the ones to use or the ones to avoid? If they're the ones to
avoid, what's the alternative?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190315/e94ec728/attachment.html>

From digitalaudiorock at gmail.com  Thu Mar 14 22:37:19 2019
From: digitalaudiorock at gmail.com (Tom Dexter)
Date: Thu, 14 Mar 2019 18:37:19 -0400
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <CAF4tN+-5Bf=2XQY9HDqpDgAckL7V3t83XVqE937Da4AowTqwvA@mail.gmail.com>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
 <CAF4tN+-5Bf=2XQY9HDqpDgAckL7V3t83XVqE937Da4AowTqwvA@mail.gmail.com>
Message-ID: <CADUj1OvOgzHC_m-hu-D92Jrmty3QxcwpdpeAgcNGTi83JW-JcA@mail.gmail.com>

On 3/14/19, Greg Oliver <oliver.greg at gmail.com> wrote:
> On Thu, Mar 14, 2019 at 5:19 PM Tom Dexter <digitalaudiorock at gmail.com>
> wrote:
>
>> I had a REALLY odd one this week, and I'm not sure what this is all
>> about:
>>
>> I have two HDHomeRun Connect HDHR4-2US units. They've both been
>> connected to an 8 port switch I have for a long time. I expressly had
>> them on the switch so as to avoid having them dependent on the router.
>>
>> On Monday I had several recordings fail. At that point I noticed that
>> the back of one HDHR was flashing red (no network connection). When I
>> tried to power it off and on it would get a link for a few seconds and
>> then drop it, and go to the blinking red status. I verified that the
>> switch port and cable were OK by connecting other devices and they all
>> worked OK. At that point I naturally figured that the HDHR, or the NIC
>> in it, must have died, so I ordered another. I actually ordered two
>> because 6th Ave Electronics (via Newegg) had them for $58 and free
>> shipping which is way cheaper than I generally see them.
>>
>> They arrived today and when I hooked one up...SAME issue...drops the
>> link and flashes red after a few seconds...almost went ballistic. What
>> I found was that both the new one and the old one I thought was dead,
>> work perfectly connected to my router, but fail connected to ANY port
>> on the switch.
>>
>> To make this even stranger, I now have a laptop of mine connected to
>> one of the same ports on that switch and it's working flawlessly. In
>> fact, my other (older) HDHR is working connected to the switch as it
>> always has.
>>
>> I have no idea what to make of that at all. I can only think that
>> maybe the switch is going bad(?) and the requirements of the HDHR to
>> maintain a link are more restrictive than other devices?? Sort of
>> crazy. Any opinions would be welcome.
>>
>> Tom
>>
>
> Did you put the new power supplies in place, or use the older ones to power
> the new units?  Just like the HD-PVR units, the wall-warts are the issue
> over 90% of the time it seems.  I do not have a single Hauppage or
> SiliconDust PS in place any longer (3x HDHR units and 2x HD-PVR units) -
> they have *all* failed on me.
>
> The HDPVRs seem to fail 100% with no warning.  The HDHRs at least give
> tuning delays for a few days (in my case) where I had time to swap them
> (recordings remain in yellow in Mythfrontend, but still fully viewable).
>
> I but variable voltage units now - they cost a few bucks more, but even the
> ones I used previously to replace the originals were failing sometimes, so
> I figure my time is worth more than the price difference.
>
> Anyhow, long-winded answer, but make sure you put the new PS on the units
> :)
>
> -greg
>

Thanks! And yes...all the tests I did today, even when testing the
original one, where with the power supply from the new unit. The
variable voltage power supplies do sound interesting though...but
again, sort of ruled out in this case.

Tom

From oliver.greg at gmail.com  Thu Mar 14 22:56:07 2019
From: oliver.greg at gmail.com (Greg Oliver)
Date: Thu, 14 Mar 2019 17:56:07 -0500
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <CADUj1OvOgzHC_m-hu-D92Jrmty3QxcwpdpeAgcNGTi83JW-JcA@mail.gmail.com>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
 <CAF4tN+-5Bf=2XQY9HDqpDgAckL7V3t83XVqE937Da4AowTqwvA@mail.gmail.com>
 <CADUj1OvOgzHC_m-hu-D92Jrmty3QxcwpdpeAgcNGTi83JW-JcA@mail.gmail.com>
Message-ID: <CAF4tN+-RbaGc0msUcDU+sPwESFKefDdJErG5t6PpmK6UzwTBXA@mail.gmail.com>

On Thu, Mar 14, 2019 at 5:38 PM Tom Dexter <digitalaudiorock at gmail.com>
wrote:

> On 3/14/19, Greg Oliver <oliver.greg at gmail.com> wrote:
> > On Thu, Mar 14, 2019 at 5:19 PM Tom Dexter <digitalaudiorock at gmail.com>
> > wrote:
> >
> >> I had a REALLY odd one this week, and I'm not sure what this is all
> >> about:
> >>
> >> I have two HDHomeRun Connect HDHR4-2US units. They've both been
> >> connected to an 8 port switch I have for a long time. I expressly had
> >> them on the switch so as to avoid having them dependent on the router.
> >>
> >> On Monday I had several recordings fail. At that point I noticed that
> >> the back of one HDHR was flashing red (no network connection). When I
> >> tried to power it off and on it would get a link for a few seconds and
> >> then drop it, and go to the blinking red status. I verified that the
> >> switch port and cable were OK by connecting other devices and they all
> >> worked OK. At that point I naturally figured that the HDHR, or the NIC
> >> in it, must have died, so I ordered another. I actually ordered two
> >> because 6th Ave Electronics (via Newegg) had them for $58 and free
> >> shipping which is way cheaper than I generally see them.
> >>
> >> They arrived today and when I hooked one up...SAME issue...drops the
> >> link and flashes red after a few seconds...almost went ballistic. What
> >> I found was that both the new one and the old one I thought was dead,
> >> work perfectly connected to my router, but fail connected to ANY port
> >> on the switch.
> >>
> >> To make this even stranger, I now have a laptop of mine connected to
> >> one of the same ports on that switch and it's working flawlessly. In
> >> fact, my other (older) HDHR is working connected to the switch as it
> >> always has.
> >>
> >> I have no idea what to make of that at all. I can only think that
> >> maybe the switch is going bad(?) and the requirements of the HDHR to
> >> maintain a link are more restrictive than other devices?? Sort of
> >> crazy. Any opinions would be welcome.
> >>
> >> Tom
> >>
> >
> > Did you put the new power supplies in place, or use the older ones to
> power
> > the new units?  Just like the HD-PVR units, the wall-warts are the issue
> > over 90% of the time it seems.  I do not have a single Hauppage or
> > SiliconDust PS in place any longer (3x HDHR units and 2x HD-PVR units) -
> > they have *all* failed on me.
> >
> > The HDPVRs seem to fail 100% with no warning.  The HDHRs at least give
> > tuning delays for a few days (in my case) where I had time to swap them
> > (recordings remain in yellow in Mythfrontend, but still fully viewable).
> >
> > I but variable voltage units now - they cost a few bucks more, but even
> the
> > ones I used previously to replace the originals were failing sometimes,
> so
> > I figure my time is worth more than the price difference.
> >
> > Anyhow, long-winded answer, but make sure you put the new PS on the units
> > :)
> >
> > -greg
> >
>
> Thanks! And yes...all the tests I did today, even when testing the
> original one, where with the power supply from the new unit. The
> variable voltage power supplies do sound interesting though...but
> again, sort of ruled out in this case.
>
> Tom
>

Just wanted to be sure - I know they can be problematic.  What type of
switch is it?  I have used Cisco and Cisco Small Business SG300s (old
Linksys models - pre--Cisco buyout) with no switching issues.

Does the switchport have any errors (if it is managed)?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190314/546235e6/attachment.html>

From oliver.greg at gmail.com  Thu Mar 14 22:58:22 2019
From: oliver.greg at gmail.com (Greg Oliver)
Date: Thu, 14 Mar 2019 17:58:22 -0500
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <CAE2RtTMcZDYmEM5mBwfFXX=oUNCJPJJL-dUWvveSM62ns1O4uA@mail.gmail.com>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
 <CAF4tN+-5Bf=2XQY9HDqpDgAckL7V3t83XVqE937Da4AowTqwvA@mail.gmail.com>
 <CAE2RtTMcZDYmEM5mBwfFXX=oUNCJPJJL-dUWvveSM62ns1O4uA@mail.gmail.com>
Message-ID: <CAF4tN+-PJaQrjzpVDNsanBfR_z5cBz6QgfGEj+Kco_j7a497kw@mail.gmail.com>

On Thu, Mar 14, 2019 at 5:35 PM Phill Edwards <philledwards at gmail.com>
wrote:

>
>>> Did you put the new power supplies in place, or use the older ones to
>> power the new units?  Just like the HD-PVR units, the wall-warts are the
>> issue over 90% of the time it seems.  I do not have a single Hauppage or
>> SiliconDust PS in place any longer (3x HDHR units and 2x HD-PVR units) -
>> they have *all* failed on me.
>>
>> The HDPVRs seem to fail 100% with no warning.  The HDHRs at least give
>> tuning delays for a few days (in my case) where I had time to swap them
>> (recordings remain in yellow in Mythfrontend, but still fully viewable).
>>
>> I but variable voltage units now - they cost a few bucks more, but even
>> the ones I used previously to replace the originals were failing sometimes,
>> so I figure my time is worth more than the price difference.
>>
>> Anyhow, long-winded answer, but make sure you put the new PS on the units
>> :)
>>
>
> Hi Greg, are you saying that the power supplies that come with the new
> HDHR4s are the ones to use or the ones to avoid? If they're the ones to
> avoid, what's the alternative?
>

I am just saying the failure rate of SDs wall-warts is very high compared
to all of my other devices with wall-warts (and a lot of other people on
this list as well).  They last a couple years generally (in my experience),
but that is definitely not stellar..  Just double checking that Tom was
using the new ones.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190314/e2c29b83/attachment.html>

From glenb at glenb.us  Thu Mar 14 23:03:50 2019
From: glenb at glenb.us (glen)
Date: Thu, 14 Mar 2019 16:03:50 -0700
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
Message-ID: <4e035c9c6d49a49eb5402379066c02542a8f5489.camel@glenb.us>

On Thu, 2019-03-14 at 18:18 -0400, Tom Dexter wrote:
> I had a REALLY odd one this week, and I'm not sure what this is all
> about:
> I have two HDHomeRun Connect HDHR4-2US units. They've both
> beenconnected to an 8 port switch I have for a long time. I expressly
> hadthem on the switch so as to avoid having them dependent on the
> router.
> On Monday I had several recordings fail. At that point I noticed
> thatthe back of one HDHR was flashing red (no network connection).
> When Itried to power it off and on it would get a link for a few
> seconds andthen drop it, and go to the blinking red status. I
> verified that theswitch port and cable were OK by connecting other
> devices and they allworked OK. At that point I naturally figured that
> the HDHR, or the NICin it, must have died, so I ordered another. I
> actually ordered twobecause 6th Ave Electronics (via Newegg) had them
> for $58 and freeshipping which is way cheaper than I generally see
> them.
> They arrived today and when I hooked one up...SAME issue...drops
> thelink and flashes red after a few seconds...almost went ballistic.
> WhatI found was that both the new one and the old one I thought was
> dead,work perfectly connected to my router, but fail connected to ANY
> porton the switch.
> To make this even stranger, I now have a laptop of mine connected
> toone of the same ports on that switch and it's working flawlessly.
> Infact, my other (older) HDHR is working connected to the switch as
> italways has.
> I have no idea what to make of that at all. I can only think
> thatmaybe the switch is going bad(?) and the requirements of the HDHR
> tomaintain a link are more restrictive than other devices?? Sort
> ofcrazy. Any opinions would be welcome.
> Tom_______________________________________________mythtv-users
> mailing listmythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

i would look toward the switch as the problem. is this a managed or
unmanaged switch ?. did you try different portson the switch ? i would
swap ethernet cables and move the hdhomeruns to ports on switch not
used before. preferably1 and 2 on the switch
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190314/fdba46d8/attachment.html>

From digitalaudiorock at gmail.com  Thu Mar 14 23:35:48 2019
From: digitalaudiorock at gmail.com (Tom Dexter)
Date: Thu, 14 Mar 2019 19:35:48 -0400
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <CAF4tN+-RbaGc0msUcDU+sPwESFKefDdJErG5t6PpmK6UzwTBXA@mail.gmail.com>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
 <CAF4tN+-5Bf=2XQY9HDqpDgAckL7V3t83XVqE937Da4AowTqwvA@mail.gmail.com>
 <CADUj1OvOgzHC_m-hu-D92Jrmty3QxcwpdpeAgcNGTi83JW-JcA@mail.gmail.com>
 <CAF4tN+-RbaGc0msUcDU+sPwESFKefDdJErG5t6PpmK6UzwTBXA@mail.gmail.com>
Message-ID: <CADUj1Ova4WvSQJg+34CNQErEnTWef8NRS-agVXeRbm39TWLdvQ@mail.gmail.com>

On 3/14/19, Greg Oliver <oliver.greg at gmail.com> wrote:
> On Thu, Mar 14, 2019 at 5:38 PM Tom Dexter <digitalaudiorock at gmail.com>
> wrote:
>
>> On 3/14/19, Greg Oliver <oliver.greg at gmail.com> wrote:
>> > On Thu, Mar 14, 2019 at 5:19 PM Tom Dexter <digitalaudiorock at gmail.com>
>> > wrote:
>> >
>> >> I had a REALLY odd one this week, and I'm not sure what this is all
>> >> about:
>> >>
>> >> I have two HDHomeRun Connect HDHR4-2US units. They've both been
>> >> connected to an 8 port switch I have for a long time. I expressly had
>> >> them on the switch so as to avoid having them dependent on the router.
>> >>
>> >> On Monday I had several recordings fail. At that point I noticed that
>> >> the back of one HDHR was flashing red (no network connection). When I
>> >> tried to power it off and on it would get a link for a few seconds and
>> >> then drop it, and go to the blinking red status. I verified that the
>> >> switch port and cable were OK by connecting other devices and they all
>> >> worked OK. At that point I naturally figured that the HDHR, or the NIC
>> >> in it, must have died, so I ordered another. I actually ordered two
>> >> because 6th Ave Electronics (via Newegg) had them for $58 and free
>> >> shipping which is way cheaper than I generally see them.
>> >>
>> >> They arrived today and when I hooked one up...SAME issue...drops the
>> >> link and flashes red after a few seconds...almost went ballistic. What
>> >> I found was that both the new one and the old one I thought was dead,
>> >> work perfectly connected to my router, but fail connected to ANY port
>> >> on the switch.
>> >>
>> >> To make this even stranger, I now have a laptop of mine connected to
>> >> one of the same ports on that switch and it's working flawlessly. In
>> >> fact, my other (older) HDHR is working connected to the switch as it
>> >> always has.
>> >>
>> >> I have no idea what to make of that at all. I can only think that
>> >> maybe the switch is going bad(?) and the requirements of the HDHR to
>> >> maintain a link are more restrictive than other devices?? Sort of
>> >> crazy. Any opinions would be welcome.
>> >>
>> >> Tom
>> >>
>> >
>> > Did you put the new power supplies in place, or use the older ones to
>> power
>> > the new units?  Just like the HD-PVR units, the wall-warts are the
>> > issue
>> > over 90% of the time it seems.  I do not have a single Hauppage or
>> > SiliconDust PS in place any longer (3x HDHR units and 2x HD-PVR units)
>> > -
>> > they have *all* failed on me.
>> >
>> > The HDPVRs seem to fail 100% with no warning.  The HDHRs at least give
>> > tuning delays for a few days (in my case) where I had time to swap them
>> > (recordings remain in yellow in Mythfrontend, but still fully
>> > viewable).
>> >
>> > I but variable voltage units now - they cost a few bucks more, but even
>> the
>> > ones I used previously to replace the originals were failing sometimes,
>> so
>> > I figure my time is worth more than the price difference.
>> >
>> > Anyhow, long-winded answer, but make sure you put the new PS on the
>> > units
>> > :)
>> >
>> > -greg
>> >
>>
>> Thanks! And yes...all the tests I did today, even when testing the
>> original one, where with the power supply from the new unit. The
>> variable voltage power supplies do sound interesting though...but
>> again, sort of ruled out in this case.
>>
>> Tom
>>
>
> Just wanted to be sure - I know they can be problematic.  What type of
> switch is it?  I have used Cisco and Cisco Small Business SG300s (old
> Linksys models - pre--Cisco buyout) with no switching issues.
>
> Does the switchport have any errors (if it is managed)?
>

It's a Trendnet TEG-S80g. I can't recall when I bought it offhand but
I have had it a good while.

Tom

From hikavdh at gmail.com  Thu Mar 14 23:37:53 2019
From: hikavdh at gmail.com (Hika van den Hoven)
Date: Fri, 15 Mar 2019 00:37:53 +0100
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
Message-ID: <64105823.20190315003753@gmail.com>

Hoi Tom,

Thursday, March 14, 2019, 11:18:24 PM, you wrote:

> I had a REALLY odd one this week, and I'm not sure what this is all about:

> I have two HDHomeRun Connect HDHR4-2US units. They've both been
> connected to an 8 port switch I have for a long time. I expressly had
> them on the switch so as to avoid having them dependent on the router.

> On Monday I had several recordings fail. At that point I noticed that
> the back of one HDHR was flashing red (no network connection). When I
> tried to power it off and on it would get a link for a few seconds and
> then drop it, and go to the blinking red status. I verified that the
> switch port and cable were OK by connecting other devices and they all
> worked OK. At that point I naturally figured that the HDHR, or the NIC
> in it, must have died, so I ordered another. I actually ordered two
> because 6th Ave Electronics (via Newegg) had them for $58 and free
> shipping which is way cheaper than I generally see them.

> They arrived today and when I hooked one up...SAME issue...drops the
> link and flashes red after a few seconds...almost went ballistic. What
> I found was that both the new one and the old one I thought was dead,
> work perfectly connected to my router, but fail connected to ANY port
> on the switch.

> To make this even stranger, I now have a laptop of mine connected to
> one of the same ports on that switch and it's working flawlessly. In
> fact, my other (older) HDHR is working connected to the switch as it
> always has.

> I have no idea what to make of that at all. I can only think that
> maybe the switch is going bad(?) and the requirements of the HDHR to
> maintain a link are more restrictive than other devices?? Sort of
> crazy. Any opinions would be welcome.

> Tom
> _______________________________________________

How/where does the homerun obtain its ip-address?
Did the laptop you tested with maybe have a hard ip-address?
In other words check your dhcp.


Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens


From digitalaudiorock at gmail.com  Thu Mar 14 23:41:27 2019
From: digitalaudiorock at gmail.com (Tom Dexter)
Date: Thu, 14 Mar 2019 19:41:27 -0400
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <4e035c9c6d49a49eb5402379066c02542a8f5489.camel@glenb.us>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
 <4e035c9c6d49a49eb5402379066c02542a8f5489.camel@glenb.us>
Message-ID: <CADUj1OuVqtWwvxbDVpvdyCxBfgx7bOd05WWixVuAJvmyd_AbPg@mail.gmail.com>

On 3/14/19, glen <glenb at glenb.us> wrote:
> On Thu, 2019-03-14 at 18:18 -0400, Tom Dexter wrote:
>> I had a REALLY odd one this week, and I'm not sure what this is all
>> about:
>> I have two HDHomeRun Connect HDHR4-2US units. They've both
>> beenconnected to an 8 port switch I have for a long time. I expressly
>> hadthem on the switch so as to avoid having them dependent on the
>> router.
>> On Monday I had several recordings fail. At that point I noticed
>> thatthe back of one HDHR was flashing red (no network connection).
>> When Itried to power it off and on it would get a link for a few
>> seconds andthen drop it, and go to the blinking red status. I
>> verified that theswitch port and cable were OK by connecting other
>> devices and they allworked OK. At that point I naturally figured that
>> the HDHR, or the NICin it, must have died, so I ordered another. I
>> actually ordered twobecause 6th Ave Electronics (via Newegg) had them
>> for $58 and freeshipping which is way cheaper than I generally see
>> them.
>> They arrived today and when I hooked one up...SAME issue...drops
>> thelink and flashes red after a few seconds...almost went ballistic.
>> WhatI found was that both the new one and the old one I thought was
>> dead,work perfectly connected to my router, but fail connected to ANY
>> porton the switch.
>> To make this even stranger, I now have a laptop of mine connected
>> toone of the same ports on that switch and it's working flawlessly.
>> Infact, my other (older) HDHR is working connected to the switch as
>> italways has.
>> I have no idea what to make of that at all. I can only think
>> thatmaybe the switch is going bad(?) and the requirements of the HDHR
>> tomaintain a link are more restrictive than other devices?? Sort
>> ofcrazy. Any opinions would be welcome.
>> Tom_______________________________________________mythtv-users
>> mailing listmythtv-users at mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>
> i would look toward the switch as the problem. is this a managed or
> unmanaged switch ?. did you try different portson the switch ? i would
> swap ethernet cables and move the hdhomeruns to ports on switch not
> used before. preferably1 and 2 on the switch
>

I definitely tried several ports, all of which work for other
devices...no luck. It's an unmanaged switch. As noted in another
reply, a Trendnet TEG-S80g.

I've had it long enough that I'm inclined to just replace it.

Any recommendations are welcome. I was looking at a Netgear GS316
which seem to get pretty good reviews.

Tom

Tom

From digitalaudiorock at gmail.com  Thu Mar 14 23:46:19 2019
From: digitalaudiorock at gmail.com (Tom Dexter)
Date: Thu, 14 Mar 2019 19:46:19 -0400
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <64105823.20190315003753@gmail.com>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
 <64105823.20190315003753@gmail.com>
Message-ID: <CADUj1OsugxkC0M+RTNtyKDkxayGtWOOgzUQxLXzp_55PkygABQ@mail.gmail.com>

On 3/14/19, Hika van den Hoven <hikavdh at gmail.com> wrote:
> Hoi Tom,
>
> Thursday, March 14, 2019, 11:18:24 PM, you wrote:
>
>> I had a REALLY odd one this week, and I'm not sure what this is all
>> about:
>
>> I have two HDHomeRun Connect HDHR4-2US units. They've both been
>> connected to an 8 port switch I have for a long time. I expressly had
>> them on the switch so as to avoid having them dependent on the router.
>
>> On Monday I had several recordings fail. At that point I noticed that
>> the back of one HDHR was flashing red (no network connection). When I
>> tried to power it off and on it would get a link for a few seconds and
>> then drop it, and go to the blinking red status. I verified that the
>> switch port and cable were OK by connecting other devices and they all
>> worked OK. At that point I naturally figured that the HDHR, or the NIC
>> in it, must have died, so I ordered another. I actually ordered two
>> because 6th Ave Electronics (via Newegg) had them for $58 and free
>> shipping which is way cheaper than I generally see them.
>
>> They arrived today and when I hooked one up...SAME issue...drops the
>> link and flashes red after a few seconds...almost went ballistic. What
>> I found was that both the new one and the old one I thought was dead,
>> work perfectly connected to my router, but fail connected to ANY port
>> on the switch.
>
>> To make this even stranger, I now have a laptop of mine connected to
>> one of the same ports on that switch and it's working flawlessly. In
>> fact, my other (older) HDHR is working connected to the switch as it
>> always has.
>
>> I have no idea what to make of that at all. I can only think that
>> maybe the switch is going bad(?) and the requirements of the HDHR to
>> maintain a link are more restrictive than other devices?? Sort of
>> crazy. Any opinions would be welcome.
>
>> Tom
>> _______________________________________________
>
> How/where does the homerun obtain its ip-address?
> Did the laptop you tested with maybe have a hard ip-address?
> In other words check your dhcp.
>
>
> Tot mails,
>   Hika                            mailto:hikavdh at gmail.com
>

The HDHR (at least this model) doesn't support static IPs. I'm setting
it based on MAC address with my router's DHCP server (a Linksys
WRT1900ACS running dd-wrt). Note that it was totally dropping the link
itself, which doesn't sound like a DHCP issue. When it keeps the link
it gets it's IP with no problem.

Thanks!
Tom

From oliver.greg at gmail.com  Thu Mar 14 23:57:26 2019
From: oliver.greg at gmail.com (Greg Oliver)
Date: Thu, 14 Mar 2019 18:57:26 -0500
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <CADUj1OsugxkC0M+RTNtyKDkxayGtWOOgzUQxLXzp_55PkygABQ@mail.gmail.com>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
 <64105823.20190315003753@gmail.com>
 <CADUj1OsugxkC0M+RTNtyKDkxayGtWOOgzUQxLXzp_55PkygABQ@mail.gmail.com>
Message-ID: <CAF4tN+9tN6J=JYLzm8+9KjrvJFupk3cg4OCrLz+2oBAEZbUC6w@mail.gmail.com>

On Thu, Mar 14, 2019 at 6:47 PM Tom Dexter <digitalaudiorock at gmail.com>
wrote:

> On 3/14/19, Hika van den Hoven <hikavdh at gmail.com> wrote:
> > Hoi Tom,
> >
> > Thursday, March 14, 2019, 11:18:24 PM, you wrote:
> >
> >> I had a REALLY odd one this week, and I'm not sure what this is all
> >> about:
> >
> >> I have two HDHomeRun Connect HDHR4-2US units. They've both been
> >> connected to an 8 port switch I have for a long time. I expressly had
> >> them on the switch so as to avoid having them dependent on the router.
> >
> >> On Monday I had several recordings fail. At that point I noticed that
> >> the back of one HDHR was flashing red (no network connection). When I
> >> tried to power it off and on it would get a link for a few seconds and
> >> then drop it, and go to the blinking red status. I verified that the
> >> switch port and cable were OK by connecting other devices and they all
> >> worked OK. At that point I naturally figured that the HDHR, or the NIC
> >> in it, must have died, so I ordered another. I actually ordered two
> >> because 6th Ave Electronics (via Newegg) had them for $58 and free
> >> shipping which is way cheaper than I generally see them.
> >
> >> They arrived today and when I hooked one up...SAME issue...drops the
> >> link and flashes red after a few seconds...almost went ballistic. What
> >> I found was that both the new one and the old one I thought was dead,
> >> work perfectly connected to my router, but fail connected to ANY port
> >> on the switch.
> >
> >> To make this even stranger, I now have a laptop of mine connected to
> >> one of the same ports on that switch and it's working flawlessly. In
> >> fact, my other (older) HDHR is working connected to the switch as it
> >> always has.
> >
> >> I have no idea what to make of that at all. I can only think that
> >> maybe the switch is going bad(?) and the requirements of the HDHR to
> >> maintain a link are more restrictive than other devices?? Sort of
> >> crazy. Any opinions would be welcome.
> >
> >> Tom
> >> _______________________________________________
> >
> > How/where does the homerun obtain its ip-address?
> > Did the laptop you tested with maybe have a hard ip-address?
> > In other words check your dhcp.
> >
> >
> > Tot mails,
> >   Hika                            mailto:hikavdh at gmail.com
> >
>
> The HDHR (at least this model) doesn't support static IPs. I'm setting
> it based on MAC address with my router's DHCP server (a Linksys
> WRT1900ACS running dd-wrt). Note that it was totally dropping the link
> itself, which doesn't sound like a DHCP issue. When it keeps the link
> it gets it's IP with no problem.
>
> Thanks!
> Tom


3rd party firmware is a good thing..  With dd-wrt, you can do a tcpdump on
the wired interface..

tcpdump -i <interface name> -nn -A -XX port 67 or port 68

This will dump your DHCP packets on that interface to the screen.  Reboot
the HDHR while that is running and post the output (if any).

I cannot remember if dd-wrt (long time since I ran it) has tcpdump
installed by default, but you can definitely install it using Entware or
whatever they call it nowadays..
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190314/0ebdf3e5/attachment.html>

From glenb at glenb.us  Fri Mar 15 00:00:03 2019
From: glenb at glenb.us (glen)
Date: Thu, 14 Mar 2019 17:00:03 -0700
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <CADUj1OsugxkC0M+RTNtyKDkxayGtWOOgzUQxLXzp_55PkygABQ@mail.gmail.com>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
 <64105823.20190315003753@gmail.com>
 <CADUj1OsugxkC0M+RTNtyKDkxayGtWOOgzUQxLXzp_55PkygABQ@mail.gmail.com>
Message-ID: <3e08ac6204f025a2728af4299c5767f54c9ee498.camel@glenb.us>

On Thu, 2019-03-14 at 19:46 -0400, Tom Dexter wrote:
> On 3/14/19, Hika van den Hoven <hikavdh at gmail.com> wrote:
> > Hoi Tom,
> > Thursday, March 14, 2019, 11:18:24 PM, you wrote:
> > > I had a REALLY odd one this week, and I'm not sure what this is
> > > allabout:
> > > I have two HDHomeRun Connect HDHR4-2US units. They've both
> > > beenconnected to an 8 port switch I have for a long time. I
> > > expressly hadthem on the switch so as to avoid having them
> > > dependent on the router.
> > > On Monday I had several recordings fail. At that point I noticed
> > > thatthe back of one HDHR was flashing red (no network
> > > connection). When Itried to power it off and on it would get a
> > > link for a few seconds andthen drop it, and go to the blinking
> > > red status. I verified that theswitch port and cable were OK by
> > > connecting other devices and they allworked OK. At that point I
> > > naturally figured that the HDHR, or the NICin it, must have died,
> > > so I ordered another. I actually ordered twobecause 6th Ave
> > > Electronics (via Newegg) had them for $58 and freeshipping which
> > > is way cheaper than I generally see them.
> > > They arrived today and when I hooked one up...SAME issue...drops
> > > thelink and flashes red after a few seconds...almost went
> > > ballistic. WhatI found was that both the new one and the old one
> > > I thought was dead,work perfectly connected to my router, but
> > > fail connected to ANY porton the switch.
> > > To make this even stranger, I now have a laptop of mine connected
> > > toone of the same ports on that switch and it's working
> > > flawlessly. Infact, my other (older) HDHR is working connected to
> > > the switch as italways has.
> > > I have no idea what to make of that at all. I can only think
> > > thatmaybe the switch is going bad(?) and the requirements of the
> > > HDHR tomaintain a link are more restrictive than other devices??
> > > Sort ofcrazy. Any opinions would be welcome.
> > > Tom_______________________________________________
> > 
> > How/where does the homerun obtain its ip-address?Did the laptop you
> > tested with maybe have a hard ip-address?In other words check your
> > dhcp.
> > 
> > Tot mails,  Hika                            mailto:
> > hikavdh at gmail.com
> > 
> 
> The HDHR (at least this model) doesn't support static IPs. I'm
> settingit based on MAC address with my router's DHCP server (a
> LinksysWRT1900ACS running dd-wrt). Note that it was totally dropping
> the linkitself, which doesn't sound like a DHCP issue. When it keeps
> the linkit gets it's IP with no problem.
> Thanks!Tom_______________________________________________mythtv-users 
> mailing listmythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

this is a really odd problem, one more thought; is it possible to put
an older firmware on ? maybe your existing onessilently updated or
something and the new ones have the latest and somehow it can't be
managed in the table the switch maintains. i know some of the hdhr
don't let you go to older firmware. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190314/3bd2e33a/attachment.html>

From david at istwok.net  Fri Mar 15 01:44:57 2019
From: david at istwok.net (David Engel)
Date: Thu, 14 Mar 2019 20:44:57 -0500
Subject: [mythtv-users] Multi-tenant type of setup
In-Reply-To: <CAF4tN+-TxM8XW4KeRWs_jF4yNFb84zxsaujhb1XKcT7Mj9aBjQ@mail.gmail.com>
References: <CAF4tN+-TxM8XW4KeRWs_jF4yNFb84zxsaujhb1XKcT7Mj9aBjQ@mail.gmail.com>
Message-ID: <20190315014457.GA17210@opus.istwok.net>

On Thu, Mar 14, 2019 at 03:46:44PM -0500, Greg Oliver wrote:
> Hi,
> 
> I was wondering if anyone has successfully setup MythTV to be a typee of
> multi-tenant setup.  2 cases:
> 
> 1.  Same household, multiple viewers - same recording.  A good way to keep
> user 1 from deleting recordings before they are viewed by all - anyone ever
> come up with a design for this?

As Simon already mentioned, this has been discussed but nothing was
ever done.

> 2.  Different Households - 1 backend (case 1 still applies as well).
> Recording Groups can keep them separate with views, but still #1 would
> apply and step on each other here.

I actually have some experience with this.

We use recording groups to partition the recordings.  Recordings in
shared groups require coordination before they are deleted.  Recording
in groups that are exclusive can be freely deleted at will.

I personally patched the source code so that new, recording rules on
specififc frontends automatically default to a custom recording group.
While writing this reply, I realized I should change that to use a
hsot-specific setting so it could be used by others.

David

> Anyone have something similar working with good results?

-- 
David Engel
david at istwok.net

From digitalaudiorock at gmail.com  Fri Mar 15 01:45:37 2019
From: digitalaudiorock at gmail.com (Tom Dexter)
Date: Thu, 14 Mar 2019 21:45:37 -0400
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <3e08ac6204f025a2728af4299c5767f54c9ee498.camel@glenb.us>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
 <64105823.20190315003753@gmail.com>
 <CADUj1OsugxkC0M+RTNtyKDkxayGtWOOgzUQxLXzp_55PkygABQ@mail.gmail.com>
 <3e08ac6204f025a2728af4299c5767f54c9ee498.camel@glenb.us>
Message-ID: <CADUj1OsVrrr2LynpfqTQfshMx6UEOQ2==4yuaMAGuGO2o7jqHA@mail.gmail.com>

On 3/14/19, glen <glenb at glenb.us> wrote:
> On Thu, 2019-03-14 at 19:46 -0400, Tom Dexter wrote:
>> On 3/14/19, Hika van den Hoven <hikavdh at gmail.com> wrote:
>> > Hoi Tom,
>> >
>> > How/where does the homerun obtain its ip-address?Did the laptop you
>> > tested with maybe have a hard ip-address?In other words check your
>> > dhcp.
>> >
>> > Tot mails,  Hika                            mailto:
>> > hikavdh at gmail.com
>> >
>>
>> The HDHR (at least this model) doesn't support static IPs. I'm
>> settingit based on MAC address with my router's DHCP server (a
>> LinksysWRT1900ACS running dd-wrt). Note that it was totally dropping
>> the linkitself, which doesn't sound like a DHCP issue. When it keeps
>> the linkit gets it's IP with no problem.
>> Thanks!Tom_______________________________________________mythtv-users
>> mailing listmythtv-users at mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>
> this is a really odd problem, one more thought; is it possible to put
> an older firmware on ? maybe your existing onessilently updated or
> something and the new ones have the latest and somehow it can't be
> managed in the table the switch maintains. i know some of the hdhr
> don't let you go to older firmware.
>

I think you missed part of this: Both the old and the new HDHR drop
the link when connected to the switch but not when connected to the
router. It's seeming more like an issue with the switch.

Tom

From glenb at glenb.us  Fri Mar 15 01:59:30 2019
From: glenb at glenb.us (glen)
Date: Thu, 14 Mar 2019 18:59:30 -0700
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <CADUj1OsVrrr2LynpfqTQfshMx6UEOQ2==4yuaMAGuGO2o7jqHA@mail.gmail.com>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
 <64105823.20190315003753@gmail.com>
 <CADUj1OsugxkC0M+RTNtyKDkxayGtWOOgzUQxLXzp_55PkygABQ@mail.gmail.com>
 <3e08ac6204f025a2728af4299c5767f54c9ee498.camel@glenb.us>
 <CADUj1OsVrrr2LynpfqTQfshMx6UEOQ2==4yuaMAGuGO2o7jqHA@mail.gmail.com>
Message-ID: <3723e59f169e973dd1c95fd96d63986ea98be881.camel@glenb.us>

On Thu, 2019-03-14 at 21:45 -0400, Tom Dexter wrote:
> On 3/14/19, glen <glenb at glenb.us> wrote:
> > On Thu, 2019-03-14 at 19:46 -0400, Tom Dexter wrote:
> > > On 3/14/19, Hika van den Hoven <hikavdh at gmail.com> wrote:
> > > > Hoi Tom,
> > > > How/where does the homerun obtain its ip-address?Did the laptop
> > > > youtested with maybe have a hard ip-address?In other words
> > > > check yourdhcp.
> > > > Tot mails,  Hika                            mailto:
> > > > hikavdh at gmail.com
> > > > 
> > > 
> > > The HDHR (at least this model) doesn't support static IPs.
> > > I'msettingit based on MAC address with my router's DHCP server
> > > (aLinksysWRT1900ACS running dd-wrt). Note that it was totally
> > > droppingthe linkitself, which doesn't sound like a DHCP issue.
> > > When it keepsthe linkit gets it's IP with no
> > > problem.Thanks!Tom_______________________________________________
> > > mythtv-usersmailing listmythtv-users at mythtv.org
> > > http://lists.mythtv.org/mailman/listinfo/mythtv-users
> > > http://wiki.mythtv.org/Mailing_List_etiquette
> > > MythTV Forums: https://forum.mythtv.org
> > 
> > this is a really odd problem, one more thought; is it possible to
> > putan older firmware on ? maybe your existing onessilently updated
> > orsomething and the new ones have the latest and somehow it can't
> > bemanaged in the table the switch maintains. i know some of the
> > hdhrdon't let you go to older firmware.
> 
> I think you missed part of this: Both the old and the new HDHR
> dropthe link when connected to the switch but not when connected to
> therouter. It's seeming more like an issue with the switch.
> Tom_______________________________________________mythtv-users
> mailing listmythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

no i didn't miss it, it was just a longshot, that perhaps the hdhr when
interacting with that switch is not gettingonto the table maintained by
the switch, and since it once did, i was thinking possibly firmware
change which would explain why the new ones don't connect either. but
easiest to try a different switch since they work directly connectedto
router
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190314/2bf08c68/attachment.html>

From stephen_agent at jsw.gen.nz  Fri Mar 15 02:18:23 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Fri, 15 Mar 2019 15:18:23 +1300
Subject: [mythtv-users] lircd unreliable after Ubuntu upgrade 16.04 >
 18.04
In-Reply-To: <CACxx4MS9X8dvpVCnbS-QyP5hVCJFC3ADQBaQ4d4m=z2_2RFxZQ@mail.gmail.com>
References: <CACxx4MRv5dmSpqtQgovfwKwnpbVAjpWTh7w0HUCEu8x_s=0SQQ@mail.gmail.com>
 <CAH8UtKMKmCZNU02CRSTYrt08SKDj3RANYVy-tS1zaXA7PGBbpA@mail.gmail.com>
 <2122734e-b02b-0c70-6e30-f3e534920673@gmail.com>
 <32ej8ep7qdun3u0vi1mop9dkrt923gm8co@4ax.com>
 <CACxx4MS9X8dvpVCnbS-QyP5hVCJFC3ADQBaQ4d4m=z2_2RFxZQ@mail.gmail.com>
Message-ID: <2b1m8epehm288l8dli6d2t4e2tqrjvkrc9@4ax.com>

On Thu, 14 Mar 2019 14:38:00 -0700, you wrote:

>On Wed, Mar 13, 2019 at 7:29 PM Stephen Worthington
><stephen_agent at jsw.gen.nz> wrote:
>>
>> On Wed, 13 Mar 2019 21:24:18 +0100, you wrote:
>>
>> >On 13/03/19 19:05, Allen Edwards wrote:
>> >>
>> >>
>> >>
>> >> On Wed, Mar 13, 2019 at 10:48 AM Zach Cutlip <uid000 at gmail.com
>> >> <mailto:uid000 at gmail.com>> wrote:
>> >>
>> >>     Hello,
>> >>
>> >>     After upgrading my MythTV setup from Ubuntu 16.04 (lirc 0.9.0) to
>> >>     Ubuntu 18.04 (lirc 0.10.0), and jumping through various hoops to get
>> >>     lircd working again, I'm finding it to be very unreliable.
>> >>
>> >>     Any suggestions, or things to try?
>> >
>> >
>> >Most likely an upgrade problem. The upgrade to 0.9.0 requires manual
>> >intervention [1]
>> >
>> >Cheers!
>> >--alec
>> >
>> >
>> >[1] https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1791409
>>
>> The lirc package as installed by 18.04 is broken.  There are a number
>> of problems with it, but the one that is most obvious is that
>> lirc-setup does not work at all (it can not find required library .so
>> files).  Your problem sounds like one of the other problems, which is
>> that it sets up systemd to run lircmd, lirc-uinput and irexec as
>> daemons, but does not set up valid configuration for those daemons. So
>> they run in the background and one (I think it is lircd-uinput) steals
>> keystrokes from the main lirc daemon.  So try running these commands
>> and see if it fixes your problem:
>>
>> sudo systemctl stop lircmd
>> sudo systemctl stop lirc-uinput
>> sudo systemctl stop irexec
>> sudo systemctl disable lircmd
>> sudo systemctl disable lirc-uinput
>> sudo systemctl disable irexec
>>
>> Alternatively, if you want to fix all the problems I found in 18.04's
>> lirc package, you can download and run the script I wrote:
>>
>> http://www.jsw.gen.nz/mythtv/lirc-ubuntu-18.04-install.sh
>>
>> It fixes lirc-setup, the above problems and probably a few more I have
>> forgotten about.  It needs to be run with sudo or as root.  I am a bit
>> surprised that your lirc is working at all - the 16.04 to 18.04
>> upgrade does not normally produce a working lirc setup, so you must
>> have done a lot of manual configuration.
>
>Hi Stephen,
>
>You are right; I didn't have a working lirc setup at all after
>upgrade. I had to troubleshoot quite a bit to get it working again
>even to the degree that it is.
>
>I don't think any of these are running:
>
> $ ps -ef | grep -E 'lircmd|lircd-uinput|irexec'
>knath    12295 11492  0 14:24 pts/1    00:00:00 grep -E
>lircmd|lircd-uinput|irexec
>$ ps -ef | grep lirc
>root     12435     1  0 14:29 ?        00:00:00 /usr/sbin/lircd --nodaemon
>
>I stopped & disabled the services just in case though.
>
>Is there anything else I can check, or diagnosis I can do?
>
>Here's my lirc_options.conf if it helps:
>
>[lircd]
>nodaemon        = False
># driver          = devinput
>driver          = default
># device          = auto
>device          = /dev/lirc0
>output          = /var/run/lirc/lircd
>pidfile         = /var/run/lirc/lircd.pid
>plugindir       = /usr/lib/i386-linux-gnu/lirc/plugins
>permission      = 666
>allow-simulate  = No
>repeat-max      = 600
>#effective-user =
>#listen         = [address:]port
>#connect        = host[:port]
>#loglevel       = 6
>#release        = true
>#release_suffix = _EVUP
>#logfile        = ...
>#driver-options = ...
>
>[lircmd]
>uinput          = False
>nodaemon        = False
>
># [modinit]
># code = /usr/sbin/modprobe lirc_serial
># code1 = /usr/bin/setfacl -m g:lirc:rw /dev/uinput
># code2 = ...
>
>
># [lircd-uinput]
># add-release-events = False
># release-timeout    = 200
># release-suffix     = _EVUP
>
>And here's the start to my lircd remote definition, which has always
>worked perfectly until now:
>
>begin remote
>
>  name  Tivo_S2
>  bits           32
>  flags SPACE_ENC|CONST_LENGTH
>  eps            20
>  aeps          200
>
>  header       9000  4500
>  one           562  1687
>  zero          562   562
>  ptrail        562
>  repeat       9000  2250
>  gap          108000
>  min_repeat      1
>  toggle_bit      0
>
>  frequency    38000
>
>      begin codes
>          TIVO                     0x00000000A10CE00F
>          TV_POWER                 0x00000000A10C0807
>          TV_INPUT                 0x00000000A10C2C03
>          WINDOW                   0x00000000A10C220D
>          LIVE_TV                  0x00000000A10C8807
>          INFO                     0x00000000A10CC807
>          GUIDE                    0x00000000A10C6C03
>          UP                       0x00000000A10C2807
>          LEFT                     0x00000000A10CE807
>          RIGHT                    0x00000000A10CA807
>          DOWN                     0x00000000A10C6807

That looks OK, but check that your lirc hardware is actually appearing
as the /dev/lirc0 device.

However, MythTV looks for a /dev/lircd device for the keystroke
outputs from the lirc daemon.  Do you have that?  I had to link the
default lirc output device (/var/run/lirc/lircd) to /dev/lircd to make
it work, as I could not find any way to configure MythTV to use the
new location for the lirc output device, and changing the setting in
lirc_options.conf made other programs unable to work with lirc.  If
you look at my script, you will find that it creates a
lircd-dev.service file in /etc/systemd/system to do this automatically
when the lirc daemon is started:

root at mypvr:/etc/systemd/system# cat lircd-dev.service
[Unit]
Description=Create the /dev/lircd device (linked to /run/lirc/lircd)
as required by MythTV.
After=lircd.service

[Service]
Type=simple
ExecStart=/bin/bash -c "ln -s /run/lirc/lircd /dev/lircd"

[Install]
WantedBy=multi-user.target

Note that /var/run/ is a link to /run, so /run/lirc/lircd is the same
as /var/run/lirc/lircd in the lirc_options.conf file.

Also, check your MythTV .lircrc files:

root at mypvr:/home/stephen# cat .lircrc
#Custom lircrc generated via mythbuntu-lirc-generator
#All application specific lircrc files are within ~/.lirc
include ~/.lirc/mythtv
include ~/.lirc/mplayer
include ~/.lirc/xine
include ~/.lirc/vlc
include ~/.lirc/xmame
include ~/.lirc/xmess
include ~/.lirc/totem
include ~/.lirc/elisa
include ~/.lirc/irexec

root at mypvr:/home/stephen# head -n 24 .lirc/mythtv
# lircrc for devinput with Hauppauge Nova TD-500 and Hauppauge
HVR-900R2 remotes (with lirc 0.9.0),
# and MCE remotes.

# Save it in ~/.lircrc

begin
    remote = devinput
    prog = mythtv
             # Guide key
    button = KEY_EPG
#    config = S
    config = Ctrl+Alt+G
    repeat = 0
    delay = 0
end

begin
    remote = devinput
    prog = mythtv
    button = KEY_EXIT
    config = Escape
    repeat = 0
    delay = 0
end

To work in your setup, all the entries for MythTV (with prog=mythtv
lines) will have to have the remote= lines set to match the driver=
setting in your lirc_options.conf file.  So they should have "remote =
default", where mine have "remote = devinput".

From stephen_agent at jsw.gen.nz  Fri Mar 15 02:54:09 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Fri, 15 Mar 2019 15:54:09 +1300
Subject: [mythtv-users] Multi-tenant type of setup
In-Reply-To: <20190315014457.GA17210@opus.istwok.net>
References: <CAF4tN+-TxM8XW4KeRWs_jF4yNFb84zxsaujhb1XKcT7Mj9aBjQ@mail.gmail.com>
 <20190315014457.GA17210@opus.istwok.net>
Message-ID: <6u2m8e11a6ct2sfdisfne007th2mmt2jij@4ax.com>

On Thu, 14 Mar 2019 20:44:57 -0500, you wrote:

>On Thu, Mar 14, 2019 at 03:46:44PM -0500, Greg Oliver wrote:
>> Hi,
>> 
>> I was wondering if anyone has successfully setup MythTV to be a typee of
>> multi-tenant setup.  2 cases:
>> 
>> 1.  Same household, multiple viewers - same recording.  A good way to keep
>> user 1 from deleting recordings before they are viewed by all - anyone ever
>> come up with a design for this?
>
>As Simon already mentioned, this has been discussed but nothing was
>ever done.
>
>> 2.  Different Households - 1 backend (case 1 still applies as well).
>> Recording Groups can keep them separate with views, but still #1 would
>> apply and step on each other here.
>
>I actually have some experience with this.
>
>We use recording groups to partition the recordings.  Recordings in
>shared groups require coordination before they are deleted.  Recording
>in groups that are exclusive can be freely deleted at will.
>
>I personally patched the source code so that new, recording rules on
>specififc frontends automatically default to a custom recording group.
>While writing this reply, I realized I should change that to use a
>hsot-specific setting so it could be used by others.
>
>David
>
>> Anyone have something similar working with good results?

The thought I came up with was similar to this.  I make recordings on
my system for my mother, and want to eventually automate how she gets
access to them instead of my having to use mythexport/mythimport to
copy them to her MythTV box.  I record things exclusively for her
using a different recording group, and have a template set up so that
I can easily use that to make a recording rule that puts things in
that recording group.  However, I also have a second set of recording
directories on each of my recording partitions, and the template tells
mythbackend to record her recordings to those different directories.
So in theory, when I get around to it, I can make a script that will
automatically export the database entries from any new recording that
is in one of those directories to her system, and delete it from mine.
The recording file would stay in her recording directory on my system,
and her system would have access to it via the network and would
delete it from there when she has watched it.  That is the simple bit.

Handling recordings that we both want to watch is more difficult.  I
put them in a joint recording group, but the recording files go to my
normal recording directories.  Here my idea was to use hard links from
those recordings to the directory that my mother's MythTV box has
network access to.  I would have my script export the database entries
for these recordings, but also leave that data in my database.  She
would be able to play these recordings from the hard link from her
network accessible directory on my box.  Then when she deleted them,
if I had not watched and deleted the recording, her delete would just
delete the hard link and leave the recording for me to watch still. If
I watched it first, then my delete of the recording would delete it
from my recording directory, but leave the recording file still in her
recording directory where it had been hard linked, and her delete
would then delete the actual recording file.

I have not actually got this working yet, but I think it should allow
it all to work automatically.

Trying to make multiple users work with only one database is even more
difficult - without significant new code in MythTV, I can not see a
way to make it work.  But if the frontend boxes that are being used
for a multiuser setup are capable enough, they could each have a
mythbackend setup with a dummy tuner, and that mythbackend could get
the database exports from the main recording mythbackend and be used
like my mother's system.  The secondary frontend boxes would still
need to have a mythfrontend setup that talked to the main recording
mythbackend to set up recordings from the Guide, but they would never
play or delete recordings from anything except the mythfrontend that
talked to the local mythbackend.

As an alternative, if the other frontend boxes were capable of doing
recordings themselves, but just lacked tuners (or access to the
aerials), then it is possible to set up the tuners on the main MythTV
box for remote access using SAT>IP via TVHeadend or minisatip.  I have
done this with my DVB-S2 tuners.  SAT>IP manages the tuners so that if
a tuner is already on the correct frequency for a newly requested
channel, it will re-use the tuner to service the new request.  So
multiple backends can be recording the same channels at the same time
using the same physical tuners.  The big downside of SAT>IP is that
MythTV does not understand the SAT>IP protocol, so it is incapable of
doing a scan to find the channels that way.  So you have to set up all
the SAT>IP channels via external software, and it has to put the URLs
for the channels into the MythTV database (iptv_channel table and
channel table) or create a playlist file that MythTV can use to load
the channel data.  But this is possible to do - it is how I do my pay
TV satellite channels from my DVB-S2 tuners.  MythTV is also unable to
gather EIT EPG data from SAT>IP tuners, so that also needs to be done
externally and loaded into MythTV using an xmltv file via
mythfilldatabase.

From georgeb1962 at gmail.com  Fri Mar 15 04:37:30 2019
From: georgeb1962 at gmail.com (George Bingham)
Date: Thu, 14 Mar 2019 23:37:30 -0500
Subject: [mythtv-users] mythfrontend on Nvidia Shield
In-Reply-To: <e191cb0c-c1ea-0b32-b270-034430860709@gmail.com>
References: <3cdc06f0-c4d6-dd15-db1d-762a4970dbed@gmail.com>
 <064f08c6-096b-5532-bfb0-e3a412be4218@gmail.com>
 <e191cb0c-c1ea-0b32-b270-034430860709@gmail.com>
Message-ID: <CAA2WpHPNHKdbLEqtUJpLnAwimm8G5_8LMJeKvVffRaCXWMCayw@mail.gmail.com>

On Wed, Mar 13, 2019 at 4:35 PM James Abernathy <jfabernathy at gmail.com>
wrote:

>
> On 3/13/19 2:54 PM, Peter Bennett wrote:
> >
> >
> > Try Settings -> Video -> Playback -> Advanced Playback Settings. Make
> > sure AVSync2 is checked then set ANSync2 -> audio correction. The
> > default value is 10. This should  fix lip sync within a short time
> > after a skip. A higher value will resync lips quicker but could cause
> > jitter at other times. A low value will take longer to resync but may
> > improve smoothness of playback in general. However is all cases the
> > sync should come back eventually.
> >
> > Another possibility - check Settings -> Video -> Playback -> General
> > Playback -> Enable Music Choice. Disable this unless you are watching
> > music choice channels. In some cases having this enabled could cause
> > loss of synchronization.
> >
> > Peter
>
> Another thing. I just watched a program where the automatic commercial
> skip worked good enough that I didn't do any manual skipping. The lip
> sync was good after the automatic skips, but in one of the scenes a few
> second after a commercial the actor was saying no and shaking his head
> side to side. The lips were in sync, but head motions was a little jerky
> like it was filmed at 15 fps. I backed the program up 30 seconds, paused
> for a few seconds and then let it run.  The video was fine with perfect
> lip sync and no jerky head motion.
>
> Jim A
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org



Hello everyone,

I hope this is helpful to some, and sorry if it's annoying to many, but
does everyone realize that you can edit the automatic commercial detection
after it's done it's thing?

I have to admit here that I did not know that you could manually edit the
commercial skip for several months before I  just happened to hit the magic
button on my keyboard.

It works best if you have a full keyboard on your frontend, which in my
case was a laptop that'd be near me in front of the couch when my TV was
connected to the backend / frontend driving my main tv display. This
allowed me to be watching pre-recorded content, with confidence that
commercial skip would not unintentionally skip parts of the show (due to
the fact that I'd edited the commercial cuts to ensure they were correct
before watching) while editing the commercials detected in the next show I
was going to watch on the TV using my laptop.

I realize that many use a remote to control their frontends, but if you
happen to have one with it's own keyboard, or a laptop like I do, it's very
easy to do once you get the hang of it. It'd take a few minutes to do for
an hour long show, but the results are worth it if you are annoyed by
skipping commercials manually, or depending on the automated commercial
detection - and then being frustrated by either missed scenes of your show
or missed commercials.

To edit a pre-recorded show, hit the "E" key, which bring you into edit
mode, and the left arrow / right arrow will move you to the next / previous
skip point, using the up and down arrow, you can switch between going back
or forward in time several seconds or just a few, a few quick taps and you
can locate the point where a commercial really does begin, and move the
skip point to that point. On screen instructions make it clear what you are
doing and once you get the hang of it it is very straightforward and quick.
Once you have corrected the beginning and end of each commercial skip, the
Escape key brings up a menu to save and continue.

I got into the habit of reviewing each pre-recorded show before watching
and also set the "commercial skip' settings to skip automatically without
showing the skip on screen.

I know many of you are thinking "well Duh! that's mythtv's whole point" but
since many folks on this list claim that they don't use commercial
detection because it's not perfect - it makes me wonder if they know how
easy it is to "correct" the commercial skip.

Just hoping that this helps someone get more satisfaction out of using
mythtv!!

-- George
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190314/6961056b/attachment.html>

From jharbestonus at gmail.com  Fri Mar 15 13:15:58 2019
From: jharbestonus at gmail.com (Jay Harbeston)
Date: Fri, 15 Mar 2019 09:15:58 -0400
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <3723e59f169e973dd1c95fd96d63986ea98be881.camel@glenb.us>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
 <64105823.20190315003753@gmail.com>
 <CADUj1OsugxkC0M+RTNtyKDkxayGtWOOgzUQxLXzp_55PkygABQ@mail.gmail.com>
 <3e08ac6204f025a2728af4299c5767f54c9ee498.camel@glenb.us>
 <CADUj1OsVrrr2LynpfqTQfshMx6UEOQ2==4yuaMAGuGO2o7jqHA@mail.gmail.com>
 <3723e59f169e973dd1c95fd96d63986ea98be881.camel@glenb.us>
Message-ID: <5DBE9EF9-05C2-461D-A9A6-FA1B8CEA2C2F@gmail.com>



> On Mar 14, 2019, at 9:59 PM, glen <glenb at glenb.us> wrote:
> 
> On Thu, 2019-03-14 at 21:45 -0400, Tom Dexter wrote:
>> On 3/14/19, glen <

> 
> no i didn't miss it, it was just a longshot, that perhaps the hdhr when interacting with that switch is not getting
> onto the table maintained by the switch, and since it once did, i was thinking possibly firmware change which would 
> explain why the new ones don't connect either. but easiest to try a different switch since they work directly connected
> to router

I have a couple hdhr3-2us tuners and a couple hdhr4-2us tuners, and the only problems I have had with them have been the wall warts as mentioned earlier.

I did have a switch that failed in a weird way recently, but the tuners were not attached to the tuners. A few years ago, I had some lightning problems(fried a router, UPS, and other items), but the switches that I had survived at that time so I believe the recent failure of the switch was related to that event. It wasn?t a hard failure currently either.

The switches I use are cheap 8 port 1gb that are usually around $30 US. If you have another switch around, try connecting to them, or if you don?t, make sure to try them on your router ports and see if they still fail. If they don?t fail when connected to your router, it?s time to replace the switch.

I consider the switches that I use to be ?disposable? and if they fail I?m not out much.

Bottom line, plug your tuners directly into the router to see if they work there. If so, replace the switch.

Regards


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190315/39a3cd5a/attachment-0001.html>

From jharbestonus at gmail.com  Fri Mar 15 13:22:55 2019
From: jharbestonus at gmail.com (Jay Harbeston)
Date: Fri, 15 Mar 2019 09:22:55 -0400
Subject: [mythtv-users] Multi-tenant type of setup
In-Reply-To: <A861EA27-01C3-4E73-AF5B-1B99B62AA211@thehobsons.co.uk>
References: <CAF4tN+-TxM8XW4KeRWs_jF4yNFb84zxsaujhb1XKcT7Mj9aBjQ@mail.gmail.com>
 <A861EA27-01C3-4E73-AF5B-1B99B62AA211@thehobsons.co.uk>
Message-ID: <9CBAF588-8C66-42D8-AE1E-726E678A6336@gmail.com>



> On Mar 14, 2019, at 5:48 PM, Simon Hobson <linux at thehobsons.co.uk> wrote:
> 
> Greg Oliver <oliver.greg at gmail.com> wrote:
> 
>> I was wondering if anyone has successfully setup MythTV to be a typee of multi-tenant setup.  2 cases:
>> 
>> 1.  Same household, multiple viewers - same recording.  A good way to keep user 1 from deleting recordings before they are viewed by all - anyone ever come up with a design for this?
>> 
>> 2.  Different Households - 1 backend (case 1 still applies as well).  Recording Groups can keep them separate with views, but still #1 would apply and step on each other here.
>> 
>> Anyone have something similar working with good results?
> 


A couple of things you can do is set the number of days to delete to more than a couple of days. If you set the date long enough, you could check the deleted group once a week to see what has been deleted.

Also you could do a shell script that would give you a list of deleted shows every day. With this you could then go and undelete them manually.  

You could also set mythtv to ONLY delete when space is needed.


You could also set up a separate backend for them. This may be the closest to what you want.

Regards.


From mkbloke at gmail.com  Fri Mar 15 13:32:02 2019
From: mkbloke at gmail.com (Ian Cameron)
Date: Fri, 15 Mar 2019 13:32:02 +0000
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
Message-ID: <CAC+xXWOjdSkA-j70UAJtETJAK-YtFrOaDc6j2_VeaarehjfDOg@mail.gmail.com>

On Thu, 14 Mar 2019 at 22:19, Tom Dexter <digitalaudiorock at gmail.com> wrote:

> I have no idea what to make of that at all. I can only think that
> maybe the switch is going bad(?) and the requirements of the HDHR to
> maintain a link are more restrictive than other devices?? Sort of
> crazy. Any opinions would be welcome.
>

It's rather puzzling, for sure.

Does the switch have an external PSU?  Could you perhaps try (if you have
one or can borrow one from somebody) another universal PSU set to the
correct voltage/pin polarity/DC connector that has an equivalent or greater
output power rating (DC amps/wattage)?

It sounds like the only thing you have not tried so far, as far as I can
remember reading in this thread.

Cheers, Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190315/472afd20/attachment.html>

From digitalaudiorock at gmail.com  Fri Mar 15 14:11:48 2019
From: digitalaudiorock at gmail.com (Tom Dexter)
Date: Fri, 15 Mar 2019 10:11:48 -0400
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <CAC+xXWOjdSkA-j70UAJtETJAK-YtFrOaDc6j2_VeaarehjfDOg@mail.gmail.com>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
 <CAC+xXWOjdSkA-j70UAJtETJAK-YtFrOaDc6j2_VeaarehjfDOg@mail.gmail.com>
Message-ID: <CADUj1Ou43T+A+tyjP7hRi32CQRfFXqJ3kUBHSt5OP6cCYWdDEQ@mail.gmail.com>

On 3/15/19, Ian Cameron <mkbloke at gmail.com> wrote:
> On Thu, 14 Mar 2019 at 22:19, Tom Dexter <digitalaudiorock at gmail.com>
> wrote:
>
>> I have no idea what to make of that at all. I can only think that
>> maybe the switch is going bad(?) and the requirements of the HDHR to
>> maintain a link are more restrictive than other devices?? Sort of
>> crazy. Any opinions would be welcome.
>>
>
> It's rather puzzling, for sure.
>
> Does the switch have an external PSU?  Could you perhaps try (if you have
> one or can borrow one from somebody) another universal PSU set to the
> correct voltage/pin polarity/DC connector that has an equivalent or greater
> output power rating (DC amps/wattage)?
>
> It sounds like the only thing you have not tried so far, as far as I can
> remember reading in this thread.
>
> Cheers, Ian
>

Thanks everyone for the replies by the way!

Yea it really is. Everything, especially the fact that it works
connected to the router, seems to point to an issue either with the
switch or it's power supply. I'd have to chase down a PSU (I might
even have a universal one hanging around) to test the latter.

What's odd however is that only the HDHRs seem to be sensitive to, or
affected by the switch. Other devices work perfectly on it. Stranger
yet is that my slightly older HDHR is still connected to it and has no
problem at all, and yet even the new HDHR had problems....sort of
random at that point.

Both of my existing units have the original firmware from 2016. I've
never done anything to them. In fact that one that's working on the
switch has 20160411 while the only that doesn't play nice with it has
20161117. I may try updating the problem one to the current firmware
and see what that does.

Thanks!
Tom

From johnpilk222 at gmail.com  Fri Mar 15 14:45:47 2019
From: johnpilk222 at gmail.com (John Pilkington)
Date: Fri, 15 Mar 2019 14:45:47 +0000
Subject: [mythtv-users] mythfrontend on Nvidia Shield
In-Reply-To: <CAA2WpHPNHKdbLEqtUJpLnAwimm8G5_8LMJeKvVffRaCXWMCayw@mail.gmail.com>
References: <3cdc06f0-c4d6-dd15-db1d-762a4970dbed@gmail.com>
 <064f08c6-096b-5532-bfb0-e3a412be4218@gmail.com>
 <e191cb0c-c1ea-0b32-b270-034430860709@gmail.com>
 <CAA2WpHPNHKdbLEqtUJpLnAwimm8G5_8LMJeKvVffRaCXWMCayw@mail.gmail.com>
Message-ID: <c98533a8-3099-a432-ec44-83cf07969f3f@gmail.com>

On 15/03/2019 04:37, George Bingham wrote:

> I know many of you are thinking "well Duh! that's mythtv's whole point" 
> but since many folks on this list claim that they don't use commercial 
> detection because it's not perfect - it makes me wonder if they know how 
> easy it is to "correct" the commercial skip.
> 
> Just hoping that this helps someone get more satisfaction out of using 
> mythtv!!
> 

I do this too - except that I have never run commflag.  Of course many 
of my recordings are from the BBC and don't have 'commercials' as such; 
but they promote other BBC stuff with great enthusiasm.

On TV recordings I use the editor, usually with skip lengths between 1 
minute and 1 keyframe, which gives completely acceptable control unless 
one is aiming to do 'real' video editing.

With DVB radio the smallest 'supported' step size is 1 second, but the 
half-second step can be used to cut with a real granularity of 1/3 
seconds with some experimenting.

After that, which usually takes 'a few' minutes, myth will play with no 
need for stepping;  I usually go on to remove the cuts altogether, which 
saves a lot of disk space.

John P



From oliver.greg at gmail.com  Fri Mar 15 15:57:26 2019
From: oliver.greg at gmail.com (Greg Oliver)
Date: Fri, 15 Mar 2019 10:57:26 -0500
Subject: [mythtv-users] Multi-tenant type of setup
In-Reply-To: <6u2m8e11a6ct2sfdisfne007th2mmt2jij@4ax.com>
References: <CAF4tN+-TxM8XW4KeRWs_jF4yNFb84zxsaujhb1XKcT7Mj9aBjQ@mail.gmail.com>
 <20190315014457.GA17210@opus.istwok.net>
 <6u2m8e11a6ct2sfdisfne007th2mmt2jij@4ax.com>
Message-ID: <CAF4tN+8u8+0hN9waM9=f8NAeUmATvRJ4cAPT-BMi8xb8Ff6rzA@mail.gmail.com>

On Thu, Mar 14, 2019 at 9:55 PM Stephen Worthington <
stephen_agent at jsw.gen.nz> wrote:

> On Thu, 14 Mar 2019 20:44:57 -0500, you wrote:
> >On Thu, Mar 14, 2019 at 03:46:44PM -0500, Greg Oliver wrote:
> >> Hi,
> >>
> >> I was wondering if anyone has successfully setup MythTV to be a typee of
> >> multi-tenant setup.  2 cases:
> >>
> >> 1.  Same household, multiple viewers - same recording.  A good way to
> keep
> >> user 1 from deleting recordings before they are viewed by all - anyone
> ever
> >> come up with a design for this?
> >
> >As Simon already mentioned, this has been discussed but nothing was
> >ever done.
> >
> >> 2.  Different Households - 1 backend (case 1 still applies as well).
> >> Recording Groups can keep them separate with views, but still #1 would
> >> apply and step on each other here.
> >
> >I actually have some experience with this.
> >
> >We use recording groups to partition the recordings.  Recordings in
> >shared groups require coordination before they are deleted.  Recording
> >in groups that are exclusive can be freely deleted at will.
> >
> >I personally patched the source code so that new, recording rules on
> >specififc frontends automatically default to a custom recording group.
> >While writing this reply, I realized I should change that to use a
> >hsot-specific setting so it could be used by others.
> >
> >David
> >
> >> Anyone have something similar working with good results?
>
> The thought I came up with was similar to this.  I make recordings on
> my system for my mother, and want to eventually automate how she gets
> access to them instead of my having to use mythexport/mythimport to
> copy them to her MythTV box.  I record things exclusively for her
> using a different recording group, and have a template set up so that
> I can easily use that to make a recording rule that puts things in
> that recording group.  However, I also have a second set of recording
> directories on each of my recording partitions, and the template tells
> mythbackend to record her recordings to those different directories.
> So in theory, when I get around to it, I can make a script that will
> automatically export the database entries from any new recording that
> is in one of those directories to her system, and delete it from mine.
> The recording file would stay in her recording directory on my system,
> and her system would have access to it via the network and would
> delete it from there when she has watched it.  That is the simple bit.
>
> Handling recordings that we both want to watch is more difficult.  I
> put them in a joint recording group, but the recording files go to my
> normal recording directories.  Here my idea was to use hard links from
> those recordings to the directory that my mother's MythTV box has
> network access to.  I would have my script export the database entries
> for these recordings, but also leave that data in my database.  She
> would be able to play these recordings from the hard link from her
> network accessible directory on my box.  Then when she deleted them,
> if I had not watched and deleted the recording, her delete would just
> delete the hard link and leave the recording for me to watch still. If
> I watched it first, then my delete of the recording would delete it
> from my recording directory, but leave the recording file still in her
> recording directory where it had been hard linked, and her delete
> would then delete the actual recording file.
>
> I have not actually got this working yet, but I think it should allow
> it all to work automatically.
>
> Trying to make multiple users work with only one database is even more
> difficult - without significant new code in MythTV, I can not see a
> way to make it work.  But if the frontend boxes that are being used
> for a multiuser setup are capable enough, they could each have a
> mythbackend setup with a dummy tuner, and that mythbackend could get
> the database exports from the main recording mythbackend and be used
> like my mother's system.  The secondary frontend boxes would still
> need to have a mythfrontend setup that talked to the main recording
> mythbackend to set up recordings from the Guide, but they would never
> play or delete recordings from anything except the mythfrontend that
> talked to the local mythbackend.
>
> As an alternative, if the other frontend boxes were capable of doing
> recordings themselves, but just lacked tuners (or access to the
> aerials), then it is possible to set up the tuners on the main MythTV
> box for remote access using SAT>IP via TVHeadend or minisatip.  I have
> done this with my DVB-S2 tuners.  SAT>IP manages the tuners so that if
> a tuner is already on the correct frequency for a newly requested
> channel, it will re-use the tuner to service the new request.  So
> multiple backends can be recording the same channels at the same time
> using the same physical tuners.  The big downside of SAT>IP is that
> MythTV does not understand the SAT>IP protocol, so it is incapable of
> doing a scan to find the channels that way.  So you have to set up all
> the SAT>IP channels via external software, and it has to put the URLs
> for the channels into the MythTV database (iptv_channel table and
> channel table) or create a playlist file that MythTV can use to load
> the channel data.  But this is possible to do - it is how I do my pay
> TV satellite channels from my DVB-S2 tuners.  MythTV is also unable to
> gather EIT EPG data from SAT>IP tuners, so that also needs to be done
> externally and loaded into MythTV using an xmltv file via
> mythfilldatabase.
>

I think I will just create a MythTV API proxy that handles it all..  I know
that currently mythfrontend does not use the API, but the remotes I am
concerned with all are..  That seems like the best way to move forward for
me.  I will try something simple to make sure python can keep up without
too much lag on playback before I get too deep into it..
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190315/a4ccc76a/attachment.html>

From hikavdh at gmail.com  Fri Mar 15 16:18:10 2019
From: hikavdh at gmail.com (Hika van den Hoven)
Date: Fri, 15 Mar 2019 17:18:10 +0100
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <CADUj1Ou43T+A+tyjP7hRi32CQRfFXqJ3kUBHSt5OP6cCYWdDEQ@mail.gmail.com>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com> 
 <CAC+xXWOjdSkA-j70UAJtETJAK-YtFrOaDc6j2_VeaarehjfDOg@mail.gmail.com>
 <CADUj1Ou43T+A+tyjP7hRi32CQRfFXqJ3kUBHSt5OP6cCYWdDEQ@mail.gmail.com>
Message-ID: <1082784743.20190315171810@gmail.com>

Hoi Tom,

Friday, March 15, 2019, 3:11:48 PM, you wrote:

> On 3/15/19, Ian Cameron <mkbloke at gmail.com> wrote:
>> On Thu, 14 Mar 2019 at 22:19, Tom Dexter <digitalaudiorock at gmail.com>
>> wrote:
>>
>>> I have no idea what to make of that at all. I can only think that
>>> maybe the switch is going bad(?) and the requirements of the HDHR to
>>> maintain a link are more restrictive than other devices?? Sort of
>>> crazy. Any opinions would be welcome.
>>>
>>
>> It's rather puzzling, for sure.
>>
>> Does the switch have an external PSU?  Could you perhaps try (if you have
>> one or can borrow one from somebody) another universal PSU set to the
>> correct voltage/pin polarity/DC connector that has an equivalent or greater
>> output power rating (DC amps/wattage)?
>>
>> It sounds like the only thing you have not tried so far, as far as I can
>> remember reading in this thread.
>>
>> Cheers, Ian
>>

> Thanks everyone for the replies by the way!

> Yea it really is. Everything, especially the fact that it works
> connected to the router, seems to point to an issue either with the
> switch or it's power supply. I'd have to chase down a PSU (I might
> even have a universal one hanging around) to test the latter.

> What's odd however is that only the HDHRs seem to be sensitive to, or
> affected by the switch. Other devices work perfectly on it. Stranger
> yet is that my slightly older HDHR is still connected to it and has no
> problem at all, and yet even the new HDHR had problems....sort of
> random at that point.

> Both of my existing units have the original firmware from 2016. I've
> never done anything to them. In fact that one that's working on the
> switch has 20160411 while the only that doesn't play nice with it has
> 20161117. I may try updating the problem one to the current firmware
> and see what that does.

> Thanks!
> Tom

Do perhaps the laptop etc that work, connect at 100 Mb and do the
failing homeruns try 1 Gb. Mine has a 1 Gb port


Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens


From mtdean at thirdcontact.com  Fri Mar 15 16:28:55 2019
From: mtdean at thirdcontact.com (Michael T. Dean)
Date: Fri, 15 Mar 2019 12:28:55 -0400
Subject: [mythtv-users] Editing recordings/skipping commercials (was Re:
 mythfrontend on Nvidia Shield)
In-Reply-To: <CAA2WpHPNHKdbLEqtUJpLnAwimm8G5_8LMJeKvVffRaCXWMCayw@mail.gmail.com>
References: <3cdc06f0-c4d6-dd15-db1d-762a4970dbed@gmail.com>
 <064f08c6-096b-5532-bfb0-e3a412be4218@gmail.com>
 <e191cb0c-c1ea-0b32-b270-034430860709@gmail.com>
 <CAA2WpHPNHKdbLEqtUJpLnAwimm8G5_8LMJeKvVffRaCXWMCayw@mail.gmail.com>
Message-ID: <5C8BD2C7.4080206@thirdcontact.com>

On 03/15/2019 12:37 AM, George Bingham wrote:
> To edit a pre-recorded show, hit the "E" key, which bring you into 
> edit mode, and the left arrow / right arrow will move you to the next 
> / previous skip point, using the up and down arrow, you can switch 
> between going back or forward in time several seconds or just a few, a 
> few quick taps and you can locate the point where a commercial really 
> does begin, and move the skip point to that point. On screen 
> instructions make it clear what you are doing and once you get the 
> hang of it it is very straightforward and quick. Once you have 
> corrected the beginning and end of each commercial skip, the Escape 
> key brings up a menu to save and continue.

There's some good information on editing recordings at 
https://www.mythtv.org/wiki/Editing_Recordings , including sections on 
"Advanced Editing" and "Editing without the MENU key"--both of which 
contain many tips for how to make editing much easier (especially if 
you're using a remote and not a keyboard).

> I got into the habit of reviewing each pre-recorded show before 
> watching and also set the "commercial skip' settings to skip 
> automatically without showing the skip on screen.

Note that you don't need to set MythTV to automatically skip 
commercials.  The commercial skip list is separate from the cut list.  
Once you edit the recording and load the commercial skip list 
(LOADCOMMSKIP, by default, Z or End) or create your own cut list, you 
have created a cut list which will always be cut from playback.

If you only add cuts where commercial weren't detected and try to rely 
on a combination of commercial skip list and cut lists, you would need 
to set MythTV to automatically skip commercials. However, this is a bad 
idea in general because there is no way to "unskip" a section of the 
show that was mismarked as a commercial. So, you're better off loading 
the commercial skip list and/or making a complete cut list. (FWIW, I 
find it's actually easier to not load the skip list because it's easier 
to add cuts than to remove or move them, so I just move through the 
recording and SELECT to start and SELECT to end cuts where you actually 
want them.)

Mike

From digitalaudiorock at gmail.com  Fri Mar 15 17:31:03 2019
From: digitalaudiorock at gmail.com (Tom Dexter)
Date: Fri, 15 Mar 2019 13:31:03 -0400
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <1082784743.20190315171810@gmail.com>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
 <CAC+xXWOjdSkA-j70UAJtETJAK-YtFrOaDc6j2_VeaarehjfDOg@mail.gmail.com>
 <CADUj1Ou43T+A+tyjP7hRi32CQRfFXqJ3kUBHSt5OP6cCYWdDEQ@mail.gmail.com>
 <1082784743.20190315171810@gmail.com>
Message-ID: <CADUj1OshcoE-an5s-HZx-YC84VZTHDJA4A6v-TQpq=BXosxmew@mail.gmail.com>

On 3/15/19, Hika van den Hoven <hikavdh at gmail.com> wrote:
> Hoi Tom,
>
> Friday, March 15, 2019, 3:11:48 PM, you wrote:
>
>> On 3/15/19, Ian Cameron <mkbloke at gmail.com> wrote:
>>> On Thu, 14 Mar 2019 at 22:19, Tom Dexter <digitalaudiorock at gmail.com>
>>> wrote:
>>>
>>>> I have no idea what to make of that at all. I can only think that
>>>> maybe the switch is going bad(?) and the requirements of the HDHR to
>>>> maintain a link are more restrictive than other devices?? Sort of
>>>> crazy. Any opinions would be welcome.
>>>>
>>>
>>> It's rather puzzling, for sure.
>>>
>>> Does the switch have an external PSU?  Could you perhaps try (if you
>>> have
>>> one or can borrow one from somebody) another universal PSU set to the
>>> correct voltage/pin polarity/DC connector that has an equivalent or
>>> greater
>>> output power rating (DC amps/wattage)?
>>>
>>> It sounds like the only thing you have not tried so far, as far as I can
>>> remember reading in this thread.
>>>
>>> Cheers, Ian
>>>
>
>> Thanks everyone for the replies by the way!
>
>> Yea it really is. Everything, especially the fact that it works
>> connected to the router, seems to point to an issue either with the
>> switch or it's power supply. I'd have to chase down a PSU (I might
>> even have a universal one hanging around) to test the latter.
>
>> What's odd however is that only the HDHRs seem to be sensitive to, or
>> affected by the switch. Other devices work perfectly on it. Stranger
>> yet is that my slightly older HDHR is still connected to it and has no
>> problem at all, and yet even the new HDHR had problems....sort of
>> random at that point.
>
>> Both of my existing units have the original firmware from 2016. I've
>> never done anything to them. In fact that one that's working on the
>> switch has 20160411 while the only that doesn't play nice with it has
>> 20161117. I may try updating the problem one to the current firmware
>> and see what that does.
>
>> Thanks!
>> Tom
>
> Do perhaps the laptop etc that work, connect at 100 Mb and do the
> failing homeruns try 1 Gb. Mine has a 1 Gb port
>
>
> Tot mails,
>   Hika                            mailto:hikavdh at gmail.com
>

It's a GB switch for sure. As far as I know the laptop is connecting
at 1GB, though I'm not going to waste a second of my life trying to
figure out where MS hid that in Windows 10 (ONLY use it for
work...hate it).

On a side note, I upgraded the HDHR that has the issue with that
switch to the newest firmware, and it still only maintains a link when
connected to the router, but not the switch. I really think there's
something up with that switch (or it's power).

Tom

From linux at thehobsons.co.uk  Fri Mar 15 19:49:28 2019
From: linux at thehobsons.co.uk (Simon Hobson)
Date: Fri, 15 Mar 2019 19:49:28 +0000
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
Message-ID: <4075CFF1-8231-4D53-86F2-CF241F389812@thehobsons.co.uk>

Tom Dexter <digitalaudiorock at gmail.com> wrote:

...
> I have no idea what to make of that at all. I can only think that
> maybe the switch is going bad(?)

It does sound rather like the switch. They can fail in "interesting" ways - I've had them "sort of" stop passing packets reliably, as in passing some packets but not others !

Certainly in a case like this, the obvious thing to do is swap the switch and see what happens.

The fact that some devices work and others don't could be simply down to slight variations in how the protocols are implemented. Behind the scenes there's actually a complete (albeit relatively simple) signalling protocol to allow the two ends to negotiate a link between them.
A few years ago we had a customer with 2 sites with a road in between. We sold them an optical link which turned out to have an "interesting" design feature which meant that it didn't work with all switches. The people who supplied and installed it for us couldn't tell us what the issue was - but we eventually tracked down that these units didn't negotiate the link properly so they would only work with managed switched where the port can be hard configured to a specific set of link parameters.


> Any recommendations are welcome. I was looking at a Netgear GS316
> which seem to get pretty good reviews.

It's looks like it's a variant of their GS1nn models. I've always found* the [FG]S1nn models to be very reliable, so I'd have no hesitation in trying the 316.

* With work hats on, I've known a lot of networks run on them.


From digitalaudiorock at gmail.com  Fri Mar 15 20:01:29 2019
From: digitalaudiorock at gmail.com (Tom Dexter)
Date: Fri, 15 Mar 2019 16:01:29 -0400
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <4075CFF1-8231-4D53-86F2-CF241F389812@thehobsons.co.uk>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
 <4075CFF1-8231-4D53-86F2-CF241F389812@thehobsons.co.uk>
Message-ID: <CADUj1Ou6Txm4=4_K3HsJPkw26FHwoatz3PkHAKSyPfNN2MD7Hw@mail.gmail.com>

On 3/15/19, Simon Hobson <linux at thehobsons.co.uk> wrote:
> Tom Dexter <digitalaudiorock at gmail.com> wrote:
>
> ...
>> I have no idea what to make of that at all. I can only think that
>> maybe the switch is going bad(?)
>
> It does sound rather like the switch. They can fail in "interesting" ways -
> I've had them "sort of" stop passing packets reliably, as in passing some
> packets but not others !
>
> Certainly in a case like this, the obvious thing to do is swap the switch
> and see what happens.
>
> The fact that some devices work and others don't could be simply down to
> slight variations in how the protocols are implemented. Behind the scenes
> there's actually a complete (albeit relatively simple) signalling protocol
> to allow the two ends to negotiate a link between them.
> A few years ago we had a customer with 2 sites with a road in between. We
> sold them an optical link which turned out to have an "interesting" design
> feature which meant that it didn't work with all switches. The people who
> supplied and installed it for us couldn't tell us what the issue was - but
> we eventually tracked down that these units didn't negotiate the link
> properly so they would only work with managed switched where the port can be
> hard configured to a specific set of link parameters.
>
>
>> Any recommendations are welcome. I was looking at a Netgear GS316
>> which seem to get pretty good reviews.
>
> It's looks like it's a variant of their GS1nn models. I've always found* the
> [FG]S1nn models to be very reliable, so I'd have no hesitation in trying the
> 316.
>
> * With work hats on, I've known a lot of networks run on them.
>

Thanks for the reply! I think you're right on all that. I've had my
existing switch for quite a while and it was really cheap. I might
just go ahead and get that Netgear. Thanks for the recommendation!

Tom

From uid000 at gmail.com  Sat Mar 16 02:15:04 2019
From: uid000 at gmail.com (Zach Cutlip)
Date: Fri, 15 Mar 2019 19:15:04 -0700
Subject: [mythtv-users] lircd unreliable after Ubuntu upgrade 16.04 >
 18.04
In-Reply-To: <2b1m8epehm288l8dli6d2t4e2tqrjvkrc9@4ax.com>
References: <CACxx4MRv5dmSpqtQgovfwKwnpbVAjpWTh7w0HUCEu8x_s=0SQQ@mail.gmail.com>
 <CAH8UtKMKmCZNU02CRSTYrt08SKDj3RANYVy-tS1zaXA7PGBbpA@mail.gmail.com>
 <2122734e-b02b-0c70-6e30-f3e534920673@gmail.com>
 <32ej8ep7qdun3u0vi1mop9dkrt923gm8co@4ax.com>
 <CACxx4MS9X8dvpVCnbS-QyP5hVCJFC3ADQBaQ4d4m=z2_2RFxZQ@mail.gmail.com>
 <2b1m8epehm288l8dli6d2t4e2tqrjvkrc9@4ax.com>
Message-ID: <CACxx4MTEMdb=+YnCm9KXJOHELgLFdx9TGUcRVQpQcPPcstncUQ@mail.gmail.com>

Hi Stephen

Thanks for the additional advice.

I checked the things you suggested.

- My mythfrontend was configured to look for its lircd socket in
/var/run/lirc/lircd, so it was finding that with no problem. I added
your systemd service descriptor though, just in case.
- My lircrc for myth maps the buttons to the remote name as defined in
lircd.conf.d. In my case, I have:

begin remote
  name  Tivo_S2

So my lircrc buttons all are for "remote = Tivo_S2".

I tried changing a few of those to "default" to correlate to
lirc_options.conf as you suggested. Those buttons stopped working
altogether until I changed them back.

Here's a thing I did notice however: If I run irw while interacting
with MythTV, I see that irw sees about 90% of the button presses (not
perfect, but much better), even while mythrontend is only responding
to about 60%. In fact there are many times when myth doesn't respond
at all, but irw clearly saw the button presses. I feel like there's
some issue with mythfrontend. I checked settings in the frontend
configuration and didn't see anything significant.

Does this give any ideas?

Thanks,
Zach

On Thu, Mar 14, 2019 at 7:20 PM Stephen Worthington
<stephen_agent at jsw.gen.nz> wrote:
>
> On Thu, 14 Mar 2019 14:38:00 -0700, you wrote:
>
> >On Wed, Mar 13, 2019 at 7:29 PM Stephen Worthington
> ><stephen_agent at jsw.gen.nz> wrote:
> >>
> >> On Wed, 13 Mar 2019 21:24:18 +0100, you wrote:
> >>
> >> >On 13/03/19 19:05, Allen Edwards wrote:
> >> >>
> >> >>
> >> >>
> >> >> On Wed, Mar 13, 2019 at 10:48 AM Zach Cutlip <uid000 at gmail.com
> >> >> <mailto:uid000 at gmail.com>> wrote:
> >> >>
> >> >>     Hello,
> >> >>
> >> >>     After upgrading my MythTV setup from Ubuntu 16.04 (lirc 0.9.0) to
> >> >>     Ubuntu 18.04 (lirc 0.10.0), and jumping through various hoops to get
> >> >>     lircd working again, I'm finding it to be very unreliable.
> >> >>
> >> >>     Any suggestions, or things to try?
> >> >
> >> >
> >> >Most likely an upgrade problem. The upgrade to 0.9.0 requires manual
> >> >intervention [1]
> >> >
> >> >Cheers!
> >> >--alec
> >> >
> >> >
> >> >[1] https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1791409
> >>
> >> The lirc package as installed by 18.04 is broken.  There are a number
> >> of problems with it, but the one that is most obvious is that
> >> lirc-setup does not work at all (it can not find required library .so
> >> files).  Your problem sounds like one of the other problems, which is
> >> that it sets up systemd to run lircmd, lirc-uinput and irexec as
> >> daemons, but does not set up valid configuration for those daemons. So
> >> they run in the background and one (I think it is lircd-uinput) steals
> >> keystrokes from the main lirc daemon.  So try running these commands
> >> and see if it fixes your problem:
> >>
> >> sudo systemctl stop lircmd
> >> sudo systemctl stop lirc-uinput
> >> sudo systemctl stop irexec
> >> sudo systemctl disable lircmd
> >> sudo systemctl disable lirc-uinput
> >> sudo systemctl disable irexec
> >>
> >> Alternatively, if you want to fix all the problems I found in 18.04's
> >> lirc package, you can download and run the script I wrote:
> >>
> >> http://www.jsw.gen.nz/mythtv/lirc-ubuntu-18.04-install.sh
> >>
> >> It fixes lirc-setup, the above problems and probably a few more I have
> >> forgotten about.  It needs to be run with sudo or as root.  I am a bit
> >> surprised that your lirc is working at all - the 16.04 to 18.04
> >> upgrade does not normally produce a working lirc setup, so you must
> >> have done a lot of manual configuration.
> >
> >Hi Stephen,
> >
> >You are right; I didn't have a working lirc setup at all after
> >upgrade. I had to troubleshoot quite a bit to get it working again
> >even to the degree that it is.
> >
> >I don't think any of these are running:
> >
> > $ ps -ef | grep -E 'lircmd|lircd-uinput|irexec'
> >knath    12295 11492  0 14:24 pts/1    00:00:00 grep -E
> >lircmd|lircd-uinput|irexec
> >$ ps -ef | grep lirc
> >root     12435     1  0 14:29 ?        00:00:00 /usr/sbin/lircd --nodaemon
> >
> >I stopped & disabled the services just in case though.
> >
> >Is there anything else I can check, or diagnosis I can do?
> >
> >Here's my lirc_options.conf if it helps:
> >
> >[lircd]
> >nodaemon        = False
> ># driver          = devinput
> >driver          = default
> ># device          = auto
> >device          = /dev/lirc0
> >output          = /var/run/lirc/lircd
> >pidfile         = /var/run/lirc/lircd.pid
> >plugindir       = /usr/lib/i386-linux-gnu/lirc/plugins
> >permission      = 666
> >allow-simulate  = No
> >repeat-max      = 600
> >#effective-user =
> >#listen         = [address:]port
> >#connect        = host[:port]
> >#loglevel       = 6
> >#release        = true
> >#release_suffix = _EVUP
> >#logfile        = ...
> >#driver-options = ...
> >
> >[lircmd]
> >uinput          = False
> >nodaemon        = False
> >
> ># [modinit]
> ># code = /usr/sbin/modprobe lirc_serial
> ># code1 = /usr/bin/setfacl -m g:lirc:rw /dev/uinput
> ># code2 = ...
> >
> >
> ># [lircd-uinput]
> ># add-release-events = False
> ># release-timeout    = 200
> ># release-suffix     = _EVUP
> >
> >And here's the start to my lircd remote definition, which has always
> >worked perfectly until now:
> >
> >begin remote
> >
> >  name  Tivo_S2
> >  bits           32
> >  flags SPACE_ENC|CONST_LENGTH
> >  eps            20
> >  aeps          200
> >
> >  header       9000  4500
> >  one           562  1687
> >  zero          562   562
> >  ptrail        562
> >  repeat       9000  2250
> >  gap          108000
> >  min_repeat      1
> >  toggle_bit      0
> >
> >  frequency    38000
> >
> >      begin codes
> >          TIVO                     0x00000000A10CE00F
> >          TV_POWER                 0x00000000A10C0807
> >          TV_INPUT                 0x00000000A10C2C03
> >          WINDOW                   0x00000000A10C220D
> >          LIVE_TV                  0x00000000A10C8807
> >          INFO                     0x00000000A10CC807
> >          GUIDE                    0x00000000A10C6C03
> >          UP                       0x00000000A10C2807
> >          LEFT                     0x00000000A10CE807
> >          RIGHT                    0x00000000A10CA807
> >          DOWN                     0x00000000A10C6807
>
> That looks OK, but check that your lirc hardware is actually appearing
> as the /dev/lirc0 device.
>
> However, MythTV looks for a /dev/lircd device for the keystroke
> outputs from the lirc daemon.  Do you have that?  I had to link the
> default lirc output device (/var/run/lirc/lircd) to /dev/lircd to make
> it work, as I could not find any way to configure MythTV to use the
> new location for the lirc output device, and changing the setting in
> lirc_options.conf made other programs unable to work with lirc.  If
> you look at my script, you will find that it creates a
> lircd-dev.service file in /etc/systemd/system to do this automatically
> when the lirc daemon is started:
>
> root at mypvr:/etc/systemd/system# cat lircd-dev.service
> [Unit]
> Description=Create the /dev/lircd device (linked to /run/lirc/lircd)
> as required by MythTV.
> After=lircd.service
>
> [Service]
> Type=simple
> ExecStart=/bin/bash -c "ln -s /run/lirc/lircd /dev/lircd"
>
> [Install]
> WantedBy=multi-user.target
>
> Note that /var/run/ is a link to /run, so /run/lirc/lircd is the same
> as /var/run/lirc/lircd in the lirc_options.conf file.
>
> Also, check your MythTV .lircrc files:
>
> root at mypvr:/home/stephen# cat .lircrc
> #Custom lircrc generated via mythbuntu-lirc-generator
> #All application specific lircrc files are within ~/.lirc
> include ~/.lirc/mythtv
> include ~/.lirc/mplayer
> include ~/.lirc/xine
> include ~/.lirc/vlc
> include ~/.lirc/xmame
> include ~/.lirc/xmess
> include ~/.lirc/totem
> include ~/.lirc/elisa
> include ~/.lirc/irexec
>
> root at mypvr:/home/stephen# head -n 24 .lirc/mythtv
> # lircrc for devinput with Hauppauge Nova TD-500 and Hauppauge
> HVR-900R2 remotes (with lirc 0.9.0),
> # and MCE remotes.
>
> # Save it in ~/.lircrc
>
> begin
>     remote = devinput
>     prog = mythtv
>              # Guide key
>     button = KEY_EPG
> #    config = S
>     config = Ctrl+Alt+G
>     repeat = 0
>     delay = 0
> end
>
> begin
>     remote = devinput
>     prog = mythtv
>     button = KEY_EXIT
>     config = Escape
>     repeat = 0
>     delay = 0
> end
>
> To work in your setup, all the entries for MythTV (with prog=mythtv
> lines) will have to have the remote= lines set to match the driver=
> setting in your lirc_options.conf file.  So they should have "remote =
> default", where mine have "remote = devinput".
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org



-- 
:wq!

From lunchtimelarry at gmail.com  Sat Mar 16 03:12:40 2019
From: lunchtimelarry at gmail.com (Larry Kennedy)
Date: Fri, 15 Mar 2019 23:12:40 -0400
Subject: [mythtv-users] MythTV V30 for CentOS (EL7)
Message-ID: <CAPCvy=myRdU1naj5vm+=tszT39X0dOreLKecnb+FdhMUN96vEw@mail.gmail.com>

Is anyone building v30 RPMs for EL7?  I've been using scrpms and it appears
to only go as far as V29.

Larry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190315/6c362601/attachment.html>

From hobbes1069 at gmail.com  Sat Mar 16 12:39:28 2019
From: hobbes1069 at gmail.com (Richard Shaw)
Date: Sat, 16 Mar 2019 07:39:28 -0500
Subject: [mythtv-users] MythTV V30 for CentOS (EL7)
In-Reply-To: <CAPCvy=myRdU1naj5vm+=tszT39X0dOreLKecnb+FdhMUN96vEw@mail.gmail.com>
References: <CAPCvy=myRdU1naj5vm+=tszT39X0dOreLKecnb+FdhMUN96vEw@mail.gmail.com>
Message-ID: <CAN3TeO0wzdBWqq-=xMZtnXtbDMjvZeGjXHYihuVtQ2=8knsgzQ@mail.gmail.com>

On Fri, Mar 15, 2019 at 10:14 PM Larry Kennedy <lunchtimelarry at gmail.com>
wrote:

> Is anyone building v30 RPMs for EL7?  I've been using scrpms and it
> appears to only go as far as V29.
>

I'm trying a local build on my desktop. If it works I'll see about doing an
official build on RPM Fusion. EL 7 is getting a bit long in the tooth but
I'll see what I can do.

Thanks,
Richard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190316/83e5db12/attachment.html>

From mythtv3 at duncb.co.uk  Sat Mar 16 12:47:36 2019
From: mythtv3 at duncb.co.uk (Duncan Brown)
Date: Sat, 16 Mar 2019 12:47:36 +0000
Subject: [mythtv-users] MythTV V30 for CentOS (EL7)
In-Reply-To: <CAPCvy=myRdU1naj5vm+=tszT39X0dOreLKecnb+FdhMUN96vEw@mail.gmail.com>
References: <CAPCvy=myRdU1naj5vm+=tszT39X0dOreLKecnb+FdhMUN96vEw@mail.gmail.com>
Message-ID: <8496b268-65de-fb56-d175-80915aa325a8@duncb.co.uk>

On 16/03/2019 03:12, Larry Kennedy wrote:
> Is anyone building v30 RPMs for EL7?? I've been using scrpms and it 
> appears to only go as far as V29.
>
> Larry
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

You just need to change the target to el7myth

http://scrpms.net/pub/RPMS/el7myth/x86_64/

Not sure why it is being hidden away like that though

Either way, working for me

cheers

Dunc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190316/28f78b67/attachment.html>

From oliver.greg at gmail.com  Sun Mar 17 02:47:09 2019
From: oliver.greg at gmail.com (Greg Oliver)
Date: Sat, 16 Mar 2019 21:47:09 -0500
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <CADUj1Ou6Txm4=4_K3HsJPkw26FHwoatz3PkHAKSyPfNN2MD7Hw@mail.gmail.com>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
 <4075CFF1-8231-4D53-86F2-CF241F389812@thehobsons.co.uk>
 <CADUj1Ou6Txm4=4_K3HsJPkw26FHwoatz3PkHAKSyPfNN2MD7Hw@mail.gmail.com>
Message-ID: <CAF4tN+9O=srsHPsrn2_1x-Ywf3YL6U3xKoj-J84tM7ovXrmkyA@mail.gmail.com>

On Fri, Mar 15, 2019 at 3:02 PM Tom Dexter <digitalaudiorock at gmail.com>
wrote:

> On 3/15/19, Simon Hobson <linux at thehobsons.co.uk> wrote:
> > Tom Dexter <digitalaudiorock at gmail.com> wrote:
> >
> > ...
> >> I have no idea what to make of that at all. I can only think that
> >> maybe the switch is going bad(?)
> >
> > It does sound rather like the switch. They can fail in "interesting"
> ways -
> > I've had them "sort of" stop passing packets reliably, as in passing some
> > packets but not others !
> >
> > Certainly in a case like this, the obvious thing to do is swap the switch
> > and see what happens.
> >
> > The fact that some devices work and others don't could be simply down to
> > slight variations in how the protocols are implemented. Behind the scenes
> > there's actually a complete (albeit relatively simple) signalling
> protocol
> > to allow the two ends to negotiate a link between them.
> > A few years ago we had a customer with 2 sites with a road in between. We
> > sold them an optical link which turned out to have an "interesting"
> design
> > feature which meant that it didn't work with all switches. The people who
> > supplied and installed it for us couldn't tell us what the issue was -
> but
> > we eventually tracked down that these units didn't negotiate the link
> > properly so they would only work with managed switched where the port
> can be
> > hard configured to a specific set of link parameters.
> >
> >
> >> Any recommendations are welcome. I was looking at a Netgear GS316
> >> which seem to get pretty good reviews.
> >
> > It's looks like it's a variant of their GS1nn models. I've always found*
> the
> > [FG]S1nn models to be very reliable, so I'd have no hesitation in trying
> the
> > 316.
> >
> > * With work hats on, I've known a lot of networks run on them.
> >
>
> Thanks for the reply! I think you're right on all that. I've had my
> existing switch for quite a while and it was really cheap. I might
> just go ahead and get that Netgear. Thanks for the recommendation!
>
> Tom
>

I work with Telephone switches and networks by day, and also have a lot of
projects I use raspberry Pis and PoE cameras for and I have been using
these cheap Zyxel switches for a while now ::

https://www.amazon.com/8-Port-Gigabit-Managed-Fanless-GS1900-8HP/dp/B00GU1KULM/ref=sr_1_1?keywords=zyxel+poe&qid=1552790568&s=gateway&sr=8-1

They are managed and have been very good for me delivering power to all 8
ports as well as fill line rate on all ports.  I am slowly replacing my
Cisco Small Business switches with them since the Cisco switches are not
PoE+ (AT) and my cameras require AT.

If you do try them out, be warned they have a qeird provisioning quirk that
even if you set a ports PVID, you also have to set that VLAN as untagged on
the membership page.  Most switches I have used automatically do that for
you and it took me an hour or so of packet captures to figure that out.

Just another vendor option for you.  Ubiquity also sells some switches I am
going to try next that are more modern in the software and allow you to run
SDN software to control them like all modern enterprise and carrier
switches.

-Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190316/dc1f3ea5/attachment.html>

From stephen_agent at jsw.gen.nz  Sun Mar 17 09:06:03 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Sun, 17 Mar 2019 22:06:03 +1300
Subject: [mythtv-users] lircd unreliable after Ubuntu upgrade 16.04 >
 18.04
In-Reply-To: <CACxx4MTEMdb=+YnCm9KXJOHELgLFdx9TGUcRVQpQcPPcstncUQ@mail.gmail.com>
References: <CACxx4MRv5dmSpqtQgovfwKwnpbVAjpWTh7w0HUCEu8x_s=0SQQ@mail.gmail.com>
 <CAH8UtKMKmCZNU02CRSTYrt08SKDj3RANYVy-tS1zaXA7PGBbpA@mail.gmail.com>
 <2122734e-b02b-0c70-6e30-f3e534920673@gmail.com>
 <32ej8ep7qdun3u0vi1mop9dkrt923gm8co@4ax.com>
 <CACxx4MS9X8dvpVCnbS-QyP5hVCJFC3ADQBaQ4d4m=z2_2RFxZQ@mail.gmail.com>
 <2b1m8epehm288l8dli6d2t4e2tqrjvkrc9@4ax.com>
 <CACxx4MTEMdb=+YnCm9KXJOHELgLFdx9TGUcRVQpQcPPcstncUQ@mail.gmail.com>
Message-ID: <vv0s8ed23sih26tgcntvt3qdl301hh2l2q@4ax.com>

On Fri, 15 Mar 2019 19:15:04 -0700, you wrote:

>Hi Stephen
>
>Thanks for the additional advice.
>
>I checked the things you suggested.
>
>- My mythfrontend was configured to look for its lircd socket in
>/var/run/lirc/lircd, so it was finding that with no problem. I added
>your systemd service descriptor though, just in case.
>- My lircrc for myth maps the buttons to the remote name as defined in
>lircd.conf.d. In my case, I have:
>
>begin remote
>  name  Tivo_S2
>
>So my lircrc buttons all are for "remote = Tivo_S2".
>
>I tried changing a few of those to "default" to correlate to
>lirc_options.conf as you suggested. Those buttons stopped working
>altogether until I changed them back.
>
>Here's a thing I did notice however: If I run irw while interacting
>with MythTV, I see that irw sees about 90% of the button presses (not
>perfect, but much better), even while mythrontend is only responding
>to about 60%. In fact there are many times when myth doesn't respond
>at all, but irw clearly saw the button presses. I feel like there's
>some issue with mythfrontend. I checked settings in the frontend
>configuration and didn't see anything significant.
>
>Does this give any ideas?
>
>Thanks,
>Zach

I think we need to trace things through right from the beginning - the
hardware.  You are using an old Tivo remote, but you have not said
what infrared receiver hardware you are using.  Is it a USB or PCI
device?  Mine is a USB device:

root at mypvr:~# lsusb | grep -i infr
Bus 005 Device 002: ID 0609:031d SMK Manufacturing, Inc. eHome
Infrared Receiver

root at mypvr:~# ll /dev/input/by-id/
total 0
drwxr-xr-x 2 root root 120 Mar 14 01:37 ./
drwxr-xr-x 4 root root 480 Mar 14 01:37 ../
lrwxrwxrwx 1 root root   9 Mar 14 01:37
usb-Logitech_USB_Receiver-event-kbd -> ../event2
lrwxrwxrwx 1 root root   9 Mar 14 01:37
usb-Logitech_USB_Receiver-if01-event-mouse -> ../event3
lrwxrwxrwx 1 root root   9 Mar 14 01:37
usb-Logitech_USB_Receiver-if01-mouse -> ../mouse0
lrwxrwxrwx 1 root root  10 Mar 14 01:37
usb-SMK_eHome_Infrared_Transceiver_SM005h4M-event-if00 -> ../event12

root at mypvr:~# ll /dev/input/by-path/
total 0
drwxr-xr-x 2 root root 140 Mar 14 01:37 ./
drwxr-xr-x 4 root root 480 Mar 14 01:37 ../
lrwxrwxrwx 1 root root   9 Mar 14 01:37
pci-0000:00:12.0-usb-0:2:1.0-event-kbd -> ../event2
lrwxrwxrwx 1 root root   9 Mar 14 01:37
pci-0000:00:12.0-usb-0:2:1.1-event-mouse -> ../event3
lrwxrwxrwx 1 root root   9 Mar 14 01:37
pci-0000:00:12.0-usb-0:2:1.1-mouse -> ../mouse0
lrwxrwxrwx 1 root root  10 Mar 14 01:37
pci-0000:00:13.0-usb-0:5:1.0-event -> ../event12
lrwxrwxrwx 1 root root  10 Mar 14 01:37 platform-eeepc-wmi-event ->
../event13

root at mypvr:~# ll /dev/lirc*
crw-rw---- 1 root video 241, 0 Mar 14 01:37 /dev/lirc0
lrwxrwxrwx 1 root root      15 Mar 14 01:38 /dev/lircd ->
/run/lirc/lircd=
lrwxrwxrwx 1 root root      13 Mar 14 01:37 /dev/lirc-mce ->
input/event12

I have a udev rule that creates the /dev/lirc-mce device, but I am not
using that device in my lirc_options.conf at the moment as there is
now only one IR remote receiver and it also shows up as /dev/lirc0.
Which I think happens because of the kernel, and the device is made
available to the "video" group in this rule:

root at mypvr:/lib/udev# grep -ir lirc *
rules.d/80-debian-compat.rules:KERNEL=="lirc[0-9]*", GROUP="video"

Now my IR receiver is handled by the kernel IR code, so if I stop
mythfrontend (and any other programs that use lirc, such as irexec),
and then stop lircd:

sudo stop lircd

Then ir-keytable shows it as an IR receiver device, using the kernel
mceusb device and using rc6 encoding:

root at mypvr:~# ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event12) with:
	Name: Media Center Ed. eHome Infrared Remote Transceiver
(0609:031d)
	Driver: mceusb, table: rc-rc6-mce
	lirc device: /dev/lirc0
	Supported protocols: other lirc rc-5 rc-5-sz jvc sony nec
sanyo mce_kbd rc-6 sharp xmp 
	Enabled protocols: lirc rc-6 
	bus: 3, vendor/product: 0609:031d, version: 0x0000
	Repeat delay = 500 ms, repeat period = 125 ms

And I can press every key on my remote and get a scancode displayed by
ir-keytable -t:

root at mypvr:~# ir-keytable -t
Testing events. Please, press CTRL-C to abort.
331876.252285: lirc protocol(rc6_mce): scancode = 0x800f0401
331876.252306: event type EV_MSC(0x04): scancode = 0x800f0401
331876.252306: event type EV_KEY(0x01) key_down: KEY_1(0x0002)
331876.252306: event type EV_SYN(0x00).
1331876.359268: lirc protocol(rc6_mce): scancode = 0x800f0401
331876.359294: event type EV_MSC(0x04): scancode = 0x800f0401
331876.359294: event type EV_SYN(0x00).
331876.488021: event type EV_KEY(0x01) key_up: KEY_1(0x0002)
331876.488021: event type EV_SYN(0x00).
331876.969385: lirc protocol(rc6_mce): scancode = 0x800f0402 toggle=1
331876.969408: event type EV_MSC(0x04): scancode = 0x800f0402
331876.969408: event type EV_KEY(0x01) key_down: KEY_2(0x0003)
331876.969408: event type EV_SYN(0x00).
2331877.076235: lirc protocol(rc6_mce): scancode = 0x800f0402 toggle=1
331877.076246: event type EV_MSC(0x04): scancode = 0x800f0402
331877.076246: event type EV_SYN(0x00).
331877.208024: event type EV_KEY(0x01) key_up: KEY_2(0x0003)
331877.208024: event type EV_SYN(0x00).
331877.760309: lirc protocol(rc6_mce): scancode = 0x800f0403
331877.760332: event type EV_MSC(0x04): scancode = 0x800f0403
331877.760332: event type EV_KEY(0x01) key_down: KEY_3(0x0004)
331877.760332: event type EV_SYN(0x00).
3331877.866216: lirc protocol(rc6_mce): scancode = 0x800f0403
331877.866236: event type EV_MSC(0x04): scancode = 0x800f0403
331877.866236: event type EV_SYN(0x00).
331877.996022: event type EV_KEY(0x01) key_up: KEY_3(0x0004)
331877.996022: event type EV_SYN(0x00).
331882.641123: lirc protocol(rc6_mce): scancode = 0x800f040f toggle=1
331882.641162: event type EV_MSC(0x04): scancode = 0x800f040f
331882.641162: event type EV_KEY(0x01) key_down: KEY_MENU(0x008b)
331882.641162: event type EV_SYN(0x00).
331882.747042: lirc protocol(rc6_mce): scancode = 0x800f040f toggle=1
331882.747060: event type EV_MSC(0x04): scancode = 0x800f040f
331882.747060: event type EV_SYN(0x00).
331882.876049: event type EV_KEY(0x01) key_up: KEY_MENU(0x008b)
331882.876049: event type EV_SYN(0x00).
331883.807005: lirc protocol(rc6_mce): scancode = 0x800f0424
331883.807030: event type EV_MSC(0x04): scancode = 0x800f0424
331883.807030: event type EV_KEY(0x01) key_down: KEY_DVD(0x0185)
331883.807030: event type EV_SYN(0x00).
331883.914077: lirc protocol(rc6_mce): scancode = 0x800f0424
331883.914102: event type EV_MSC(0x04): scancode = 0x800f0424
331883.914102: event type EV_SYN(0x00).
331884.044099: event type EV_KEY(0x01) key_up: KEY_DVD(0x0185)
331884.044099: event type EV_SYN(0x00).
331887.589880: lirc protocol(rc6_mce): scancode = 0x800f0426 toggle=1
331887.589900: event type EV_MSC(0x04): scancode = 0x800f0426
331887.589900: event type EV_KEY(0x01) key_down: KEY_EPG(0x016d)
331887.589900: event type EV_SYN(0x00).
331887.695853: lirc protocol(rc6_mce): scancode = 0x800f0426 toggle=1
331887.695870: event type EV_MSC(0x04): scancode = 0x800f0426
331887.695870: event type EV_SYN(0x00).
331887.824018: event type EV_KEY(0x01) key_up: KEY_EPG(0x016d)
331887.824018: event type EV_SYN(0x00).
331888.407841: lirc protocol(rc6_mce): scancode = 0x800f0425
331888.407865: event type EV_MSC(0x04): scancode = 0x800f0425
331888.407865: event type EV_KEY(0x01) key_down: KEY_TUNER(0x0182)
331888.407865: event type EV_SYN(0x00).
331888.514829: lirc protocol(rc6_mce): scancode = 0x800f0425
331888.514843: event type EV_MSC(0x04): scancode = 0x800f0425
331888.514843: event type EV_SYN(0x00).
331888.644024: event type EV_KEY(0x01) key_up: KEY_TUNER(0x0182)
331888.644024: event type EV_SYN(0x00).
^C

So, does that happen with your remote?  If your remote is actually
using the "default" driver, as specified in your lirc_options, then I
believe that it should not be showing up in ir-keytable.  If it is
showing up in ir-keytable, then it is likely you should be using the
devinput driver.

Also, you posted your remote definition file:

begin remote

  name  Tivo_S2
  bits           32
  flags SPACE_ENC|CONST_LENGTH
  eps            20
  aeps          200

  header       9000  4500
  one           562  1687
  zero          562   562
  ptrail        562
  repeat       9000  2250
  gap          108000
  min_repeat      1
  toggle_bit      0

  frequency    38000

      begin codes
          TIVO                     0x00000000A10CE00F
          TV_POWER                 0x00000000A10C0807
          TV_INPUT                 0x00000000A10C2C03
          WINDOW                   0x00000000A10C220D
          LIVE_TV                  0x00000000A10C8807
          INFO                     0x00000000A10CC807
          GUIDE                    0x00000000A10C6C03
          UP                       0x00000000A10C2807
          LEFT                     0x00000000A10CE807
          RIGHT                    0x00000000A10CA807
          DOWN                     0x00000000A10C6807

But what file name is that in, and where is it referenced in the IR
setup files?  The driver line in your lirc_options.conf file says
"driver = default", which should mean that there is a
/etc/lirc/lircd.conf.d/default.lircd.conf file, in the same way I have
a devinput.lircd.conf file:

root at mypvr:/etc/lirc/lircd.conf.d# ll
total 48
drwxr-xr-x 2 root root  4096 Oct  6 03:51 ./
drwxr-xr-x 3 root root  4096 Oct  6 05:46 ../
-rw-r--r-- 1 root root 35015 Oct  6 05:26 devinput.lircd.conf
-rw-r--r-- 1 root root   615 Aug 13  2017 README.conf.d

and that should be where your Tivo_S2 definition is.

From lunchtimelarry at gmail.com  Sun Mar 17 13:59:01 2019
From: lunchtimelarry at gmail.com (Larry Kennedy)
Date: Sun, 17 Mar 2019 09:59:01 -0400
Subject: [mythtv-users] MythTV V30 for CentOS (EL7)
In-Reply-To: <8496b268-65de-fb56-d175-80915aa325a8@duncb.co.uk>
References: <CAPCvy=myRdU1naj5vm+=tszT39X0dOreLKecnb+FdhMUN96vEw@mail.gmail.com>
 <8496b268-65de-fb56-d175-80915aa325a8@duncb.co.uk>
Message-ID: <CAPCvy=kd1RUHkSHvkh0PuZTHW+VZHP4cs8DLBzPsPBAmLQ4ggQ@mail.gmail.com>

On Sat, Mar 16, 2019 at 8:49 AM Duncan Brown <mythtv3 at duncb.co.uk> wrote:

> On 16/03/2019 03:12, Larry Kennedy wrote:
>
> Is anyone building v30 RPMs for EL7?  I've been using scrpms and it
> appears to only go as far as V29.
>
> Larry
>
> _______________________________________________
> mythtv-users mailing listmythtv-users at mythtv.orghttp://lists.mythtv.org/mailman/listinfo/mythtv-usershttp://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
> You just need to change the target to el7myth
>
> http://scrpms.net/pub/RPMS/el7myth/x86_64/
>
> Not sure why it is being hidden away like that though
>
> Either way, working for me
>
> cheers
> Dunc
>

Thanks!  I'll look into it.


> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190317/4d4fa9ee/attachment.html>

From ctreleaven at cogeco.ca  Sun Mar 17 17:21:18 2019
From: ctreleaven at cogeco.ca (Craig Treleaven)
Date: Sun, 17 Mar 2019 13:21:18 -0400
Subject: [mythtv-users] 3TB...poof
Message-ID: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>

So, yet again, the drive with all my recordings is unreadable.  This has happened to me in September 2015, August 2013 and at least one time before that although I?m not sure of the date.  And again this past Tuesday night.  I know the dates because in 2013 I started labelling drives and enclosures with the date purchased and I purchased these items specifically because of these problems.

I?m running Myth on Mac so virtually none of you care.  However, if there is someone out there on OS X that has experienced this and actually KNOWS a solution, I?d love to hear it.  I?ve tried a number of things over the last several days with success.  Various versions of Apple?s Disk Utility.  Swapping the drive into a couple of known-good enclosures.  Tried TestDisk.   The closest I got was that Disk Utility would mount the volume even though it reported it as damaged.  But CarbonCopyCloner was never able to copy more than 150MB off it.

Craig


From Larry.Finger at lwfinger.net  Sun Mar 17 17:40:53 2019
From: Larry.Finger at lwfinger.net (Larry Finger)
Date: Sun, 17 Mar 2019 12:40:53 -0500
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
Message-ID: <ab7f5a29-fc12-353e-f139-ab8cc504c83d@lwfinger.net>

On 3/17/19 12:21 PM, Craig Treleaven wrote:
> So, yet again, the drive with all my recordings is unreadable.  This has happened to me in September 2015, August 2013 and at least one time before that although I?m not sure of the date.  And again this past Tuesday night.  I know the dates because in 2013 I started labelling drives and enclosures with the date purchased and I purchased these items specifically because of these problems.
> 
> I?m running Myth on Mac so virtually none of you care.  However, if there is someone out there on OS X that has experienced this and actually KNOWS a solution, I?d love to hear it.  I?ve tried a number of things over the last several days with success.  Various versions of Apple?s Disk Utility.  Swapping the drive into a couple of known-good enclosures.  Tried TestDisk.   The closest I got was that Disk Utility would mount the volume even though it reported it as damaged.  But CarbonCopyCloner was never able to copy more than 150MB off it.

What does smartctl have to say about this drive? The utility is part of 
smartmontools.

I do not use OS X, but I have had a number of disk failures over the years. I 
finally implemented RAID on my system. I have / and /home mounted on RAID5, and 
/boot on RAID0, with /boot/efi not in a RAID array. Since setting up the system, 
I had one drive fail. Given Murphy's law, the failed drive was the one with 
/boot/efi, but I had a backup copy on another drive. A few minutes work using a 
rescue system got me back up and running with no loss of data.

Larry


From mtusers at dorscm.wakeful.net  Sun Mar 17 19:03:57 2019
From: mtusers at dorscm.wakeful.net (Matt Dorsch)
Date: Sun, 17 Mar 2019 15:03:57 -0400
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <ab7f5a29-fc12-353e-f139-ab8cc504c83d@lwfinger.net>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
 <ab7f5a29-fc12-353e-f139-ab8cc504c83d@lwfinger.net>
Message-ID: <CAFWmYv2VxDShxQ183hKwSb1twwxPq+pbmKbojhtfftCMEnDhQw@mail.gmail.com>

If you made a list of the possible causes of the failures, MythTV shouldn't
be on the list. It has no control over the correctness of the filesystem.
That would be the OS's job.

If the drive passes a read-only test, which only checks if each sector can
be read successfully not the contents of the sector, then either the OS had
an issue that corrupted the FS, or there was a problem with the data
channel. Both of those a pretty unlikely these days, except old hardware
might cause a data issue.

If the drive fails a read-only test, the damage goes beyond the filesystem,
either to the circuit board of the drive or the platters themselves. This
is usually caused by low quality components, old age, or bad power. If your
system is on a UPS with AVR, it's probably not bad power.

SMART can be a useful tool to see if drives are showing signs of age:
Backblaze has done some analysis to see what SMART metrics are useful when
trying to predict an impending drive failure.

https://www.backblaze.com/blog/what-smart-stats-indicate-hard-drive-failures/

Not all manufacturers use the stats in transparent ways: e.g., one of my
drives reports a Reallocated Sectors Count of 2^31 - 1.

On a different note, 5 years ago I discovered several of my drives had
failed, but the OS still kept using them. A few months later, it dawned on
me that I probably shouldn't be using the vacuum cleaner's carpet
attachment right next to the computers and external disk under my desk.

Matt

On Sun, Mar 17, 2019 at 1:41 PM Larry Finger <Larry.Finger at lwfinger.net>
wrote:

> On 3/17/19 12:21 PM, Craig Treleaven wrote:
> > So, yet again, the drive with all my recordings is unreadable.  This has
> happened to me in September 2015, August 2013 and at least one time before
> that although I?m not sure of the date.  And again this past Tuesday
> night.  I know the dates because in 2013 I started labelling drives and
> enclosures with the date purchased and I purchased these items specifically
> because of these problems.
> >
> > I?m running Myth on Mac so virtually none of you care.  However, if
> there is someone out there on OS X that has experienced this and actually
> KNOWS a solution, I?d love to hear it.  I?ve tried a number of things over
> the last several days with success.  Various versions of Apple?s Disk
> Utility.  Swapping the drive into a couple of known-good enclosures.  Tried
> TestDisk.   The closest I got was that Disk Utility would mount the volume
> even though it reported it as damaged.  But CarbonCopyCloner was never able
> to copy more than 150MB off it.
>
> What does smartctl have to say about this drive? The utility is part of
> smartmontools.
>
> I do not use OS X, but I have had a number of disk failures over the
> years. I
> finally implemented RAID on my system. I have / and /home mounted on
> RAID5, and
> /boot on RAID0, with /boot/efi not in a RAID array. Since setting up the
> system,
> I had one drive fail. Given Murphy's law, the failed drive was the one
> with
> /boot/efi, but I had a backup copy on another drive. A few minutes work
> using a
> rescue system got me back up and running with no loss of data.
>
> Larry
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190317/8e3e17c4/attachment.html>

From ctreleaven at cogeco.ca  Mon Mar 18 02:42:18 2019
From: ctreleaven at cogeco.ca (Craig Treleaven)
Date: Sun, 17 Mar 2019 22:42:18 -0400
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <CAFWmYv2VxDShxQ183hKwSb1twwxPq+pbmKbojhtfftCMEnDhQw@mail.gmail.com>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
 <ab7f5a29-fc12-353e-f139-ab8cc504c83d@lwfinger.net>
 <CAFWmYv2VxDShxQ183hKwSb1twwxPq+pbmKbojhtfftCMEnDhQw@mail.gmail.com>
Message-ID: <2F8DAFE4-B18B-41D1-9027-3D8FA5786DA6@cogeco.ca>

> On Mar 17, 2019, at 3:03 PM, Matt Dorsch <mtusers at dorscm.wakeful.net> wrote:
> 
> If you made a list of the possible causes of the failures, MythTV shouldn't be on the list. It has no control over the correctness of the filesystem. That would be the OS's job.
> 
> If the drive passes a read-only test, which only checks if each sector can be read successfully not the contents of the sector, then either the OS had an issue that corrupted the FS, or there was a problem with the data channel. Both of those a pretty unlikely these days, except old hardware might cause a data issue.
> 
> If the drive fails a read-only test, the damage goes beyond the filesystem, either to the circuit board of the drive or the platters themselves. This is usually caused by low quality components, old age, or bad power. If your system is on a UPS with AVR, it's probably not bad power.
> 

I?ve had multiple failures of the volume that Myth stores recordings on.  I?ve had no other failures.  I know that?s not a statistical sample but Myth has something to  do with it.

The failures have been with different sizes of drives and from different vendors.  Note that after the failure, the drive enclosure is usually no longer usable (one exception).  Ie if I put a known-good drive in the enclosure, it is not readable.  As I said earlier, the damaged drive is also unreadable in a known-good enclosure.  The failed enclosures are from different vendors and include Firewire 400, USB 2 and USB 3 methods of connection.

I don?t record a lot.  I have 4 OTA tuners (HDHomeruns) receiving North American broadcast HDTV.  It is very rare to have all tuners recording at the same time.  I do flag for commercials during recording so that may up the load.  I don?t believe I?ve ever been watching a recording during a failure.  The backend does not run any other applications.

After the first failure, I equipped the backend with an Uninterruptible Power Supply.  The UPS was in place during the next 2 failures.  The UPS died a few months ago and I haven?t replaced it.  There were no indications of a power problem during the most recent failure.  My clock in my microwave is the most sensitive indicator of a power problem in our house and I haven?t had to reset it in a long time.

Craig
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190317/1280947d/attachment.html>

From mystica at gmail.com  Mon Mar 18 04:32:00 2019
From: mystica at gmail.com (Mike Hodson)
Date: Sun, 17 Mar 2019 22:32:00 -0600
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <2F8DAFE4-B18B-41D1-9027-3D8FA5786DA6@cogeco.ca>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
 <ab7f5a29-fc12-353e-f139-ab8cc504c83d@lwfinger.net>
 <CAFWmYv2VxDShxQ183hKwSb1twwxPq+pbmKbojhtfftCMEnDhQw@mail.gmail.com>
 <2F8DAFE4-B18B-41D1-9027-3D8FA5786DA6@cogeco.ca>
Message-ID: <CAN++4hHUQTAp3bDrVEnPYmBYxjMVp=DbWJjT=+QhUvEkQi1U2A@mail.gmail.com>

On Sun, Mar 17, 2019, 20:43 Craig Treleaven <ctreleaven at cogeco.ca> wrote

> I?ve had multiple failures of the volume that Myth stores recordings on.
> I?ve had no other failures.  I know that?s not a statistical sample but
> Myth has something to  do with it.
>

Possibly the simple constant use is the only mitigating factor here. Myth
definitely does cause near constant access, if it has a lot of recordings
scheduled.


> The failures have been with different sizes of drives and from different
> vendors.  Note that after the failure, the drive enclosure is usually no
> longer usable (one exception).
>

So none of these are internal disks? All are external? I'm going to venture
that the electronics in an external enclosure may not be the best option
for 24/7 use.

 Ie if I put a known-good drive in the enclosure, it is not readable.  As I
> said earlier, the damaged drive is also unreadable in a known-good
> enclosure.  The failed enclosures are from different vendors and include
> Firewire 400, USB 2 and USB 3 methods of connection.
>

So the enclosures all die, and in the process kill the disk physically in
some method it sounds like?


> I don?t record a lot.  I have 4 OTA tuners (HDHomeruns) receiving North
> American broadcast HDTV.  It is very rare to have all tuners recording at
> the same time.  I do flag for commercials during recording so that may up
> the load.  I don?t believe I?ve ever been watching a recording during a
> failure.  The backend does not run any other applications.
>

It's not so much about throughput but the fact the disk and enclosure are
powered all the time.


> After the first failure, I equipped the backend with an Uninterruptible
> Power Supply.  The UPS was in place during the next 2 failures.  The UPS
> died a few months ago and I haven?t replaced it.  There were no indications
> of a power problem during the most recent failure.  My clock in my
> microwave is the most sensitive indicator of a power problem in our house
> and I haven?t had to reset it in a long time.
>

The microwave will only tell you about outages; not under or overvolt
periods. It would be useful to have some sort of meter that plugs into the
wall outlet and logs the voltage and frequency on your line, to understand
if surges may be killibg the cheap made-to-be-disposable electronics in the
enclosures.

Could you perhaps build the drive internally to your Myth machine if you
maybe bought a bigger case?  External enclosures are decidedly meant for
part-time use.

Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190317/8fd0567b/attachment.html>

From mystica at gmail.com  Mon Mar 18 04:37:25 2019
From: mystica at gmail.com (Mike Hodson)
Date: Sun, 17 Mar 2019 22:37:25 -0600
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <CAN++4hHUQTAp3bDrVEnPYmBYxjMVp=DbWJjT=+QhUvEkQi1U2A@mail.gmail.com>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
 <ab7f5a29-fc12-353e-f139-ab8cc504c83d@lwfinger.net>
 <CAFWmYv2VxDShxQ183hKwSb1twwxPq+pbmKbojhtfftCMEnDhQw@mail.gmail.com>
 <2F8DAFE4-B18B-41D1-9027-3D8FA5786DA6@cogeco.ca>
 <CAN++4hHUQTAp3bDrVEnPYmBYxjMVp=DbWJjT=+QhUvEkQi1U2A@mail.gmail.com>
Message-ID: <CAN++4hGKVACY2PTJnUum697hum1ZHFTuLWbn0Tta-7frMNV3rA@mail.gmail.com>

On Sun, Mar 17, 2019, 22:32 Mike Hodson <mystica at gmail.com> wrote:

>
>
> Could you perhaps build the drive internally to your Myth machine if you
> maybe bought a bigger case?  External enclosures are decidedly meant for
> part-time use.
>

Ah the problem I forgot with using a Mac.... They stopped designing useful
cases a decade ago.

You need something with higher quality electronics meant for 24/7 use, like
a NAS, or some sort of proper workstations type or accept that most
external enclosures suck and never should be relied upon.

Mike

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190317/435f28ac/attachment.html>

From hmcgregor at biggeeks.org  Mon Mar 18 04:48:56 2019
From: hmcgregor at biggeeks.org (Harry McGregor)
Date: Sun, 17 Mar 2019 21:48:56 -0700
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <CAN++4hGKVACY2PTJnUum697hum1ZHFTuLWbn0Tta-7frMNV3rA@mail.gmail.com>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
 <ab7f5a29-fc12-353e-f139-ab8cc504c83d@lwfinger.net>
 <CAFWmYv2VxDShxQ183hKwSb1twwxPq+pbmKbojhtfftCMEnDhQw@mail.gmail.com>
 <2F8DAFE4-B18B-41D1-9027-3D8FA5786DA6@cogeco.ca>
 <CAN++4hHUQTAp3bDrVEnPYmBYxjMVp=DbWJjT=+QhUvEkQi1U2A@mail.gmail.com>
 <CAN++4hGKVACY2PTJnUum697hum1ZHFTuLWbn0Tta-7frMNV3rA@mail.gmail.com>
Message-ID: <f1cba570-30b6-9e7a-dac5-bd502f126283@biggeeks.org>


On 3/17/19 9:37 PM, Mike Hodson wrote:
>
>
> On Sun, Mar 17, 2019, 22:32 Mike Hodson <mystica at gmail.com 
> <mailto:mystica at gmail.com>> wrote:
>
>
>
>     Could you perhaps build the drive internally to your Myth machine
>     if you maybe bought a bigger case?? External enclosures are
>     decidedly meant for part-time use.
>
>
> Ah the problem I forgot with using a Mac.... They stopped designing 
> useful cases a decade ago.
>
> You need something with higher quality electronics meant for 24/7 use, 
> like a NAS, or some sort of proper workstations type or accept that 
> most external enclosures suck and never should be relied upon.

At a minimum, setup a small room fan blowing at/across the external drives.

The cases tend to overheat easily, which will cause problems.

Also there is a good chance the data is still on the drive.? Most 
external drives use a firmware offset that makes the data difficult to 
reach outside of the drives enclosure.? Finding an identical enclosure 
and swapping the drive should get the data accessible.

-Harry

> Mike
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190317/40b2b3b1/attachment.html>

From stephenbcollier at gmail.com  Mon Mar 18 06:07:56 2019
From: stephenbcollier at gmail.com (Stephen Collier)
Date: Mon, 18 Mar 2019 17:07:56 +1100
Subject: [mythtv-users] MythTV V30 for CentOS (EL7)
In-Reply-To: <CAPCvy=myRdU1naj5vm+=tszT39X0dOreLKecnb+FdhMUN96vEw@mail.gmail.com>
References: <CAPCvy=myRdU1naj5vm+=tszT39X0dOreLKecnb+FdhMUN96vEw@mail.gmail.com>
Message-ID: <8f4e87ee-7c88-c582-4ddc-7f8647577f04@gmail.com>

On 16/03/2019 2:12 pm, Larry Kennedy wrote:
> Is anyone building v30 RPMs for EL7?? I've been using scrpms and it
> appears to only go as far as V29.
>
> Larry
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

I've put them in el7myth due to some incompatibility with libva? which
will be fixed soon
http://scrpms.net/pub/RPMS/el7myth/x86_64/


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190318/98c8f690/attachment.html>

From craig at zpratts.net  Mon Mar 18 06:53:50 2019
From: craig at zpratts.net (Craig Pratt)
Date: Sun, 17 Mar 2019 23:53:50 -0700
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
Message-ID: <807f5063-1261-8c65-d5e8-db929205d6af@zpratts.net>

Every drive failure I've had has been heat-related. And a constant-use 
drive can generate lots of heat. I went through 3 disks in my Myth box 
until I figured out that the cabinet I had the PC in wasn't ventilating 
enough (and hddtemp was showing the drive was hot - over 40C). They all 
failed in ways similar to what you're describing. It required a lot of 
labor to get the recordings off the disks when they started to fail - as 
they would work for a while and then die.

Since replacing the glass door with a mesh cloth door, I've had one 2TB 
drive in there for 6 years now without issue - running 30-35C. It was 
the same make and manufacture as the 2 that died before it. Temperature 
was clearly the cause.

And I can't even tell you how many external drives I've seen fail (some 
of my own, others of friend's). Not sure if it's the heat/poor 
ventilation, bad power supplies, or what. But they're the worst.

I'd recommend finding some kind of enclosure that has good ventilation. 
I don't think most as designed to support drives with near-constant use. 
I can't speak to use of a NAS since I haven't used one first-hand. But 
as others have mentioned, RAID-0 would be a good way to go if you can 
afford the disks...

cp

On 3/17/19 10:21 AM, Craig Treleaven wrote:
> So, yet again, the drive with all my recordings is unreadable.  This has happened to me in September 2015, August 2013 and at least one time before that although I?m not sure of the date.  And again this past Tuesday night.  I know the dates because in 2013 I started labelling drives and enclosures with the date purchased and I purchased these items specifically because of these problems.
>
> I?m running Myth on Mac so virtually none of you care.  However, if there is someone out there on OS X that has experienced this and actually KNOWS a solution, I?d love to hear it.  I?ve tried a number of things over the last several days with success.  Various versions of Apple?s Disk Utility.  Swapping the drive into a couple of known-good enclosures.  Tried TestDisk.   The closest I got was that Disk Utility would mount the volume even though it reported it as damaged.  But CarbonCopyCloner was never able to copy more than 150MB off it.
>
> Craig
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org



From mkbloke at gmail.com  Mon Mar 18 07:04:19 2019
From: mkbloke at gmail.com (Ian Cameron)
Date: Mon, 18 Mar 2019 07:04:19 +0000
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
Message-ID: <CAC+xXWOi_L+Z0HuMdeu3KAGMfzUccch+PnpcvQ5u-zbhsuOPRA@mail.gmail.com>

On Sun, 17 Mar 2019 at 17:23, Craig Treleaven <ctreleaven at cogeco.ca> wrote:

> So, yet again, the drive with all my recordings is unreadable.  This has
> happened to me in September 2015, August 2013 and at least one time before
> that although I?m not sure of the date.  And again this past Tuesday
> night.  I know the dates because in 2013 I started labelling drives and
> enclosures with the date purchased and I purchased these items specifically
> because of these problems.
>

I can't find it now, but not so long ago, somebody posted a link to a
manufacturer's paper that said their consumer level hard drives are not
specified to be used more than one per case/enclosure and that they are not
specified for 24/7 use.

The advice was that you should be looking to purchase professional level
hard drives to get the best possible life for 24/7 operation in enclosures
with multiple hard drives.

Cheers, Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190318/230d74ba/attachment.html>

From stephen_agent at jsw.gen.nz  Mon Mar 18 08:18:59 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Mon, 18 Mar 2019 21:18:59 +1300
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <2F8DAFE4-B18B-41D1-9027-3D8FA5786DA6@cogeco.ca>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
 <ab7f5a29-fc12-353e-f139-ab8cc504c83d@lwfinger.net>
 <CAFWmYv2VxDShxQ183hKwSb1twwxPq+pbmKbojhtfftCMEnDhQw@mail.gmail.com>
 <2F8DAFE4-B18B-41D1-9027-3D8FA5786DA6@cogeco.ca>
Message-ID: <km3u8e9vhdp2llb3j5bku44jjcono0sf9d@4ax.com>

On Sun, 17 Mar 2019 22:42:18 -0400, you wrote:

>> On Mar 17, 2019, at 3:03 PM, Matt Dorsch <mtusers at dorscm.wakeful.net> wrote:
>> 
>> If you made a list of the possible causes of the failures, MythTV shouldn't be on the list. It has no control over the correctness of the filesystem. That would be the OS's job.
>> 
>> If the drive passes a read-only test, which only checks if each sector can be read successfully not the contents of the sector, then either the OS had an issue that corrupted the FS, or there was a problem with the data channel. Both of those a pretty unlikely these days, except old hardware might cause a data issue.
>> 
>> If the drive fails a read-only test, the damage goes beyond the filesystem, either to the circuit board of the drive or the platters themselves. This is usually caused by low quality components, old age, or bad power. If your system is on a UPS with AVR, it's probably not bad power.
>> 
>
>I?ve had multiple failures of the volume that Myth stores recordings on.  I?ve had no other failures.  I know that?s not a statistical sample but Myth has something to  do with it.
>
>The failures have been with different sizes of drives and from different vendors.  Note that after the failure, the drive enclosure is usually no longer usable (one exception).  Ie if I put a known-good drive in the enclosure, it is not readable.  As I said earlier, the damaged drive is also unreadable in a known-good enclosure.  The failed enclosures are from different vendors and include Firewire 400, USB 2 and USB 3 methods of connection.
>
>I don?t record a lot.  I have 4 OTA tuners (HDHomeruns) receiving North American broadcast HDTV.  It is very rare to have all tuners recording at the same time.  I do flag for commercials during recording so that may up the load.  I don?t believe I?ve ever been watching a recording during a failure.  The backend does not run any other applications.
>
>After the first failure, I equipped the backend with an Uninterruptible Power Supply.  The UPS was in place during the next 2 failures.  The UPS died a few months ago and I haven?t replaced it.  There were no indications of a power problem during the most recent failure.  My clock in my microwave is the most sensitive indicator of a power problem in our house and I haven?t had to reset it in a long time.
>
>Craig

Do you have smartmontools installed and monitoring your drives?  You
should, and you should have it set up to alert you when there are any
problems or drives get too hot.

There is a Linux command line program HDSentinel that is also useful
for reading the status of drives, although it does not have any
options to do automatic alarms like smartmontools.  It is capable of
reading some USB drive mounts that smartmontools does not know how to
access.  It is available here:

https://www.hdsentinel.com/hard_disk_sentinel_linux.php

But whether it will run on a Mac is another thing.

What sort of drives are you buying?  MythTV is something that is often
24x7, but the typical cheap desktop drives available these days are
not rated to be operating 24x7 and will die early if you do that to
them.  For 24x7 operation, you need to have NAS drives or better,
which are rated to be able to do that.  Older desktop drives were
built better and were OK, but the modern ones are built to a price and
are quite bad.  Just having modern desktop drives sitting there
powered up and rotating is enough to get them to wear out early - they
are meant for Windows boxes that are on for no more than a normal
working day of 8-9 hours, and off for the rest.

The other main problem with enclosures for drives is that often they
are not well ventilated and push up the operating temperature of your
drives.  I have one enclosure where the drive runs far too hot, but I
only use it for backups a few hours a month, so it works OK despite
that.  But when I use it, I have it over one of the exit fans on top
of my PC case, otherwise I get over temperature alarms.  So for
something that is 24x7, you need a well ventilated enclosure - it
probably should have a fan.  It is better to actually take the drive
out of the enclosure (or just buy bare drives) and run it on its side
in the open, using power and SATA cables dragged out a slot in the
back of your PC.  I have three drives operated that way, and they run
much cooler than the ones inside the case.  There are three photos
here:

http://www.jsw.gen.nz/mythtv/externaldrives

I do not know if it is possible to use a drive that way with a Mac,
but I do recommend trying it if possible instead of using enclosures.

Here are the temperature reports from smartmontools for my three
internal recording drives:

root at mypvr:~/temp/temp# smartctl -A /dev/disk/by-label/rec1 | grep -i
temp
190 Airflow_Temperature_Cel 0x0022   051   041   045    Old_age Always
In_the_past 49 (Min/Max 39/52 #966)
194 Temperature_Celsius     0x0022   049   059   000    Old_age Always
-       49 (0 17 0 0 0)
root at mypvr:~/temp/temp# smartctl -A /dev/disk/by-label/rec2 | grep -i
temp
190 Airflow_Temperature_Cel 0x0022   053   049   040    Old_age Always
-       47 (Min/Max 37/50)
194 Temperature_Celsius     0x0022   047   051   000    Old_age Always
-       47 (0 23 0 0 0)
root at mypvr:~/temp/temp# smartctl -A /dev/disk/by-label/rec3 | grep -i
temp
194 Temperature_Celsius     0x0002   117   117   000    Old_age Always
-       51 (Min/Max 21/61)

The rec2 drive is a brand new helium filled drive enterprise class
drive, hence the slightly lower temperature.  Today is one of the
hottest days this year where I live, and the rec3 drive is just over
its limit for reporting over temperature, but that drive is actually
OK to 60 degrees Celsius.  Some drives have a max temperature rating
of only 50 degrees C, and I prefer to keep all drives under 50.

Here are the same reports for my three external recording drives at
the back of the MythTV box:

root at mypvr:~/temp/temp# smartctl -A /dev/disk/by-label/rec4 | grep -i
temp
194 Temperature_Celsius     0x0022   108   101   000    Old_age Always
-       44
root at mypvr:~/temp/temp# smartctl -A /dev/disk/by-label/rec5 | grep -i
temp
194 Temperature_Celsius     0x0022   108   096   000    Old_age Always
-       42
root at mypvr:~/temp/temp# smartctl -A /dev/disk/by-label/rec6 | grep -i
temp
194 Temperature_Celsius     0x0022   109   100   000    Old_age Always
-       43

They are significantly cooler, despite not having a fan at all.

I am also running one of my recording drives in an external USB 3
drive mount - that also works better than an enclosure as it can keep
cool.  I have added a picture of that to the above URL.  Its drive
mount is one that smartmontools can not read, so here is its
temperature data from HDSentinel:

Temperature  : 41 ?C
Highest Temp.: 49 ?C

It is running even cooler than the three drives at the back of the PC
as it is up above the PC well away from the warm air it puts out from
its fans.  It used to be in another four drive enclosure I have, but
that enclosure has a fan, so its lifetime maximum temperature is 49
?C.  It would be higher if it had been inside a PC for any length of
time.

From jan.ceuleers at gmail.com  Mon Mar 18 14:47:10 2019
From: jan.ceuleers at gmail.com (Jan Ceuleers)
Date: Mon, 18 Mar 2019 15:47:10 +0100
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <2F8DAFE4-B18B-41D1-9027-3D8FA5786DA6@cogeco.ca>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
 <ab7f5a29-fc12-353e-f139-ab8cc504c83d@lwfinger.net>
 <CAFWmYv2VxDShxQ183hKwSb1twwxPq+pbmKbojhtfftCMEnDhQw@mail.gmail.com>
 <2F8DAFE4-B18B-41D1-9027-3D8FA5786DA6@cogeco.ca>
Message-ID: <7268b925-b95f-f104-5972-762a688ca72e@gmail.com>

On 18/03/2019 03:42, Craig Treleaven wrote:
> I?ve had multiple failures of the volume that Myth stores recordings on.
> ?I?ve had no other failures. ?I know that?s not a statistical sample but
> Myth has something to ?do with it.

Others have commented that MythTV cannot be the cause of filesystem
corruption and they were right. For an application to be able to corrupt
a filesystem it would need to write to the raw device (i.e. straight to
the disk or to the partition), which it would only be able to do if it
had root privileges.

You might be observing a correlation between MythTV and fs corruption,
but correlation is not causation. The correlation might come from the
fact that MythTV is a heavy user of disk space, meaning that if a disk
is iffy it is more likely than other applications (which use less disk
space) to notice.

> The failures have been with different sizes of drives and from different
> vendors. ?Note that after the failure, the drive enclosure is usually no
> longer usable (one exception). ?Ie if I put a known-good drive in the
> enclosure, it is not readable. ?As I said earlier, the damaged drive is
> also unreadable in a known-good enclosure. ?The failed enclosures are
> from different vendors and include Firewire 400, USB 2 and USB 3 methods
> of connection.

OK, so we're talking about external drives. Don't use external drives if
you value reliability. They're just not made for 24x7 operation and they
introduce 2 additional failure modes, namely the external cabling (which
in the case of internal drives is of course also needed but less likely
to be touched/wiggled, or, seeing as they are inside the enclosure,
subject to interference), and the need for another power supply.

A 2.5" drive will fit inside most enclosures, and it will be more
reliable than an external drive.

In other words my money is on a hardware issue. Either the power supply
of your external drive, or an issue involving cabling (including a
physical issue or possibly EM interference).

HTH, Jan

From jan.ceuleers at gmail.com  Mon Mar 18 14:56:22 2019
From: jan.ceuleers at gmail.com (Jan Ceuleers)
Date: Mon, 18 Mar 2019 15:56:22 +0100
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <807f5063-1261-8c65-d5e8-db929205d6af@zpratts.net>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
 <807f5063-1261-8c65-d5e8-db929205d6af@zpratts.net>
Message-ID: <4ba596a9-afda-a23b-606a-39cf44a59921@gmail.com>

On 18/03/2019 07:53, Craig Pratt wrote:
> Every drive failure I've had has been heat-related. And a constant-use
> drive can generate lots of heat. I went through 3 disks in my Myth box
> until I figured out that the cabinet I had the PC in wasn't ventilating
> enough (and hddtemp was showing the drive was hot - over 40C). They all
> failed in ways similar to what you're describing. It required a lot of
> labor to get the recordings off the disks when they started to fail - as
> they would work for a while and then die.

During the course of last year I bit the bullet and went to all-flash.
Very expensive but much quieter (of course), less power-hungry and much
less heat.

# df
Filesystem      1K-blocks       Used  Available Use% Mounted on
udev             16273212          0   16273212   0% /dev
tmpfs             3260772      18284    3242488   1% /run
/dev/nvme0n1p1   95989516   33523784   57566612  37% /
tmpfs            16303844        200   16303644   1% /dev/shm
tmpfs                5120          8       5112   1% /run/lock
tmpfs            16303844          0   16303844   0% /sys/fs/cgroup
/dev/sda       3845587976 3441859884  208360364  95% /mnt/disk5
/dev/sdd       3845587976 3455781388  194438860  95% /mnt/disk4
/dev/sdg       1922729864   86856928 1738180824   5% /mnt/disk8
/dev/md0       1821807984  225445836 1503796644  14% /home
/dev/sdf       1922729864   94682744 1730355008   6% /mnt/disk7
tmpfs             3260772         36    3260736   1% /run/user/108
tmpfs             3260772          0    3260772   0% /run/user/0

I then got rid of all of the old hard disks I had been accumulating over
the years. Took several days to secure-erase them all before disposal.

From linux at thehobsons.co.uk  Mon Mar 18 15:51:30 2019
From: linux at thehobsons.co.uk (Simon Hobson)
Date: Mon, 18 Mar 2019 15:51:30 +0000
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <7268b925-b95f-f104-5972-762a688ca72e@gmail.com>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
 <ab7f5a29-fc12-353e-f139-ab8cc504c83d@lwfinger.net>
 <CAFWmYv2VxDShxQ183hKwSb1twwxPq+pbmKbojhtfftCMEnDhQw@mail.gmail.com>
 <2F8DAFE4-B18B-41D1-9027-3D8FA5786DA6@cogeco.ca>
 <7268b925-b95f-f104-5972-762a688ca72e@gmail.com>
Message-ID: <7285B3C2-16C4-44D3-A4C2-F3842B5F9E73@thehobsons.co.uk>

Jan Ceuleers <jan.ceuleers at gmail.com> wrote:

> A 2.5" drive will fit inside most enclosures, and it will be more
> reliable than an external drive.

Unfortunately, as has already been mentioned in the thread, Apple don't really make expandable machines - even the most high end have limited expansion capability.
On the upside, except for the newest models (which have thunderbolt ports), they do have Firewire which I've found to be very reliable - although Firewire capable enclosures can be quite pricey (even used !). I've managed to build up a sufficient collection of external drive cases/docks for my needs - the LaCie Quadro ones are good and have a metal case for heat dissipation. I also note that the LaCie ones are designed to have a small (40mm ?) fan but they aren't fitted in any of mine.

Many years ago (back in the days of real SCSI) I wanted to add a few drives (including a small tape drive) to a Mac and found the price of enclosures "a bit daunting". Instead I bought a cheap generic PC case and used that.


From jan.ceuleers at gmail.com  Mon Mar 18 16:48:25 2019
From: jan.ceuleers at gmail.com (Jan Ceuleers)
Date: Mon, 18 Mar 2019 17:48:25 +0100
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <7285B3C2-16C4-44D3-A4C2-F3842B5F9E73@thehobsons.co.uk>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
 <ab7f5a29-fc12-353e-f139-ab8cc504c83d@lwfinger.net>
 <CAFWmYv2VxDShxQ183hKwSb1twwxPq+pbmKbojhtfftCMEnDhQw@mail.gmail.com>
 <2F8DAFE4-B18B-41D1-9027-3D8FA5786DA6@cogeco.ca>
 <7268b925-b95f-f104-5972-762a688ca72e@gmail.com>
 <7285B3C2-16C4-44D3-A4C2-F3842B5F9E73@thehobsons.co.uk>
Message-ID: <c6336828-3cd2-41d8-d6b1-cd7f8b16d2d3@gmail.com>

On 18/03/2019 16:51, Simon Hobson wrote:
> Jan Ceuleers <jan.ceuleers at gmail.com> wrote:
> 
>> A 2.5" drive will fit inside most enclosures, and it will be more
>> reliable than an external drive.
> 
> Unfortunately, as has already been mentioned in the thread, Apple don't really make expandable machines - even the most high end have limited expansion capability.

That's not unfortunate - it is a blessing. The obvious way forward is
not to pay the Cupertino tax and buy affordable and expandable hardware.

From bishoptf at gmail.com  Mon Mar 18 16:55:06 2019
From: bishoptf at gmail.com (Tom Bishop)
Date: Mon, 18 Mar 2019 11:55:06 -0500
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <c6336828-3cd2-41d8-d6b1-cd7f8b16d2d3@gmail.com>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
 <ab7f5a29-fc12-353e-f139-ab8cc504c83d@lwfinger.net>
 <CAFWmYv2VxDShxQ183hKwSb1twwxPq+pbmKbojhtfftCMEnDhQw@mail.gmail.com>
 <2F8DAFE4-B18B-41D1-9027-3D8FA5786DA6@cogeco.ca>
 <7268b925-b95f-f104-5972-762a688ca72e@gmail.com>
 <7285B3C2-16C4-44D3-A4C2-F3842B5F9E73@thehobsons.co.uk>
 <c6336828-3cd2-41d8-d6b1-cd7f8b16d2d3@gmail.com>
Message-ID: <CACQ6_EjtVGwcxkJpOEjLXiQLrKjh7HtDpapi7OkdTE8XW0cBJw@mail.gmail.com>

On Mon, Mar 18, 2019, 11:48 AM Jan Ceuleers <jan.ceuleers at gmail.com> wrote:

> On 18/03/2019 16:51, Simon Hobson wrote:
> > Jan Ceuleers <jan.ceuleers at gmail.com> wrote:
> >
> >> A 2.5" drive will fit inside most enclosures, and it will be more
> >> reliable than an external drive.
> >
> > Unfortunately, as has already been mentioned in the thread, Apple don't
> really make expandable machines - even the most high end have limited
> expansion capability.
>
> That's not unfortunate - it is a blessing. The obvious way forward is
> not to pay the Cupertino tax and buy affordable and expandable hardware.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org


Eh folks can use what they choose but I would put the drives in a cheap NAS
enclosure, that usually has a fan and should be better from a longevity
perspective, then mount it via NFS etc, wouldn't have great performance but
should be adequate for myth....

My .02 but if it's not working time to try a different approach. :)

>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190318/e4552c60/attachment.html>

From d-ulrick at comcast.net  Mon Mar 18 17:35:51 2019
From: d-ulrick at comcast.net (Dave Ulrick)
Date: Mon, 18 Mar 2019 12:35:51 -0500 (CDT)
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <CACQ6_EjtVGwcxkJpOEjLXiQLrKjh7HtDpapi7OkdTE8XW0cBJw@mail.gmail.com>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
 <ab7f5a29-fc12-353e-f139-ab8cc504c83d@lwfinger.net>
 <CAFWmYv2VxDShxQ183hKwSb1twwxPq+pbmKbojhtfftCMEnDhQw@mail.gmail.com>
 <2F8DAFE4-B18B-41D1-9027-3D8FA5786DA6@cogeco.ca>
 <7268b925-b95f-f104-5972-762a688ca72e@gmail.com>
 <7285B3C2-16C4-44D3-A4C2-F3842B5F9E73@thehobsons.co.uk>
 <c6336828-3cd2-41d8-d6b1-cd7f8b16d2d3@gmail.com>
 <CACQ6_EjtVGwcxkJpOEjLXiQLrKjh7HtDpapi7OkdTE8XW0cBJw@mail.gmail.com>
Message-ID: <alpine.LFD.2.21.1903181217160.6579@lion.cso.niu.edu>

On Mon, 18 Mar 2019, Tom Bishop wrote:

> On Mon, Mar 18, 2019, 11:48 AM Jan Ceuleers <jan.ceuleers at gmail.com> wrote:
>
>> On 18/03/2019 16:51, Simon Hobson wrote:
>>> Jan Ceuleers <jan.ceuleers at gmail.com> wrote:
>>>
>>>> A 2.5" drive will fit inside most enclosures, and it will be more
>>>> reliable than an external drive.
>>>
>>> Unfortunately, as has already been mentioned in the thread, Apple don't
>> really make expandable machines - even the most high end have limited
>> expansion capability.
>>
>> That's not unfortunate - it is a blessing. The obvious way forward is
>> not to pay the Cupertino tax and buy affordable and expandable hardware.
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>
>
> Eh folks can use what they choose but I would put the drives in a cheap NAS
> enclosure, that usually has a fan and should be better from a longevity
> perspective, then mount it via NFS etc, wouldn't have great performance but
> should be adequate for myth....
>
> My .02 but if it's not working time to try a different approach. :)

My experience with hard drives:

I run well-ventilated mid-tower Linux-based PCs with plenty of space for 
extra internal hard drives. Internal hard drives tend to work year after 
year. My MythTV recordings drive is internal to such a PC and has been 
glitch-free for the 3+ years it's been installed.

Regarding external USB drive enclosures, I've done OK with single-drive 
enclosures. What has _not_ worked well for me has been dual-drive 
enclosures. I've tried several dual-drive enclosures (with an exhaust fan) 
with two matching hard drives set up as a RAID 1 array. More than once, 
I've had one of the two drives fail within a week or two of the 
enclosure's initial installation. Up to now, I've attributed this to 
faulty enclosures.

So, I've stuck with single-drive enclosures until my recent acquisition of 
a LAN-attached dual-bay Synology NAS. What made me decide to try a 
dual-drive enclosure again was my discovery that some models of hard 
drives, especially the cheaper drives that are sold for home use, are 
prone to premature failure when installed in a high vibration location 
such as the dual-drive USB hard drive enclosures I'd tried before. So, 
this time around I spent some extra money for a pair of hard drives that 
are marketed specifically for use in NAS enclosures. These drives are made 
with anti-vibration technology that's supposed to help them run reliably 
in a high-vibration environment such as a multi-drive enclosure. I've been 
running this NAS for nearly 3 weeks without any hard drive issues so it's 
already outlived at least two of my older USB dual-drive enclosures. 
Hopefully the anti-vibration technology of the hard drives plus the 
Synology enclosure's exhaust fan will help these hard drives to last at 
least a few years.

Dave
-- 
Dave Ulrick
d-ulrick at comcast.net

From bkamen at benjammin.net  Mon Mar 18 17:59:59 2019
From: bkamen at benjammin.net (Ben)
Date: Mon, 18 Mar 2019 12:59:59 -0500
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <alpine.LFD.2.21.1903181217160.6579@lion.cso.niu.edu>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
 <ab7f5a29-fc12-353e-f139-ab8cc504c83d@lwfinger.net>
 <CAFWmYv2VxDShxQ183hKwSb1twwxPq+pbmKbojhtfftCMEnDhQw@mail.gmail.com>
 <2F8DAFE4-B18B-41D1-9027-3D8FA5786DA6@cogeco.ca>
 <7268b925-b95f-f104-5972-762a688ca72e@gmail.com>
 <7285B3C2-16C4-44D3-A4C2-F3842B5F9E73@thehobsons.co.uk>
 <c6336828-3cd2-41d8-d6b1-cd7f8b16d2d3@gmail.com>
 <CACQ6_EjtVGwcxkJpOEjLXiQLrKjh7HtDpapi7OkdTE8XW0cBJw@mail.gmail.com>
 <alpine.LFD.2.21.1903181217160.6579@lion.cso.niu.edu>
Message-ID: <5d11c1bd-dce6-9c97-a3cc-8dc21dc4da98@benjammin.net>

I can echo the same sentiment.

I keep my drives cool to warm -- and I've known installs with low flow that have roasted drives to failure.

A great example was this HP mini-tower that held 4 drives in a very RAID-oriented design. Only 1 fan at the back of the chassis.

The drives got baked and failed within a year.

I took a look at the system for the person and taped over all the ventilation holes on the system to better direct the air-flow over the drives.

The drives operating temps went from 52-55'C down to the low-to-30'C range.

So far that system has been happy as can be.

For my own Linux server system that runs Myth, I have PWM controlled fans through a crystalfontz LCD display that also lets' me control the fan speeds through software in which I can scan in drive temps.

So I strive to keep my drive temps under 35'C. The system slows it's fans down in winter to avoid over cooling. (The whole box is really quiet in the winter. It's kinda funny)

Avoid thermal shocks. Keep the drives under 40'C... They've lasted me for 5+yrs running 24/7/365.

Consider running Munin as well and link in the drive temps there to monitor them...

 ?-Ben


From mystica at gmail.com  Mon Mar 18 18:12:02 2019
From: mystica at gmail.com (Mike Hodson)
Date: Mon, 18 Mar 2019 12:12:02 -0600
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <5d11c1bd-dce6-9c97-a3cc-8dc21dc4da98@benjammin.net>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
 <ab7f5a29-fc12-353e-f139-ab8cc504c83d@lwfinger.net>
 <CAFWmYv2VxDShxQ183hKwSb1twwxPq+pbmKbojhtfftCMEnDhQw@mail.gmail.com>
 <2F8DAFE4-B18B-41D1-9027-3D8FA5786DA6@cogeco.ca>
 <7268b925-b95f-f104-5972-762a688ca72e@gmail.com>
 <7285B3C2-16C4-44D3-A4C2-F3842B5F9E73@thehobsons.co.uk>
 <c6336828-3cd2-41d8-d6b1-cd7f8b16d2d3@gmail.com>
 <CACQ6_EjtVGwcxkJpOEjLXiQLrKjh7HtDpapi7OkdTE8XW0cBJw@mail.gmail.com>
 <alpine.LFD.2.21.1903181217160.6579@lion.cso.niu.edu>
 <5d11c1bd-dce6-9c97-a3cc-8dc21dc4da98@benjammin.net>
Message-ID: <CAN++4hEfM=dhnS201x1D3Vnh_h1BrUZfeOAY7p0v+0AodRrcKQ@mail.gmail.com>

On Mon, Mar 18, 2019, 12:01 Ben <bkamen at benjammin.net> wrote:

I can echo the same sentiment.
>
> I keep my drives cool to warm -- and I've known installs with low flow
> that have roasted drives to failure.
>

...


> Consider running Munin as well and link in the drive temps there to
> monitor them...
>
>   -Ben
>

I also echo all the sentiments of keeping your drives cool and monitoring
the temperature with S.M.A.R.T.

Regarding an OSX native application, smartmontools itself has a command
line version that should be able to provide it what something like munin as
a continually running logging service would need.

I also did find an application that is native OS X GUI
https://www.corecode.io/smartreporter/ which I believe is a wrapper around
the command line smartmontools.

I hope that all of these great replies from everyone will help to get your
next MythTV Drive continually working for a very long future!

Mike

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190318/e1edbc5f/attachment.html>

From bkamen at benjammin.net  Mon Mar 18 18:30:57 2019
From: bkamen at benjammin.net (Ben)
Date: Mon, 18 Mar 2019 13:30:57 -0500
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <CAN++4hEfM=dhnS201x1D3Vnh_h1BrUZfeOAY7p0v+0AodRrcKQ@mail.gmail.com>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
 <ab7f5a29-fc12-353e-f139-ab8cc504c83d@lwfinger.net>
 <CAFWmYv2VxDShxQ183hKwSb1twwxPq+pbmKbojhtfftCMEnDhQw@mail.gmail.com>
 <2F8DAFE4-B18B-41D1-9027-3D8FA5786DA6@cogeco.ca>
 <7268b925-b95f-f104-5972-762a688ca72e@gmail.com>
 <7285B3C2-16C4-44D3-A4C2-F3842B5F9E73@thehobsons.co.uk>
 <c6336828-3cd2-41d8-d6b1-cd7f8b16d2d3@gmail.com>
 <CACQ6_EjtVGwcxkJpOEjLXiQLrKjh7HtDpapi7OkdTE8XW0cBJw@mail.gmail.com>
 <alpine.LFD.2.21.1903181217160.6579@lion.cso.niu.edu>
 <5d11c1bd-dce6-9c97-a3cc-8dc21dc4da98@benjammin.net>
 <CAN++4hEfM=dhnS201x1D3Vnh_h1BrUZfeOAY7p0v+0AodRrcKQ@mail.gmail.com>
Message-ID: <48808ef2-dd11-87f6-b516-d6859ccc7b4f@benjammin.net>

Another important think about smartmontools is it can notify you on important things like when the drives have a change in any of the error/diag counters.

When running RAIDs -- this can prove critical to know a particular drive in the array is unhappy and to take action.

personally, I have another CPU power to run mdadm (software RAID) which has worked great over the almost 11yrs this particular server has been running.

I've completely changed out/upgraded my RAID array drives in it at least once not including the random drives that fail for whatever reason.

for those random drives, every time one start to feel ill, smartmontools let me know well in advance.

 ? -Ben

From linux at thehobsons.co.uk  Mon Mar 18 19:00:52 2019
From: linux at thehobsons.co.uk (Simon Hobson)
Date: Mon, 18 Mar 2019 19:00:52 +0000
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <c6336828-3cd2-41d8-d6b1-cd7f8b16d2d3@gmail.com>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
 <ab7f5a29-fc12-353e-f139-ab8cc504c83d@lwfinger.net>
 <CAFWmYv2VxDShxQ183hKwSb1twwxPq+pbmKbojhtfftCMEnDhQw@mail.gmail.com>
 <2F8DAFE4-B18B-41D1-9027-3D8FA5786DA6@cogeco.ca>
 <7268b925-b95f-f104-5972-762a688ca72e@gmail.com>
 <7285B3C2-16C4-44D3-A4C2-F3842B5F9E73@thehobsons.co.uk>
 <c6336828-3cd2-41d8-d6b1-cd7f8b16d2d3@gmail.com>
Message-ID: <1137C111-C72F-46D2-8C1E-378288B9E527@thehobsons.co.uk>

Jan Ceuleers <jan.ceuleers at gmail.com> wrote:
> 

> That's not unfortunate - it is a blessing. The obvious way forward is not to pay the Cupertino tax and buy affordable and expandable hardware.

Apple kit isn't always as expensive as it looks at first sight. It's a regular criticism, but a few times I've looked at alternative hardware **with similar specs** and found them comparable. That's more the case with laptops than desktops, and they've not done servers for a looooong time - I used to run two of the G4 servers.

But yes, for something like this, just run GNU/Linux on generic x86 hardware - unless for some reason you have some apple hardware lying around, and even then I;d consider running Linux on it for a Myth backend.



Tom Bishop <bishoptf at gmail.com> wrote:

> Eh folks can use what they choose but I would put the drives in a cheap NAS enclosure, that usually has a fan and should be better from a longevity perspective, then mount it via NFS etc, wouldn't have great performance but should be adequate for myth....

Agreed, but I'd prefer to direct connect it - but not all RAID/NAS type boxes support that. NAS & NFS is adding quite a lot of layers between Myth and the storage. There's a lot of RAID enclosures that have much the same physical arrangement as a good NAS box, but the ones (with Firewire) that seem to come up on eBay seem to only do RAID and not JBOD :-(
Firewire should always support multiple drive as JBOD, but for SATA it needs specific support in the host for a port multiplier.

From ylee at columbia.edu  Mon Mar 18 19:28:04 2019
From: ylee at columbia.edu (Yeechang Lee)
Date: Mon, 18 Mar 2019 12:28:04 -0700
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
Message-ID: <23695.61764.856721.860001@dobie.ylee.org>

Craig Treleaven <ctreleaven at cogeco.ca> says:
> Various versions of Apple?s Disk Utility.

Disk Utility is a frontend for fsck, but it may be preferable to run
fsck directly. Try

`fsck_hfs -c 2200m -fyprd /dev/diskxsy`

Repeat until a) fsck_hfs does *not* say "File system was modified",[1]
or b) the problems fsck_hfs finds and fixes/does not fix do not
change. In other words, if fsck_hfs gives up after the first try, try
again.

(This is assuming that the filesystem is the problem and not the
physical disk, of course.)

As Jan and others said, MythTV isn't the cause of the failure, and
external enclosures aren't a good idea. Cheap ones can't pass along
SMART diagnostics. My setup is below; the N40L can't run MacOS, but
I've used a Mac client to a Linux server for 15 years, before and
including MythTV. If you insist on MacOS on the server, you are better
off with either a Mac Pro with room for internal drives, or an
inexpensive NAS; either prebuilt like Synology
(<https://thewirecutter.com/reviews/best-network-attached-storage/>),
or something like FreeNAS. (Microservers are inexpensive on
Craigslist.)

[1] Yes, this includes those times when you run `fsck -fy` in Mac
single-user mode after an unclean shotdown

-- 
Frontend:		Apple MacBook Pro 2012 2.6GHz with 1TB SSD
Backend:		HP Microserver N40L 1.5GHz with 4x3TB HDDs
Tuners:			Three from CableCARD plus two over-the-air

From justin at jalcorn.net  Mon Mar 18 20:55:22 2019
From: justin at jalcorn.net (Justin Alcorn)
Date: Mon, 18 Mar 2019 16:55:22 -0400
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
Message-ID: <CAHyJEifLR5cYPUyMYD0hMdGMb6uV+Ek1LHxzOgORo8EYx7VLZQ@mail.gmail.com>

If the drive is at all recoverable, spinrite should be able to get it to
the point where you can pull your data off it.

Yup, venerable old spinrite from Gibson Research Corporation. grc.com  I
keep an old computer sitting on my workbench just to spinrite drives.
It'll take many many hours or days to do it on level 2 - but if it's
recoverable, spinrite will get it readable.

If spinrite can see it but can't recover it....nothing can.
-- 
Justin B. Alcorn
The views expressed are not necessarily my own, much less anyone else's
PGP Fingerprint CCEB F776 C3FD 1050 C8DB  532E B8B9 BED7 7764 406C


On Sun, Mar 17, 2019 at 1:21 PM Craig Treleaven <ctreleaven at cogeco.ca>
wrote:

> So, yet again, the drive with all my recordings is unreadable.  This has
> happened to me in September 2015, August 2013 and at least one time before
> that although I?m not sure of the date.  And again this past Tuesday
> night.  I know the dates because in 2013 I started labelling drives and
> enclosures with the date purchased and I purchased these items specifically
> because of these problems.
>
> I?m running Myth on Mac so virtually none of you care.  However, if there
> is someone out there on OS X that has experienced this and actually KNOWS a
> solution, I?d love to hear it.  I?ve tried a number of things over the last
> several days with success.  Various versions of Apple?s Disk Utility.
> Swapping the drive into a couple of known-good enclosures.  Tried
> TestDisk.   The closest I got was that Disk Utility would mount the volume
> even though it reported it as damaged.  But CarbonCopyCloner was never able
> to copy more than 150MB off it.
>
> Craig
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190318/158816cf/attachment.html>

From jam at tigger.ws  Mon Mar 18 23:31:45 2019
From: jam at tigger.ws (James Linder)
Date: Tue, 19 Mar 2019 07:31:45 +0800
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <mailman.117.1552920989.1604.mythtv-users@mythtv.org>
References: <mailman.117.1552920989.1604.mythtv-users@mythtv.org>
Message-ID: <3BBD8F61-00C8-40FA-84C2-746D1DADFB85@tigger.ws>



> On 18 Mar 2019, at 10:56 pm, mythtv-users-request at mythtv.org wrote:
> 
>> If you made a list of the possible causes of the failures, MythTV shouldn't be on the list. It has no control over the correctness of the filesystem. That would be the OS's job.
>> 
>> If the drive passes a read-only test, which only checks if each sector can be read successfully not the contents of the sector, then either the OS had an issue that corrupted the FS, or there was a problem with the data channel. Both of those a pretty unlikely these days, except old hardware might cause a data issue.
>> 
>> If the drive fails a read-only test, the damage goes beyond the filesystem, either to the circuit board of the drive or the platters themselves. This is usually caused by low quality components, old age, or bad power. If your system is on a UPS with AVR, it's probably not bad power.
>> 
> 
> I?ve had multiple failures of the volume that Myth stores recordings on.  I?ve had no other failures.  I know that?s not a statistical sample but Myth has something to  do with it.

A few things apple does are very nice (many are not) but timemachine for backups is very nice.
(As is their whole bundle concept, where an application and all it's libraries are lumped together to make an ?app')

A few years ago Seagate in their ?ATA more than an interface? paper said this was where we are going. EG there is venimous rejection of their statement that if you have more than 1 disk near another then one WILL fail.

As the cost of flash drops it looks more and more attractive. You *can* get 4T samsung SSDs.

backintime is loosely based on timemachine and with USB external disks is a cheap and easy backup solutiom.

What is even more horrid is apple do not support ntfs so even that is a track-into-the-woods. Sympathies Craig, but you are somewhat knackered.

James

From jam at tigger.ws  Mon Mar 18 23:37:13 2019
From: jam at tigger.ws (James Linder)
Date: Tue, 19 Mar 2019 07:37:13 +0800
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <mailman.117.1552920989.1604.mythtv-users@mythtv.org>
References: <mailman.117.1552920989.1604.mythtv-users@mythtv.org>
Message-ID: <9A753735-0353-4EC7-84DA-E1DD4D6F43BB@tigger.ws>

I posted without the meat sorry! myth may be screwing the disks but that is an OS defect. myth is allowed to say anything it likes to the disks. My meandering comment about ntfs should have also asked what file system you are using.

> On 18 Mar 2019, at 10:56 pm, mythtv-users-request at mythtv.org wrote:
> 
>> If you made a list of the possible causes of the failures, MythTV shouldn't be on the list. It has no control over the correctness of the filesystem. That would be the OS's job.
>> 
>> If the drive passes a read-only test, which only checks if each sector can be read successfully not the contents of the sector, then either the OS had an issue that corrupted the FS, or there was a problem with the data channel. Both of those a pretty unlikely these days, except old hardware might cause a data issue.
>> 
>> If the drive fails a read-only test, the damage goes beyond the filesystem, either to the circuit board of the drive or the platters themselves. This is usually caused by low quality components, old age, or bad power. If your system is on a UPS with AVR, it's probably not bad power.
>> 
> 
> I?ve had multiple failures of the volume that Myth stores recordings on.  I?ve had no other failures.  I know that?s not a statistical sample but Myth has something to  do with it.

A few things apple does are very nice (many are not) but timemachine for backups is very nice.
(As is their whole bundle concept, where an application and all it's libraries are lumped together to make an ?app')

A few years ago Seagate in their ?ATA more than an interface? paper said this was where we are going. EG there is venimous rejection of their statement that if you have more than 1 disk near another then one WILL fail.

As the cost of flash drops it looks more and more attractive. You *can* get 4T samsung SSDs.

backintime is loosely based on timemachine and with USB external disks is a cheap and easy backup solutiom.

What is even more horrid is apple do not support ntfs so even that is a track-into-the-woods. Sympathies Craig, but you are somewhat knackered.

James

From stephen_agent at jsw.gen.nz  Tue Mar 19 02:10:27 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Tue, 19 Mar 2019 15:10:27 +1300
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <9A753735-0353-4EC7-84DA-E1DD4D6F43BB@tigger.ws>
References: <mailman.117.1552920989.1604.mythtv-users@mythtv.org>
 <9A753735-0353-4EC7-84DA-E1DD4D6F43BB@tigger.ws>
Message-ID: <gjj09edeqas8tmv9j73ns9phcuoq66o2ok@4ax.com>

On Tue, 19 Mar 2019 07:37:13 +0800, you wrote:

>As the cost of flash drops it looks more and more attractive. You *can* get 4T samsung SSDs.

Except that when you run the figures for a MythTV recording drive,
even a 4 TByte SSD will get worn out pretty rapidly.  That is for the
level of recording I do though, which is pretty heavy.  When huge SSDs
get down in price enough that you can afford to replace them every 4-5
years, then they will be the right choice for MythTV.  But we are not
there yet.

From oliver.greg at gmail.com  Tue Mar 19 05:26:56 2019
From: oliver.greg at gmail.com (Greg Oliver)
Date: Tue, 19 Mar 2019 00:26:56 -0500
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <gjj09edeqas8tmv9j73ns9phcuoq66o2ok@4ax.com>
References: <mailman.117.1552920989.1604.mythtv-users@mythtv.org>
 <9A753735-0353-4EC7-84DA-E1DD4D6F43BB@tigger.ws>
 <gjj09edeqas8tmv9j73ns9phcuoq66o2ok@4ax.com>
Message-ID: <CAF4tN+_bp-wnGVVTtqeY8rpggBJtO_5wi9_byC0ZW0kXt48Bag@mail.gmail.com>

On Mon, Mar 18, 2019 at 9:11 PM Stephen Worthington <
stephen_agent at jsw.gen.nz> wrote:

> On Tue, 19 Mar 2019 07:37:13 +0800, you wrote:
>
> >As the cost of flash drops it looks more and more attractive. You *can*
> get 4T samsung SSDs.
>
> Except that when you run the figures for a MythTV recording drive,
> even a 4 TByte SSD will get worn out pretty rapidly.  That is for the
> level of recording I do though, which is pretty heavy.  When huge SSDs
> get down in price enough that you can afford to replace them every 4-5
> years, then they will be the right choice for MythTV.  But we are not
> there yet.
>

I have been running MythTV since the early 2000s and since 2008 as the main
System in the house.  I have had (and all are still in use):

2x (5x 2TB) Raid-5 Enclosure
1x (5x 3TB) Raid-5 Enclosure
1x (5x 6TB) Raid-5 Enclosure

They are all the same brand (SansDigital) tower which has E-Sata and USB
outputs.  I have had to replace the fans and PS in 3 of 4 (the 6TB array
will start dieing soon I am sure), but I have never lost a single drive.  I
do vacuum the front screens and back fan and vents routinely (old telecom
routine maintenance habit I suppose)..

Anyhow, they are relatively cheap in relation since they come fully ready
to go - no external power or anything is required, but they are not network
connected, so an Esata connection is needed (unless you are courageous and
want to run USB3).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190319/15553f77/attachment.html>

From wdormann at gmail.com  Tue Mar 19 17:37:07 2019
From: wdormann at gmail.com (Will Dormann)
Date: Tue, 19 Mar 2019 11:37:07 -0600
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
Message-ID: <5eb17e04-07d3-b3e7-1422-9fdb52546255@gmail.com>

On 3/17/19 11:21 AM, Craig Treleaven wrote:
> So, yet again, the drive with all my recordings is unreadable.  This
> has happened to me in September 2015, August 2013 and at least one
> time before that although I?m not sure of the date.  And again this
> past Tuesday night.  I know the dates because in 2013 I started
> labelling drives and enclosures with the date purchased and I
> purchased these items specifically because of these problems.
> 
> I?m running Myth on Mac so virtually none of you care.  However, if
> there is someone out there on OS X that has experienced this and
> actually KNOWS a solution, I?d love to hear it.


If you're running any system without Smartmontools smartd monitoring and
notification, then don't be surprised when a drive dies without warning.
 This has nothing to do with macOS or MythTV.

The relevant part of my smartd.conf file is:

?
#DEVICESCAN -d removable -n standby -m root -M exec
/usr/share/smartmontools/smartd-runner
/dev/sda -a -o on -S on -s (S/../.././03|L/../../6/04) -m wdormann at gmail.com


That is, comment out the "DEVICESCAN" line and add a line that is
relevant to your system.   The second line above runs a short self-test
every day at 3AM, and a long self-test once a week at 4AM, emailing me
if there's any trouble (either due to a failed self-test, or if
something bad happens during normal operation).

Note that some drive failures are not predictable.  smartd won't help
you with those.  However, it *will* tell you when many things are not
looking good.  Such as running with a too-high temperature, or if the
reallocated sector count grows beyond 0.


-WD

From darylangela at gmail.com  Wed Mar 20 10:31:38 2019
From: darylangela at gmail.com (Daryl McDonald)
Date: Wed, 20 Mar 2019 06:31:38 -0400
Subject: [mythtv-users] No 6 O'clock News
Message-ID: <CAMwtTBDE4gogDtuFAV4kVA01h4gQgV4UoOzU3O5mOvR3SUFHSg@mail.gmail.com>

Normally my system powers up at 5:50 pm for the first recording of the
evening, the news. Last night it was still in a POST process (I believe) no
splash screen, no OS options. Somewhere in there I see "sata* DRDY" I have
no idea what causes it, but what fixes it is e2fsck on my storage disks.
Should I be adding a script to my weekly.cron file to systematically
unmount>e2fsck>mount my three recording drives?
Here is a mythbackend.log:(not quite)
the full log doesn't go to paste,Jan2nd - Jan 26th only, opening the log
from files shows to Mar 20th with a warning banner on top "corrupt
characters do not edit" or similar.
Bill's shortlog.sh isn't cooperating with me either:
 http://paste.ubuntu.com/p/tCvNSsGsZk/
only a few lines show up.
I'm open to ideas   TIA   Daryl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190320/dac1204d/attachment.html>

From support at drdos.info  Wed Mar 20 11:16:39 2019
From: support at drdos.info (Doug Lytle)
Date: Wed, 20 Mar 2019 07:16:39 -0400 (EDT)
Subject: [mythtv-users] No 6 O'clock News
In-Reply-To: <CAMwtTBDE4gogDtuFAV4kVA01h4gQgV4UoOzU3O5mOvR3SUFHSg@mail.gmail.com>
References: <CAMwtTBDE4gogDtuFAV4kVA01h4gQgV4UoOzU3O5mOvR3SUFHSg@mail.gmail.com>
Message-ID: <sig.19822e2a10.502596072.2985.1553080599320.JavaMail.zimbra@drdos.info>

In my experience, a DRDY is an indication of a failing drive.

Doug

From stephen_agent at jsw.gen.nz  Wed Mar 20 11:37:28 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Thu, 21 Mar 2019 00:37:28 +1300
Subject: [mythtv-users] No 6 O'clock News
In-Reply-To: <sig.19822e2a10.502596072.2985.1553080599320.JavaMail.zimbra@drdos.info>
References: <CAMwtTBDE4gogDtuFAV4kVA01h4gQgV4UoOzU3O5mOvR3SUFHSg@mail.gmail.com>
 <sig.19822e2a10.502596072.2985.1553080599320.JavaMail.zimbra@drdos.info>
Message-ID: <98949e1f5asntm1rrh9sm8l16vv6mv6nkg@4ax.com>

On Wed, 20 Mar 2019 07:16:39 -0400 (EDT), you wrote:

>In my experience, a DRDY is an indication of a failing drive.
>
>Doug

It can also be a bad cable, or even a bad SATA port.  Almost certainly
a hardware fault though.  So it is worth just swapping the cable for a
new one to see if that is the cause.  And it can happen where a cable
was not quite plugged on properly and has worked loose or expanded and
contracted with temperature cycles and is no longer making good
contact.

From darylangela at gmail.com  Wed Mar 20 15:18:45 2019
From: darylangela at gmail.com (Daryl McDonald)
Date: Wed, 20 Mar 2019 11:18:45 -0400
Subject: [mythtv-users] No 6 O'clock News
In-Reply-To: <98949e1f5asntm1rrh9sm8l16vv6mv6nkg@4ax.com>
References: <CAMwtTBDE4gogDtuFAV4kVA01h4gQgV4UoOzU3O5mOvR3SUFHSg@mail.gmail.com>
 <sig.19822e2a10.502596072.2985.1553080599320.JavaMail.zimbra@drdos.info>
 <98949e1f5asntm1rrh9sm8l16vv6mv6nkg@4ax.com>
Message-ID: <CAMwtTBDHrUuXHUeEa6YeufTKwVkD3_YYG3y+J3BNiUUb4OJJzg@mail.gmail.com>

On Wed, Mar 20, 2019 at 7:39 AM Stephen Worthington <
stephen_agent at jsw.gen.nz> wrote:

> On Wed, 20 Mar 2019 07:16:39 -0400 (EDT), you wrote:
>
> >In my experience, a DRDY is an indication of a failing drive.
> >
> >Doug
>
> It can also be a bad cable, or even a bad SATA port.  Almost certainly
> a hardware fault though.  So it is worth just swapping the cable for a
> new one to see if that is the cause.  And it can happen where a cable
> was not quite plugged on properly and has worked loose or expanded and
> contracted with temperature cycles and is no longer making good
> contact.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org


We went down the hardware path recently, I replaced my mobo and sata cables
and power cables, and the problem returned. running the e2fsck repairs the
corruption in the drive and away we go again. This is occurring on a new
drive that had the recordings cloned/copied onto it, and the corruption too
I assume. Is there a switch that I can add to "sudo e2fsck /dev/sd** -y" to
make it report to a text doc that I can share with the list to shed further
light? It may take a while for corruption to recur, but I'd like to find
out why and address the root cause.
My skills are at the enthusiastic amateur level, and I'm open to
suggestions.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190320/f61f2603/attachment-0001.html>

From martinc at itrans.com  Wed Mar 20 18:46:40 2019
From: martinc at itrans.com (Martin Compton)
Date: Wed, 20 Mar 2019 13:46:40 -0500
Subject: [mythtv-users] 4K Video Settings
In-Reply-To: <5eb17e04-07d3-b3e7-1422-9fdb52546255@gmail.com>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
 <5eb17e04-07d3-b3e7-1422-9fdb52546255@gmail.com>
Message-ID: <d6513ad5-3424-f92f-d9f8-aefef4c4ad40@itrans.com>

My old TV crapped out, and I have a new 4K UHD television.? I'm running 
an AMD A8 CPU/GPU which surprisingly drives the display at 4K 
resolution.? However, that also limits the de-interlacing options (i.e. 
no 2X filters).

All of my content is 1080i or lower.? Would I be better off changing the 
X / Myth resolution to 1920x1080 and letting the TV upscale, or continue 
to let the GPU do it with lessor de-interlacing?

Curious as to what others are doing.

Martin

From jayf0ster at roadrunner.com  Wed Mar 20 19:06:03 2019
From: jayf0ster at roadrunner.com (Jay Foster)
Date: Wed, 20 Mar 2019 12:06:03 -0700
Subject: [mythtv-users] 4K Video Settings
In-Reply-To: <d6513ad5-3424-f92f-d9f8-aefef4c4ad40@itrans.com>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
 <5eb17e04-07d3-b3e7-1422-9fdb52546255@gmail.com>
 <d6513ad5-3424-f92f-d9f8-aefef4c4ad40@itrans.com>
Message-ID: <9a99db2b-bf19-c8e3-d10e-8c2230e8fa26@roadrunner.com>

On 3/20/2019 11:46 AM, Martin Compton wrote:
> My old TV crapped out, and I have a new 4K UHD television.? I'm 
> running an AMD A8 CPU/GPU which surprisingly drives the display at 4K 
> resolution.? However, that also limits the de-interlacing options 
> (i.e. no 2X filters).
>
> All of my content is 1080i or lower.? Would I be better off changing 
> the X / Myth resolution to 1920x1080 and letting the TV upscale, or 
> continue to let the GPU do it with lessor de-interlacing?
>
> Curious as to what others are doing.
>
> Martin
I had the same situation happen to me about two years ago.? For me, 
however, my video card did not support the 4K resolution.? I fixed the 
video card to 1920x1080 and let MythTV scale everything to that and the 
TV to scale to the display resolution.? Works fine.
Jay

From pb.mythtv at gmail.com  Wed Mar 20 19:39:36 2019
From: pb.mythtv at gmail.com (Peter Bennett)
Date: Wed, 20 Mar 2019 15:39:36 -0400
Subject: [mythtv-users] 4K Video Settings
In-Reply-To: <d6513ad5-3424-f92f-d9f8-aefef4c4ad40@itrans.com>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
 <5eb17e04-07d3-b3e7-1422-9fdb52546255@gmail.com>
 <d6513ad5-3424-f92f-d9f8-aefef4c4ad40@itrans.com>
Message-ID: <3d8a228e-25c5-6fdf-77f4-0b92219d43d1@gmail.com>



On 3/20/19 2:46 PM, Martin Compton wrote:
> My old TV crapped out, and I have a new 4K UHD television.? I'm 
> running an AMD A8 CPU/GPU which surprisingly drives the display at 4K 
> resolution.? However, that also limits the de-interlacing options 
> (i.e. no 2X filters).
>
> All of my content is 1080i or lower.? Would I be better off changing 
> the X / Myth resolution to 1920x1080 and letting the TV upscale, or 
> continue to let the GPU do it with lessor de-interlacing?
>
> Curious as to what others are doing.
>
> Martin

To get 2x deinterlace, you need a refresh rate of 50 or 60 Hz. At 4K 
resolution this needs a HDMI 2.1 cable and an HDMI 2.1 capable port on 
your video card and TV. On my 4K display, only the first HDMI port 
supports 60 Hz, the second port runs only at 30 Hz at 4K resolution..

So you may be able to solve it with a new cable and/or switching to a 
different HDMI port on your TV.

Failing this, I would say it is better to run the TV at 1920x1080.

Peter

From jam at tigger.ws  Thu Mar 21 03:59:03 2019
From: jam at tigger.ws (James Linder)
Date: Thu, 21 Mar 2019 11:59:03 +0800
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <mailman.135.1553095143.1604.mythtv-users@mythtv.org>
References: <mailman.135.1553095143.1604.mythtv-users@mythtv.org>
Message-ID: <73E70811-FFAF-4B13-A7B3-DE0F3162E42D@tigger.ws>



> On 20 Mar 2019, at 11:19 pm, mythtv-users-request at mythtv.org wrote:
> 
>> Unfortunately, as has already been mentioned in the thread, Apple don't really make expandable machines - even the most high end have limited expansion capability.
> 
> That's not unfortunate - it is a blessing. The obvious way forward is
> not to pay the Cupertino tax and buy affordable and expandable hardware.

In order to seamlessly drain all your munnie while keeping you happy, apple make good reliable hardware. If you are clever enough to play and win you are silly to not take advantage.

James

From jam at tigger.ws  Thu Mar 21 04:27:20 2019
From: jam at tigger.ws (James Linder)
Date: Thu, 21 Mar 2019 12:27:20 +0800
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <mailman.135.1553095143.1604.mythtv-users@mythtv.org>
References: <mailman.135.1553095143.1604.mythtv-users@mythtv.org>
Message-ID: <4D668658-CB57-4746-AFC0-DE00848F080B@tigger.ws>



> On 20 Mar 2019, at 11:19 pm, mythtv-users-request at mythtv.org wrote:
> 
>> As the cost of flash drops it looks more and more attractive. You *can* get 4T samsung SSDs.
> 
> Except that when you run the figures for a MythTV recording drive,
> even a 4 TByte SSD will get worn out pretty rapidly.  That is for the
> level of recording I do though, which is pretty heavy.  When huge SSDs
> get down in price enough that you can afford to replace them every 4-5
> years, then they will be the right choice for MythTV.  But we are not
> there yet.


Actually Stephen that is not true. Shock horror amazement (me not you):

[sandypit] /home/jam [1002]% !459
sudo /usr/sbin/smartctl -A /dev/sda
[sudo] password for root:
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.12.14-lp150.12.45-default] (SUSE RPM)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       1956
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       25
177 Wear_Leveling_Count     0x0013   099   099   000    Pre-fail  Always       -       3
179 Used_Rsvd_Blk_Cnt_Tot   0x0013   100   100   010    Pre-fail  Always       -       0
181 Program_Fail_Cnt_Total  0x0032   100   100   010    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   010    Old_age   Always       -       0
183 Runtime_Bad_Block       0x0013   100   100   010    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0032   062   048   000    Old_age   Always       -       38
195 Hardware_ECC_Recovered  0x001a   200   200   000    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x003e   100   100   000    Old_age   Always       -       0
235 Unknown_Attribute       0x0012   099   099   000    Old_age   Always       -       12
241 Total_LBAs_Written      0x0032   099   099   000    Old_age   Always       -       3425086849

Recording 1/2 doz shows / day on a samsung 1T disk with a total write life of 600T

Based on 3 months usage 
that?s 1.7T yielding a lifetime of 86 years.

4T cheapest 4 bit mlc is 2x that.

James

From gregorio.gervasio at gmail.com  Thu Mar 21 04:49:28 2019
From: gregorio.gervasio at gmail.com (Gregorio Gervasio Jr.)
Date: Wed, 20 Mar 2019 21:49:28 -0700
Subject: [mythtv-users] 4K Video Settings
In-Reply-To: <3d8a228e-25c5-6fdf-77f4-0b92219d43d1@gmail.com> (Peter Bennett's
 message of "Wed, 20 Mar 2019 15:39:36 -0400")
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
 <5eb17e04-07d3-b3e7-1422-9fdb52546255@gmail.com>
 <d6513ad5-3424-f92f-d9f8-aefef4c4ad40@itrans.com>
 <3d8a228e-25c5-6fdf-77f4-0b92219d43d1@gmail.com>
Message-ID: <m3va0cde7b.fsf@xanthu.gervasio.home>

>>>>> Peter Bennett writes:
[...]
> To get 2x deinterlace, you need a refresh rate of 50 or 60 Hz. At 4K
> resolution this needs a HDMI 2.1 cable and an HDMI 2.1 capable port on
> your video card and TV. On my 4K display, only the first HDMI port
> supports 60 Hz, the second port runs only at 30 Hz at 4K resolution..
[...]

I think you meant HDMI 2.0.  The first HDMI 2.1 TVs aren't coming out
for a few more weeks (LG's new OLEDs and high-end LCDs).

-- 
Gregorio Gervasio Jr.        gregorio.gervasio at gmail.com

From stephen_agent at jsw.gen.nz  Thu Mar 21 06:39:14 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Thu, 21 Mar 2019 19:39:14 +1300
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <4D668658-CB57-4746-AFC0-DE00848F080B@tigger.ws>
References: <mailman.135.1553095143.1604.mythtv-users@mythtv.org>
 <4D668658-CB57-4746-AFC0-DE00848F080B@tigger.ws>
Message-ID: <tgb69et3uvfvub6gkakt6f42dhbcs4e6lo@4ax.com>

On Thu, 21 Mar 2019 12:27:20 +0800, you wrote:

>
>
>> On 20 Mar 2019, at 11:19 pm, mythtv-users-request at mythtv.org wrote:
>> 
>>> As the cost of flash drops it looks more and more attractive. You *can* get 4T samsung SSDs.
>> 
>> Except that when you run the figures for a MythTV recording drive,
>> even a 4 TByte SSD will get worn out pretty rapidly.  That is for the
>> level of recording I do though, which is pretty heavy.  When huge SSDs
>> get down in price enough that you can afford to replace them every 4-5
>> years, then they will be the right choice for MythTV.  But we are not
>> there yet.
>
>
>Actually Stephen that is not true. Shock horror amazement (me not you):
>
>[sandypit] /home/jam [1002]% !459
>sudo /usr/sbin/smartctl -A /dev/sda
>[sudo] password for root:
>smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.12.14-lp150.12.45-default] (SUSE RPM)
>Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
>
>=== START OF READ SMART DATA SECTION ===
>SMART Attributes Data Structure revision number: 1
>Vendor Specific SMART Attributes with Thresholds:
>ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
>  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
>  9 Power_On_Hours          0x0032   099   099   000    Old_age   Always       -       1956
> 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       25
>177 Wear_Leveling_Count     0x0013   099   099   000    Pre-fail  Always       -       3
>179 Used_Rsvd_Blk_Cnt_Tot   0x0013   100   100   010    Pre-fail  Always       -       0
>181 Program_Fail_Cnt_Total  0x0032   100   100   010    Old_age   Always       -       0
>182 Erase_Fail_Count_Total  0x0032   100   100   010    Old_age   Always       -       0
>183 Runtime_Bad_Block       0x0013   100   100   010    Pre-fail  Always       -       0
>187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
>190 Airflow_Temperature_Cel 0x0032   062   048   000    Old_age   Always       -       38
>195 Hardware_ECC_Recovered  0x001a   200   200   000    Old_age   Always       -       0
>199 UDMA_CRC_Error_Count    0x003e   100   100   000    Old_age   Always       -       0
>235 Unknown_Attribute       0x0012   099   099   000    Old_age   Always       -       12
>241 Total_LBAs_Written      0x0032   099   099   000    Old_age   Always       -       3425086849
>
>Recording 1/2 doz shows / day on a samsung 1T disk with a total write life of 600T
>
>Based on 3 months usage 
>that?s 1.7T yielding a lifetime of 86 years.
>
>4T cheapest 4 bit mlc is 2x that.
>
>James

I record a bit more than that:

Number of shows:
    5252
Number of episodes:
    60734
First recording:
    Sunday November 29th, 2009
Last recording:
    Thursday March 21st, 2019
Total Running Time:
    9 years 3 months 20 days 16 hrs 43 mins
Total Recorded:
    6 years 12 days 11 hrs 30 mins
Percent of time spent recording:
    64%

A quick estimate of my recording seems to come out at just above 30
Gbytes per day, based on how much my free space has gone down since I
installed a 12 Tbyte drive to replace an old 3 Tbyte one.

But even then, it would be viable to use an SSD for recording now, as
that works out to 54 years of endurance at my rate of recording.  But
not for storage - I would still need to move recordings off on to hard
drives:

Recording space
Filesystem      Size  Used Avail Use% Mounted on
/dev/sdb3       3.7T  2.9T  818G  78% /mnt/rec1
/dev/sdd2        11T   11T  818G  93% /mnt/rec2
/dev/sda5       2.7T  1.9T  816G  70% /mnt/rec3
/dev/sdo1       3.7T  2.9T  817G  79% /mnt/rec4
/dev/sdc1       2.8T  2.0T  819G  71% /mnt/rec5
/dev/sdn1       3.7T  2.9T  819G  79% /mnt/rec6
/dev/sde1       5.5T  4.7T  818G  86% /mnt/rec7
total            33T   27T  5.6T  83% -

I think 33 Tbytes of SSD would still be a little too expensive.

From per at computer.org  Thu Mar 21 08:49:33 2019
From: per at computer.org (Per Jessen)
Date: Thu, 21 Mar 2019 09:49:33 +0100
Subject: [mythtv-users] 3TB...poof
References: <4D668658-CB57-4746-AFC0-DE00848F080B@tigger.ws>
 <tgb69et3uvfvub6gkakt6f42dhbcs4e6lo@4ax.com>
Message-ID: <q6vj6t$bp1$1@saturn.local.net>

Stephen Worthington wrote:

> 
> Recording space
> Filesystem      Size  Used Avail Use% Mounted on
> /dev/sdb3       3.7T  2.9T  818G  78% /mnt/rec1
> /dev/sdd2        11T   11T  818G  93% /mnt/rec2
> /dev/sda5       2.7T  1.9T  816G  70% /mnt/rec3
> /dev/sdo1       3.7T  2.9T  817G  79% /mnt/rec4
> /dev/sdc1       2.8T  2.0T  819G  71% /mnt/rec5
> /dev/sdn1       3.7T  2.9T  819G  79% /mnt/rec6
> /dev/sde1       5.5T  4.7T  818G  86% /mnt/rec7
> total            33T   27T  5.6T  83% -
> 
> I think 33 Tbytes of SSD would still be a little too expensive.

I see Samsung 2Tb SSDs at CHF365 - yeah, 15 of those would be a major
investment. :-)



-- 
Per Jessen, Z?rich (4.2?C)



From george.poulson at gmail.com  Thu Mar 21 08:51:02 2019
From: george.poulson at gmail.com (George Poulson)
Date: Thu, 21 Mar 2019 08:51:02 +0000
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <tgb69et3uvfvub6gkakt6f42dhbcs4e6lo@4ax.com>
References: <mailman.135.1553095143.1604.mythtv-users@mythtv.org>
 <4D668658-CB57-4746-AFC0-DE00848F080B@tigger.ws>
 <tgb69et3uvfvub6gkakt6f42dhbcs4e6lo@4ax.com>
Message-ID: <CACgjHi+-OHEQTWL2w=AAiL+0iBkRtA0LqHtC4D-mhAFLtUajAg@mail.gmail.com>

On Thu, 21 Mar 2019 at 06:40, Stephen Worthington <stephen_agent at jsw.gen.nz>
wrote:


> total            33T   27T  5.6T  83% -
>
> I think 33 Tbytes of SSD would still be a little too expensive.
>

I think you must have more recordings there than I could possibly watch in
my remaining lifetime :-O
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190321/5017317f/attachment.html>

From stephen_agent at jsw.gen.nz  Thu Mar 21 09:50:00 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Thu, 21 Mar 2019 22:50:00 +1300
Subject: [mythtv-users] 3TB...poof
In-Reply-To: <CACgjHi+-OHEQTWL2w=AAiL+0iBkRtA0LqHtC4D-mhAFLtUajAg@mail.gmail.com>
References: <mailman.135.1553095143.1604.mythtv-users@mythtv.org>
 <4D668658-CB57-4746-AFC0-DE00848F080B@tigger.ws>
 <tgb69et3uvfvub6gkakt6f42dhbcs4e6lo@4ax.com>
 <CACgjHi+-OHEQTWL2w=AAiL+0iBkRtA0LqHtC4D-mhAFLtUajAg@mail.gmail.com>
Message-ID: <5fn69edtm7d4j42sn7dh6oja3mi8hh3p0p@4ax.com>

On Thu, 21 Mar 2019 08:51:02 +0000, you wrote:

>On Thu, 21 Mar 2019 at 06:40, Stephen Worthington <stephen_agent at jsw.gen.nz>
>wrote:
>
>
>> total            33T   27T  5.6T  83% -
>>
>> I think 33 Tbytes of SSD would still be a little too expensive.
>>
>
>I think you must have more recordings there than I could possibly watch in
>my remaining lifetime :-O

Yes, that is about right.  But it means I always have enough to choose
from.  And about 15%? of that is recordings for my mother - I move
them to her MythTV box when she has enough room and wants some more.

From jfabernathy at gmail.com  Thu Mar 21 10:08:13 2019
From: jfabernathy at gmail.com (James Abernathy)
Date: Thu, 21 Mar 2019 06:08:13 -0400
Subject: [mythtv-users] mythtv android download link down
Message-ID: <624e64dd-32a8-3a5f-994e-a5518847a69a@gmail.com>

The link on the wiki for Mythtv Android 
(https://www.mythtv.org/wiki/Android) had a link for downloading the 
.APK that is returning a 502 Bad Gateway error message 
(https://dl.bintray.com/bennettpeter/generic/)

Jim A



From johnpilk222 at gmail.com  Thu Mar 21 11:16:57 2019
From: johnpilk222 at gmail.com (John Pilkington)
Date: Thu, 21 Mar 2019 11:16:57 +0000
Subject: [mythtv-users] mythtv android download link down
In-Reply-To: <624e64dd-32a8-3a5f-994e-a5518847a69a@gmail.com>
References: <624e64dd-32a8-3a5f-994e-a5518847a69a@gmail.com>
Message-ID: <601685fe-2b71-4ea7-c146-59fe8ac29341@gmail.com>

On 21/03/2019 10:08, James Abernathy wrote:
> The link on the wiki for Mythtv Android 
> (https://www.mythtv.org/wiki/Android) had a link for downloading the 
> .APK that is returning a 502 Bad Gateway error message 
> (https://dl.bintray.com/bennettpeter/generic/)
> 
> Jim A

It looks ok for me, but Firefox still gives an extra colon in the address

https://dl.bintray.com/bennettpeter/generic/mythtv_30/android_32/:mythfrontend-20190310-arm-v30.0-28-g60cfb7c05ae.apk

John P



From jfabernathy at gmail.com  Thu Mar 21 11:25:21 2019
From: jfabernathy at gmail.com (James Abernathy)
Date: Thu, 21 Mar 2019 07:25:21 -0400
Subject: [mythtv-users] mythtv android download link down
In-Reply-To: <601685fe-2b71-4ea7-c146-59fe8ac29341@gmail.com>
References: <624e64dd-32a8-3a5f-994e-a5518847a69a@gmail.com>
 <601685fe-2b71-4ea7-c146-59fe8ac29341@gmail.com>
Message-ID: <3f08513c-af46-3a22-47a6-26a89800458c@gmail.com>


On 3/21/19 7:16 AM, John Pilkington wrote:
> On 21/03/2019 10:08, James Abernathy wrote:
>> The link on the wiki for Mythtv Android 
>> (https://www.mythtv.org/wiki/Android) had a link for downloading the 
>> .APK that is returning a 502 Bad Gateway error message 
>> (https://dl.bintray.com/bennettpeter/generic/)
>>
>> Jim A
>
> It looks ok for me, but Firefox still gives an extra colon in the address
>
> https://dl.bintray.com/bennettpeter/generic/mythtv_30/android_32/:mythfrontend-20190310-arm-v30.0-28-g60cfb7c05ae.apk 
>
>
> John P

It's back up for me now.



From pb.mythtv at gmail.com  Thu Mar 21 14:27:39 2019
From: pb.mythtv at gmail.com (Peter Bennett)
Date: Thu, 21 Mar 2019 10:27:39 -0400
Subject: [mythtv-users] 4K Video Settings
In-Reply-To: <m3va0cde7b.fsf@xanthu.gervasio.home>
References: <34892D98-E6E5-4183-924A-7A3CD5416B30@cogeco.ca>
 <5eb17e04-07d3-b3e7-1422-9fdb52546255@gmail.com>
 <d6513ad5-3424-f92f-d9f8-aefef4c4ad40@itrans.com>
 <3d8a228e-25c5-6fdf-77f4-0b92219d43d1@gmail.com>
 <m3va0cde7b.fsf@xanthu.gervasio.home>
Message-ID: <a161affe-0cec-9eca-898a-98fcadb328fc@gmail.com>



On 3/21/19 12:49 AM, Gregorio Gervasio Jr. wrote:
>>>>>> Peter Bennett writes:
> [...]
>> To get 2x deinterlace, you need a refresh rate of 50 or 60 Hz. At 4K
>> resolution this needs a HDMI 2.1 cable and an HDMI 2.1 capable port on
>> your video card and TV. On my 4K display, only the first HDMI port
>> supports 60 Hz, the second port runs only at 30 Hz at 4K resolution..
> [...]
>
> I think you meant HDMI 2.0.  The first HDMI 2.1 TVs aren't coming out
> for a few more weeks (LG's new OLEDs and high-end LCDs).
>
Yes - you are correct - HDMI 2.0, Sorry

Peter

From digitalaudiorock at gmail.com  Thu Mar 21 19:14:48 2019
From: digitalaudiorock at gmail.com (Tom Dexter)
Date: Thu, 21 Mar 2019 15:14:48 -0400
Subject: [mythtv-users] Sudden issue with HDHomeRun on network switch?
In-Reply-To: <CADUj1Ou6Txm4=4_K3HsJPkw26FHwoatz3PkHAKSyPfNN2MD7Hw@mail.gmail.com>
References: <CADUj1OvqnANNQFbiwVEtkX8Y=zWc+E1DrDN+CcLoX0_RpM-h4Q@mail.gmail.com>
 <4075CFF1-8231-4D53-86F2-CF241F389812@thehobsons.co.uk>
 <CADUj1Ou6Txm4=4_K3HsJPkw26FHwoatz3PkHAKSyPfNN2MD7Hw@mail.gmail.com>
Message-ID: <CADUj1Osk=HT2V+FsoHcocrACUV0sGRvZ2r+DR9jxJNuMG2C=gg@mail.gmail.com>

On 3/15/19, Tom Dexter <digitalaudiorock at gmail.com> wrote:
> On 3/15/19, Simon Hobson <linux at thehobsons.co.uk> wrote:
>> Tom Dexter <digitalaudiorock at gmail.com> wrote:
>>
>> ...
>>> I have no idea what to make of that at all. I can only think that
>>> maybe the switch is going bad(?)
>>
>> It does sound rather like the switch. They can fail in "interesting" ways
>> -
>> I've had them "sort of" stop passing packets reliably, as in passing some
>> packets but not others !
>>
>> Certainly in a case like this, the obvious thing to do is swap the switch
>> and see what happens.
>>
>> The fact that some devices work and others don't could be simply down to
>> slight variations in how the protocols are implemented. Behind the scenes
>> there's actually a complete (albeit relatively simple) signalling
>> protocol
>> to allow the two ends to negotiate a link between them.
>> A few years ago we had a customer with 2 sites with a road in between. We
>> sold them an optical link which turned out to have an "interesting"
>> design
>> feature which meant that it didn't work with all switches. The people who
>> supplied and installed it for us couldn't tell us what the issue was -
>> but
>> we eventually tracked down that these units didn't negotiate the link
>> properly so they would only work with managed switched where the port can
>> be
>> hard configured to a specific set of link parameters.
>>
>>
>>> Any recommendations are welcome. I was looking at a Netgear GS316
>>> which seem to get pretty good reviews.
>>
>> It's looks like it's a variant of their GS1nn models. I've always found*
>> the
>> [FG]S1nn models to be very reliable, so I'd have no hesitation in trying
>> the
>> 316.
>>
>> * With work hats on, I've known a lot of networks run on them.
>>
>
> Thanks for the reply! I think you're right on all that. I've had my
> existing switch for quite a while and it was really cheap. I might
> just go ahead and get that Netgear. Thanks for the recommendation!
>
> Tom
>

Just to update on this one: As long as I kept the problem HDHR on my
router instead of the switch it worked perfectly. In fact the
occasional failed recordings I've had for a while appear to be a thing
of the past.

Today I got a new switch...went with an 8-port Netgear GS308-100PAS.
That's now hooked up and both HDHRs are working perfectly connected to
it. So yea...switches can do some seemingly arbitrary stuff for sure.

Thanks everyone for the help!
Tom

From jam at tigger.ws  Fri Mar 22 13:23:10 2019
From: jam at tigger.ws (James Linder)
Date: Fri, 22 Mar 2019 21:23:10 +0800
Subject: [mythtv-users] C change card
In-Reply-To: <mailman.135.1553095143.1604.mythtv-users@mythtv.org>
References: <mailman.135.1553095143.1604.mythtv-users@mythtv.org>
Message-ID: <5C5D1E17-A412-40A2-A279-CD1C83D5A19D@tigger.ws>

Hi
I added a second dual tuner USB dongle.
Can anybody say that this is ?normal?

  card 1	channel A	Haupauge Nova dual HD
C card 2	channel any A mux
C card 1	channel B
C card 2	channel any B mux

C card 3	channel X	Winfast dual win TV
C card 3	channel any X mux
C card 4	channel X
C card 4	channel X (but without doubt cold select any on Xs mux)

just puzzled by order being 1 2 1 2 3 3 4 4. I setup 2 virtual tuners on each tuner.
I had 1 Haupauge tuner stop working until power cycled.
FYI the new haupauge win TV dual tuner *does* work on kernel 4.18 and getting firmware dvb-demod-si2168-02.fw

James

From jayf0ster at roadrunner.com  Fri Mar 22 16:54:11 2019
From: jayf0ster at roadrunner.com (Jay Foster)
Date: Fri, 22 Mar 2019 09:54:11 -0700
Subject: [mythtv-users] Ubuntu Nvidia Driver Update
Message-ID: <748fdf96-011c-9720-1335-de8a6f3cad81@roadrunner.com>

I am currently running 0.28-fixes on mythbuntu 14.04.? I have the NVIDIA 
Corporation GK208 [GeForce GT 630 Rev. 2] (rev a1) video card with the 
340.102 driver.? There is an update available to the 340.107 driver.? 
Are there any known issues with this update?? Will it fix the video 
artifacts on some NBC stations when using VDPAU?

Jay

From support at drdos.info  Fri Mar 22 17:04:46 2019
From: support at drdos.info (Doug Lytle)
Date: Fri, 22 Mar 2019 13:04:46 -0400 (EDT)
Subject: [mythtv-users] Ubuntu Nvidia Driver Update
In-Reply-To: <748fdf96-011c-9720-1335-de8a6f3cad81@roadrunner.com>
References: <748fdf96-011c-9720-1335-de8a6f3cad81@roadrunner.com>
Message-ID: <sig.29849f1bde.434142291.851.1553274286764.JavaMail.zimbra@drdos.info>

>>> There is an update available to the 340.107 driver

Debian is only offering 340.106, which I upgraded to a couple weeks ago without issue.

Hopefully .107 isn't that much of a difference.

Doug

From mike.bibbings at gmail.com  Fri Mar 22 18:47:41 2019
From: mike.bibbings at gmail.com (Mike Bibbings)
Date: Fri, 22 Mar 2019 18:47:41 +0000
Subject: [mythtv-users] C change card
In-Reply-To: <5C5D1E17-A412-40A2-A279-CD1C83D5A19D@tigger.ws>
References: <mailman.135.1553095143.1604.mythtv-users@mythtv.org>
 <5C5D1E17-A412-40A2-A279-CD1C83D5A19D@tigger.ws>
Message-ID: <dca255cd-01a5-ca51-ff71-42b180bfd4df@gmail.com>

On 22/03/2019 13:23, James Linder wrote:
> Hi
> I added a second dual tuner USB dongle.
> Can anybody say that this is ?normal?
>
>    card 1	channel A	Haupauge Nova dual HD
> C card 2	channel any A mux
> C card 1	channel B
> C card 2	channel any B mux
>
> C card 3	channel X	Winfast dual win TV
> C card 3	channel any X mux
> C card 4	channel X
> C card 4	channel X (but without doubt cold select any on Xs mux)
>
> just puzzled by order being 1 2 1 2 3 3 4 4. I setup 2 virtual tuners on each tuner.
> I had 1 Haupauge tuner stop working until power cycled.
> FYI the new haupauge win TV dual tuner *does* work on kernel 4.18 and getting firmware dvb-demod-si2168-02.fw
>
> James

What version of mythtv are you using?

That order looks like it is due to the way in which the tuners were 
configured.

In earlier mythtv versions e.g. 0.28 the Multi record settings were set 
in Capture Card setup.

Later versions e.g. 29 and on, moved the setting to Input Connections 
setup (Interactions between Inputs).

With these later versions, if you want a sequential order, which is not 
normally needed, you need to add the tuner in Capture Card, setup a 
Video Source, then go to Input Connections and set Multi record before 
adding the next tuner in Capture Cards.

As far as kernel 4.18 is concerned, yes, most of the Hauppauge changes 
have been incorporated .

Hauppauge (Brad Love) did a good job in getting the changes incorporated 
in later kernel versions (via V4L subsystem), although there are still a 
few changes not yet upstreamed.

Hauppauge also provide a custom kernel ppa for Ubuntu based systems 
(https://github.com/b-rad-NDi/Ubuntu-media-tree-kernel-builder).

I just wish TBS had done the same, I have a number of TBS cards and have 
to rebuild V4L every time the kernel gets updated.


Mike





From pb.mythtv at gmail.com  Fri Mar 22 18:56:34 2019
From: pb.mythtv at gmail.com (Peter Bennett)
Date: Fri, 22 Mar 2019 14:56:34 -0400
Subject: [mythtv-users] Ubuntu Nvidia Driver Update
In-Reply-To: <748fdf96-011c-9720-1335-de8a6f3cad81@roadrunner.com>
References: <748fdf96-011c-9720-1335-de8a6f3cad81@roadrunner.com>
Message-ID: <3bf92b7f-96d5-c83d-c2f5-f1213fbde5dd@gmail.com>



On 3/22/19 12:54 PM, Jay Foster wrote:
> I am currently running 0.28-fixes on mythbuntu 14.04.? I have the 
> NVIDIA Corporation GK208 [GeForce GT 630 Rev. 2] (rev a1) video card 
> with the 340.102 driver.? There is an update available to the 340.107 
> driver.? Are there any known issues with this update? Will it fix the 
> video artifacts on some NBC stations when using VDPAU?
>

There is no fix for the mpeg2 pixellation issue, that seems to be on all 
Nvidia devices including shield. I am running version 418.43 and the 
problem exists there as well.

You can get newer driver versions using the ppa:
sudo add-apt-repository ppa:graphics-drivers/ppa

v 396 and above will support NVDEC in Mythtv (master branch)
v 415 and above will support h265 playback using vdpau or nvdec (master 
branch)



From pb.mythtv at gmail.com  Fri Mar 22 18:56:44 2019
From: pb.mythtv at gmail.com (Peter Bennett)
Date: Fri, 22 Mar 2019 14:56:44 -0400
Subject: [mythtv-users] Ubuntu Nvidia Driver Update
In-Reply-To: <748fdf96-011c-9720-1335-de8a6f3cad81@roadrunner.com>
References: <748fdf96-011c-9720-1335-de8a6f3cad81@roadrunner.com>
Message-ID: <d182db5b-eb78-49f8-6932-49a5ce4eae8d@gmail.com>



On 3/22/19 12:54 PM, Jay Foster wrote:
> I am currently running 0.28-fixes on mythbuntu 14.04.? I have the 
> NVIDIA Corporation GK208 [GeForce GT 630 Rev. 2] (rev a1) video card 
> with the 340.102 driver.? There is an update available to the 340.107 
> driver.? Are there any known issues with this update? Will it fix the 
> video artifacts on some NBC stations when using VDPAU?
>

There is no fix for the mpeg2 pixellation issue, that seems to be on all 
Nvidia devices including shield. I am running version 418.43 and the 
problem exists there as well.

You can get newer driver versions using the ppa:
sudo add-apt-repository ppa:graphics-drivers/ppa

v 396 and above will support NVDEC in Mythtv (master branch)
v 415 and above will support h265 playback using vdpau or nvdec (master 
branch)



From david at istwok.net  Fri Mar 22 21:32:52 2019
From: david at istwok.net (David Engel)
Date: Fri, 22 Mar 2019 16:32:52 -0500
Subject: [mythtv-users] Ubuntu Nvidia Driver Update
In-Reply-To: <3bf92b7f-96d5-c83d-c2f5-f1213fbde5dd@gmail.com>
References: <748fdf96-011c-9720-1335-de8a6f3cad81@roadrunner.com>
 <3bf92b7f-96d5-c83d-c2f5-f1213fbde5dd@gmail.com>
Message-ID: <20190322213252.GA11558@opus.istwok.net>

On Fri, Mar 22, 2019 at 02:56:34PM -0400, Peter Bennett wrote:
> 
> 
> On 3/22/19 12:54 PM, Jay Foster wrote:
> > I am currently running 0.28-fixes on mythbuntu 14.04.? I have the NVIDIA
> > Corporation GK208 [GeForce GT 630 Rev. 2] (rev a1) video card with the
> > 340.102 driver.? There is an update available to the 340.107 driver.?
> > Are there any known issues with this update? Will it fix the video
> > artifacts on some NBC stations when using VDPAU?
> > 
> 
> There is no fix for the mpeg2 pixellation issue, that seems to be on all
> Nvidia devices including shield. I am running version 418.43 and the problem
> exists there as well.

Very old cards do not have the problem.  I still have a 9500GT that
doesn't have the pixelation problem.  Of course, that card also
doesn't do other things that newer cards do like HDMI, 4k and h.264/5.

David
-- 
David Engel
david at istwok.net

From jan.ceuleers at gmail.com  Sat Mar 23 07:10:51 2019
From: jan.ceuleers at gmail.com (Jan Ceuleers)
Date: Sat, 23 Mar 2019 08:10:51 +0100
Subject: [mythtv-users] Slave backend reboot procedure
Message-ID: <dcb28f44-7e3e-ad12-fc4a-a6a2c281494e@gmail.com>

Dear list,

A little while ago I moved some of my tuners to another location in the
house so that they are closer to the signal source, thereby improving
recording quality. In doing so I connected them to a machine which
previously was only a frontend, i.e. turning it into a slave backend as
well.

It seems though that whenever I reboot that machine its tuners aren't
regarded as being available (as repported by Mythweb) until I also
restart the slave backend (not necessarily the whole machine, just the
backend service).

Many years ago I also had a slave backend (on a much older MythTV
release), and I remember that restarting the slave backend caused its
tuners to become available automatically, i.e. without the need to
restart the master backend process.

I therefore assume that there is something in my configuration which
currently breaks this. Any ideas?

$ mythbackend --version
Please attach all output as a file in bug reports.
MythTV Version : v29.1
MythTV Branch :
Network Protocol : 91
Library API : 29.20180316-1
QT Version : 5.5.1
Options compiled in:
 linux profile use_hidesyms using_alsa using_oss using_pulse
using_pulseoutput using_backend using_bindings_perl
using_bindings_python using_bindings_php using_crystalhd using_dvb
using_firewire using_frontend using_hdhomerun using_vbox using_ceton
using_hdpvr using_ivtv using_joystick_menu using_libcec using_libcrypto
using_libdns_sd using_libfftw3 using_libxml2 using_lirc using_mheg
using_opengl using_opengl_video using_opengl_themepainter using_qtwebkit
using_qtscript using_qtdbus using_taglib using_v4l2 using_x11
using_xrandr using_xv using_profiletype using_systemd_notify
using_systemd_journal using_bindings_perl using_bindings_python
using_bindings_php using_freetype2 using_mythtranscode using_opengl
using_vaapi using_vdpau using_ffmpeg_threads using_mheg using_libass
using_libxml2 using_libmp3lame

Thanks, Jan

From hikavdh at gmail.com  Sat Mar 23 10:55:17 2019
From: hikavdh at gmail.com (Hika van den Hoven)
Date: Sat, 23 Mar 2019 11:55:17 +0100
Subject: [mythtv-users] Slave backend reboot procedure
In-Reply-To: <dcb28f44-7e3e-ad12-fc4a-a6a2c281494e@gmail.com>
References: <dcb28f44-7e3e-ad12-fc4a-a6a2c281494e@gmail.com>
Message-ID: <187262311.20190323115517@gmail.com>

Hoi Jan,

Saturday, March 23, 2019, 8:10:51 AM, you wrote:

> Dear list,

> A little while ago I moved some of my tuners to another location in the
> house so that they are closer to the signal source, thereby improving
> recording quality. In doing so I connected them to a machine which
> previously was only a frontend, i.e. turning it into a slave backend as
> well.

> It seems though that whenever I reboot that machine its tuners aren't
> regarded as being available (as repported by Mythweb) until I also
> restart the slave backend (not necessarily the whole machine, just the
> backend service).

> Many years ago I also had a slave backend (on a much older MythTV
> release), and I remember that restarting the slave backend caused its
> tuners to become available automatically, i.e. without the need to
> restart the master backend process.

> I therefore assume that there is something in my configuration which
> currently breaks this. Any ideas?

I have the same under 0.27 (Gentoo). I think the slave needs to be on
when I start the master. But I have never really investigated as the
tuner on the slave is only there for show. I only use the slave on my
regular working machine for heavy jobs. I don't think I have ever
changed anything in this regard from the default.

I just checked and it shows as 'currently not connected'. I have
restarted the machine with the slave 1 or 2 weeks ago, I normally only
suspend it and the master has been running longer. When I restart the
master I normally do that from the machine running the slave, but it
could be that last time the slave was not running.

Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens


From hikavdh at gmail.com  Sat Mar 23 11:00:55 2019
From: hikavdh at gmail.com (Hika van den Hoven)
Date: Sat, 23 Mar 2019 12:00:55 +0100
Subject: [mythtv-users] Slave backend reboot procedure
In-Reply-To: <187262311.20190323115517@gmail.com>
References: <dcb28f44-7e3e-ad12-fc4a-a6a2c281494e@gmail.com>
 <187262311.20190323115517@gmail.com>
Message-ID: <816766399.20190323120055@gmail.com>

Hoi Hika,

Saturday, March 23, 2019, 11:55:17 AM, you wrote:

> Hoi Jan,

> Saturday, March 23, 2019, 8:10:51 AM, you wrote:

>> Dear list,

>> A little while ago I moved some of my tuners to another location in the
>> house so that they are closer to the signal source, thereby improving
>> recording quality. In doing so I connected them to a machine which
>> previously was only a frontend, i.e. turning it into a slave backend as
>> well.

>> It seems though that whenever I reboot that machine its tuners aren't
>> regarded as being available (as repported by Mythweb) until I also
>> restart the slave backend (not necessarily the whole machine, just the
>> backend service).

>> Many years ago I also had a slave backend (on a much older MythTV
>> release), and I remember that restarting the slave backend caused its
>> tuners to become available automatically, i.e. without the need to
>> restart the master backend process.

>> I therefore assume that there is something in my configuration which
>> currently breaks this. Any ideas?

> I have the same under 0.27 (Gentoo). I think the slave needs to be on
> when I start the master. But I have never really investigated as the
> tuner on the slave is only there for show. I only use the slave on my
> regular working machine for heavy jobs. I don't think I have ever
> changed anything in this regard from the default.

> I just checked and it shows as 'currently not connected'. I have
> restarted the machine with the slave 1 or 2 weeks ago, I normally only
> suspend it and the master has been running longer. When I restart the
> master I normally do that from the machine running the slave, but it
> could be that last time the slave was not running.

I just checked. Restarting the master didn't change the status.
Restarting the slave did.


Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens


From stuarta at squashedfrog.net  Mon Mar 25 09:22:11 2019
From: stuarta at squashedfrog.net (Stuart Auchterlonie)
Date: Mon, 25 Mar 2019 09:22:11 +0000
Subject: [mythtv-users] Slave backend reboot procedure
In-Reply-To: <dcb28f44-7e3e-ad12-fc4a-a6a2c281494e@gmail.com>
References: <dcb28f44-7e3e-ad12-fc4a-a6a2c281494e@gmail.com>
Message-ID: <0d6bf9b8-9d51-5002-b96d-aebf7945ff18@squashedfrog.net>

On 23/03/2019 07:10, Jan Ceuleers wrote:
> Dear list,
> 
> A little while ago I moved some of my tuners to another location in the
> house so that they are closer to the signal source, thereby improving
> recording quality. In doing so I connected them to a machine which
> previously was only a frontend, i.e. turning it into a slave backend as
> well.
> 
> It seems though that whenever I reboot that machine its tuners aren't
> regarded as being available (as repported by Mythweb) until I also
> restart the slave backend (not necessarily the whole machine, just the
> backend service).
> 
> Many years ago I also had a slave backend (on a much older MythTV
> release), and I remember that restarting the slave backend caused its
> tuners to become available automatically, i.e. without the need to
> restart the master backend process.
> 
> I therefore assume that there is something in my configuration which
> currently breaks this. Any ideas?
> 

It could be coming online before the networking is available
and therefore doesn't come up properly.

You've no said what distro you are running on, so depending on
which one, and whether it's systemd, you may need to
a) verify this is the issue
b) work out how to ensure the slave backend service is started
   after networking is online.


Regards
Stuart


> $ mythbackend --version
> Please attach all output as a file in bug reports.
> MythTV Version : v29.1
> MythTV Branch :
> Network Protocol : 91
> Library API : 29.20180316-1
> QT Version : 5.5.1
> Options compiled in:
>  linux profile use_hidesyms using_alsa using_oss using_pulse
> using_pulseoutput using_backend using_bindings_perl
> using_bindings_python using_bindings_php using_crystalhd using_dvb
> using_firewire using_frontend using_hdhomerun using_vbox using_ceton
> using_hdpvr using_ivtv using_joystick_menu using_libcec using_libcrypto
> using_libdns_sd using_libfftw3 using_libxml2 using_lirc using_mheg
> using_opengl using_opengl_video using_opengl_themepainter using_qtwebkit
> using_qtscript using_qtdbus using_taglib using_v4l2 using_x11
> using_xrandr using_xv using_profiletype using_systemd_notify
> using_systemd_journal using_bindings_perl using_bindings_python
> using_bindings_php using_freetype2 using_mythtranscode using_opengl
> using_vaapi using_vdpau using_ffmpeg_threads using_mheg using_libass
> using_libxml2 using_libmp3lame
> 
> Thanks, Jan
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
> 


From jan.ceuleers at gmail.com  Mon Mar 25 15:47:35 2019
From: jan.ceuleers at gmail.com (Jan Ceuleers)
Date: Mon, 25 Mar 2019 16:47:35 +0100
Subject: [mythtv-users] Slave backend reboot procedure
In-Reply-To: <0d6bf9b8-9d51-5002-b96d-aebf7945ff18@squashedfrog.net>
References: <dcb28f44-7e3e-ad12-fc4a-a6a2c281494e@gmail.com>
 <0d6bf9b8-9d51-5002-b96d-aebf7945ff18@squashedfrog.net>
Message-ID: <8495340e-38af-9f68-52e0-99b0b491108c@gmail.com>

On 25/03/2019 10:22, Stuart Auchterlonie wrote:
> It could be coming online before the networking is available
> and therefore doesn't come up properly.
> 
> You've no said what distro you are running on, so depending on
> which one, and whether it's systemd, you may need to
> a) verify this is the issue
> b) work out how to ensure the slave backend service is started
>    after networking is online.

Stuart,

Thanks. It's Ubuntu 16.04, i.e. with systemd. Here is the service file
on the slave backend:

# cat /etc/systemd/system/mythtv-backend.service
# JCE modified this file:
# 1. set StartLimitInterval to 0 (was 10m)
# 2. add dependency on videop* devices
# 3. drop mysql.service dependency (since this is a slave backend)

[Unit]
Description=MythTV Backend
Documentation=https://www.mythtv.org/wiki/Mythbackend
After=network.target dev-videop2.device dev-videop3.device
dev-videop5.device
wants=dev-videop2.device dev-videop3.device dev-videop5.device

[Service]
User=mythtv
EnvironmentFile=-/etc/mythtv/additional.args
ExecStart=/usr/bin/mythbackend --quiet --syslog local7 $ADDITIONAL_ARGS
#StartLimitBurst=10
StartLimitInterval=0
Restart=on-failure
RestartSec=1

[Install]
WantedBy=multi-user.target


And on the master backend:

# cat /etc/systemd/system/mythtv-backend.service
# JCE modified this file:
# 1. set StartLimitInterval to 0 (was 10m)
# 2. add dependency on videop* devices

[Unit]
Description=MythTV Backend
Documentation=https://www.mythtv.org/wiki/Mythbackend
After=mysql.service network.target dev-videop0.device dev-videop1.device
Wants=dev-videop0.device dev-videop1.device

[Service]
User=mythtv
EnvironmentFile=-/etc/mythtv/additional.args
ExecStart=/usr/bin/mythbackend --quiet --syslog local7 $ADDITIONAL_ARGS
StartLimitBurst=10
StartLimitInterval=10min
Restart=on-failure
RestartSec=20

[Install]
WantedBy=multi-user.target


The /dev/videop* devices are created by udev rules (the p stands for
persistent) based on the tuners' serial numbers:

# cat /etc/udev/rules.d/10-JCE-persistent-tuner.rules
# Create a persistent name /dev/videop0 to tuner SN 7300-00-F06D3877
SUBSYSTEM=="video4linux", KERNEL=="video[0-9]*",
ATTRS{manufacturer}=="Hauppauge", ATTRS{product}=="WinTV",
ATTRS{serial}=="7300-00-F06D3877", SYMLINK+="videop0"

# Create a persistent name /dev/videop1 to tuner SN 7300-00-F06C9907
SUBSYSTEM=="video4linux", KERNEL=="video[0-9]*",
ATTRS{manufacturer}=="Hauppauge", ATTRS{product}=="WinTV",
ATTRS{serial}=="7300-00-F06C9907", SYMLINK+="videop1"

# Create a persistent name /dev/videop2 to tuner SN 7300-00-F06EFBC0 old
# Create a persistent name /dev/videop2 to tuner SN 7300-00-F082CB8C
SUBSYSTEM=="video4linux", KERNEL=="video[0-9]*",
ATTRS{manufacturer}=="Hauppauge", ATTRS{product}=="WinTV",
ATTRS{serial}=="7300-00-F082CB8C", SYMLINK+="videop2"

# Create a persistent name /dev/videop3 to tuner SN 7300-00-F07801CC
SUBSYSTEM=="video4linux", KERNEL=="video[0-9]*",
ATTRS{manufacturer}=="Hauppauge", ATTRS{product}=="WinTV",
ATTRS{serial}=="7300-00-F07801CC", SYMLINK+="videop3"

# Create a persistent name /dev/videop5 to tuner SN 7300-00-F0000002
SUBSYSTEM=="video4linux", KERNEL=="video[0-9]*",
ATTRS{manufacturer}=="Hauppauge", ATTRS{product}=="WinTV",
ATTRS{serial}=="7300-00-F0000002", SYMLINK+="videop5"


The creation of the device nodes is also signaled to systemd thusly:

# cat /etc/udev/rules.d/99-mythbackend.rules
#
# Create systemd device units for capture devices
#
# JCE: From https://www.mythtv.org/wiki/Systemd_mythbackend_Configuration
#
SUBSYSTEM=="video4linux", TAG+="systemd"
SUBSYSTEM=="dvb", TAG+="systemd"
SUBSYSTEM=="firewire", TAG+="systemd"

Thanks, Jan

From mythtv at hbuus.com  Mon Mar 25 18:13:47 2019
From: mythtv at hbuus.com (faginbagin)
Date: Mon, 25 Mar 2019 14:13:47 -0400
Subject: [mythtv-users] Slave backend reboot procedure
In-Reply-To: <dcb28f44-7e3e-ad12-fc4a-a6a2c281494e@gmail.com>
References: <dcb28f44-7e3e-ad12-fc4a-a6a2c281494e@gmail.com>
Message-ID: <b74e2de2-9ebf-42a2-f087-7c5158d8f5a1@hbuus.com>

On 3/23/2019 3:10 AM, Jan Ceuleers wrote:
> Dear list,
> 
> A little while ago I moved some of my tuners to another location in the
> house so that they are closer to the signal source, thereby improving
> recording quality. In doing so I connected them to a machine which
> previously was only a frontend, i.e. turning it into a slave backend as
> well.
> 
> It seems though that whenever I reboot that machine its tuners aren't
> regarded as being available (as repported by Mythweb) until I also
> restart the slave backend (not necessarily the whole machine, just the
> backend service).
> 
> Many years ago I also had a slave backend (on a much older MythTV
> release), and I remember that restarting the slave backend caused its
> tuners to become available automatically, i.e. without the need to
> restart the master backend process.
> 
> I therefore assume that there is something in my configuration which
> currently breaks this. Any ideas?
> 
> $ mythbackend --version
> Please attach all output as a file in bug reports.
> MythTV Version : v29.1
> MythTV Branch :
> Network Protocol : 91
> Library API : 29.20180316-1
> QT Version : 5.5.1
> Options compiled in:
>  linux profile use_hidesyms using_alsa using_oss using_pulse
> using_pulseoutput using_backend using_bindings_perl
> using_bindings_python using_bindings_php using_crystalhd using_dvb
> using_firewire using_frontend using_hdhomerun using_vbox using_ceton
> using_hdpvr using_ivtv using_joystick_menu using_libcec using_libcrypto
> using_libdns_sd using_libfftw3 using_libxml2 using_lirc using_mheg
> using_opengl using_opengl_video using_opengl_themepainter using_qtwebkit
> using_qtscript using_qtdbus using_taglib using_v4l2 using_x11
> using_xrandr using_xv using_profiletype using_systemd_notify
> using_systemd_journal using_bindings_perl using_bindings_python
> using_bindings_php using_freetype2 using_mythtranscode using_opengl
> using_vaapi using_vdpau using_ffmpeg_threads using_mheg using_libass
> using_libxml2 using_libmp3lame
> 
> Thanks, Jan
> 

FWIW, I don't have this problem. I've got a slave backend that's woken
by wake-on-lan in time to record prime time shows, and I don't have to
restart the mythbackend process on the slave to see the tuners. However,
my tuners are PCI cards (two Hauppauge HVR-1600 cards), and I'm guessing
yours are USB tuners. Maybe that's the difference?

FWIW, I'm running the same mythtv version as you, but on Ubuntu 18.04.

From jan.ceuleers at gmail.com  Mon Mar 25 18:54:55 2019
From: jan.ceuleers at gmail.com (Jan Ceuleers)
Date: Mon, 25 Mar 2019 19:54:55 +0100
Subject: [mythtv-users] Slave backend reboot procedure
In-Reply-To: <b74e2de2-9ebf-42a2-f087-7c5158d8f5a1@hbuus.com>
References: <dcb28f44-7e3e-ad12-fc4a-a6a2c281494e@gmail.com>
 <b74e2de2-9ebf-42a2-f087-7c5158d8f5a1@hbuus.com>
Message-ID: <91f0ac03-a1ba-e28f-5b79-85b34dfe53c6@gmail.com>

On 25/03/2019 19:13, faginbagin wrote:
> FWIW, I don't have this problem. I've got a slave backend that's woken
> by wake-on-lan in time to record prime time shows, and I don't have to
> restart the mythbackend process on the slave to see the tuners. However,
> my tuners are PCI cards (two Hauppauge HVR-1600 cards), and I'm guessing
> yours are USB tuners. Maybe that's the difference?
> 
> FWIW, I'm running the same mythtv version as you, but on Ubuntu 18.04.

Thanks Helen

From colonius at free.fr  Mon Mar 25 18:59:28 2019
From: colonius at free.fr (Klaus Becker)
Date: Mon, 25 Mar 2019 19:59:28 +0100
Subject: [mythtv-users] frontend in english
Message-ID: <8a172a98-e14d-5ce3-ed11-babe1e0c9b66@free.fr>

Hi,

how to change frontend language from french to english?

In Debian unstable, I found no way to do that.

I searched on the web and in mythweb.

I tried

$ export LANG=; mythfrontend

and

$ export LANG=en_US.UTF-8; mythfrontend.

Both work with other programms, but not with frontend or setup.

cheers

Klaus

From mike.bibbings at gmail.com  Mon Mar 25 19:22:00 2019
From: mike.bibbings at gmail.com (Mike Bibbings)
Date: Mon, 25 Mar 2019 19:22:00 +0000
Subject: [mythtv-users] frontend in english
In-Reply-To: <8a172a98-e14d-5ce3-ed11-babe1e0c9b66@free.fr>
References: <8a172a98-e14d-5ce3-ed11-babe1e0c9b66@free.fr>
Message-ID: <3a2c75b3-4452-15c5-5077-d9d99b71875e@gmail.com>

On 25/03/2019 18:59, Klaus Becker wrote:
> Hi,
>
> how to change frontend language from french to english?
>
> In Debian unstable, I found no way to do that.
>
> I searched on the web and in mythweb.
>
> I tried
>
> $ export LANG=; mythfrontend
>
> and
>
> $ export LANG=en_US.UTF-8; mythfrontend.
>
> Both work with other programms, but not with frontend or setup.
>
> cheers
>
> Klaus 


It is done in mythfrontend Setup>Appearance>Localisation.

Just tried it on my system (English > French)

Mike



From jksjdevelop at gmail.com  Mon Mar 25 19:33:16 2019
From: jksjdevelop at gmail.com (jksjdevelop)
Date: Mon, 25 Mar 2019 19:33:16 +0000
Subject: [mythtv-users] Change v30.0-25-gbceea69806 makes playback visibly
 jumpy (March 10th)
Message-ID: <23227c7c-33e3-d2a6-9398-2fa37057cd77@googlemail.com>

The Medea is 1080i 25Hz UK DVB-S2

The platform is Ubuntu 18.10 64 bit Nvidia GeForce GT 1030/PCIe/SSE2 
Driver Version: 390.116

Change AVSync2: Use frame timestamps to determine elapsed play time - 
causes frames to be discarded.

With verbose logging on playback.

At the previous commit, the picture is rock solid with an even scrolling 
news ticker, despite some frames being discarded

MythTV Version : v30.0-24-g90468ec49a
MythTV Branch : (HEAD detached at 90468ec49a)

2019-03-25 18:37:47.571475 I? Player(0): FPS:?? 25.09 Mean: 39850 
Std.Dev:? 6823 CPUs: 6% 4% 3% 3%
2019-03-25 18:37:47.611354 I? Player(0): AV Sync, audio ahead by -25 ms
2019-03-25 18:37:47.651361 I? Player(0): AV Sync, audio ahead by -24 ms
2019-03-25 18:37:47.691386 I? Player(0): AV Sync, audio ahead by -24 ms
2019-03-25 18:37:47.731370 I? Player(0): AV Sync, audio ahead by 61 ms
2019-03-25 18:37:47.771335 I? Player(0): AV Sync, audio ahead by -24 ms
2019-03-25 18:37:47.811385 I? Player(0): AV Sync, audio ahead by -24 ms
2019-03-25 18:37:47.851356 I? Player(0): AV Sync, audio ahead by -25 ms
2019-03-25 18:37:47.945553 I? Player(0): AV Sync, audio ahead by 75 ms
2019-03-25 18:37:48.115719 I? Player(0): AV Sync, audio ahead by 86 ms
2019-03-25 18:37:48.165400 I? Player(0): AV Sync, audio ahead by 96 ms
2019-03-25 18:37:48.265463 I? Player(0): AV Sync, audio ahead by 75 ms
2019-03-25 18:37:48.315680 I? Player(0): AV Sync, audio ahead by 85 ms
2019-03-25 18:37:48.375455 I? Player(0): AV Sync, audio ahead by 66 ms
2019-03-25 18:37:48.455489 I? Player(0): AV Sync, audio ahead by 65 ms
2019-03-25 18:37:48.505434 I? Player(0): AV Sync, audio ahead by 75 ms
2019-03-25 18:37:48.515385 I? VidOutVDPAU: Frame B is in use by avlib 
and so is being held for later discarding.
2019-03-25 18:37:48.535378 I? VidOutVDPAU: Frame B is in use by avlib 
and so is being held for later discarding.
2019-03-25 18:37:48.535387 I? VidOutVDPAU: Frame B is in use by avlib 
and so is being held for later discarding.
2019-03-25 18:37:48.551326 I? VidOutVDPAU: Frame B is in use by avlib 
and so is being held for later discarding.
2019-03-25 18:37:48.551335 I? VidOutVDPAU: Frame B is in use by avlib 
and so is being held for later discarding.
2019-03-25 18:37:48.571431 I? Player(0): AV Sync, audio ahead by -24 ms
2019-03-25 18:37:48.615457 I? Player(0): AV Sync, audio ahead by 66 ms
2019-03-25 18:37:48.665543 I? Player(0): AV Sync, audio ahead by 76 ms
2019-03-25 18:37:48.731440 I? Player(0): AV Sync, audio ahead by 61 ms
2019-03-25 18:37:48.811439 I? Player(0): AV Sync, audio ahead by 61 ms
2019-03-25 18:37:48.891484 I? Player(0): AV Sync, audio ahead by 62 ms
2019-03-25 18:37:48.971474 I? Player(0): AV Sync, audio ahead by -24 ms
2019-03-25 18:37:49.065890 I? Player(0): AV Sync, audio ahead by 75 ms

Introducing the next change and patching the compilation error. Causes 
many more frames to be dropped and the picture becomes visibly jerky. 
Changing to Opengl High Quality does not fix the issue,

MythTV Version : v30.0-25-gbceea69806-dirty
MythTV Branch : (HEAD detached at bceea69806)

25 18:58:06 tv mythfrontend: mythfrontend[17102]: I CoreContext 
mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 76 ms
Mar 25 18:58:06 tv mythfrontend: mythfrontend[17102]: I CoreContext 
mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 86 ms
Mar 25 18:58:06 tv mythfrontend: mythfrontend[17102]: I CoreContext 
mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 65 ms
Mar 25 18:58:06 tv mythfrontend: mythfrontend[17102]: I CoreContext 
mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 65 ms
Mar 25 18:58:06 tv mythfrontend: mythfrontend[17102]: I CoreContext 
mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 66 ms
Mar 25 18:58:06 tv mythfrontend: mythfrontend[17102]: I CoreContext 
mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 85 ms
Mar 25 18:58:06 tv mythfrontend: mythfrontend[17102]: I CoreContext 
videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame B is in 
use by avlib and so is being held for later discarding.
Mar 25 18:58:06 tv mythfrontend: mythfrontend[17102]: I CoreContext 
mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 77 ms
Mar 25 18:58:06 tv mythfrontend: mythfrontend[17102]: I CoreContext 
videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame d is in 
use by avlib and so is being held for later discarding.
Mar 25 18:58:06 tv mythfrontend: mythfrontend[17102]: I CoreContext 
mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 75 ms
Mar 25 18:58:06 tv mythfrontend: mythfrontend[17102]: I CoreContext 
videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame d is in 
use by avlib and so is being held for later discarding.
Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 86 ms
Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame g is in 
use by avlib and so is being held for later discarding.
Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 77 ms
Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame g is in 
use by avlib and so is being held for later discarding.
Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 87 ms
Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame g is in 
use by avlib and so is being held for later discarding.
Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame g is in 
use by avlib and so is being held for later discarding.
Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 68 ms
Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 65 ms
Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame F is in 
use by avlib and so is being held for later discarding.
Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 75 ms
Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame F is in 
use by avlib and so is being held for later discarding.
Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 75 ms
Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 75 ms
Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame h is in 
use by avlib and so is being held for later discarding.
Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
mythplayer.cpp:749 (AutoDeint) Player(0): 400 interlaced frames seen.
Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame h is in 
use by avlib and so is being held for later discarding.
Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame h is in 
use by avlib and so is being held for later discarding.
Mar 25 18:58:08 tv mythfrontend: mythfrontend[17102]: I CoreContext 
jitterometer.cpp:120 (RecordEndTime) Player(0): FPS: 24.93 Mean: 40106 
Std.Dev:? 8712 CPUs: 4% 4% 4% 4%
Mar 25 18:58:08 tv mythfrontend: mythfrontend[17102]: I CoreContext 
videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame a is in 
use by avlib and so is being held for later discarding.
Mar 25 18:58:08 tv mythfrontend: mythfrontend[17102]: I CoreContext 
mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 77 ms
Mar 25 18:58:08 tv mythfrontend: mythfrontend[17102]: I CoreContext 
videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame a is in 
use by avlib and so is being held for later discarding.
Mar 25 18:58:08 tv mythfrontend: mythfrontend[17102]: I CoreContext 
mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 87 ms
Mar 25 18:58:08 tv mythfrontend: mythfrontend[17102]: I CoreContext 
videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame a is in 
use by avlib and so is being held for later discarding.
Mar 25 18:58:08 tv mythfro



From mailinglist at darac.org.uk  Mon Mar 25 20:29:37 2019
From: mailinglist at darac.org.uk (Darac Marjal)
Date: Mon, 25 Mar 2019 20:29:37 +0000
Subject: [mythtv-users] frontend in english
In-Reply-To: <3a2c75b3-4452-15c5-5077-d9d99b71875e@gmail.com>
References: <8a172a98-e14d-5ce3-ed11-babe1e0c9b66@free.fr>
 <3a2c75b3-4452-15c5-5077-d9d99b71875e@gmail.com>
Message-ID: <8536dcab-0359-de56-a2b0-47816a02dc1a@darac.org.uk>


On 25/03/2019 19:22, Mike Bibbings wrote:
> On 25/03/2019 18:59, Klaus Becker wrote:
>> Hi,
>>
>> how to change frontend language from french to english?
>>
>> In Debian unstable, I found no way to do that.
>>
>> I searched on the web and in mythweb.
>>
>> I tried
>>
>> $ export LANG=; mythfrontend
>>
>> and
>>
>> $ export LANG=en_US.UTF-8; mythfrontend.
>>
>> Both work with other programms, but not with frontend or setup.
>>
>> cheers
>>
>> Klaus 
>
>
> It is done in mythfrontend Setup>Appearance>Localisation.


Just to point out, those options probably /don't/ appear in the French
localisation.

However, it's a fair point, why doesn't Myth honour the user's
localisation settings like a good application?


>
> Just tried it on my system (English > French)
>
> Mike
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190325/b6908fa8/attachment.html>

From perkins1724 at hotmail.com  Mon Mar 25 21:14:17 2019
From: perkins1724 at hotmail.com (Mark Perkins)
Date: Mon, 25 Mar 2019 21:14:17 +0000
Subject: [mythtv-users] frontend in english
In-Reply-To: <8536dcab-0359-de56-a2b0-47816a02dc1a@darac.org.uk>
References: <8a172a98-e14d-5ce3-ed11-babe1e0c9b66@free.fr>
 <3a2c75b3-4452-15c5-5077-d9d99b71875e@gmail.com>
 <8536dcab-0359-de56-a2b0-47816a02dc1a@darac.org.uk>
Message-ID: <SLXP216MB0128B6B1AE0AAF7DEB9A90C2B75E0@SLXP216MB0128.KORP216.PROD.OUTLOOK.COM>



On 26 March 2019 7:00:01 am Darac Marjal <mailinglist at darac.org.uk> wrote:


On 25/03/2019 19:22, Mike Bibbings wrote:


It is done in mythfrontend Setup>Appearance>Localisation.


Just to point out, those options probably don't appear in the French localisation.

Do you mean they will be in French not English? Or that they wont appear at all? If the latter why would that be so?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190325/ee3133ec/attachment.html>

From stuarta at squashedfrog.net  Mon Mar 25 22:08:41 2019
From: stuarta at squashedfrog.net (Stuart auchterlonie)
Date: Mon, 25 Mar 2019 22:08:41 +0000
Subject: [mythtv-users] Slave backend reboot procedure
In-Reply-To: <8495340e-38af-9f68-52e0-99b0b491108c@gmail.com>
References: <dcb28f44-7e3e-ad12-fc4a-a6a2c281494e@gmail.com>
 <0d6bf9b8-9d51-5002-b96d-aebf7945ff18@squashedfrog.net>
 <8495340e-38af-9f68-52e0-99b0b491108c@gmail.com>
Message-ID: <76e27d72-8c11-d407-c4b1-43fd243f7e47@squashedfrog.net>



On 25/03/2019 15:47, Jan Ceuleers wrote:
> On 25/03/2019 10:22, Stuart Auchterlonie wrote:
>> It could be coming online before the networking is available
>> and therefore doesn't come up properly.
>>
>> You've no said what distro you are running on, so depending on
>> which one, and whether it's systemd, you may need to
>> a) verify this is the issue
>> b) work out how to ensure the slave backend service is started
>>     after networking is online.
> Stuart,
>
> Thanks. It's Ubuntu 16.04, i.e. with systemd. Here is the service file
> on the slave backend:
>
> # cat /etc/systemd/system/mythtv-backend.service
> # JCE modified this file:
> # 1. set StartLimitInterval to 0 (was 10m)
> # 2. add dependency on videop* devices
> # 3. drop mysql.service dependency (since this is a slave backend)
>
> [Unit]
> Description=MythTV Backend
> Documentation=https://www.mythtv.org/wiki/Mythbackend
> After=network.target dev-videop2.device dev-videop3.device
> dev-videop5.device
> wants=dev-videop2.device dev-videop3.device dev-videop5.device

On my Fedora boxes there is another target `network-online` which, if it 
exists (should do)
# systemctl list-units | grep network-online

You should swap network.target to network-online.target, which waits 
longer for the network
to actually come online.


Regards
Stuart


> [Service]
> User=mythtv
> EnvironmentFile=-/etc/mythtv/additional.args
> ExecStart=/usr/bin/mythbackend --quiet --syslog local7 $ADDITIONAL_ARGS
> #StartLimitBurst=10
> StartLimitInterval=0
> Restart=on-failure
> RestartSec=1
>
> [Install]
> WantedBy=multi-user.target
>
>
> And on the master backend:
>
> # cat /etc/systemd/system/mythtv-backend.service
> # JCE modified this file:
> # 1. set StartLimitInterval to 0 (was 10m)
> # 2. add dependency on videop* devices
>
> [Unit]
> Description=MythTV Backend
> Documentation=https://www.mythtv.org/wiki/Mythbackend
> After=mysql.service network.target dev-videop0.device dev-videop1.device
> Wants=dev-videop0.device dev-videop1.device
>
> [Service]
> User=mythtv
> EnvironmentFile=-/etc/mythtv/additional.args
> ExecStart=/usr/bin/mythbackend --quiet --syslog local7 $ADDITIONAL_ARGS
> StartLimitBurst=10
> StartLimitInterval=10min
> Restart=on-failure
> RestartSec=20
>
> [Install]
> WantedBy=multi-user.target
>
>
> The /dev/videop* devices are created by udev rules (the p stands for
> persistent) based on the tuners' serial numbers:
>
> # cat /etc/udev/rules.d/10-JCE-persistent-tuner.rules
> # Create a persistent name /dev/videop0 to tuner SN 7300-00-F06D3877
> SUBSYSTEM=="video4linux", KERNEL=="video[0-9]*",
> ATTRS{manufacturer}=="Hauppauge", ATTRS{product}=="WinTV",
> ATTRS{serial}=="7300-00-F06D3877", SYMLINK+="videop0"
>
> # Create a persistent name /dev/videop1 to tuner SN 7300-00-F06C9907
> SUBSYSTEM=="video4linux", KERNEL=="video[0-9]*",
> ATTRS{manufacturer}=="Hauppauge", ATTRS{product}=="WinTV",
> ATTRS{serial}=="7300-00-F06C9907", SYMLINK+="videop1"
>
> # Create a persistent name /dev/videop2 to tuner SN 7300-00-F06EFBC0 old
> # Create a persistent name /dev/videop2 to tuner SN 7300-00-F082CB8C
> SUBSYSTEM=="video4linux", KERNEL=="video[0-9]*",
> ATTRS{manufacturer}=="Hauppauge", ATTRS{product}=="WinTV",
> ATTRS{serial}=="7300-00-F082CB8C", SYMLINK+="videop2"
>
> # Create a persistent name /dev/videop3 to tuner SN 7300-00-F07801CC
> SUBSYSTEM=="video4linux", KERNEL=="video[0-9]*",
> ATTRS{manufacturer}=="Hauppauge", ATTRS{product}=="WinTV",
> ATTRS{serial}=="7300-00-F07801CC", SYMLINK+="videop3"
>
> # Create a persistent name /dev/videop5 to tuner SN 7300-00-F0000002
> SUBSYSTEM=="video4linux", KERNEL=="video[0-9]*",
> ATTRS{manufacturer}=="Hauppauge", ATTRS{product}=="WinTV",
> ATTRS{serial}=="7300-00-F0000002", SYMLINK+="videop5"
>
>
> The creation of the device nodes is also signaled to systemd thusly:
>
> # cat /etc/udev/rules.d/99-mythbackend.rules
> #
> # Create systemd device units for capture devices
> #
> # JCE: From https://www.mythtv.org/wiki/Systemd_mythbackend_Configuration
> #
> SUBSYSTEM=="video4linux", TAG+="systemd"
> SUBSYSTEM=="dvb", TAG+="systemd"
> SUBSYSTEM=="firewire", TAG+="systemd"
>
> Thanks, Jan
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org


From stephen_agent at jsw.gen.nz  Tue Mar 26 02:47:18 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Tue, 26 Mar 2019 15:47:18 +1300
Subject: [mythtv-users] Slave backend reboot procedure
In-Reply-To: <76e27d72-8c11-d407-c4b1-43fd243f7e47@squashedfrog.net>
References: <dcb28f44-7e3e-ad12-fc4a-a6a2c281494e@gmail.com>
 <0d6bf9b8-9d51-5002-b96d-aebf7945ff18@squashedfrog.net>
 <8495340e-38af-9f68-52e0-99b0b491108c@gmail.com>
 <76e27d72-8c11-d407-c4b1-43fd243f7e47@squashedfrog.net>
Message-ID: <h11j9e5von3k6u520i46ldt6javfrbidtg@4ax.com>

On Mon, 25 Mar 2019 22:08:41 +0000, you wrote:

>
>
>On 25/03/2019 15:47, Jan Ceuleers wrote:
>> On 25/03/2019 10:22, Stuart Auchterlonie wrote:
>>> It could be coming online before the networking is available
>>> and therefore doesn't come up properly.
>>>
>>> You've no said what distro you are running on, so depending on
>>> which one, and whether it's systemd, you may need to
>>> a) verify this is the issue
>>> b) work out how to ensure the slave backend service is started
>>>     after networking is online.
>> Stuart,
>>
>> Thanks. It's Ubuntu 16.04, i.e. with systemd. Here is the service file
>> on the slave backend:
>>
>> # cat /etc/systemd/system/mythtv-backend.service
>> # JCE modified this file:
>> # 1. set StartLimitInterval to 0 (was 10m)
>> # 2. add dependency on videop* devices
>> # 3. drop mysql.service dependency (since this is a slave backend)
>>
>> [Unit]
>> Description=MythTV Backend
>> Documentation=https://www.mythtv.org/wiki/Mythbackend
>> After=network.target dev-videop2.device dev-videop3.device
>> dev-videop5.device
>> wants=dev-videop2.device dev-videop3.device dev-videop5.device
>
>On my Fedora boxes there is another target `network-online` which, if it 
>exists (should do)
># systemctl list-units | grep network-online
>
>You should swap network.target to network-online.target, which waits 
>longer for the network
>to actually come online.
>
>
>Regards
>Stuart

The network.online target is much less useful than most people seem to
think, unfortunately.  In Ubuntu, you get network.online as soon as
one network device has an IP address.  That means it comes up as soon
as localhost comes up and gets its IP address.  That is a long time
before any real network device such as an Ethernet port has come up
and got an IP address, even if the IP addresses are static.  DHCP IP
addresses take longer.  WiFi devices take even longer.  For a slave
backend, I believe it needs to wait for two things: access to the
remote database, and access to the remote master backend.  Those are
not necessarily on the same machine and accessible via the same
network path, but they usually are.

Both MySQL and MariaDB are very good at starting up and binding their
required network interfaces.  They start up as soon as localhost does,
and after that register themselves for messages from the system about
network interfaces coming up and down.  On each of those messages,
they check the interface that has changed, decide whether they are
using it, and then bind or unbind it.  This method of binding network
interfaces is the gold standard way of doing it, but unfortunately
takes quite a bit of effort by the authors, and MythTV does not do
this.  MythTV simply looks at the network interfaces available at the
time it starts up, and binds any that are available and match what it
wants to bind to.  After startup, MythTV does not check for any
changes to the interfaces, either coming up or going down.  So while
MySQL and MariaDB can start at any time and will still get all their
network interfaces, MythTV requires that it only be started after all
its network interfaces are already available - they must be up and
have all their IP addresses assigned.  So if an interface has both
IPv4 and IPv6 addresses, or has more than one IP or IPv6 address, all
the ones MythTV wants must be up.

At this point, I run out of knowledge about MythTV's requirements for
slave backends as I have never used one.  If the slave backend gets
all its network interfaces at the time it starts up, it may or may not
also require that the master backend already be up and able to respond
to it.  I hope that is not the case and the slave backend will be able
to cope with the master backend going away and coming back again, and
vice versus.

This has been an ongoing problem for MythTV for some time, but has
been aggravated by Ubuntu changing to use systemd as that change has
caused mythbackend to be started much earlier and with the default
systemd .service files for mythbackend it generally only works if only
localhost is being used.  If networked tuners or external frontends
are being used, then the systemd unit needs to be changed so that it
will only start mythbackend once all the network addresses needed by
mythbackend are up and working.  And the networked tuners also need to
be up and working, as mythbackend tests them only at startup and will
not use any tuner that does not respond to that testing.

The most recent solution to this problem is to use another systemd
unit that will wait for the necessary interfaces to be up and the
networked tuners to be available by sending a ping to the networked
tuners, and will keep doing that until it gets a reply.  Only then
will that unit signal that it is up.  The mythbackend unit is changed
to wait on this new systemd unit before it starts.  To make this work,
I wrote a small python program called "wait-until-pingable.py" which
is available from here:

http://www.jsw.gen.nz/mythtv/wait-until-pingable.py

This was discussed in this mailing list thread:

https://lists.gt.net/mythtv/users/621911

The "full-internet.service" file is also available here:

http://www.jsw.gen.nz/mythtv/full-internet.service

Put that in /etc/systemd/system and edit the "<mytuner>" to be the IP
address or host name to wait for.  Run wait-until-pingable.py with the
--help option to see what options it has.  It needs to be run as root,
so if testing it, use sudo.  In the case of slave backends, it may be
that the master backend needs to wait for the slave box to be
pingable, and the slave backend needs to wait for the master box to be
pingable.  If you need to wait for more than one network connection
(eg multiple network tuners or a network tuner and a master backend),
then create multiple "full-internet.service" files (with different
names) and have the mythbackend .service file wait on all of them.
Note that full-internet.service itself waits for
NetworkManager-wait-online.service before it runs.  So you will need
to enable that service if you have not already.  And if you are not
using Network Manager, you will need to use a different target for
starting full-internet.service.

Unfortunately, I have yet to do a version of wait-until-pingable.py
that handles IPv6, so if you are using IPv6 you will need to find
another way of doing what wait-until-pingable.py does.  Let me know if
you need IPv6, as I think I know how to make the necessary changes to
wait-until-pingable.py now, but I just need to find the time to do it.

From colonius at free.fr  Tue Mar 26 08:13:24 2019
From: colonius at free.fr (Klaus Becker)
Date: Tue, 26 Mar 2019 09:13:24 +0100
Subject: [mythtv-users] frontend in english
In-Reply-To: <8536dcab-0359-de56-a2b0-47816a02dc1a@darac.org.uk>
References: <8a172a98-e14d-5ce3-ed11-babe1e0c9b66@free.fr>
 <3a2c75b3-4452-15c5-5077-d9d99b71875e@gmail.com>
 <8536dcab-0359-de56-a2b0-47816a02dc1a@darac.org.uk>
Message-ID: <aacc19b7-7d60-683e-5b7e-36ad55c18826@free.fr>

Le 25/03/2019 ? 21:29, Darac Marjal a ?crit?:
> 
> On 25/03/2019 19:22, Mike Bibbings wrote:
>> On 25/03/2019 18:59, Klaus Becker wrote:
>>> Hi,
>>>
>>> how to change frontend language from french to english?
>>>
>>> In Debian unstable, I found no way to do that.
>>>
>>> I searched on the web and in mythweb.
>>>
>>> I tried
>>>
>>> $ export LANG=; mythfrontend
>>>
>>> and
>>>
>>> $ export LANG=en_US.UTF-8; mythfrontend.
>>>
>>> Both work with other programms, but not with frontend or setup.
>>>
>>> cheers
>>>
>>> Klaus 
>>
>>
>> It is done in mythfrontend Setup>Appearance>Localisation.


works, thank you

Klaus


> 
> 
> Just to point out, those options probably /don't/ appear in the French 
> localisation.
> 
> However, it's a fair point, why doesn't Myth honour the user's 
> localisation settings like a good application?
> 
> 
>>
>> Just tried it on my system (English > French)
>>
>> Mike

From jksjdevelop at gmail.com  Tue Mar 26 10:42:15 2019
From: jksjdevelop at gmail.com (jksjdevelop)
Date: Tue, 26 Mar 2019 10:42:15 +0000
Subject: [mythtv-users] Change v30.0-25-gbceea69806 makes playback
 visibly jumpy (March 10th)
In-Reply-To: <23227c7c-33e3-d2a6-9398-2fa37057cd77@googlemail.com>
References: <23227c7c-33e3-d2a6-9398-2fa37057cd77@googlemail.com>
Message-ID: <449491e0-93c7-704e-6e46-dccab0398785@googlemail.com>


On 25/03/2019 19:33, jksjdevelop wrote:
> The Medea is 1080i 25Hz UK DVB-S2
>
> The platform is Ubuntu 18.10 64 bit Nvidia GeForce GT 1030/PCIe/SSE2 
> Driver Version: 390.116
>
> Change AVSync2: Use frame timestamps to determine elapsed play time - 
> causes frames to be discarded.
>
> With verbose logging on playback.
>
> At the previous commit, the picture is rock solid with an even 
> scrolling news ticker, despite some frames being discarded
>
> MythTV Version : v30.0-24-g90468ec49a
> MythTV Branch : (HEAD detached at 90468ec49a)
>
> 2019-03-25 18:37:47.571475 I? Player(0): FPS:?? 25.09 Mean: 39850 
> Std.Dev:? 6823 CPUs: 6% 4% 3% 3%
> 2019-03-25 18:37:47.611354 I? Player(0): AV Sync, audio ahead by -25 ms
> 2019-03-25 18:37:47.651361 I? Player(0): AV Sync, audio ahead by -24 ms
> 2019-03-25 18:37:47.691386 I? Player(0): AV Sync, audio ahead by -24 ms
> 2019-03-25 18:37:47.731370 I? Player(0): AV Sync, audio ahead by 61 ms
> 2019-03-25 18:37:47.771335 I? Player(0): AV Sync, audio ahead by -24 ms
> 2019-03-25 18:37:47.811385 I? Player(0): AV Sync, audio ahead by -24 ms
> 2019-03-25 18:37:47.851356 I? Player(0): AV Sync, audio ahead by -25 ms
> 2019-03-25 18:37:47.945553 I? Player(0): AV Sync, audio ahead by 75 ms
> 2019-03-25 18:37:48.115719 I? Player(0): AV Sync, audio ahead by 86 ms
> 2019-03-25 18:37:48.165400 I? Player(0): AV Sync, audio ahead by 96 ms
> 2019-03-25 18:37:48.265463 I? Player(0): AV Sync, audio ahead by 75 ms
> 2019-03-25 18:37:48.315680 I? Player(0): AV Sync, audio ahead by 85 ms
> 2019-03-25 18:37:48.375455 I? Player(0): AV Sync, audio ahead by 66 ms
> 2019-03-25 18:37:48.455489 I? Player(0): AV Sync, audio ahead by 65 ms
> 2019-03-25 18:37:48.505434 I? Player(0): AV Sync, audio ahead by 75 ms
> 2019-03-25 18:37:48.515385 I? VidOutVDPAU: Frame B is in use by avlib 
> and so is being held for later discarding.
> 2019-03-25 18:37:48.535378 I? VidOutVDPAU: Frame B is in use by avlib 
> and so is being held for later discarding.
> 2019-03-25 18:37:48.535387 I? VidOutVDPAU: Frame B is in use by avlib 
> and so is being held for later discarding.
> 2019-03-25 18:37:48.551326 I? VidOutVDPAU: Frame B is in use by avlib 
> and so is being held for later discarding.
> 2019-03-25 18:37:48.551335 I? VidOutVDPAU: Frame B is in use by avlib 
> and so is being held for later discarding.
> 2019-03-25 18:37:48.571431 I? Player(0): AV Sync, audio ahead by -24 ms
> 2019-03-25 18:37:48.615457 I? Player(0): AV Sync, audio ahead by 66 ms
> 2019-03-25 18:37:48.665543 I? Player(0): AV Sync, audio ahead by 76 ms
> 2019-03-25 18:37:48.731440 I? Player(0): AV Sync, audio ahead by 61 ms
> 2019-03-25 18:37:48.811439 I? Player(0): AV Sync, audio ahead by 61 ms
> 2019-03-25 18:37:48.891484 I? Player(0): AV Sync, audio ahead by 62 ms
> 2019-03-25 18:37:48.971474 I? Player(0): AV Sync, audio ahead by -24 ms
> 2019-03-25 18:37:49.065890 I? Player(0): AV Sync, audio ahead by 75 ms
>
> Introducing the next change and patching the compilation error. Causes 
> many more frames to be dropped and the picture becomes visibly jerky. 
> Changing to Opengl High Quality does not fix the issue,
>
> MythTV Version : v30.0-25-gbceea69806-dirty
> MythTV Branch : (HEAD detached at bceea69806)
>
> 25 18:58:06 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 76 ms
> Mar 25 18:58:06 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 86 ms
> Mar 25 18:58:06 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 65 ms
> Mar 25 18:58:06 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 65 ms
> Mar 25 18:58:06 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 66 ms
> Mar 25 18:58:06 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 85 ms
> Mar 25 18:58:06 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame B is in 
> use by avlib and so is being held for later discarding.
> Mar 25 18:58:06 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 77 ms
> Mar 25 18:58:06 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame d is in 
> use by avlib and so is being held for later discarding.
> Mar 25 18:58:06 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 75 ms
> Mar 25 18:58:06 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame d is in 
> use by avlib and so is being held for later discarding.
> Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 86 ms
> Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame g is in 
> use by avlib and so is being held for later discarding.
> Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 77 ms
> Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame g is in 
> use by avlib and so is being held for later discarding.
> Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 87 ms
> Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame g is in 
> use by avlib and so is being held for later discarding.
> Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame g is in 
> use by avlib and so is being held for later discarding.
> Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 68 ms
> Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 65 ms
> Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame F is in 
> use by avlib and so is being held for later discarding.
> Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 75 ms
> Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame F is in 
> use by avlib and so is being held for later discarding.
> Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 75 ms
> Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 75 ms
> Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame h is in 
> use by avlib and so is being held for later discarding.
> Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> mythplayer.cpp:749 (AutoDeint) Player(0): 400 interlaced frames seen.
> Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame h is in 
> use by avlib and so is being held for later discarding.
> Mar 25 18:58:07 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame h is in 
> use by avlib and so is being held for later discarding.
> Mar 25 18:58:08 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> jitterometer.cpp:120 (RecordEndTime) Player(0): FPS: 24.93 Mean: 40106 
> Std.Dev:? 8712 CPUs: 4% 4% 4% 4%
> Mar 25 18:58:08 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame a is in 
> use by avlib and so is being held for later discarding.
> Mar 25 18:58:08 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 77 ms
> Mar 25 18:58:08 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame a is in 
> use by avlib and so is being held for later discarding.
> Mar 25 18:58:08 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> mythplayer.cpp:2289 (AVSync2) Player(0): AV Sync, audio ahead by 87 ms
> Mar 25 18:58:08 tv mythfrontend: mythfrontend[17102]: I CoreContext 
> videoout_vdpau.cpp:1065 (CheckFrameStates) VidOutVDPAU: Frame a is in 
> use by avlib and so is being held for later discarding.
> Mar 25 18:58:08 tv mythfro
>
>
Apologies for misleading info, the testing must have got confused.

This issue is limited to playback of 1080i 25Hz using VDPAU high quality 
and Avsync2. When using AvSync1 with VDPAU there is no visible jitter 
but frames are still being dropped, dependent on the medea. There are no 
visible issues or dropped frames with OpenGL High Quality under Avsync2.


From pb.mythtv at gmail.com  Tue Mar 26 14:37:01 2019
From: pb.mythtv at gmail.com (Peter Bennett)
Date: Tue, 26 Mar 2019 10:37:01 -0400
Subject: [mythtv-users] Change v30.0-25-gbceea69806 makes playback
 visibly jumpy (March 10th)
In-Reply-To: <23227c7c-33e3-d2a6-9398-2fa37057cd77@googlemail.com>
References: <23227c7c-33e3-d2a6-9398-2fa37057cd77@googlemail.com>
Message-ID: <afa26129-01fe-c327-e8f6-472d2b8badd2@gmail.com>



On 3/25/19 3:33 PM, jksjdevelop wrote:
> The Medea is 1080i 25Hz UK DVB-S2
>
> The platform is Ubuntu 18.10 64 bit Nvidia GeForce GT 1030/PCIe/SSE2 
> Driver Version: 390.116
>
> Change AVSync2: Use frame timestamps to determine elapsed play time - 
> causes frames to be discarded.
>
> With verbose logging on playback.
>
> At the previous commit, the picture is rock solid with an even 
> scrolling news ticker, despite some frames being discarded
>
> MythTV Version : v30.0-24-g90468ec49a
> MythTV Branch : (HEAD detached at 90468ec49a)
>
> _______________________________________________


There are several commits around that time
(most recent is listed first)
* 60cfb7c05a 2019/03/10 Peter Bennett : Fix compile error from bceea69806d
* 76ea9755b6 2019/03/10 Peter Bennett : Playback: Fix jerkiness with 
codec-deinterlaced content
* 13f5fd8307 2019/03/10 Peter Bennett : Playback: Improve "Music Choice" 
detection
* bceea69806 2019/03/10 Peter Bennett : AVSync2: Use frame timestamps to 
determine elapsed play time
* 90468ec49a 2019/03/10 Peter Bennett : Playback: AvSync2 fix fast 
forward/rewind

bceea69806 did introduce jerkiness and that was fixed the same day in a 
later commit 76ea9755b6.
Also the compile error was fixed in 60cfb7c05a.

Please try a version after 60cfb7c05a

Peter

From jan.ceuleers at gmail.com  Tue Mar 26 16:42:01 2019
From: jan.ceuleers at gmail.com (Jan Ceuleers)
Date: Tue, 26 Mar 2019 17:42:01 +0100
Subject: [mythtv-users] Slave backend reboot procedure
In-Reply-To: <h11j9e5von3k6u520i46ldt6javfrbidtg@4ax.com>
References: <dcb28f44-7e3e-ad12-fc4a-a6a2c281494e@gmail.com>
 <0d6bf9b8-9d51-5002-b96d-aebf7945ff18@squashedfrog.net>
 <8495340e-38af-9f68-52e0-99b0b491108c@gmail.com>
 <76e27d72-8c11-d407-c4b1-43fd243f7e47@squashedfrog.net>
 <h11j9e5von3k6u520i46ldt6javfrbidtg@4ax.com>
Message-ID: <07aade02-c03c-14f5-3184-10e767739248@gmail.com>

On 26/03/2019 03:47, Stephen Worthington wrote:
> The most recent solution to this problem is to use another systemd
> unit that will wait for the necessary interfaces to be up and the
> networked tuners to be available by sending a ping to the networked
> tuners, and will keep doing that until it gets a reply.

Tremendously helpful Stephen, thank you very much. Applied this to my
system and will test the next time anything needs rebooting.

From angela.schmid at wolke7.net  Tue Mar 26 17:06:25 2019
From: angela.schmid at wolke7.net (Angela)
Date: Tue, 26 Mar 2019 18:06:25 +0100
Subject: [mythtv-users] Slave backend reboot procedure
In-Reply-To: <h11j9e5von3k6u520i46ldt6javfrbidtg@4ax.com>
References: <dcb28f44-7e3e-ad12-fc4a-a6a2c281494e@gmail.com>
 <0d6bf9b8-9d51-5002-b96d-aebf7945ff18@squashedfrog.net>
 <8495340e-38af-9f68-52e0-99b0b491108c@gmail.com>
 <76e27d72-8c11-d407-c4b1-43fd243f7e47@squashedfrog.net>
 <h11j9e5von3k6u520i46ldt6javfrbidtg@4ax.com>
Message-ID: <000201d4e3f6$3f8f1a70$bead4f50$@wolke7.net>

> From: mythtv-users [mailto:mythtv-users-bounces at mythtv.org] On Behalf
> Of Stephen Worthington

> Both MySQL and MariaDB are very good at starting up and binding their
> required network interfaces.  They start up as soon as localhost does, and
> after that register themselves for messages from the system about network
> interfaces coming up and down.  On each of those messages, they check the
> interface that has changed, decide whether they are using it, and then
bind
> or unbind it.  This method of binding network interfaces is the gold
standard
> way of doing it, but unfortunately takes quite a bit of effort by the
authors,
> and MythTV does not do this.  MythTV simply looks at the network
interfaces
> available at the time it starts up, and binds any that are available and
match
> what it wants to bind to.  After startup, MythTV does not check for any
> changes to the interfaces, either coming up or going down.  So while MySQL
> and MariaDB can start at any time and will still get all their network
interfaces,
> MythTV requires that it only be started after all its network interfaces
are
> already available - they must be up and have all their IP addresses
assigned.
> So if an interface has both
> IPv4 and IPv6 addresses, or has more than one IP or IPv6 address, all the
> ones MythTV wants must be up.

There exists several options:
- use default route 0.0.0.0 or [::] to bind, these are instantly available,
use a firewall for unwanted interfaces
- using rtnetlink for network changes (programmatically)
- freebind-sockopt, to bind to interfaces which are not yet available
(programmatically)

Only mysql v8 supports multiple bind-addresses, so to bind to multiple
addresses for older versions needs to bind to 0.0.0.0.

>  If you need to wait for more than
> one network connection (eg multiple network tuners or a network tuner and
> a master backend), then create multiple "full-internet.service" files
(with
> different
> names) and have the mythbackend .service file wait on all of them.
> Note that full-internet.service itself waits for NetworkManager-wait-
> online.service before it runs.  So you will need to enable that service if
you
> have not already.  And if you are not using Network Manager, you will need
> to use a different target for starting full-internet.service.

That network-online.target works correct and you advice to enable
NetworkManager-wait-online.service, On a Ubuntu server systemd-networkd is
used.
Only one of them should be enabled:
systemctl is-enabled systemd-networkd-wait-online.service
systemctl is-enabled NetworkManager-wait-online.service

The service should have:
After=network-online.target
Wants=network-online.target

Cheers
Angela


From jksjdevelop at gmail.com  Tue Mar 26 19:32:18 2019
From: jksjdevelop at gmail.com (jksjdevelop)
Date: Tue, 26 Mar 2019 19:32:18 +0000
Subject: [mythtv-users] Change v30.0-25-gbceea69806 makes playback
 visibly jumpy (March 10th)
In-Reply-To: <afa26129-01fe-c327-e8f6-472d2b8badd2@gmail.com>
References: <23227c7c-33e3-d2a6-9398-2fa37057cd77@googlemail.com>
 <afa26129-01fe-c327-e8f6-472d2b8badd2@gmail.com>
Message-ID: <614a61a8-2058-cf9d-ee1e-2d2ae9c0d732@googlemail.com>


On 26/03/2019 14:37, Peter Bennett wrote:
>
>
> On 3/25/19 3:33 PM, jksjdevelop wrote:
>> The Medea is 1080i 25Hz UK DVB-S2
>>
>> The platform is Ubuntu 18.10 64 bit Nvidia GeForce GT 1030/PCIe/SSE2 
>> Driver Version: 390.116
>>
>> Change AVSync2: Use frame timestamps to determine elapsed play time - 
>> causes frames to be discarded.
>>
>> With verbose logging on playback.
>>
>> At the previous commit, the picture is rock solid with an even 
>> scrolling news ticker, despite some frames being discarded
>>
>> MythTV Version : v30.0-24-g90468ec49a
>> MythTV Branch : (HEAD detached at 90468ec49a)
>>
>> _______________________________________________
>
>
> There are several commits around that time
> (most recent is listed first)
> * 60cfb7c05a 2019/03/10 Peter Bennett : Fix compile error from 
> bceea69806d
> * 76ea9755b6 2019/03/10 Peter Bennett : Playback: Fix jerkiness with 
> codec-deinterlaced content
> * 13f5fd8307 2019/03/10 Peter Bennett : Playback: Improve "Music 
> Choice" detection
> * bceea69806 2019/03/10 Peter Bennett : AVSync2: Use frame timestamps 
> to determine elapsed play time
> * 90468ec49a 2019/03/10 Peter Bennett : Playback: AvSync2 fix fast 
> forward/rewind
>
> bceea69806 did introduce jerkiness and that was fixed the same day in 
> a later commit 76ea9755b6.
> Also the compile error was fixed in 60cfb7c05a.
>
> Please try a version after 60cfb7c05a
>
> Peter
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

Thanks for the response.

I have retested against the version pre change v30.0-28-g60cfb7c05a and 
the latest v30.0-38-g3af3cad3d7.

The early version works fine but the latest is jittery using Avsync2 
VDPAU High Quality. I record from both satellite and terrestrial which 
have different bit rates. The best quality picture across the two types 
is now produced by? Avsync2 OpenGL High Quality.

MythTV Version : v30.0-28-g60cfb7c05a
Playback silky smooth as shown by a news ticker using VDPAU High Quality 
for both Avsync 1 and Avsync2
572 instances per minute of Frame X is in use by avlib and so is being 
held for later discarding

-----------------------------------------------------------
MythTV Version :v30.0-38-g3af3cad3d7
Playback jerky using Avsync2 VDPAU High Quality
584 instances per minute of Frame X is in use by avlib and so is being 
held for later discarding
So presume the above message is not significant.

Playback smooth using Avsync1 VDPAU High Quality
160 instances per minute of Frame X is in use by avlib and so is being 
held for later discarding

Playback smooth using Avsync2 OpenGL High Quality
No error messages

Playback smooth using Avsync1 OpenGL High Quality
No error messages

I will clear my git local store and do a full rebuild tomorrow just to 
check.


From mbrown at wheelgroup.org  Wed Mar 27 14:46:33 2019
From: mbrown at wheelgroup.org (Mark Brown)
Date: Wed, 27 Mar 2019 10:46:33 -0400
Subject: [mythtv-users] HD playback problem w/ kernel greater than
 4.18.16-300.fc29
In-Reply-To: <aee875cd-1cf3-b7e3-1225-d32c28894f6c@gmail.com>
References: <CAHgT1OUQASjrUTVRF3rZumvzp3zmjLpog+1z5z8OU-wNF5M2aQ@mail.gmail.com>
 <168d24bf7a4.ff451883206397.6290603281727569535@zoho.com>
 <CAHgT1OXTw6RfGRa39GroB4NA9oa68zDzn+nUCh-2MvZ8k4r3pQ@mail.gmail.com>
 <aee875cd-1cf3-b7e3-1225-d32c28894f6c@gmail.com>
Message-ID: <CAHgT1OWep6Pqx-MyN=cMHnZRXDaFBMoyfn3Gtkbwk6WJjNQ1Cg@mail.gmail.com>

On Mon, Feb 11, 2019 at 4:52 PM John Pilkington <johnpilk222 at gmail.com>
wrote:

> On 11/02/2019 20:56, Mark Brown wrote:
> > Hey, sorry for the delay in responding.  I booted my fc29 front end to
> > kernel 4.20.6-200 and hd playback was still severely choppy.  I verified
> > that mythfrontend is indeed using vaapi (m > playback > playback data),
> > but playback still suffers.  Changed vid scan to progressive as you
> > suggested, and it improved playback some, but still to choppy to live
> > with.  Rebooted fc 29 front end to kernel 4.18.16-300, and all is well
> > again, all playback is smooth and works fine.  For me the problem began
> > late in fc28 when the first kernel 4.19 came on the scene.  I upgraded
> > the front end to fc29, but that again only works great when its using
> > the 4.18 series kernel.  Id be interested in what you see if you put the
> > 4.18 kernel on your fresh fc29 laptop and see if your playback is
> > improved...
> >
> > Thanks,
> > -M
>
> I tried google with 'vaapi kernel 4.20 bugzilla' and first hit was
>
>   https://bugzilla.kernel.org/show_bug.cgi?id=109051
>
> which appears to have been festering since 2005 and is now at comment
> 987.  Many comments are long.  Baytrail, probably not the N2380...
>
> John P
> ________________
>

I tried booting the frontend box to kernel 5.0.3-200, and updated to mythtv
30.0-3 today and still see very choppy HD playback.  Seems like every
kernel version greater than 4.18.16-300 and vaapi has had this problem, at
least for me.  4.18.16-300 and vaapi still works great tho...
Thx, Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190327/7856ac72/attachment.html>

From jayf0ster at roadrunner.com  Wed Mar 27 20:55:08 2019
From: jayf0ster at roadrunner.com (Jay Foster)
Date: Wed, 27 Mar 2019 13:55:08 -0700
Subject: [mythtv-users] Channel Scan Issue
Message-ID: <7aa832c7-2cf2-539f-bb26-e2a343491136@roadrunner.com>

Due to the 600 MHz spectrum repack, some of my channels have moved.  I 
rescanned the affected channels with no issues (good signal lock, etc.). 
  However, one station will not lock in live TV (for testing purposes). 
The other stations work correctly.  In live TV, it gets around 12 to 30% 
signal, which is nuts.  It is about 97% when I do the channel scan.  Any 
ideas what's going wrong?

MythTV 0.28

From stephen_agent at jsw.gen.nz  Thu Mar 28 01:19:17 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Thu, 28 Mar 2019 14:19:17 +1300
Subject: [mythtv-users] Channel Scan Issue
In-Reply-To: <7aa832c7-2cf2-539f-bb26-e2a343491136@roadrunner.com>
References: <7aa832c7-2cf2-539f-bb26-e2a343491136@roadrunner.com>
Message-ID: <s18o9e5iujg19d64tgnqgg22rkl3mt7dq5@4ax.com>

On Wed, 27 Mar 2019 13:55:08 -0700, you wrote:

>Due to the 600 MHz spectrum repack, some of my channels have moved.  I 
>rescanned the affected channels with no issues (good signal lock, etc.). 
>  However, one station will not lock in live TV (for testing purposes). 
>The other stations work correctly.  In live TV, it gets around 12 to 30% 
>signal, which is nuts.  It is about 97% when I do the channel scan.  Any 
>ideas what's going wrong?
>
>MythTV 0.28

The repack is all about putting multiple channels on to the unused
bandwidth of other channels.  Does the problem channel have any other
channels on the same frequency?  Do they work?

From jayf0ster at roadrunner.com  Thu Mar 28 15:12:39 2019
From: jayf0ster at roadrunner.com (Jay Foster)
Date: Thu, 28 Mar 2019 08:12:39 -0700
Subject: [mythtv-users] Channel Scan Issue
In-Reply-To: <s18o9e5iujg19d64tgnqgg22rkl3mt7dq5@4ax.com>
References: <7aa832c7-2cf2-539f-bb26-e2a343491136@roadrunner.com>
 <s18o9e5iujg19d64tgnqgg22rkl3mt7dq5@4ax.com>
Message-ID: <5135bcff-03c0-4cf1-10b4-c013ffb7a723@roadrunner.com>

On 3/27/2019 6:19 PM, Stephen Worthington wrote:
> On Wed, 27 Mar 2019 13:55:08 -0700, you wrote:
>
>> Due to the 600 MHz spectrum repack, some of my channels have moved.  I
>> rescanned the affected channels with no issues (good signal lock, etc.).
>>   However, one station will not lock in live TV (for testing purposes).
>> The other stations work correctly.  In live TV, it gets around 12 to 30%
>> signal, which is nuts.  It is about 97% when I do the channel scan.  Any
>> ideas what's going wrong?
>>
>> MythTV 0.28
> The repack is all about putting multiple channels on to the unused
> bandwidth of other channels.  Does the problem channel have any other
> channels on the same frequency?  Do they work?
>
No.? After some experimenting and rescanning, I came to the conclusion 
that despite me having deleted the old channels and rescanning them on 
the new transport, MythTV was still trying to tune them using the old 
transport (physical channel).? Seems that deleting channels does not 
completely delete them, or at least for this one station it did not.? I 
also discovered problems where I changed the '_' channel separator back 
to the (proper) '.' character, only to find that the changes do not 
stick for one (different) station.

I ended up deleting all channels on each of my inputs and then doing a 
whole scan on each input.? I then had to change all of the '_' channel 
separators to '.' (using mythweb) in order to get live TV to work 
(otherwise I would get a black screen).

I still need to add back in all of the channel icon files.? Doing this 
from the mythbackend-setup utility is tedious and takes most of a day.? 
Is there a script I can use to automate this?? I have about 280 channels 
over six inputs to enter the icon filenames.


From allen.p.edwards at gmail.com  Thu Mar 28 15:55:45 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Thu, 28 Mar 2019 08:55:45 -0700
Subject: [mythtv-users] Channel Scan Issue
In-Reply-To: <5135bcff-03c0-4cf1-10b4-c013ffb7a723@roadrunner.com>
References: <7aa832c7-2cf2-539f-bb26-e2a343491136@roadrunner.com>
 <s18o9e5iujg19d64tgnqgg22rkl3mt7dq5@4ax.com>
 <5135bcff-03c0-4cf1-10b4-c013ffb7a723@roadrunner.com>
Message-ID: <CAH8UtKNefcuxf-jhq0uQ93aW3bX6buKU3QB7FEz7pzqtwSwjjQ@mail.gmail.com>

On Thu, Mar 28, 2019 at 8:13 AM Jay Foster <jayf0ster at roadrunner.com> wrote:

> On 3/27/2019 6:19 PM, Stephen Worthington wrote:
> > On Wed, 27 Mar 2019 13:55:08 -0700, you wrote:
> >
> >> Due to the 600 MHz spectrum repack, some of my channels have moved.  I
> >> rescanned the affected channels with no issues (good signal lock, etc.).
> >>   However, one station will not lock in live TV (for testing purposes).
> >> The other stations work correctly.  In live TV, it gets around 12 to 30%
> >> signal, which is nuts.  It is about 97% when I do the channel scan.  Any
> >> ideas what's going wrong?
> >>
> >> MythTV 0.28
> > The repack is all about putting multiple channels on to the unused
> > bandwidth of other channels.  Does the problem channel have any other
> > channels on the same frequency?  Do they work?
> >
> No.  After some experimenting and rescanning, I came to the conclusion
> that despite me having deleted the old channels and rescanning them on
> the new transport, MythTV was still trying to tune them using the old
> transport (physical channel).  Seems that deleting channels does not
> completely delete them, or at least for this one station it did not.  I
> also discovered problems where I changed the '_' channel separator back
> to the (proper) '.' character, only to find that the changes do not
> stick for one (different) station.
>
> I ended up deleting all channels on each of my inputs and then doing a
> whole scan on each input.  I then had to change all of the '_' channel
> separators to '.' (using mythweb) in order to get live TV to work
> (otherwise I would get a black screen).
>
> I still need to add back in all of the channel icon files.  Doing this
> from the mythbackend-setup utility is tedious and takes most of a day.
> Is there a script I can use to automate this?  I have about 280 channels
> over six inputs to enter the icon filenames.
>

I am curious why I have not had a problem with the repack.  I have assumed
that Schedules Direct just dealt with it.  I noticed the other day that my
TV cannot tune to some channels but Myth is fine.  I have not rescanned my
TV as we almost never watch live TV on the TV itself. I am concerned I am
not understanding and maybe the fact that I set up Myth after the repack as
this is a relatively new install of Myth. I know there is another repack
coming so will I need to do something with Myth at that time?

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190328/a8ca98be/attachment.html>

From george.poulson at gmail.com  Thu Mar 28 16:50:55 2019
From: george.poulson at gmail.com (George Poulson)
Date: Thu, 28 Mar 2019 16:50:55 +0000
Subject: [mythtv-users] Channel Scan Issue
In-Reply-To: <CAH8UtKNefcuxf-jhq0uQ93aW3bX6buKU3QB7FEz7pzqtwSwjjQ@mail.gmail.com>
References: <7aa832c7-2cf2-539f-bb26-e2a343491136@roadrunner.com>
 <s18o9e5iujg19d64tgnqgg22rkl3mt7dq5@4ax.com>
 <5135bcff-03c0-4cf1-10b4-c013ffb7a723@roadrunner.com>
 <CAH8UtKNefcuxf-jhq0uQ93aW3bX6buKU3QB7FEz7pzqtwSwjjQ@mail.gmail.com>
Message-ID: <CACgjHiJeomTGuwn-tm2=VUbmutCFGUZOEoBrDCYrrX1KjydihA@mail.gmail.com>

On Thu, 28 Mar 2019 at 15:57, Allen Edwards <allen.p.edwards at gmail.com>
wrote:


> I am curious why I have not had a problem with the repack.
>
I have assumed that Schedules Direct just dealt with it.
>
I noticed the other day that my TV cannot tune to some channels but Myth is
> fine.
>


It would be really useful if someone could say where in the World this issue
relates to :-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190328/3f569c67/attachment.html>

From allen.p.edwards at gmail.com  Thu Mar 28 19:20:56 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Thu, 28 Mar 2019 12:20:56 -0700
Subject: [mythtv-users] Channel Scan Issue
In-Reply-To: <CACgjHiJeomTGuwn-tm2=VUbmutCFGUZOEoBrDCYrrX1KjydihA@mail.gmail.com>
References: <7aa832c7-2cf2-539f-bb26-e2a343491136@roadrunner.com>
 <s18o9e5iujg19d64tgnqgg22rkl3mt7dq5@4ax.com>
 <5135bcff-03c0-4cf1-10b4-c013ffb7a723@roadrunner.com>
 <CAH8UtKNefcuxf-jhq0uQ93aW3bX6buKU3QB7FEz7pzqtwSwjjQ@mail.gmail.com>
 <CACgjHiJeomTGuwn-tm2=VUbmutCFGUZOEoBrDCYrrX1KjydihA@mail.gmail.com>
Message-ID: <CAH8UtKOx5ah2UdhNdt_-BzWxjE-9od2gn9bj_UauGghArYkDSA@mail.gmail.com>

On Thu, Mar 28, 2019 at 9:51 AM George Poulson <george.poulson at gmail.com>
wrote:

> On Thu, 28 Mar 2019 at 15:57, Allen Edwards <allen.p.edwards at gmail.com>
> wrote:
>
>
>> I am curious why I have not had a problem with the repack.
>>
> I have assumed that Schedules Direct just dealt with it.
>>
> I noticed the other day that my TV cannot tune to some channels but Myth
>> is fine.
>>
>
>
> It would be really useful if someone could say where in the World this
> issue relates to :-)
>

I am in the United States or America.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190328/dc6f4bcb/attachment.html>

From jharbestonus at gmail.com  Thu Mar 28 19:54:48 2019
From: jharbestonus at gmail.com (Jay Harbeston)
Date: Thu, 28 Mar 2019 15:54:48 -0400
Subject: [mythtv-users] Channel Scan Issue
In-Reply-To: <CAH8UtKOx5ah2UdhNdt_-BzWxjE-9od2gn9bj_UauGghArYkDSA@mail.gmail.com>
References: <7aa832c7-2cf2-539f-bb26-e2a343491136@roadrunner.com>
 <s18o9e5iujg19d64tgnqgg22rkl3mt7dq5@4ax.com>
 <5135bcff-03c0-4cf1-10b4-c013ffb7a723@roadrunner.com>
 <CAH8UtKNefcuxf-jhq0uQ93aW3bX6buKU3QB7FEz7pzqtwSwjjQ@mail.gmail.com>
 <CACgjHiJeomTGuwn-tm2=VUbmutCFGUZOEoBrDCYrrX1KjydihA@mail.gmail.com>
 <CAH8UtKOx5ah2UdhNdt_-BzWxjE-9od2gn9bj_UauGghArYkDSA@mail.gmail.com>
Message-ID: <59174BC2-7DE2-4189-A29D-AB2ED4F15A13@gmail.com>



> On Mar 28, 2019, at 3:20 PM, Allen Edwards <allen.p.edwards at gmail.com> wrote:
> 
> 
> 
> On Thu, Mar 28, 2019 at 9:51 AM George Poulson <george.poulson at gmail.com <mailto:george.poulson at gmail.com>> wrote:
> On Thu, 28 Mar 2019 at 15:57, Allen Edwards <allen.p.edwards at gmail.com <mailto:allen.p.edwards at gmail.com>> wrote:
>  
> I am curious why I have not had a problem with the repack. 
> I have assumed that Schedules Direct just dealt with it. 
> I noticed the other day that my TV cannot tune to some channels but Myth is fine.
> 
> 
> It would be really useful if someone could say where in the World this issue relates to :-)
> 
> I am in the United States or America. 
> _______________________________________________

In that case, I imagine your problem with your tv is that it needs to rescan the channels for changes due to repack mentioned earlier in this thread

I am assuming that the same antenna is feeding your television as well as the mythtv tuners and that the signal strength to the tv and tuners is the same.

Antennaweb.org <http://antennaweb.org/> has info regarding channel repack changes.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190328/6720e517/attachment.html>

From allen.p.edwards at gmail.com  Thu Mar 28 20:20:21 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Thu, 28 Mar 2019 13:20:21 -0700
Subject: [mythtv-users] Channel Scan Issue
In-Reply-To: <59174BC2-7DE2-4189-A29D-AB2ED4F15A13@gmail.com>
References: <7aa832c7-2cf2-539f-bb26-e2a343491136@roadrunner.com>
 <s18o9e5iujg19d64tgnqgg22rkl3mt7dq5@4ax.com>
 <5135bcff-03c0-4cf1-10b4-c013ffb7a723@roadrunner.com>
 <CAH8UtKNefcuxf-jhq0uQ93aW3bX6buKU3QB7FEz7pzqtwSwjjQ@mail.gmail.com>
 <CACgjHiJeomTGuwn-tm2=VUbmutCFGUZOEoBrDCYrrX1KjydihA@mail.gmail.com>
 <CAH8UtKOx5ah2UdhNdt_-BzWxjE-9od2gn9bj_UauGghArYkDSA@mail.gmail.com>
 <59174BC2-7DE2-4189-A29D-AB2ED4F15A13@gmail.com>
Message-ID: <CAH8UtKN-8_omz+ZhJHRXPFBA7mqMU7ex9azTG5MWEBhbZESFDw@mail.gmail.com>

On Thu, Mar 28, 2019 at 12:55 PM Jay Harbeston <jharbestonus at gmail.com>
wrote:

>
>
> On Mar 28, 2019, at 3:20 PM, Allen Edwards <allen.p.edwards at gmail.com>
> wrote:
>
>
>
> On Thu, Mar 28, 2019 at 9:51 AM George Poulson <george.poulson at gmail.com>
> wrote:
>
>> On Thu, 28 Mar 2019 at 15:57, Allen Edwards <allen.p.edwards at gmail.com>
>> wrote:
>>
>>
>>> I am curious why I have not had a problem with the repack.
>>>
>> I have assumed that Schedules Direct just dealt with it.
>>>
>> I noticed the other day that my TV cannot tune to some channels but Myth
>>> is fine.
>>>
>>
>>
>> It would be really useful if someone could say where in the World this
>> issue relates to :-)
>>
>
> I am in the United States or America.
> _______________________________________________
>
>
> In that case, I imagine your problem with your tv is that it needs to
> rescan the channels for changes due to repack mentioned earlier in this
> thread
>
> I am assuming that the same antenna is feeding your television as well as
> the mythtv tuners and that the signal strength to the tv and tuners is the
> same.
>
> Antennaweb.org has info regarding channel repack changes.
>

Right.  TV not working is completely expected.  I have not done a rescan.
Both HDHR boxes and the TV are split from a line coming from a preamp in
the attic so signal is good for all.

What is unexpected is that Myth is working without a rescan.  I see two
explanations:
1)  Schedules Direct takes care of translating channels to frequencies so I
will not have to do anything going forward
2) I don't watch the channels that moved until after I did the reinstall of
Myth and just happened to notice the missing TV channels then.

In case 1 I will not have to do anything on the next repack.  If case 2
then I will need to learn how to do a rescan in Myth.

Anyone know if it is case 1 or case 2?

That link is dead but this one is very useful https://antennaweb.org/Address It
has to be https.

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190328/06887784/attachment.html>

From jharbestonus at gmail.com  Thu Mar 28 20:54:29 2019
From: jharbestonus at gmail.com (Jay Harbeston)
Date: Thu, 28 Mar 2019 16:54:29 -0400
Subject: [mythtv-users] Channel Scan Issue
In-Reply-To: <CAH8UtKN-8_omz+ZhJHRXPFBA7mqMU7ex9azTG5MWEBhbZESFDw@mail.gmail.com>
References: <7aa832c7-2cf2-539f-bb26-e2a343491136@roadrunner.com>
 <s18o9e5iujg19d64tgnqgg22rkl3mt7dq5@4ax.com>
 <5135bcff-03c0-4cf1-10b4-c013ffb7a723@roadrunner.com>
 <CAH8UtKNefcuxf-jhq0uQ93aW3bX6buKU3QB7FEz7pzqtwSwjjQ@mail.gmail.com>
 <CACgjHiJeomTGuwn-tm2=VUbmutCFGUZOEoBrDCYrrX1KjydihA@mail.gmail.com>
 <CAH8UtKOx5ah2UdhNdt_-BzWxjE-9od2gn9bj_UauGghArYkDSA@mail.gmail.com>
 <59174BC2-7DE2-4189-A29D-AB2ED4F15A13@gmail.com>
 <CAH8UtKN-8_omz+ZhJHRXPFBA7mqMU7ex9azTG5MWEBhbZESFDw@mail.gmail.com>
Message-ID: <420093D7-3400-4FD5-BAF2-CE00AB1D33FA@gmail.com>



> On Mar 28, 2019, at 4:20 PM, Allen Edwards <allen.p.edwards at gmail.com> wrote:
> 
> 
> 
> On Thu, Mar 28, 2019 at 12:55 PM Jay Harbeston <jharbestonus at gmail.com <mailto:jharbestonus at gmail.com>> wrote:
> 
> 
>> On Mar 28, 2019, at 3:20 PM, Allen Edwards <allen.p.edwards at gmail.com <mailto:allen.p.edwards at gmail.com>> wrote:
>> 
>> 
>> 
>> On Thu, Mar 28, 2019 at 9:51 AM George Poulson <george.poulson at gmail.com <mailto:george.poulson at gmail.com>> wrote:
>> On Thu, 28 Mar 2019 at 15:57, Allen Edwards <allen.p.edwards at gmail.com <mailto:allen.p.edwards at gmail.com>> wrote:
>>  
>> I am curious why I have not had a problem with the repack. 
>> I have assumed that Schedules Direct just dealt with it. 
>> I noticed the other day that my TV cannot tune to some channels but Myth is fine.
>> 
>> 
>> It would be really useful if someone could say where in the World this issue relates to :-)
>> 
>> I am in the United States or America. 
>> _______________________________________________
> 
> In that case, I imagine your problem with your tv is that it needs to rescan the channels for changes due to repack mentioned earlier in this thread
> 
> I am assuming that the same antenna is feeding your television as well as the mythtv tuners and that the signal strength to the tv and tuners is the same.
> 
> Antennaweb.org <http://antennaweb.org/> has info regarding channel repack changes.
> 
> Right.  TV not working is completely expected.  I have not done a rescan.  Both HDHR boxes and the TV are split from a line coming from a preamp in the attic so signal is good for all.
> 
> What is unexpected is that Myth is working without a rescan.  I see two explanations:
> 1)  Schedules Direct takes care of translating channels to frequencies so I will not have to do anything going forward
> 2) I don't watch the channels that moved until after I did the reinstall of Myth and just happened to notice the missing TV channels then.
> 
> In case 1 I will not have to do anything on the next repack.  If case 2 then I will need to learn how to do a rescan in Myth.
> 
> Anyone know if it is case 1 or case 2?
> 

I?m confused.. Does mythtv see the channels on their new channel number? If so, mythtv must have been installed after the channels moved. Sounds like case 2 is the solution. Solved!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190328/b10f2986/attachment.html>

From allen.p.edwards at gmail.com  Thu Mar 28 21:24:53 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Thu, 28 Mar 2019 14:24:53 -0700
Subject: [mythtv-users] Channel Scan Issue
In-Reply-To: <420093D7-3400-4FD5-BAF2-CE00AB1D33FA@gmail.com>
References: <7aa832c7-2cf2-539f-bb26-e2a343491136@roadrunner.com>
 <s18o9e5iujg19d64tgnqgg22rkl3mt7dq5@4ax.com>
 <5135bcff-03c0-4cf1-10b4-c013ffb7a723@roadrunner.com>
 <CAH8UtKNefcuxf-jhq0uQ93aW3bX6buKU3QB7FEz7pzqtwSwjjQ@mail.gmail.com>
 <CACgjHiJeomTGuwn-tm2=VUbmutCFGUZOEoBrDCYrrX1KjydihA@mail.gmail.com>
 <CAH8UtKOx5ah2UdhNdt_-BzWxjE-9od2gn9bj_UauGghArYkDSA@mail.gmail.com>
 <59174BC2-7DE2-4189-A29D-AB2ED4F15A13@gmail.com>
 <CAH8UtKN-8_omz+ZhJHRXPFBA7mqMU7ex9azTG5MWEBhbZESFDw@mail.gmail.com>
 <420093D7-3400-4FD5-BAF2-CE00AB1D33FA@gmail.com>
Message-ID: <CAH8UtKP=hQ4P1Y2P0+MJdmUFzVn5_VwsVBgSneKiUvMpUSLrLA@mail.gmail.com>

On Thu, Mar 28, 2019 at 1:54 PM Jay Harbeston <jharbestonus at gmail.com>
wrote:

>
>
> On Mar 28, 2019, at 4:20 PM, Allen Edwards <allen.p.edwards at gmail.com>
> wrote:
>
>
>
> On Thu, Mar 28, 2019 at 12:55 PM Jay Harbeston <jharbestonus at gmail.com>
> wrote:
>
>>
>>
>> On Mar 28, 2019, at 3:20 PM, Allen Edwards <allen.p.edwards at gmail.com>
>> wrote:
>>
>>
>>
>> On Thu, Mar 28, 2019 at 9:51 AM George Poulson <george.poulson at gmail.com>
>> wrote:
>>
>>> On Thu, 28 Mar 2019 at 15:57, Allen Edwards <allen.p.edwards at gmail.com>
>>> wrote:
>>>
>>>
>>>> I am curious why I have not had a problem with the repack.
>>>>
>>> I have assumed that Schedules Direct just dealt with it.
>>>>
>>> I noticed the other day that my TV cannot tune to some channels but Myth
>>>> is fine.
>>>>
>>>
>>>
>>> It would be really useful if someone could say where in the World this
>>> issue relates to :-)
>>>
>>
>> I am in the United States or America.
>> _______________________________________________
>>
>>
>> In that case, I imagine your problem with your tv is that it needs to
>> rescan the channels for changes due to repack mentioned earlier in this
>> thread
>>
>> I am assuming that the same antenna is feeding your television as well as
>> the mythtv tuners and that the signal strength to the tv and tuners is the
>> same.
>>
>> Antennaweb.org <http://antennaweb.org/> has info regarding channel
>> repack changes.
>>
>
> Right.  TV not working is completely expected.  I have not done a rescan.
> Both HDHR boxes and the TV are split from a line coming from a preamp in
> the attic so signal is good for all.
>
> What is unexpected is that Myth is working without a rescan.  I see two
> explanations:
> 1)  Schedules Direct takes care of translating channels to frequencies so
> I will not have to do anything going forward
> 2) I don't watch the channels that moved until after I did the reinstall
> of Myth and just happened to notice the missing TV channels then.
>
> In case 1 I will not have to do anything on the next repack.  If case 2
> then I will need to learn how to do a rescan in Myth.
>
> Anyone know if it is case 1 or case 2?
>
>
> I?m confused.. Does mythtv see the channels on their new channel number?
> If so, mythtv must have been installed after the channels moved. Sounds
> like case 2 is the solution. Solved!
>

OK, then on 3/13/2020 Virtual channel 2 moves from real channel 44 to 31.
Can I just go into MythWeb and change TB Channelinfo freqid for the four
sub channum's associated with channel 2 from 44 to a 31? Or do I need to do
a rescan on all the tuners?

Rescanning is a huge pain because the scan picks up the wrong station for
one of the channels and it is a pain to fake it out. I can't even remember
what I did.

I will also have another repack on 5/1/2020 for channels 7 and 11 so
whatever I need to do, I will need to do twice.

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190328/4a672e25/attachment.html>

From allen.p.edwards at gmail.com  Thu Mar 28 22:18:27 2019
From: allen.p.edwards at gmail.com (Allen Edwards)
Date: Thu, 28 Mar 2019 15:18:27 -0700
Subject: [mythtv-users] Channel Scan Issue
In-Reply-To: <CAH8UtKP=hQ4P1Y2P0+MJdmUFzVn5_VwsVBgSneKiUvMpUSLrLA@mail.gmail.com>
References: <7aa832c7-2cf2-539f-bb26-e2a343491136@roadrunner.com>
 <s18o9e5iujg19d64tgnqgg22rkl3mt7dq5@4ax.com>
 <5135bcff-03c0-4cf1-10b4-c013ffb7a723@roadrunner.com>
 <CAH8UtKNefcuxf-jhq0uQ93aW3bX6buKU3QB7FEz7pzqtwSwjjQ@mail.gmail.com>
 <CACgjHiJeomTGuwn-tm2=VUbmutCFGUZOEoBrDCYrrX1KjydihA@mail.gmail.com>
 <CAH8UtKOx5ah2UdhNdt_-BzWxjE-9od2gn9bj_UauGghArYkDSA@mail.gmail.com>
 <59174BC2-7DE2-4189-A29D-AB2ED4F15A13@gmail.com>
 <CAH8UtKN-8_omz+ZhJHRXPFBA7mqMU7ex9azTG5MWEBhbZESFDw@mail.gmail.com>
 <420093D7-3400-4FD5-BAF2-CE00AB1D33FA@gmail.com>
 <CAH8UtKP=hQ4P1Y2P0+MJdmUFzVn5_VwsVBgSneKiUvMpUSLrLA@mail.gmail.com>
Message-ID: <CAH8UtKOEgrNKaa1Dbo4rDxHeYTGU+-RSgbrGJVH+Bahdw9OidQ@mail.gmail.com>

On Thu, Mar 28, 2019 at 2:24 PM Allen Edwards <allen.p.edwards at gmail.com>
wrote:

>
>
> On Thu, Mar 28, 2019 at 1:54 PM Jay Harbeston <jharbestonus at gmail.com>
> wrote:
>
>>
>>
>> On Mar 28, 2019, at 4:20 PM, Allen Edwards <allen.p.edwards at gmail.com>
>> wrote:
>>
>>
>>
>> On Thu, Mar 28, 2019 at 12:55 PM Jay Harbeston <jharbestonus at gmail.com>
>> wrote:
>>
>>>
>>>
>>> On Mar 28, 2019, at 3:20 PM, Allen Edwards <allen.p.edwards at gmail.com>
>>> wrote:
>>>
>>>
>>>
>>> On Thu, Mar 28, 2019 at 9:51 AM George Poulson <george.poulson at gmail.com>
>>> wrote:
>>>
>>>> On Thu, 28 Mar 2019 at 15:57, Allen Edwards <allen.p.edwards at gmail.com>
>>>> wrote:
>>>>
>>>>
>>>>> I am curious why I have not had a problem with the repack.
>>>>>
>>>> I have assumed that Schedules Direct just dealt with it.
>>>>>
>>>> I noticed the other day that my TV cannot tune to some channels but
>>>>> Myth is fine.
>>>>>
>>>>
>>>>
>>>> It would be really useful if someone could say where in the World this
>>>> issue relates to :-)
>>>>
>>>
>>> I am in the United States or America.
>>> _______________________________________________
>>>
>>>
>>> In that case, I imagine your problem with your tv is that it needs to
>>> rescan the channels for changes due to repack mentioned earlier in this
>>> thread
>>>
>>> I am assuming that the same antenna is feeding your television as well
>>> as the mythtv tuners and that the signal strength to the tv and tuners is
>>> the same.
>>>
>>> Antennaweb.org <http://antennaweb.org/> has info regarding channel
>>> repack changes.
>>>
>>
>> Right.  TV not working is completely expected.  I have not done a
>> rescan.  Both HDHR boxes and the TV are split from a line coming from a
>> preamp in the attic so signal is good for all.
>>
>> What is unexpected is that Myth is working without a rescan.  I see two
>> explanations:
>> 1)  Schedules Direct takes care of translating channels to frequencies so
>> I will not have to do anything going forward
>> 2) I don't watch the channels that moved until after I did the reinstall
>> of Myth and just happened to notice the missing TV channels then.
>>
>> In case 1 I will not have to do anything on the next repack.  If case 2
>> then I will need to learn how to do a rescan in Myth.
>>
>> Anyone know if it is case 1 or case 2?
>>
>>
>> I?m confused.. Does mythtv see the channels on their new channel number?
>> If so, mythtv must have been installed after the channels moved. Sounds
>> like case 2 is the solution. Solved!
>>
>
> OK, then on 3/13/2020 Virtual channel 2 moves from real channel 44 to 31.
> Can I just go into MythWeb and change TB Channelinfo freqid for the four
> sub channum's associated with channel 2 from 44 to a 31? Or do I need to do
> a rescan on all the tuners?
>
> Rescanning is a huge pain because the scan picks up the wrong station for
> one of the channels and it is a pain to fake it out. I can't even remember
> what I did.
>
> I will also have another repack on 5/1/2020 for channels 7 and 11 so
> whatever I need to do, I will need to do twice.
>
> Allen
>

I recalled my issue with the scanning.  I can receive channel 7, KGO as
either real channel 7, which I want, or real channel 35 which I do not
want.  If I do a scan, Myth finds 7 and then overwrites it when it gets to
35.  What I think I had to do was do the scan and then do another scan and
interrupt it before it got to 35.  Not sure but I think that is what I did.

I would like to rephrase my question. When there is a repack on 3/13/2020,
do I need to do anything?  Will the information from Schedules Direct just
update everything?  If not, how do I modify the Myth database to get the
new information in. I really do not wish to do a rescan because besides the
above, I need to edit the result to eliminate the channels I don't want.
As I recall, about half the channels end up with no program information
because I have them blanked out at Schedules Direct but a rescan puts them
in the lineup anyway. My tuners are first generation HDHR boxes of which I
have 2 (4 tuners).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190328/62df4c66/attachment.html>

From jayf0ster at roadrunner.com  Thu Mar 28 22:24:27 2019
From: jayf0ster at roadrunner.com (Jay Foster)
Date: Thu, 28 Mar 2019 15:24:27 -0700
Subject: [mythtv-users] Channel Scan Issue
In-Reply-To: <CAH8UtKP=hQ4P1Y2P0+MJdmUFzVn5_VwsVBgSneKiUvMpUSLrLA@mail.gmail.com>
References: <7aa832c7-2cf2-539f-bb26-e2a343491136@roadrunner.com>
 <s18o9e5iujg19d64tgnqgg22rkl3mt7dq5@4ax.com>
 <5135bcff-03c0-4cf1-10b4-c013ffb7a723@roadrunner.com>
 <CAH8UtKNefcuxf-jhq0uQ93aW3bX6buKU3QB7FEz7pzqtwSwjjQ@mail.gmail.com>
 <CACgjHiJeomTGuwn-tm2=VUbmutCFGUZOEoBrDCYrrX1KjydihA@mail.gmail.com>
 <CAH8UtKOx5ah2UdhNdt_-BzWxjE-9od2gn9bj_UauGghArYkDSA@mail.gmail.com>
 <59174BC2-7DE2-4189-A29D-AB2ED4F15A13@gmail.com>
 <CAH8UtKN-8_omz+ZhJHRXPFBA7mqMU7ex9azTG5MWEBhbZESFDw@mail.gmail.com>
 <420093D7-3400-4FD5-BAF2-CE00AB1D33FA@gmail.com>
 <CAH8UtKP=hQ4P1Y2P0+MJdmUFzVn5_VwsVBgSneKiUvMpUSLrLA@mail.gmail.com>
Message-ID: <1dd4de4a-0562-b431-4982-d102c8df2c7f@roadrunner.com>

On 3/28/2019 2:24 PM, Allen Edwards wrote:
>
>
> OK, then on 3/13/2020 Virtual channel 2 moves from real channel 44 to 31.
> Can I just go into MythWeb and change TB Channelinfo freqid for the 
> four sub channum's associated with channel 2 from 44 to a 31? Or do I 
> need to do a rescan on all the tuners?
>
> Rescanning is a huge pain because the scan picks up the wrong station 
> for one of the channels and it is a pain to fake it out. I can't even 
> remember what I did.
>
> I will also have another repack on 5/1/2020 for channels 7 and 11 so 
> whatever I need to do, I will need to do twice.
>
> Allen
>
I do not know if that will work (I do not know how freqid is related to 
the transport).? What I did do successfully for several station 
relocations is the following:
Using the mythtvbackend-setup application, choose menu item 6.
For each input/tuner, I first selected each existing channel on the 
transport that was moving and deleted it (press d).? This is so when the 
same channels are added by scanning the new transport, they are not 
duplicates.
For each input/tuner, you may need to edit the transports (last item in 
the menu I think) and arrow down a couple of times to add new 
transport.? For the transport frequency, enter the *center* frequency 
for the new physical channel (31 in your example).? You will need to 
lookup the channel frequencies for your region (you did not specify).? 
Google/wikipedia is a good source for this (TV channel frequencies).
For each input/tuner, select scan from the menu, and choose scan 
existing transport.? For the transport, you should now be able to select 
the new channel (31) and scan.

This procedure worked fine, except the last channel I needed to 
relocate.? For some reason, MythTV continued to attempt to tune the old 
transport (physical channel) which does not work.? I ended up deleting 
everything and starting over, which I agree is a major pain.? I would 
end up with some conflicting channels, which the only way forward was to 
choose to ignore all of them.? Then I manually added the ones that I 
wanted using the process above.

Jay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190328/784ba5cc/attachment.html>

From pb.mythtv at gmail.com  Fri Mar 29 16:14:31 2019
From: pb.mythtv at gmail.com (Peter Bennett)
Date: Fri, 29 Mar 2019 12:14:31 -0400
Subject: [mythtv-users] Change v30.0-25-gbceea69806 makes playback
 visibly jumpy (March 10th)
In-Reply-To: <614a61a8-2058-cf9d-ee1e-2d2ae9c0d732@googlemail.com>
References: <23227c7c-33e3-d2a6-9398-2fa37057cd77@googlemail.com>
 <afa26129-01fe-c327-e8f6-472d2b8badd2@gmail.com>
 <614a61a8-2058-cf9d-ee1e-2d2ae9c0d732@googlemail.com>
Message-ID: <b4cc3a4c-b6fe-5f80-c519-a4072fa892e8@gmail.com>



On 3/26/19 3:32 PM, jksjdevelop wrote:
>
> On 26/03/2019 14:37, Peter Bennett wrote:
>>
>>
>> On 3/25/19 3:33 PM, jksjdevelop wrote:
>>> The Medea is 1080i 25Hz UK DVB-S2
>>>
>>> The platform is Ubuntu 18.10 64 bit Nvidia GeForce GT 1030/PCIe/SSE2 
>>> Driver Version: 390.116
>>>
>>> Change AVSync2: Use frame timestamps to determine elapsed play time 
>>> - causes frames to be discarded.
>>>
>>> With verbose logging on playback.
>>>
>>> At the previous commit, the picture is rock solid with an even 
>>> scrolling news ticker, despite some frames being discarded
>>>
>>> MythTV Version : v30.0-24-g90468ec49a
>>> MythTV Branch : (HEAD detached at 90468ec49a)
>>>
>>> _______________________________________________
>>
>>
>> There are several commits around that time
>> (most recent is listed first)
>> * 60cfb7c05a 2019/03/10 Peter Bennett : Fix compile error from 
>> bceea69806d
>> * 76ea9755b6 2019/03/10 Peter Bennett : Playback: Fix jerkiness with 
>> codec-deinterlaced content
>> * 13f5fd8307 2019/03/10 Peter Bennett : Playback: Improve "Music 
>> Choice" detection
>> * bceea69806 2019/03/10 Peter Bennett : AVSync2: Use frame timestamps 
>> to determine elapsed play time
>> * 90468ec49a 2019/03/10 Peter Bennett : Playback: AvSync2 fix fast 
>> forward/rewind
>>
>> bceea69806 did introduce jerkiness and that was fixed the same day in 
>> a later commit 76ea9755b6.
>> Also the compile error was fixed in 60cfb7c05a.
>>
>> Please try a version after 60cfb7c05a
>>
>> Peter
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>
> Thanks for the response.
>
> I have retested against the version pre change v30.0-28-g60cfb7c05a 
> and the latest v30.0-38-g3af3cad3d7.
>
> The early version works fine but the latest is jittery using Avsync2 
> VDPAU High Quality. I record from both satellite and terrestrial which 
> have different bit rates. The best quality picture across the two 
> types is now produced by? Avsync2 OpenGL High Quality.
>
> MythTV Version : v30.0-28-g60cfb7c05a
> Playback silky smooth as shown by a news ticker using VDPAU High 
> Quality for both Avsync 1 and Avsync2
> 572 instances per minute of Frame X is in use by avlib and so is being 
> held for later discarding
>
> -----------------------------------------------------------
> MythTV Version :v30.0-38-g3af3cad3d7
> Playback jerky using Avsync2 VDPAU High Quality
> 584 instances per minute of Frame X is in use by avlib and so is being 
> held for later discarding
> So presume the above message is not significant.
>
> Playback smooth using Avsync1 VDPAU High Quality
> 160 instances per minute of Frame X is in use by avlib and so is being 
> held for later discarding
>
> Playback smooth using Avsync2 OpenGL High Quality
> No error messages
>
> Playback smooth using Avsync1 OpenGL High Quality
> No error messages
>
> I will clear my git local store and do a full rebuild tomorrow just to 
> check.
>
>

I have tried various videos with the latest MythTV version and -v 
playback and do not see that "avlib in use" message at all.

I have one TV series which is a British series (Midsomer murders) from a 
USA channel (ovation). Using VDPAU it is very choppy, almost 
unwatchable. I changed the display refresh rate from 60 to 50 and that 
is a great improvement. Changing from VDPAU to OpenGL Slim is a further 
improvement.

Is your video interlaced? Double rate deinterlacers need a refresh rate 
double the frame rate.

Also check your driver version. You can get newer driver versions for 
ubuntu from the ppa:

sudo add-apt-repository ppa:graphics-drivers/ppa

Try the latest driver that is available from there.


From km at mathcs.emory.edu  Sat Mar 30 16:44:38 2019
From: km at mathcs.emory.edu (Ken Mandelberg)
Date: Sat, 30 Mar 2019 12:44:38 -0400
Subject: [mythtv-users] logfile selection
Message-ID: <b8065070-0268-cb71-127f-9155b41550ed@mathcs.emory.edu>

I get a lot of log files I don't need. I really only want the 
mythbackendlog and sometimes the mythfilldatabase. I definitely don't 
want the many mythpreviewgen files and generally not the mythcommflag or 
the mythmetadatalookup files.

How do I specify exactly which log files I want it to generate.


From stephen_agent at jsw.gen.nz  Sat Mar 30 18:00:36 2019
From: stephen_agent at jsw.gen.nz (Stephen Worthington)
Date: Sun, 31 Mar 2019 07:00:36 +1300
Subject: [mythtv-users] logfile selection
In-Reply-To: <b8065070-0268-cb71-127f-9155b41550ed@mathcs.emory.edu>
References: <b8065070-0268-cb71-127f-9155b41550ed@mathcs.emory.edu>
Message-ID: <53bv9edipirbhed6dc8mru4v0gug7de6f5@4ax.com>

On Sat, 30 Mar 2019 12:44:38 -0400, you wrote:

>I get a lot of log files I don't need. I really only want the 
>mythbackendlog and sometimes the mythfilldatabase. I definitely don't 
>want the many mythpreviewgen files and generally not the mythcommflag or 
>the mythmetadatalookup files.
>
>How do I specify exactly which log files I want it to generate.

It is generally better to keep all the log files, as that means you
have them when something goes wrong and can then use them to diagnose
the problem.  Normally, the log files will be handled via syslog
(rsyslogd) and will be rotated automatically (using logrotate), so
they will not grow too big or too many.  If your log files are not
handled that way, then I would suggest setting them up so that they
are.  The settings for controlling rsyslogd are normally in
/etc/rsyslog.d and for logrotate are in /etc/logrotate.d.  Adjust them
as required to control what is logged to what files, and how those log
files are rotated.

If you want to disable log output, then run each myth<xxx> command
with its "--help" option to find its command line logging options,
then find where it is run from and adjust the command line settings to
change the log output.

What distro are you using?

From keemllib at gmail.com  Sat Mar 30 18:25:17 2019
From: keemllib at gmail.com (Bill Meek)
Date: Sat, 30 Mar 2019 13:25:17 -0500
Subject: [mythtv-users] logfile selection
In-Reply-To: <53bv9edipirbhed6dc8mru4v0gug7de6f5@4ax.com>
References: <b8065070-0268-cb71-127f-9155b41550ed@mathcs.emory.edu>
 <53bv9edipirbhed6dc8mru4v0gug7de6f5@4ax.com>
Message-ID: <fcdf1804-9b2b-dbe6-f6f2-daf4780a878e@gmail.com>

On 3/30/19 1:00 PM, Stephen Worthington wrote:
> On Sat, 30 Mar 2019 12:44:38 -0400, you wrote:
> 
>> I get a lot of log files I don't need. I really only want the
>> mythbackendlog and sometimes the mythfilldatabase. I definitely don't
>> want the many mythpreviewgen files and generally not the mythcommflag or
>> the mythmetadatalookup files.
>>
>> How do I specify exactly which log files I want it to generate.
> 
> It is generally better to keep all the log files, as that means you
> have them when something goes wrong and can then use them to diagnose
> the problem.  Normally, the log files will be handled via syslog
> (rsyslogd) and will be rotated automatically (using logrotate), so
> they will not grow too big or too many.  If your log files are not
> handled that way, then I would suggest setting them up so that they
> are.  The settings for controlling rsyslogd are normally in
> /etc/rsyslog.d and for logrotate are in /etc/logrotate.d.  Adjust them
> as required to control what is logged to what files, and how those log
> files are rotated.
> 
> If you want to disable log output, then run each myth<xxx> command
> with its "--help" option to find its command line logging options,
> then find where it is run from and adjust the command line settings to
> change the log output.
> 
> What distro are you using?

Also note that commands like mythpreviewgen, run by the backend, inherit the
backend's logging choices.

The comment in the initial paragraph could suggest that the --logpath switch
is in play.

If that's the case, a cron.hourly script containing lines like:

   find /var/log/mythtv -type f -mmin  +15 -name "mythpreviewgen.2*.log" -delete

clears preview files > 15 minutes old (choose times/cron.xxx to your liking.)

Personally, I pipe the output of a find to a local script that archives the
detailed logs into a myth<xxx>.log file and let logrotate manage them as
Stephen suggests.

-- 
Bill

From keemllib at gmail.com  Sat Mar 30 19:33:36 2019
From: keemllib at gmail.com (Bill Meek)
Date: Sat, 30 Mar 2019 14:33:36 -0500
Subject: [mythtv-users] Channel Scan Issue
In-Reply-To: <CAH8UtKP=hQ4P1Y2P0+MJdmUFzVn5_VwsVBgSneKiUvMpUSLrLA@mail.gmail.com>
References: <7aa832c7-2cf2-539f-bb26-e2a343491136@roadrunner.com>
 <s18o9e5iujg19d64tgnqgg22rkl3mt7dq5@4ax.com>
 <5135bcff-03c0-4cf1-10b4-c013ffb7a723@roadrunner.com>
 <CAH8UtKNefcuxf-jhq0uQ93aW3bX6buKU3QB7FEz7pzqtwSwjjQ@mail.gmail.com>
 <CACgjHiJeomTGuwn-tm2=VUbmutCFGUZOEoBrDCYrrX1KjydihA@mail.gmail.com>
 <CAH8UtKOx5ah2UdhNdt_-BzWxjE-9od2gn9bj_UauGghArYkDSA@mail.gmail.com>
 <59174BC2-7DE2-4189-A29D-AB2ED4F15A13@gmail.com>
 <CAH8UtKN-8_omz+ZhJHRXPFBA7mqMU7ex9azTG5MWEBhbZESFDw@mail.gmail.com>
 <420093D7-3400-4FD5-BAF2-CE00AB1D33FA@gmail.com>
 <CAH8UtKP=hQ4P1Y2P0+MJdmUFzVn5_VwsVBgSneKiUvMpUSLrLA@mail.gmail.com>
Message-ID: <9233f714-6637-8fb2-cfb9-bed982d30dfb@gmail.com>

On 3/28/19 4:24 PM, Allen Edwards wrote:

...

> OK, then on 3/13/2020 Virtual channel 2 moves from real channel 44 to 31.
> Can I just go into MythWeb and change TB Channelinfo freqid for the four
> sub channum's associated with channel 2 from 44 to a 31? Or do I need to do
> a rescan on all the tuners?

...

Just changing the freqid won't help. Here's an example:

+--------+----------+---------------------------------+---------+--------+-----------+
| chanid | callsign | xmltvid                         | mplexid | freqid | serviceid |
+--------+----------+---------------------------------+---------+--------+-----------+
|   1321 | WFLD     | I20361.json.schedulesdirect.org |       7 | 31     |         3 |
|   1501 | WPWR     | I34662.json.schedulesdirect.org |       7 | 31     |         7 |
+--------+----------+---------------------------------+---------+--------+-----------+

WPWR had a different mplexid, freqid and serviceid. Now the mplexid and freqid are
the same. The serviceid is the unique part. [mplexid is just an index into another
MythTV table]

-- 
Bill

From hikavdh at gmail.com  Sun Mar 31 03:27:40 2019
From: hikavdh at gmail.com (Hika van den Hoven)
Date: Sun, 31 Mar 2019 05:27:40 +0200
Subject: [mythtv-users] Missing season episode numbering while it is there
Message-ID: <803193219.20190331052740@gmail.com>

Hoi All,

I have for over a year noticed that season episode numbering often
does not show on a recording. I maintain the graber I use and know it
was supplied. I see when pressing info that the data is there as a
correct SxEx statement is shown, but metadata shows zip. I see this
most often when there is no episode title. Actually then the failure
is 100%.

My present guess is that before entering graberdata a ttvdb check is
done on the episode title, which obviously will fail on absence of
such a title.

My question (I am running still 0.27) is my guess correct and then
why? If my guess is incorrect then again why?

I can and do correct the metadata, but it is extremely annoying to
have to do it while the data was there! Including that I have to
manually activate a new metadata lookup as the automatic one is based
on incomplete data while the data was there to begin with.

-- 
Tot Mails,
 Hika                          mailto:hikavdh at gmail.com
Mijn Mailadres is gewijzigd. Zie hierboven!

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens


From gary.buhrmaster at gmail.com  Sun Mar 31 04:15:38 2019
From: gary.buhrmaster at gmail.com (Gary Buhrmaster)
Date: Sun, 31 Mar 2019 04:15:38 +0000
Subject: [mythtv-users] Missing season episode numbering while it is
 there
In-Reply-To: <803193219.20190331052740@gmail.com>
References: <803193219.20190331052740@gmail.com>
Message-ID: <CAMfXtQy646HvAWJm4qYznP+W2ezgZRAQubU9rwzLpgkMGS7DGg@mail.gmail.com>

Private reply.....

On Sun, Mar 31, 2019 at 3:29 AM Hika van den Hoven <hikavdh at gmail.com> wrote:

> My question (I am running still 0.27)

At least a few changes were made post 0.27 in the
xmltv and season number parsing.  Move up to the
current release (v30) and report if that release is not
properly working with a compliant XMLTV grabber.

From jksjdevelop at gmail.com  Sun Mar 31 09:55:24 2019
From: jksjdevelop at gmail.com (John)
Date: Sun, 31 Mar 2019 10:55:24 +0100
Subject: [mythtv-users] Change v30.0-25-gbceea69806 makes playback
 visibly jumpy (March 10th)
In-Reply-To: <b4cc3a4c-b6fe-5f80-c519-a4072fa892e8@gmail.com>
References: <23227c7c-33e3-d2a6-9398-2fa37057cd77@googlemail.com>
 <afa26129-01fe-c327-e8f6-472d2b8badd2@gmail.com>
 <614a61a8-2058-cf9d-ee1e-2d2ae9c0d732@googlemail.com>
 <b4cc3a4c-b6fe-5f80-c519-a4072fa892e8@gmail.com>
Message-ID: <353937ca-f33f-d55e-d2d7-55225c1c1440@googlemail.com>

On 29/03/2019 16:14, Peter Bennett wrote:
>
>
> On 3/26/19 3:32 PM, jksjdevelop wrote:
>>
>> On 26/03/2019 14:37, Peter Bennett wrote:
>>>
>>>
>>> On 3/25/19 3:33 PM, jksjdevelop wrote:
>>>> The Medea is 1080i 25Hz UK DVB-S2
>>>>
>>>> The platform is Ubuntu 18.10 64 bit Nvidia GeForce GT 
>>>> 1030/PCIe/SSE2 Driver Version: 390.116
>>>>
>>>> Change AVSync2: Use frame timestamps to determine elapsed play time 
>>>> - causes frames to be discarded.
>>>>
>>>> With verbose logging on playback.
>>>>
>>>> At the previous commit, the picture is rock solid with an even 
>>>> scrolling news ticker, despite some frames being discarded
>>>>
>>>> MythTV Version : v30.0-24-g90468ec49a
>>>> MythTV Branch : (HEAD detached at 90468ec49a)
>>>>
>>>> _______________________________________________
>>>
>>>
>>> There are several commits around that time
>>> (most recent is listed first)
>>> * 60cfb7c05a 2019/03/10 Peter Bennett : Fix compile error from 
>>> bceea69806d
>>> * 76ea9755b6 2019/03/10 Peter Bennett : Playback: Fix jerkiness with 
>>> codec-deinterlaced content
>>> * 13f5fd8307 2019/03/10 Peter Bennett : Playback: Improve "Music 
>>> Choice" detection
>>> * bceea69806 2019/03/10 Peter Bennett : AVSync2: Use frame 
>>> timestamps to determine elapsed play time
>>> * 90468ec49a 2019/03/10 Peter Bennett : Playback: AvSync2 fix fast 
>>> forward/rewind
>>>
>>> bceea69806 did introduce jerkiness and that was fixed the same day 
>>> in a later commit 76ea9755b6.
>>> Also the compile error was fixed in 60cfb7c05a.
>>>
>>> Please try a version after 60cfb7c05a
>>>
>>> Peter
>>> _______________________________________________
>>> mythtv-users mailing list
>>> mythtv-users at mythtv.org
>>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>>> http://wiki.mythtv.org/Mailing_List_etiquette
>>> MythTV Forums: https://forum.mythtv.org
>>
>> Thanks for the response.
>>
>> I have retested against the version pre change v30.0-28-g60cfb7c05a 
>> and the latest v30.0-38-g3af3cad3d7.
>>
>> The early version works fine but the latest is jittery using Avsync2 
>> VDPAU High Quality. I record from both satellite and terrestrial 
>> which have different bit rates. The best quality picture across the 
>> two types is now produced by? Avsync2 OpenGL High Quality.
>>
>> MythTV Version : v30.0-28-g60cfb7c05a
>> Playback silky smooth as shown by a news ticker using VDPAU High 
>> Quality for both Avsync 1 and Avsync2
>> 572 instances per minute of Frame X is in use by avlib and so is 
>> being held for later discarding
>>
>> -----------------------------------------------------------
>> MythTV Version :v30.0-38-g3af3cad3d7
>> Playback jerky using Avsync2 VDPAU High Quality
>> 584 instances per minute of Frame X is in use by avlib and so is 
>> being held for later discarding
>> So presume the above message is not significant.
>>
>> Playback smooth using Avsync1 VDPAU High Quality
>> 160 instances per minute of Frame X is in use by avlib and so is 
>> being held for later discarding
>>
>> Playback smooth using Avsync2 OpenGL High Quality
>> No error messages
>>
>> Playback smooth using Avsync1 OpenGL High Quality
>> No error messages
>>
>> I will clear my git local store and do a full rebuild tomorrow just 
>> to check.
>>
>>
>
> I have tried various videos with the latest MythTV version and -v 
> playback and do not see that "avlib in use" message at all.
>
> I have one TV series which is a British series (Midsomer murders) from 
> a USA channel (ovation). Using VDPAU it is very choppy, almost 
> unwatchable. I changed the display refresh rate from 60 to 50 and that 
> is a great improvement. Changing from VDPAU to OpenGL Slim is a 
> further improvement.
>
> Is your video interlaced? Double rate deinterlacers need a refresh 
> rate double the frame rate.
>
> Also check your driver version. You can get newer driver versions for 
> ubuntu from the ppa:
>
> sudo add-apt-repository ppa:graphics-drivers/ppa
>
> Try the latest driver that is available from there.
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

Thanks. I tried the Ubuntu 19.04 beta which has Nvidia 418.56.

Playback is identical with the same messages.

Tried latest master - the same.

Tried nvdec on latest master - perfect.

So I can use nvdec or opengl high quality with no downside, so the issue 
is possibly unique to my configuration and not worth pursuing unless 
others report it.

For the record, the stream info is:-

Input #0, mpegts, from '/media/library/TV/livetv/9921_20190325155058.ts':
 ? Duration: 01:09:03.44, start: 11524.027933, bitrate: 8283 kb/s
 ? Program 1
 ??? Stream #0:0[0x1388]: Video: h264 (High) ([27][0][0][0] / 0x001B), 
yuv420p(tv, bt709, top first), 1920x1080 [SAR 1:1 DAR 16:9], 25 fps, 25 
tbr, 90k tbn, 50 tbc
 ??? Stream #0:1[0x138c](eng): Subtitle: dvb_subtitle ([6][0][0][0] / 
0x0006)
 ??? Stream #0:2[0x138b](eng,eng): Subtitle: dvb_teletext ([6][0][0][0] 
/ 0x0006)
 ??? Stream #0:3[0x1389](eng): Audio: ac3 ([129][0][0][0] / 0x0081), 
48000 Hz, stereo, fltp, 192 kb/s


From hikavdh at gmail.com  Sun Mar 31 15:26:15 2019
From: hikavdh at gmail.com (Hika van den Hoven)
Date: Sun, 31 Mar 2019 17:26:15 +0200
Subject: [mythtv-users] Missing season episode numbering while it is
 there
In-Reply-To: <CAMfXtQy646HvAWJm4qYznP+W2ezgZRAQubU9rwzLpgkMGS7DGg@mail.gmail.com>
References: <803193219.20190331052740@gmail.com> 
 <CAMfXtQy646HvAWJm4qYznP+W2ezgZRAQubU9rwzLpgkMGS7DGg@mail.gmail.com>
Message-ID: <1841690570.20190331172615@gmail.com>

Hoi Gary,

Sunday, March 31, 2019, 6:15:38 AM, you wrote:

> Private reply.....

> On Sun, Mar 31, 2019 at 3:29 AM Hika van den Hoven <hikavdh at gmail.com> wrote:

>> My question (I am running still 0.27)

> At least a few changes were made post 0.27 in the
> xmltv and season number parsing.  Move up to the
> current release (v30) and report if that release is not
> properly working with a compliant XMLTV grabber.
> _______________________________________________

It can be several month before I can find time to do the upgrade.


Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens


From rbonafied at gmail.com  Sun Mar 31 20:30:13 2019
From: rbonafied at gmail.com (Ralph)
Date: Sun, 31 Mar 2019 16:30:13 -0400
Subject: [mythtv-users] Compiling mythtv.30 - why does hdhomerun show
 disabled?
Message-ID: <11cae8b1-f773-56c3-4b17-39fdda60610d@gmail.com>

Hi,

I've always downloaded the source and compiled it on my Mageia based
system.  With Mythtv.30, I'm attempting to to the same thing I've always
done.  However, I noticed in the output of the configure step the
following: HDHomeRun support         no

I then downloaded the libhdhomerun libraries from Silicondust and put
the compiled libhdhomerun.so into /usr/local/lib I also manually copied
the hdhomerun.h to /usr/local/include but that doesn't seem to be working.

What am I missing?

This is the full output from configure:

#### MythTV CONFIGURATION ####
# Basic Settings
Qt minimum version        5.3
Qt installed version      5.9.4
Compile type              profile
Compiler cache            no
DistCC                    no
qmake                     /usr/lib64/qt5/bin/qmake
install prefix            /usr/local/mythtv.30
runtime prefix            /usr/local/mythtv.30
CPU                       x86 x86_64 (model name	: AMD Athlon(tm) II X2
250 Processor)
standalone assembly       yes
x86 assembler             yasm
MMX enabled               yes
MMXEXT enabled            yes
3DNow! enabled            yes
3DNow! extended enabled   yes
SSE enabled               yes
SSSE3 enabled             yes
AESNI enabled             yes
AVX enabled               yes
AVX2 enabled              yes
XOP enabled               yes
FMA3 enabled              yes
FMA4 enabled              yes
i686 features enabled     yes
Creating configuration files ...

# Input Support
Joystick menu             yes
lirc support              yes
libCEC device support     no [/usr/include]
Video4Linux support       yes
ivtv support              yes
HD-PVR support            yes
FireWire support          no
DVB support               yes [/usr/include]
DVB-S2 support            yes
HDHomeRun support         no
V at Box TV Gateway support  yes
Ceton support             yes
DVEO ASI support          no

# Sound Output Support
PulseAudio support        yes
OSS support               yes
ALSA support              yes
JACK support              default
libfftw3 support          yes

# Video Output Support
x11 support               yes
xnvctrl support           no
xrandr support            yes
xv support                no
VDPAU support             yes
VAAPI support             no
VAAPI2 support            no
CrystalHD support         no
OpenMAX support           no
OpenGL support            yes
OpenGL video              yes
OpenGL ThemePainter       yes
MHEG support              yes
libass subtitle support   yes

# Misc Features
Frontend                  yes
Backend                   yes
multi threaded libavcodec yes
libxml2 support           yes [/usr/include/libxml2]
libdns_sd (Bonjour)       no
libcrypto                 yes
OpenGL ES 2.0             no
bluray support            yes (system)
BD-J (Bluray java)        no
BD-J type                 j2se
systemd_notify            yes
systemd_journal           yes

# Bindings
bindings_perl             yes
bindings_python           yes
bindings_php              yes

# External Codec Options
mp3lame                   yes
xvid                      yes
x264                      yes
x265 (HEVC)               no
vpx                       no

# Compilation Options
Enforce c++11 nullptr     no

Creating libs/libmythbase/mythconfig.h and libs/libmythbase/mythconfig.mak

libs/libmythbase/mythconfig.h is unchanged
libs/libmythbase/mythconfig.mak is unchanged
Configuring libmythdvdnav...
Configuring libudfread...
Configuring libmythsoundtouch...

From keemllib at gmail.com  Sun Mar 31 20:45:53 2019
From: keemllib at gmail.com (Bill Meek)
Date: Sun, 31 Mar 2019 15:45:53 -0500
Subject: [mythtv-users] Compiling mythtv.30 - why does hdhomerun show
 disabled?
In-Reply-To: <11cae8b1-f773-56c3-4b17-39fdda60610d@gmail.com>
References: <11cae8b1-f773-56c3-4b17-39fdda60610d@gmail.com>
Message-ID: <c74b2c35-86be-337c-849e-b9df277e8ec4@gmail.com>

On 3/31/19 3:30 PM, Ralph wrote:
> I've always downloaded the source and compiled it on my Mageia based
> system.  With Mythtv.30, I'm attempting to to the same thing I've always
> done.  However, I noticed in the output of the configure step the
> following: HDHomeRun support         no

Maybe something like: libhdhomerun-dev

-- 
Bill

From rbonafied at gmail.com  Sun Mar 31 23:21:51 2019
From: rbonafied at gmail.com (Ralph)
Date: Sun, 31 Mar 2019 19:21:51 -0400
Subject: [mythtv-users] Compiling mythtv.30 - why does hdhomerun show
 disabled?
In-Reply-To: <c74b2c35-86be-337c-849e-b9df277e8ec4@gmail.com>
References: <11cae8b1-f773-56c3-4b17-39fdda60610d@gmail.com>
 <c74b2c35-86be-337c-849e-b9df277e8ec4@gmail.com>
Message-ID: <893678b7-7577-7fce-b47c-c5675cf33c83@gmail.com>

On 3/31/19 4:45 PM, Bill Meek wrote:
> On 3/31/19 3:30 PM, Ralph wrote:
>> I've always downloaded the source and compiled it on my Mageia based
>> system.? With Mythtv.30, I'm attempting to to the same thing I've always
>> done.? However, I noticed in the output of the configure step the
>> following: HDHomeRun support???????? no
> 
> Maybe something like: libhdhomerun-dev
> 
My distro (Mageia) doesn't have any packages for hdhomerun.