Re: Tiger Audio Units and 96kHz
Re: Tiger Audio Units and 96kHz
- Subject: Re: Tiger Audio Units and 96kHz
- From: Jeremy Sagan <email@hidden>
- Date: Sat, 29 Oct 2005 12:22:01 -0400
Hello Chris,
Thank you. Yes you are right and I was completely wrong. AU Lab shows
that these plug-ins do work fine.
My problem was that I was not setting the sample rate on the input
scope to the plug-ins and this seemingly only affected the format
converter type plug-ins. I was not expecting AUTimePitch and these
other plug-ins to do an additional sample rate conversion but seeing
as they are 'format converters' I guess that makes sense.
Is there any hard and fast rule as to setting the sample rate on
particular scopes depending on the audio unit type?
Jeremy
On Oct 28, 2005, at 9:11 PM, Chris Rogers wrote:
Jeremy,
We tested these AUs at different sample-rates including 96KHz.
Please try this test with "AU Lab" with your hardware device set to
96KHz.
Chris Rogers
Core Audio
Apple Computer
On Oct 28, 2005, at 6:04 PM, Jeremy Sagan wrote:
Hello,
After further analysis I am leaning toward this problem being
within these audio units. I tried to reproduce this with AudioUnit
hosting and could not BUT audiounit hosting does not seem to be
setting the destination sample rate to 96kHz even though the
default system output device is set to 96kHz. Information appears
in the console and it shows that while the file is 96k the
destination output is still being configured to a sample rate of
44.1kHz.
Also my own independent testing has discovered some interesting
phenomena. First at 96kHz in my code, if I load AUTImePitch it
will work if the quality setting is low or medium. As soon as the
quality is set higher, the plug-in calls my input procedure but
asks for only 366 (or so) samples during each V2Render and the
audio packet buffer size being rendered is 1024 and the
AUTimePitch rate is 1.0. This means that the component is not
asking for enough data so there is no way it could render
properly. The resultant audio is a very slowed down version of the
original and my presumption is that this is a result of a
mathematical overflow type error.
The AUVarispeed does not render properly at high sample rates
regardless of the quality setting which, as far as I can tell, has
no affect on the sound.
AUPitch, which is not a format converter plugin, exhibits a
different problem at high sample rates but may be related. It
introduces static into the audio signal.
I am still open to the problem being in my code (especially since
this code to deal with format converter AU's is new) but the fact
that many other plug-ins render fine at 96k and that the
AUTimePitch renders okay if the quality is low seems to indicate
the problem lies within the Apple AU's.
On Oct 28, 2005, at 3:23 PM, Jeremy Sagan wrote:
Has anyone tried to get the Varispeed unit, the TimePitch unit
and the Pitch Unit to work with a 96kHz sample rate?
I cannot get them to work. The problem with the format converters
may be in my code so I was wondering if anybody has used these
with 96kHz audio files?
Thanks,
Jeremy
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40verizon.net
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:
40apple.com
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