Sergio Granada-Moreno

This might be very simple but I can't get groove~ to work with named transports, as it is sugested in groove~ reference:

@transport [symbol] Sets the name of a transport object with which to associate.

In this patch groove~ is still following global tempo despite being named after a particular transport object. I need to have a couple of groove~ each one associated to a particular transport...

This might be very simple but I can't get groove~ to work with named transports, as it is sugested in groove~ reference:
@transport [symbol] Sets the name of a transport object with which to associate. 

lock-groove-to-named-transports-help-needed

It looks like the @transport attribute of groove~ has never properly worked in Max 7. We will take a closer look.

@Ben, as a seemingly related feature request, it would be bitchin' if the phasor~ object had a 'transport' attribute and could lock to a named transport.

The phasor~ feature request is long standing, and I agree, a great one!

This came up as part of a larger project in which I am working on for Uni. The idea is to work with groove~ ZTX technology as in a position-based enveloping sampler, as much as possible, due to groove~ own functionality and issues with its sync outlet, etc.

I've found that using groove~ in @lock mode allows to 'hack' the transport object to which groove~ is associated, as if the [transport] object were the wavetable oscillator. Please see attachment.

This is actually the best way I've found to make the playback position jump and move backwards when using groove~, however, if groove~ can not be associated with a named transport this have no use inside Max For Live.

This came up as part of a larger project in which I am working on for Uni. The idea is to work with groove~ ZTX technology as in a position-based enveloping sampler, as much as possible, due to groove~ own functionality and issues with its sync outlet, etc. 

EDIT: max file seems to be too large to be attached or copy compressed… :I

Here is a link to download from sendspace (less than 5 secs!)

EDIT: max file seems to be too large to be attached or copy compressed… :I
Here is a link to download from sendspace (less than 5 secs!)

@Ben Bracken, how is your 'closer look' going?

Do you think this could be fixed in 7.0.6 release version or something? Or would you rather just take out the 'named transport' stuff from groove~ reference?

Any comments would be highly appreciated !

@Ben Bracken, how is your 'closer look' going? 

 Do you think this could be fixed in 7.0.6 release version or something? Or would you rather just take out the 'named transport' stuff from groove~ reference?

Any comments would be highly appreciated !


@Sergio Granada-Moreno this apparently hasn't been working since the beginning, so I can't say if it can or will be fixed.

EDIT It would be great to know more about this. Is it a limitation associated with ZTX technology?

@Ben
EDIT It would be great to know more about this. Is it a limitation associated with ZTX technology?


@lock groove~ to named transports: help needed!