Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Device unplugged, how application should handle the situation?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Device unplugged, how application should handle the situation?

Subject: Re: Device unplugged, how application should handle the situation?
From: Rustam Muginov <email@hidden>
Date: Tue, 13 Dec 2005 14:10:13 +0300

On Nov 11, 2005, at 10:45 PM, Jeff Moore wrote:

What would be better strategy to the application which does allow user to choose from sound devices for input and output. track the "device gone" situation, track the "default system sound input/output changed" e.t.c.?

I need the application to switch to other devices "on the fly" then current i/o device is gone.
I'd use AUHAL, which has support for all of that.

Jeff, how does AUHAL handles "device unplugged" event? Is it possible to make AUHAL automaticaly "switch" to another device and continue input/output when device unplugged? Thank you.

--
Sincerely,
	Rustam Muginov

_______________________________________________
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: Device unplugged, how application should handle the situation?
From: Jeff Moore <email@hidden>


Prev by Date:
Re: Blocked in MIDIClientCreate

Next by Date:
How to play a waveform?

Previous by thread:
Re: AUGraph Serialization

Next by thread:
Re: Device unplugged, how application should handle the situation?

Index(es):

Date
Thread