MythGrowl Released
December 27th, 2006I’ve just finished writing MythGrowl - a fairly simple MAC OS X application that generates Growl notifications when your MythTV backend starts and stops recording or watching a show. You simply specify the IP address or hostname of your MythTV backend server and it will start notifying you. The application (universal binary) is available below.
Update: This is no longer the place to download MythGrowl. It has moved to http://mythgrowl.sourceforge.net/ Download the latest version there!
 |
Download now |
Complete source code can be downloaded here
I’m releasing MythGrowl under the GPL.
You have to promise to check for regular updates and report any bugs. I plan to implement the Sparkle update system in the next release.
Screenshots:
December 27th, 2006 at 9:18 pm
NICE!!
Thank-you, this looks very interesting.
January 7th, 2007 at 12:09 am
[...] MythGrowl Released [...]
January 27th, 2007 at 8:18 pm
Very nice app. I recompiled it for my ppc mac, my first ever experience with xCode. I would just like to ask, does it only work for notifications encoder 1? It doesn’t do anything when a recording starts on the second card.
January 30th, 2007 at 10:39 am
Hi Mike - I’m really glad you like the app, yes it seems that the compiled application is not a universal binary as I claimed. I will sort this out in the next release. That’s also a very good point you raised about it only notifying you when a recording starts on another encoder, I only have 1 tuner card so hadn’t given it any thought. I will be sure to fix this in the next release which should be in a week or so and it will have some other new features as well that I’m still working on.
Thanks a lot for the feedback and feel free to send any other feedback you might have my way.
March 4th, 2007 at 8:19 am
Hello,
I’m getting an error in XCode trying to recompile MythGrowl for PPC. Is there anyway you could either post the PPC version, or else verify that 0.3 still builds correctly under XCode?
My error:
Building target “MythGrowl†of project “mythgrowl†— (1 error, 1 warning)
cd /Users/joe/Desktop/mythgrowl
/usr/bin/gcc-4.0 -o /Users/joe/Desktop/mythgrowl/build/Debug/MythGrowl.app/Contents/MacOS/MythGrowl -L/Users/joe/Desktop/mythgrowl/build/Debug -L/Users/joe/Desktop/mythgrowl -F/Users/joe/Desktop/mythgrowl/build/Debug -F/Users/joe/Desktop/mythgrowl -filelist /Users/joe/Desktop/mythgrowl/build/mythgrowl.build/Debug/MythGrowl.build/Objects-normal/ppc/MythGrowl.LinkFileList -framework Cocoa -framework Growl-WithInstaller -framework AGRegex -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk
/usr/bin/ld: warning /Users/joe/Desktop/mythgrowl/AGRegex.framework/AGRegex cputype (7, architecture i386) does not match cputype (18) for specified -arch flag: ppc (file not loaded)
/usr/bin/ld: Undefined symbols:
.objc_class_name_AGRegex
collect2: ld returned 1 exit status
/usr/bin/ld: warning /Users/joe/Desktop/mythgrowl/AGRegex.framework/AGRegex cputype (7, architecture i386) does not match cputype (18) for specified -arch flag: ppc (file not loaded)
/usr/bin/ld: Undefined symbols:
.objc_class_name_AGRegex
collect2: ld returned 1 exit status
Build failed (1 error, 1 warning)
March 13th, 2007 at 7:25 pm
Any chance you could put that Sparkle framework in sometime soon?
March 18th, 2007 at 9:27 am
Adam-
Sparkle support has now been added as well as a number of other features you will hopefully like. The project has been moved to Sourceforge and can now be downloaded at
http://mythgrowl.sourceforge.net/
I’d love to hear any feedback you might have. Sorry it took so long.
March 21st, 2008 at 11:32 pm
Hi,
great app… well it looks like a great app. I cant get i to work, is there something else I have to do? I have put in the IP and left the port number standard 6544.
but no pop ups appear,i am on leaopard and the mythtv box is running myth version 0.20.2.
Can any one help?…….
March 30th, 2008 at 1:19 am
Joe-
If you use your web browser and goto http://your-myth-backend-ip:6544 does it show you the mythbackend status page? MythGrowl gets its info off that page so if you can’t access that from your browser then it definitely won’t work. Could a firewall be blocking the connection?
John