Transport not needed for Slave Sync?

[ChiLam]

So to reduce the footprint of my sequencer template, built up mainly from the existing StepNote objects, I was looking at condensing things down a bit.

Up till now I had a Transport object in each and every Container/tab which contained a Step object - however I thought it might be possible to delete these and just use one at Project level. Infact I removed ALL of the Transport objects and to my suprise the template still ran! So I guess it was completely unecessary to include them in the first place so long as your only going to slave the clock externally?

[ndivuyo]

yea, unless you want to have transport controls on your layout

[Macciza]

Yes
Maybe do a bit more research into MIDI Clocks so you get the full gist of them

If you are Slaved to external clocks you naturally have no local control - except for local remote control of the app that is sending clock . . .

If you are running clocks locally, they are 'global' within the app i.e. they are accessible everywhere regardless of where they are controlled from.
If you want to be able to control the same clock from multiple places then maybe look into Alias's . . .

Cheers