Mailing List Archive

I've now just uploaded a new version both with and without plugins to the
sourceforge repository (
https://sourceforge.net/projects/mythtvformacosx/files/).

I have also updated the build script which required some major surgery to
get mythplugins working again.

James - this might fix your metadata issues. One of the things I
discovered while fixing the plugins was that the helper apps were missing
some of the dylibs required to work (or were linking to the build
directory...). Adding the libs to the app as a framework and modifying the
executable to search inside the mythfrontend.app is now automated in my
build script.

~John

>

On Sat, Jul 4, 2020 at 9:09 AM John Hoyt <john.hoyt@gmail.com> wrote:

> I've now just uploaded a new version both with and without plugins to the
> sourceforge repository (
> https://sourceforge.net/projects/mythtvformacosx/files/).
>
> I have also updated the build script which required some major surgery to
> get mythplugins working again.
>
> James - this might fix your metadata issues. One of the things I
> discovered while fixing the plugins was that the helper apps were missing
> some of the dylibs required to work (or were linking to the build
> directory...). Adding the libs to the app as a framework and modifying the
> executable to search inside the mythfrontend.app is now automated in my
> build script.
>
> ~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
>

John,
Thanks for this update. This fixed the issue of the persistent menu bar
appearing on my HighSierra frontend.
For anyone else with older hardware, I have an Early 2009 Mini (GeForce
9400m 256MB), but I can still get decent playback with this build using
VideoToolbox(decode only) and "low quality" deinterlacing.
WRT the metadata grabber, how does one set this up? The setup page in the
frontend currently lists no available options. Does one need to download
the python scripts or copy them from a linux installation and place them in
a specific directory on the Mac frontend?

Steve
--
________________________
"destroying the fundamental underpinnings of the broadcast television
ecosystem"

> For anyone else with older hardware, I have an Early 2009 Mini (GeForce
> 9400m 256MB), but I can still get decent playback with this build using
> VideoToolbox(decode only) and "low quality" deinterlacing.
> WRT the metadata grabber, how does one set this up? The setup page in the
> frontend currently lists no available options. Does one need to download
> the python scripts or copy them from a linux installation and place them in
> a specific directory on the Mac frontend?
>

No clue - I added the "mythmetadatalookup" binary (...and requested support
libraries) to the app bundle. There's a directory in the app
Mythfrontend.app/Contenst/Resources that should be the correct place to
drop lib or share files.

If it's missing any required python resources let me know which ones and I
can try to bundle them into the app in the future (I'm sure they get
installed while I'm building into my temp install directory somewhere.
It's just a matter of hunting and gathering, and occasionally linking the
bits in the app).

BTW - I added a page to the wiki to walk folks through the build process
https://www.mythtv.org/wiki/Building_MythFrontend_on_Mac_OS_X

Well, I think I just figured out why the metadatsearch and python bindings
are failing. There's a hard code in these files pointing to python2.6

- mythtv/programs/mythbackend/main.cpp
- mythtv/programs/mythfrontend/main.cpp
- mythtv/programs/mythmetadatalookup/main.cpp

The line in each file is:

QString("%1/../Resources/lib/python2.6/site-packages:%2")


I've just submitted a big report and will see if I can get a work around
working

>

On Sun, Jul 5, 2020 at 7:07 PM John Hoyt <john.hoyt@gmail.com> wrote:

> Well, I think I just figured out why the metadatsearch and python bindings
> are failing. There's a hard code in these files pointing to python2.6
>
> - mythtv/programs/mythbackend/main.cpp
> - mythtv/programs/mythfrontend/main.cpp
> - mythtv/programs/mythmetadatalookup/main.cpp
>
> The line in each file is:
>
> QString("%1/../Resources/lib/python2.6/site-packages:%2")
>
>
> I've just submitted a big report and will see if I can get a work around
> working
>

I also just uploaded some pre-built version with working metadata
capability to SourceForge. I tested the capability in Videos and
everything works on my system. Others may be missing some python modules
(I copied in the modules installed by ansible to the app), so if things
don't work for you please let me know and I'll add more modules.

> On 6 Jul 2020, at 5:24 pm, John Hoyt <john.hoyt@gmail.com> wrote:
>
> On Sun, Jul 5, 2020 at 7:07 PM John Hoyt <john.hoyt@gmail.com> wrote:
> Well, I think I just figured out why the metadatsearch and python bindings are failing. There's a hard code in these files pointing to python2.6
> • mythtv/programs/mythbackend/main.cpp
> • mythtv/programs/mythfrontend/main.cpp
> • mythtv/programs/mythmetadatalookup/main.cpp
> The line in each file is:
> QString("%1/../Resources/lib/python2.6/site-packages:%2")
>
> I've just submitted a big report and will see if I can get a work around working
>
> I also just uploaded some pre-built version with working metadata capability to SourceForge. I tested the capability in Videos and everything works on my system. Others may be missing some python modules (I copied in the modules installed by ansible to the app), so if things don't work for you please let me know and I'll add more modules.

John
I tried the radio-stream plugin that works perfectly
I tried meta data look up (i->change video details->retrieve details)
Which fails in about 1 sec.

Using the: /Volumes/MythFrontend-31-intel-10.13.6-v31-3ef7db67fe-with-plugins
Playing on macbook pro 2019 running catalina

James

_______________________________________________
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

>
> Using the:
> /Volumes/MythFrontend-31-intel-10.13.6-v31-3ef7db67fe-with-plugins
> Playing on macbook pro 2019 running catalina
>
> James
>

James, you;ll need to download the
MythFrontend-31-intel-10.13.6-v31-3ef7db67fe*.1*-with-plugins version I
posted this AM. (key is the .1 rev)

Sorry about that - the older version didn't have the python bits copied
into the correct place.

If that doesn't work - I'd love to get a copy of the log output to try to
debug later in the week. There's a good chance of python incompatibilities
getting in the way since I use the macports version.

On Mon, Jul 6, 2020 at 8:28 AM John Hoyt <john.hoyt@gmail.com> wrote:

> Using the:
>> /Volumes/MythFrontend-31-intel-10.13.6-v31-3ef7db67fe-with-plugins
>> Playing on macbook pro 2019 running catalina
>>
>> James
>>
>
> James, you;ll need to download the
> MythFrontend-31-intel-10.13.6-v31-3ef7db67fe*.1*-with-plugins version I
> posted this AM. (key is the .1 rev)
>
> Sorry about that - the older version didn't have the python bits copied
> into the correct place.
>
> If that doesn't work - I'd love to get a copy of the log output to try to
> debug later in the week. There's a good chance of python incompatibilities
> getting in the way since I use the macports version.
>

Here's the direct link to the "right" version
https://sourceforge.net/projects/mythtvformacosx/files/MythFrontend-31-intel-10.13.6-v31-3ef7db67fe.1-with-plugins.dmg/download

> On 6 Jul 2020, at 8:28 pm, John Hoyt <john.hoyt@gmail.com> wrote:
>
> Using the: /Volumes/MythFrontend-31-intel-10.13.6-v31-3ef7db67fe-with-plugins
> Playing on macbook pro 2019 running catalina
>
> James
>
> James, you;ll need to download the MythFrontend-31-intel-10.13.6-v31-3ef7db67fe.1-with-plugins version I posted this AM. (key is the .1 rev)
>
> Sorry about that - the older version didn't have the python bits copied into the correct place.
>
> If that doesn't work - I'd love to get a copy of the log output to try to debug later in the week. There's a good chance of python incompatibilities getting in the way since I use the macports version.

John sorry. I did not notice the .1 but I did get the correct dmg

MythFrontend-31-intel-10.13.6-v31-3ef7db67fe.1-with-plugins.dmg

I'll run it by cli (I don't know how/where logs are, this gives a goog trace

James
_______________________________________________
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 6 Jul 2020, at 8:54 pm, jam@tigger.ws wrote:
>
>
>
>> On 6 Jul 2020, at 8:28 pm, John Hoyt <john.hoyt@gmail.com> wrote:
>>
>> Using the: /Volumes/MythFrontend-31-intel-10.13.6-v31-3ef7db67fe-with-plugins
>> Playing on macbook pro 2019 running catalina
>>
>> James
>>
>> James, you;ll need to download the MythFrontend-31-intel-10.13.6-v31-3ef7db67fe.1-with-plugins version I posted this AM. (key is the .1 rev)
>>
>> Sorry about that - the older version didn't have the python bits copied into the correct place.
>>
>> If that doesn't work - I'd love to get a copy of the log output to try to debug later in the week. There's a good chance of python incompatibilities getting in the way since I use the macports version.
>
> John sorry. I did not notice the .1 but I did get the correct dmg
>
> MythFrontend-31-intel-10.13.6-v31-3ef7db67fe.1-with-plugins.dmg
>
> I'll run it by cli (I don't know how/where logs are, this gives a goog trace

Using the SAME dmg, instead of running from the downloaded dmg I installed, then ran in a terminal to get a trace and it worked.perfectly.
Perhaps I was just stupid somewhere, but my feedback was spurios noise, sorry, and a huge thankyou for all your efforts.

The linux frontend is sluggish starting and in menu ops, the osx version is worse. I'll spend some time trying to find out where and I'll feedback.

James
_______________________________________________
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

>
> Using the SAME dmg, instead of running from the downloaded dmg I
> installed, then ran in a terminal to get a trace and it worked.perfectly.
> Perhaps I was just stupid somewhere, but my feedback was spurios noise,
> sorry, and a huge thankyou for all your efforts.
>

Strange - I wouldn't expect the older version to work. I had copied in the
MythTV python module to that one, but the app wasn't setup correctly to
find it in the python3.8 I copied in. The new dmg fixes this by adding a
symlink internal to the app from python3.8->python2.6 (a packaging hack
until my new ticket gets resolved...)

You may have the MyhTV module copied to somewhere else on your system.

Glad it's working for you! Agree that mythtv is starting up slow on both
linux (ubuntu in my case) and MacOS. I'd suggest running with the "-v
all,nodatabase" flag to get more output while you try to track down
whatever is being slow to load.

> On 7 Jul 2020, at 7:33 am, John Hoyt <john.hoyt@gmail.com> wrote:
>
> Using the SAME dmg, instead of running from the downloaded dmg I installed, then ran in a terminal to get a trace and it worked.perfectly.
> Perhaps I was just stupid somewhere, but my feedback was spurios noise, sorry, and a huge thankyou for all your efforts.
>
> Strange - I wouldn't expect the older version to work. I had copied in the MythTV python module to that one, but the app wasn't setup correctly to find it in the python3.8 I copied in. The new dmg fixes this by adding a symlink internal to the app from python3.8->python2.6 (a packaging hack until my new ticket gets resolved...)
>
> You may have the MyhTV module copied to somewhere else on your system.
>
> Glad it's working for you! Agree that mythtv is starting up slow on both linux (ubuntu in my case) and MacOS. I'd suggest running with the "-v all,nodatabase" flag to get more output while you try to track down whatever is being slow to load.

Sorry John I’ve csused confusion

I downloaded the correct dmg
I ran it from the dmg and had no meta data work
I (to avoid the alias stuff) copied it and pasted to my local Applicions. Which turns out to be an alias to /Applications with local permissions. Meta data now worked.

There is an issue however

I’m using MythCenter Wide theme, but I tried a few and they are all the same.

If you pause playback you get a usage bar and the time displayed.
My build (using your ansible script), your earlier builds my linux frontends DO show this behaviour.
The recent metadata fixes DO NOT show anything on screen during pause.

James
_______________________________________________
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

James - good catch the OSD in playback is mesed up on my version as well.
I clearly missed this when testing Mark Kendal's bug fixes. I'll submit a
new ticket into track.

Mark - many apologies for the mess up and missing this bug in testing.

On Mon, Jul 6, 2020 at 8:53 PM jam <jam@tigger.ws> wrote:

>
>
> > On 7 Jul 2020, at 7:33 am, John Hoyt <john.hoyt@gmail.com> wrote:
> >
> > Using the SAME dmg, instead of running from the downloaded dmg I
> installed, then ran in a terminal to get a trace and it worked.perfectly.
> > Perhaps I was just stupid somewhere, but my feedback was spurios noise,
> sorry, and a huge thankyou for all your efforts.
> >
> > Strange - I wouldn't expect the older version to work. I had copied in
> the MythTV python module to that one, but the app wasn't setup correctly to
> find it in the python3.8 I copied in. The new dmg fixes this by adding a
> symlink internal to the app from python3.8->python2.6 (a packaging hack
> until my new ticket gets resolved...)
> >
> > You may have the MyhTV module copied to somewhere else on your system.
> >
> > Glad it's working for you! Agree that mythtv is starting up slow on
> both linux (ubuntu in my case) and MacOS. I'd suggest running with the "-v
> all,nodatabase" flag to get more output while you try to track down
> whatever is being slow to load.
>
> Sorry John I’ve csused confusion
>
> I downloaded the correct dmg
> I ran it from the dmg and had no meta data work
> I (to avoid the alias stuff) copied it and pasted to my local Applicions.
> Which turns out to be an alias to /Applications with local permissions.
> Meta data now worked.
>
> There is an issue however
>
> I’m using MythCenter Wide theme, but I tried a few and they are all the
> same.
>
> If you pause playback you get a usage bar and the time displayed.
> My build (using your ansible script), your earlier builds my linux
> frontends DO show this behaviour.
> The recent metadata fixes DO NOT show anything on screen during pause.
>
> James
> _______________________________________________
> 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 Tue, Jul 7, 2020 at 5:38 AM John Hoyt <john.hoyt@gmail.com> wrote:

> James - good catch the OSD in playback is mesed up on my version as well.
> I clearly missed this when testing Mark Kendal's bug fixes. I'll submit a
> new ticket into track.
>
> Mark - many apologies for the mess up and missing this bug in testing.
>

I just opened ticket 13646 (https://code.mythtv.org/trac/ticket/13646) to
hopefully get this resolved. Again, apologies that I missed this in test.

On Mon, Jul 6, 2020 at 2:26 AM John Hoyt <john.hoyt@gmail.com> wrote:

> On Sun, Jul 5, 2020 at 7:07 PM John Hoyt <john.hoyt@gmail.com> wrote:
>
>> Well, I think I just figured out why the metadatsearch and python
>> bindings are failing. There's a hard code in these files pointing to
>> python2.6
>>
>> - mythtv/programs/mythbackend/main.cpp
>> - mythtv/programs/mythfrontend/main.cpp
>> - mythtv/programs/mythmetadatalookup/main.cpp
>>
>> The line in each file is:
>>
>> QString("%1/../Resources/lib/python2.6/site-packages:%2")
>>
>>
>> I've just submitted a big report and will see if I can get a work around
>> working
>>
>
> I also just uploaded some pre-built version with working metadata
> capability to SourceForge. I tested the capability in Videos and
> everything works on my system. Others may be missing some python modules
> (I copied in the modules installed by ansible to the app), so if things
> don't work for you please let me know and I'll add more modules.
> _______________________________________________
> 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


Hi John,
Thank you for your continued work on the mac 0.31 frontend!
In your latest ".1" build, I can see the grabbers in
/Resources/share/mythtv/metadata, but they do not show up to be selected in
the metadata settings page (I've tried under multiple themes). As a
result, metadata lookups fail, e.g.:


2020-07-11 09:41:13.497473 I Running Grabber: -l en -a US -M Star.Wars

2020-07-11 09:41:13.544406 E MythSystemLegacy() command not executable,

eno: No such file or directory (2)

Is there something that has to be edited/moved before the frontend will
find the python modules within the metadata settings page?

Thanks,
Steve

--
________________________
"destroying the fundamental underpinnings of the broadcast television
ecosystem"

>
>
>>> Hi John,
> Thank you for your continued work on the mac 0.31 frontend!
> In your latest ".1" build, I can see the grabbers in
> /Resources/share/mythtv/metadata, but they do not show up to be selected in
> the metadata settings page (I've tried under multiple themes). As a
> result, metadata lookups fail, e.g.:
>
>
> 2020-07-11 09:41:13.497473 I Running Grabber: -l en -a US -M Star.Wars
>
> 2020-07-11 09:41:13.544406 E MythSystemLegacy() command not executable,
>
> eno: No such file or directory (2)
>
> Is there something that has to be edited/moved before the frontend will
> find the python modules within the metadata settings page?
>
> Thanks,
> Steve
>

Steve - try grabbing the data in the video browser. Navigate to the item
and hit the Info key (I key) -> Change Video Details -> Retrieve Details

Let me know if that works and what comes out on the console. I have
noticed some movies try thetvdb grabber and fail there.

Also - can you point me to the metadata settings page you're referring to?
Mine seem to work - but maybe I'm looking in the wrong place.

BTW - the python hard code ticket I opened up has been fixed/closed. I can
post an updated build if you'd like - but I'm unsure if it will fix any of
your problems. Just let me know if you'd like to give it a go and I'll
spin up the VM and compile/post it to sourceforge.

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

>
>>>> Hi John,
>> Thank you for your continued work on the mac 0.31 frontend!
>> In your latest ".1" build, I can see the grabbers in
>> /Resources/share/mythtv/metadata, but they do not show up to be selected in
>> the metadata settings page (I've tried under multiple themes). As a
>> result, metadata lookups fail, e.g.:
>>
>>
>> 2020-07-11 09:41:13.497473 I Running Grabber: -l en -a US -M Star.Wars
>>
>> 2020-07-11 09:41:13.544406 E MythSystemLegacy() command not executable,
>>
>> eno: No such file or directory (2)
>>
>> Is there something that has to be edited/moved before the frontend will
>> find the python modules within the metadata settings page?
>>
>> Thanks,
>> Steve
>>
>
> Steve - try grabbing the data in the video browser. Navigate to the item
> and hit the Info key (I key) -> Change Video Details -> Retrieve Details
>
> Let me know if that works and what comes out on the console. I have
> noticed some movies try thetvdb grabber and fail there.
>
> Also - can you point me to the metadata settings page you're referring to?
> Mine seem to work - but maybe I'm looking in the wrong place.
>
> BTW - the python hard code ticket I opened up has been fixed/closed. I
> can post an updated build if you'd like - but I'm unsure if it will fix any
> of your problems. Just let me know if you'd like to give it a go and I'll
> spin up the VM and compile/post it to sourceforge.
>

I'm actually posting the new builds now - should be up in 5 min.

Another thought I had is that maybe there's some garbage path in your
~/.mythtv directory. Have you tried moving the directory to a new name
then start with a fresh set of mythtv settings?

On Sat, Jul 11, 2020 at 1:30 PM John Hoyt <john.hoyt@gmail.com> wrote:

>
>>>> Hi John,
>> Thank you for your continued work on the mac 0.31 frontend!
>> In your latest ".1" build, I can see the grabbers in
>> /Resources/share/mythtv/metadata, but they do not show up to be selected in
>> the metadata settings page (I've tried under multiple themes). As a
>> result, metadata lookups fail, e.g.:
>>
>>
>> 2020-07-11 09:41:13.497473 I Running Grabber: -l en -a US -M Star.Wars
>>
>> 2020-07-11 09:41:13.544406 E MythSystemLegacy() command not executable,
>>
>> eno: No such file or directory (2)
>>
>> Is there something that has to be edited/moved before the frontend will
>> find the python modules within the metadata settings page?
>>
>> Thanks,
>> Steve
>>
>
> Steve - try grabbing the data in the video browser. Navigate to the item
> and hit the Info key (I key) -> Change Video Details -> Retrieve Details
>
> Let me know if that works and what comes out on the console. I have
> noticed some movies try thetvdb grabber and fail there.
>
> Also - can you point me to the metadata settings page you're referring to?
> Mine seem to work - but maybe I'm looking in the wrong place.
>
> BTW - the python hard code ticket I opened up has been fixed/closed. I
> can post an updated build if you'd like - but I'm unsure if it will fix any
> of your problems. Just let me know if you'd like to give it a go and I'll
> spin up the VM and compile/post it to sourceforge.
> _______________________________________________
> 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
>

John,

That is what I was doing (attempting to grab data from the Info menu via
Retrieve Details in the video browser) to generate the console messages.
There are no Grabbers available to that method because they currently can
not be set in the metadata settings page:
Setup->Artwork and Data sources

Steve
--
________________________
"destroying the fundamental underpinnings of the broadcast television
ecosystem"

>
> That is what I was doing (attempting to grab data from the Info menu via
> Retrieve Details in the video browser) to generate the console messages.
> There are no Grabbers available to that method because they currently can
> not be set in the metadata settings page:
> Setup->Artwork and Data sources
>
> Steve
>

Can you attach the full mythtv console output when this occurs? It's
strange because the app on my system checks internally for all of the
metadata and python goodies now. Clearly you're not having any luck and
I'm beginning to suspect a configuration issue either on your system or
some hard code that I need to track down on the compile.

James - is metadata downloading still working on your system with the
latest build that I just uploaded to sourceforge (it is on mine)?

On Sat, Jul 11, 2020 at 2:03 PM John Hoyt <john.hoyt@gmail.com> wrote:

>
>
> On Sat, Jul 11, 2020 at 4:28 PM John Hoyt <john.hoyt@gmail.com> wrote:
>
>>
>>>>> Hi John,
>>> Thank you for your continued work on the mac 0.31 frontend!
>>> In your latest ".1" build, I can see the grabbers in
>>> /Resources/share/mythtv/metadata, but they do not show up to be selected in
>>> the metadata settings page (I've tried under multiple themes). As a
>>> result, metadata lookups fail, e.g.:
>>>
>>>
>>> 2020-07-11 09:41:13.497473 I Running Grabber: -l en -a US -M Star.Wars
>>>
>>> 2020-07-11 09:41:13.544406 E MythSystemLegacy() command not executable,
>>>
>>> eno: No such file or directory (2)
>>>
>>> Is there something that has to be edited/moved before the frontend will
>>> find the python modules within the metadata settings page?
>>>
>>> Thanks,
>>> Steve
>>>
>>
>> Steve - try grabbing the data in the video browser. Navigate to the item
>> and hit the Info key (I key) -> Change Video Details -> Retrieve Details
>>
>> Let me know if that works and what comes out on the console. I have
>> noticed some movies try thetvdb grabber and fail there.
>>
>> Also - can you point me to the metadata settings page you're referring
>> to? Mine seem to work - but maybe I'm looking in the wrong place.
>>
>> BTW - the python hard code ticket I opened up has been fixed/closed. I
>> can post an updated build if you'd like - but I'm unsure if it will fix any
>> of your problems. Just let me know if you'd like to give it a go and I'll
>> spin up the VM and compile/post it to sourceforge.
>>
>
> I'm actually posting the new builds now - should be up in 5 min.
>
> Another thought I had is that maybe there's some garbage path in your
> ~/.mythtv directory. Have you tried moving the directory to a new name
> then start with a fresh set of mythtv settings?
> _______________________________________________
> 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
>
Good idea. I gave that a try, re-connected to the database, but still was
unable to set anything in the Artwork and Data Sources page.
What do you see on the Artwork and Data Sources page?

--
________________________
"destroying the fundamental underpinnings of the broadcast television
ecosystem"

>
> What do you see on the Artwork and Data Sources page?
>

Unfortunately the grabbers get filled out for me no issues.

Do you have macports and python3.8 from macports installed? I'm beginning
to suspect that the python bits will only work if you have a matching setup
to my own.

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

> What do you see on the Artwork and Data Sources page?
>>
>
> Unfortunately the grabbers get filled out for me no issues.
>
> Do you have macports and python3.8 from macports installed? I'm beginning
> to suspect that the python bits will only work if you have a matching setup
> to my own.
> _______________________________________________
> 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
>

Hi John,
Attached is the log file with the Grabber attempt using your latest build.
I have macports, but not python3.8 installed. That's a good suggestion.
Let me remind myself how to install stuff via macports and give that a try.

Thanks again,
Steve
--
________________________
"destroying the fundamental underpinnings of the broadcast television
ecosystem"

>
> Hi John,
>>
> Attached is the log file with the Grabber attempt using your latest build.
> I have macports, but not python3.8 installed. That's a good suggestion.
> Let me remind myself how to install stuff via macports and give that a try.
>
> sudo port install python3.8 I think :)

the following lines have me confused (i.e. I don't know what they mean)

"2020-07-11 14:23:30.297714 E [24677/71687] MetadataDownload
mythsystemlegacy.cpp:163 (SetCommand) - MythSystemLegacy() command not
executable,
eno: No such file or directory (2)"

I'll have to look into them a bit more.

> I have macports, but not python3.8 installed. That's a good suggestion.
>> Let me remind myself how to install stuff via macports and give that a try.
>>
>
make that "sudo port install python38" - just updated the sourceforge site
readme to hint that this could be a fix. Let me know if this fixes the
python bits for you and I'll add more definitive language to the site.

On Sun, Jul 12, 2020 at 5:49 AM John Hoyt <john.hoyt@gmail.com> wrote:

>
> I have macports, but not python3.8 installed. That's a good suggestion.
>>> Let me remind myself how to install stuff via macports and give that a try.
>>>
>>
> make that "sudo port install python38" - just updated the sourceforge site
> readme to hint that this could be a fix. Let me know if this fixes the
> python bits for you and I'll add more definitive language to the site.
> _______________________________________________
> 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
>

OK - I got python3.8 installed. Now tmdb.py is selectable in the settings
page as "TheMovieDB.orgV3".
However, there is still nothing selectable for TV shows.

Unfortunately, the grabber still doesn't seem to work:

2020-07-12 11:02:38.143524 I Running Grabber: -l en -a US -N 11 A New Hope

2020-07-12 11:02:38.143601 E MythSystemLegacy() command not executable,

eno: No such file or directory (2)

2020-07-12 11:02:38.143624 I Running Grabber: -l en -a US -C 11

2020-07-12 11:02:38.354766 I Running Grabber:
/Applications/Mythfrontend.app/Contents/Resources/share/mythtv/metadata/Movie/tmdb3.py
-l en -a US -D 11

2020-07-12 11:02:38.770950 I Running Grabber:
/Applications/Mythfrontend.app/Contents/Resources/share/mythtv/metadata/Movie/tmdb3.py
-l en -a US -D 11

2020-07-12 11:02:39.027629 I Metadata Lookup Failed: No Results Star Wars:
Episode IV 0 0

2020-07-12 11:02:39.080022 I No results found for Star Wars: Episode IV 0 0

I tried this on any number of files with the same results. At this point,
the frontend is clearly finding the grabber script in
/Resources/share/mythtv/metadata/Movie/, so I guess it's an issue with the
grabber itself, and not the frontend build.
It's a bit strange: the file name is Star.Wars.Episode.IV.mp4, so I guess
the frontend is getting "A New Hope" from the existing metadata?

Steve
--
________________________
"destroying the fundamental underpinnings of the broadcast television
ecosystem"

>
>
>> OK - I got python3.8 installed. Now tmdb.py is selectable in the
> settings page as "TheMovieDB.orgV3".
> However, there is still nothing selectable for TV shows.
>
> Unfortunately, the grabber still doesn't seem to work:
>
> 2020-07-12 11:02:38.143524 I Running Grabber: -l en -a US -N 11 A New
> Hope
>
> 2020-07-12 11:02:38.143601 E MythSystemLegacy() command not executable,
>
> eno: No such file or directory (2)
>
> 2020-07-12 11:02:38.143624 I Running Grabber: -l en -a US -C 11
>
> 2020-07-12 11:02:38.354766 I Running Grabber:
> /Applications/Mythfrontend.app/Contents/Resources/share/mythtv/metadata/Movie/tmdb3.py
> -l en -a US -D 11
>
> 2020-07-12 11:02:38.770950 I Running Grabber:
> /Applications/Mythfrontend.app/Contents/Resources/share/mythtv/metadata/Movie/tmdb3.py
> -l en -a US -D 11
>
> 2020-07-12 11:02:39.027629 I Metadata Lookup Failed: No Results Star
> Wars: Episode IV 0 0
>
> 2020-07-12 11:02:39.080022 I No results found for Star Wars: Episode IV 0
> 0
>
> I tried this on any number of files with the same results. At this point,
> the frontend is clearly finding the grabber script in
> /Resources/share/mythtv/metadata/Movie/, so I guess it's an issue with the
> grabber itself, and not the frontend build.
> It's a bit strange: the file name is Star.Wars.Episode.IV.mp4, so I guess
> the frontend is getting "A New Hope" from the existing metadata?
>

Sounds like not all of the python libraries I copied in are being found (I
think I need to set the PYTHONPATH variable to include the app's python
directory as the top of the search list). My guess is that this works for
James and myself since we installed all of the python support libraries via
macports.

I'll try to hunt down the python pathing gremlins, but I suspect I may
never get them all. Also starting to get well out of my experience
wheelhouse.

If anyone else knows how to set environmental variables from inside a MacOS
Application (not from the user's profile nor launchd....), I'm open to
suggestions on how to fix it :)

>
> Sounds like not all of the python libraries I copied in are being found (I
> think I need to set the PYTHONPATH variable to include the app's python
> directory as the top of the search list). My guess is that this works for
> James and myself since we installed all of the python support libraries via
> macports.
>
> I'll try to hunt down the python pathing gremlins, but I suspect I may
> never get them all. Also starting to get well out of my experience
> wheelhouse.
>
> If anyone else knows how to set environmental variables from inside a
> MacOS Application (not from the user's profile nor launchd....), I'm open
> to suggestions on how to fix it :)
>

Steve,

I just did an exhaustive search on the macport python packages required to
compile mythfrontend. All of the support ports except the core python3.8
are now copied into the latest version I just finished uploading to
sourceforge. Please download and give a whirl.

...if this doesn't work there's definitely some nast python pathing that
needs to be worked out.

~John

On Sun, Jul 12, 2020 at 1:30 PM John Hoyt <john.hoyt@gmail.com> wrote:

> Sounds like not all of the python libraries I copied in are being found (I
>> think I need to set the PYTHONPATH variable to include the app's python
>> directory as the top of the search list). My guess is that this works for
>> James and myself since we installed all of the python support libraries via
>> macports.
>>
>> I'll try to hunt down the python pathing gremlins, but I suspect I may
>> never get them all. Also starting to get well out of my experience
>> wheelhouse.
>>
>> If anyone else knows how to set environmental variables from inside a
>> MacOS Application (not from the user's profile nor launchd....), I'm open
>> to suggestions on how to fix it :)
>>
>
> Steve,
>
> I just did an exhaustive search on the macport python packages required to
> compile mythfrontend. All of the support ports except the core python3.8
> are now copied into the latest version I just finished uploading to
> sourceforge. Please download and give a whirl.
>
> ...if this doesn't work there's definitely some nast python pathing that
> needs to be worked out.
>
> ~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
>

Hi John,
Unfortunately, same results/same log messages with this build. Out of
desperation, I even did "sudo port select --set python python38" (I had
previously just done --set python3 python38), but that didn't help.
It's a good question about the python path - unfortunately, I have no idea
how it is being set within the app itself.

Thanks again for trying. LIkely, your build will still work for many users
that have a more comprehensive python installation via macports.

Steve
--
________________________
"destroying the fundamental underpinnings of the broadcast television
ecosystem"

> On 13 Jul 2020, at 2:13 am, scram69 <scram69@gmail.com> wrote:
>
> OK - I got python3.8 installed. Now tmdb.py is selectable in the settings page as "TheMovieDB.orgV3".
> However, there is still nothing selectable for TV shows.
>
> Unfortunately, the grabber still doesn't seem to work:
> 2020-07-12 11:02:38.143524 I Running Grabber: -l en -a US -N 11 A New Hope
> 2020-07-12 11:02:38.143601 E MythSystemLegacy() command not executable,
> eno: No such file or directory (2)
> 2020-07-12 11:02:38.143624 I Running Grabber: -l en -a US -C 11
> 2020-07-12 11:02:38.354766 I Running Grabber: /Applications/Mythfrontend.app/Contents/Resources/share/mythtv/metadata/Movie/tmdb3.py -l en -a US -D 11
> 2020-07-12 11:02:38.770950 I Running Grabber: /Applications/Mythfrontend.app/Contents/Resources/share/mythtv/metadata/Movie/tmdb3.py -l en -a US -D 11
> 2020-07-12 11:02:39.027629 I Metadata Lookup Failed: No Results Star Wars: Episode IV 0 0
> 2020-07-12 11:02:39.080022 I No results found for Star Wars: Episode IV 0 0
>
> I tried this on any number of files with the same results. At this point, the frontend is clearly finding the grabber script in /Resources/share/mythtv/metadata/Movie/, so I guess it's an issue with the grabber itself, and not the frontend build.
> It's a bit strange: the file name is Star.Wars.Episode.IV.mp4, so I guess the frontend is getting "A New Hope" from the existing metadata?

Steve I don’t understand. John posted a version of the frontend where the grabber does work, The problem there is the OSD foes not work.
Are the problems you are having with *that* version? I have done some testing but not lots

James
_______________________________________________
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 Sun, Jul 12, 2020 at 5:33 PM jam <jam@tigger.ws> wrote:

>
>
> > On 13 Jul 2020, at 2:13 am, scram69 <scram69@gmail.com> wrote:
> >
> > OK - I got python3.8 installed. Now tmdb.py is selectable in the
> settings page as "TheMovieDB.orgV3".
> > However, there is still nothing selectable for TV shows.
> >
> > Unfortunately, the grabber still doesn't seem to work:
> > 2020-07-12 11:02:38.143524 I Running Grabber: -l en -a US -N 11 A New
> Hope
> > 2020-07-12 11:02:38.143601 E MythSystemLegacy() command not executable,
> > eno: No such file or directory (2)
> > 2020-07-12 11:02:38.143624 I Running Grabber: -l en -a US -C 11
> > 2020-07-12 11:02:38.354766 I Running Grabber:
> /Applications/Mythfrontend.app/Contents/Resources/share/mythtv/metadata/Movie/tmdb3.py
> -l en -a US -D 11
> > 2020-07-12 11:02:38.770950 I Running Grabber:
> /Applications/Mythfrontend.app/Contents/Resources/share/mythtv/metadata/Movie/tmdb3.py
> -l en -a US -D 11
> > 2020-07-12 11:02:39.027629 I Metadata Lookup Failed: No Results Star
> Wars: Episode IV 0 0
> > 2020-07-12 11:02:39.080022 I No results found for Star Wars: Episode IV
> 0 0
> >
> > I tried this on any number of files with the same results. At this
> point, the frontend is clearly finding the grabber script in
> /Resources/share/mythtv/metadata/Movie/, so I guess it's an issue with the
> grabber itself, and not the frontend build.
> > It's a bit strange: the file name is Star.Wars.Episode.IV.mp4, so I
> guess the frontend is getting "A New Hope" from the existing metadata?
>
> Steve I don’t understand. John posted a version of the frontend where the
> grabber does work, The problem there is the OSD foes not work.
> Are the problems you are having with *that* version? I have done some
> testing but not lots
>
> James
> _______________________________________________
> 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
>

James,
I believe John's latest version (posted today) fixes the issue with the OSD.
My issue has to do with the frontend's ability to access the python
installation on my mac.

Steve
--
________________________
"destroying the fundamental underpinnings of the broadcast television
ecosystem"

John did not go well for me.
I installed python38 from macports
Since it core dumped I ran in in a term

[haycorn] /Users/jam [503]% /Applications/Mythfrontend.app/Contents/MacOS/mythfrontend
2020-07-13 11:41:51.777520 I Setup Interrupt: 2 handler
2020-07-13 11:41:51.777560 I Setup Terminated: 15 handler
2020-07-13 11:41:51.777572 I Setup Segmentation fault: 11 handler
2020-07-13 11:41:51.777584 I Setup Abort trap: 6 handler
2020-07-13 11:41:51.777595 I Setup Bus error: 10 handler
2020-07-13 11:41:51.777607 I Setup Floating point exception: 8 handler
2020-07-13 11:41:51.777618 I Setup Illegal instruction: 4 handler
2020-07-13 11:41:51.777632 I Setup User defined signal 1: 30 handler
2020-07-13 11:41:51.777643 I Setup User defined signal 2: 31 handler
2020-07-13 11:41:51.777658 I Setup Hangup: 1 handler
2020-07-13 11:41:51.777784 C mythfrontend version: fixes/31 [v31.0-72-g8212a9b7bf] www.mythtv.org
2020-07-13 11:41:51.777799 C Qt version: compile: 5.14.2, runtime: 5.14.2
2020-07-13 11:41:51.777833 I macOS High Sierra (10.13) (x86_64)
2020-07-13 11:41:51.777841 N Enabled verbose msgs: general
2020-07-13 11:41:51.777867 N Setting Log Level to LOG_INFO
2020-07-13 11:41:51.789086 I Added logging to the console
2020-07-13 11:41:51.789198 N Using runtime prefix = /Applications/Mythfrontend.app/Contents/Resources
2020-07-13 11:41:51.789209 N Using configuration directory = /Users/jam/.mythtv
2020-07-13 11:41:51.789277 I Assumed character encoding: en_AU.UTF-8
2020-07-13 11:41:51.790198 I Loading en_us translation for module mythfrontend
2020-07-13 11:41:51.790588 I Empty LocalHostName. This is typical.
2020-07-13 11:41:51.790605 I Using a profile name of: 'haycorn.home' (Usually the same as this host's name.)
2020-07-13 11:41:51.790727 I Start up testing connections. DB 192.168.5.33, BE , attempt 0, status dbAwake, Delay: 2000
2020-07-13 11:41:53.422519 N Setting QT default locale to en_AU
2020-07-13 11:41:53.422541 I Current locale en_AU
2020-07-13 11:41:53.422615 E No locale defaults file for en_AU, skipping
2020-07-13 11:41:53.426228 I Display: Found screen 'iMac'
2020-07-13 11:41:53.426263 I Display: Using screen 'iMac' (Make: Unknown Model: Unknown)
2020-07-13 11:41:53.426282 I Display: Qt screen pixel ratio: 1.00
2020-07-13 11:41:53.426313 I Display: Geometry: 2560x1440+0+0 Size(Qt): 596.55mmx335.56mm
2020-07-13 11:41:53.427110 N Display: Desktop video mode: 2560x1440 60.000Hz
2020-07-13 11:41:53.499106 E PowerOSX: Failed to setup power source callback
2020-07-13 11:41:53.499216 I Power: Supported actions: Suspend,Restart,Shutdown
2020-07-13 11:41:54.008707 I Listening on TCP 0.0.0.0:6547
2020-07-13 11:41:54.010104 I Listening on TCP [::]:6547
2020-07-13 11:41:57.649934 I Loading en_us translation for module mythfrontend
2020-07-13 11:41:57.658062 E LIRC: Failed to connect to Unix socket '/var/run/lirc/lircd'
eno: No such file or directory (2)
2020-07-13 11:41:57.672662 I UDPListener: Enabling
2020-07-13 11:41:57.673858 I Binding to UDP 0.0.0.0:6948
2020-07-13 11:41:57.673945 I Binding to UDP [::]:6948
2020-07-13 11:41:57.760427 I Using Frameless Window
2020-07-13 11:41:57.761208 I Display: Have main widget
2020-07-13 11:41:57.761220 I Display: Have main window
2020-07-13 11:41:57.761991 I Display: Found screen 'iMac'
2020-07-13 11:41:57.763549 I UI Screen Resolution: 1600 x 900
2020-07-13 11:41:57.849617 I OpenGL: OpenGL vendor : ATI Technologies Inc.
2020-07-13 11:41:57.849635 I OpenGL: OpenGL renderer : AMD Radeon HD 6770M OpenGL Engine
2020-07-13 11:41:57.849646 I OpenGL: OpenGL version : 2.1 ATI-1.68.20
2020-07-13 11:41:57.849655 I OpenGL: Qt platform : cocoa
2020-07-13 11:41:57.849662 I OpenGL: Qt OpenGL format : OpenGL 2.1
2020-07-13 11:41:57.849673 I OpenGL: Qt OpenGL surface : RGBA: 888-1 Depth: 0 Stencil: 0
2020-07-13 11:41:57.849681 I OpenGL: Max texture size : 16384
2020-07-13 11:41:57.849688 I OpenGL: Max texture units : 16
2020-07-13 11:41:57.849699 I OpenGL: Shaders : Yes
2020-07-13 11:41:57.849710 I OpenGL: NPOT textures : Yes
2020-07-13 11:41:57.849717 I OpenGL: Multitexturing : Yes
2020-07-13 11:41:57.849725 I OpenGL: Rectangular textures : Yes
2020-07-13 11:41:57.849731 I OpenGL: Buffer mapping : Yes
2020-07-13 11:41:57.849742 I OpenGL: Framebuffer objects : Yes
2020-07-13 11:41:57.849749 I OpenGL: 16bit framebuffers : Yes
2020-07-13 11:41:57.849757 I OpenGL: Unpack Subimage : Yes
2020-07-13 11:41:57.849763 I OpenGL: GL_RED/GL_R8 : Yes
2020-07-13 11:41:57.861115 I OpenGL: Initialised MythRenderOpenGL
2020-07-13 11:41:57.861130 I OpenGL: Using full range output
2020-07-13 11:41:57.861200 I High DPI scaling disabled
2020-07-13 11:41:57.863817 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/remotecache
2020-07-13 11:41:57.867177 I MythUIHelper: Kept 60 files, deleted 0 files, stat error on 0 files
2020-07-13 11:41:57.867222 I MythUIHelper: Pruning cache directory: /Users/jam/.mythtv/cache/thumbnails
2020-07-13 11:41:57.874306 I MythUIHelper: Kept 133 files, deleted 0 files, stat error on 0 files
2020-07-13 11:42:00.118146 I MythCoreContext::ConnectCommandSocket(): Connecting to backend server: 192.168.5.33:6543 (try 1 of 1)
2020-07-13 11:42:00.119434 I MythCoreContext::CheckProtoVersion(): Using protocol version 91 BuzzOff
2020-07-13 11:42:00.177945 E CECAdapter: Failed to find any CEC devices.
2020-07-13 11:42:00.178342 I CECAdapter: Closing down CEC.
2020-07-13 11:42:00.179524 E RAOP Device: Aborting startup - no key found.
2020-07-13 11:42:00.180419 I AirPlay: Created airplay objects.
2020-07-13 11:42:00.186720 I Current MythTV Schema Version (DBSchemaVer): 1361
2020-07-13 11:42:00.222495 I Listening on TCP 0.0.0.0:5100
2020-07-13 11:42:00.223987 I Listening on TCP [::]:5100
2020-07-13 11:42:00.225877 I VTBDec: Supported/available VideoToolbox decoders:
2020-07-13 11:42:00.225899 I VTBDec: H264
2020-07-13 11:42:00.884786 N Registering Internal as a media playback plugin.
2020-07-13 11:42:00.904546 I Bonjour: Service registration complete: name 'MythTV on haycorn.home' type '_airplay._tcp.' domain: 'local.'
2020-07-13 11:42:00.907397 N Registering WebBrowser as a media playback plugin.
2020-07-13 11:42:00.907524 I Loading en_us translation for module mythbrowser
2020-07-13 11:42:00.927145 I Loading en_us translation for module mythgame
2020-07-13 11:42:00.947117 I Current MythMusic Schema Version (MusicDBSchemaVer): 1024
2020-07-13 11:42:00.978630 I Loading en_us translation for module mythmusic
2020-07-13 11:42:00.995957 I Loading en_us translation for module mythnews
2020-07-13 11:42:01.015652 I Loading en_us translation for module mythweather
2020-07-13 11:42:01.019501 I Using Frameless Window
2020-07-13 11:42:01.029467 I Display: Have main widget
2020-07-13 11:42:01.029479 I Display: Have main window
2020-07-13 11:42:01.030191 I Display: Found screen 'iMac'
2020-07-13 11:42:01.030205 I Display: Waiting for new screen
2020-07-13 11:42:01.049904 C Received Segmentation fault: 11: Code 1, PID 0, UID 0, Value 0x00000000
2020-07-13 11:42:01.151601 I Bonjour: Service registration complete: name 'Mythfrontend on haycorn.home' type '_mythfrontend._tcp.' domain: 'local.'
Segmentation fault: 11

James

_______________________________________________
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

> I believe John's latest version (posted today) fixes the issue with the
> OSD.
>

Unfortunately that is not correct. Fixing the OSD is out of my skill set.
I do have a ticket in trac opened for it (
https://code.mythtv.org/trac/ticket/13646). Getting this one fixed will
probably take a bit much like the quarter screen playback issues.

On Sun, Jul 12, 2020 at 11:50 PM jam <jam@tigger.ws> wrote:

> John did not go well for me.
> I installed python38 from macports
> Since it core dumped I ran in in a term
>

James,

That stinks. I have no clue what could cause the segfault as this latest
build only copies in additional python components. If the older version is
working for you - stick with it until the OSD issue gets resolved.

Did MacOS generate a crash report? If so, can you mine it for the culprit
error message / dylib or application.

Was installing python38 the only change you made to your system? If so -
try removing it and running

Also - are you saying the metadata was working on your system before you
installed python38???? I had assumed (clearly incorrectly) that you had it
installed after you were trying to compile, as this was not the case, can
you describe your runtime setup (version of MacOS, version of Xcode, what
ports if any are installed)? We're chasing a strange gremlin with the
metadata grabber not working for Steve - so there's probably a very subtle
difference in both of your configurations that may give us a hint to
solving the riddle.

~John

> On 13 Jul 2020, at 5:53 pm, John Hoyt <john.hoyt@gmail.com> wrote:
>
> John did not go well for me.
> I installed python38 from macports
> Since it core dumped I ran in in a term
>
> James,
>
> That stinks. I have no clue what could cause the segfault as this latest build only copies in additional python components. If the older version is working for you - stick with it until the OSD issue gets resolved.
>
> Did MacOS generate a crash report? If so, can you mine it for the culprit error message / dylib or application.
>
> Was installing python38 the only change you made to your system? If so - try removing it and running
>
> Also - are you saying the metadata was working on your system before you installed python38???? I had assumed (clearly incorrectly) that you had it installed after you were trying to compile, as this was not the case, can you describe your runtime setup (version of MacOS, version of Xcode, what ports if any are installed)? We're chasing a strange gremlin with the metadata grabber not working for Steve - so there's probably a very subtle difference in both of your configurations that may give us a hint to solving the riddle.

John from my building attemps I surely had python38 installed. MythFrontend-31-intel-10.13.6-v31-3ef7db67fe.1-with-plugins.dmg does grab meta data, does work but has no OSD. The OSD is more important than the grabbing (I use alinux frontend to do that) so I'm using an even older version:
fixes/31 [v31.0-40-gce23a0225f]
3ef7db67fe does work still, just the latest build coredumps.

So to get the trace info for you I ran it and --- it worked!
Careful check of the git no says it is.the same. I downloaded once only so not a dl problem. I posted a sig 11 so I'm not dreaming. Will try using and see what happens (but the OSD is a biggie so I may break.

James
_______________________________________________
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

> OSD is a biggie so I may break.
>

James - apologies but I am personally unable to fix the OSD issue - it is
currently out of my knowledge and experience base to do so. This is why
I've opened a ticket (https://code.mythtv.org/trac/ticket/13646).

The mythtv developer's team are much more experienced with the code here
(it deals with all sorts of QT5 goodness with MacOS specific work arounds)
and will be able to help get it fixed when they have the time (they're
quite busy chasing down other tickets plus their away from MythTV lives).
They have been EXTREMELY helpful getting the quarter screen issues fixed to
date and I am confident that they'll get this one fixed when they have
time. One of the rules in the developer's FAQ about submitting tickets is
to "be patient" and I absolutely will respect this request.

> On 13 Jul 2020, at 9:04 pm, John Hoyt <john.hoyt@gmail.com> wrote:
>
> OSD is a biggie so I may break.
>
> James - apologies but I am personally unable to fix the OSD issue - it is currently out of my knowledge and experience base to do so. This is why I've opened a ticket (https://code.mythtv.org/trac/ticket/13646).
>
> The mythtv developer's team are much more experienced with the code here (it deals with all sorts of QT5 goodness with MacOS specific work arounds) and will be able to help get it fixed when they have the time (they're quite busy chasing down other tickets plus their away from MythTV lives). They have been EXTREMELY helpful getting the quarter screen issues fixed to date and I am confident that they'll get this one fixed when they have time. One of the rules in the developer's FAQ about submitting tickets is to "be patient" and I absolutely will respect this request.

John I think you have gone the extra 500 miles on this. so I'm definitely being patient and any posting I do is ment to help and is not in any way to complain. Thanks mate!
James
_______________________________________________
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

James - All good (and glad to help where I can)!

BTW - I have had the MythFrontend.app core dump on at least once before the
first time using it after a build - then never again. If it does happen to
you again (and likewise for me), try to track down the system report that
apple generates. It'd be great to know what internal item caused the
segfault.

>
> Thanks again for trying. LIkely, your build will still work for many
> users that have a more comprehensive python installation via macports.
>

If you want to match the python install James and I are using - you
probably only need to match what's in ansible. You can do this with the
following command

"sudo port install py38-future py38-requests py38-requests-cache py38-lxml
py38-oauthlib py38-curl py38-simplejson py38-wheel py38-pip py38-pymysql"

...I'm still going to have to figure out a way to work through the python
path internals for the app...

On Mon, Jul 13, 2020 at 11:54 PM John Hoyt <john.hoyt@gmail.com> wrote:

> Thanks again for trying. LIkely, your build will still work for many
>>
> users that have a more comprehensive python installation via macports.
>>
>
> If you want to match the python install James and I are using
>
- you probably only need to match what's in ansible.
>
You can do this with the following command
>
> "sudo port install py38-future py38-requests py38-requests-cache py38-lxml
> py38-oauthlib py38-curl py38-simplejson py38-wheel py38-pip py38-pymysql"
>
> ...I'm still going to have to figure out a way to work through the
>
python path internals for the app...
>
>
Hi, below a short overview about MythTV and
python grabbers for television and videos:

1) The default grabber script paths are determined by the
sharedir = installprefix + "/share/mythtv/"
and the default script location (see item below).

2) Those default locations can be overwritten by specific settings
of the frontend. If not present, they point to their defaults
"TelevisionGrabber" -> metadata/Television/ttvdb.py
"MovieGrabber" -> metadata/Movie/tmdb3.py
An error in the log like
"MythSystemLegacy() command not executable,
eno: No such file or directory (2)"
might occur, if the setting for that grabber is wrong or empty.
See Frontend: Setup->Artwork and Data Sources
A search in the mysql settings table may be useful:
select * from settings where value like "%Grabber";

3) The grabber scripts itself must be executable and the
first line (shebang) must point to the installed python version.

4) The scripts can be tested by running them with the
"-t" parameter from the command line,
e.g.: "/usr/share/mythtv/metadata/Television/ttvdb.py -t"
The result is either a traceback or the message
"Everything appears in order."
Tracebacks usually give hints about missing python packages.

5) Pythonpath
If the python package "MythTV" is not installed in its standard
location like "/lib/python<version>/site-packages/MythTV",
the PYTHONPATH environment variable must be set to the folder
containing the "MythTV" python package.

Roland

Thanks Roland - greatly appreciate the help here! Please see the
commentary in line below.


> 1) The default grabber script paths are determined by the
> sharedir = installprefix + "/share/mythtv/"
> and the default script location (see item below).
>

This gets a bit weird on macOS as the eventual installed path gets moved
into the .app file. That being said - I believe this is working as mythtv
is finding the python grabbers I copy into the application from
installprefix + "/share/mythtv/


> 2) Those default locations can be overwritten by specific settings
> of the frontend. If not present, they point to their defaults
> "TelevisionGrabber" -> metadata/Television/ttvdb.py
> "MovieGrabber" -> metadata/Movie/tmdb3.py
> An error in the log like
> "MythSystemLegacy() command not executable,
> eno: No such file or directory (2)"
> might occur, if the setting for that grabber is wrong or empty.
> See Frontend: Setup->Artwork and Data Sources
> A search in the mysql settings table may be useful:
> select * from settings where value like "%Grabber";
>

This is an excellent piece of info I'll have to add to the wiki for
troubleshooting.


> 3) The grabber scripts itself must be executable and the
> first line (shebang) must point to the installed python version.
>

So it looks like the shebang is linked properly to the macports python
version - which is why Steve was having issues without having that version
of python installed. Also validates that use instructions for building the
way I did requires a matched python version to the one that's used to build
the application.

As far as setting the scripts executable - it looks like ttvdb and tmdb are
getting set executable - the rest are not. That's an easy fix in the build
script. Will push that fix out to my github repository when I make a new
build.

4) The scripts can be tested by running them with the
> "-t" parameter from the command line,
> e.g.: "/usr/share/mythtv/metadata/Television/ttvdb.py -t"
> The result is either a traceback or the message
> "Everything appears in order."
> Tracebacks usually give hints about missing python packages.
>

Thanks - this will be very helpful checking to make sure I put in all of
the necessary bits (...with the exception of the macports python install
itself, that thing is over twice the size of mythfrontend...),


> 5) Pythonpath
> If the python package "MythTV" is not installed in its standard
> location like "/lib/python<version>/site-packages/MythTV",
> the PYTHONPATH environment variable must be set to the folder
> containing the "MythTV" python package.
>

Setting the PYTHONPATH during application launch on MacOS takes quite a bit
of trickery from launch daemon. I might need to suggest users add a line to
their bash/zsh profiles. If I compile with PYTHONPATH set, does that get
automatically applied to the application's python path?

Just following up on the python issues - I've verified that everything
internal to the application appears correct and the appropriate files are
set executable.

You absolutely need to have python3 of some sort (preferably 3.8 which I am
building with) installed and located or symlinked to
/opt/local/bin/python3.8

To anyone having issues after verifying that python3 is installed and/or
symlinked, please run these commands to help me troubleshoot (note you'll
have correct APP_PATH to where your application is stored)

APP_PATH=/Applications/Mythfrontend.app

export PYTHONPATH=$APP_PATH/Contents/Resources/lib/python3.8/site-packages

$APP_PATH/Contents/Resources/share/mythtv/metadata/Television/ttvdb.py -t

$APP_PATH/Contents/Resources/share/mythtv/metadata/Movie/tmdb3.py -t

>

On Fri, Jul 17, 2020 at 8:34 AM John Hoyt <john.hoyt@gmail.com> wrote:

> Just following up on the python issues - I've verified that everything
> internal to the application appears correct and the appropriate files are
> set executable.
>
> You absolutely need to have python3 of some sort (preferably 3.8 which I
> am building with) installed and located or symlinked to
> /opt/local/bin/python3.8
>
> To anyone having issues after verifying that python3 is installed and/or
> symlinked, please run these commands to help me troubleshoot (note you'll
> have correct APP_PATH to where your application is stored)
>
> APP_PATH=/Applications/Mythfrontend.app
>
> export PYTHONPATH=$APP_PATH/Contents/Resources/lib/python3.8/site-packages
>
> $APP_PATH/Contents/Resources/share/mythtv/metadata/Television/ttvdb.py -t
>
> $APP_PATH/Contents/Resources/share/mythtv/metadata/Movie/tmdb3.py -t
>

Steve - I may have figured out your metadata grabber issue. The app bundle
was missing the mysqlclient pieces. I've now copied them into the latest
build. Please test when you get a chance and if that fails, send me the
output of the debug commands from my last email (above).

James - still no OSD fix, but Mark has an idea what the problem is.

On Fri, Jul 17, 2020 at 3:25 PM John Hoyt <john.hoyt@gmail.com> wrote:

> On Fri, Jul 17, 2020 at 8:34 AM John Hoyt <john.hoyt@gmail.com> wrote:
>
>> Just following up on the python issues - I've verified that everything
>> internal to the application appears correct and the appropriate files are
>> set executable.
>>
>> You absolutely need to have python3 of some sort (preferably 3.8 which I
>> am building with) installed and located or symlinked to
>> /opt/local/bin/python3.8
>>
>> To anyone having issues after verifying that python3 is installed and/or
>> symlinked, please run these commands to help me troubleshoot (note you'll
>> have correct APP_PATH to where your application is stored)
>>
>> APP_PATH=/Applications/Mythfrontend.app
>>
>> export PYTHONPATH=$APP_PATH/Contents/Resources/lib/python3.8/site-packages
>>
>> $APP_PATH/Contents/Resources/share/mythtv/metadata/Television/ttvdb.py -t
>>
>> $APP_PATH/Contents/Resources/share/mythtv/metadata/Movie/tmdb3.py -t
>>
>
> Steve - I may have figured out your metadata grabber issue. The app
> bundle was missing the mysqlclient pieces. I've now copied them into the
> latest build. Please test when you get a chance and if that fails, send me
> the output of the debug commands from my last email (above).
>
> James - still no OSD fix, but Mark has an idea what the problem is.
> _______________________________________________
> 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
>

Hi John,

Sorry I mis-spoke about the OSD. It is working fine for me, but that is
likely a function of the fact I'm running on a mini connected to the TV and
not using a built-in display like a laptop.

I've downloaded your latest build, but unfortunately no joy:

2020-07-18 09:23:18.326442 I Running Grabber:
/Applications/Mythfrontend.app/Contents/Resources/share/mythtv/metadata/Movie/tmdb3.py
-l en -a US -C 105

2020-07-18 09:23:18.575312 I Metadata Lookup Failed: No Results Back to
the Future 0 0

2020-07-18 09:23:18.741871 I No results found for Back to the Future 0 0


It looks like there's an issue with the grabbers:

familymini@familymini ~ % APP_PATH=/Applications/Mythfrontend.app

familymini@familymini ~ % export
PYTHONPATH=$APP_PATH/Contents/Resources/lib/python3.8/site-packages

familymini@familymini ~ %
$APP_PATH/Contents/Resources/share/mythtv/metadata/Television/ttvdb.py -t


The modules tvdb_api.py (v2.0 or greater).

They should have been installed along with the MythTV python bindings.

Error:(No viable database module found.)


familymini@familymini ~ %
$APP_PATH/Contents/Resources/share/mythtv/metadata/Movie/tmdb3.py -t

Failed to import MythTV bindings. Check your `configure` output to make
sure installation was not disabled due to external dependencies

Failed to import PyTMDB3 library. This should have been included with the
python MythTV bindings.


Here's what I have installed:

familymini@familymini ~ % port installed requested

The following ports are currently installed:

exiv2 @0.27.2_0 (active)

lame @3.100_1 (active)

libbluray @1.1.2_0 (active)

libsamplerate @0.1.9_1 (active)

python38 @3.8.3_0 (active)

qt5 @5.14.0_0 (active)

qt5-mysql-plugin @5.14.0_0+mariadb55 (active)

qt5-qtscript @5.14.0_0 (active)

qt5-qtwebkit @5.9.1_4 (active)

taglib @1.11.1_0 (active)

x264 @20191217_0 (active)

x265 @3.2.1_0 (active)

yasm @1.3.0_0 (active)
--

-Steve
________________________
"destroying the fundamental underpinnings of the broadcast television
ecosystem"

On 7/18/20 11:40 AM, scram69 wrote:
>
>
> On Fri, Jul 17, 2020 at 3:25 PM John Hoyt <john.hoyt@gmail.com <mailto:john.hoyt@gmail.com>> wrote:
>
> On Fri, Jul 17, 2020 at 8:34 AM John Hoyt <john.hoyt@gmail.com <mailto:john.hoyt@gmail.com>> wrote:
>
> Just following up on the python issues - I've verified that everything internal to the application appears correct and the appropriate
> files are set executable.
>
> You absolutely need to have python3 of some sort (preferably 3.8 which I am building with) installed and located or symlinked to
> /opt/local/bin/python3.8
>
> To anyone having issues after verifying that python3 is installed and/or symlinked, please run these commands to help me
> troubleshoot (note you'll have correct APP_PATH to where your application is stored)
>
> APP_PATH=/Applications/Mythfrontend.app
>
> export PYTHONPATH=$APP_PATH/Contents/Resources/lib/python3.8/site-packages
>
> $APP_PATH/Contents/Resources/share/mythtv/metadata/Television/ttvdb.py -t
>
> $APP_PATH/Contents/Resources/share/mythtv/metadata/Movie/tmdb3.py -t
>
>
> Steve - I may have figured out your metadata grabber issue.  The app bundle was missing the mysqlclient pieces.  I've now copied them into
> the latest build.  Please test when you get a chance and if that fails, send me the output of the debug commands from my last email (above).
>
> James - still no OSD fix, but Mark has an idea what the problem is.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org <mailto: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
>
>
> Hi John,
>
> Sorry I mis-spoke about the OSD.  It is working fine for me, but that is likely a function of the fact I'm running on a mini connected to the TV
> and not using a built-in display like a laptop.
>
> I've downloaded your latest build, but unfortunately no joy:
>
> 2020-07-18 09:23:18.326442 I  Running Grabber: /Applications/Mythfrontend.app/Contents/Resources/share/mythtv/metadata/Movie/tmdb3.py -l en -a
> US -C 105
>
> 2020-07-18 09:23:18.575312 I  Metadata Lookup Failed: No Results Back to the Future 0 0
>
> 2020-07-18 09:23:18.741871 I  No results found for Back to the Future 0 0
>
>
> It looks like there's an issue with the grabbers:
>
> familymini@familymini ~ % APP_PATH=/Applications/Mythfrontend.app
>
> familymini@familymini ~ % export PYTHONPATH=$APP_PATH/Contents/Resources/lib/python3.8/site-packages
>
> familymini@familymini ~ % $APP_PATH/Contents/Resources/share/mythtv/metadata/Television/ttvdb.py -t
>
>
> The modules tvdb_api.py (v2.0 or greater).
>
> They should have been installed along with the MythTV python bindings.
>
> Error:(No viable database module found.)
>
>
> familymini@familymini ~ % $APP_PATH/Contents/Resources/share/mythtv/metadata/Movie/tmdb3.py -t
>
> Failed to import MythTV bindings. Check your `configure` output to make sure installation was not disabled due to external dependencies
>
> Failed to import PyTMDB3 library. This should have been included with the python MythTV bindings.
>
>
> Here's what I have installed:
>
>
> familymini@familymini ~ % port installed requested
>
> The following ports are currently installed:
>
>   exiv2 @0.27.2_0 (active)
>
>   lame @3.100_1 (active)
>
>   libbluray @1.1.2_0 (active)
>
>   libsamplerate @0.1.9_1 (active)
>
>   python38 @3.8.3_0 (active)
>
>   qt5 @5.14.0_0 (active)
>
>   qt5-mysql-plugin @5.14.0_0+mariadb55 (active)
>
>   qt5-qtscript @5.14.0_0 (active)
>
>   qt5-qtwebkit @5.9.1_4 (active)
>
>   taglib @1.11.1_0 (active)
>
>   x264 @20191217_0 (active)
>
>   x265 @3.2.1_0 (active)
>
>   yasm @1.3.0_0 (active)
>
> --
>
> -Steve

Just playing along here, not a Mac user. Is there a file named: mythproto.py
anywhere on the host. I use the locate command, but find works.


echo $PYTHONPATH # Must be valid or ignore the next ls

ls -ld $PYTHONPATH $PYTHONPATH/*

--
Bill
_______________________________________________
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

>
> Just playing along here, not a Mac user. Is there a file named:
> mythproto.py
> anywhere on the host. I use the locate command, but find works.
>
>
> echo $PYTHONPATH # Must be valid or ignore the next ls
>
> ls -ld $PYTHONPATH $PYTHONPATH/*
>
> --
> Bill
>

Steve, can you double check and confirm that you are trying to use
the 89d1991ef2 version (high sierra, I haven't updated the Catalina builds
in a bit)? Sourceforge tells me that no one has downloaded it yet
(wouldn't be the first time Sourceforge was wrong...).

Also, please run Bill's suggested commands - that was I can compare to my
system.

Thanks!
John

Have you run the following to make sure macports is using the correct
python?:

sudo port select python python38

sudo port select python3 python38


BTW - this is what I get with everything working

XXX@XXX Downloads % APP_PATH=~/Downloads/Mythfrontend.app
XXX@XXX Downloads % export
PYTHONPATH=$APP_PATH/Contents/Resources/lib/python3.8/site-packages
XXX@XXX Downloads %
$APP_PATH/Contents/Resources/share/mythtv/metadata/Television/ttvdb.py -t
Everything appears to be in order
XXX@XXX Downloads % ls -ld $PYTHONPATH $PYTHONPATH/*
drwxr-xr-x@ 46 XXX staff 1472 Jul 17 18:06
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages
drwxr-xr-x@ 13 XXX staff 416 Jul 17 11:31
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/MySQLdb
drwxr-xr-x@ 22 XXX staff 704 Jul 17 18:04
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/MythTV
-rw-r--r--@ 1 XXX staff 373 Jul 17 18:04
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/MythTV-31.0._1-py3.8.egg-info
drwxr-xr-x@ 8 XXX staff 256 May 15 09:03
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/PyMySQL-0.9.3-py3.8.egg-info
drwxr-xr-x@ 26 XXX staff 832 May 15 08:34
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/asn1crypto
drwxr-xr-x@ 7 XXX staff 224 May 15 08:34
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/asn1crypto-1.3.0-py3.8.egg-info
drwxr-xr-x@ 7 XXX staff 224 May 15 09:02
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/blinker
drwxr-xr-x@ 6 XXX staff 192 May 15 09:02
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/blinker-1.4-py3.8.egg-info
drwxr-xr-x@ 7 XXX staff 224 Jul 3 11:40
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/certifi
-rw-r--r--@ 1 XXX staff 3269 Jun 23 01:44
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/certifi-2020.06.20-py3.8.egg-info
drwxr-xr-x@ 23 XXX staff 736 May 15 08:34
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/cffi
drwxr-xr-x@ 9 XXX staff 288 May 15 08:34
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/cffi-1.14.0-py3.8.egg-info
drwxr-xr-x@ 43 XXX staff 1376 May 15 09:02
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/chardet
drwxr-xr-x@ 7 XXX staff 224 May 15 09:02
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/chardet-3.0.4-py3.8.egg-info
drwxr-xr-x@ 10 XXX staff 320 May 15 08:34
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/cryptography
drwxr-xr-x@ 8 XXX staff 256 May 15 08:34
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/cryptography-2.9.2-py3.8.egg-info
drwxr-xr-x@ 4 XXX staff 128 May 15 09:02
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/curl
drwxr-xr-x@ 11 XXX staff 352 May 15 09:01
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/future
drwxr-xr-x@ 7 XXX staff 224 May 15 09:01
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/future-0.18.2-py3.8.egg-info
drwxr-xr-x@ 11 XXX staff 352 Jul 3 11:40
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/idna
drwxr-xr-x@ 6 XXX staff 192 Jul 3 11:40
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/idna-2.10-py3.8.egg-info
drwxr-xr-x@ 13 XXX staff 416 May 15 09:02
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/jwt
drwxr-xr-x@ 24 XXX staff 768 May 15 09:02
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/lxml
drwxr-xr-x@ 8 XXX staff 256 May 15 09:02
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/lxml-4.4.1-py3.8.egg-info
drwxr-xr-x@ 6 XXX staff 192 Jul 17 11:31
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/mysqlclient-1.4.6-py3.8.egg-info
drwxr-xr-x@ 9 XXX staff 288 May 15 09:02
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/oauthlib
drwxr-xr-x@ 8 XXX staff 256 May 15 09:02
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/oauthlib-1.0.3-py3.8.egg-info
drwxr-xr-x@ 16 XXX staff 512 May 15 08:34
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/pycparser
-rw-r--r--@ 1 XXX staff 909 Mar 18 04:34
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/pycparser-2.20-py3.8.egg-info
-rw-r--r--@ 1 XXX staff 4690 Mar 21 03:57
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/pycurl-7.43.0.5-py3.8.egg-info
-rwxr-xr-x@ 1 XXX staff 151552 Mar 21 03:57
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/
pycurl.cpython-38-darwin.so
drwxr-xr-x@ 17 XXX staff 544 May 15 09:03
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/pymysql
drwxr-xr-x@ 21 XXX staff 672 Jul 3 11:41
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/requests
drwxr-xr-x@ 8 XXX staff 256 Jul 3 11:41
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/requests-2.24.0-py3.8.egg-info
drwxr-xr-x@ 7 XXX staff 224 May 15 09:02
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/requests_cache
drwxr-xr-x@ 7 XXX staff 224 May 15 09:02
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/requests_cache-0.5.0-py3.8.egg-info
drwxr-xr-x@ 14 XXX staff 448 May 15 09:02
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/simplejson
-rw-r--r--@ 1 XXX staff 3415 Nov 21 2019
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/simplejson-3.17.0-py3.8.egg-info
-rw-r--r--@ 1 XXX staff 1988 May 25 05:12
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/six-1.15.0-py3.8.egg-info
-rw-r--r--@ 1 XXX staff 34159 May 21 11:25
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/six.py
drwxr-xr-x@ 16 XXX staff 512 May 15 09:02
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/urllib3
drwxr-xr-x@ 7 XXX staff 224 May 15 09:02
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/urllib3-1.25.9-py3.8.egg-info
drwxr-xr-x@ 14 XXX staff 448 May 15 09:03
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/wheel
drwxr-xr-x@ 9 XXX staff 288 May 15 09:03
/Users/XXX/Downloads/Mythfrontend.app/Contents/Resources/lib/python3.8/site-packages/wheel-0.34.2-py3.8.egg-info

>

After digging into the python .so files deeper, it looks like my current
build process has the python related .so files looking into /opt/local for
any additional support libraries. This explains why James and I are able
to get the metadata grabbers working as we've used the build script which
installs everything necessary.

I've just tried copying those support libraries into the app and linking
them but unfortunately doing so broke all metadata grabbers in the
process. I'm going to try to keep hacking at this another day with
fresh eyes.

Stev, in the meantime, the current best way to get metadata grabbers
working is to install the necessary python pieces via macports. The
following command should do the trick:

sudo port install py38-future py38-requests py38-requests-cache py38-lxml
py38-oauthlib py38-curl py38-simplejson py38-wheel py38-pip py38-pymysql
py38-mysqlclient

I'll add a note to the sourceforge page.

>

> On 19 Jul 2020, at 12:40 am, scram69 <scram69@gmail.com> wrote:
>
> James - still no OSD fix, but Mark has an idea what the problem is.

Everytime you post I eagerly scan :-)
James
_______________________________________________
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 18, 2020 at 4:15 PM John Hoyt <john.hoyt@gmail.com> wrote:

> After digging into the python .so files deeper, it looks like my current
> build process has the python related .so files looking into /opt/local for
> any additional support libraries. This explains why James and I are able
> to get the metadata grabbers working as we've used the build script which
> installs everything necessary.
>
> I've just tried copying those support libraries into the app and linking
> them but unfortunately doing so broke all metadata grabbers in the
> process. I'm going to try to keep hacking at this another day with
> fresh eyes.
>
> Stev, in the meantime, the current best way to get metadata grabbers
> working is to install the necessary python pieces via macports. The
> following command should do the trick:
>
> sudo port install py38-future py38-requests py38-requests-cache py38-lxml
> py38-oauthlib py38-curl py38-simplejson py38-wheel py38-pip py38-pymysql
> py38-mysqlclient
>
> I'll add a note to the sourceforge page.
>
>> _______________________________________________
> 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
>

John,

After about 30 minutes building mariadb, installing all of those
dependencies you listed finally did the trick. I got the "Everything
appears to be in order" message from the test, and the grabbers were able
to fetch metadata.

Thanks again for your help! Hopefully this troubleshooting exercise
ultimately results in the ability to build the app with all dependencies
included-

Steve
--
________________________
"destroying the fundamental underpinnings of the broadcast television
ecosystem"

>
> Thanks again for your help! Hopefully this troubleshooting exercise
>> ultimately results in the ability to build the app with all dependencies
>> included-
>>
>
Steve, thanks for the update - this confirms that the python install is the
culprit (thank you to Bill as well as I never would have stumbled on this
without you suggesting the library paths).

Still banging my head against the python deployment problem and have run
out of ideas. It may just be a reality that users who want working python
bindings may have to install the necessary support packages via macports.
This is what happens in Ubuntu (i.e. apt installs all of the appropriate
python goodies), I was just hoping to get them inserted and running in the
application somehow...

> On Jul 19, 2020, at 4:45 PM, John Hoyt <john.hoyt@gmail.com> wrote:
>
> Thanks again for your help! Hopefully this troubleshooting exercise ultimately results in the ability to build the app with all dependencies included-
>
> Steve, thanks for the update - this confirms that the python install is the culprit (thank you to Bill as well as I never would have stumbled on this without you suggesting the library paths).
>
> Still banging my head against the python deployment problem and have run out of ideas. It may just be a reality that users who want working python bindings may have to install the necessary support packages via macports. This is what happens in Ubuntu (i.e. apt installs all of the appropriate python goodies), I was just hoping to get them inserted and running in the application somehow…


I’m not really familiar with how it the python bindings should work in the bundled app*…but around 2014, one of the devs modified the official packaging script to make them functional. Perhaps you can glean something from his commit:

https://github.com/MythTV/packaging/commit/e44052360ea268d0cf927897140e6e06134391ae#diff-6d1353539e2de6c424680420280cc319

Craig
*This was one of the key reasons I only pursued installing Myth in the ‘linux’ fashion. Prior to the above commit, I didn’t think it was possible to make the bindings work.

On 7/19/20 3:45 PM, John Hoyt wrote:
> Thanks again for your help!  Hopefully this troubleshooting exercise ultimately results in the ability to build the app with all
> dependencies included-
>
>
> Steve, thanks for the update - this confirms that the python install is the culprit (thank you to Bill as well as I never would have stumbled on
> this without you suggesting the library paths).
>
> Still banging my head against the python deployment problem and have run out of ideas.  It may just be a reality that users who want working
> python bindings may have to install the necessary support packages via macports.  This is what happens in Ubuntu (i.e. apt installs all of the
> appropriate python goodies), I was just hoping to get them inserted and running in the application somehow...

Fish out of water here, but the Ansible task:

- name: install packages
become: yes
become_user: root
become_method: sudo
macports:
name:
'{{ lookup("flattened", macports_pkg_list) }}'
update_cache: yes

uses the macports command to install the packages. I don't know why they're not
going to the proper place.

You could run ansible with -vvv and look through (the very large) output
to see it it makes sense.

--
Bill
_______________________________________________
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

>
> uses the macports command to install the packages. I don't know why
> they're not
> going to the proper place.
>
> You could run ansible with -vvv and look through (the very large) output
> to see it it makes sense.
>

Bill - they are going to the correct place and macports/ansible is working
correctly. Anyone who installs the python packages either manually or with
ansible seems to have a fully working setup. The issue is trying to get a
fully bundled application where anyone can download it and run the
application without the need to install anything (beyond maybe just
python38) from macports.

To that end, I've got everything working and bundled into the application
except for the python executable and the python support packages (e.g.
py39-mysqlclient, py38-lxml). The MyhTV python bundles builds and installs
correctly.

Craig - thanks for the pointer. I'll take another pass at that build
script (and more specifically that check in). There's some magic with
install_name_tool and the osx_bundler.pl script that I'm missing and
hopefully those will give me the proper insights. The interesting thing to
note is that when I install python38 (and the extra packages) into the
application as a framework (with all support libraries), the application
stops seeing the MythTV python package even though it is present and pathed
correctly (I tested the path by modifying one of the metadata grabbers to
dump the sys.path to a file).

Thanks for the pointers, I'll keep hacking at it.

>
> Craig - thanks for the pointer. I'll take another pass at that build
> script (and more specifically that check in). There's some magic with
> install_name_tool and the osx_bundler.pl script that I'm missing and
> hopefully those will give me the proper insights. The interesting thing to
> note is that when I install python38 (and the extra packages) into the
> application as a framework (with all support libraries), the application
> stops seeing the MythTV python package even though it is present and pathed
> correctly (I tested the path by modifying one of the metadata grabbers to
> dump the sys.path to a file).
>

Craig - it looks like the osx_bunder.pl script downloads and compiles the
python packages as static libraries - this is why they were able to be
shipped with the application without modification. MacPorts compiles
the necessary python parts (mysqlclient, lxml, curl) with dynamic
libraries (point back to /opt/local/lib), so any *.so files copied into the
application need to have their support .so or .dylib files copied into the
app's framework and re-linked to the app's internal Framework and not
/opt/local/lib.

osx_bundler.pl does a lot of the necessary magic copying the dynamically
linked libraries into the application Framework directory and even updates
the link internal to the .so files with "install_name_tool" to a new path
relative to the executable (example:
"@executable_path/../Frameworks//mariadb.framework//mariadb") - BUT the
application can't seem to follow the @executable_path links.

If I update all of the "@executable_path" links in app's
Resources/lib/python3.8/sites-available .so files with install_name_tool to
non-relative (i.e. hard code) paths pointing to the libraries copied into
the Framework by osx-bundler.pl everyhting works. Unfortunately since
these are now hard linked to my filesystem, the app will break if I move it
to any new directory.

I feel like I'm a relative path away from wrapping this up - just can't
seem to stumble on the right path for the requesting application
(mythmetadata).

>
> I feel like I'm a relative path away from wrapping this up - just can't
> seem to stumble on the right path for the requesting application
> (mythmetadata).
>

I believe the latest versions of MythFrontend.app that I just uploaded to
SourceForge (https://sourceforge.net/projects/mythtvformacosx/) fix the
python and metadata grabber issues.

Getting python portable was quite a bit more involved than I originally
thought (been hacking at this for the past week - lots of dead ends...).
The new builds now include a portable version of python3. The trick to
getting this to work was using py2app to build a portable version of one of
the metadata grabbers (ttvdb.pl seems to work best as it has the most
dependencies).

I also had to steal a play from the mythbuntu folks where the application's
executable is now an sh script that sets some local variables (mainly
PYTHONHOME and PYTHONPATH) then calls the real executable now named
"mythfrontend.real".

I've tested that the new applications work on a clean (i.e. no macports no
python3) High Sierra VM, so hopefully no one comes across any new python
related issues :)

BTW - Are there any devs out there kind enough to take on my Trac ticket
getting the compile script into the packaging baseline (
https://code.mythtv.org/trac/ticket/13642)? It could certainly use a
review and probably some verified testing by other users - BUT - it seems
to be working very well for me and I've put a substantial amount of hours
into it at this point...

>

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

> I feel like I'm a relative path away from wrapping this up - just can't
>> seem to stumble on the right path for the requesting application
>> (mythmetadata).
>>
>
> I believe the latest versions of MythFrontend.app that I just uploaded to
> SourceForge (https://sourceforge.net/projects/mythtvformacosx/) fix the
> python and metadata grabber issues.
>
> Getting python portable was quite a bit more involved than I originally
> thought (been hacking at this for the past week - lots of dead ends...).
> The new builds now include a portable version of python3. The trick to
> getting this to work was using py2app to build a portable version of one of
> the metadata grabbers (ttvdb.pl seems to work best as it has the most
> dependencies).
>
> I also had to steal a play from the mythbuntu folks where the
> application's executable is now an sh script that sets some local variables
> (mainly PYTHONHOME and PYTHONPATH) then calls the real executable now named
> "mythfrontend.real".
>
> I've tested that the new applications work on a clean (i.e. no macports no
> python3) High Sierra VM, so hopefully no one comes across any new python
> related issues :)
>
> BTW - Are there any devs out there kind enough to take on my Trac ticket
> getting the compile script into the packaging baseline (
> https://code.mythtv.org/trac/ticket/13642)? It could certainly use a
> review and probably some verified testing by other users - BUT - it seems
> to be working very well for me and I've put a substantial amount of hours
> into it at this point...
>
>> _______________________________________________
> 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
>

Hi John,

I tested this build today on my High Sierra frontend (no macports) and it
could successfully use the metadata grabbers. Nice work!

I'm still trying to understand why on the High Sierra frontend, regardless
of which build I use, I can't get rid of the Mac OS menu bar at the top of
the screen, either for the gui or playback. I've been through every
setting in Appearance.
Am I correct in assuming that only the files in the "Catalina" folder were
built with 10.15, and everything else was built with 10.13?

Steve
--
________________________
"destroying the fundamental underpinnings of the broadcast television
ecosystem"

>
> I'm still trying to understand why on the High Sierra frontend, regardless
> of which build I use, I can't get rid of the Mac OS menu bar at the top of
> the screen, either for the gui or playback. I've been through every
> setting in Appearance.
>

I noticed that too during testing. I did notice that if I launch the app
and wait (i.e. don't change to anything else, just double click and wait
the LONG wait) the menu bar goes away. No clue how to fix it - it would
require some deeper knowledge of how mythtv renders and tells the OS that
the app goes full screen. If it really bothers you, I'd suggest opening a
ticket in trac (https://code.mythtv.org/trac).

On Catalina, none of these issues occur.


> Am I correct in assuming that only the files in the "Catalina" folder were
> built with 10.15, and everything else was built with 10.13?
>

I tried to annotate the sourceforge readme.md to help clear this up -
anything in the top level are built with High Sierra, anything in the
Catalina folder are built on Catalina (unless I screw up the upload which
can happen :) ).

Additionally, if you download a file and want to make sure you have the
right version, the compile script automatically puts the OS version in the
.dmg filename - so anything with a "10.13" in the filename was compiled on
High Sierra, anything compiles on Catalina has a 10.15 in the filename.