• 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: Enable system volume when driver doesn't
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Enable system volume when driver doesn't


  • Subject: Re: Enable system volume when driver doesn't
  • From: Stéphane Letz <email@hidden>
  • Date: Tue, 18 Mar 2008 12:08:43 +0100


Perhaps it would be possible to use Jack. I'm not sure. In order for OS X to
activate its master volume control, a device driver (Jack in this case) has
to reply correctly to a number of queries (getProperty calls) from the
system and then of course it has to implement that volume control
(setProperty call). This can be either a master volume control affecting all
output channels (in a group) or it can be separate volume controls for each
channel, in which case OS X (or whoever it is) will call all and every of
the controls when the user changes, what to the user appears as a master
volume control. Actually, the built-in analog audio device in MBP and iMac
presents to OS X two volume controls, one for the left and one for the right
channel. Yet to the user this appears as a one master control.



What kind of property the user-land driver would have to implement? Jeff can you help here?


Jack doesn't answer these queries and doesn't implement volume control. One
would have to modify Jack. That needs not to be simpler than writing
volume-controlling-only device driver. That depends on support that one
would receive for current Jack authors and maintainers, on how well it is
written, commented, documented, and on how many cooks there were during its
development history, so to speak. Some open source code is beautiful, some
is ugly, and some I wouldn't touch with a pair of tongs. Then there are
robustness and easy-to-pre-configure issues - from what I saw in user's
manual, Jack would need a lot of polishing in these areas to be useful in my
environment.

Current Jack on OSX maintainer is essentially one (me..) doing what I can, and perfectly knowing that things are far from perfect. I consider the jack server and JackRouter infrastructure to be quite solid now, and the real weakness being in the configuration tools and user experience (JackPilot)


But you're invited to participate in this open source project.



There are plenty of pieces of the solution to your problem that are
available, but it seems that you're complaining that you can't trivially
plug a bunch of existing products together and have your own business
model. You've got to add some value if you want to be a VAR. ;-)

There you go again - off topic. Your comment here is based on your own
assumption of what I'm adding or not. You don't have a slightest idea about
that. You start with wrong assumption and therefore your conclusion is
incorrect.

Regards

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


  • Follow-Ups:
    • Re: Enable system volume when driver doesn't
      • From: "Mikael Hakman" <email@hidden>
  • Prev by Date: Re: ExtendedAudioFile on iPhone
  • Next by Date: rendering multiple audio inputs
  • Previous by thread: Re: Enable system volume when driver doesn't
  • Next by thread: Re: Enable system volume when driver doesn't
  • Index(es):
    • Date
    • Thread