Re: [Canorus-devel] send() parameters

[Matevž J. <mat...@gm...>]

Hi Georg.

Yes, only "time" would be better. You can find the following terms in 
Canorus code:
- timeStart - absolute start of music event
- timeLength - length of music event
- timeEnd - absolute end of the music event calculated from timeStart + 
timeLength
- playableLength - musical length of notes, rests (quarter, whole, half)

Any timeLength can be translated to a series of playableLengths and the 
other way around as well. TimeLength 256 is defined as a playableLength 
quarter note. TimeLength is not affected by the Tempo.


Regards.
-Matevž

Georg Rudolph pravi:
> Matevž Jekovec schrieb:
>   
>> Hi Georg.
>>
>> I still don't understand the parameters in CAMidiDevice::send()...
>>
>> I thought you should put a timeOffset as the second parameter - I 
>> thought the second parameter is the MIDI offset in front of the sysex 
>> message. So you should put the timeOffset instead of the timeLength. 
>> TimeLength should probably mean NOTE-ON + NOTE-OFF combination in my 
>> opinion.
>>
>>   
>>     
> Hi Matevž,
>
> the differentiation (offset) is done in CAMidiExport::send(). 
> CARtMidiDevice::send() doesn't use this time parameter at all. Like in
> sendMetaEvent() I preferred to do these midi qirks in CAMidiExport,
> because it's only needed there.
>
> timeLength is a name I got from
> CAPlayableLength::playableLengthToTimeLength(), and it means a time
> scaled like note values. Maybe time would be the right name, like it is
> all around in canorus.
>
> Regards,
> Georg
>
>
>