dalinnen

with the current version of max on my ppc powerbook, the 'hook' message is somewhat broken with 'seq'. the float value that is suppose to follow the 'hook' message is being truncated to an integer by seq.

to replicate: open the seq helpfile and add a float number box going to a 'prepend hook' that goes into the seq. start at 1.0 and drag the number box between 1 and almost 2; the note spacing will not change at all (seq is only seeing 1's). once you hit 2 however, the note spacing will immediately double (and do so again and again for every 2.x value you drag through). when you send any number below 1 (e.g., 0.9), this value will truncate to 0, and all notes are now positioned simultaneously at the first instance of the sequence.

the 'hook' message still works perfectly in max 4.5.7. hopefully someone can confirm that this is broken on max 4.6.2. i miss this feature.

with the current version of max on my ppc powerbook, the 'hook' message is somewhat broken with 'seq'.  the float value that is suppose to follow the 'hook' message is being truncated to an integer by seq.

to replicate: open the seq helpfile and add a float number box going to a 'prepend hook' that goes into the seq.  start at 1.0 and drag the number box between 1 and almost 2; the note spacing will not change at all (seq is only seeing 1's).  once you hit 2 however, the note spacing will immediately double (and do so again and again for every 2.x value you drag through).  when you send any number below 1 (e.g., 0.9), this value will truncate to 0, and all notes are now positioned simultaneously at the first instance of the sequence.

the 'hook' message still works perfectly in max 4.5.7.  hopefully someone can confirm that this is broken on max 4.6.2.  i miss this feature.

bug-in-seq-max-4-6-2

I never used seq. I press record, then gradually increase the flonum that leads via prepend hook to seq while playing notes on my keyboard. Then I write the file to disk and import it in logic. I see all notes I played on the same position, the first bar.

Quote: dave linnenbank wrote on Thu, 12 April 2007 15:19

----------------------------------------------------

> with the current version of max on my ppc powerbook, the 'hook' message is somewhat broken with 'seq'. the float value that is suppose to follow the 'hook' message is being truncated to an integer by seq.

> to replicate: open the seq helpfile and add a float number box going to a 'prepend hook' that goes into the seq. start at 1.0 and drag the number box between 1 and almost 2; the note spacing will not change at all (seq is only seeing 1's). once you hit 2 however, the note spacing will immediately double (and do so again and again for every 2.x value you drag through). when you send any number below 1 (e.g., 0.9), this value will truncate to 0, and all notes are now positioned simultaneously at the first instance of the sequence.

> the 'hook' message still works perfectly in max 4.5.7. hopefully someone can confirm that this is broken on max 4.6.2. i miss this feature.

Quote: dave linnenbank wrote on Thu, 12 April 2007 15:19
----------------------------------------------------
> hello, all.
>
> with the current version of max on my ppc powerbook, the 'hook' message is somewhat broken with 'seq'.  the float value that is suppose to follow the 'hook' message is being truncated to an integer by seq.
>
> to replicate: open the seq helpfile and add a float number box going to a 'prepend hook' that goes into the seq.  start at 1.0 and drag the number box between 1 and almost 2; the note spacing will not change at all (seq is only seeing 1's).  once you hit 2 however, the note spacing will immediately double (and do so again and again for every 2.x value you drag through).  when you send any number below 1 (e.g., 0.9), this value will truncate to 0, and all notes are now positioned simultaneously at the first instance of the sequence.
>
> the 'hook' message still works perfectly in max 4.5.7.  hopefully someone can confirm that this is broken on max 4.6.2.  i miss this feature.
>
> thanks much.
>
> --dave linnenbank
----------------------------------------------------


i'm sorry, mattijs; i should have been more clear on that point.

for replicating, once you open the seq helpfile, click the bang button to start the preloaded midi file at regular speed. this makes life easier as you can hear the original tempo/speed of the sequence before using the 'hook' messages. with that in mind, try the original replication instructions, included below.

with the current situation sending any 'hook x' message where x is less than one will result in the situation you describe with all notes in the same location. this should be moving the notes closer together by the floating point factor you enter (as it did in previous versions). as it stands now, the float is truncated and sending 0.9 means sending 0 means all the notes at at the same position.

also, please note what version of max you are using.

for replicating, once you open the seq helpfile, click the bang button to start the preloaded midi file at regular speed.  this makes life easier as you can hear the original tempo/speed of the sequence before using the 'hook' messages.  with that in mind, try the original replication instructions, included below.

with the current situation sending any 'hook x' message where x is less than one will result in the situation you describe with all notes in the same location.  this should be moving the notes closer together by the floating point factor you enter (as it did in previous versions).  as it stands now, the float is truncated and sending 0.9 means sending 0 means all the notes at at the same position.

> to replicate: open the seq helpfile and add a float number box going to a 'prepend hook' that goes into the seq. start at 1.0 and drag the number box between 1 and almost 2; the note spacing will not change at all (seq is only seeing 1's). once you hit 2 however, the note spacing will immediately double (and do so again and again for every 2.x value you drag through). when you send any number below 1 (e.g., 0.9), this value will truncate to 0, and all notes are now positioned simultaneously at the first instance of the sequence.


Ok. Confirmed in max 4.6.2, mac os 10.4.8.

- increase hook from 1. to 1.99: nothing changes

Quote: dave linnenbank wrote on Thu, 12 April 2007 15:52

> i'm sorry, mattijs; i should have been more clear on that point.

> for replicating, once you open the seq helpfile, click the bang button to start the preloaded midi file at regular speed. this makes life easier as you can hear the original tempo/speed of the sequence before using the 'hook' messages. with that in mind, try the original replication instructions, included below.

> with the current situation sending any 'hook x' message where x is less than one will result in the situation you describe with all notes in the same location. this should be moving the notes closer together by the floating point factor you enter (as it did in previous versions). as it stands now, the float is truncated and sending 0.9 means sending 0 means all the notes at at the same position.

> also, please note what version of max you are using.

> > to replicate: open the seq helpfile and add a float number box going to a 'prepend hook' that goes into the seq. start at 1.0 and drag the number box between 1 and almost 2; the note spacing will not change at all (seq is only seeing 1's). once you hit 2 however, the note spacing will immediately double (and do so again and again for every 2.x value you drag through). when you send any number below 1 (e.g., 0.9), this value will truncate to 0, and all notes are now positioned simultaneously at the first instance of the sequence.

It's even worse. try this sequentially: 
- increase hook from 1. to 1.99: nothing changes
- increase to 2.: plays with 2.
- go back to 1.: still plays 2.
- go to 0.99: plays all at once
- go to 1.: still plays all at once
- go to 2.: still plays all at once

Quote: dave linnenbank wrote on Thu, 12 April 2007 15:52
----------------------------------------------------
> i'm sorry, mattijs; i should have been more clear on that point.
>
> for replicating, once you open the seq helpfile, click the bang button to start the preloaded midi file at regular speed.  this makes life easier as you can hear the original tempo/speed of the sequence before using the 'hook' messages.  with that in mind, try the original replication instructions, included below.
>
> with the current situation sending any 'hook x' message where x is less than one will result in the situation you describe with all notes in the same location.  this should be moving the notes closer together by the floating point factor you enter (as it did in previous versions).  as it stands now, the float is truncated and sending 0.9 means sending 0 means all the notes at at the same position.
>
> also, please note what version of max you are using.
>
> --dave linnenbank
>
> > to replicate: open the seq helpfile and add a float number box going to a 'prepend hook' that goes into the seq. start at 1.0 and drag the number box between 1 and almost 2; the note spacing will not change at all (seq is only seeing 1's). once you hit 2 however, the note spacing will immediately double (and do so again and again for every 2.x value you drag through). when you send any number below 1 (e.g., 0.9), this value will truncate to 0, and all notes are now positioned simultaneously at the first instance of the sequence.
----------------------------------------------------


in terms of your test, this is the expected functionality. the 'hook' message destructively moves notes to new locations so 'hook 1' always means keep it exactly where it already is. (this is why you never want continuous output from your number box with the 'hook' message as your scaling quickly builds up.)

the only real problem is that the floats are being truncated and now - amongst other things - it is impossible to move the notes closer together without having them completely simultaneous.

it is nice to wire up a hook-based patch that makes a value of 1 always restore the original note position, 2 always double the distances, and 0.5 always make them twice as fast. i was going to ask my students to build this as part of a homework for next week when i discovered this bug. luckily while my computer is on 4.6.2, the lab is still 4.5.7 so the game is still on...

Quote: Mattijs wrote on Thu, 12 April 2007 10:31

> Ok. Confirmed in max 4.6.2, mac os 10.4.8.

> It's even worse. try this sequentially: 

> - increase hook from 1. to 1.99: nothing changes

in terms of your test, this is the expected functionality.  the 'hook' message destructively moves notes to new locations so 'hook 1' always means keep it exactly where it already is.  (this is why you never want continuous output from your number box with the 'hook' message as your scaling quickly builds up.)

it is nice to wire up a hook-based patch that makes a value of 1 always restore the original note position, 2 always double the distances, and 0.5 always make them twice as fast.  i was going to ask my students to build this as part of a homework for next week when i discovered this bug.  luckily while my computer is on 4.6.2, the lab is still 4.5.7 so the game is still on...

Quote: Mattijs wrote on Thu, 12 April 2007 10:31
----------------------------------------------------
> Ok. Confirmed in max 4.6.2, mac os 10.4.8.
>
> It's even worse. try this sequentially: 
> - increase hook from 1. to 1.99: nothing changes
> - increase to 2.: plays with 2.
> - go back to 1.: still plays 2.
> - go to 0.99: plays all at once
> - go to 1.: still plays all at once
> - go to 2.: still plays all at once
>
> Seems very broken..
>
> Mattijs


Quote: dave linnenbank wrote on Thu, 12 April 2007 16:53

> in terms of your test, this is the expected functionality. the 'hook' message destructively moves notes to new locations so 'hook 1' always means keep it exactly where it already is. (this is why you never want continuous output from your number box with the 'hook' message as your scaling quickly builds up.)

Ah, I understand, as I said, no experience with seq ;)

> the only real problem is that the floats are being truncated and now - amongst other things - it is impossible to move the notes closer together without having them completely simultaneous.

Quote: dave linnenbank wrote on Thu, 12 April 2007 16:53
----------------------------------------------------
> thanks for the confirmation.
>
> in terms of your test, this is the expected functionality.  the 'hook' message destructively moves notes to new locations so 'hook 1' always means keep it exactly where it already is.  (this is why you never want continuous output from your number box with the 'hook' message as your scaling quickly builds up.)

>
> the only real problem is that the floats are being truncated and now - amongst other things - it is impossible to move the notes closer together without having them completely simultaneous.

I can reproduce this weirdness. I shall log it and we'll have a look at it.

i assume it is know by those who might fix this, but the hook message bug (to the seq object) previously mentioned here is still present in max 4.6.3. that being said, thanks for taking other bugs out of existence.

i assume it is know by those who might fix this, but the hook message bug (to the seq object) previously mentioned here is still present in max 4.6.3.  that being said, thanks for taking other bugs out of existence.

as was reported in max 4.6.x, the 'hook [float]' message to seq is still broken as of 5.0.5. seq interprets the float value given with hook as an integer, effectively making your only scaling options 0% (all notes at once), 100%, 200%, etc.

would be great to see this fixed. in case it helps, max 4.5.7 worked perfectly.

as was reported in max 4.6.x, the 'hook [float]' message to seq is still broken as of 5.0.5.  seq interprets the float value given with hook as an integer, effectively making your only scaling options 0% (all notes at once), 100%, 200%, etc.

would be great to see this fixed.  in case it helps, max 4.5.7 worked perfectly.

On 10 oct. 08, at 06:13, dave linnenbank wrote:

> as was reported in max 4.6.x, the 'hook [float]' message to seq is 

> still broken as of 5.0.5. seq interprets the float value given with 

> hook as an integer, effectively making your only scaling options 0% 

> would be great to see this fixed. in case it helps, max 4.5.7 

Thanks. This is fixed for the next incremental.

> as was reported in max 4.6.x, the 'hook [float]' message to seq is  
> still broken as of 5.0.5.  seq interprets the float value given with  
> hook as an integer, effectively making your only scaling options 0%  
> (all notes at once), 100%, 200%, etc.
>
> would be great to see this fixed.  in case it helps, max 4.5.7  
> worked perfectly.

bug in seq; max 4.6.2