Re: issues with AUHAL input render
Re: issues with AUHAL input render
- Subject: Re: issues with AUHAL input render
- From: Jochen Fischer <email@hidden>
- Date: Mon, 10 Dec 2018 18:02:28 -0500
Hi Randy,
I have a Scarlett 2i2 and it works just fine via its macOS USB interface
without any special drivers.
However, I recall a few gotchas when I started using it. Try the following
things:
- Open the Audio MIDI Setup program. Select your Scarlett. Make sure the
input sampling rate is set to what you would expect.
- Set the default input device in System Preferences -> Sound to your
Scarlett channel.
The hope is to get some data with those settings. With everything set to
expected default values you should not have to change the ASBD. Once it
works, you can add the code to make adjustments programmatically.
Jochen
On Mon, Dec 10, 2018 at 3:25 PM Randy Locklair <email@hidden> wrote:
>
> Hi There:
>
> I’m working with a project that is using AUHAL to read data from an audio
> interface. I’ve isolated the issue I’m having to a very small and
> non-specific example which I am happy to share, but in an effort to keep
> the noise down I figured I’d try explaining it instead (its rather simple…)
>
> I have a very basic example that opens up an AUHAL unit and reads audio
> data from an input callback.
>
> I have 3 devices (well, two, one has two different drivers…) attached to
> the machine, and the code only works with one interface.
>
> I have an Electron Digitakt that has a Bit Accurate and a Core Audio
> driver, and I have a Focusrite Scarlett 18i20 with just its base driver.
>
> The Electron Bit Accurate driver works great— no matter what configuration
> I set up it works. An unchanged ASBD, a clear ASBD with 16 bit int data,
> etc., just about anything that makes sense works.
>
> I select either of the other devices, either the Electron on the Core
> Audio device, OR the Focusrite, and I just get zeros back from
> AudioUnitRender.
>
> Anyone ever run into anything like this and have any ideas?
>
> Thanks so much, I’ve been searching my butt off and haven’t found anything
> online…and the fact that its working with one but not the other driver for
> the same device has me going nuts (but hopefully is a big clue to someone
> else…)
>
> Thanks!!!
>
> Randy
> _______________________________________________
> 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