From eric at lisaneric.org  Mon Feb  1 15:27:02 2016
From: eric at lisaneric.org (Eric Sharkey)
Date: Mon, 1 Feb 2016 10:27:02 -0500
Subject: [mythtv] 0.28 Release Schedule
In-Reply-To: <20160131174544.GC4433@datium.datix.lan>
References: <568D8821.8090007@squashedfrog.net>
 <569F9A1D.3090708@squashedfrog.net>
 <CAOQWjw2t4Xp+bjthm8-+TX-xkcgZCdKSuoUHcwKa7y5jd=Dpuw@mail.gmail.com>
 <1577001.GLQUtsOc9g@ace> <20160131174544.GC4433@datium.datix.lan>
Message-ID: <CAC73aR2b--aj5BQf98xVa9dOMu5hg=ELy=2hgN9XB-aHV_R-JA@mail.gmail.com>

On Sun, Jan 31, 2016 at 12:45 PM, David A. De Graaf <dad at datix.us> wrote:
> I believe that the Hauppauge PVR 150 is incapable of playing back
> while recording without a slight delay interposed.

The PVR 150 is incapable of playback at all.  The 350 can be used as a
playback device, but the 150 is record only.

I think you mean MythTV is incapable of playing back PVR 150
recordings without a slight delay.

This is strange.  I'm not currently using my 150, but when I did I
never experienced such effects.  It could be a regression in the
MythTV playback code.  Most people have moved away from SD analog
recording cards, so this sort of thing is getting less coverage.

Eric

From stuarta at squashedfrog.net  Mon Feb  1 23:57:33 2016
From: stuarta at squashedfrog.net (Stuart Auchterlonie)
Date: Mon, 1 Feb 2016 23:57:33 +0000
Subject: [mythtv] [UPDATED] 0.28 Release Schedule
In-Reply-To: <569F9A1D.3090708@squashedfrog.net>
References: <568D8821.8090007@squashedfrog.net>
 <569F9A1D.3090708@squashedfrog.net>
Message-ID: <56AFF0ED.4020203@squashedfrog.net>

On 20/01/16 14:30, Stuart Auchterlonie wrote:

> 
> So the new timelines are as follows
> 
> 1st Feb - cut a beta for 0.28, and ideally tag 0.27.6

Both done today.

Regards
Stuart Auchterlonie


> 
> 29th Feb - cut RC1
> 
> 28th Mar - release 0.28
> 
> probably be additional RC's between RC1 and release.
> 
> 
> Regards
> Stuart
> 



From mike.bibbings at gmail.com  Tue Feb  9 18:20:10 2016
From: mike.bibbings at gmail.com (Mike Bibbings)
Date: Tue, 9 Feb 2016 18:20:10 +0000
Subject: [mythtv] State of Raspberry Pi 2 build
In-Reply-To: <FFE2408A-171D-4EDE-A74F-B56AC5434643@gmail.com>
References: <56AA84B0.1090605@comcast.net>
 <820E9B7E-74BF-425B-AD0C-482EE2E23CA1@gmail.com>
 <56ABC83B.3010806@comcast.net> <56ACB0DF.7010808@gmail.com>
 <FFE2408A-171D-4EDE-A74F-B56AC5434643@gmail.com>
Message-ID: <56BA2DDA.8000108@gmail.com>

On 31/01/16 12:35, Piotr Oniszczuk wrote:
>> Wiadomo?? napisana przez Mike Bibbings <mike.bibbings at gmail.com> w dniu 30.01.2016, o godz. 13:47:
>>
>> I have just tried MiniMyth2 and it works reasonably well against my mythbackend 0.28pre with DVB-S/S2 and DVB-T/T2 tuners (I am in the UK using Freest and Freeview).
> Mike, thx for Your time spent on MM2!
>> The main issue I have is with HD (H264), both LiveTV and recorded programs in that there is some jitter, even with OSD renderer set to softblend (in openmax profile), if set to opengl2 HD is totally unusable. SD live TV  and recorded programs are ok.
> Yes. This seems to be key issue now.
> For me this is show stopper.
> Main Q for me is: is RPI2 support in MythTV actively developed?
> I see LVR a bit abandon mythtv devs team.
> This is big loose for project :-(
>> These results are comparable to my RPI2 build  on Debian Jessie (x86_64) using  Lawrence Rust mythbuild.sh system.
> This is v. good message for me.
> So now I know how to build whole OS to have working mythtv on RPI2.
>> Although under RPI2 Raspbian Jessie only xcv works for me (eglfs seg faults at startup).
> I believe it is Qt build issue on Jessie.
> I spent over week to understand how to do this correctly on ARCHLINUX.
> (BTW: On original ArchLinux ARM nothing works. FE segfaults or hangs on startup)
>> Meg (Red Button) services work, but  live TV  stutters very badly even using softblend.
> I think - again - this is OSD rendering issue.
>> The good news is that Mythbrowser (Web) and MythNews (News Feeds) do work (I believe this is due to later QT5 version than in Lawrence Rust build which uses 5.4.0).
> I believe all functions should work OK in MM2 (albeit I not tested every one of them ;-) )
>> I tried to change to Steppes theme, but download failed in Theme Chooser. Steppes (2.17) did work when I installed it manually from git. Changing theme does work in Lawrence Rust build.
> I?ll look on this. Probably interference with some of my patches?
>> I am  a bit confused about tar v bsdtar. The --numeric-owner option only seems to apply to tar, not bsdtar. The image I created was done as root on Debian Jessie (x86_64) using tar with the ?numeric-owner option.
> I?m confused here. If user unpacks archive in terminal window as root - all should be OK without any ?numeric-owner option.
> I?m doing this routinely in Fedora23 VM
> br
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-dev
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

Piotr,

Lawrence Rust is still working on improving playback on RPi2.
There are some patches to mythtv master (not on github yet) which may 
assist you, in particular patch 
0308-VO-Threaded-softblend-OSD-rendering.patch from 
http://softsystem.co.uk/download/mythtv/mythpatches-0.24.tar.bz2.

I did a quick and dirty build with just this patch and it does improve 
playback in xcb, less jerkiness when displaying information on screen 
whilst in live tv.

There are some other patches in which may be relevant, I did try 
applying all of the Lawrence Rust patches to mythtv master but building 
using mythbuild.sh failed (I think a number of the patches are not 
longer needed)

Mike



From piotr.oniszczuk at gmail.com  Tue Feb  9 21:32:37 2016
From: piotr.oniszczuk at gmail.com (Piotr Oniszczuk)
Date: Tue, 9 Feb 2016 22:32:37 +0100
Subject: [mythtv] State of Raspberry Pi 2 build
In-Reply-To: <56BA2DDA.8000108@gmail.com>
References: <56AA84B0.1090605@comcast.net>
 <820E9B7E-74BF-425B-AD0C-482EE2E23CA1@gmail.com>
 <56ABC83B.3010806@comcast.net> <56ACB0DF.7010808@gmail.com>
 <FFE2408A-171D-4EDE-A74F-B56AC5434643@gmail.com> <56BA2DDA.8000108@gmail.com>
Message-ID: <353698B8-2021-4C81-B2D0-610DBB184AC3@gmail.com>


> Wiadomo?? napisana przez Mike Bibbings <mike.bibbings at gmail.com> w dniu 09.02.2016, o godz. 19:20:
> 
>> 
> 
> Piotr,
> 
> Lawrence Rust is still working on improving playback on RPi2.
> There are some patches to mythtv master (not on github yet) which may assist you, in particular patch 0308-VO-Threaded-softblend-OSD-rendering.patch from http://softsystem.co.uk/download/mythtv/mythpatches-0.24.tar.bz2.
> 
> I did a quick and dirty build with just this patch and it does improve playback in xcb, less jerkiness when displaying information on screen whilst in live tv.
> 
> There are some other patches in which may be relevant, I did try applying all of the Lawrence Rust patches to mythtv master but building using mythbuild.sh failed (I think a number of the patches are not longer needed)
> 
> Mike
> 
> 
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-dev
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

Mike,
Thx for poiner.
I?m tracking LVR commits and also noticed threaded softblend patch. It looks interesting :-)
I?m on short holidays and beg.next week I?ll update MiniMyth2 RPI2 edition.
New ver. should have at least:
-playback defaults OOB ready for RPI2 (so no need to setup playback profile for RPI2)
-fixed reboot/shutdown
If xcb will look promissing - I?ll consider to switch default from EGLFS to xcb?.

br

   

From pgbennett at comcast.net  Tue Feb  9 21:37:57 2016
From: pgbennett at comcast.net (Peter Bennett)
Date: Tue, 9 Feb 2016 16:37:57 -0500
Subject: [mythtv] State of Raspberry Pi 2 build
In-Reply-To: <56BA2DDA.8000108@gmail.com>
References: <56AA84B0.1090605@comcast.net>
 <820E9B7E-74BF-425B-AD0C-482EE2E23CA1@gmail.com>
 <56ABC83B.3010806@comcast.net> <56ACB0DF.7010808@gmail.com>
 <FFE2408A-171D-4EDE-A74F-B56AC5434643@gmail.com> <56BA2DDA.8000108@gmail.com>
Message-ID: <56BA5C35.5040205@comcast.net>

On 02/09/2016 01:20 PM, Mike Bibbings wrote:
> On 31/01/16 12:35, Piotr Oniszczuk wrote:
>>> Wiadomo?? napisana przez Mike Bibbings <mike.bibbings at gmail.com> w
>>> dniu 30.01.2016, o godz. 13:47:
>>>
>>> I have just tried MiniMyth2 and it works reasonably well against my
>>> mythbackend 0.28pre with DVB-S/S2 and DVB-T/T2 tuners (I am in the
>>> UK using Freest and Freeview).
>> Mike, thx for Your time spent on MM2!
>>> The main issue I have is with HD (H264), both LiveTV and recorded
>>> programs in that there is some jitter, even with OSD renderer set to
>>> softblend (in openmax profile), if set to opengl2 HD is totally
>>> unusable. SD live TV  and recorded programs are ok.
>> Yes. This seems to be key issue now.
>> For me this is show stopper.
>> Main Q for me is: is RPI2 support in MythTV actively developed?
>> I see LVR a bit abandon mythtv devs team.
>> This is big loose for project :-(
>>> These results are comparable to my RPI2 build  on Debian Jessie
>>> (x86_64) using  Lawrence Rust mythbuild.sh system.
>> This is v. good message for me.
>> So now I know how to build whole OS to have working mythtv on RPI2.
>>> Although under RPI2 Raspbian Jessie only xcv works for me (eglfs seg
>>> faults at startup).
>> I believe it is Qt build issue on Jessie.
>> I spent over week to understand how to do this correctly on ARCHLINUX.
>> (BTW: On original ArchLinux ARM nothing works. FE segfaults or hangs
>> on startup)
>>> Meg (Red Button) services work, but  live TV  stutters very badly
>>> even using softblend.
>> I think - again - this is OSD rendering issue.
>>> The good news is that Mythbrowser (Web) and MythNews (News Feeds) do
>>> work (I believe this is due to later QT5 version than in Lawrence
>>> Rust build which uses 5.4.0).
>> I believe all functions should work OK in MM2 (albeit I not tested
>> every one of them ;-) )
>>> I tried to change to Steppes theme, but download failed in Theme
>>> Chooser. Steppes (2.17) did work when I installed it manually from
>>> git. Changing theme does work in Lawrence Rust build.
>> I?ll look on this. Probably interference with some of my patches?
>>> I am  a bit confused about tar v bsdtar. The --numeric-owner option
>>> only seems to apply to tar, not bsdtar. The image I created was done
>>> as root on Debian Jessie (x86_64) using tar with the ?numeric-owner
>>> option.
>> I?m confused here. If user unpacks archive in terminal window as root
>> - all should be OK without any ?numeric-owner option.
>> I?m doing this routinely in Fedora23 VM
>> br
>>
>> _______________________________________________
>> mythtv-dev mailing list
>> mythtv-dev at mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-dev
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>
> Piotr,
>
> Lawrence Rust is still working on improving playback on RPi2.
> There are some patches to mythtv master (not on github yet) which may
> assist you, in particular patch
> 0308-VO-Threaded-softblend-OSD-rendering.patch from
> http://softsystem.co.uk/download/mythtv/mythpatches-0.24.tar.bz2.
>
> I did a quick and dirty build with just this patch and it does improve
> playback in xcb, less jerkiness when displaying information on screen
> whilst in live tv.
>
> There are some other patches in which may be relevant, I did try
> applying all of the Lawrence Rust patches to mythtv master but
> building using mythbuild.sh failed (I think a number of the patches
> are not longer needed)
>
> Mike
>
>
> _______________________________________________

I am working on some RPI patches for a couple of playback issue. Those
will be ready in a couple of days. I have patches for both of these
issues and I am testing them currently.

https://code.mythtv.org/trac/ticket/12643
https://code.mythtv.org/trac/ticket/12644

I will try the softblend OSD patch you mentioned.

Peter


From pgbennett at comcast.net  Wed Feb 10 03:06:06 2016
From: pgbennett at comcast.net (Peter Bennett)
Date: Tue, 9 Feb 2016 22:06:06 -0500
Subject: [mythtv] State of Raspberry Pi 2 build
In-Reply-To: <56BA2DDA.8000108@gmail.com>
References: <56AA84B0.1090605@comcast.net>
 <820E9B7E-74BF-425B-AD0C-482EE2E23CA1@gmail.com>
 <56ABC83B.3010806@comcast.net> <56ACB0DF.7010808@gmail.com>
 <FFE2408A-171D-4EDE-A74F-B56AC5434643@gmail.com> <56BA2DDA.8000108@gmail.com>
Message-ID: <56BAA91E.3010000@comcast.net>

On 02/09/2016 01:20 PM, Mike Bibbings wrote:
> On 31/01/16 12:35, Piotr Oniszczuk wrote:
>>> Wiadomo?? napisana przez Mike Bibbings <mike.bibbings at gmail.com> w
>>> dniu 30.01.2016, o godz. 13:47:
>>>
>>> I have just tried MiniMyth2 and it works reasonably well against my
>>> mythbackend 0.28pre with DVB-S/S2 and DVB-T/T2 tuners (I am in the
>>> UK using Freest and Freeview).
>> Mike, thx for Your time spent on MM2!
>>> The main issue I have is with HD (H264), both LiveTV and recorded
>>> programs in that there is some jitter, even with OSD renderer set to
>>> softblend (in openmax profile), if set to opengl2 HD is totally
>>> unusable. SD live TV  and recorded programs are ok.
>> Yes. This seems to be key issue now.
>> For me this is show stopper.
>> Main Q for me is: is RPI2 support in MythTV actively developed?
>> I see LVR a bit abandon mythtv devs team.
>> This is big loose for project :-(
>>> These results are comparable to my RPI2 build  on Debian Jessie
>>> (x86_64) using  Lawrence Rust mythbuild.sh system.
>> This is v. good message for me.
>> So now I know how to build whole OS to have working mythtv on RPI2.
>>> Although under RPI2 Raspbian Jessie only xcv works for me (eglfs seg
>>> faults at startup).
>> I believe it is Qt build issue on Jessie.
>> I spent over week to understand how to do this correctly on ARCHLINUX.
>> (BTW: On original ArchLinux ARM nothing works. FE segfaults or hangs
>> on startup)
>>> Meg (Red Button) services work, but  live TV  stutters very badly
>>> even using softblend.
>> I think - again - this is OSD rendering issue.
>>> The good news is that Mythbrowser (Web) and MythNews (News Feeds) do
>>> work (I believe this is due to later QT5 version than in Lawrence
>>> Rust build which uses 5.4.0).
>> I believe all functions should work OK in MM2 (albeit I not tested
>> every one of them ;-) )
>>> I tried to change to Steppes theme, but download failed in Theme
>>> Chooser. Steppes (2.17) did work when I installed it manually from
>>> git. Changing theme does work in Lawrence Rust build.
>> I?ll look on this. Probably interference with some of my patches?
>>> I am  a bit confused about tar v bsdtar. The --numeric-owner option
>>> only seems to apply to tar, not bsdtar. The image I created was done
>>> as root on Debian Jessie (x86_64) using tar with the ?numeric-owner
>>> option.
>> I?m confused here. If user unpacks archive in terminal window as root
>> - all should be OK without any ?numeric-owner option.
>> I?m doing this routinely in Fedora23 VM
>> br
>>
>> _______________________________________________
>> mythtv-dev mailing list
>> mythtv-dev at mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-dev
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>
> Piotr,
>
> Lawrence Rust is still working on improving playback on RPi2.
> There are some patches to mythtv master (not on github yet) which may
> assist you, in particular patch
> 0308-VO-Threaded-softblend-OSD-rendering.patch from
> http://softsystem.co.uk/download/mythtv/mythpatches-0.24.tar.bz2.
>
> I did a quick and dirty build with just this patch and it does improve
> playback in xcb, less jerkiness when displaying information on screen
> whilst in live tv.
>
> There are some other patches in which may be relevant, I did try
> applying all of the Lawrence Rust patches to mythtv master but
> building using mythbuild.sh failed (I think a number of the patches
> are not longer needed)
>
> Mike
>
>

I tried the OSD patch and it is still jerky. I do not think that it has
helped.

You cannot install all of Lawrence's patches. Some have conflicts, some
are already installed and many are nothing to do with Raspberry PI. I
have selected a couple of the relevant ones and fixed some errors in
them for the two tickets I am working on.

I am unable to run with EGLFS. On startup it displays the theme
background and then fails with a seg fault. Then the console is locked
and I have to reboot.

Peter


From dekarl at spaetfruehstuecken.org  Wed Feb 10 07:19:21 2016
From: dekarl at spaetfruehstuecken.org (Karl Dietz)
Date: Wed, 10 Feb 2016 08:19:21 +0100
Subject: [mythtv] State of Raspberry Pi 2 build
In-Reply-To: <56BAA91E.3010000@comcast.net>
References: <56AA84B0.1090605@comcast.net>
 <820E9B7E-74BF-425B-AD0C-482EE2E23CA1@gmail.com>
 <56ABC83B.3010806@comcast.net> <56ACB0DF.7010808@gmail.com>
 <FFE2408A-171D-4EDE-A74F-B56AC5434643@gmail.com> <56BA2DDA.8000108@gmail.com>
 <56BAA91E.3010000@comcast.net>
Message-ID: <56BAE479.3020606@spaetfruehstuecken.org>

On 10.02.2016 04:06, Peter Bennett wrote:
>
> I am unable to run with EGLFS. On startup it displays the theme
> background and then fails with a seg fault. Then the console is locked
> and I have to reboot.

Did that generate a core dump? Does the backtrace hint at the root
cause?

Regards,
Karl

From pgbennett at comcast.net  Wed Feb 10 15:41:12 2016
From: pgbennett at comcast.net (Peter Bennett)
Date: Wed, 10 Feb 2016 10:41:12 -0500
Subject: [mythtv] State of Raspberry Pi 2 build
In-Reply-To: <56BAE479.3020606@spaetfruehstuecken.org>
References: <56AA84B0.1090605@comcast.net>
 <820E9B7E-74BF-425B-AD0C-482EE2E23CA1@gmail.com>
 <56ABC83B.3010806@comcast.net> <56ACB0DF.7010808@gmail.com>
 <FFE2408A-171D-4EDE-A74F-B56AC5434643@gmail.com> <56BA2DDA.8000108@gmail.com>
 <56BAA91E.3010000@comcast.net> <56BAE479.3020606@spaetfruehstuecken.org>
Message-ID: <56BB5A18.7080909@comcast.net>

On 02/10/2016 02:19 AM, Karl Dietz wrote:
> On 10.02.2016 04:06, Peter Bennett wrote:
>>
>> I am unable to run with EGLFS. On startup it displays the theme
>> background and then fails with a seg fault. Then the console is locked
>> and I have to reboot.
>
> Did that generate a core dump? Does the backtrace hint at the root
> cause?
>
> Regards,
> Karl

Hi Karl

I guess I should compile with debug turned on. I think there are several
problems with the eglfs side of things that I am concentrating on the
xcb usage, which only has 1 problem - the jerkiness with OSD. Also
MythTV normally recommends running under X so it seems that xcb is a
sensible choice.
beiklmw
Below is the back trace. Would you like me to compile with debug and try
again?

Core was generated by `/home/pi/mythtvdir/bin/mythfrontend'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x6dbb0438 in ?? () from
/home/pi/proj/mythtv-xbuild/mythtv-v0.28-pre-3529-g48ee1ab-RPI2/plugins/platforms/libqeglfs.so
(gdb) bt
#0  0x6dbb0438 in ?? () from
/home/pi/proj/mythtv-xbuild/mythtv-v0.28-pre-3529-g48ee1ab-RPI2/plugins/platforms/libqeglfs.so
#1  0x6dbb0cdc in ?? () from
/home/pi/proj/mythtv-xbuild/mythtv-v0.28-pre-3529-g48ee1ab-RPI2/plugins/platforms/libqeglfs.so
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)

The log file has several errors that seem to indicate it is still trying
to use X11, so that may be the root cause
2016-02-10 10:14:31.379553 C  MythXOpenDisplay() failed
2016-02-10 10:14:31.379750 E  ScreenSaverX11Private: Failed to open
connection to X11 server
2016-02-10 10:14:31.379779 I  ScreenSaverX11Private: DPMS is not supported.
2016-02-10 10:14:31.438553 C  MythXOpenDisplay() failed
2016-02-10 10:14:31.587646 C  MythXOpenDisplay() failed
2016-02-10 10:14:31.588286 N  Desktop video mode: 0x0 -1000000.000 Hz
2016-02-10 10:14:31.619527 C  MythXOpenDisplay() failed
2016-02-10 10:14:31.619565 E  DisplaResX: MythXOpenDisplay call failed

Peter



From mike.bibbings at gmail.com  Wed Feb 10 17:24:17 2016
From: mike.bibbings at gmail.com (Mike Bibbings)
Date: Wed, 10 Feb 2016 17:24:17 +0000
Subject: [mythtv] State of Raspberry Pi 2 build
In-Reply-To: <56BAA91E.3010000@comcast.net>
References: <56AA84B0.1090605@comcast.net>
 <820E9B7E-74BF-425B-AD0C-482EE2E23CA1@gmail.com>
 <56ABC83B.3010806@comcast.net> <56ACB0DF.7010808@gmail.com>
 <FFE2408A-171D-4EDE-A74F-B56AC5434643@gmail.com> <56BA2DDA.8000108@gmail.com>
 <56BAA91E.3010000@comcast.net>
Message-ID: <56BB7241.8090008@gmail.com>

On 10/02/16 03:06, Peter Bennett wrote:
> On 02/09/2016 01:20 PM, Mike Bibbings wrote:
>> On 31/01/16 12:35, Piotr Oniszczuk wrote:
>>>> Wiadomo?? napisana przez Mike Bibbings<mike.bibbings at gmail.com>  w
>>>> dniu 30.01.2016, o godz. 13:47:
>>>>
>>>> I have just tried MiniMyth2 and it works reasonably well against my
>>>> mythbackend 0.28pre with DVB-S/S2 and DVB-T/T2 tuners (I am in the
>>>> UK using Freest and Freeview).
>>> Mike, thx for Your time spent on MM2!
>>>> The main issue I have is with HD (H264), both LiveTV and recorded
>>>> programs in that there is some jitter, even with OSD renderer set to
>>>> softblend (in openmax profile), if set to opengl2 HD is totally
>>>> unusable. SD live TV  and recorded programs are ok.
>>> Yes. This seems to be key issue now.
>>> For me this is show stopper.
>>> Main Q for me is: is RPI2 support in MythTV actively developed?
>>> I see LVR a bit abandon mythtv devs team.
>>> This is big loose for project :-(
>>>> These results are comparable to my RPI2 build  on Debian Jessie
>>>> (x86_64) using  Lawrence Rust mythbuild.sh system.
>>> This is v. good message for me.
>>> So now I know how to build whole OS to have working mythtv on RPI2.
>>>> Although under RPI2 Raspbian Jessie only xcv works for me (eglfs seg
>>>> faults at startup).
>>> I believe it is Qt build issue on Jessie.
>>> I spent over week to understand how to do this correctly on ARCHLINUX.
>>> (BTW: On original ArchLinux ARM nothing works. FE segfaults or hangs
>>> on startup)
>>>> Meg (Red Button) services work, but  live TV  stutters very badly
>>>> even using softblend.
>>> I think - again - this is OSD rendering issue.
>>>> The good news is that Mythbrowser (Web) and MythNews (News Feeds) do
>>>> work (I believe this is due to later QT5 version than in Lawrence
>>>> Rust build which uses 5.4.0).
>>> I believe all functions should work OK in MM2 (albeit I not tested
>>> every one of them ;-) )
>>>> I tried to change to Steppes theme, but download failed in Theme
>>>> Chooser. Steppes (2.17) did work when I installed it manually from
>>>> git. Changing theme does work in Lawrence Rust build.
>>> I?ll look on this. Probably interference with some of my patches?
>>>> I am  a bit confused about tar v bsdtar. The --numeric-owner option
>>>> only seems to apply to tar, not bsdtar. The image I created was done
>>>> as root on Debian Jessie (x86_64) using tar with the ?numeric-owner
>>>> option.
>>> I?m confused here. If user unpacks archive in terminal window as root
>>> - all should be OK without any ?numeric-owner option.
>>> I?m doing this routinely in Fedora23 VM
>>> br
>>>
>>> _______________________________________________
>>> mythtv-dev mailing list
>>> mythtv-dev at mythtv.org
>>> http://lists.mythtv.org/mailman/listinfo/mythtv-dev
>>> http://wiki.mythtv.org/Mailing_List_etiquette
>>> MythTV Forums:https://forum.mythtv.org
>> Piotr,
>>
>> Lawrence Rust is still working on improving playback on RPi2.
>> There are some patches to mythtv master (not on github yet) which may
>> assist you, in particular patch
>> 0308-VO-Threaded-softblend-OSD-rendering.patch from
>> http://softsystem.co.uk/download/mythtv/mythpatches-0.24.tar.bz2.
>>
>> I did a quick and dirty build with just this patch and it does improve
>> playback in xcb, less jerkiness when displaying information on screen
>> whilst in live tv.
>>
>> There are some other patches in which may be relevant, I did try
>> applying all of the Lawrence Rust patches to mythtv master but
>> building using mythbuild.sh failed (I think a number of the patches
>> are not longer needed)
>>
>> Mike
>>
>>
> I tried the OSD patch and it is still jerky. I do not think that it has
> helped.
>
> You cannot install all of Lawrence's patches. Some have conflicts, some
> are already installed and many are nothing to do with Raspberry PI. I
> have selected a couple of the relevant ones and fixed some errors in
> them for the two tickets I am working on.
>
> I am unable to run with EGLFS. On startup it displays the theme
> background and then fails with a seg fault. Then the console is locked
> and I have to reboot.
>
> Peter
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-dev
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums:https://forum.mythtv.org
Console lockup can be fixed without reboot (info from Lawrence) if 
keyboard is attached by

  alt-sysrq-r

The patch (0308) does improve xcb performance on my system, it is still 
jittery but less so. I am in UK with HD h264. The Playback data on 
screen display goes from around 11 FPS without the patch to 16 FPS with 
the patch for Live TV, but it does have someway to go as FPS should be 
25. This is with Video 1920x1080i at 25.00fps. eglfs still seg faults on 
startup

I have also done a bit more testing on MiniMyth2.

With eglfs I can get pretty good HD h264 live TV and video playback with 
OSD render set to opengl, rather than softblend, by overclocking :
boot_delay=2
arm_freq=1000
core_freq=500
h264_freq=500
isp_freq=0
v3d_freq=500
avoid_pwm_pll=1
sdram_freq=500
over_voltage=2
force_turbo=1 (Disables throttling.)
temp_limit=80 (Temperature limit. Used for testing / fail safe.)

Playback data shows FPS around 25 (varies 23 to 27),  again for 
1920x1080i at 25.00fps

I also tried xcb (after installing X) on MiniMyth2, similar results as 
before ( the overclocking above makes little or no difference), opengl 
OSD not good - stutters, softblend -  much better, but still jitters.

For me eglfs is better than xcb on MiniMyth2, but all my TV's can be set 
to disable overscan

Mike





From gnassas at mac.com  Thu Feb 11 15:25:31 2016
From: gnassas at mac.com (George Nassas)
Date: Thu, 11 Feb 2016 10:25:31 -0500
Subject: [mythtv] [mythtv-commits] mythtv branch master updated by
 dekarl. v0.28-pre-3055-gd231e46
In-Reply-To: <20150824190041.BD12381445@alcor.mythtv.org>
References: <20150824190041.BD12381445@alcor.mythtv.org>
Message-ID: <D412129E-19FB-4D34-9615-3A440C8BBCD1@mac.com>

On Aug 24, 2015, at 3:00 PM, Git Repo Owner <noreply at mythtv.org> wrote:

> commit d231e4636908fb814a9b1d90d18c4b902e2c7f6c
> Author:    Karl Dietz <dekarl at mythtv.org> at Tue, 4 Aug 2015 22:27:01 +0200
> Committer: Karl Dietz <dekarl at mythtv.org> at Mon, 24 Aug 2015 20:59:54 +0200
> URL:       http://code.mythtv.org/cgit/mythtv/commit/?id=d231e4636908fb814a9b1d90d18c4b902e2c7f6c
> 
> Add utility function to clear all bookmarks.

Hi, will there be an api way to call this too? Services are best but an internal keybinding would help too.

If not, what is the thinking on adding such a thing. I imagine the two existing tickets which manipulate recordedmarkup would have to be merged and this clearing functionality added etc.

I?m willing to do that if someone will review and commit in a reasonable timeframe.

- George


From J.Pilk at tesco.net  Sun Feb 14 11:42:27 2016
From: J.Pilk at tesco.net (John Pilkington)
Date: Sun, 14 Feb 2016 11:42:27 +0000
Subject: [mythtv] Attempted build of v0.28-pre-3571-g4517c12 fails with
 missing fc22/x86_64/usr/share/mythtv/mythmusic folder
Message-ID: <56C06823.5040503@tesco.net>

I have a successful fc22 build of 0.28-pre-3516.  Today's attempt had a 
small trial patch but no changes here that seem likely to be 
responsible.  Has anyone else had trouble?   At present I have no I more 
info, but wonder if something in 3555 might have caused it.

John P


From piotr.oniszczuk at gmail.com  Sun Feb 14 11:55:24 2016
From: piotr.oniszczuk at gmail.com (Piotr Oniszczuk)
Date: Sun, 14 Feb 2016 12:55:24 +0100
Subject: [mythtv] State of Raspberry Pi 2 build
In-Reply-To: <56BB7241.8090008@gmail.com>
References: <56AA84B0.1090605@comcast.net>
 <820E9B7E-74BF-425B-AD0C-482EE2E23CA1@gmail.com>
 <56ABC83B.3010806@comcast.net> <56ACB0DF.7010808@gmail.com>
 <FFE2408A-171D-4EDE-A74F-B56AC5434643@gmail.com> <56BA2DDA.8000108@gmail.com>
 <56BAA91E.3010000@comcast.net> <56BB7241.8090008@gmail.com>
Message-ID: <FCBEEC45-CD13-4835-8684-6788B23F20D1@gmail.com>


> Wiadomo?? napisana przez Mike Bibbings <mike.bibbings at gmail.com> w dniu 10.02.2016, o godz. 18:24:
> 
> 
> 
> I have also done a bit more testing on MiniMyth2.
> 
> With eglfs I can get pretty good HD h264 live TV and video playback with OSD render set to opengl, rather than softblend, by overclocking :
> boot_delay=2
> arm_freq=1000
> core_freq=500
> h264_freq=500
> isp_freq=0
> v3d_freq=500
> avoid_pwm_pll=1
> sdram_freq=500
> over_voltage=2
> force_turbo=1 (Disables throttling.)
> temp_limit=80 (Temperature limit. Used for testing / fail safe.)
> 
> Playback data shows FPS around 25 (varies 23 to 27),  again for 1920x1080i at 25.00fps
> 
> I also tried xcb (after installing X) on MiniMyth2, similar results as before ( the overclocking above makes little or no difference), opengl OSD not good - stutters, softblend -  much better, but still jitters.
> 
> For me eglfs is better than xcb on MiniMyth2, but all my TV?s can be set to disable overscan

Mike,
FYI: http://www.gossamer-threads.com/lists/mythtv/users/595468#595468


From piotr.oniszczuk at gmail.com  Sun Feb 14 11:58:42 2016
From: piotr.oniszczuk at gmail.com (Piotr Oniszczuk)
Date: Sun, 14 Feb 2016 12:58:42 +0100
Subject: [mythtv] State of Raspberry Pi 2 build
In-Reply-To: <FCBEEC45-CD13-4835-8684-6788B23F20D1@gmail.com>
References: <56AA84B0.1090605@comcast.net>
 <820E9B7E-74BF-425B-AD0C-482EE2E23CA1@gmail.com>
 <56ABC83B.3010806@comcast.net> <56ACB0DF.7010808@gmail.com>
 <FFE2408A-171D-4EDE-A74F-B56AC5434643@gmail.com> <56BA2DDA.8000108@gmail.com>
 <56BAA91E.3010000@comcast.net> <56BB7241.8090008@gmail.com>
 <FCBEEC45-CD13-4835-8684-6788B23F20D1@gmail.com>
Message-ID: <F4CA4105-457C-47D5-BD46-861A7EFE876A@gmail.com>


> 
> Mike,
> FYI: http://www.gossamer-threads.com/lists/mythtv/users/595468#595468
> 
> 
oops I mean:
http://www.gossamer-threads.com/lists/mythtv/users/596180#596180
sorry. wrong paste :-)


From J.Pilk at tesco.net  Sun Feb 14 15:40:44 2016
From: J.Pilk at tesco.net (John Pilkington)
Date: Sun, 14 Feb 2016 15:40:44 +0000
Subject: [mythtv] Attempted build of v0.28-pre-3571-g4517c12 fails with
 missing fc22/x86_64/usr/share/mythtv/mythmusic folder
In-Reply-To: <56C06823.5040503@tesco.net>
References: <56C06823.5040503@tesco.net>
Message-ID: <56C09FFC.1090408@tesco.net>

On 14/02/16 11:42, John Pilkington wrote:
> I have a successful fc22 build of 0.28-pre-3516.  Today's attempt had a
> small trial patch but no changes here that seem likely to be
> responsible.  Has anyone else had trouble?   At present I have no I more
> info, but wonder if something in 3555 might have caused it.
>
> John P

An attempted rebuild of 3571 without my trial patch failed in the same 
way.  A repeated build of 3516 succeeded.

My spec files are based on those from rpmfusion;  I suspect that 
_localstatedir isn't being set, but don't see any reason for a change.



From pletchtd at gmail.com  Wed Feb 17 01:48:00 2016
From: pletchtd at gmail.com (Tim Pletcher)
Date: Tue, 16 Feb 2016 20:48:00 -0500
Subject: [mythtv] mythtranscode --fifodir removing original file
Message-ID: <CABBGYbHhpiEqLfXg6FpTZvrNc0yrv31vyAoUbCBnbagbvmvYOg@mail.gmail.com>

I am running master MythTV Version : v0.28-pre-3578-g96d4686 and attempting
to employ mythtranscode with the --fifodir option to pipe to ffmpeg for
transcoding in a temporary working directory. Everything is working as
expected however the mythtranscode operation appears to remove the original
.ts file after the operation completes. This leaves the database with an
orphan record pointing to a now missing file.  I can work around this by
making a backup of the original, performing the transcode, and then copying
the backup to replace the then missing original file but this is obviously
a clunky solution.

In the brief searching I performed, it looks like this issue with fifodir
was mentioned in the comments associated with issue #12385
<https://code.mythtv.org/trac/ticket/12385> but it isn't clear to me if the
patch addressed this aspect.

Has anyone else had this issue or is it user error?


Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-dev/attachments/20160216/f1f4e548/attachment.html>

From perkins1724 at hotmail.com  Wed Feb 17 07:17:09 2016
From: perkins1724 at hotmail.com (Mark Perkins)
Date: Wed, 17 Feb 2016 17:47:09 +1030
Subject: [mythtv] mythtranscode --fifodir removing original file
In-Reply-To: <CABBGYbHhpiEqLfXg6FpTZvrNc0yrv31vyAoUbCBnbagbvmvYOg@mail.gmail.com>
References: <CABBGYbHhpiEqLfXg6FpTZvrNc0yrv31vyAoUbCBnbagbvmvYOg@mail.gmail.com>
Message-ID: <BLU404-EAS237C63312A714006EC995A9B7AE0@phx.gbl>





> On 17 Feb 2016, at 12:18 pm, Tim Pletcher <pletchtd at gmail.com> wrote:
> 
> I am running master MythTV Version : v0.28-pre-3578-g96d4686 and attempting to employ mythtranscode with the --fifodir option to pipe to ffmpeg for transcoding in a temporary working directory. Everything is working as expected however the mythtranscode operation appears to remove the original .ts file after the operation completes. This leaves the database with an orphan record pointing to a now missing file.  I can work around this by making a backup of the original, performing the transcode, and then copying the backup to replace the then missing original file but this is obviously a clunky solution.
> 
> In the brief searching I performed, it looks like this issue with fifodir was mentioned in the comments associated with issue #12385 but it isn't clear to me if the patch addressed this aspect.  
> 
> Has anyone else had this issue or is it user error?
> 
> 
> Tim
> 
> 
> 
> _______________________________________________

Yes I noted this behavior about 4 months ago when I had an aborted attempt at moving to master. Although I had a number of issues at the time (hence 'aborted') and assumed it was user error. I had intended to go back and verify but have not done so yet and there are other things I want to test first.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-dev/attachments/20160217/cc75f749/attachment.html>
-------------- next part --------------
_______________________________________________
mythtv-dev mailing list
mythtv-dev at mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

From piotr.oniszczuk at gmail.com  Wed Feb 17 10:14:26 2016
From: piotr.oniszczuk at gmail.com (Piotr Oniszczuk)
Date: Wed, 17 Feb 2016 11:14:26 +0100
Subject: [mythtv] Upgrading to Qt5.5.1 - is it safe?
Message-ID: <CALxQnOL2yLitUnxVfpa0RQEpmX1hdxPTfrGDgPzjQTN0M1a0BA@mail.gmail.com>

Dears,

I have fairly stable BE/FE - both on Qt5.4.1.

Looking on root cause of #12558 it looks 5.4.1 isn't best choice.

If I want to move away from 5.4.1 - what You advice: 5.4.2 or 5.5.1?

I prefer 5.5.1.

Do we know any problems/expected incompatibilities by using 5.5.1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-dev/attachments/20160217/412220d2/attachment.html>

From J.Pilk at tesco.net  Wed Feb 17 14:19:47 2016
From: J.Pilk at tesco.net (John Pilkington)
Date: Wed, 17 Feb 2016 14:19:47 +0000
Subject: [mythtv] Attempted build of v0.28-pre-3571-g4517c12 fails with
 missing fc22/x86_64/usr/share/mythtv/mythmusic folder
In-Reply-To: <56C09FFC.1090408@tesco.net>
References: <56C06823.5040503@tesco.net> <56C09FFC.1090408@tesco.net>
Message-ID: <56C48183.20704@tesco.net>

On 14/02/16 15:40, John Pilkington wrote:
> On 14/02/16 11:42, John Pilkington wrote:
>> I have a successful fc22 build of 0.28-pre-3516.  Today's attempt had a
>> small trial patch but no changes here that seem likely to be
>> responsible.  Has anyone else had trouble?   At present I have no I more
>> info, but wonder if something in 3555 might have caused it.
>>
>> John P
>
> An attempted rebuild of 3571 without my trial patch failed in the same
> way.  A repeated build of 3516 succeeded.
>
> My spec files are based on those from rpmfusion;  I suspect that
> _localstatedir isn't being set, but don't see any reason for a change.
>

The failure is in the package-building stage.  A build of 3579 --without 
most plugins worked, as did one --without just mythmusic.  Looks as if I 
need to update the mythmusic %files stanza in the specfile.

Each run of rpmbuild --quiet yields > 20kB of compilation 'warnings', 
many obviously of long standing although presumably not critical.  I 
find that rather surprising.

It also takes nearly an hour :-(



From J.Pilk at tesco.net  Fri Feb 19 09:43:28 2016
From: J.Pilk at tesco.net (John Pilkington)
Date: Fri, 19 Feb 2016 09:43:28 +0000
Subject: [mythtv] Attempted build of v0.28-pre-3571-g4517c12 fails with
 missing fc22/x86_64/usr/share/mythtv/mythmusic folder
In-Reply-To: <56C48183.20704@tesco.net>
References: <56C06823.5040503@tesco.net> <56C09FFC.1090408@tesco.net>
 <56C48183.20704@tesco.net>
Message-ID: <56C6E3C0.2070705@tesco.net>

On 17/02/16 14:19, John Pilkington wrote:
> On 14/02/16 15:40, John Pilkington wrote:
>> On 14/02/16 11:42, John Pilkington wrote:
>>> I have a successful fc22 build of 0.28-pre-3516.  Today's attempt had a
>>> small trial patch but no changes here that seem likely to be
>>> responsible.  Has anyone else had trouble?   At present I have no I more
>>> info, but wonder if something in 3555 might have caused it.
>>>
>>> John P
>>
>> An attempted rebuild of 3571 without my trial patch failed in the same
>> way.  A repeated build of 3516 succeeded.
>>
>> My spec files are based on those from rpmfusion;  I suspect that
>> _localstatedir isn't being set, but don't see any reason for a change.
>>
>
> The failure is in the package-building stage.  A build of 3579 --without
> most plugins worked, as did one --without just mythmusic.  Looks as if I
> need to update the mythmusic %files stanza in the specfile.
>
> Each run of rpmbuild --quiet yields > 20kB of compilation 'warnings',
> many obviously of long standing although presumably not critical.  I
> find that rather surprising.
>
> It also takes nearly an hour :-(
>

It's working again, in both fc22 and SL7.2, after adding the second line 
below:
     mkdir -p %{buildroot}%{_localstatedir}/lib/mythmusic
     mkdir -p %{buildroot}%{_datadir}/mythtv/mythmusic

I should probably post the entire 0.28-compatible specfile somewhere. 
In a Ticket?







From hobbes1069 at gmail.com  Fri Feb 19 17:34:42 2016
From: hobbes1069 at gmail.com (Richard Shaw)
Date: Fri, 19 Feb 2016 11:34:42 -0600
Subject: [mythtv] mythbackend: Suppress timestamp in log?
Message-ID: <CAN3TeO12e27uAemzOUwc-ipL5LXYWz973EuhYKO8_--4fEaOsQ@mail.gmail.com>

Since I log to the journal I already get a timestamp, getting two takes up
lots of columns and makes the log much more difficult to read.

Do you automatically get a timestamp when logging to syslog? Could
supression of the timestamp be added to the --syslog command line option?

Thanks,
Richard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-dev/attachments/20160219/977faab9/attachment.html>

From keemllib at gmail.com  Fri Feb 19 18:15:27 2016
From: keemllib at gmail.com (Bill Meek)
Date: Fri, 19 Feb 2016 12:15:27 -0600
Subject: [mythtv] mythbackend: Suppress timestamp in log?
In-Reply-To: <CAN3TeO12e27uAemzOUwc-ipL5LXYWz973EuhYKO8_--4fEaOsQ@mail.gmail.com>
References: <CAN3TeO12e27uAemzOUwc-ipL5LXYWz973EuhYKO8_--4fEaOsQ@mail.gmail.com>
Message-ID: <56C75BBF.9030203@gmail.com>

On 02/19/2016 11:34 AM, Richard Shaw wrote:
> Since I log to the journal I already get a timestamp, getting two takes up
> lots of columns and makes the log much more difficult to read.
>
> Do you automatically get a timestamp when logging to syslog? Could
> supression of the timestamp be added to the --syslog command line option?

I did two things for journal-only logging:

In the .unit file, add --quiet to the backend startup ExecStart line (as
opposed to redirecting the stdout/err to /dev/null [why send something to
the console only to throw it away].)

In /etc/systemd/journald.conf, I uncommented and set to no the following:
ForwardToSyslog=no. Not sure if systemd-journald was the only thing restarted,
or if I just did a warm boot to be sure.

The remaining issue is duplicate program names (mythbackend[2090]: mythbackend[2090]:)
and I haven't looked into that one.

This is Ubuntu 15.10 and 0.28-beta FYI.

-- 
Bill

From cschieli at gmail.com  Fri Feb 19 18:45:14 2016
From: cschieli at gmail.com (=?UTF-8?Q?C=C3=A9dric_Schieli?=)
Date: Fri, 19 Feb 2016 19:45:14 +0100
Subject: [mythtv] mythbackend: Suppress timestamp in log?
In-Reply-To: <56C75BBF.9030203@gmail.com>
References: <CAN3TeO12e27uAemzOUwc-ipL5LXYWz973EuhYKO8_--4fEaOsQ@mail.gmail.com>
 <56C75BBF.9030203@gmail.com>
Message-ID: <CAM-ziR78YCjss=mDcM5pci7pqZ2QoraN9ZfXOXS5E39c=k6mag@mail.gmail.com>

2016-02-19 19:15 GMT+01:00 Bill Meek <keemllib at gmail.com>:

> On 02/19/2016 11:34 AM, Richard Shaw wrote:
>
>> Since I log to the journal I already get a timestamp, getting two takes up
>> lots of columns and makes the log much more difficult to read.
>>
>> Do you automatically get a timestamp when logging to syslog? Could
>> supression of the timestamp be added to the --syslog command line option?
>>
>
> I did two things for journal-only logging:
>
> In the .unit file, add --quiet to the backend startup ExecStart line (as
> opposed to redirecting the stdout/err to /dev/null [why send something to
> the console only to throw it away].)
>
> In /etc/systemd/journald.conf, I uncommented and set to no the following:
> ForwardToSyslog=no. Not sure if systemd-journald was the only thing
> restarted,
> or if I just did a warm boot to be sure.
>
> The remaining issue is duplicate program names (mythbackend[2090]:
> mythbackend[2090]:)
> and I haven't looked into that one.
>
> This is Ubuntu 15.10 and 0.28-beta FYI.


In my setup I wanted to solve this for all the mythtv programs, not only
for the backend, so I hacked directly into
mythtv/libs/libmythbase/loggingserver.cpp:

https://github.com/sdrik/mythtv/commit/da6facec4ecaab329615f7ceb42936593ab35489

Regards,
C?dric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-dev/attachments/20160219/fde8149e/attachment.html>

From gary.buhrmaster at gmail.com  Fri Feb 19 19:01:27 2016
From: gary.buhrmaster at gmail.com (Gary Buhrmaster)
Date: Fri, 19 Feb 2016 19:01:27 +0000
Subject: [mythtv] mythbackend: Suppress timestamp in log?
In-Reply-To: <CAN3TeO12e27uAemzOUwc-ipL5LXYWz973EuhYKO8_--4fEaOsQ@mail.gmail.com>
References: <CAN3TeO12e27uAemzOUwc-ipL5LXYWz973EuhYKO8_--4fEaOsQ@mail.gmail.com>
Message-ID: <CAMfXtQy-d3pkzC4zewCLdMq5BjHmpSmhpK4q41JMJrvcc0AJUA@mail.gmail.com>

On Fri, Feb 19, 2016 at 5:34 PM, Richard Shaw <hobbes1069 at gmail.com> wrote:
> Since I log to the journal I already get a timestamp, getting two takes up
> lots of columns and makes the log much more difficult to read.

I presume you are using stdout to the journal?

This can (as posted by Mike) lose some information
that is not sent to the console (but will be sent
to a file or syslog).  Whether that additional
information is useful may depend on your next
failure.

And while reworking the logging is a long term
goal, I think that adding in the option to to directly
log via sd_journal_[print|send] might be a good
enough interim solution with maybe a new
--journal-logging command line option?

I sort of have coding such to submit as a feature
patch (for consideration) on my "wish I had some
time to contribute right now" list, but every time
I look at the logging I have found myself starting
to look at danielk's (not complete) logging rewrite
branch.  I need to stop doing that and just add
in journal logging (at the next time I have time).
Of course, if anyone else gets there first, I will
not be upset.

From keemllib at gmail.com  Fri Feb 19 20:15:48 2016
From: keemllib at gmail.com (Bill Meek)
Date: Fri, 19 Feb 2016 14:15:48 -0600
Subject: [mythtv] mythbackend: Suppress timestamp in log?
In-Reply-To: <CAMfXtQy-d3pkzC4zewCLdMq5BjHmpSmhpK4q41JMJrvcc0AJUA@mail.gmail.com>
References: <CAN3TeO12e27uAemzOUwc-ipL5LXYWz973EuhYKO8_--4fEaOsQ@mail.gmail.com>
 <CAMfXtQy-d3pkzC4zewCLdMq5BjHmpSmhpK4q41JMJrvcc0AJUA@mail.gmail.com>
Message-ID: <56C777F4.1050705@gmail.com>

On 02/19/2016 01:01 PM, Gary Buhrmaster wrote:
> This can (as posted by Mike) lose some information
> that is not sent to the console (but will be sent
> to a file or syslog).  Whether that additional
> information is useful may depend on your next
> failure.

Agreed, but not much lost. journalctl --output short-precise will
provide the uS timestamp. I think it's just the thread (LWP)
that's lost. The duplicate program name is nuisance.

journalctl --output short-precise --unit mythtv-backend:
Feb 19 08:34:15.038309 ofc0 mythbackend[2090]: mythbackend[2090]: I HouseKeeping housekeeper.cpp:153 (Run) HouseKeeperTask 'LogClean' Finished 
Successfully.

  --logpath entry:
2016-02-19 10:13:30.116806 I [2603/2742] HouseKeeping housekeeper.cpp:153 (Run) - HouseKeeperTask 'LogClean' Finished Successfully

Full disclosure, I actually prefer --logpath, but was just testing
systemd on my office host.

-- 
Bill

From gary.buhrmaster at gmail.com  Sat Feb 20 01:32:26 2016
From: gary.buhrmaster at gmail.com (Gary Buhrmaster)
Date: Sat, 20 Feb 2016 01:32:26 +0000
Subject: [mythtv] mythbackend: Suppress timestamp in log?
In-Reply-To: <56C777F4.1050705@gmail.com>
References: <CAN3TeO12e27uAemzOUwc-ipL5LXYWz973EuhYKO8_--4fEaOsQ@mail.gmail.com>
 <CAMfXtQy-d3pkzC4zewCLdMq5BjHmpSmhpK4q41JMJrvcc0AJUA@mail.gmail.com>
 <56C777F4.1050705@gmail.com>
Message-ID: <CAMfXtQwrtECwD_mRoB9oN58ay1mRNvCCKJ=T0B=z41RhaNKMnA@mail.gmail.com>

On Fri, Feb 19, 2016 at 8:15 PM, Bill Meek <keemllib at gmail.com> wrote:
> .... I think it's just the thread (LWP) that's lost.

I actually believe that the context, file, and line are
also missing.  Of course, as I said previously,
whether that missing data matters will depend on
your next failure (and whom you expect to assist
you in addressing the failure).

From keemllib at gmail.com  Sat Feb 20 02:24:40 2016
From: keemllib at gmail.com (Bill Meek)
Date: Fri, 19 Feb 2016 20:24:40 -0600
Subject: [mythtv] mythbackend: Suppress timestamp in log?
In-Reply-To: <CAMfXtQwrtECwD_mRoB9oN58ay1mRNvCCKJ=T0B=z41RhaNKMnA@mail.gmail.com>
References: <CAN3TeO12e27uAemzOUwc-ipL5LXYWz973EuhYKO8_--4fEaOsQ@mail.gmail.com>
 <CAMfXtQy-d3pkzC4zewCLdMq5BjHmpSmhpK4q41JMJrvcc0AJUA@mail.gmail.com>
 <56C777F4.1050705@gmail.com>
 <CAMfXtQwrtECwD_mRoB9oN58ay1mRNvCCKJ=T0B=z41RhaNKMnA@mail.gmail.com>
Message-ID: <56C7CE68.1080100@gmail.com>

On 02/19/2016 07:32 PM, Gary Buhrmaster wrote:
> On Fri, Feb 19, 2016 at 8:15 PM, Bill Meek <keemllib at gmail.com> wrote:
>> .... I think it's just the thread (LWP) that's lost.
>
> I actually believe that the context, file, and line are
> also missing.  Of course, as I said previously,
> whether that missing data matters will depend on
> your next failure (and whom you expect to assist
> you in addressing the failure).

They're there:

$ journalctl --output short-precise --unit mythtv-backend.service --lines 1
Feb 19 20:11:14.072265 ofc0 mythbackend[11093]: mythbackend[11093]: N Expire autoexpire.cpp:264 (CalcParams) AutoExpire: CalcParams(): Max 
required Free Space: 10.0 GB w/freq: 15 min

I think what's confusing is that if the BE isn't started with
--quiet and --syslog, console output will end up in the journal
too* and if memory serves, that's the one without the helpful
info.

* double logging

-- 
Bill

From gary.buhrmaster at gmail.com  Sat Feb 20 02:57:07 2016
From: gary.buhrmaster at gmail.com (Gary Buhrmaster)
Date: Sat, 20 Feb 2016 02:57:07 +0000
Subject: [mythtv] mythbackend: Suppress timestamp in log?
In-Reply-To: <56C7CE68.1080100@gmail.com>
References: <CAN3TeO12e27uAemzOUwc-ipL5LXYWz973EuhYKO8_--4fEaOsQ@mail.gmail.com>
 <CAMfXtQy-d3pkzC4zewCLdMq5BjHmpSmhpK4q41JMJrvcc0AJUA@mail.gmail.com>
 <56C777F4.1050705@gmail.com>
 <CAMfXtQwrtECwD_mRoB9oN58ay1mRNvCCKJ=T0B=z41RhaNKMnA@mail.gmail.com>
 <56C7CE68.1080100@gmail.com>
Message-ID: <CAMfXtQyPUOvCogacvwReTNG5Nzi9nvd+0DfpufmFFEd+Z8YgCw@mail.gmail.com>

On Sat, Feb 20, 2016 at 2:24 AM, Bill Meek <keemllib at gmail.com> wrote:
> .... console output will end up in the journal
> too* and if memory serves, that's the one without the helpful
> info.

Right, and that is why I said

   "I presume you are using stdout to the journal?"

So, you were responding to a completely different
set of conditions even though you explicitly
quoted and replied to my email.  If you are logging
stdout, it is NOT in there (as you agree).

Yes, MythTV gives one enough rope to hang
yourself, and a few others, along the way.
Add in systemd, with more knowledge than
most boy scouts regarding knots, and you
can have some interesting results.

From gary.buhrmaster at gmail.com  Sat Feb 20 03:13:57 2016
From: gary.buhrmaster at gmail.com (Gary Buhrmaster)
Date: Sat, 20 Feb 2016 03:13:57 +0000
Subject: [mythtv] Attempted build of v0.28-pre-3571-g4517c12 fails with
 missing fc22/x86_64/usr/share/mythtv/mythmusic folder
In-Reply-To: <56C6E3C0.2070705@tesco.net>
References: <56C06823.5040503@tesco.net> <56C09FFC.1090408@tesco.net>
 <56C48183.20704@tesco.net> <56C6E3C0.2070705@tesco.net>
Message-ID: <CAMfXtQyGckvA5O7zTQG2uohbe3NSxYtwRcS4gYm14d0Fudyr4g@mail.gmail.com>

On Fri, Feb 19, 2016 at 9:43 AM, John Pilkington <J.Pilk at tesco.net> wrote:
....
> I should probably post the entire 0.28-compatible specfile somewhere. In a
> Ticket?

Since you started from rpmfusion, you likely want to
share them there (or with Richard Shaw directly
who is the rpmfusion mythtv packager), especially
since now that 0.28 can (in theory) be built for
EPEL (well, if rpmfusion fixes the infrastructure to
allow that (last I knew it was broken))

The MythTV packaging branch for rpm's have not
been maintained since (approximately) Mythdora
days (Ok, maybe it is not quite that bad, but
close).

I suspect if you want to take on the responsibility
for maintaining the mythtv rpm build packaging that
that will not be refused (I believe the packaging
repo has a different set of committers).  Of course,
you and Richard might want to coordinate some
of that.

Note that rpm packaging is also (in theory) used
for SUSE, so you may need to expand your testing
a bit (although a fedora only spec file that works
is likely better than a 2013 spec file that likely
does not work at all anywhere).

From J.Pilk at tesco.net  Sat Feb 20 09:17:41 2016
From: J.Pilk at tesco.net (John Pilkington)
Date: Sat, 20 Feb 2016 09:17:41 +0000
Subject: [mythtv] Attempted build of v0.28-pre-3571-g4517c12 fails with
 missing fc22/x86_64/usr/share/mythtv/mythmusic folder
In-Reply-To: <CAMfXtQyGckvA5O7zTQG2uohbe3NSxYtwRcS4gYm14d0Fudyr4g@mail.gmail.com>
References: <56C06823.5040503@tesco.net> <56C09FFC.1090408@tesco.net>
 <56C48183.20704@tesco.net> <56C6E3C0.2070705@tesco.net>
 <CAMfXtQyGckvA5O7zTQG2uohbe3NSxYtwRcS4gYm14d0Fudyr4g@mail.gmail.com>
Message-ID: <56C82F35.5090805@tesco.net>

On 20/02/16 03:13, Gary Buhrmaster wrote:
> On Fri, Feb 19, 2016 at 9:43 AM, John Pilkington <J.Pilk at tesco.net> wrote:
> ....
>> I should probably post the entire 0.28-compatible specfile somewhere. In a
>> Ticket?
>
> Since you started from rpmfusion, you likely want to
> share them there (or with Richard Shaw directly
> who is the rpmfusion mythtv packager), especially
> since now that 0.28 can (in theory) be built for
> EPEL (well, if rpmfusion fixes the infrastructure to
> allow that (last I knew it was broken))
>
> The MythTV packaging branch for rpm's have not
> been maintained since (approximately) Mythdora
> days (Ok, maybe it is not quite that bad, but
> close).
>
> I suspect if you want to take on the responsibility
> for maintaining the mythtv rpm build packaging that
> that will not be refused (I believe the packaging
> repo has a different set of committers).  Of course,
> you and Richard might want to coordinate some
> of that.
>
> Note that rpm packaging is also (in theory) used
> for SUSE, so you may need to expand your testing
> a bit (although a fedora only spec file that works
> is likely better than a 2013 spec file that likely
> does not work at all anywhere).

Gary:  Thanks for that.  I was beginning to think that Richard probably 
has a 0.28-compatible version in the works and alternative input might 
confuse the issue.  In which case I could just watch that space...

My version needs some polishing but it currently works for me. 
Richard's 0.27-5-ish has services missing from mine.  I'm an interested 
user but have no real desire to spend yet more time on Mythtv or take on 
a formal role.  And it seems that other people are building 
Myth-on-Fedora without the packaging step.

I'll see how it goes.

John



From pgbennett at comcast.net  Sat Feb 20 17:20:29 2016
From: pgbennett at comcast.net (Peter Bennett)
Date: Sat, 20 Feb 2016 12:20:29 -0500
Subject: [mythtv] Ubuntu Mate on Raspberry Pi2
Message-ID: <56C8A05D.90505@comcast.net>

As discussed in the IRC chat, I fixed the issue of setuid hanging the
front end, and recompiled with all of the same configure settings as
used in the PPA build.

There are still multiple issues with running the front end under Ubuntu
Mate on Raspberry Pi 2. The sound cuts in and out during playback if
ALSA is selected. Playback is jerky. If I select pulseaudio the sound is
out of sync with the picture. Jumping back or forward causes sound to go
off. Exiting playback hangs the system indefinitely on "Please Wait...".
I have attached the setuid patch here. I will be away for a week. I will
look at it some more after that.

If anybody has had better luck with Ubuntu Mate please let me know.

Peter
-------------- next part --------------
A non-text attachment was scrubbed...
Name: setuid_hang.patch
Type: text/x-patch
Size: 1479 bytes
Desc: not available
URL: <http://lists.mythtv.org/pipermail/mythtv-dev/attachments/20160220/2b697cd0/attachment.bin>

From torbjorn.jansson at mbox200.swipnet.se  Sun Feb 21 16:48:31 2016
From: torbjorn.jansson at mbox200.swipnet.se (Torbjorn Jansson)
Date: Sun, 21 Feb 2016 17:48:31 +0100
Subject: [mythtv] iptv recorder with enigma2 box
Message-ID: <56C9EA5F.9010802@mbox200.swipnet.se>

Hello

i have tested the iptv support in mythtv (master and not fixes/0.27) and 
found some problems.
my testing was done against my dvb box that is based on enigma2 and its 
web interface.

iptv recorder was pointed at one of the urls from the web interface

problem 1: url too long
url got cutoff since it was longer than 128 character limit of 
capturecard.videodevice in the database.

so i had to download the m3u file manually and put it on a web server to 
make url shorter

question: can we extend that field, for example by doubling it so long 
urls work?


problem 2: "#EXTM3U "
channel scanning didn't work at all, it just complained about the file.
apparently there is an extra space in the first line of the m3u file 
like this without quotes: "#EXTM3U "

a simple trim near the beginning of: IPTVChannelFetcher::ParsePlaylist 
should do the trick


problem 3: format of #EXTINF:
next the format of EXTINF: is a bit different, like this:
#EXTINF:-1,Animal Planet

normally there is another number after the comma sign (channel number), 
like this:
#EXTINF:0,1 Animal Planet
Where 1 is the channel number to use


fixing this would require changing the for example the first regexp in 
parse_extinf()
but i don't fully understand the existing regex and what happens if we 
don't have any channum?
in my case it doesnt exist in the m3u file, so allocating channums based 
on order in the file is probably best bet (maybe already done?)


fixing above three problems results in successful scanning of channels.
BUT then there is a 4th issue.

problem 4: channel.serviceid=0
field serviceid in channel table is 0, result is that the backend can't 
find the channel once it has successful started receiving data.
there is errors in the log about not able to find program 0 in PAT

only way to workaround this is specify #EXTVLCOPT:program= in the m3u file.

i assume there is no way of convincing the backend to tune to the only 
working service there is?

i think the streaming service in enigma2 webui is very simple, it takes 
a service ref url and based on that tunes the mux and applies pid 
filtering and then sends the data as is over http
so there is no modification of PAT/PMT before sending it resulting in 
backend receiving lots of programs in the PAT but only one will work.


i just want to see what you think about the problems above.
i can probably make some patches for some of the issues, but problem 4 i 
dont know how to fix other than modifying the m3u file so it contains 
#EXTVLCOPT:program

From torbjorn.jansson at mbox200.swipnet.se  Sun Feb 21 17:19:33 2016
From: torbjorn.jansson at mbox200.swipnet.se (Torbjorn Jansson)
Date: Sun, 21 Feb 2016 18:19:33 +0100
Subject: [mythtv] iptv recorder with enigma2 box
In-Reply-To: <56C9EA5F.9010802@mbox200.swipnet.se>
References: <56C9EA5F.9010802@mbox200.swipnet.se>
Message-ID: <56C9F1A5.4070404@mbox200.swipnet.se>

there is another problem.
whenever i try to open up my iptv card in mythtv-setup the setup program 
freezes for a very long time.

in the log i can see:

2016-02-21 18:13:13.063067 I  VBox: Found 1 possible VBoxes
QIODevice::read (QNetworkReplyHttpImpl): device not open
2016-02-21 18:15:13.144049 I  VBox: GetDeviceDesc() failed for <Unknown>
2016-02-21 18:15:13.144087 I  VBox: Using UPNP to search for Vboxes (3 secs)
QIODevice::read (QNetworkReplyHttpImpl): device not open
2016-02-21 18:15:16.416803 I  VBox: Found 1 possible VBoxes
QIODevice::read (QNetworkReplyHttpImpl): device not open
QIODevice::read (QNetworkReplyHttpImpl): device not open
2016-02-21 18:17:16.494787 I  VBox: GetDeviceDesc() failed for <Unknown>
2016-02-21 18:17:16.497308 E  V4L2(): Could not open '':
                         eno: No such file or directory (2)

it took nearly 5 minutes from when i pressed return on the card until 
its settings opend.

what is VBox ?


On 2016-02-21 17:48, Torbjorn Jansson wrote:
> Hello
>
> i have tested the iptv support in mythtv (master and not fixes/0.27) and
> found some problems.
> my testing was done against my dvb box that is based on enigma2 and its
> web interface.
>
> iptv recorder was pointed at one of the urls from the web interface
>
> problem 1: url too long
> url got cutoff since it was longer than 128 character limit of
> capturecard.videodevice in the database.
>
> so i had to download the m3u file manually and put it on a web server to
> make url shorter
>
> question: can we extend that field, for example by doubling it so long
> urls work?
>
>
> problem 2: "#EXTM3U "
> channel scanning didn't work at all, it just complained about the file.
> apparently there is an extra space in the first line of the m3u file
> like this without quotes: "#EXTM3U "
>
> a simple trim near the beginning of: IPTVChannelFetcher::ParsePlaylist
> should do the trick
>
>
> problem 3: format of #EXTINF:
> next the format of EXTINF: is a bit different, like this:
> #EXTINF:-1,Animal Planet
>
> normally there is another number after the comma sign (channel number),
> like this:
> #EXTINF:0,1 Animal Planet
> Where 1 is the channel number to use
>
>
> fixing this would require changing the for example the first regexp in
> parse_extinf()
> but i don't fully understand the existing regex and what happens if we
> don't have any channum?
> in my case it doesnt exist in the m3u file, so allocating channums based
> on order in the file is probably best bet (maybe already done?)
>
>
> fixing above three problems results in successful scanning of channels.
> BUT then there is a 4th issue.
>
> problem 4: channel.serviceid=0
> field serviceid in channel table is 0, result is that the backend can't
> find the channel once it has successful started receiving data.
> there is errors in the log about not able to find program 0 in PAT
>
> only way to workaround this is specify #EXTVLCOPT:program= in the m3u file.
>
> i assume there is no way of convincing the backend to tune to the only
> working service there is?
>
> i think the streaming service in enigma2 webui is very simple, it takes
> a service ref url and based on that tunes the mux and applies pid
> filtering and then sends the data as is over http
> so there is no modification of PAT/PMT before sending it resulting in
> backend receiving lots of programs in the PAT but only one will work.
>
>
> i just want to see what you think about the problems above.
> i can probably make some patches for some of the issues, but problem 4 i
> dont know how to fix other than modifying the m3u file so it contains
> #EXTVLCOPT:program


From dekarl at spaetfruehstuecken.org  Mon Feb 22 07:07:42 2016
From: dekarl at spaetfruehstuecken.org (Karl Dietz)
Date: Mon, 22 Feb 2016 08:07:42 +0100
Subject: [mythtv] iptv recorder with enigma2 box
In-Reply-To: <56C9EA5F.9010802@mbox200.swipnet.se>
References: <56C9EA5F.9010802@mbox200.swipnet.se>
Message-ID: <56CAB3BE.5030908@spaetfruehstuecken.org>

Hi Torbjorn,

did you open a bug ticket to track these issues?

On 21.02.2016 17:48, Torbjorn Jansson wrote:
> problem 1: url too long
> url got cutoff since it was longer than 128 character limit of
> capturecard.videodevice in the database.

Can you post the playlist and preferably a documentation that can be
used to determite the maximum URL length? (to the ticket)

> problem 2: "#EXTM3U "
> channel scanning didn't work at all, it just complained about the file.
> apparently there is an extra space in the first line of the m3u file
> like this without quotes: "#EXTM3U "

Please post a sample, so our parser can be relaxed to accept more
variants of M3U.

> problem 3: format of #EXTINF:
> next the format of EXTINF: is a bit different, like this:
> #EXTINF:-1,Animal Planet

That's an issue. Our parser is written around the concept of playlists
with channel numbers. Preferably Enigma2 would prepend the channel
number that is used in the other interfaces.
(TV screen / webiste / etc.)

> problem 4: channel.serviceid=0
> field serviceid in channel table is 0, result is that the backend can't
> find the channel once it has successful started receiving data.
> there is errors in the log about not able to find program 0 in PAT
>
> only way to workaround this is specify #EXTVLCOPT:program= in the m3u file.
>
> i assume there is no way of convincing the backend to tune to the only
> working service there is?

This requires a rewrite / redesign. Reading a bit of the stream,
counting PIDs of the packets, then trying to figure out which service
uses these PIDs. With some services sharing PIDs this is going to be a
bit of guessing game.

But if I remember correctly the URLs contains all kinds of tuning
details, like frequency, PIDs, etc. if the program_number/service_id is
also part of the tuning information, then it would be easiest to extend
the playlist generator to just add this information.

Regards,
Karl

From jyavenard at gmail.com  Mon Feb 22 20:42:52 2016
From: jyavenard at gmail.com (Jean-Yves Avenard)
Date: Tue, 23 Feb 2016 07:42:52 +1100
Subject: [mythtv] iptv recorder with enigma2 box
In-Reply-To: <56CAB3BE.5030908@spaetfruehstuecken.org>
References: <56C9EA5F.9010802@mbox200.swipnet.se>
 <56CAB3BE.5030908@spaetfruehstuecken.org>
Message-ID: <CANpj82Kp3hE6qoJpcvumwrVDi7Rx4H1apPf7b1Uhd-cec8ygLA@mail.gmail.com>

Hi

On Monday, 22 February 2016, Karl Dietz <dekarl at spaetfruehstuecken.org>
wrote:

> Hi Torbjorn,
>
> did you open a bug ticket to track these issues?
>
> On 21.02.2016 17:48, Torbjorn Jansson wrote:
>
>> problem 1: url too long
>> url got cutoff since it was longer than 128 character limit of
>> capturecard.videodevice in the database.
>>
>
> Can you post the playlist and preferably a documentation that can be
> used to determite the maximum URL length? (to the ticket)
>
> problem 2: "#EXTM3U "
>> channel scanning didn't work at all, it just complained about the file.
>> apparently there is an extra space in the first line of the m3u file
>> like this without quotes: "#EXTM3U "
>>
>
> Please post a sample, so our parser can be relaxed to accept more
> variants of M3U.
>
> problem 3: format of #EXTINF:
>> next the format of EXTINF: is a bit different, like this:
>> #EXTINF:-1,Animal Planet
>>
>
> That's an issue. Our parser is written around the concept of playlists
> with channel numbers. Preferably Enigma2 would prepend the channel
> number that is used in the other interfaces.
> (TV screen / webiste / etc.)
>
> problem 4: channel.serviceid=0
>> field serviceid in channel table is 0, result is that the backend can't
>> find the channel once it has successful started receiving data.
>> there is errors in the log about not able to find program 0 in PAT
>>
>> only way to workaround this is specify #EXTVLCOPT:program= in the m3u
>> file.
>>
>> i assume there is no way of convincing the backend to tune to the only
>> working service there is?
>>
>
> This requires a rewrite / redesign. Reading a bit of the stream,
> counting PIDs of the packets, then trying to figure out which service
> uses these PIDs. With some services sharing PIDs this is going to be a
> bit of guessing game.
>
> But if I remember correctly the URLs contains all kinds of tuning
> details, like frequency, PIDs, etc. if the program_number/service_id is
> also part of the tuning information, then it would be easiest to extend
> the playlist generator to just add this information.
>
> Regards,
> Karl



There is no standard for a playlist of HLS stream.
I made the one we're using to look a bit like the MP3 one as used by the
old WinAmp and that we could reuse the existing playlist code.

The only thing defined is what's found in the m3u8 one (the HLS stream
itself)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-dev/attachments/20160223/fd386906/attachment.html>

From cschieli at gmail.com  Mon Feb 22 20:45:28 2016
From: cschieli at gmail.com (=?UTF-8?Q?C=C3=A9dric_Schieli?=)
Date: Mon, 22 Feb 2016 21:45:28 +0100
Subject: [mythtv] mythbackend: Suppress timestamp in log?
In-Reply-To: <CAMfXtQy-d3pkzC4zewCLdMq5BjHmpSmhpK4q41JMJrvcc0AJUA@mail.gmail.com>
References: <CAN3TeO12e27uAemzOUwc-ipL5LXYWz973EuhYKO8_--4fEaOsQ@mail.gmail.com>
 <CAMfXtQy-d3pkzC4zewCLdMq5BjHmpSmhpK4q41JMJrvcc0AJUA@mail.gmail.com>
Message-ID: <CAM-ziR5ja97BQhj-B59LGPUVGPDjn54ugOy3wuwbmO7zUb-Psg@mail.gmail.com>

2016-02-19 20:01 GMT+01:00 Gary Buhrmaster <gary.buhrmaster at gmail.com>:

> And while reworking the logging is a long term
> goal, I think that adding in the option to to directly
> log via sd_journal_[print|send] might be a good
> enough interim solution with maybe a new
> --journal-logging command line option?
>
> I sort of have coding such to submit as a feature
> patch (for consideration) on my "wish I had some
> time to contribute right now" list, but every time
> I look at the logging I have found myself starting
> to look at danielk's (not complete) logging rewrite
> branch.  I need to stop doing that and just add
> in journal logging (at the next time I have time).
> Of course, if anyone else gets there first, I will
> not be upset.
>


This was also on my todo list for a very long time, so I decided to give it
a whirl...
It's a bit hackish, because I've hijacked the SyslogLogger, but I think
that it make it less intrusive: it's still a kind of syslogger after all.

Tell me if it's worth polishing it up and making a formal submission.

https://github.com/sdrik/mythtv/tree/features/journal/master
https://github.com/sdrik/mythtv/tree/features/journal/0.27
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-dev/attachments/20160222/00da35d9/attachment.html>

From stuarta at squashedfrog.net  Tue Feb 23 09:49:00 2016
From: stuarta at squashedfrog.net (Stuart Auchterlonie)
Date: Tue, 23 Feb 2016 09:49:00 +0000
Subject: [mythtv] mythbackend: Suppress timestamp in log?
In-Reply-To: <CAM-ziR5ja97BQhj-B59LGPUVGPDjn54ugOy3wuwbmO7zUb-Psg@mail.gmail.com>
References: <CAN3TeO12e27uAemzOUwc-ipL5LXYWz973EuhYKO8_--4fEaOsQ@mail.gmail.com>
 <CAMfXtQy-d3pkzC4zewCLdMq5BjHmpSmhpK4q41JMJrvcc0AJUA@mail.gmail.com>
 <CAM-ziR5ja97BQhj-B59LGPUVGPDjn54ugOy3wuwbmO7zUb-Psg@mail.gmail.com>
Message-ID: <56CC2B0C.9070708@squashedfrog.net>

On 22/02/16 20:45, C?dric Schieli wrote:
> 
> 2016-02-19 20:01 GMT+01:00 Gary Buhrmaster <gary.buhrmaster at gmail.com
> <mailto:gary.buhrmaster at gmail.com>>:
> 
>     And while reworking the logging is a long term
>     goal, I think that adding in the option to to directly
>     log via sd_journal_[print|send] might be a good
>     enough interim solution with maybe a new
>     --journal-logging command line option?
> 
>     I sort of have coding such to submit as a feature
>     patch (for consideration) on my "wish I had some
>     time to contribute right now" list, but every time
>     I look at the logging I have found myself starting
>     to look at danielk's (not complete) logging rewrite
>     branch.  I need to stop doing that and just add
>     in journal logging (at the next time I have time).
>     Of course, if anyone else gets there first, I will
>     not be upset.
> 
> 
> 
> This was also on my todo list for a very long time, so I decided to give
> it a whirl...
> It's a bit hackish, because I've hijacked the SyslogLogger, but I think
> that it make it less intrusive: it's still a kind of syslogger after all.
> 
> Tell me if it's worth polishing it up and making a formal submission.
> 
> https://github.com/sdrik/mythtv/tree/features/journal/master
> https://github.com/sdrik/mythtv/tree/features/journal/0.27
> 

Please do submit this for inclusion...

Regards
Stuart



From dekarl at spaetfruehstuecken.org  Wed Feb 24 16:53:58 2016
From: dekarl at spaetfruehstuecken.org (Karl Dietz)
Date: Wed, 24 Feb 2016 17:53:58 +0100
Subject: [mythtv] iptv recorder with enigma2 box
In-Reply-To: <56CAB3BE.5030908@spaetfruehstuecken.org>
References: <56C9EA5F.9010802@mbox200.swipnet.se>
 <56CAB3BE.5030908@spaetfruehstuecken.org>
Message-ID: <56CDE026.7080909@spaetfruehstuecken.org>

Hi Torbjorn,

On 22.02.2016 08:07, Karl Dietz wrote:
> Hi Torbjorn,
>
> did you open a bug ticket to track these issues?
>
> On 21.02.2016 17:48, Torbjorn Jansson wrote:
>> problem 1: url too long
>> url got cutoff since it was longer than 128 character limit of
>> capturecard.videodevice in the database.
>
> Can you post the playlist and preferably a documentation that can be
> used to determite the maximum URL length? (to the ticket)
>
>> problem 2: "#EXTM3U "
>> channel scanning didn't work at all, it just complained about the file.
>> apparently there is an extra space in the first line of the m3u file
>> like this without quotes: "#EXTM3U "
>
> Please post a sample, so our parser can be relaxed to accept more
> variants of M3U.

I think this has been fixed in the web interface three years ago...

It was broken in July 2011 and fixed in December 2012.
https://schwerkraft.elitedvb.net/plugins/scmgit/cgi-bin/gitweb.cgi?p=enigma2-plugins/enigma2-plugins.git;a=history;f=webinterface/src/web/services.m3u.xml;h=e8fc673d66ceddd605c14cf724bf7b274618dbc4;hb=HEAD

>> problem 3: format of #EXTINF:
>> problem 4: channel.serviceid=0

Seeing that there is a template engine in place it should be very
straight forward to fix these two problems in Enigma2.

for problem 4:
diff --git a/webinterface/src/web/services.m3u.xml 
b/webinterface/src/web/services.m3u.xml
index e8fc673..1adc10c 100644
--- a/webinterface/src/web/services.m3u.xml
+++ b/webinterface/src/web/services.m3u.xml
@@ -1,6 +1,7 @@
  <e2:screen name="ServiceListWebScreen"><e2:element source="localip" 
macro="ipadress" />#EXTM3U
  #EXTVLCOPT--http-reconnect=true
  <e2:element source="ServiceList" id="bRef"><e2:convert 
type="web:ListFiller">#EXTINF:-1,<e2:item name="Name" filter="xml" />
+#EXTVLCOPT:program_number=<e2:item name="Sid" filter="xml" />
  http://<e2:item macro="ipadress" filter="xml" />:8001/<e2:item 
name="Reference" filter="xml" />
  </e2:convert><e2:convert type="web:TextToHTML" />
  </e2:element>

Regards,
Karl