Mailing List Archive

On 7/12/20 2:05 AM, BP wrote:
> On 7/9/20 6:35 PM, John P Poet wrote:
>
>>
>>     I thought the HDPVR2 was not Myth compatible.  Has that changed?
>>
>>
>> https://github.com/jpoet/HauppaugeUSB
>>
>
> Do you know if the HDPVR2 is working with 1080P over component? My
> cable box has recently decided to keep resetting to 1080P from 1080i
> which creates failed recordings with the HDPVR.
>
My box literally stinks to high heaven, due to a refrigerator failure.
Hint: please do describe your box and environment, otherwise, one could
be mislead in terminology from a spouse or partner with a yeast or
bacterial genital infection to a big box store central computing matrix.

And Myth and anything else is *never* complete, not even Windows,
OSX-whatever, it's always advancing.

Describe the problem more fully, include failure logs, your general
environment (your specific IP isn't good, a network described without an
IP is good), then you can get help.
Currently, your plea for help is like a global plea for help in a house
fire, entirely omitting the continent, let alone the country that you
live in.

>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Sat, Jul 11, 2020 at 11:05 PM BP <lists@qucae.com> wrote:

> On 7/9/20 6:35 PM, John P Poet wrote:
>
> >
> > I thought the HDPVR2 was not Myth compatible. Has that changed?
> >
> >
> > https://github.com/jpoet/HauppaugeUSB
> >
>
> Do you know if the HDPVR2 is working with 1080P over component? My
> cable box has recently decided to keep resetting to 1080P from 1080i
> which creates failed recordings with the HDPVR.
>

The one I just got has no component video inputs, just HDMI.

On Wed, Jul 15, 2020 at 9:13 PM DryHeat122 <dryheat122@gmail.com> wrote:

>
>
> On Sat, Jul 11, 2020 at 11:05 PM BP <lists@qucae.com> wrote:
>
>> On 7/9/20 6:35 PM, John P Poet wrote:
>>
>> >
>> > I thought the HDPVR2 was not Myth compatible. Has that changed?
>> >
>> >
>> > https://github.com/jpoet/HauppaugeUSB
>> >
>>
>> Do you know if the HDPVR2 is working with 1080P over component? My
>> cable box has recently decided to keep resetting to 1080P from 1080i
>> which creates failed recordings with the HDPVR.
>>
>
> The one I just got has no component video inputs, just HDMI.
>
But wait! The one I just got is bare bones. The docs say "Note: HD PVR 2
will not record video from HDMI with HDCP copy protection. If you are
recording from a cable or satellite TV box, we have included a set of
Component video cables to connect to your box." So I withdraw my previous
reply, and great now I'm going to have to hunt down this cable.

On Fri, Jul 10, 2020 at 4:12 AM John Hoyt <john.hoyt@gmail.com> wrote:

> That is not for the inexperienced or faint of heart to install and
>> configure. It scares me a little :-) I can't imagine what it was like to
>> develop it!
>>
>
> Configuration is actually not as scary as it looks at first. Also, it was
> quite worth it as I've found my colossus to work with higher reliability
> and better quality than my HDPVR ever did.
>
> If you're running Ubuntu - you can use the compiled binary on my
> Launchpad ppa to skip the compile steps -
> https://launchpad.net/~john-hoyt/+archive/ubuntu/hauppaugeusb
>

I decided to try this with my current Myth setup, and it looks like you
don't have a version for Ubuntu 16.04. So I did the compile myself.
Everything was going great until the very end of the make and I got:

g++ -g -c -Wall -std=c++11 -fdiagnostics-color -DBOOST_LOG_DYN_LINK
-pthread -m64 -g -O3 -D_GNU_SOURCE -DDRIVER_BUILD -DHAUPPAUGE -DHCW_E5BDA
`pkg-config --cflags libusb-1.0` -I.. -I./Hauppauge/Common
-I./Wrappers/linux -I./Hauppauge/Common/FX2API
-I./Hauppauge/Common/Rx/ADV7842 -I./Hauppauge/Common/Rx/ADV7842/RX
-I./Hauppauge/Common/Rx/ADV7842/RX/LIB
-I./Hauppauge/Common/Rx/ADV7842/RX/HAL
-I./Hauppauge/Common/Rx/ADV7842/RX/HAL/4G
-I./Hauppauge/Common/Rx/ADV7842/RX/HAL/4G/ADV7842/HAL
-I./Hauppauge/Common/Rx/ADV7842/RX/HAL/4G/ADV7842/MACROS
-I./Hauppauge/Common/Rx -I./Hauppauge/Common/EncoderDev
-I./Hauppauge/Common/EncoderDev/HAPIHost
-I./Hauppauge/Common/EncoderDev/HAPIHost/MChip `pkg-config --cflags
libusb-1.0` ./Hauppauge/Common/Rx/audio_CS8416.cpp -o audio_CS8416.o
./Hauppauge/Common/Rx/audio_CS8416.cpp: In member function ‘bool
audio_CS8416::DeviceIO::write(audio_CS8416::DeviceIO::Reg, const uint8_t*,
size_t)’:
./Hauppauge/Common/Rx/audio_CS8416.cpp:173:39: error: ‘memcpy’ was not
declared in this scope
memcpy(sendbuff + 1, data, len);
^
Makefile:61: recipe for target 'audio_CS8416.o' failed
make: *** [audio_CS8416.o] Error 1

What to do?

On Wed, Jul 22, 2020 at 9:44 AM DryHeat122 <dryheat122@gmail.com> wrote:

> On Fri, Jul 10, 2020 at 4:12 AM John Hoyt <john.hoyt@gmail.com> wrote:
>
>> That is not for the inexperienced or faint of heart to install and
>>> configure. It scares me a little :-) I can't imagine what it was like to
>>> develop it!
>>>
>>
>> Configuration is actually not as scary as it looks at first. Also, it
>> was quite worth it as I've found my colossus to work with higher
>> reliability and better quality than my HDPVR ever did.
>>
>> If you're running Ubuntu - you can use the compiled binary on my
>> Launchpad ppa to skip the compile steps -
>> https://launchpad.net/~john-hoyt/+archive/ubuntu/hauppaugeusb
>>
>
> I decided to try this with my current Myth setup, and it looks like you
> don't have a version for Ubuntu 16.04. So I did the compile myself.
> Everything was going great until the very end of the make and I got:
>
> g++ -g -c -Wall -std=c++11 -fdiagnostics-color -DBOOST_LOG_DYN_LINK
> -pthread -m64 -g -O3 -D_GNU_SOURCE -DDRIVER_BUILD -DHAUPPAUGE -DHCW_E5BDA
> `pkg-config --cflags libusb-1.0` -I.. -I./Hauppauge/Common
> -I./Wrappers/linux -I./Hauppauge/Common/FX2API
> -I./Hauppauge/Common/Rx/ADV7842 -I./Hauppauge/Common/Rx/ADV7842/RX
> -I./Hauppauge/Common/Rx/ADV7842/RX/LIB
> -I./Hauppauge/Common/Rx/ADV7842/RX/HAL
> -I./Hauppauge/Common/Rx/ADV7842/RX/HAL/4G
> -I./Hauppauge/Common/Rx/ADV7842/RX/HAL/4G/ADV7842/HAL
> -I./Hauppauge/Common/Rx/ADV7842/RX/HAL/4G/ADV7842/MACROS
> -I./Hauppauge/Common/Rx -I./Hauppauge/Common/EncoderDev
> -I./Hauppauge/Common/EncoderDev/HAPIHost
> -I./Hauppauge/Common/EncoderDev/HAPIHost/MChip `pkg-config --cflags
> libusb-1.0` ./Hauppauge/Common/Rx/audio_CS8416.cpp -o audio_CS8416.o
> ./Hauppauge/Common/Rx/audio_CS8416.cpp: In member function ‘bool
> audio_CS8416::DeviceIO::write(audio_CS8416::DeviceIO::Reg, const uint8_t*,
> size_t)’:
> ./Hauppauge/Common/Rx/audio_CS8416.cpp:173:39: error: ‘memcpy’ was not
> declared in this scope
> memcpy(sendbuff + 1, data, len);
> ^
> Makefile:61: recipe for target 'audio_CS8416.o' failed
> make: *** [audio_CS8416.o] Error 1
>
> What to do?
>

I know next to nothing about cpp but I looked up the error, and it seems to
be caused by failure to declare #include <cstring> I added that to the top
of audio_CS8416.cpp and the build completed without errors.
Perhaps @JohnPoet would like to add this to the patches?

Bottom line is that I now have it working. Here are a couple of notes for
others trying this:

When I first connected the HDPVR2 the light was rapid flashing blue which
according to docs means the machine can't "see" it. When I tried to record
I got a repeated error:

2020-07-22T12:15:53.632520 ERRR <main> USBif.cpp:485 (controlMessage)
cannot send control message: No such device (it may have been disconnected)

But after exiting the commsn the light was solid blue. So I tried again
and got

2020-07-22T12:16:42.638981 CRIT <main> Logger.cpp:83 (setLogLevelFilter)
Changing loglevel to NOTC
2020-07-22T12:16:42.639124 CRIT <main> hauppauge2.cpp:347 (main) Starting up
2020-07-22T12:16:42.650486 CRIT <main> hauppauge2.cpp:360 (main)
Initializing [Bus: 2, Port: 6] E524-00-00ABAE4A
[long pause]
2020-07-22T12:17:05.061224 CRIT <main> HauppaugeDev.cpp:392
(init_component) Cannot determine video mode.
2020-07-22T12:17:05.362389 CRIT <main> hauppauge2.cpp:476 (main) Done.

I discovered that the second to last error means there is no video signal.
My cable box was off. After turning it on I got a recording.

For the devs, I did get one error:

2020-07-22T12:50:50.152620 ERRR <main> FX2Device.cpp:115 (I2CWriteRead)
I2C: Improper answer: status 07

I don't know what it means, but it didn't prevent the recording.

Thanks for all the help everyone!

>
> I decided to try this with my current Myth setup, and it looks like you
> don't have a version for Ubuntu 16.04.
>

Correct - sorry about that. Unfortunately launchpad blocks the upload for
no longer supported versions of Ubuntu. I used to have a Xenial
build posted, but dropped it when I ran out of space in launchpad.

On Wed, Jul 22, 2020 at 1:07 PM DryHeat122 <dryheat122@gmail.com> wrote:

>
>
> On Wed, Jul 22, 2020 at 9:44 AM DryHeat122 <dryheat122@gmail.com> wrote:
>
>> On Fri, Jul 10, 2020 at 4:12 AM John Hoyt <john.hoyt@gmail.com> wrote:
>>
>>> That is not for the inexperienced or faint of heart to install and
>>>> configure. It scares me a little :-) I can't imagine what it was like to
>>>> develop it!
>>>>
>>>
>>> Configuration is actually not as scary as it looks at first. Also, it
>>> was quite worth it as I've found my colossus to work with higher
>>> reliability and better quality than my HDPVR ever did.
>>>
>>> If you're running Ubuntu - you can use the compiled binary on my
>>> Launchpad ppa to skip the compile steps -
>>> https://launchpad.net/~john-hoyt/+archive/ubuntu/hauppaugeusb
>>>
>>
>> I decided to try this with my current Myth setup, and it looks like you
>> don't have a version for Ubuntu 16.04. So I did the compile myself.
>> Everything was going great until the very end of the make and I got:
>>
>> g++ -g -c -Wall -std=c++11 -fdiagnostics-color -DBOOST_LOG_DYN_LINK
>> -pthread -m64 -g -O3 -D_GNU_SOURCE -DDRIVER_BUILD -DHAUPPAUGE -DHCW_E5BDA
>> `pkg-config --cflags libusb-1.0` -I.. -I./Hauppauge/Common
>> -I./Wrappers/linux -I./Hauppauge/Common/FX2API
>> -I./Hauppauge/Common/Rx/ADV7842 -I./Hauppauge/Common/Rx/ADV7842/RX
>> -I./Hauppauge/Common/Rx/ADV7842/RX/LIB
>> -I./Hauppauge/Common/Rx/ADV7842/RX/HAL
>> -I./Hauppauge/Common/Rx/ADV7842/RX/HAL/4G
>> -I./Hauppauge/Common/Rx/ADV7842/RX/HAL/4G/ADV7842/HAL
>> -I./Hauppauge/Common/Rx/ADV7842/RX/HAL/4G/ADV7842/MACROS
>> -I./Hauppauge/Common/Rx -I./Hauppauge/Common/EncoderDev
>> -I./Hauppauge/Common/EncoderDev/HAPIHost
>> -I./Hauppauge/Common/EncoderDev/HAPIHost/MChip `pkg-config --cflags
>> libusb-1.0` ./Hauppauge/Common/Rx/audio_CS8416.cpp -o audio_CS8416.o
>> ./Hauppauge/Common/Rx/audio_CS8416.cpp: In member function ‘bool
>> audio_CS8416::DeviceIO::write(audio_CS8416::DeviceIO::Reg, const uint8_t*,
>> size_t)’:
>> ./Hauppauge/Common/Rx/audio_CS8416.cpp:173:39: error: ‘memcpy’ was not
>> declared in this scope
>> memcpy(sendbuff + 1, data, len);
>> ^
>> Makefile:61: recipe for target 'audio_CS8416.o' failed
>> make: *** [audio_CS8416.o] Error 1
>>
>> What to do?
>>
>
> I know next to nothing about cpp but I looked up the error, and it seems
> to be caused by failure to declare #include <cstring> I added that to the
> top of audio_CS8416.cpp and the build completed without errors.
> Perhaps @JohnPoet would like to add this to the patches?
>
> Bottom line is that I now have it working. Here are a couple of notes for
> others trying this:
>
> When I first connected the HDPVR2 the light was rapid flashing blue which
> according to docs means the machine can't "see" it. When I tried to record
> I got a repeated error:
>
> 2020-07-22T12:15:53.632520 ERRR <main> USBif.cpp:485 (controlMessage)
> cannot send control message: No such device (it may have been disconnected)
>
> But after exiting the commsn the light was solid blue. So I tried again
> and got
>
> 2020-07-22T12:16:42.638981 CRIT <main> Logger.cpp:83 (setLogLevelFilter)
> Changing loglevel to NOTC
> 2020-07-22T12:16:42.639124 CRIT <main> hauppauge2.cpp:347 (main) Starting
> up
> 2020-07-22T12:16:42.650486 CRIT <main> hauppauge2.cpp:360 (main)
> Initializing [Bus: 2, Port: 6] E524-00-00ABAE4A
> [long pause]
> 2020-07-22T12:17:05.061224 CRIT <main> HauppaugeDev.cpp:392
> (init_component) Cannot determine video mode.
> 2020-07-22T12:17:05.362389 CRIT <main> hauppauge2.cpp:476 (main) Done.
>
> I discovered that the second to last error means there is no video
> signal. My cable box was off. After turning it on I got a recording.
>
> For the devs, I did get one error:
>
> 2020-07-22T12:50:50.152620 ERRR <main> FX2Device.cpp:115 (I2CWriteRead)
> I2C: Improper answer: status 07
>
> I don't know what it means, but it didn't prevent the recording.
>
> Thanks for all the help everyone!
>

Sooooo...having the HDPVR2 making test recordings, I set it up in Myth per
the instructions in the https://github.com/jpoet/HauppaugeUSB. When I try
to record anything, say from the program guide, it says "recorder offline"
and I can find nothing in the frontend or backend logs about it. However,
the recorder shows the half-green lite indicating it's ready and I can
still do test recordings. How to troubleshoot?

On Wed, Jul 22, 2020 at 5:12 PM DryHeat122 <dryheat122@gmail.com> wrote:

>
>
> On Wed, Jul 22, 2020 at 1:07 PM DryHeat122 <dryheat122@gmail.com> wrote:
>
>>
>>
>> On Wed, Jul 22, 2020 at 9:44 AM DryHeat122 <dryheat122@gmail.com> wrote:
>>
>>> On Fri, Jul 10, 2020 at 4:12 AM John Hoyt <john.hoyt@gmail.com> wrote:
>>>
>>>> That is not for the inexperienced or faint of heart to install and
>>>>> configure. It scares me a little :-) I can't imagine what it was like to
>>>>> develop it!
>>>>>
>>>>
>>>> Configuration is actually not as scary as it looks at first. Also, it
>>>> was quite worth it as I've found my colossus to work with higher
>>>> reliability and better quality than my HDPVR ever did.
>>>>
>>>> If you're running Ubuntu - you can use the compiled binary on my
>>>> Launchpad ppa to skip the compile steps -
>>>> https://launchpad.net/~john-hoyt/+archive/ubuntu/hauppaugeusb
>>>>
>>>
>>> I decided to try this with my current Myth setup, and it looks like you
>>> don't have a version for Ubuntu 16.04. So I did the compile myself.
>>> Everything was going great until the very end of the make and I got:
>>>
>>> g++ -g -c -Wall -std=c++11 -fdiagnostics-color -DBOOST_LOG_DYN_LINK
>>> -pthread -m64 -g -O3 -D_GNU_SOURCE -DDRIVER_BUILD -DHAUPPAUGE -DHCW_E5BDA
>>> `pkg-config --cflags libusb-1.0` -I.. -I./Hauppauge/Common
>>> -I./Wrappers/linux -I./Hauppauge/Common/FX2API
>>> -I./Hauppauge/Common/Rx/ADV7842 -I./Hauppauge/Common/Rx/ADV7842/RX
>>> -I./Hauppauge/Common/Rx/ADV7842/RX/LIB
>>> -I./Hauppauge/Common/Rx/ADV7842/RX/HAL
>>> -I./Hauppauge/Common/Rx/ADV7842/RX/HAL/4G
>>> -I./Hauppauge/Common/Rx/ADV7842/RX/HAL/4G/ADV7842/HAL
>>> -I./Hauppauge/Common/Rx/ADV7842/RX/HAL/4G/ADV7842/MACROS
>>> -I./Hauppauge/Common/Rx -I./Hauppauge/Common/EncoderDev
>>> -I./Hauppauge/Common/EncoderDev/HAPIHost
>>> -I./Hauppauge/Common/EncoderDev/HAPIHost/MChip `pkg-config --cflags
>>> libusb-1.0` ./Hauppauge/Common/Rx/audio_CS8416.cpp -o audio_CS8416.o
>>> ./Hauppauge/Common/Rx/audio_CS8416.cpp: In member function ‘bool
>>> audio_CS8416::DeviceIO::write(audio_CS8416::DeviceIO::Reg, const uint8_t*,
>>> size_t)’:
>>> ./Hauppauge/Common/Rx/audio_CS8416.cpp:173:39: error: ‘memcpy’ was not
>>> declared in this scope
>>> memcpy(sendbuff + 1, data, len);
>>> ^
>>> Makefile:61: recipe for target 'audio_CS8416.o' failed
>>> make: *** [audio_CS8416.o] Error 1
>>>
>>> What to do?
>>>
>>
>> I know next to nothing about cpp but I looked up the error, and it seems
>> to be caused by failure to declare #include <cstring> I added that to the
>> top of audio_CS8416.cpp and the build completed without errors.
>> Perhaps @JohnPoet would like to add this to the patches?
>>
>> Bottom line is that I now have it working. Here are a couple of notes
>> for others trying this:
>>
>> When I first connected the HDPVR2 the light was rapid flashing blue which
>> according to docs means the machine can't "see" it. When I tried to record
>> I got a repeated error:
>>
>> 2020-07-22T12:15:53.632520 ERRR <main> USBif.cpp:485 (controlMessage)
>> cannot send control message: No such device (it may have been disconnected)
>>
>> But after exiting the commsn the light was solid blue. So I tried again
>> and got
>>
>> 2020-07-22T12:16:42.638981 CRIT <main> Logger.cpp:83 (setLogLevelFilter)
>> Changing loglevel to NOTC
>> 2020-07-22T12:16:42.639124 CRIT <main> hauppauge2.cpp:347 (main) Starting
>> up
>> 2020-07-22T12:16:42.650486 CRIT <main> hauppauge2.cpp:360 (main)
>> Initializing [Bus: 2, Port: 6] E524-00-00ABAE4A
>> [long pause]
>> 2020-07-22T12:17:05.061224 CRIT <main> HauppaugeDev.cpp:392
>> (init_component) Cannot determine video mode.
>> 2020-07-22T12:17:05.362389 CRIT <main> hauppauge2.cpp:476 (main) Done.
>>
>> I discovered that the second to last error means there is no video
>> signal. My cable box was off. After turning it on I got a recording.
>>
>> For the devs, I did get one error:
>>
>> 2020-07-22T12:50:50.152620 ERRR <main> FX2Device.cpp:115 (I2CWriteRead)
>> I2C: Improper answer: status 07
>>
>> I don't know what it means, but it didn't prevent the recording.
>>
>> Thanks for all the help everyone!
>>
>
> Sooooo...having the HDPVR2 making test recordings, I set it up in Myth per
> the instructions in the https://github.com/jpoet/HauppaugeUSB. When I
> try to record anything, say from the program guide, it says "recorder
> offline" and I can find nothing in the frontend or backend logs about it.
> However, the recorder shows the half-green lite indicating it's ready and I
> can still do test recordings. How to troubleshoot?
>

My first guess would be a permission problem. The HD-PVR2 externalrecorder
process will run as the same user as mythbackend. If that user does not
have permission to write its log file, for example, it will fail.

Run mythbackend with "-v channel,record", if you are not already. The
mythbackend log should show the reason for the error.

John

That was it...I had the wrong group in the config file. Now Myth no longer
says the recorder is offline, the recordings are merely failing. So that's
progress?

I think it might be failing because my channel changer is failing, and that
is because my FireWire seems to be hosed. plugreport returns nothing,
firewire_tester can't connect to any port.

This is bizarre because FireWire and the channel changer was working until
I started the recorder changeover this morning. Can you think of any reason
the HDPVR2 software would affect FireWire?

On Wed, Jul 22, 2020, 5:31 PM John P Poet <jppoet@gmail.com> wrote:

> On Wed, Jul 22, 2020 at 5:12 PM DryHeat122 <dryheat122@gmail.com> wrote:
>
>>
>>
>> On Wed, Jul 22, 2020 at 1:07 PM DryHeat122 <dryheat122@gmail.com> wrote:
>>
>>>
>>>
>>> On Wed, Jul 22, 2020 at 9:44 AM DryHeat122 <dryheat122@gmail.com> wrote:
>>>
>>>> On Fri, Jul 10, 2020 at 4:12 AM John Hoyt <john.hoyt@gmail.com> wrote:
>>>>
>>>>> That is not for the inexperienced or faint of heart to install and
>>>>>> configure. It scares me a little :-) I can't imagine what it was like to
>>>>>> develop it!
>>>>>>
>>>>>
>>>>> Configuration is actually not as scary as it looks at first. Also, it
>>>>> was quite worth it as I've found my colossus to work with higher
>>>>> reliability and better quality than my HDPVR ever did.
>>>>>
>>>>> If you're running Ubuntu - you can use the compiled binary on my
>>>>> Launchpad ppa to skip the compile steps -
>>>>> https://launchpad.net/~john-hoyt/+archive/ubuntu/hauppaugeusb
>>>>>
>>>>
>>>> I decided to try this with my current Myth setup, and it looks like you
>>>> don't have a version for Ubuntu 16.04. So I did the compile myself.
>>>> Everything was going great until the very end of the make and I got:
>>>>
>>>> g++ -g -c -Wall -std=c++11 -fdiagnostics-color -DBOOST_LOG_DYN_LINK
>>>> -pthread -m64 -g -O3 -D_GNU_SOURCE -DDRIVER_BUILD -DHAUPPAUGE -DHCW_E5BDA
>>>> `pkg-config --cflags libusb-1.0` -I.. -I./Hauppauge/Common
>>>> -I./Wrappers/linux -I./Hauppauge/Common/FX2API
>>>> -I./Hauppauge/Common/Rx/ADV7842 -I./Hauppauge/Common/Rx/ADV7842/RX
>>>> -I./Hauppauge/Common/Rx/ADV7842/RX/LIB
>>>> -I./Hauppauge/Common/Rx/ADV7842/RX/HAL
>>>> -I./Hauppauge/Common/Rx/ADV7842/RX/HAL/4G
>>>> -I./Hauppauge/Common/Rx/ADV7842/RX/HAL/4G/ADV7842/HAL
>>>> -I./Hauppauge/Common/Rx/ADV7842/RX/HAL/4G/ADV7842/MACROS
>>>> -I./Hauppauge/Common/Rx -I./Hauppauge/Common/EncoderDev
>>>> -I./Hauppauge/Common/EncoderDev/HAPIHost
>>>> -I./Hauppauge/Common/EncoderDev/HAPIHost/MChip `pkg-config --cflags
>>>> libusb-1.0` ./Hauppauge/Common/Rx/audio_CS8416.cpp -o audio_CS8416.o
>>>> ./Hauppauge/Common/Rx/audio_CS8416.cpp: In member function ‘bool
>>>> audio_CS8416::DeviceIO::write(audio_CS8416::DeviceIO::Reg, const uint8_t*,
>>>> size_t)’:
>>>> ./Hauppauge/Common/Rx/audio_CS8416.cpp:173:39: error: ‘memcpy’ was not
>>>> declared in this scope
>>>> memcpy(sendbuff + 1, data, len);
>>>> ^
>>>> Makefile:61: recipe for target 'audio_CS8416.o' failed
>>>> make: *** [audio_CS8416.o] Error 1
>>>>
>>>> What to do?
>>>>
>>>
>>> I know next to nothing about cpp but I looked up the error, and it seems
>>> to be caused by failure to declare #include <cstring> I added that to the
>>> top of audio_CS8416.cpp and the build completed without errors.
>>> Perhaps @JohnPoet would like to add this to the patches?
>>>
>>> Bottom line is that I now have it working. Here are a couple of notes
>>> for others trying this:
>>>
>>> When I first connected the HDPVR2 the light was rapid flashing blue
>>> which according to docs means the machine can't "see" it. When I tried to
>>> record I got a repeated error:
>>>
>>> 2020-07-22T12:15:53.632520 ERRR <main> USBif.cpp:485 (controlMessage)
>>> cannot send control message: No such device (it may have been disconnected)
>>>
>>> But after exiting the commsn the light was solid blue. So I tried again
>>> and got
>>>
>>> 2020-07-22T12:16:42.638981 CRIT <main> Logger.cpp:83 (setLogLevelFilter)
>>> Changing loglevel to NOTC
>>> 2020-07-22T12:16:42.639124 CRIT <main> hauppauge2.cpp:347 (main)
>>> Starting up
>>> 2020-07-22T12:16:42.650486 CRIT <main> hauppauge2.cpp:360 (main)
>>> Initializing [Bus: 2, Port: 6] E524-00-00ABAE4A
>>> [long pause]
>>> 2020-07-22T12:17:05.061224 CRIT <main> HauppaugeDev.cpp:392
>>> (init_component) Cannot determine video mode.
>>> 2020-07-22T12:17:05.362389 CRIT <main> hauppauge2.cpp:476 (main) Done.
>>>
>>> I discovered that the second to last error means there is no video
>>> signal. My cable box was off. After turning it on I got a recording.
>>>
>>> For the devs, I did get one error:
>>>
>>> 2020-07-22T12:50:50.152620 ERRR <main> FX2Device.cpp:115 (I2CWriteRead)
>>> I2C: Improper answer: status 07
>>>
>>> I don't know what it means, but it didn't prevent the recording.
>>>
>>> Thanks for all the help everyone!
>>>
>>
>> Sooooo...having the HDPVR2 making test recordings, I set it up in Myth
>> per the instructions in the https://github.com/jpoet/HauppaugeUSB. When
>> I try to record anything, say from the program guide, it says "recorder
>> offline" and I can find nothing in the frontend or backend logs about it.
>> However, the recorder shows the half-green lite indicating it's ready and I
>> can still do test recordings. How to troubleshoot?
>>
>
> My first guess would be a permission problem. The HD-PVR2 externalrecorder
> process will run as the same user as mythbackend. If that user does not
> have permission to write its log file, for example, it will fail.
>
> Run mythbackend with "-v channel,record", if you are not already. The
> mythbackend log should show the reason for the error.
>
> John
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>

After successfully building this on my Ubuntu 16.04 box, I tried building
it again on my new 20.04 box. This time I got the following errors when
running make:

../../Common/EncoderDev/encoderDev_DXT.cpp: In destructor 'virtual
encoderDev_DXT_t::~encoderDev_DXT_t()':
../../Common/EncoderDev/encoderDev_DXT.cpp:13:2: error: 'wrapLogInfo' was
not declared in this scope; did you mean 'wrapLogError'?
13 | wrapLogInfo("encoderDev_DXT_t::~encoderDev_DXT_t()");
| ^~~~~~~~~~~
| wrapLogError
../../Common/EncoderDev/encoderDev_DXT.cpp: In member function 'virtual
bool encoderDev_DXT_t::init()':
../../Common/EncoderDev/encoderDev_DXT.cpp:24:2: error: 'wrapLogInfo' was
not declared in this scope; did you mean 'wrapLogError'?
24 | wrapLogInfo("encoderDev_DXT_t::init()");
| ^~~~~~~~~~~
| wrapLogError
../../Common/EncoderDev/encoderDev_DXT.cpp: In member function 'virtual
bool encoderDev_DXT_t::startCapture()':
../../Common/EncoderDev/encoderDev_DXT.cpp:183:2: error: 'wrapLogInfo' was
not declared in this scope; did you mean 'wrapLogError'?
183 | wrapLogInfo("encoderDev_DXT_t::startCapture()");
| ^~~~~~~~~~~
| wrapLogError
../../Common/EncoderDev/encoderDev_DXT.cpp: In member function 'virtual
bool encoderDev_DXT_t::stopCapture()':
../../Common/EncoderDev/encoderDev_DXT.cpp:190:2: error: 'wrapLogInfo' was
not declared in this scope; did you mean 'wrapLogError'?
190 | wrapLogInfo("encoderDev_DXT_t::stopCapture()");
| ^~~~~~~~~~~
| wrapLogError
make[1]: *** [<builtin>: encoderDev_DXT.o] Error 1
make[1]: Leaving directory
'/home/steve/src/Hauppauge/hauppauge_hdpvr2_157321_patched_2016-09-26/TestApp/build-ADV7842'
make: *** [Makefile:2: all] Error 2

How to fix? Change wrapLogInfo to wrapLogError as suggested?

On Wed, Jul 22, 2020 at 5:47 PM DryHeat122 <dryheat122@gmail.com> wrote:

> That was it...I had the wrong group in the config file. Now Myth no
> longer says the recorder is offline, the recordings are merely failing. So
> that's progress?
>
> I think it might be failing because my channel changer is failing, and
> that is because my FireWire seems to be hosed. plugreport returns nothing,
> firewire_tester can't connect to any port.
>
> This is bizarre because FireWire and the channel changer was working until
> I started the recorder changeover this morning. Can you think of any reason
> the HDPVR2 software would affect FireWire?
>
> On Wed, Jul 22, 2020, 5:31 PM John P Poet <jppoet@gmail.com> wrote:
>
>> On Wed, Jul 22, 2020 at 5:12 PM DryHeat122 <dryheat122@gmail.com> wrote:
>>
>>>
>>>
>>> On Wed, Jul 22, 2020 at 1:07 PM DryHeat122 <dryheat122@gmail.com> wrote:
>>>
>>>>
>>>>
>>>> On Wed, Jul 22, 2020 at 9:44 AM DryHeat122 <dryheat122@gmail.com>
>>>> wrote:
>>>>
>>>>> On Fri, Jul 10, 2020 at 4:12 AM John Hoyt <john.hoyt@gmail.com> wrote:
>>>>>
>>>>>> That is not for the inexperienced or faint of heart to install and
>>>>>>> configure. It scares me a little :-) I can't imagine what it was like to
>>>>>>> develop it!
>>>>>>>
>>>>>>
>>>>>> Configuration is actually not as scary as it looks at first. Also,
>>>>>> it was quite worth it as I've found my colossus to work with higher
>>>>>> reliability and better quality than my HDPVR ever did.
>>>>>>
>>>>>> If you're running Ubuntu - you can use the compiled binary on my
>>>>>> Launchpad ppa to skip the compile steps -
>>>>>> https://launchpad.net/~john-hoyt/+archive/ubuntu/hauppaugeusb
>>>>>>
>>>>>
>>>>> I decided to try this with my current Myth setup, and it looks like
>>>>> you don't have a version for Ubuntu 16.04. So I did the compile myself.
>>>>> Everything was going great until the very end of the make and I got:
>>>>>
>>>>> g++ -g -c -Wall -std=c++11 -fdiagnostics-color -DBOOST_LOG_DYN_LINK
>>>>> -pthread -m64 -g -O3 -D_GNU_SOURCE -DDRIVER_BUILD -DHAUPPAUGE -DHCW_E5BDA
>>>>> `pkg-config --cflags libusb-1.0` -I.. -I./Hauppauge/Common
>>>>> -I./Wrappers/linux -I./Hauppauge/Common/FX2API
>>>>> -I./Hauppauge/Common/Rx/ADV7842 -I./Hauppauge/Common/Rx/ADV7842/RX
>>>>> -I./Hauppauge/Common/Rx/ADV7842/RX/LIB
>>>>> -I./Hauppauge/Common/Rx/ADV7842/RX/HAL
>>>>> -I./Hauppauge/Common/Rx/ADV7842/RX/HAL/4G
>>>>> -I./Hauppauge/Common/Rx/ADV7842/RX/HAL/4G/ADV7842/HAL
>>>>> -I./Hauppauge/Common/Rx/ADV7842/RX/HAL/4G/ADV7842/MACROS
>>>>> -I./Hauppauge/Common/Rx -I./Hauppauge/Common/EncoderDev
>>>>> -I./Hauppauge/Common/EncoderDev/HAPIHost
>>>>> -I./Hauppauge/Common/EncoderDev/HAPIHost/MChip `pkg-config --cflags
>>>>> libusb-1.0` ./Hauppauge/Common/Rx/audio_CS8416.cpp -o audio_CS8416.o
>>>>> ./Hauppauge/Common/Rx/audio_CS8416.cpp: In member function ‘bool
>>>>> audio_CS8416::DeviceIO::write(audio_CS8416::DeviceIO::Reg, const uint8_t*,
>>>>> size_t)’:
>>>>> ./Hauppauge/Common/Rx/audio_CS8416.cpp:173:39: error: ‘memcpy’ was not
>>>>> declared in this scope
>>>>> memcpy(sendbuff + 1, data, len);
>>>>> ^
>>>>> Makefile:61: recipe for target 'audio_CS8416.o' failed
>>>>> make: *** [audio_CS8416.o] Error 1
>>>>>
>>>>> What to do?
>>>>>
>>>>
>>>> I know next to nothing about cpp but I looked up the error, and it
>>>> seems to be caused by failure to declare #include <cstring> I added that
>>>> to the top of audio_CS8416.cpp and the build completed without errors.
>>>> Perhaps @JohnPoet would like to add this to the patches?
>>>>
>>>> Bottom line is that I now have it working. Here are a couple of notes
>>>> for others trying this:
>>>>
>>>> When I first connected the HDPVR2 the light was rapid flashing blue
>>>> which according to docs means the machine can't "see" it. When I tried to
>>>> record I got a repeated error:
>>>>
>>>> 2020-07-22T12:15:53.632520 ERRR <main> USBif.cpp:485 (controlMessage)
>>>> cannot send control message: No such device (it may have been disconnected)
>>>>
>>>> But after exiting the commsn the light was solid blue. So I tried
>>>> again and got
>>>>
>>>> 2020-07-22T12:16:42.638981 CRIT <main> Logger.cpp:83
>>>> (setLogLevelFilter) Changing loglevel to NOTC
>>>> 2020-07-22T12:16:42.639124 CRIT <main> hauppauge2.cpp:347 (main)
>>>> Starting up
>>>> 2020-07-22T12:16:42.650486 CRIT <main> hauppauge2.cpp:360 (main)
>>>> Initializing [Bus: 2, Port: 6] E524-00-00ABAE4A
>>>> [long pause]
>>>> 2020-07-22T12:17:05.061224 CRIT <main> HauppaugeDev.cpp:392
>>>> (init_component) Cannot determine video mode.
>>>> 2020-07-22T12:17:05.362389 CRIT <main> hauppauge2.cpp:476 (main) Done.
>>>>
>>>> I discovered that the second to last error means there is no video
>>>> signal. My cable box was off. After turning it on I got a recording.
>>>>
>>>> For the devs, I did get one error:
>>>>
>>>> 2020-07-22T12:50:50.152620 ERRR <main> FX2Device.cpp:115 (I2CWriteRead)
>>>> I2C: Improper answer: status 07
>>>>
>>>> I don't know what it means, but it didn't prevent the recording.
>>>>
>>>> Thanks for all the help everyone!
>>>>
>>>
>>> Sooooo...having the HDPVR2 making test recordings, I set it up in Myth
>>> per the instructions in the https://github.com/jpoet/HauppaugeUSB.
>>> When I try to record anything, say from the program guide, it says
>>> "recorder offline" and I can find nothing in the frontend or backend logs
>>> about it. However, the recorder shows the half-green lite indicating it's
>>> ready and I can still do test recordings. How to troubleshoot?
>>>
>>
>> My first guess would be a permission problem. The HD-PVR2
>> externalrecorder process will run as the same user as mythbackend. If that
>> user does not have permission to write its log file, for example, it will
>> fail.
>>
>> Run mythbackend with "-v channel,record", if you are not already. The
>> mythbackend log should show the reason for the error.
>>
>> John
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users@mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>>
>

On Sat, Jul 25, 2020 at 9:46 AM DryHeat122 <dryheat122@gmail.com> wrote:

> After successfully building this on my Ubuntu 16.04 box, I tried building
> it again on my new 20.04 box. This time I got the following errors when
> running make:
>
> ../../Common/EncoderDev/encoderDev_DXT.cpp: In destructor 'virtual
> encoderDev_DXT_t::~encoderDev_DXT_t()':
> ../../Common/EncoderDev/encoderDev_DXT.cpp:13:2: error: 'wrapLogInfo' was
> not declared in this scope; did you mean 'wrapLogError'?
> 13 | wrapLogInfo("encoderDev_DXT_t::~encoderDev_DXT_t()");
> | ^~~~~~~~~~~
> | wrapLogError
> ../../Common/EncoderDev/encoderDev_DXT.cpp: In member function 'virtual
> bool encoderDev_DXT_t::init()':
> ../../Common/EncoderDev/encoderDev_DXT.cpp:24:2: error: 'wrapLogInfo' was
> not declared in this scope; did you mean 'wrapLogError'?
> 24 | wrapLogInfo("encoderDev_DXT_t::init()");
> | ^~~~~~~~~~~
> | wrapLogError
> ../../Common/EncoderDev/encoderDev_DXT.cpp: In member function 'virtual
> bool encoderDev_DXT_t::startCapture()':
> ../../Common/EncoderDev/encoderDev_DXT.cpp:183:2: error: 'wrapLogInfo' was
> not declared in this scope; did you mean 'wrapLogError'?
> 183 | wrapLogInfo("encoderDev_DXT_t::startCapture()");
> | ^~~~~~~~~~~
> | wrapLogError
> ../../Common/EncoderDev/encoderDev_DXT.cpp: In member function 'virtual
> bool encoderDev_DXT_t::stopCapture()':
> ../../Common/EncoderDev/encoderDev_DXT.cpp:190:2: error: 'wrapLogInfo' was
> not declared in this scope; did you mean 'wrapLogError'?
> 190 | wrapLogInfo("encoderDev_DXT_t::stopCapture()");
> | ^~~~~~~~~~~
> | wrapLogError
> make[1]: *** [<builtin>: encoderDev_DXT.o] Error 1
> make[1]: Leaving directory
> '/home/steve/src/Hauppauge/hauppauge_hdpvr2_157321_patched_2016-09-26/TestApp/build-ADV7842'
> make: *** [Makefile:2: all] Error 2
>
> How to fix? Change wrapLogInfo to wrapLogError as suggested?
>

When you built it on 20.04, did you start from scratch? If not, I would
give that a try as it is possible the layers of patches are causing an
issue.
If you already did start from scratch, you may need to wait for another
ubuntu user to step up and help as it may be an issue with the base OS.

John

If by "start from scratch" you mean follow the instructions on your git
page, yes I did that. Do you know if it works as-is on 18.04, because I am
not so far along in the process I couldn't bail out and install that
instead.

On Sat, Jul 25, 2020 at 10:47 AM John P Poet <jppoet@gmail.com> wrote:

> On Sat, Jul 25, 2020 at 9:46 AM DryHeat122 <dryheat122@gmail.com> wrote:
>
>> After successfully building this on my Ubuntu 16.04 box, I tried building
>> it again on my new 20.04 box. This time I got the following errors when
>> running make:
>>
>> ../../Common/EncoderDev/encoderDev_DXT.cpp: In destructor 'virtual
>> encoderDev_DXT_t::~encoderDev_DXT_t()':
>> ../../Common/EncoderDev/encoderDev_DXT.cpp:13:2: error: 'wrapLogInfo' was
>> not declared in this scope; did you mean 'wrapLogError'?
>> 13 | wrapLogInfo("encoderDev_DXT_t::~encoderDev_DXT_t()");
>> | ^~~~~~~~~~~
>> | wrapLogError
>> ../../Common/EncoderDev/encoderDev_DXT.cpp: In member function 'virtual
>> bool encoderDev_DXT_t::init()':
>> ../../Common/EncoderDev/encoderDev_DXT.cpp:24:2: error: 'wrapLogInfo' was
>> not declared in this scope; did you mean 'wrapLogError'?
>> 24 | wrapLogInfo("encoderDev_DXT_t::init()");
>> | ^~~~~~~~~~~
>> | wrapLogError
>> ../../Common/EncoderDev/encoderDev_DXT.cpp: In member function 'virtual
>> bool encoderDev_DXT_t::startCapture()':
>> ../../Common/EncoderDev/encoderDev_DXT.cpp:183:2: error: 'wrapLogInfo'
>> was not declared in this scope; did you mean 'wrapLogError'?
>> 183 | wrapLogInfo("encoderDev_DXT_t::startCapture()");
>> | ^~~~~~~~~~~
>> | wrapLogError
>> ../../Common/EncoderDev/encoderDev_DXT.cpp: In member function 'virtual
>> bool encoderDev_DXT_t::stopCapture()':
>> ../../Common/EncoderDev/encoderDev_DXT.cpp:190:2: error: 'wrapLogInfo'
>> was not declared in this scope; did you mean 'wrapLogError'?
>> 190 | wrapLogInfo("encoderDev_DXT_t::stopCapture()");
>> | ^~~~~~~~~~~
>> | wrapLogError
>> make[1]: *** [<builtin>: encoderDev_DXT.o] Error 1
>> make[1]: Leaving directory
>> '/home/steve/src/Hauppauge/hauppauge_hdpvr2_157321_patched_2016-09-26/TestApp/build-ADV7842'
>> make: *** [Makefile:2: all] Error 2
>>
>> How to fix? Change wrapLogInfo to wrapLogError as suggested?
>>
>
> When you built it on 20.04, did you start from scratch? If not, I would
> give that a try as it is possible the layers of patches are causing an
> issue.
> If you already did start from scratch, you may need to wait for another
> ubuntu user to step up and help as it may be an issue with the base OS.
>
> John
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>

On Sat, Jul 25, 2020 at 11:52 AM DryHeat122 <dryheat122@gmail.com> wrote:

> If by "start from scratch" you mean follow the instructions on your git
> page, yes I did that. Do you know if it works as-is on 18.04, because I am
> not so far along in the process I couldn't bail out and install that
> instead.
>
> On Sat, Jul 25, 2020 at 10:47 AM John P Poet <jppoet@gmail.com> wrote:
>
>> On Sat, Jul 25, 2020 at 9:46 AM DryHeat122 <dryheat122@gmail.com> wrote:
>>
>>> After successfully building this on my Ubuntu 16.04 box, I tried
>>> building it again on my new 20.04 box. This time I got the following errors
>>> when running make:
>>>
>>> ../../Common/EncoderDev/encoderDev_DXT.cpp: In destructor 'virtual
>>> encoderDev_DXT_t::~encoderDev_DXT_t()':
>>> ../../Common/EncoderDev/encoderDev_DXT.cpp:13:2: error: 'wrapLogInfo'
>>> was not declared in this scope; did you mean 'wrapLogError'?
>>> 13 | wrapLogInfo("encoderDev_DXT_t::~encoderDev_DXT_t()");
>>> | ^~~~~~~~~~~
>>> | wrapLogError
>>> ../../Common/EncoderDev/encoderDev_DXT.cpp: In member function 'virtual
>>> bool encoderDev_DXT_t::init()':
>>> ../../Common/EncoderDev/encoderDev_DXT.cpp:24:2: error: 'wrapLogInfo'
>>> was not declared in this scope; did you mean 'wrapLogError'?
>>> 24 | wrapLogInfo("encoderDev_DXT_t::init()");
>>> | ^~~~~~~~~~~
>>> | wrapLogError
>>> ../../Common/EncoderDev/encoderDev_DXT.cpp: In member function 'virtual
>>> bool encoderDev_DXT_t::startCapture()':
>>> ../../Common/EncoderDev/encoderDev_DXT.cpp:183:2: error: 'wrapLogInfo'
>>> was not declared in this scope; did you mean 'wrapLogError'?
>>> 183 | wrapLogInfo("encoderDev_DXT_t::startCapture()");
>>> | ^~~~~~~~~~~
>>> | wrapLogError
>>> ../../Common/EncoderDev/encoderDev_DXT.cpp: In member function 'virtual
>>> bool encoderDev_DXT_t::stopCapture()':
>>> ../../Common/EncoderDev/encoderDev_DXT.cpp:190:2: error: 'wrapLogInfo'
>>> was not declared in this scope; did you mean 'wrapLogError'?
>>> 190 | wrapLogInfo("encoderDev_DXT_t::stopCapture()");
>>> | ^~~~~~~~~~~
>>> | wrapLogError
>>> make[1]: *** [<builtin>: encoderDev_DXT.o] Error 1
>>> make[1]: Leaving directory
>>> '/home/steve/src/Hauppauge/hauppauge_hdpvr2_157321_patched_2016-09-26/TestApp/build-ADV7842'
>>> make: *** [Makefile:2: all] Error 2
>>>
>>> How to fix? Change wrapLogInfo to wrapLogError as suggested?
>>>
>>
>> When you built it on 20.04, did you start from scratch? If not, I would
>> give that a try as it is possible the layers of patches are causing an
>> issue.
>> If you already did start from scratch, you may need to wait for another
>> ubuntu user to step up and help as it may be an issue with the base OS.
>>
>> John
>>
>
Please do not top-post. Mailing list convention is to bottom post.

I am a Fedora user, but I know this package has been used by Ubuntu users.
I assume it works on 20.04 and 18.04, but I cannot guarantee it.

John

>
> Please do not top-post. Mailing list convention is to bottom post.
>
> I am a Fedora user, but I know this package has been used by Ubuntu users.
> I assume it works on 20.04 and 18.04, but I cannot guarantee it.
>

It works and has been tested on Ubuntu 18.04, 18.10, 19.04, 19.10, and
20.04. I have built in manually and also have it building on launchpad for
all of versions listed.

I successfully compiled following the instructions on jpoet's github site
(literally just copying and pasting) and am able to get it to compile
without any issues.

Steve, unfortunately, I recognize "it works for me" is not what you're
looking for but I suspect it indicates you have either a setup issue
(missing dependencies or are modifying the instructions slightly).

Did you run "sudo apt-get install libboost-log-dev
libboost-program-options-dev libusb-1.0-0-dev build-essential'?

On Sat, Jul 25, 2020 at 11:18 AM John Hoyt <john.hoyt@gmail.com> wrote:

> Please do not top-post. Mailing list convention is to bottom post.
>>
>> I am a Fedora user, but I know this package has been used by Ubuntu
>> users. I assume it works on 20.04 and 18.04, but I cannot guarantee it.
>>
>
> It works and has been tested on Ubuntu 18.04, 18.10, 19.04, 19.10, and
> 20.04. I have built in manually and also have it building on launchpad for
> all of versions listed.
>
> I successfully compiled following the instructions on jpoet's github site
> (literally just copying and pasting) and am able to get it to compile
> without any issues.
>
> Steve, unfortunately, I recognize "it works for me" is not what you're
> looking for but I suspect it indicates you have either a setup issue
> (missing dependencies or are modifying the instructions slightly).
>
> Did you run "sudo apt-get install libboost-log-dev
> libboost-program-options-dev libusb-1.0-0-dev build-essential'?
>

Thanks @JohnPoet and @JohnHoyt, sorry about the earlier top-post. I know
that's the norm but gmail works against it and I just forgot. I will go
through the build process again. Meanwhile @JohnHoyt I have not used
launchpad before. Can you point to instructions for getting your 20.04
build off of there?

>
> Thanks @JohnPoet and @JohnHoyt, sorry about the earlier top-post. I know
> that's the norm but gmail works against it and I just forgot. I will go
> through the build process again. Meanwhile @JohnHoyt I have not used
> launchpad before. Can you point to instructions for getting your 20.04
> build off of there?
>

You need to add my repo with these commands:

sudo add-apt-repository ppa:john-hoyt/hauppaugeusb
sudo apt-get update

The can install the "drivers" with

sudo apt-get install hauppaugeusb

>
>
> You need to add my repo with these commands:
>
> sudo add-apt-repository ppa:john-hoyt/hauppaugeusb
> sudo apt-get update
>
> The can install the "drivers" with
>
> sudo apt-get install hauppaugeusb
>

BTW - I should add that you'll still need to setup udev rules and the
config file and setup mythtv to use it as an external recorder. The PPA
pretty much only lets you skip the compile and install pieces.

On Sat, Jul 25, 2020 at 4:39 PM John Hoyt <john.hoyt@gmail.com> wrote:

>
>> You need to add my repo with these commands:
>>
>> sudo add-apt-repository ppa:john-hoyt/hauppaugeusb
>> sudo apt-get update
>>
>> The can install the "drivers" with
>>
>> sudo apt-get install hauppaugeusb
>>
>
> BTW - I should add that you'll still need to setup udev rules and the
> config file and setup mythtv to use it as an external recorder. The PPA
> pretty much only lets you skip the compile and install pieces.
>

After connecting to the repository and running the install, there is
nothing in /opt

>
> After connecting to the repository and running the install, there is
> nothing in /opt
>

That's strange. Did apt give you any errors? Also, what version of
ubuntu did you land on?

What does the output of "dpkg-query -L hauppaugeusb" give you?

On Sun, Jul 26, 2020 at 6:32 PM John Hoyt <john.hoyt@gmail.com> wrote:

> After connecting to the repository and running the install, there is
>> nothing in /opt
>>
>
> That's strange. Did apt give you any errors? Also, what version of
> ubuntu did you land on?
>
> What does the output of "dpkg-query -L hauppaugeusb" give you?
>

Here's what mine outputs:

dpkg-query -L hauppaugeusb
/.
/opt
/opt/Hauppauge
/opt/Hauppauge/bin
/opt/Hauppauge/bin/hauppauge2
/opt/Hauppauge/etc
/opt/Hauppauge/etc/sample.conf
/opt/Hauppauge/firmware
/opt/Hauppauge/firmware/llama_usb_vx_host_slave_t22_24.bin
/opt/Hauppauge/firmware/mips_vx_host_slave.bin
/usr
/usr/share
/usr/share/doc
/usr/share/doc/hauppaugeusb
/usr/share/doc/hauppaugeusb/changelog.gz
/usr/share/doc/hauppaugeusb/copyright

On Sun, Jul 26, 2020 at 3:34 PM John Hoyt <john.hoyt@gmail.com> wrote:

> On Sun, Jul 26, 2020 at 6:32 PM John Hoyt <john.hoyt@gmail.com> wrote:
>
>> After connecting to the repository and running the install, there is
>>> nothing in /opt
>>>
>>
>> That's strange. Did apt give you any errors? Also, what version of
>> ubuntu did you land on?
>>
>> What does the output of "dpkg-query -L hauppaugeusb" give you?
>>
>
> Here's what mine outputs:
>
> dpkg-query -L hauppaugeusb
> /.
> /opt
> /opt/Hauppauge
> /opt/Hauppauge/bin
> /opt/Hauppauge/bin/hauppauge2
> /opt/Hauppauge/etc
> /opt/Hauppauge/etc/sample.conf
> /opt/Hauppauge/firmware
> /opt/Hauppauge/firmware/llama_usb_vx_host_slave_t22_24.bin
> /opt/Hauppauge/firmware/mips_vx_host_slave.bin
> /usr
> /usr/share
> /usr/share/doc
> /usr/share/doc/hauppaugeusb
> /usr/share/doc/hauppaugeusb/changelog.gz
> /usr/share/doc/hauppaugeusb/copyright
>

It said not installed, so I installed the package again, and now /opt is
there. Maybe I accidentally skipped the install step. Sorry for the
noise!

On Sun, Jul 26, 2020, 5:03 PM DryHeat122 <dryheat122@gmail.com> wrote:

>
>
> On Sun, Jul 26, 2020 at 3:34 PM John Hoyt <john.hoyt@gmail.com> wrote:
>
>> On Sun, Jul 26, 2020 at 6:32 PM John Hoyt <john.hoyt@gmail.com> wrote:
>>
>>> After connecting to the repository and running the install, there is
>>>> nothing in /opt
>>>>
>>>
>>> That's strange. Did apt give you any errors? Also, what version of
>>> ubuntu did you land on?
>>>
>>> What does the output of "dpkg-query -L hauppaugeusb" give you?
>>>
>>
>> Here's what mine outputs:
>>
>> dpkg-query -L hauppaugeusb
>> /.
>> /opt
>> /opt/Hauppauge
>> /opt/Hauppauge/bin
>> /opt/Hauppauge/bin/hauppauge2
>> /opt/Hauppauge/etc
>> /opt/Hauppauge/etc/sample.conf
>> /opt/Hauppauge/firmware
>> /opt/Hauppauge/firmware/llama_usb_vx_host_slave_t22_24.bin
>> /opt/Hauppauge/firmware/mips_vx_host_slave.bin
>> /usr
>> /usr/share
>> /usr/share/doc
>> /usr/share/doc/hauppaugeusb
>> /usr/share/doc/hauppaugeusb/changelog.gz
>> /usr/share/doc/hauppaugeusb/copyright
>>
>
> It said not installed, so I installed the package again, and now /opt is
> there. Maybe I accidentally skipped the install step. Sorry for the
> noise!
>

Just to report...I was sitting here watching a recorded program on Myth,
when I saw an unfamiliar flash over by the equipment. It was HDPVR2 firing
up to record something. Unfortunately I don't yet have a channel change
solution (my FireWire seems to have crapped out) but at least the recorder
looks to be in good working order. Thank you all so much for the input and
especially John P for writing then sharing his software.

On 7/22/20 7:04 PM, John Hoyt wrote:
> I decided to try this with my current Myth setup, and it looks like
> you don't have a version for Ubuntu 16.04. 
>
>
> Correct - sorry about that.  Unfortunately launchpad blocks the upload
> for no longer supported versions of Ubuntu.  I used to have a Xenial
> build posted, but dropped it when I ran out of space in launchpad.


I think I'll add myself to the list of HD-PVR 1212 owners where the
device has slowly gotten less and less reliable over time. And my power
is coming from the computer's PSU, so it can't be the supplied wall wart
that's the problem.

The latest failure sequence was just yesterday:
1) Noticed recording that was choppy
2) Power cycled HD-PVR
3) Rather than being recognized by the computer, it showed up in dmesg as:
usb 1-6: new full-speed USB device number 10 using xhci_hcd
usb 1-6: Device not responding to setup address.
usb 1-6: Device not responding to setup address.
usb 1-6: device not accepting address 10, error -71

Where the device number would increment with each power cycle. This
happened once before perhaps a year ago and I did some number of actions
including opening the case, switching USB ports on the computer, and
switching USB cables, and eventually it worked.

This time around I ended up giving up on it, only to realize that just
after leaving it sit there for a while the device was picked up, and I
confirmed that it is functional to record.


Anyway, long story short, I want a contingency plan for when my device
fully kicks the bucket, and this HD-PVR 2 stuff has piqued my interest.
But I'm a little curious:

1) Ubuntu 16.04 reaches EOL on April 2021, which hasn't arrived yet. So
it seems odd that the upload to support 16.04 wouldn't be allowed for
that reason.
2) It looks like the project page https://github.com/jpoet/HauppaugeUSB
indicates that fixes/31 is required. Is this required to support
external recorders in general?


Based on track record, I've found that updating a system without a
specific worthwhile reason will usually end up in one of two scenarios:
1) After some indefinite amount of time/effort spent, the system may
work as well as it did before.
2) After some indefinite amount of time/effort spent, the system isn't
working as it did before.

As such, I'm a happy owner of a MythTV 29.1 on Ubuntu 16.04 system (ever
since 14.04 went EOL, lather, rinse, repeat...)

If I happen to go the HD-PVR2 route, or if April 2021 rolls around
before I know it, I'm curious if there are any guides to help avoid any
"gotchas" with updating to a newer version of Ubuntu. I seem to recall
seeing chatter here about lirc being problematic starting with Ubuntu
18.04? And I'm an old school lircd user with a homemade receiver wired
into a serial port. I'd hate to go down an upgrade path that results in
a no-longer-working remote control, for example.


Thanks for any tips/info!
-WD
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Wed, Jul 29, 2020 at 6:16 AM Will Dormann <wdormann@gmail.com> wrote:

> On 7/22/20 7:04 PM, John Hoyt wrote:
> > I decided to try this with my current Myth setup, and it looks like
> > you don't have a version for Ubuntu 16.04.
> >
> >
> > Correct - sorry about that. Unfortunately launchpad blocks the upload
> > for no longer supported versions of Ubuntu. I used to have a Xenial
> > build posted, but dropped it when I ran out of space in launchpad.
>
>
> I think I'll add myself to the list of HD-PVR 1212 owners where the
> device has slowly gotten less and less reliable over time. And my power
> is coming from the computer's PSU, so it can't be the supplied wall wart
> that's the problem.
>
> The latest failure sequence was just yesterday:
> 1) Noticed recording that was choppy
> 2) Power cycled HD-PVR
> 3) Rather than being recognized by the computer, it showed up in dmesg as:
> usb 1-6: new full-speed USB device number 10 using xhci_hcd
> usb 1-6: Device not responding to setup address.
> usb 1-6: Device not responding to setup address.
> usb 1-6: device not accepting address 10, error -71
>
> Where the device number would increment with each power cycle. This
> happened once before perhaps a year ago and I did some number of actions
> including opening the case, switching USB ports on the computer, and
> switching USB cables, and eventually it worked.
>
> This time around I ended up giving up on it, only to realize that just
> after leaving it sit there for a while the device was picked up, and I
> confirmed that it is functional to record.
>
>
> Anyway, long story short, I want a contingency plan for when my device
> fully kicks the bucket, and this HD-PVR 2 stuff has piqued my interest.
> But I'm a little curious:
>
> 1) Ubuntu 16.04 reaches EOL on April 2021, which hasn't arrived yet. So
> it seems odd that the upload to support 16.04 wouldn't be allowed for
> that reason.
> 2) It looks like the project page https://github.com/jpoet/HauppaugeUSB
> indicates that fixes/31 is required. Is this required to support
> external recorders in general?
>
>
> Based on track record, I've found that updating a system without a
> specific worthwhile reason will usually end up in one of two scenarios:
> 1) After some indefinite amount of time/effort spent, the system may
> work as well as it did before.
> 2) After some indefinite amount of time/effort spent, the system isn't
> working as it did before.
>
> As such, I'm a happy owner of a MythTV 29.1 on Ubuntu 16.04 system (ever
> since 14.04 went EOL, lather, rinse, repeat...)
>
> If I happen to go the HD-PVR2 route, or if April 2021 rolls around
> before I know it, I'm curious if there are any guides to help avoid any
> "gotchas" with updating to a newer version of Ubuntu. I seem to recall
> seeing chatter here about lirc being problematic starting with Ubuntu
> 18.04? And I'm an old school lircd user with a homemade receiver wired
> into a serial port. I'd hate to go down an upgrade path that results in
> a no-longer-working remote control, for example.
>
>
> Thanks for any tips/info!
> -WD
>

Can offer a couple things other than what is in this thread. There is a guy
on e-bay selling used used HDPVR2s for I think $80, but they are bare
bones--no power supply or cable for component video input. Had to buy a
6V-2A power supply from Amazon and the cable from Hauppauge. I was able to
get it installed and working on 18.04/Myth 31 using John H's compiled code
and John P's config instructions.

I wasn't sure exactly what John P was referring to re fixes/31. I did not
apply any fixes, just installed latest distro of 18.04. I actually started
with xubuntu 20.04 but had problems with screen-timeouts that I couldn't
resolve. Tried ubuntu 20.04 but it crashed right after install during the
update process. My mobo is like 10 years old so I suspect there may have
been some hardware incompatibilities. Went to 18.04 and it installed
smoothly.

...except there is this problem with the install hanging in some cases due
to a faulty os-prober. See here
<https://unix.stackexchange.com/questions/511289/ubuntu-18-04-server-installation-gets-stuck-at-66-while-runningupdate-grub/600231#600231>
for a workaround.

If you go up to myth 31 note that XMLTV is a *big change* for the listings
grabber, and there is a learning curve. Whereas before you just entered
your schedules direct id/pw in mythtv-setup, now the grabber is a whole
thing you have to install and configure. If you decide to upgrade check
thread "XMLTV setup can't run mythtv-setup as user mythtv" for helpful info
on getting it working.

Good luck!

Steve

On 7/29/20 2:27 PM, DryHeat122 wrote:
> I wasn't sure exactly what John P was referring to re fixes/31.  I did
> not apply any fixes, just installed latest distro of 18.04. I actually
> started with xubuntu 20.04 but had problems with screen-timeouts that I
> couldn't resolve. Tried ubuntu 20.04 but it crashed right after install
> during the update process.  My mobo is like 10 years old so I suspect
> there may have been some hardware incompatibilities. Went to 18.04 and
> it installed smoothly.

Interesting. So if you're running the Ubuntu-provided MythTV, I'd say
that you're running 29.1+fixes, if I'm reading
https://packages.ubuntu.com/bionic/mythtv right?

I'm running 29.1+fixes myself on 16.04, as my Mythbuntu PPA:
https://launchpad.net/~mythbuntu/+archive/ubuntu/0.29/+sourcepub/10541501/+listing-archive-extra
as my current MythTV machine's origins can be traced to MythBuntu rather
than Ubuntu + the MythTV package.

If you are indeed on 29.1+fixes from Ubuntu and your HD PVR 2 works,
then I suspect it may be fair to say that the statement in the github
page of "If you want to use this with MythTV, you will want fixes/31 or
later." may be incorrect?

John P: Can you share your motivations for this requirement?


> If you go up to myth 31 note that XMLTV is a /big change/ for the
> listings grabber, and there is a learning curve.  Whereas before you
> just entered your schedules direct id/pw in mythtv-setup, now the
> grabber is a whole thing you have to install and configure.  If you
> decide to upgrade check thread "XMLTV setup can't run mythtv-setup as
> user mythtv" for helpful info on getting it working.


Good to know. So that gives me a thread of 16 messages to sift through.
There's also a thread of 20 messages with the subject of
"[mythtv-users] lircd unreliable after Ubuntu upgrade 16.04 > 18.04".
And maybe there are other troubles that somebody might encounter when
upgrading to Ubuntu 18.04 (or newer), which might require locating and
sifting through other email threads. There's also a thread of 9
messages with the subject line of "[mythtv-users] successful upgrades to
ubuntu 18.04 from 16.04?"

Which perhaps brings us to what I intended to be my original point:
Is there any guide (e.g. a wiki where people could contribute) that may
serve as a single source of the information that one might need before
attempting an upgrade of a MythTV system? Which might include things
that change on the OS level (e.g. lirc) or things that change on the
MythTV level (e.g. XMLTV)


Thanks!
-WD
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org