[MacPorts] #39714: mythtv-core.25 builds on ppc but scheduling fails

[MacPorts]

#39714: mythtv-core.25 builds on ppc but scheduling fails
-----------------------------+--------------------------
  Reporter:  swbhenderson@…  |      Owner:  ctreleaven@…
      Type:  defect          |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:  2.1.3
Resolution:                  |   Keywords:  ppc ppc64
      Port:  mythtv-core.25  |
-----------------------------+--------------------------

Comment (by kelsie@…):

 I've been building mythtv on ppc and Linux so we have some common issues.

 I'll share what I've learned from attempting builds 25/26 on Fedora 12/PPC

 As you have learned the import from a mythtv-setup scan of channels from a
 HDHR using OTA always imports the char set wrong? As a result as mentioned
 the channels are invisible. While that can be resolved with :
 *check that they are wrong with mysql


 {{{
 mysql> select visible from channel
     -> ;
 +---------+
 | visible |
 +---------+
 |       0 |
 |     127 |
 |     127 |
 |     127 |
 |     127 |
 |     127 |
 |     127 |
 |     127 |
 |     127 |
 |     127 |
 |     127 |
 +---------+

 Fix them:
 mysql> UPDATE  `mythconverg`.`channel` SET  `visible` =  '1' WHERE
 visible='127';
 Query OK, 10 rows affected (0.00 sec)
 Rows matched: 10  Changed: 10  Warnings: 0mysql> select visible from
 channel;
 +---------+
 | visible |
 +---------+
 |       0 |
 |       1 |
 |       1 |
 |       1 |
 |       1 |
 |       1 |
 |       1 |
 |       1 |
 |       1 |
 |       1 |
 |       1 |
 +---------+
 11 rows in set (0.00 sec)

 }}}


 This only works around the channels not showing up in the schedule. Then
 the channels in
 channel and dtv-multiplex need to be updated because the all have improper
 charsets for the channel names and such. I don't have a one line sql fix
 for this yet because of all the variables but
 you could use phpmyadmin and visually edit the fields and correct or you
 could just edit the channel data directly in mythtv-setup.

 Everything I've stated is probably redundant but I'm good a being cpt.
 obvious.

 However after performing the manual fixes to the db now I can use
 mythtv25/26 on ppc
 for schedules and recordings.

 I have a 10 year old iMac G4 1.2 that I've been testing on and It can't do
 more than 15fps on 1080p
 content and can barely manage 25fps for 720p using the internal
 play(ffmpeg) from mythtv.
 SD works fine for frontend playback and ...
 This next line will cause me some grief I'm sure but:

 You can use a G4 to play back HD in mythtv-25 if you use mythvideo and
 setup mplayer with some options such as lowres=1/skiploopfilter=all.
 ****tangent over

 ===Did anyone figure out why the channel imports are wrong with the
 charset? ====
 I haven't had a chance to compare the x86 vs ppc import.
 *Questions about the failed imported data into mysql.
   *I'll look into if someone can point me in the right direction.

 ****hdhr firmware related?
 ****mysql configuration differences on ppc vs x86?
 ****Is endianness really be related to cause of this mythtv-setup
 channelscan sql import since
 it half works?

 *I would file a bug report with mythtv for the 26.X releases, but ...Since
 now I'm probably #2 PowerPC 32 bit mythtv user ...
 I don't expect mythtv proper would acknowledge me much on this until I can
 present something on a silver platter.
 I've seen too many mythtv developer comments that suggest people with PPC
 move on
 to newer hardware.

 I'm particularly stubborn and since the mythtv and ffmpeg developers have
 insisted on upgrading by
 abandoning ppc32 efforts, it's up to the individuals such as us to find
 and suggest solutions.

 They don't see the reason in working on 10 year old hardware that uses
 more power with less performance. However my 10 year old  is making a fine
 backend and storage server since upgrading the hard drive to 1TB. For
 power it uses about 75W fully loaded and about 35 idle.

 I've gotten the message from some devs that they will not spend any brain
 power working on 10 year old hardware for naught. Hence the earlier silver
 platter reference.
 I don't mean to sound derogatory if interpreted as so.
 What mythtv proper does is not unique in dropping support of older
 hardware. I understand they have to keep an eye on the future only.

 If we work together though as users we can get some more use out of these
 old macs.

 *Yes 10 year old machines uses more power so.
 If your old mac uses more than 100W you might want to try and offset that
 somehow by using Wake On Lan or suspend where you can.

 Kelsie at ELmythOS.org

-- 
Ticket URL: <https://trac.macports.org/ticket/39714#comment:25>
MacPorts <http://www.macports.org/>
Ports system for OS X