• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Looking at levels on a mixer
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Looking at levels on a mixer


  • Subject: Re: Looking at levels on a mixer
  • From: Neil Clayton <email@hidden>
  • Date: Tue, 12 Sep 2006 11:27:18 +0100

Yes. I can. I did lots of digging and found the reason though. Stupidity on my part. It turned out that I was incorrectly passing a reference to an Obj-C object (should have been the C++ one doing the play through). What was weird (and this was what made me thought it was kinda of working) was that in the debugger, I could correctly step through the code - just that it'd fail on those two read property calls. Anyway, sorted now. My own silly fault. Thanks for the Q in response though, it made me keep going and ask "why".

anyway ...

Is there a good paper somewhere on what must be initialized first, i.e: Open Graph, manipulate / connection, then initialize? (e.g:lifecycle stuff) for the various AU's? I suppose that's one of the things I've found most confusing. Things like: I can enable metering mode after I've set the output format on the mixed, but not before graph is initialized.

---
Neil Clayton



On 11 Sep 2006, at 19:55, William Stewart wrote:

Can you make other calls on mMixerUnit and it is still ok?

On 11/09/2006, at 11:23 AM, Neil Clayton wrote:

Hello everyone.

I'm going insane attempting to get some levels from a mixer (3d mixer in this case).
I can get as far as enabling metering (no error returned), and after that point I initialize the graph, but when I attempt to read using:


err = AudioUnitGetParameter(mMixerUnit, k3DMixerParam_PostAveragePower, kAudioUnitScope_Input, 0, &currentAmps);

I get -2147450879, or badComponentInstance (when I debug). mMixerUnit still seems to be set to a valid value.

Can anyone give me tips on what situations might cause this?

Regards,
---
Neil Clayton




_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com


This email sent to email@hidden

--
mailto:email@hidden
tel: +1 408 974 4056
______________________________________________________________________ ____
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
______________________________________________________________________ ____



_______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Looking at levels on a mixer (From: Neil Clayton <email@hidden>)

  • Prev by Date: Re: AU views and offset with composite windows
  • Next by Date: scaudiofillbuffer
  • Previous by thread: Looking at levels on a mixer
  • Next by thread: AU views and offset with composite windows
  • Index(es):
    • Date
    • Thread