• 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: IO Proc doesn't behave as expected
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: IO Proc doesn't behave as expected


  • Subject: Re: IO Proc doesn't behave as expected
  • From: Chris Rolfe <email@hidden>
  • Date: Mon, 14 Mar 2005 23:57:04 -0800

On 3/12/05 11:59 AM, "Robert Grant" <email@hidden> wrote:
> There's something else going on here...

Thanks for the response (it gave me the spur to continue debugging...).

The problem seems to be my output unit initialization. I'm using a local
variable to set the output unit's format. I assumed that
AudioUnitSetProperty would copy the struct, but it appears to expect the
caller to retain the memory.

Assuming I'm not mistaken, is this by-design? Is it generally true of data
passed to AudioUnitSetProperty?

Chris



//=======================================================
// Code Example:

// !! BUG !! Local data. Call succeeds, but host callback generates garbage.
OSStatus setformat()
{
AudioStreamBasicDescription format = { 48000.0, type, flags, 4, 1, 4, 2, 32
};
OSStatus err = AudioUnitSetProperty (theUnit,
                            kAudioUnitProperty_StreamFormat,
                            kAudioUnitScope_Input,
                            0,
                            format,
                            sizeof(AudioStreamBasicDescription));

}

// Works! Static data. Call succeeds. Sine tones fill the air.
AudioStreamBasicDescription format = { 48000.0, type, flags, 4, 1, 4, 2, 32
};
OSStatus setformat()
{
OSStatus err = AudioUnitSetProperty (theUnit,
                            kAudioUnitProperty_StreamFormat,
                            kAudioUnitScope_Input,
                            0,
                            format,
                            sizeof(AudioStreamBasicDescription));
}


Chris


>
> Robert.
>
> On Mar 11, 2005, at 9:58 PM, Chris Rolfe wrote:
>
>> Taking for granted initialization, etc., can anyone suggest why
>> starting/sleeping/stopping an IO Proc works, but the same IO Proc might
>> produce garbage when start/stop are called from a Cocoa UI, a la:
>>
>>
>> This works fine:
>>
>> void start() {  AudioOutputUnitStart (unit);   }
>> void stop()  {  AudioOutputUnitStop  (unit);   }
>>
>> void test()
>> {
>>         start();
>>         usleep (4 * 1000 * 1000); // sleep this thread while audio
>> plays
>>         stop();
>> }
>>
>> This sucks:
>>
>> -(void) startButton () { start() ; }
>> -(void) stopButton ()  { stop() ; }
>>
>> TIA,
>> Chris
>>
>>
>>  _______________________________________________
>> 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
>

--
circular reasoning: a syllogism in which the premise depends on or is
equivalent to the conclusion; see, reasoning, circular.


 _______________________________________________
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

  • Follow-Ups:
    • Re: IO Proc doesn't behave as expected
      • From: William Stewart <email@hidden>
References: 
 >Re: IO Proc doesn't behave as expected (From: Robert Grant <email@hidden>)

  • Prev by Date: Re: auval missing in my system
  • Next by Date: Disconnecting an AudioUnitConnection
  • Previous by thread: Re: IO Proc doesn't behave as expected
  • Next by thread: Re: IO Proc doesn't behave as expected
  • Index(es):
    • Date
    • Thread