More ludicrous behavior from the digidesign CoreAudio drivers
More ludicrous behavior from the digidesign CoreAudio drivers
- Subject: More ludicrous behavior from the digidesign CoreAudio drivers
- From: Christopher Penrose <email@hidden>
- Date: Wed, 10 Sep 2003 13:06:10 -0400
Installing CoreAudio drivers makes ALL your audio drivers single
client! What kind of arrogance is this?
I know that someone's feelings may be involved here, but I just can't
fathom how inconsiderate the digidesign CoreAudio drivers are to users
and developers. What about our time? What about our wasted
institutional dollars on this completely uncooperative
hardware/software combinations (Protools LE and the mBox)? Because of
the arrogant single-client design, we have been forced to use multiple
audio devices (mBox and Apple built-in hardware); now I have discovered
that this is further complicated this:
Even while using the Apple Built-in Hardware, I discovered that I have
a single-client audio driver as long as the CoreAudio drivers are
installed -- NO MATTER WHAT HARDWARE I AM USING. I had two audio
applications open; I used the first perfectly well through the Apple
built-in hardware; after the audio playback had completed in the first
application, I tried to use the second application..... it crashed.
Never had I seen this before. I tried with a commandline application
and got a traceable bus error. The code trace is below and clearly
implicates the Digidesign audio driver. The error goes away if you
close the first application. Why the Digidesign code is even being
executed while I am using the Apple built-in hardware? The sound is
clearly coming from my laptop speakers, and not the mBox.... Why do
they arrogantly usurp the entire driver?
Program received signal EXC_BAD_ACCESS, Could not access memory.
0x00c23d7c in LowIOSetPeripheralValue ()
(gdb) bt
#0 0x00c23d7c in LowIOSetPeripheralValue ()
#1 0x00b0f334 in unknown_text ()
#2 0x00b0f448 in unknown_text ()
#3 0x00c24480 in RawDeviceAdded(void*, unsigned) ()
#4 0x00c24378 in DoInstallNotification(void*) ()
#5 0x00b0ed30 in unknown_text ()
#6 0x00b0ee68 in unknown_text ()
#7 0x00b0f294 in unknown_text ()
#8 0x00b0ef28 in unknown_text ()
#9 0x00adcc30 in unknown_text ()
#10 0x00ad7b4c in unknown_text ()
#11 0x00ae0cf0 in unknown_text ()
#12 0x00a10c74 in unknown_text ()
#13 0x004e124c in IODriverInit () at
../../../../Libs/Source/CDIOLibAccess.cpp:232
#14 0x004dfb68 in DigiCoreAudioDevice::GetDirectIO() (this=0x6aa40) at
../Source/DigiCoreAudioDevice.cpp:667
#15 0x004dfaa4 in DigiCoreAudioDevice::InitDirectIO() (this=0x6aa40) at
../Source/DigiCoreAudioDevice.cpp:631
#16 0x004dff90 in DigiCoreAudioDevice::Initialize() (this=0x6aa40) at
../Source/DigiCoreAudioDevice.cpp:845
#17 0x004de6c4 in DigiCoreAudioPlugIn::Initialize() (this=0x58250) at
../Source/DigiCoreAudioPlugIn.cpp:54
#18 0x004e6d80 in HPPlugInInitialize(AudioHardwarePlugInInterface**)
(inSelf=0x0) at
../../../../SDKs/AppleCoreAudio/HALPlugInSDK/HAL/PlugIns/
HPPlugInInterface.cpp:171
#19 0x94db3040 in HALPlugInDeviceFactory::Initialize() ()
#20 0x94db8638 in HALSystem::Initialize() ()
#21 0x94db86d8 in HALSystem::GetInstance() ()
#22 0x94d914e0 in AudioHardwareGetProperty ()
#23 0x0000245c in main (argc=2, argv=0xbffff02c) at betterplay.c:284
(gdb)
I am tempted to make a bumper sticker, and/or a t-shirt: DIGIDESIGN
OUT OF COREAUDIO!
This is completely asinine and unacceptable. What are these people at
Digidesign thinking? Do they believe that they can re-write their
customers' operating system as they see fit?
Do the people at Apple agree that this is a bad idea? Am I just
missing something? Are we all supposed to use Protools exclusively now
because none of our other software works once we install these drivers?
Frustrated beyond belief,
Christopher
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.