[mythtv-users] UPDATE 2: Re: WinTV-dualHD TV Tuner now found (1 tuner)

[A. F. Cano]

On Sun, Sep 10, 2017 at 07:03:59PM +0100, Ian Campbell wrote:
> On Sun, 2017-09-10 at 16:09 +0100, Mike Bibbings wrote:
> > > Does anyone know what Debian kernel has the 2-tuner patch/addition?
> > 
> > Don't know about any kernel supporting 2 tuner patch on Ubuntu or Debian.
> > As far as I can tell such patches are not yet in upstream.
> 
> This is relevant because Debian's policy is to only accept patches
> which are upstream. Once they are in upstream they might be backported
> if there is demand, or else one has to be patient and wait for the
> newer kernel version to filter through the various release systems.
> 
> Linux has a merge window open now, so fingers crossed for this patch
> going in for v4.14!

I hope it makes it into stretch-backports soon!

I have now finished upgrading the myth box from Debian Jessie to
Stretch.  It was a long process with some hickups.  I had to clean up
some broken packages and old dependencies with apt-get and dpkg since
aptitude became unusable at some point.  The worse part though is that
the differences between kde 4 (jessie) and kde 5 (stretch) are so big
and incompatible that I'll be trying to recover my favorite look and
feel for weeks to come.  Just about all my favorite applets are gone
and the configuration didn't carry though at all.  This computer doesn't
just display myth on the tv.

Then I installed the stretch-backports kernel (now 4.12) and upon
reboot, the tuner was recognized.  I now have 1 tuner, so I'm back
to where I was before the old OnAir Creator died.

In contrast to that, the upgrede of myth 0.27 (jessie) to 0.28
(stretch), packaged by deb-multimedia, was super easy.  Mythtv-setup
recognized the tuner and the configuration was straightforward.  Upon
first start I was asked to confirm the upgrade of schema and the
database was soon filling up with EIT data.

I have noticed one improvement/bug fix: in 0.27 I used to have to start
the frontend that displayed on the TV (hdmi connection) with

mythfrontend -w -geometry +1920+0

as Debian puts the HDMI display to the right of the primary VGA display
and the -w was necessary or the playback wouldn't start on the same
screen as the front end interface was.

This has now been fixed (in 0.28) and only 

mythfrontend -geometry +1920+0

is needed.  I still get overscan, which doesn't happen when I start
mythfronend on the primary screen.  I usually have 2 front-ends running,
one on each screen.

Xrandr reports this:

Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 8192 x 8192
VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 880mm x 490mm
   1920x1080     60.00*+
   1680x1050     59.95  
   1440x900      59.89  
   1360x768      60.02  
   1024x768      60.00  
   800x600       60.32  
   640x480       59.94  
   720x400       70.08  
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 1209mm x 680mm
   1920x1080     60.00*+  50.00    59.94    30.00    25.00    24.00    29.97    23.98  
   1920x1080i    60.00    50.00    59.94  
   1680x1050     59.88  
   1600x900      60.00  
   1280x1024     75.02    60.02  
   1440x900      59.90  
   1366x768      59.79  
   1280x800      59.91  
   1152x864      75.00  
   1280x720	 60.00    50.00    59.94  
   1024x768	 75.03    70.07    60.00  
   832x624	 74.55
   800x600       72.19    75.00    60.32  
   720x576       50.00
   720x576i      50.00  
   720x480       60.00    59.94  
   720x480i      60.00    59.94  
   640x480       75.00    72.81    66.67    60.00    59.94  
   720x400       70.08

I don't understand why I'm getting myth displayed too big on the TV.
All 4 edges are cut off, the clock and date on the bottom edge are cut off 
in half and only the top half is visible.  The same happens with video.

Is there anything I can do in myth to tell it to conform to the display
size that xrandr reports? (1920x1080)  Or do I have to set some
parameter in some X config file?  Keep in mind that this has to be
specific to the HDMI screen.  Like I said, when running on the
primary screen (VGA-1) it works like it should.

Thanks for all the help so far!

> Ian.

Augustine