Forums > MaxMSP

bugs in transport object

September 10, 2012 | 10:56 am

quite surprised I found out that there are bugs in the transport object:

1. if a position message in ticks or bbu is sent AFTER a timesig message, transport does not jump to the correct position – (… in the forum I found reports about this older than two years)
2. maybe it’s me but I can’t get the resetbarcount function working

here’s a patch to demonstrate:

– Pasted Max Patch, click to expand. –


September 10, 2012 | 7:05 pm

Hi Alex,

Yeah, something’s not working right.

We’ll have a look at it.

if you need a workaround, and are willing to consider a slightly off the wall suggestion, perhaps make one huge bar of 1000000 4 or something and do the bar management yourself



September 11, 2012 | 10:17 am

Hey Andrew,

thanks for the workaround. In the meantime I found another one. If the timesig message is sent at bbu 1 1 0 it doesn’t have the negative effect regarding the time position on reset.

Greetings Alex

Viewing 3 posts - 1 through 3 (of 3 total)