Re: More MIDIServer questions
Re: More MIDIServer questions
- Subject: Re: More MIDIServer questions
- From: Ethan Funk <email@hidden>
- Date: Mon, 3 Nov 2008 16:08:25 -0700
no, its because the switched out user is not the active user, so it
shouldn't be active. Audio behaves the same way.
Yes - I had to work a bit to get around that too... I run my daemon
under a user who never logs in via the GUI. As such, CoreAudio never
gets notified that the user has logged out and so the audio works
regardless of who is logged in. Otherwise, I would have to run it as
root (dangerous) and that would not be acceptable.
I don't know what this has to do with "exclusive" access - that is
not a semantic we have layered on top of this, but one you are
applying.
Our intention on only allowing a single active user was based
around what we though general user expectations would be.
We don't have any intention of changing this basic behaviour (which
I think we have also stated previously)
Bill
The reasoning behind this audio/midi behavior in the OS is good and
it is what I would expect. I have an unusual situation where my
software is running a broadcast and it MUST run regardless of what a
user does. The user accesses my daemon via a GUI front end
application. This makes it difficult for the user to do anything
that would stop the broadcast. In this case, the audio is not just a
user service: it must be running at all times.
I'm thinking now that MIDI machine control is not an option for this
application.
Thanks,
Ethan...
_______________________________________________
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