kAudioOutputUnitProperty_IsRunning doesn't correspond to the audio device running
kAudioOutputUnitProperty_IsRunning doesn't correspond to the audio device running
- Subject: kAudioOutputUnitProperty_IsRunning doesn't correspond to the audio device running
- From: Steve Checkoway <email@hidden>
- Date: Sat, 11 Nov 2006 04:24:56 -0800
When I change the default output's format (by changing from 44.1kHz
to 48kHz, for example), my audio unit property listener fires with
kAudioUnitProperty_StreamFormat. If I then call
AudioDeviceGetCurrentTime on the corresponding audio device, I get
the error kAudioHardwareNotRunningError but the
kAudioOutputUnitProperty_IsRunning never fires (as a result of the
device stopping).
I really need to keep the time stamps returned by
AudioDeviceGetCurrentTime() and those passed to my render function in
sync but I'm unsure how to do that in the face of changing output
formats.
Actually, looking back at my logs, it looks like when the
kAudioOutputUnitProperty_IsRunning fires for the first time I start
the output unit, the device is still saying that it isn't running.
Lastly, I'm setting kAudioOutputUnitProperty_StartTimestampsAtZero to
zero but this constant doesn't appear in the 2.8 sdk so I'm using the
constant 2007, will this not work on 2.8? (I realize I asked this
before in mid June, but no one answered.) If not, I need to deal with
this as well.
Any advice is very much appreciated.
--
Steve Checkoway
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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
- Prev by Date:
Re: Changing the Default audio input and output devices
- Next by Date:
kAudioOutputUnitProperty_IsRunning doesn't correspond to the audio device running When I change the default output's format (by changing from 44.1kHz to 48kHz, for example), my audio unit property listener fires with kAudioUnitProperty_StreamFormat. If I then call AudioDeviceGetCurrentTime on the corresponding audio device, I get the error kAudioHardwareNotRunningError but the kAudioOutputUnitProperty_IsRunning never fires (as a result of the device stopping). I really need to keep the time stamps returned by AudioDeviceGetCurrentTime() and those passed to my render function in sync but I'm unsure how to do that in the face of changing output formats. Actually, looking back at my logs, it looks like when the kAudioOutputUnitProperty_IsRunning fires for the first time I start the output unit, the device is still saying that it isn't running. Lastly, I'm setting kAudioOutputUnitProperty_StartTimestampsAtZero to zero but this constant doesn't appear in the 2.8 sdk s o I'm using the constant 2007, will this not work on 2.8? (I realize I asked this before in mid June, but no one answered.) If not, I need to deal with this as well. Any advice is very much appreciated. -- Steve Checkoway
- Previous by thread:
Re: Changing the Default audio input and output devices
- Next by thread:
kAudioOutputUnitProperty_IsRunning doesn't correspond to the audio device running When I change the default output's format (by changing from 44.1kHz to 48kHz, for example), my audio unit property listener fires with kAudioUnitProperty_StreamFormat. If I then call AudioDeviceGetCurrentTime on the corresponding audio device, I get the error kAudioHardwareNotRunningError but the kAudioOutputUnitProperty_IsRunning never fires (as a result of the device stopping). I really need to keep the time stamps returned by AudioDeviceGetCurrentTime() and those passed to my render function in sync but I'm unsure how to do that in the face of changing output formats. Actually, looking back at my logs, it looks like when the kAudioOutputUnitProperty_IsRunning fires for the first time I start the output unit, the device is still saying that it isn't running. Lastly, I'm setting kAudioOutputUnitProperty_StartTimestampsAtZero to zero but this constant doesn't appear in the 2.8 sdk s o I'm using the constant 2007, will this not work on 2.8? (I realize I asked this before in mid June, but no one answered.) If not, I need to deal with this as well. Any advice is very much appreciated. -- Steve Checkoway
- Index(es):