True-durations ain't true

[rc0]

Hello,

I tried the following tree with tempo 60 on a voice:

(? (((4 4) ((1 (1 1 1 1 -996)) -3))))

and if i use the true-durations object, I suppose to get something like:

(1 1 1 1 -996 -3000)

but instead true-durations gives me nil as a result.
why is this happening?

best,
rc

[haddad]

Dear rc,

Yes same problem as your last post.
true-duration uses Objfromobjs method transforming a voice into a chord-seq. In your 1 millisecond example, (can you hear 1 millisecond by the way?), the chord-seq reduces your rhythm to one event because it cannot display 1 ms event due to noteon/noteoff (even midi cannot play this). So you get to have a nil. and if you quantify the rhythm you will get an empty voice.

The problem here is also limitation. Even machines have limits

Best
K

[rc0]

Hi K,

I see.
I understand that machines have limits. What I don’t get it is the inconsistency of this object. In the case of this tree:
(? (((4 4) ((1 (-220 1 1 1 1 -220)) -3))))
the object gives durations of 2 ms.

• why it can compute 2 ms and not 1 ms even if both are inaudible and unplayable by midi?
• why it omits the last rest of the tree (-3)?
  

in the beginning i thought that the object calculated true durations from the inlets (onsets & durs) since chord-seq works fine with 1ms and it even return it back from its outlet.

• is there a way to calculate the real true durations of a chord-seq and voice?

best,
rc

[haddad]

Can you send the patch above please? that way it is easier for me to explain
best
K

[rc0]

Dear K,

Sorry for the late reply. Here’s the patch.

true-durations_limits.omp (6.9 KB)

best
rc

[haddad]

Dear rc,

Here is some comments:

and the patch:
true-durations_limits1.omp (14.1 KB)

Best
K