mvpmc-devel — developer discussions

[Mvpmc-devel] loook at that!

[Sarah B. <ala...@ta...>]

Yo! 

Just look at  that great stuff outta here! You're gonna love  it, I swear! More info here <http://nketevije.browardpsychologist.com/e4rrsaw>

Sent from my iPhone, Sarah Beeby

[Mvpmc-devel] Fw: great news

[Gold F. <ala...@ta...>]

Dear! 
We've got some  great  news for  you! Just take a look <http://esteem.villanakara.com/e4xxak>

Gold Foot

Re: [Mvpmc-devel] Rasberry Pi 2 is a good option for replacement for MVP with mvpmc as MythTV Frontend that works with both SD and HD TV's

[Karl D. <de...@sp...>]

Hi Rob,

On 05.01.2016 04:09, Rob Young wrote:

> I found that OpenElec builds are available for both platforms so I obtained a Rasberry Pi 2 and FLIRC IR receiver, installed OpenElec 6.0 on it, configured PVR.MythTV and could not be happier with the results.   I now have all my entertainment functions available through a single device using Kodi - including watching recordings, setting recording rules, watching live TV, and watching movies from our digital library.   I found playback of SD MPEG2 recordings in MythTV was smooth out of the box, but playback of HD MPEG2 recordings somewhat less than smooth so I had to to purchase the MPEG2 codec license from the Rasberry Pi store for $5 to enable hardware decoding of MPEG2 files and with the codec enabled playback is very smooth for HD recordings and CPU utilization low.

Just a heads up. There is an active effort to bring the real MythTV
Frontend to the Raspberry Pi.

http://lists.mythtv.org/pipermail/mythtv-users/2016-January/date.html

Regards,
Karl

Re: [Mvpmc-devel] Rasberry Pi 2 is a good option for replacement for MVP with mvpmc as MythTV Frontend that works with both SD and HD TV's

[Mike Li <fit...@gm...>]

Cool stuff. Thanks for sharing.

I am thinking building a new media center after using mvpmc for many years.
Based on your previous email, I could probably figure out many things. But
I am just wondering if you could put together some kind of
guide/instructions of what you did, that would be very helpful to me and
anyone in this community who is interested.

Kind regards,
-Mike

On Mon, Jan 4, 2016 at 10:09 PM, Rob Young <rjw...@te...> wrote:

>
> For anyone currently using mvpmc with MythTV who might be considering
> moving to the latest MythTV, or are considering options to get HD content I
> thought I would share my experience.
>
> I have used mvpmc on a MVP as my frontend solution for MythTV for the past
> 8+ years and have been extremely happy with that solution as it worked
> reliably and could be easily operated by my wife and children.   However,
> due to my cable company's switch to all digital broadcasting, I needed to
> update my tuner hardware to continue to use MythTV to record, which
> required an upgrade of MythTV from 0.24 to 0.27.4 to get support the HD
> Homerun Prime tuner I chose to use.   Unfortunately mvpmc just would not
> work with my MythTV 0.27.4 install - I received advice from members of this
> forum, but was still unable to get mvpmc working properly with MythTV
> 0.27.4 and did not have the time to dig into it further.   As a result, I
> found myself looking for a new frontend solution for my MythTV setup   I
> looked at several options including UPnP clients built into streaming
> devices, nettop's, and other low power devices that could perform frontend
> duties with either MythFrontend or Kodi.
>
> My most limiting requirement is my need for composite or component video
> connections as I have an older TV that does not have HDMI.   I found most
> current nettop's and streaming devices only have HDMI output - which will
> not work in my environment.   We already have a WDTV Live for watching
> movies in our digital collection and it has a UPnP client in it.   While it
> sort of worked with MythTV and bought me some time - the UPnP client with
> the WDTV Live did not support commercial skip, the user interface lacks
> details about recordings (such as date recorded), and was generally clunky
> and unreliable (would fail with a streaming error frequently) and most
> importantly not loved by my wife or children.    I should note that I do
> not know if the limitations and reliability issues we experienced with WDTV
> Live is due to UPnP specifications, support for UPnP in MythTV, or the UPnP
> client implementation in WDTV Live.    I also briefly considered Jailbroken
> Apple TV2, and nettops PC's to run either MythFrontend or Kodi but had to
> rule these potential solutions out due to lack of composite or component
> outputs.
>
> A friend pointed out to me that  that Rasberry Pi and Pi 2 models have
> both HDMI and composite outputs, have excellent video chips and attractive
> price points.   I found that OpenElec builds are available for both
> platforms so I obtained a Rasberry Pi 2 and FLIRC IR receiver, installed
> OpenElec 6.0 on it, configured PVR.MythTV and could not be happier with the
> results.   I now have all my entertainment functions available through a
> single device using Kodi - including watching recordings, setting recording
> rules, watching live TV, and watching movies from our digital library.   I
> found playback of SD MPEG2 recordings in MythTV was smooth out of the box,
> but playback of HD MPEG2 recordings somewhat less than smooth so I had to
> to purchase the MPEG2 codec license from the Rasberry Pi store for $5 to
> enable hardware decoding of MPEG2 files and with the codec enabled playback
> is very smooth for HD recordings and CPU utilization low.    It is early
> days still, but my wife and kids find it much easier to use and more
> reliable than the UPnP solution with WDTV we have been using for the past
> couple of months.
>
> For anyone looking for a replacement for mvpmc on MVP - either to get
> support for newer MythTV releases or to get HD capability, I would highly
> recommend looking at OpenElec on Rasberry Pi 2.    Having said that, I
> still hope to be able to get my two MVP's with mvpmc working again for
> other TV's in our house.
>
>
> Rob.
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Mvpmc-devel mailing list
> Mvp...@li...
> https://lists.sourceforge.net/lists/listinfo/mvpmc-devel
>



-- 
Kind regards,
~Michael

[Mvpmc-devel] Rasberry Pi 2 is a good option for replacement for MVP with mvpmc as MythTV Frontend that works with both SD and HD TV's

[Rob Y. <rjw...@te...>]

For anyone currently using mvpmc with MythTV who might be considering moving to the latest MythTV, or are considering options to get HD content I thought I would share my experience.

I have used mvpmc on a MVP as my frontend solution for MythTV for the past 8+ years and have been extremely happy with that solution as it worked reliably and could be easily operated by my wife and children.   However, due to my cable company's switch to all digital broadcasting, I needed to update my tuner hardware to continue to use MythTV to record, which required an upgrade of MythTV from 0.24 to 0.27.4 to get support the HD Homerun Prime tuner I chose to use.   Unfortunately mvpmc just would not work with my MythTV 0.27.4 install - I received advice from members of this forum, but was still unable to get mvpmc working properly with MythTV 0.27.4 and did not have the time to dig into it further.   As a result, I found myself looking for a new frontend solution for my MythTV setup   I looked at several options including UPnP clients built into streaming devices, nettop's, and other low power devices that could perform frontend duties with either MythFrontend or Kodi.   

My most limiting requirement is my need for composite or component video connections as I have an older TV that does not have HDMI.   I found most current nettop's and streaming devices only have HDMI output - which will not work in my environment.   We already have a WDTV Live for watching movies in our digital collection and it has a UPnP client in it.   While it sort of worked with MythTV and bought me some time - the UPnP client with the WDTV Live did not support commercial skip, the user interface lacks details about recordings (such as date recorded), and was generally clunky and unreliable (would fail with a streaming error frequently) and most importantly not loved by my wife or children.    I should note that I do not know if the limitations and reliability issues we experienced with WDTV Live is due to UPnP specifications, support for UPnP in MythTV, or the UPnP client implementation in WDTV Live.    I also briefly considered Jailbroken Apple TV2, and nettops PC's to run either MythFrontend or Kodi but had to rule these potential solutions out due to lack of composite or component outputs.   

A friend pointed out to me that  that Rasberry Pi and Pi 2 models have both HDMI and composite outputs, have excellent video chips and attractive price points.   I found that OpenElec builds are available for both platforms so I obtained a Rasberry Pi 2 and FLIRC IR receiver, installed OpenElec 6.0 on it, configured PVR.MythTV and could not be happier with the results.   I now have all my entertainment functions available through a single device using Kodi - including watching recordings, setting recording rules, watching live TV, and watching movies from our digital library.   I found playback of SD MPEG2 recordings in MythTV was smooth out of the box, but playback of HD MPEG2 recordings somewhat less than smooth so I had to to purchase the MPEG2 codec license from the Rasberry Pi store for $5 to enable hardware decoding of MPEG2 files and with the codec enabled playback is very smooth for HD recordings and CPU utilization low.    It is early days still, but my wife and kids find it much easier to use and more reliable than the UPnP solution with WDTV we have been using for the past couple of months.

For anyone looking for a replacement for mvpmc on MVP - either to get support for newer MythTV releases or to get HD capability, I would highly recommend looking at OpenElec on Rasberry Pi 2.    Having said that, I still hope to be able to get my two MVP's with mvpmc working again for other TV's in our house.


Rob.

Re: [Mvpmc-devel] Problems with 0.27.4

[Rob Y. <rjw...@te...>]

I have tried completely disabling IPV6 in the kernel of my backend server, but my results are the same - mvpmc fails to create a socket in cmyth_connect with errno 97.   

I am a bit baffled as to why this was not an issue before, but is now after my backend was updated from Fedora 12 to Fedora 22 and Mythtv 0.24 to 0.27.4.     Not sure what to try next.   Is there a VM image available somewhere for a build environment for mvpmc?    If so, then I can experiment with debug statements to help understand why the failure is occurring and maybe take a crack at fixing up the logic in cmyth_connect if it proves necessary.

Any other suggestions?

Thanks!

Rob.



----- Original Message -----
From: "Jon Gettler" <ge...@ac...>
To: "Rob Young" <rjw...@te...>
Cc: "Charles Barnwell" <cgb...@gm...>, "L-mvpmc-devel" <mvp...@li...>
Sent: Sunday, October 11, 2015 10:46:42 AM
Subject: Re: [Mvpmc-devel] Problems with 0.27.4

The kernel running on the mediamvp as part of mvpmc does not support
IPv6.  Enabling IPv6 would probably use up too much memory.

It looks like cmyth_connect() is broken.  It calls getaddrinfo() on a
hostname and then looks for any IPv4 or IPv6 results.  It attempts to
create a socket to the first good address it finds, and then bails out
if the socket cannot be created.  It really should be trying to
connect to each address returned from getaddrinfo() until it finds one
that works.  It should only fail if none of the addresses are
reachable.

Rob, a quick solution would be to disable IPv6 on the myth server, if
that is an option.

Jon


On Sun, Oct 11, 2015 at 12:01 PM, Rob Young <rjw...@te...> wrote:
> Hi Charles,
>
> I have enabled logging for mvpmc and found it is failing in cmyth_connect:
>
> (cmyth)cmyth_connect: cannot create socket (97)
> (cmyth)cmyth_conn_connect: cmyth_connect(mythserver, 6543, 1024) failed
> (cmyth)cmyth_conn_connect_ctrl: done connecting control connection ret = (nil)
> mythtv_shutdown(): closing mythtv connection
> (cmyth)mythtv_shutdown [src/mythtv.c:504]: (trace) {
> (cmyth)mythtv_close [src/mythtv.c:488]: (trace) {
>
>
> errno 97 from the socket() call is address family not supported by protocol.    Looking at the code I am wondering if it might have something to do with IPV6 support (although I am not using IPV6 it seems it is enabled on my upgraded backend).
>
> I have verified that the hostname mythserver does resolve to an IPV4 address, nothing is blocking port 6543 on my backend, and have verified with Telnet that connections can be established port 6543.
>
> Any thoughts or suggestions are appreciated.
>
> Thanks.
>
>
> Rob.
>
>
> ----- Original Message -----
> From: "Charles Barnwell" <cgb...@gm...>
> To: mvp...@li...
> Sent: Sunday, October 11, 2015 3:05:34 AM
> Subject: Re: [Mvpmc-devel] Problems with 0.27.4
>
> Hi Rob,
>
> Well you are not the only person still using mvpmc.  I have, but I am
> still running Myth 0.24.  Have you tried tracing to see what is happening?
>
> Charles.
>
> On 08/10/15 21:26, Rob Young wrote:
>> Am I the only one still using mvpmc these days?    I have two of them, and have been using since 2007, and hope to get a few more months out of them.   I know I am dealing with obsolete hardware and software.   My plan is to update my frontends in the next year as I update other equipment.    I don't care about guide data, on screen programming or live TV - I use them only to watch recordings in mythtv.
>>
>> I just completed a much needed update to my backend from 0.24 to 0.27.4 - primarily to get support for HDHomerun Prime tuner.
>>
>> Since upgrading to 0.27.4, both of my MediaMVP's running the September 2014 dongle previously referenced as supporting 0.27.1 and above, disconnect from the backend and display an error message to this effect immediately after selecting a recording to view.   This happens on both old and new recordings (my old recordings are recorded using PVR-150 and new on HDHomerun Prime).
>>
>> I see there were some recent commits to the GIT repository for mvpmc referenced previously in this mailing list.   Not sure if they are relevant to my issue and if so if someone has made a new dongle available somewhere or if I would have to setup a VM and pull the code and build one myself.
>>
>> I am able to capture and send relevent logs from mvpmc and mythtv if necessary.    I have a software background and may be able to dig-in the code myself - but my C is very rusty.
>>
>> Thanks in advance.
>>
>>
>> Rob.
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Mvpmc-devel mailing list
>> Mvp...@li...
>> https://lists.sourceforge.net/lists/listinfo/mvpmc-devel
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Mvpmc-devel mailing list
> Mvp...@li...
> https://lists.sourceforge.net/lists/listinfo/mvpmc-devel
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Mvpmc-devel mailing list
> Mvp...@li...
> https://lists.sourceforge.net/lists/listinfo/mvpmc-devel

Re: [Mvpmc-devel] Problems with 0.27.4

[Rob Y. <rjw...@te...>]

Thanks.  I thought the code in cmyth_connect() looked wrong - but it has probably always been this way and must work in most circumstances.

I will disable IPV6 completely on my myth server and ensure there are no IPV6 addresses  configured anywhere in the myth database and retest.

Rob.

> On Oct 11, 2015, at 10:46 AM, Jon Gettler <ge...@ac...> wrote:
> 
> The kernel running on the mediamvp as part of mvpmc does not support
> IPv6.  Enabling IPv6 would probably use up too much memory.
> 
> It looks like cmyth_connect() is broken.  It calls getaddrinfo() on a
> hostname and then looks for any IPv4 or IPv6 results.  It attempts to
> create a socket to the first good address it finds, and then bails out
> if the socket cannot be created.  It really should be trying to
> connect to each address returned from getaddrinfo() until it finds one
> that works.  It should only fail if none of the addresses are
> reachable.
> 
> Rob, a quick solution would be to disable IPv6 on the myth server, if
> that is an option.
> 
> Jon
> 
> 
>> On Sun, Oct 11, 2015 at 12:01 PM, Rob Young <rjw...@te...> wrote:
>> Hi Charles,
>> 
>> I have enabled logging for mvpmc and found it is failing in cmyth_connect:
>> 
>> (cmyth)cmyth_connect: cannot create socket (97)
>> (cmyth)cmyth_conn_connect: cmyth_connect(mythserver, 6543, 1024) failed
>> (cmyth)cmyth_conn_connect_ctrl: done connecting control connection ret = (nil)
>> mythtv_shutdown(): closing mythtv connection
>> (cmyth)mythtv_shutdown [src/mythtv.c:504]: (trace) {
>> (cmyth)mythtv_close [src/mythtv.c:488]: (trace) {
>> 
>> 
>> errno 97 from the socket() call is address family not supported by protocol.    Looking at the code I am wondering if it might have something to do with IPV6 support (although I am not using IPV6 it seems it is enabled on my upgraded backend).
>> 
>> I have verified that the hostname mythserver does resolve to an IPV4 address, nothing is blocking port 6543 on my backend, and have verified with Telnet that connections can be established port 6543.
>> 
>> Any thoughts or suggestions are appreciated.
>> 
>> Thanks.
>> 
>> 
>> Rob.
>> 
>> 
>> ----- Original Message -----
>> From: "Charles Barnwell" <cgb...@gm...>
>> To: mvp...@li...
>> Sent: Sunday, October 11, 2015 3:05:34 AM
>> Subject: Re: [Mvpmc-devel] Problems with 0.27.4
>> 
>> Hi Rob,
>> 
>> Well you are not the only person still using mvpmc.  I have, but I am
>> still running Myth 0.24.  Have you tried tracing to see what is happening?
>> 
>> Charles.
>> 
>>> On 08/10/15 21:26, Rob Young wrote:
>>> Am I the only one still using mvpmc these days?    I have two of them, and have been using since 2007, and hope to get a few more months out of them.   I know I am dealing with obsolete hardware and software.   My plan is to update my frontends in the next year as I update other equipment.    I don't care about guide data, on screen programming or live TV - I use them only to watch recordings in mythtv.
>>> 
>>> I just completed a much needed update to my backend from 0.24 to 0.27.4 - primarily to get support for HDHomerun Prime tuner.
>>> 
>>> Since upgrading to 0.27.4, both of my MediaMVP's running the September 2014 dongle previously referenced as supporting 0.27.1 and above, disconnect from the backend and display an error message to this effect immediately after selecting a recording to view.   This happens on both old and new recordings (my old recordings are recorded using PVR-150 and new on HDHomerun Prime).
>>> 
>>> I see there were some recent commits to the GIT repository for mvpmc referenced previously in this mailing list.   Not sure if they are relevant to my issue and if so if someone has made a new dongle available somewhere or if I would have to setup a VM and pull the code and build one myself.
>>> 
>>> I am able to capture and send relevent logs from mvpmc and mythtv if necessary.    I have a software background and may be able to dig-in the code myself - but my C is very rusty.
>>> 
>>> Thanks in advance.
>>> 
>>> 
>>> Rob.
>>> 
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> Mvpmc-devel mailing list
>>> Mvp...@li...
>>> https://lists.sourceforge.net/lists/listinfo/mvpmc-devel
>> 
>> 
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Mvpmc-devel mailing list
>> Mvp...@li...
>> https://lists.sourceforge.net/lists/listinfo/mvpmc-devel
>> 
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Mvpmc-devel mailing list
>> Mvp...@li...
>> https://lists.sourceforge.net/lists/listinfo/mvpmc-devel

Re: [Mvpmc-devel] Problems with 0.27.4

[Jon G. <ge...@ac...>]

The kernel running on the mediamvp as part of mvpmc does not support
IPv6.  Enabling IPv6 would probably use up too much memory.

It looks like cmyth_connect() is broken.  It calls getaddrinfo() on a
hostname and then looks for any IPv4 or IPv6 results.  It attempts to
create a socket to the first good address it finds, and then bails out
if the socket cannot be created.  It really should be trying to
connect to each address returned from getaddrinfo() until it finds one
that works.  It should only fail if none of the addresses are
reachable.

Rob, a quick solution would be to disable IPv6 on the myth server, if
that is an option.

Jon


On Sun, Oct 11, 2015 at 12:01 PM, Rob Young <rjw...@te...> wrote:
> Hi Charles,
>
> I have enabled logging for mvpmc and found it is failing in cmyth_connect:
>
> (cmyth)cmyth_connect: cannot create socket (97)
> (cmyth)cmyth_conn_connect: cmyth_connect(mythserver, 6543, 1024) failed
> (cmyth)cmyth_conn_connect_ctrl: done connecting control connection ret = (nil)
> mythtv_shutdown(): closing mythtv connection
> (cmyth)mythtv_shutdown [src/mythtv.c:504]: (trace) {
> (cmyth)mythtv_close [src/mythtv.c:488]: (trace) {
>
>
> errno 97 from the socket() call is address family not supported by protocol.    Looking at the code I am wondering if it might have something to do with IPV6 support (although I am not using IPV6 it seems it is enabled on my upgraded backend).
>
> I have verified that the hostname mythserver does resolve to an IPV4 address, nothing is blocking port 6543 on my backend, and have verified with Telnet that connections can be established port 6543.
>
> Any thoughts or suggestions are appreciated.
>
> Thanks.
>
>
> Rob.
>
>
> ----- Original Message -----
> From: "Charles Barnwell" <cgb...@gm...>
> To: mvp...@li...
> Sent: Sunday, October 11, 2015 3:05:34 AM
> Subject: Re: [Mvpmc-devel] Problems with 0.27.4
>
> Hi Rob,
>
> Well you are not the only person still using mvpmc.  I have, but I am
> still running Myth 0.24.  Have you tried tracing to see what is happening?
>
> Charles.
>
> On 08/10/15 21:26, Rob Young wrote:
>> Am I the only one still using mvpmc these days?    I have two of them, and have been using since 2007, and hope to get a few more months out of them.   I know I am dealing with obsolete hardware and software.   My plan is to update my frontends in the next year as I update other equipment.    I don't care about guide data, on screen programming or live TV - I use them only to watch recordings in mythtv.
>>
>> I just completed a much needed update to my backend from 0.24 to 0.27.4 - primarily to get support for HDHomerun Prime tuner.
>>
>> Since upgrading to 0.27.4, both of my MediaMVP's running the September 2014 dongle previously referenced as supporting 0.27.1 and above, disconnect from the backend and display an error message to this effect immediately after selecting a recording to view.   This happens on both old and new recordings (my old recordings are recorded using PVR-150 and new on HDHomerun Prime).
>>
>> I see there were some recent commits to the GIT repository for mvpmc referenced previously in this mailing list.   Not sure if they are relevant to my issue and if so if someone has made a new dongle available somewhere or if I would have to setup a VM and pull the code and build one myself.
>>
>> I am able to capture and send relevent logs from mvpmc and mythtv if necessary.    I have a software background and may be able to dig-in the code myself - but my C is very rusty.
>>
>> Thanks in advance.
>>
>>
>> Rob.
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Mvpmc-devel mailing list
>> Mvp...@li...
>> https://lists.sourceforge.net/lists/listinfo/mvpmc-devel
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Mvpmc-devel mailing list
> Mvp...@li...
> https://lists.sourceforge.net/lists/listinfo/mvpmc-devel
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Mvpmc-devel mailing list
> Mvp...@li...
> https://lists.sourceforge.net/lists/listinfo/mvpmc-devel

Re: [Mvpmc-devel] Problems with 0.27.4

[Rob Y. <rjw...@te...>]

Hi Charles,

I have enabled logging for mvpmc and found it is failing in cmyth_connect:

(cmyth)cmyth_connect: cannot create socket (97)
(cmyth)cmyth_conn_connect: cmyth_connect(mythserver, 6543, 1024) failed
(cmyth)cmyth_conn_connect_ctrl: done connecting control connection ret = (nil)
mythtv_shutdown(): closing mythtv connection
(cmyth)mythtv_shutdown [src/mythtv.c:504]: (trace) {
(cmyth)mythtv_close [src/mythtv.c:488]: (trace) {


errno 97 from the socket() call is address family not supported by protocol.    Looking at the code I am wondering if it might have something to do with IPV6 support (although I am not using IPV6 it seems it is enabled on my upgraded backend).  

I have verified that the hostname mythserver does resolve to an IPV4 address, nothing is blocking port 6543 on my backend, and have verified with Telnet that connections can be established port 6543.

Any thoughts or suggestions are appreciated.

Thanks.


Rob.


----- Original Message -----
From: "Charles Barnwell" <cgb...@gm...>
To: mvp...@li...
Sent: Sunday, October 11, 2015 3:05:34 AM
Subject: Re: [Mvpmc-devel] Problems with 0.27.4

Hi Rob,

Well you are not the only person still using mvpmc.  I have, but I am 
still running Myth 0.24.  Have you tried tracing to see what is happening?

Charles.

On 08/10/15 21:26, Rob Young wrote:
> Am I the only one still using mvpmc these days?    I have two of them, and have been using since 2007, and hope to get a few more months out of them.   I know I am dealing with obsolete hardware and software.   My plan is to update my frontends in the next year as I update other equipment.    I don't care about guide data, on screen programming or live TV - I use them only to watch recordings in mythtv.
>
> I just completed a much needed update to my backend from 0.24 to 0.27.4 - primarily to get support for HDHomerun Prime tuner.
>
> Since upgrading to 0.27.4, both of my MediaMVP's running the September 2014 dongle previously referenced as supporting 0.27.1 and above, disconnect from the backend and display an error message to this effect immediately after selecting a recording to view.   This happens on both old and new recordings (my old recordings are recorded using PVR-150 and new on HDHomerun Prime).
>
> I see there were some recent commits to the GIT repository for mvpmc referenced previously in this mailing list.   Not sure if they are relevant to my issue and if so if someone has made a new dongle available somewhere or if I would have to setup a VM and pull the code and build one myself.
>
> I am able to capture and send relevent logs from mvpmc and mythtv if necessary.    I have a software background and may be able to dig-in the code myself - but my C is very rusty.
>
> Thanks in advance.
>
>
> Rob.
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Mvpmc-devel mailing list
> Mvp...@li...
> https://lists.sourceforge.net/lists/listinfo/mvpmc-devel


------------------------------------------------------------------------------
_______________________________________________
Mvpmc-devel mailing list
Mvp...@li...
https://lists.sourceforge.net/lists/listinfo/mvpmc-devel

Re: [Mvpmc-devel] Problems with 0.27.4

[Charles B. <cgb...@gm...>]

Hi Rob,

Well you are not the only person still using mvpmc.  I have, but I am 
still running Myth 0.24.  Have you tried tracing to see what is happening?

Charles.

On 08/10/15 21:26, Rob Young wrote:
> Am I the only one still using mvpmc these days?    I have two of them, and have been using since 2007, and hope to get a few more months out of them.   I know I am dealing with obsolete hardware and software.   My plan is to update my frontends in the next year as I update other equipment.    I don't care about guide data, on screen programming or live TV - I use them only to watch recordings in mythtv.
>
> I just completed a much needed update to my backend from 0.24 to 0.27.4 - primarily to get support for HDHomerun Prime tuner.
>
> Since upgrading to 0.27.4, both of my MediaMVP's running the September 2014 dongle previously referenced as supporting 0.27.1 and above, disconnect from the backend and display an error message to this effect immediately after selecting a recording to view.   This happens on both old and new recordings (my old recordings are recorded using PVR-150 and new on HDHomerun Prime).
>
> I see there were some recent commits to the GIT repository for mvpmc referenced previously in this mailing list.   Not sure if they are relevant to my issue and if so if someone has made a new dongle available somewhere or if I would have to setup a VM and pull the code and build one myself.
>
> I am able to capture and send relevent logs from mvpmc and mythtv if necessary.    I have a software background and may be able to dig-in the code myself - but my C is very rusty.
>
> Thanks in advance.
>
>
> Rob.
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Mvpmc-devel mailing list
> Mvp...@li...
> https://lists.sourceforge.net/lists/listinfo/mvpmc-devel

[Mvpmc-devel] Problems with 0.27.4

[Rob Y. <rjw...@te...>]

Am I the only one still using mvpmc these days?    I have two of them, and have been using since 2007, and hope to get a few more months out of them.   I know I am dealing with obsolete hardware and software.   My plan is to update my frontends in the next year as I update other equipment.    I don't care about guide data, on screen programming or live TV - I use them only to watch recordings in mythtv.

I just completed a much needed update to my backend from 0.24 to 0.27.4 - primarily to get support for HDHomerun Prime tuner.   

Since upgrading to 0.27.4, both of my MediaMVP's running the September 2014 dongle previously referenced as supporting 0.27.1 and above, disconnect from the backend and display an error message to this effect immediately after selecting a recording to view.   This happens on both old and new recordings (my old recordings are recorded using PVR-150 and new on HDHomerun Prime).

I see there were some recent commits to the GIT repository for mvpmc referenced previously in this mailing list.   Not sure if they are relevant to my issue and if so if someone has made a new dongle available somewhere or if I would have to setup a VM and pull the code and build one myself.    

I am able to capture and send relevent logs from mvpmc and mythtv if necessary.    I have a software background and may be able to dig-in the code myself - but my C is very rusty.

Thanks in advance.


Rob.

Re: [Mvpmc-devel] Kin Koo y

[Kin K. <ki...@ya...>]

http://sgk-ssk.com/qryjeyh/djrcuglnsztpvqswdepddbpcflixuyt.ozslhknqtehqesxbqvbbnrwszwjgig 







































 Kin Koo 
 

Re: [Mvpmc-devel] New Dongle

[Charles B. <cgb...@gm...>]

Thanks Bernhard,

This will keep my mvp box going for a while.

Charles.
On 7 Sep 2014 18:36, "Bernhard Geier" <ge...@ge...> wrote:

> Source is on github: https://github.com/citronalco/mvpmc/
> Binary dongle download: https://github.com/citronalco/mvpmc/wiki
>
> No functional changes, so LiveTV and TV Guide still don't work, I only
> merged most of the updates of Gettler's cmyth library.
>
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Mvpmc-devel mailing list
> Mvp...@li...
> https://lists.sourceforge.net/lists/listinfo/mvpmc-devel
>

[Mvpmc-devel] New Dongle

[Bernhard G. <ge...@ge...>]

Source is on github: https://github.com/citronalco/mvpmc/
Binary dongle download: https://github.com/citronalco/mvpmc/wiki

No functional changes, so LiveTV and TV Guide still don't work, I only
merged most of the updates of Gettler's cmyth library.

Re: [Mvpmc-devel] New dongle available

[Bernhard G. <ge...@ge...>]

The source is finally on github:
https://github.com/citronalco/mvpmc

Re: [Mvpmc-devel] New dongle available

[Dave A. <da...@th...>]

On 13 Jan 2014, at 17:13, Bernhard Geier <ge...@ge...> wrote:

> Dave Ansell <dave@...> writes:
> 
>> 
>> Thankyou!
>> 
>> I still have a couple of MVPs - still easier to use than XBMC/Pi (except
> for HD of course.)
>> 
>> Will test shortly, though I am still stuck on 0.24 since I haven’t had a
> working dongle since then.
>> 
> 
> If the one I posted last year did not work for your purposes I doubt that
> this one will.
> 
> I use it to watch MythTV recordings and videos on the NFS mounts, nothing
> more, and it's working properly for that with 0.26.
> For programming recordings and stuff I use MythWeb.
> 
> 
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today. 
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> Mvpmc-devel mailing list
> Mvp...@li...
> https://lists.sourceforge.net/lists/listinfo/mvpmc-devel



Fair enough, thanks anyway.
It has certainly been the case in the past that things like scheduling and bookmarks (which both require sql access) have been broken.   (and wife likes to use them!)
I am still trying to move to XBMC as frontend but the user interface is still inferior to MVPMC IMHO.    Scheduling is virtually impossible to understand for example.

Re: [Mvpmc-devel] New dongle available

[Bernhard G. <ge...@ge...>]

Dave Ansell <dave@...> writes:

> 
> Thankyou!
> 
> I still have a couple of MVPs - still easier to use than XBMC/Pi (except
for HD of course.)
> 
> Will test shortly, though I am still stuck on 0.24 since I haven’t had a
working dongle since then.
> 

If the one I posted last year did not work for your purposes I doubt that
this one will.

I use it to watch MythTV recordings and videos on the NFS mounts, nothing
more, and it's working properly for that with 0.26.
For programming recordings and stuff I use MythWeb.

Re: [Mvpmc-devel] New dongle available

[Brian J. M. <br...@in...>]

On Sun, 2014-01-12 at 16:48 +0000, Bernhard Geier wrote: 
> I don't know if anybody out there still uses the MediaMVP. I do.

I do also.  Well, my mother does.  :-)

> This time I was able to use the most current release of Jon Gettler's
> libcmyth, which means the dongle is supposed to work with MythTV >= 0.27.

Ahh.  Super sweet!

> LiveTV still does not work.

Doesn't matter here.  The whole point of a PVR is to avoid LiveTV.  :-)

Cheers, and thanks for the work!

b.

Re: [Mvpmc-devel] New dongle available

[Dave A. <da...@th...>]

Thankyou!

I still have a couple of MVPs - still easier to use than XBMC/Pi (except for HD of course.)

Will test shortly, though I am still stuck on 0.24 since I haven’t had a working dongle since then.


On 12 Jan 2014, at 16:48, Bernhard Geier <ge...@ge...> wrote:

> I don't know if anybody out there still uses the MediaMVP. I do.
> 
> This time I was able to use the most current release of Jon Gettler's
> libcmyth, which means the dongle is supposed to work with MythTV >= 0.27.
> LiveTV still does not work.
> 
> New Dongle:
> ftp://ftp.geierb.de/mvpmc/dongle/
> 
> Source:
> ftp://ftp.geierb.de/mvpmc/mvpmc-cmyth-2013-06-18-no_livetv.tar.bz2
> 
> 
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> Mvpmc-devel mailing list
> Mvp...@li...
> https://lists.sourceforge.net/lists/listinfo/mvpmc-devel

[Mvpmc-devel] New dongle available

[Bernhard G. <ge...@ge...>]

I don't know if anybody out there still uses the MediaMVP. I do.

This time I was able to use the most current release of Jon Gettler's
libcmyth, which means the dongle is supposed to work with MythTV >= 0.27.
LiveTV still does not work.

New Dongle:
ftp://ftp.geierb.de/mvpmc/dongle/

Source:
ftp://ftp.geierb.de/mvpmc/mvpmc-cmyth-2013-06-18-no_livetv.tar.bz2

Re: [Mvpmc-devel] [Mvpmc-users] XBMC's MythTV PVR add-on

[Tom M. <tme...@gm...>]

[Moving a conversation here from the mvpmc users list.]

Jon Gettler wrote:
> Tom Metro wrote:
>     How about an antique 0.21.0+fixes?
> 
> Any idea what is broken?

No, not specifically. I wrote up my observations in this XBMC forum posting:
http://forum.xbmc.org/showthread.php?tid=164827

Where I wrote:

  I'm trying to use it with an ancient MythTV back-end, 0.21.0+fixes,
  and while all the database I/O works just fine (recording, schedules,
  and listings show fine), attempting to play a video results in
  "waiting..." appearing for about a minute and then nothing...

and I quoted some bits from the XBMC log including "Open - error probing
input format, pvr://recordings/[...]20130512_140000.pvr".

I didn't investigate further because I didn't know if it would be
pointless if it was definitely known that 0.21 was not supported.

I hoped to receive confirmation from the PVR add-on developers, but no
response from them. I can't really say they seem all that active on the
forum. (I miss the mvpmc developer community, which was small, but
responsive.)


> If not, it is certainly a lot easier to test with some of the test
> programs in cmyth (https://github.com/cmyth/cmyth).

That's a thought...

Maybe I can build a version of the PVR add-on that uses the mvpmc
version of the library? (Which could be messy, as I think they've
changed the API.) Or at least revert the chunk of code responsible for
streaming video.

I have disappointment and mixed feelings about the XBMC MythTV PVR
add-on. The first point of confusion is that they "hid" this
functionality under the banner of "Live TV" and don't explain in their
documentation that you have to enable live TV to get PVR access. Live
TV? I never use Live TV. Why would I enable that? (Not until I dug up a
YouTube video demoing the PVR stuff did I learn otherwise.)

The other is that the options for showing the show list is once again on
par with what you might see from a 2005-era UPnP client. You drill down
into a recording group, then you have to either pick categories or
series titles. Less usability than the 2006-era mvpmc design. What I
want is recording group *filters*, like mvpmc, and the ability to drill
down to categories, *then* to series titles, then episodes, sorted by
original air date. (mvpmc gets close, but shows episodes once you get
into categories.)

Anyway, I'm pointlessly griping to the wrong audience...but I guess my
point is that this makes me less motivated to invest a bunch of effort
into getting it working, if the end result is going to be worse
usability compared to mvpmc. (Though obviously better codec support and
higher resolution.)

Who knows, maybe fixing the UI problems will be comparatively easy, once
the protocol issues are resolved.

(I've also tried out the "MythBox" add-on and using the older style
mythtv:// service path, but neither seems to support the old back-end,
or are otherwise broken. (And both have even worse UI.))


> The ideal solution here would be to transition mvpmc to use the libcmyth
> repository on github, instead of the built-in version.
...
> However, I really have no idea how much interest there would be in
> doing that, or how much use mvpmc is even getting these days.

Right.

If mvpmc development has effectively ceased, does that make sense?

Is there anyone still actively working on porting mvpmc to X or anything
else?

 -Tom

[Mvpmc-devel] (no subject)

[Kin K. <ki...@ya...>]

http://www.poker-bonuscode.de/apokbj/bhcahzjn34gx9gpge3uclrk0.1k8sve5pt0?p4efgh0z2nzdst434

Re: [Mvpmc-devel] New Dongle

[Bernhard G. <ge...@ge...>]

Paulus, Markus G A (Mark <mark.paulus@...> writes:

> 
> Well, I had a chance to do a couple of things over the weekend.  This
> is pretty limited, since I don't use my mvpmc much, but here's what I did.
> (BTW, this is running against mythtv 0.25)
>
> I get the full list of shows, including my HD shows.
> 
> I am able to play my SD based recordings (Made via pvr 150/250).
> 
> I am able to delete shows (and don't get the multiple refreshes)

I'm glad to hear that. 

> Program Finder (Scheduling) option errors out with: 
>     No MythTV SQL support.  MythTV version: 72.
> 
> This is probably existing problem, but the Schedule Recordings
> option doesn't seem to honor the "visible" flag.  eg, I have
> to use the same schedulesdirect source for my SD only 
> (pvr-150/250) and my HD (HDHR/HD-PVR) devices.  So, since my
> PVR-150/250 can't capture HD stuff, I set the "visible" flag to 0
> and they don't record on those channels (at least, that's the way
> I think it 's supposed to work.  If not, I would appreciate anyone 
> letting me know different).  So, in the MVPMC, I see shows
> on channels on sources that have the visible set to 0.

Yes, all the EPG/scheduling stuff (also used by LiveTV) is very old.
XBMC guys fixed some of the issues. But while doing this they changed the whole
epg & channel handling, so it's very hard to get the changes back into mvpmc.

So if you (or anyone else reading this) is motivated to do some programming go
ahead. I haven't done any C programming the last maybe 10 years and I have
forgotten nearly everything, so I'm very skeptic if I can do that. 

Re: [Mvpmc-devel] New Dongle

[Paulus, M. G A \(Mark\) <mar...@ve...>]

Well, I had a chance to do a couple of things over the weekend.  This
is pretty limited, since I don't use my mvpmc much, but here's what I did.
(BTW, this is running against mythtv 0.25)

I get the full list of shows, including my HD shows.

I am able to play my SD based recordings (Made via pvr 150/250).

I am able to delete shows (and don't get the multiple refreshes)

Program Finder (Scheduling) option errors out with: 
    No MythTV SQL support.  MythTV version: 72.

This is probably existing problem, but the Schedule Recordings
option doesn't seem to honor the "visible" flag.  eg, I have
to use the same schedulesdirect source for my SD only 
(pvr-150/250) and my HD (HDHR/HD-PVR) devices.  So, since my
PVR-150/250 can't capture HD stuff, I set the "visible" flag to 0
and they don't record on those channels (at least, that's the way
I think it 's supposed to work.  If not, I would appreciate anyone 
letting me know different).  So, in the MVPMC, I see shows
on channels on sources that have the visible set to 0.

That's about all I do with my mvpmc.  I don't use it for livetv, so
I didn't test that.  I also don't use it for music, so I didn't test
that either.

-----Original Message-----
From: Brian J. Murrell [mailto:br...@in...] 
Sent: Wednesday, November 14, 2012 8:45 PM
To: mvp...@li...
Subject: Re: [Mvpmc-devel] New Dongle

On 12-11-13 08:28 AM, Brian J. Murrell wrote:
> On 12-10-02 04:36 PM, Bernhard Geier wrote:
>>
>> I only tested the dongle for a few minutes up to now, watching and 
>> deleting recordings works, at least with my MythTV 0.24 backend,
> 
> Has it held up in 0.24 testing?
> ...
> More interestingly, has anyone given this dongle any solid testing 
> with 0.25?

Has nobody at all done any testing of this (or any of the later Bernhard
produced) dongle(s) on 0.24 or 0.25 and would like to report their results?  Really just interested in solid playback with functional commercial skip, again, ideally on 0.25 so that I don't have to roll my own 0.24 on Ubuntu 12.04.

Maybe it's time to retire these old MVPMCs.  :-(

Cheers,
b.

Re: [Mvpmc-devel] New Dongle

[Charles B. <cgb...@gm...>]

On Nov 15, 2012 3:46 AM, "Brian J. Murrell" <br...@in...> wrote:

>
> Has nobody at all done any testing of this (or any of the later Bernhard
> produced) dongle(s) on 0.24 or 0.25 and would like to report their
> results?  Really just interested in solid playback with functional
> commercial skip, again, ideally on 0.25 so that I don't have to roll my
> own 0.24 on Ubuntu 12.04.

I've been using it for a while, but just on 0.24 which was working with
previous dongles anyway.  I'm planning to install a test 0.25 system and
I'll provide feedback once I have.

>
> Maybe it's time to retire these old MVPMCs.  :-(
>

My raspberry pi running xbmc works well with 0.24, and I am sure will with
0.25 too.  I haven't got mythbox plugin working so don't have full
functionality and it is significantly slower than the MVPMC box.

Charles.