AudioUnit's outDeltaSampleOffsetToNextBeat.
AudioUnit's outDeltaSampleOffsetToNextBeat.
- Subject: AudioUnit's outDeltaSampleOffsetToNextBeat.
- From: "David Viens" <email@hidden>
- Date: Mon, 02 Feb 2004 17:43:30 -0500
Hello
We are implementing AUDispatchGetMusicalTimeLocation in our host,
And searching through the archives (and headers)
(moslty au_properties.html) Gave me most of what i needed.
But really i fail to see the point with: outDeltaSampleOffsetToNextBeat!
something like outDeltaSampleOffsetToNext__Bar__ would have
been usefull to plugins authors imho.
outDeltaSampleOffsetToNextBeat is defined as
"Will contain the number of samples until the next whole beat from the start sample
of the current rendering buffer."
to reuse the au_properties.html example:
Score Time Sig: |3/4 | |4/8 |6/8 |5/8 |3/4 |4/4 |
Down Beats: 1 4 7 9 12 14.5 17.5 21.5
if the host sequencer is currently at outCurrentBeat=14.1
why would the plugin care to receive a sampleOffset to beat at ppq=15
(that doesnt really exist) which is 0.5 ppq after the start of the 3/4 bar???
Unless "next whole beat" also means start of the next bar, whichever comes first?
Many open source VST plugins ive looked at (like Marc's excellent DFX line)
calculates something like samplesUntilNextBar which is more usefull
in order to say, to reset an LFO at each mesure start. Or recalulate params.
This also means that given all the other fields, a plugin can recalculate
either outDeltaSampleOffsetToNextBeat or say a samplesUntilNextBar by itmself too.
So im very puzzled.
Cheers.
-------------------------------------------
David Viens, Plogue Art et Technologie Inc.
Montreal.
http://www.plogue.com
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.