Transport State
Hello,
This is a really basic question. I'm probably overlooking something, but I can't seem to get a response from the state output of transport. I hope I'm not being stupid, but in the help file for transport a toggle is attached to state but doesn't seem to respond whether or not transport is active. Is it not meant to do this? Is there another efficient way for transport to output a bang or a 1 or 0 to show whether it's active?
Thank you
Hi 2000,
in your patch, the [metro] object that is sending the bangs to the [transport] object is linked to the transport itself, because you use @interval 1 ticks. When you start the transport it reports correctly the state (== 1) because [metro] is sending bangs . When you stop the transport, your [metro] object stops as well and your [transport] object is not polling the state anymore. Hence the state output doesn't change.
If you un-link the [metro] from the transport e.g. by using a time unit as interval instead of ticks it works fine:
P.S.: If you use Edit > Copy Compressed you can paste your patch directly into the forum without attaching an extra file.
As Jan said, [transport] outputs the state and other information only when you bang it.
Some related advice:
- it's a bad idea to give your patches the name of a Max object - a thing to absolutely avoid (I see your patch was called Transport).
- for patch excerpts to post on this forum, select the patch objects, then menu Edit -> Copy Compressed. Then paste in your post. That's the fastest way for forum users to see your patch/try it out.
Hello,
Thank you both for the advice. I hope I've copied and pasted this patch correctly.
Sorry, the previous patch was the help file. I was trying to understand the principle. I'm trying to adapt this patch by Source Audio in order to have the state reflected. Could I ask if you have any advice with this?
Yes, I wasn't thinking when naming the patch.
Thank you
here ya go :)
Hello,
Thank you. Sorry for being slow. It works when the clock source is internal, but it is not changing when receiving information from the IAC driver.
Thank you
that patch has a mistake - split 20. 400. (filter false tempo output after a pause) is in wrong position.
if you use midi clock to run tranport, then you also need to use
midi messages to update running state
or send bang each time you tell transport to start or stop (blue part )
Hello,
Amazing.
Thank you very much