(2012-07-25, 18:23)davilla Wrote: If it's not broke, I would not upgrade for the kicks of it. Here's what happens, every single time Apple posts a new OSX version. Users upgrade without a thought, something does not work right, they get told to downgrade, then they start complaining
Personally, (and I'm a dev too) I never, ever update a box that I depend on until maybe years after the update pops out. Why, the first one is always buggy as hell, and it takes a few rounds of get things right.
Hint, my mainline production boxes run 10.6.8, why ? It's stable as all get out
Well, my old media server was a PowerMac Digital Audio from 2001 and while it was updated to ~2005 specs with a 1.8GHz G4, etc., Apple dumped all support for it in iTunes, etc. (not to mention surfing was getting slow and virtually all official browsers dumped it as well), so NOT upgrading wasn't exactly an option at this point unless all I ever wanted it to do was serve XBMC. Thus, I bought a new computer and guess what, they come with Mountain Lion, not 10.6.8 Snow Leopard. So the idea of not upgrading for stability reasons is great and all, but not exactly practical at times.
My experience using Eden on ATV1 (which I guess is where it will stay since I was told XBMC will not be updated for Gen1 ATVs running Apple's own software anymore...so much for NOT updating operating systems, I guess) is that AFP is more or less broken since most of my tv shows will pretty much lock up after about a half hour or so and from what I've read on here, it will not likely ever be fixed (and even if it is, ATV Gen1 won't see the fixes either way).
SMB is broken in Mountain Lion for anything but browsing files from XBMC (i.e. media files won't play), so I used SMBUp to switch to Samba3. This "mostly" works, but I've found some truly odd behaviors as well. For instance, I have a photo gallery set of directories and most images load fine. However, one entire batch of photos (that loaded fine from my old server) refuse to load now, BUT if I use AFP instead for that directory, those same files load just fine (slaps head in frustration). Fortunately, I think AFP is stable enough for just pictures, but I can't fathom why it refuses to load them in SMB only. No file renaming helps, but re-encoding via Photoshop did result in a readable version (but why do they work with AFP and the old server's SMB?)
Similarly, I've found some TV Shows that will not load correctly with Samba3 from Mountain Lion. One entire DVD series won't play, but again, if I use AFP instead, they play just fine (and they played fine from the old PPC Leopard server with SMB). An episode of a show which I encoded myself with Handbrake in HD does the same thing (worked fine on old server with SMB but only plays with AFP now, but AFP risks a lock-up sooner or later). All the SD versions of the show I had previously encoded work fine with SMB. Other shows I encoded in HD with the same Handbrake settings work fine with SMB so I'm totally baffled as to what the cause of the issue is.
On the other hand, on the old server there were a few movies that would not play correctly in XBMC (e.g. The Black Hole Anchor Bay DVD I encoded to M4V would have audio but no picture before, but the newer Disney release I encoded played fine, but now they both play fine on the new server (one still doesn't show the "SD" logo, though).
Ultimately, I had to choose between running an old server that had no redeeming features for other applications (browser out of date, iTunes no longer supported, etc.) but worked fine with XBMC or switching to a brand new Mac Mini Quad-Core i7 that should be usable for many years to come. Of course, I had no idea that the new machine would present any real issues when I got it. Overall, I like Mountain Lion better than Snow Leopard (other than the loss of Rosetta, which had some impact here for a few apps, but running Wine and/or VMWare Fusion let me use Windows versions instead and they weren't used much anyway.) Sadly, I guess the server software was better in Snow Leopard (making it a snap to set up NFS shares instead whereas it's been removed from the server software in Mountain Lion and you have to manually set it up or buy some 3rd party software to do what Apple used to apparently do just fine from what I've read. There's also WebDav, but I have not been able to get it to work yet with XBMC (directory shows up empty or with some odd sub-folders and it was supposed to be just a one-click affair).
At the rate Apple is starting to move with OS updates and dumping support for older computers, the idea of remaining with a stable version of the OS like Snow Leopard forever will quite probably become less and less realistic. And if developers stick with older machines, it's just that much more likely that things will break for people with newer computers. I guess too bad for them. Personally, I'm starting to think it might be simpler in the long run to just convert all my AVI and MKV files over to M4V and then I can be sure they will work in AppleTV's own GUI. OTOH, Apple's newer ATV units (I also have one ATV Gen2 unit) also sometimes fail to play files for reasons unknown. I have a few HD movies I encoded myself with Handbrake that played fine on ATV Gen1 and in iTunes on the new computer, but just sit there with the busy thing running in ATV2 (other moves encoded using the same Handbrake settings play just fine and so again, I have no idea what it is the ATV doesn't like that any other computer plays just fine with.) Personally, I find it all frustrating. I just wanted to not have to use DVDs and/or BDs anymore (the server and ATVs let me just beam the entire library around the house and sync to my iPod Touch, etc. easily so it sucks when a file doesn't work for reasons unknown).