max 5 tempo object bug?
dear friends, it seems that max 5 tempo obj doesn't work like the 4.6 one. if you open the tempo.maxhelp and use a float value for tempo, the max window say: tempo doesn't understand "float".
why? if you work in the same way in the older version, everything is fine...
anyone noticed the same?
thank you
emj
Thanks - I can reproduce and we'll have a look at it for the next incremental release.
-A
I can reproduce also.
It's harder for people to remix stuff you produce (IDM or any type of EDM or hip-hop, for that matter) if you put its tempo inbetween the cracks, i.e. 127.666 instead of just 127. Makes it harder to beatmatch. I don't really know why I'm typing this, but it's barely related.
On 14 mai 08, at 19:15, Andrew Pask wrote:
> Thanks - I can reproduce and we'll have a look at it for the next
> incremental release.
It's fixed for the next incremental. Thanks.
ej
Quote: Eli wrote on Wed, 14 May 2008 19:55
----------------------------------------------------
> I can reproduce also.
> It's harder for people to remix stuff you produce (IDM or any type of EDM or hip-hop, for that matter) if you put its tempo inbetween the cracks, i.e. 127.666 instead of just 127. Makes it harder to beatmatch. I don't really know why I'm typing this, but it's barely related.
----------------------------------------------------
I'm looking forward to "IDM" getting into phasing... play 120 against 120-2/3 and a 4/4 pattern will take six hours to resync. That's what I call a rave.-