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

Hey,
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

bugs-in-transport-object

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

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.

bugs in transport object