Maybe you should put it not simply. USB already works as described with many
apps, utilities and tools. For example, with QuickTime Broadcaster the user
selects a device, a codec and a destination. With USB sound inputs or outputs
the user can select drivers and encoders from preferences or within apps.
Command line tools on systems other than Apple offer tools for selecting
devices, encoding and destinations, which Apple offers in tools available in
QuickTime or in the I/OKit.
Sent from my iPad
> On Sep 21, 2016, at 1:20 PM, Andy Peters <de...@latke.net> wrote:
>> On Sep 20, 2016, at 4:53 PM, Mark Brandon Leavenworth
>> <theleavenwor...@gmail.com> wrote:
>> Let me restate the proposition with more clarity. I envision a standard and
>> secure Apple utility or app where the user selects a device, port or socket,
>> a driver (with a prompt for the recommended driver), a codec or encoder, and
>> a second device, socket, port or file. For a device, socket or port,
>> selection would be made for 'transmit' or 'receive' or 'both' while for a
>> file, even though the codec could be binary, text, or various other options,
>> either 'transmit' (read) or 'receive' (write), but not 'both' could be
>> selected. The app or utility, in turn, ought to be scriptable with
>> What are the technical or security concerns or objections?
> Put simply, that’s not at all how USB works, so the rest of the discussion is
> Do not post admin requests to the list. They will be ignored.
> Usb mailing list (Usb@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> This email sent to theleavenwor...@gmail.com
Do not post admin requests to the list. They will be ignored.
Usb mailing list (Usb@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
This email sent to arch...@mail-archive.com