• 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: How to capture the audio of an output device in OSX
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to capture the audio of an output device in OSX


  • Subject: Re: How to capture the audio of an output device in OSX
  • From: Admiral Quality <email@hidden>
  • Date: Wed, 10 Sep 2014 09:09:24 -0400

Just curious then Paul. Why does my pro-sumer Edirol UA-1000, as well
as every other USB and Firewire audio interface I've ever used, work
as full duplex in applications? (Wouldn't be much good if it didn't!)

- Mike

On Wed, Sep 10, 2014 at 7:42 AM, Paul Davis <email@hidden> wrote:
>
>
> On Wed, Sep 10, 2014 at 12:12 AM, Dodo <email@hidden> wrote:
>>
>>
>> Hi all,
>>
>>
>> reading the doc of Jack, i find:
>>
>> "- New Mac Intel use 2 different CoreAudio device for input/output.
>> Jackdmp cannot directly handle 2 devices to do duplex processing. An
>> "aggregate" device has to be built in this case.
>> Use the "/Applications/Utilities/Audio MIDI Setup" tool to build and
>> aggregate device that combine both input and output in a single duplex
>> device, then select it when launching jackdmp, with something like :
>> ....
>> ....
>> jackdmp -R -d coreaudio -n "~:Aggregate:0"
>>
>> or directly with the JackPilot tool.
>> "
>>
>>
>> So, it seems to me that Jack uses an aggregate device to carry out its
>> task....and I'm not cool with that.
>
>
> This is out of date documentation. JACK creates an aggregate device
> programmatically when necessary.
>
> Perhaps you are not aware that since the switch to Intel, Apple has *never*
> presented the builtin audio chipset as a single duplex device. Thus
> applications that have duplex behaviour have to either handle two different
> devices or use an aggregate **if they want to use the builtin audio
> chipset**.
>
> Pro- and prosumer (in fact, almost any USB or Firewire) audio interfaces do
> not behave this way - they appear as single duplex-capable devices.
>
>
>  _______________________________________________
> 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
 _______________________________________________
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: How to capture the audio of an output device in OSX
      • From: Paul Davis <email@hidden>
References: 
 >How to capture the audio of an output device in OSX (From: claudio santoro <email@hidden>)
 >Re: How to capture the audio of an output device in OSX (From: Frederic De Jaeger <email@hidden>)
 >Re: How to capture the audio of an output device in OSX (From: Zack Morris <email@hidden>)
 >Re: How to capture the audio of an output device in OSX (From: Paul Davis <email@hidden>)
 >Re: How to capture the audio of an output device in OSX (From: Dodo <email@hidden>)
 >Re: How to capture the audio of an output device in OSX (From: Paul Davis <email@hidden>)

  • Prev by Date: Re: How to capture the audio of an output device in OSX
  • Next by Date: Re: How to capture the audio of an output device in OSX
  • Previous by thread: Re: How to capture the audio of an output device in OSX
  • Next by thread: Re: How to capture the audio of an output device in OSX
  • Index(es):
    • Date
    • Thread