Question about transport , and stopping toggle while transport is playing

you are currently banging transport and make it report its current status.

wouldnt be turning it on and off be what you wanted?

and note the order; tranport is beeing triggered before 2n

I thought banging the transport was the way to make it show bars, beat, units at it's output
Is there another way ?

Here 's the same is happening , using metro4n @ active 1 directly to transport , and a metro 1n@active 1(red ) same sync problems .
This is all getting pretty confusing

Here I got rid of the toggle
Just using @ active argument , beat and bars are out of sync

I assume the @ active means that the metro is synced to the master clock , and doesn't need a toggle to start , both are set @active 1 , meaning first transport ?
The manual is not clear about any of this

It would be great if you could alter the patch so it syncs after stopping re-starting the toggle

Here both metros set to @active 1 , one is 4n the other 1n
Totally out of sync when transport starts

that there is a transport object doesnt mean that you would require that weird thing to do simple stuff. it somehow seems easier to use the metro output to make you own bars and beats display.

the invisible crosslinks between metro and transports are a mystery, i live in a world of milliseconds and counter objects, that seems easier.

back in the days when transport did not exist we had to build it on our own and then it does what you want. :)

i think when you set it to "resetbarcount 1" it should be enough to resend the time signature and it should fully reset to other objects on restart. but i just didnt get it working in m7 either.

the 1n (your last patch) always comes on the "3", it´s wicked.

This is unlocked misterious global transport.
I would not in a dream try to build any tight sequencing around that

I am not sure wht you guys are trying to say , avoid the transport because it's not tight and use the metro's milliseconds approach ?
That's not a solution at all and merely indicates there is in underlying roblem
For me the metro set to n-values are pretty tight when scheduler overdrive and audio interrupt is on , even when using 32n for rapid hi-hats .
The problem was when stopping and restarting metro's , it loses sync with the main transport .
I wan't to use max for composing and am used to rock solid timing with reaktor ,renoise + architect ( seriously check out loomer's architect , i'ts an amazingmodular midi environment )
If global transport should be avoided and max Millisec. timing is the way to do it I'll probably won't get a subscription ( my demo will run out in a few days )

i know that you are about to check out all objects atm and not build on a concrete project, but transport is one of these objects you usually do not need to make thing work. if can save you a lot of time if you need exactly that - but the more "high level" an object is, the less it contains a general approach useful in many situations.

it is a good all in one solution if you really need to be able to pause and restart a song at any given time position, but everything else seems easier with simple objects.

when i first saw the global transport and it didnt even have buttons for "start" "stop" and "resume" like DAWs usually have, i decided to ignore it.

you can see here how fun it can be already only to discuss all the philosophical aspects of bars, beats, crotchets, PPQ, BPM, milliseconds, industry standards and personal needs, the "correct" music theory and best practice programming https://cycling74.com/forums/tempo-doesnt-respect-time-signature

so it is no wonder that sometimes there are objects not everybody loves or which do not work for you.
like i recently said in a similar thread, if something doesnt work for you, use something different. it doesnt matter if it is a bug or your fault or whatever.

i know that this doesnt answer your original question how to make transport work with metro.

oh yeah and architect is fun, that´s a good piece of work. it is very close to what i do with max, but has the better user interface. unfortunately it is very midi focused.