RE: Confusing problem with GetComponentInfo()
RE: Confusing problem with GetComponentInfo()
- Subject: RE: Confusing problem with GetComponentInfo()
- From: "Chris Reed" <email@hidden>
- Date: Sun, 17 Nov 2002 18:37:55 -0600
- Thread-topic: Confusing problem with GetComponentInfo()
Robert,
Yes, I've used the debugger to verify that the ComponentDescription is valid before calling FindNextComponent(). I have no way to verify the Component that you get back since it's just an array of bytes, but then GetComponentInfo() returns noErr so I assume it's OK.
The same ComponentDescription is used to get the name and to create a graph node, and the graph node is created just fine.
The other oddity is that the exact same method is used to fill in the name fields at app initialisation and when the user selects a new component. And for the same AU, it will always work at init time and always fail when the user selects it during runtime.
I've also derez'd the resource files for the problem nodes and of course everything looks correct.
Perhaps I will try using the other fields on GetComponentInfo() and see if they return anything valid, or if they too are left untouched.
Btw, I'll be adding MusicEffect support to SynthTest soon (probably), so maybe I'll be able to help figure out why AUMIDIController isn't working for you.
Thanks
-chris
-----Original Message-----
From: Robert Grant [
mailto:email@hidden]
Sent: Sat 11/16/2002 1:08 PM
To: Chris Reed
Cc: email@hidden
Subject: Re: Confusing problem with GetComponentInfo()
On Friday, November 15, 2002, at 04:27 PM, Chris Reed wrote:
>
>
The problem is, for certain components (always the same ones,
>
apparently), GetComponentInfo() does not fill in the name handle if
>
called when the user selects a new component from the menu.
>
Hi Chris,
As far as I can tell there should be no difference in the operation of
this function no
matter when or how many times it can be called. If it worked once then
it should work
every time. Are you sure the ComponentDescription is not getting
trashed at some
point? Or the AU is not bogus? I had an a bug with AUGraphNewNode one
time where
it was saying it loaded it but then wouldn't wire it up. The
ComponentDescription I'd used
to create the node was uninitialized!
I guess I'm trying to say that the culprit is probably somewhere
else...?
Of course I'm trying to track down why the AUMIDIController isn't
controlling my
MusicEffects.... All the functions are returning OK status too :-)
Good luck,
Robert.
_______________________________________________
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.