"Define" instruments grayed out

Hi - just tested this out for you.

I do not normally have my Yamaha midi keyboard checked in Preferences>Midi>Devices section, because my soft-synths have WAY better sounds than the on-board ones of my cheesy YPG-235.  I bought it because it has 76 notes, and I use it to play mostly piano sounds through Kontakt 5.

OK, like you indicate in your post, when I went to Preferences>Midi>Instruments, I couldn't really do anything.

So, in a thinking it through for a moment moment, I went back to the Devices and checked on my Yamaha keyboard in the Output devices section.

Then I went back to Instruments, and this time I have a BUNCH of stuff listed on the left side, and when I choose one of the lefts and one of the rights, I can then click on define and I get the instrument definitions dialog box.

Give this a shot and please post back to tell me if that addressed this issue for you, 

Bob Bone

Good question, that.  The brether thing.

So X1, in inputs/outputs under devices, doesn't list the Motif.  Doesn't show up, which is weird, bc when I connect it via USB to the Mac, the Mac asks, do you want it to talk to Windows or Mac...etc.  Of course I say Windows.  




So there's another teeny weenie factoid I failed to mention, but I think it has no bearing - which is I'm running sonar on a mac within a partition using VMWare Fusion, which contains Windows 7.  But it's a physical partition, etc.

Until you have a MIDI device installed and checked in Prefs--->MIDI devices, you won't be able to define an instrument as there's nothing to define it to.

That's where the problem is. As to installing drivers on a MAC for windows, I can't help there I'm afraid. Having said that last time I used a MAC with bootcamp it was pretty much the same as installation on a PC.

Perhaps another MAC user will jump in and help with that part.

Hi all,

OK, so, I realized, hey, this is a device and it needs this things called a "driver". :).  So here's how that went.  I went to the Yamaha site and downloaded the Windows 7 driver.  I went through the process when suddenly it pronounced that my processor was not up to snuff for the driver, or some such.  So I downloaded the Mac driver and of course no problem.  Went back to Windows, and there's the Motif in Devices still lacking a driver, so I ran the driver program again (for windows of course) and same problem occurred, not the right processor or whatever.  So I think the lack of a driver is the problem.  How to fix?  I have absolutely no clue.  

Eric

robert_e_bone


Erik, your last post contained this: "So there's another teeny weenie factoid I failed to mention, but I think it has no bearing - which is" followed by the blah blah blahs.


It is my experience that these so-called 'tiny' things are ALWAYS Colonel Mustard in the Study with the Lead Pipe (lots of times it is the seemingly insignificant things that are the culprits)


Any other Mac folk out there???

I will circle back after finishing helping a couple of other folks out - I truly do not know what I am doing with Macs, but will see if you still need help and will try to provide it.

Mac folks???   RRRRed Robin! - (I was hoping a Mac user would respond with a hearty 'YUM'), 

Bob Bone

Unfortunately no driver = no device but I'm surprised the driver relies on a certain amount of processor power.

Perhaps it's just because you are running Windows on bootcamp? I think someone who knows more about MACs and bootcamp is needed.

Ducati - You may be completely correct - I have no Mac knowledge whatsoever.  Anybody????

Bob Bone