An alternate process for building and installing Myth on OS X; particularly the backend.
Better Mac backend
The current Perl-based build processes are great for producing a self-contained Mac frontend. But if you want to run the backend on OS X, then having the essential programs packaged deep in an application bundle is less than ideal. The MacPorts distribution aims to make it much easier to install the backend and run it in a production mode:
- Full support of the Perl/python bindings. This means that standard Myth backup, optimization, and metadata functions will work.
- Install and run Myth like other 'server-type' software such as MySQL, file-sharing, web-serving, etc. Control the Myth backend with standard OS X functions (launchctl) and have the system start automatically during the boot process.
- Provide the full suite of myth programs, if you need them, like mythmetadatalookup, mythutil, etc. This, in turn, means that various user jobs and scripts from the wiki will function with fewer glitches and modifications.
The documentation on this page will focus on running the Myth master backend (version 0.27), including the MySQL database server, on an OS X machine. Using the MacPorts install it is also possible to run the machine as a slave backend or job queue server. It may be possible to run the machine as a Myth media server; this configurations hasn't been tested. If you do, please share the results by updating these pages!
Consistent, repeatable build process
MacPorts is a stable and mature system for bringing open-source software to the Mac platform. Changes are tested and reviewed before being committed to MacPorts. MacPorts operates some build slaves (Mountain Lion, Lion and Snow Leopard, all on 64 bit machines, currently) which automatically build the default variant of each port. All this means that if you decide to try building with MacPorts, there is a strong likelihood that it will just work. And, if it doesn't, there is an active support system working to resolve any problems.
On OS X, diving into the command line just to start the Myth frontend isn't very 'Mac-like'! So the MacPorts installation of Myth included a handful of simple Applescript applications to make common activities just a little more convenient:
Myth_Setup and Myth_Filldatabase are probably only going to be necessary when you first confgure Myth or make major changes. Myth_Frontend, however, is the preferred way to start the frontend. You may want to drag the Myth_Frontend icon onto your Dock if you plan to use it regularly.
Myth_Stop_Start provides a simple way to start the Myth backend and to schedule daily log file rotation and pruning. Note that the Myth backend is run as a server process. That means, if enabled, it starts automatically when OS X is started--no user needs to be logged on. Similarly, f you click "Stop MythBackend", the server process will remain disabled through restarts, etc.
The script looks for a MySQL server running on the current machine and won't start the backend without one. If your database server is running on another machine on your network, this script won't work for you. You'll have to manually issue the appropriate launchctl commands.
Myth generates a LOT of log files. We use logrotate to keep the most important ones (mythbackend, mythfrontend, mythtv-setup, etc) for two months and to delete those created by some of Myth's 'utility' programs (mythpreviewgen, mythcommflag, mythfilldatabase, mythmetadatalookup, etc).
- Myth 0.27 AirPlay support may not work. http://code.mythtv.org/trac/ticket/11901
- PPC and 32 bit Intel support has been dropped in 0.26 and later. It appears possible to support these platforms but time is limited and hardware that is 6-plus years old is barely up to the task anyway. If someone wants to help, contact me on the macports-users or mythtv-users mailing lists and I'll try to point you in the right direction.
- Myth 0.26 may prevent your system from going to sleep. Even when the system is otherwise not doing anything, mythlogserver passes 'heartbeat' messages with any running client programs, such as mythbackend. OS X interprets this message passing as work being performed and therefore does not put the system to sleep. The system may therefore use more electricity.
- Myth 0.26 logging may fail in some circumstances. If mythlogserver is not currently running, it will not be automatically launched by starting another Myth program from the command line (eg mythfrontend, mythutil, mythshutdown, etc). OS X's Console app will show crash reports (possibly many) for mythlogserver. However, a backend machine with mythbackend started via Myth_Stop_Start will always have mythlogserver running and will therefore not exhibit this problem. The applescript helpers for MythFrontend, MythFillDatabase and Myth-Setup all ensure that mythlogserver is either running or started before launching any of these programs.
Plugins are not installed.
Building Myth on OS X via MacPorts
See Building Myth for Mac with MacPorts for details
The MacPorts build process has been successfully tested on OS X 10.5, 10.6, 10.7, and 10.8. Building with firewire support to capture mpeg streams from a set top box has been successfully implemented under 10.5.8 on a PPC G5, and under 10.8.2 on an Intel Mini.
Before first run
This section assumes you are using MySQL database server software installed via MacPorts. The server portion of the software is installed with the following command.
sudo port install mysql5-server
- If this is your first installation of Myth on this machine, Myth's database (mythconverg) has to be intialized, and the server software started, with the following three commands:
sudo -u _mysql mysql_install_db5 sudo port load mysql5-server mysql5 -u root -p < /opt/local/share/mythtv/database/mc.sql
Look in Activity Monitor to see that the "mysqld" is running. We can't go further until it is!
- A one-time step is required to install support for multiple time zones in MySQL. Follow the procedure on MySQL Time Zone Tables to ensure that your MySQL installation is ready for Myth 0.26 or 0.27. Doing this will not affect the operation of Myth 0.25, either.
Note, on MySQL on my system, the user "mythtv" has the password "mythtv" but the user "root" has no password. (Don't tell anyone, OK? I don't want my database hacked! ;) Terminal may not be able to find the commands unless you enter the full path. The commands that worked for me were:
/opt/local/lib/mysql5/bin/mysql -u mythtv -p mythconverg /opt/local/lib/mysql5/bin/mysql_tzinfo_to_sql /usr/share/zoneinfo | /opt/local/lib/mysql5/bin/mysql -u root mysql
Media Storage Locations
Next, Myth needs to be told where to store all your media. It is common to dedicate one or more external disks--and usually not the startup disk--to hold your recordings, videos, music, etc. At the bare minimum, create at least one new folder to use as the default for everything that Myth wants to store. More commonly, you'll have separate directories for TV, Videos, Music, Images, and Metadata. It will be simpler to use volume and folder names that do not include spaces. On OS X, the path to a folder on an external drive is "/Volumes/<drive_name>/<folder_name>".
Initial Myth Setup
After you've created the directories you want to use (and made note of the paths), you must run the mythtv-setup program. You can do this from the command line but there is also an Applescript (Myth_Setup) short cut. Be sure to complete each of the steps.
You will likely need to run Myth_Filldatabase at this point to populate the fill in all those television programs that your tuner(s) will be able to record. Unfortunately, the Applescript can't show the progress of this program as it runs. Activity Monitor should list mythfilldatabase as it is running and it should finish within a few minutes.
Start It Up!
We're getting close now. With Myth's setup done, it is time to start the backend. Use the Myth_Start_Stop Applescript to start the backend. Again, in Activity Monitor you should see a new line for "mythbackend".
The grand finale: start up the frontend with the Myth_Frontend Applescript. Hopefully all has gone well and you're off and running with Myth on OS X!!
To do: running the Job queue on other OS X machines ...