This entry was posted
on Monday, September 18th, 2006 at 7:18 pm and is filed under Apple, MythTV, Open Source, Multimedia, Software, Mac OS X Intel.
You can follow any responses to this entry through the RSS 2.0 feed.
You can skip to the end and leave a response. Pinging is currently not allowed.
21 Responses to “MythFrontend 0.20 Mac OS X Intel”
After previously using Matt’s 0.19 binary on my Macbook, I ran into a problem with running his 0.20 binary. Playing recordings and live tv came out distorted.
I was able to get it working by deleting all the settings for my Macbook on the backend. (At the cost of losing all the settings for my Mac’s frontend.)
delete from settings where hostname=’macbook’;
Just something to try if anyone else runs into this problem.
Thanks, Matt, for providing these convenient Myth binaries!
What you’ve run into sounds like possibly the issue that is mentioned on the MythTV wiki’s OS X x86 page about turning on the vector assisted video routines - if they’re not on the video ends up distorted. Could you confirm this was the issue?
I experienced exactly the same problem with distorted playback. The solution was to enable the vector optimized colorspace option as mentioned on the wiki. What made me to be totally ignorant for that option was that it used be an altivec optimized, something not so relevant on a Intel mac…
Thanks for the packages. What i’m wondering though is how to get sound working on the mac mini with spidf? OSX apparently doesn’t have a /dev/audio or /dev/mixer
Hey matt. There have been a bundle of problems with database stuff on the 0.20 version and now the latest 0.20 build seem sto be running protocol 31, not 30. Any chance of a rebuild on the latest protocol? Thanks for all you work!
I’ve been building off the release-0-20 tag. Are the protocol 31 builds tracking some branch, or are people using the trunk? If you can give me more specifics on how to checkout a “known good” revision or tag, I’d be happy to do this.
I’m running the 0.20 that came from Ubuntu Edgy’s repositories as my backend, and I’m getting the same problem as Lex says: the backend is running protocol 31.
Anyone run into the problem (this build and the universal) where Mythfrontend just hangs on startup? It seems to load but then just sits in my Dock with no black arrow until I Force Quit. I don’t see anything on the screen. Tried a few different builds with the same problem. x86 Intel Core Duo
September 19th, 2006 at 12:57 pm
Good stuff! I just finished setting up my 0.20 backend and now can run myth on my new macbook. Thanks from downunder.
September 20th, 2006 at 9:52 pm
After previously using Matt’s 0.19 binary on my Macbook, I ran into a problem with running his 0.20 binary. Playing recordings and live tv came out distorted.
I was able to get it working by deleting all the settings for my Macbook on the backend. (At the cost of losing all the settings for my Mac’s frontend.)
delete from settings where hostname=’macbook’;
Just something to try if anyone else runs into this problem.
Thanks, Matt, for providing these convenient Myth binaries!
September 20th, 2006 at 11:27 pm
I’m glad to help out where I can!
What you’ve run into sounds like possibly the issue that is mentioned on the MythTV wiki’s OS X x86 page about turning on the vector assisted video routines - if they’re not on the video ends up distorted. Could you confirm this was the issue?
Regardless, thanks for the info and workaround.
September 21st, 2006 at 12:30 pm
I experienced exactly the same problem with distorted playback. The solution was to enable the vector optimized colorspace option as mentioned on the wiki. What made me to be totally ignorant for that option was that it used be an altivec optimized, something not so relevant on a Intel mac…
And, Matt, thanks for the binaries!
September 23rd, 2006 at 5:09 am
spot on - thanks!
September 24th, 2006 at 12:56 pm
Thanks for the packages. What i’m wondering though is how to get sound working on the mac mini with spidf? OSX apparently doesn’t have a /dev/audio or /dev/mixer
September 24th, 2006 at 6:54 pm
Does anyone have a full front-end + back-end running on OSX?
I’m looking at the HDHomeRun as the tuner (Ethernet based), so I don’t need any hardware PCI support.
Nathan
nharris@eoimaging.com
September 25th, 2006 at 4:32 pm
Intel only huh?
I’m still on PPC - any word on getting a PPC version (or Universal)?
It would be much appreciated. Thanks.
September 25th, 2006 at 7:33 pm
I’ve given the PPC build a whirl twice and it has failed both times. Still tinkering with it when I have spare time…
September 27th, 2006 at 2:24 am
Is this build with or without plugins?
If without, can you build a version with the (working) plugins ?
It would be much appreciated. Thanks.
September 27th, 2006 at 8:21 am
This build is with all plugins and themes.
September 27th, 2006 at 11:53 am
Thanks for all of your hard work!
The apple remote feature was great in .19. Is there any plans to reinclude that for .20?
Thanks,
Chris
September 27th, 2006 at 11:54 am
I take that back! It works already!
Chris
September 28th, 2006 at 11:32 am
It seems to be using enormous amounts of RAM on my MacBook Pro? Around 5-600 MB? 0.19 only used around 100 MB. Apart from that it works great!
September 28th, 2006 at 1:13 pm
Hey matt. There have been a bundle of problems with database stuff on the 0.20 version and now the latest 0.20 build seem sto be running protocol 31, not 30. Any chance of a rebuild on the latest protocol?
Thanks for all you work!
September 28th, 2006 at 2:48 pm
Mads:
Interesting on the ram use. That is huge. I’m curious if it is the act of compiling in all the plugins and making the themes available?
September 28th, 2006 at 2:50 pm
lex:
I’ve been building off the release-0-20 tag. Are the protocol 31 builds tracking some branch, or are people using the trunk? If you can give me more specifics on how to checkout a “known good” revision or tag, I’d be happy to do this.
September 28th, 2006 at 7:45 pm
I think it’s a 0-20-fixes tag… I’m just trying to find out…
December 10th, 2006 at 4:31 pm
I’m running the 0.20 that came from Ubuntu Edgy’s repositories as my backend, and I’m getting the same problem as Lex says: the backend is running protocol 31.
Cheers,
Aaron.
February 13th, 2007 at 12:23 am
Anyone run into the problem (this build and the universal) where Mythfrontend just hangs on startup? It seems to load but then just sits in my Dock with no black arrow until I Force Quit. I don’t see anything on the screen. Tried a few different builds with the same problem. x86 Intel Core Duo
February 24th, 2007 at 12:51 pm
Wow very cool. I just got my first mac, an intel macbook pro and it works great. I’m very impressed. Thanks for all the hard work.