Yamaha KX49 won't work with GarageBand

You probably need to explain exactly what you've done/tired/hooked-up, etc. so someone can try to help you.

Bradlez92 wrote:
Thanks to the one guy who got me to elaborate and get my noodle working ;D

Sometimes that's all it takes.

Bradlez92 wrote:
I figured it out. After some thinking, I read the "Read Me" file that came with the driver I got from the Yamaha website. I apparently installed it incorrectly. After deleting the bad driver, I redownloaded and followed procedure.

I went ape s--------hit when it worked.

Thanks to the one guy who got me to elaborate and get my noodle working ;D

What exactly did you do?

I'm trying to get it to work and I followed all the instructions but nothing will make it work. :/

Does it matter if you're booted into 64-bit when you actually install it? I booted into 32-bit after install and still, no dice. ...

PS -- I followed all the steps in the readme. I deleted all traces of the old driver and restarted. I disconnected all the USB things I could -- could not get all of them since the Mac Pro has some built-in hub or something that shows up in the list in USB area of System Profiler. Anyway then I ran the installer while logged in as my main user (who is an admin), and then restarted again, then hooked up the UX-16 device. It does not recognize it in Audio MIDI Setup, and the Yamaha preference pane crashes the System Preferences app after giving this message: " Alert Cannot access to a driver."

I tried adding my main user to the "wheel" group but that didn't help (I noticed it set all the group for the driver to "wheel"). I also tried to change the group of all the driver items to "admin" instead of "wheel" but that also did not help. I booted off OS X dvd and ran the permissions and disk repairs, and also redid my ACLs for my home folder (which took FOREVER). Now I'm going to repair prebindings and see if that helps...

I noticed I was having this problem with my Yamaha UX-16 and its Yamaha USB MIDI driver. I would get this dialog box error that says "Alert Cannot access to a driver." And then System Preferences would crash and of course we have this:

Exception Type: EXC BADACCESS (SIGSEGV)
Exception Codes: KERN INVALIDADDRESS at 0x0000000000000026

So I read where someone said that creating a new user fixes it. So I created a new user and of course that fixed it. But I also noticed where the guy said that he copied the Preferences folder from the new user to the old user and that fixed it for the old user. But why should it? I had a sneaking suspicion that permissions were involved. I was right. (Can I please say: I FRAKKING HATE PERMISSIONS!!)

As it turns out here is the cause of all our woes. Are you ready for this?

drumroll plz

The group of the folders in your Users/YourUser/ directory need to all be "staff" ....... that's it. Especially Users/YourUser/Library/Preferences ... once I set its group to "staff" then it worked.

PS -- to set it to staff, go to terminal and type su and then enter. Then type your password. Next type chown YourUser:staff /Users/YourUser/Library/Preferences ... you can also type ls -l to see what all folders in /Users/YourUser directory are set to groups other than staff. In my case, a lot of them were set to wheel instead... I have no idea why. I also don't know why farking Disk Utility is not smart enough to fix this! Give me a break Apple!

I strongly feel that the "permissions" system is the WORST feature of OS X, and it needs to be fixed or just plain done away with. I know that it supposedly makes the system more secure. But there weren't permissions in OS 9 and it was arguably even more secure than OS X. What's the point of permissions anyway if someone can just take an OS X install DVD and reset your password? LOL!

If you're going to keep permissions, Apple, then you need to make them easier to understand. Don't have group names like "wheel" and "staff" that are super-confusing and make no sense at all. I mean, seriously, nothing in the computer should be called "wheel," it's the most counter-intuitive and hard-to-understand thing I've ever heard of in my entire life, except for Jolly Ranchers brand Jello. If you're going to have a permissions repair feature in Disk Utility, which gives the user the impression that their permissions have been fixed, then you need to make sure *that it actually works*! Please!

Actually the previous post is not true.

Actually what happened is that once I had logged in as the new user and accessed the preference pane, then it started working on my old user. I thought it was because I changed groups on the folders, but no, that wasn't it.

Something in the older user is stopping it from being able to access the drivers. But on the new user it's fine. I still think it has something to do with permissions... but I don't know what... any ideas??

PS -- The old user is one that I migrated over.

Turns out there were two copies of the driver plugin: one in the Users/Me/Library/Audio/MIDI Drivers. And one in /Library/Audio/MIDI Drivers.

Cmon Apple. The Mac should be smart enough to detect driver conflicts.

Look in your console after it crashes... What are the errors?

A question for Daddie Mac please.

My Itunes 'unexpectedly quits' every time since updating on 1 April. I have a separate thread running on iTunes discussion about this.

In one of your posts here, you said "The group of the folders in your Users/YourUser/ directory need to all be "staff" ....... that's it. Especially Users/YourUser/Library/Preferences ... once I set its group to "staff" then it worked.

PS -- to set it to staff, go to terminal and type su and then enter. Then type your password. Next type chown YourUser:staff /Users/YourUser/Library/Preferences ... you can also type ls -l to see what all folders in /Users/YourUser directory are set to groups other than staff."

I tried this, but could not work out how to change the directory to "staff". Can you advise me please?

Regards

Paul