Mac OSX

  • Thread starter Thread starter bdemenil
  • Start date Start date
Mac users, per capita, tend to know how to keep their systems running better than PC users

I don't know about that. The whole thing about Mac is that it's supposed to be easier to configure / more user friendly / easier for the non-techy. So from that perspective, Mac attracts people who are not particularly technology oriented - at least when it comes to hardware and OS configuration.

Of course, the PC is such a commodity that many PC users are completely clueless when it comes to technology.

Allot of people do go around saying Mac is more stable than PC, so if the two are about the same, as you just stated, then that's something that people should know about - considering stability is one of Mac's big selling points.

I could be wrong, but I'd guess if you took a sampling of professional studios running OSX with Protools, you'd find a good number of them have to reboot at least once in a day of normal use.
 
I have no idea why that should ever be the case.

I use my Mac DAW as not just a DAW, but my everyday computer, and I rarely need to restart. (Though I do have MIDI problems sometimes that require a restart, but that is M-Audio's problem, whether they believe me or not. It's their shoddy drivers.)
 
Okay, audio hardware going wonky.... sounds like a driver bug. What kind of audio interface was this? If it's external, try unplugging and replugging. If it's PCI... well, the reboot is basically power cycling the card and reloading the drivers. If the hardware is flaky, the power cycle could be working around the problem. If the software is flaky, well, you can probably fix that by manually unloading and reloading the driver.

To try that... check in /System/Library/Extensions and see if there's a driver bundle for your card. If so, the next time the interface wedges, instead of rebooting, launch Terminal.app (it's in /Applications/Utilities). Then type:

sudo kextunload /System/Library/Extensions/MyAudioInterface.kext

substituting the actual name of the driver extension for your audio interface. Now hit return. Type the admin password when prompted. Then, at the next command prompt, type:

sudo kextload /System/Library/Extensions/MyAudioInterface.kext

See if that cures the problem. If it does, scream at the company that made your audio interface. If it doesn't... scream at the company that made your audio interface. :D
 
hahaha, are you serious?

Yes, I am

I've worked with different UNIX based OSes - as a programmer and as a system administrator. WinXP is as stable, although it's true XP is a resource hog (but from the look of the OSX UI, OSX might not be so efficient either - is all that animation really necessary?). There may be certain applications for which a good UNIX based OS has a clear stability advantage over Windows - but not in the realm of home use/ standard workstation/ or Multimedia workstation.

Now I'm sure that if as much time and money was invested into developing a UNIX based OS as has been invested into developing Windows, we'd all be better off.
 
OMG sum d00d on this site said Mac sux, i bettr cancel my Mac order!!!??!!
 
bdemenil said:
By the way, it's great that OSX has incorporated many pieces of Unix (BSD) architecture. UNIX is a wonderful environment to work in - I certainly wish Windows was as efficient, well organized and transparent as a good Unix OS. However, UNIX isn't foolproof either, and these days a good Windows system is as stable as a good UNIX system (in most applications).

It doesn't incorporate Unix. It's built on Unix; Darwin to be specific.

bdemenil said:
I don't know about that. The whole thing about Mac is that it's supposed to be easier to configure / more user friendly / easier for the non-techy. So from that perspective, Mac attracts people who are not particularly technology oriented - at least when it comes to hardware and OS configuration.

It may appear to be "stupid friendly" on the surface, but the Unix backbone provides plenty of features for the advanced user.
 
Back
Top