Feature Request: @transport argument for [vst~]

May 26, 2013 at 4:01pm

Feature Request: @transport argument for [vst~]

The title says it all.
Max supports multiple named [transport]s running at different speeds, as well as [setclock] and other parallel timing tools.
Being able to lock a vst plugin hosted in [vst~] to a particular transport would be very nice indeed.
Anyone else agree?
Or, is this already available in some way?

Mar 18, 2014 at 1:24am

I was about to request the same thing. After discovering this feature request, I am curious if this has been implemented or is a future possibility.


You must be logged in to reply to this topic.