Ezbus/audio Midi Setup Weirdness, Anybody else experience this? Options

[Levon River]

For some weird reason that is entirely beyond my ken, Apple's Audio MIDI Setup will *not* retain the EZBus as the "Selected Audio Device." It's startin' to get on me nerves.

In the "Default Input" dropdown it has EZbus. In the "Default Output" dropdown it has EZbus. But for "Selected Audio Device" it has "Built-in audio controller" showing in the dropdown. If I drop it down, EZBus is there to select. So I select it (which then opens a whole "Input Section" that wasn't there before I selected it). So I quit Audio MIDI Setup. And *every time* I go back into it, it has changed "Selected Audio Device" back to "Built-in audio controller."

I've tried changing it, then rebooting. No go. I can't find any preferences file that I can trash. So now I'm at the end of my rope.

Does anybody know what in tarnation is going on here and how to fumigate the gremlins?

[Levon River]

Hello Levon,

I'm having exactly the same problem as you with my EZbus and the Audio Setup in Mac OS 10.2.4.  Choose EZbus.  Close, reopen, and it's gone, back to Built-in audio controller.  Did you find out what was going on?

Cheers,

Philip

Hey, phillip: didn't mean to ignore anybody here--I get weirdnesses happening in the forum read/not read indicators from time to time (they all go dark), and I just flat out missed replies to this thread.

No, I've never found out or figured it out. Having read buserror's later replies, I'm still not sure I get it entirely, but I'll just take it at face value. Things are working (for the most part)--I just don't understand why or how, and the point, I guess, is that the people who create these things MAKE it *impossible* to find out.

I understand that one of the people very instrumental in creating Audi MIDI Setup and other aspects of Core Audio and Core MIDI is the same person who brought us OMS. As far as I'm concerned, OMS was to creativity as a blender on "LIQUEFY" is to kittens, and it was because of this *exact* twisted "logic" in interface.

Another example of this same brand of madness from AMS (which example obviously was lifted right out of OMS) is this: in the MIDI pane, click on (or create) a "device" (synth or sound module), then select it and click on the "Show Info" pane, and open "More Properties." See all those "Transmit" and "Receive" buttons? Now put yourself in the head of a newbie and try to answer this question: "Are they "on," or are they "off"? Now click on one. Did you turn it "on," or did you turn it "off?" Do you know? Can you tell? Is it labled ANYWHERE? Is there ANY documentation that gives you ANY clue of what the default state is?

The answer to ALL questions above is a *resounding* *N O*!!

Of course, this is ONLY the absolute most rock-bottom, fundamental, and important setting you can make on that synth or sound module.

This kind of "you figure it out" mentality MUST arise out of either insufferable arrogance or a "dropped on their head" incident. It's just so mind-numbingly incomprehensible, you just...

Okay, I have to take a walk now.

But then these same people who "design" this kind of weenieness all scratch their heads and wonder why they are *swamped* with support phone calls and e-mails.

"Is it plugged in?"

Plug THIS in.



This post has been edited by Levon River: Sun 13 Apr 2003, 16:20