[Rosegarden-devel] audio segments and sequencer resolution

[Richard B. <bo...@bo...>]

Actually while we're on Segments I'm currently implementing audio file support.
My XML sketch of how audio will be supported is something like this:

<composition ...>

    <audio id="0" file="audio/cymbal.wav"/>
    <audio id="1" file="audio/beep.wav"/>
    <audio id="2" file="audio/909-hats.wav"/> 
    <audio id="3" file="audio/909-kick.wav"/>

</composition>

<segment track="0" start="70" audio="0">
    <start marker="125"/>
    <end marker="500"/>
</segment>

The Segment starts at 70 and is of length (500-125).  The sample starts
playing at 125 ticks in.  Integrity of the sample and duration is
confirmed when the XML is loaded and an AudioFileManager object is
created.  Use of ticks for sample length takes us onto my next point..

...sequencer resolution.  Currently it's very low 96ppq (384 pulses per bar).
Like I've said before, pro sequencers are usually about ten times as precise
- Logic is 960 ppq.

Have a look at this note:

http://groups.google.com/groups?q=sequencer+resolution+ppq&hl=en&selm=2416574462.20975%40magic.ca&rnum=3

Theoretically we can increase our resolution with NotationTypes::m_crotchetTime?
Can we still support these higher resolutions?  If so should we do a little
testing now?  Should we also make this value available in XML so that different
sequencer resolutions are supported?

Thoughts?

R