Rép : Problems when changing sample rate on a aggregate device (2)
Rép : Problems when changing sample rate on a aggregate device (2)
- Subject: Rép : Problems when changing sample rate on a aggregate device (2)
- From: Stéphane Letz <email@hidden>
- Date: Wed, 5 Dec 2007 15:21:16 +0100
Message: 9
Date: Tue, 4 Dec 2007 08:49:50 -0800
From: Jeff Moore <email@hidden>
Subject: Re: Problems when changing sample rate on a aggregate device
To: CoreAudio API <email@hidden>
Message-ID: <email@hidden>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Your main problem appears that you are not waiting for the
notifications from the HAL before blindly continuing your
configuration code. Basically, you are assuming what you set actually
took without actually making sure by waiting for the notifications
from the HAL to finish shaking out. This is probably causing your
configuration code to run while the HAL is still updating it's
internal state, which is giving you an incoherent view of the device.
You should _never_ assume any call to change device configuration has
succeeded successfully until you get _all_ the notifications. For an
aggregate device, this can take a while given that there are many
devices whose state is changing.
To complete: this buggy behavior can actually be reproduced using AMS
and HALLAB:
- changing SR from AMS on the aggregate device, no change in HALLAB
- using the file player tool in HALLAB, changing SR from AMS on the
aggregate device,, file player stopping....
Stephane Letz
_______________________________________________
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