Ok. So I think I've tracked down the root of the problem. The translate ms to notevalues seems to depend on the current transport tempo. For a lot of bpm values, translate will behave as desired. However certain tempo values will cause translate to output a 0. when going from ms to notevalues.
Yes, but if you look at my example patch- the note values ARE bound to the current tempo. I'm just translating a timevalue to ms and then back. Translate will put out a 0. on certain tempo values and not others.
I'm not familiar with the 'n' time value. Can you describe what it is you are trying to translate ms to exactly? The transport output is outputting ticks. Do you want to translate from ticks to something else?
they should really add that to the translate obj. i guess e. g. observing the clip length (start and end marker) is frequently used. now i have to write my own translators just to have a cliplength or position in bbu or ms for example.
notevalues are there for convenience to express common individual notes duration. translate ticks bbu is going to give you bars.beats.units which is probably what you need (you don't have ms coming out the raw ticks outlet of transport).