AU timing in DP and Logic
AU timing in DP and Logic
- Subject: AU timing in DP and Logic
- From: Richard Burnett <email@hidden>
- Date: Fri, 29 Feb 2008 08:46:18 -0800
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:
This email sent to email@hidden