Re: AU timing in DP and Logic
Re: AU timing in DP and Logic
- Subject: Re: AU timing in DP and Logic
- From: Richard Burnett <email@hidden>
- Date: Sun, 2 Mar 2008 13:43:36 -0500
Thanks for the help Bill. I have built the AU with the included files
and set the preprocessor macro to define AU_DEBUG_DISPATCHER. In
looking through the code I can't seem to figure out where the output
gets written once the host starts running.
Again, thanks for your help. This seems to be the path I want to take.
Rick
On Feb 29, 2008, at 4:00 PM, William Stewart wrote:
If you have a look in the SDK you'll notice there's a bunch of code
if'def'd out for AUDebugDispatcher - the SampleEffect unit is a good
place to start. You have to add AUDebugDispatcher.h and .cpp to the
project (and you can add code to this as well if you need to).
You'll need to define AU_DEBUG_DISPATCHER in the project
(Prepocessor Macros) and if you do a search for this you'll see how
its all put together
If you enable this, then we'll log all of the API calls into the AU
with their args - you'd have to add code I think for the MIDI calls,
but that should be pretty straight forward.
Bill
On Feb 29, 2008, at 8:46 AM, Richard Burnett wrote:
Hello All,
I have spent a few days heavily testing the programs Digital
Performer 5.13 and Logic Pro 8. Mainly I looked at the summing
algorithm (works the same), the panning levels (do not work the
same) and plugins. I have noticed two very interesting situations
and wanted to ask about them here:
(1) The output of time dependent (compressors, filters) plugins do
not match between both programs. If I turn off the plugins, the
summation out of Logic or DP is exactly the same (used null
testing). It always appears that Logic is a tad hotter (and by tad
I mean pretty small difference). I cannot figure out why they
would be different unless some time based information is getting
passed differently.
(2) VI plugins in both applications do not sound out exactly when
the midi note does in each program. In DP the notes are always
late AND they are not consistent on how late they are. In Logic,
the first note sounds early to the point it is coming in at a hot
spot causing a pop (non zero) and then the rest are late. The note
is at the same spot where the recording is starting, still, I don't
think it should be doing this. Is this a timing issue of when
CoreMIDI gets data and then when it gets to the plugin?
Has anyone had experience looking at these two issues? And if not,
does anyone know of an AU plugin that actually just shows you what
the host is telling it? Like, how much to process, what the time
is, tempo, etc? I could probably code something up in Max/MSP but
I wanted to make sure someone hadn't already gone down this path.
Thanks!
Rick
Asylum Studio Productions
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
@apple.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