automatically stopping the timeline object

Apr 17, 2008 at 5:42pm

automatically stopping the timeline object

I know timeline is practically not used anymore (buggy), but I was wondering if anyone knows why sending a stop message triggered from a track event doesn’t work. I sent a stop message into tiOut 1 (located in the track patch), and printed it when it emerges from the timeline outlet so I know it’s there. Clicking on the stop message in the same patcher as the timeline works, but when the stop message comes from a track patch, it doesn’t stop???

Any ideas?

Thanks!

#36979
Apr 17, 2008 at 6:09pm

Your message subject should be:
Automatically stop using the timeline object.
It is officially dead in Max 5.
Trying to use it is a waste of time.
If you think there is a bug, e-mail support@cycling74.
J-F.

> I know timeline is practically not used anymore (buggy), but I was wondering
> if anyone knows why sending a stop message triggered from a track event
> doesn’t work. I sent a stop message into tiOut 1 (located in the track patch),
> and printed it when it emerges from the timeline outlet so I know it’s there.
> Clicking on the stop message in the same patcher as the timeline works, but
> when the stop message comes from a track patch, it doesn’t stop???
>
> Any ideas?
>
> Thanks!

#127293
Apr 17, 2008 at 7:50pm

#127294
Apr 17, 2008 at 8:45pm

On 2008 Apr 17, at 2:50 PM, Gary Lee Nelson wrote:
> Remind me…is there something Max 5 to replace Timeline?

Yes.

best,
Tim
____________________________________
Tap.Tools – Objects for Max, MSP, and Jitter

http://electrotap.com/taptoolsmax/

#127295
Apr 24, 2008 at 9:18am

Timothy Place schrieb:
> On 2008 Apr 17, at 2:50 PM, Gary Lee Nelson wrote:
>> Remind me…is there something Max 5 to replace Timeline?
>
> Yes.

Timothy Place schrieb:
> On 2008 Apr 23, at 2:40 AM, Alessandro Fogar wrote:
>> I was thinking that a new gui object dealing with time was on the
>> way, probably it’s not.
>
> Hi — This is correct.

I think the second response is more correct than the first one. Dealing
with time in the new way is great, the idea of a timepoint is pretty
brilliant, but it is not a timeline… (its missing the line part…)

Also it would be essential to be able to have changing time signatures.
100% of the composed pieces I have to deal with, have signature changes.
This is also true for classical music of ancient times. Even the better
techno tracks start to rock if they change the signature…
That means, as nice as the transport is, I can’t use it in its full
potential…
A timeline would be something where you can define these changes beside
timepoints. It might be enough to let a timepoint change the signature,
which doesn’t seem possible at the moment. (please correct me if I’m
wrong…)

Stefan

Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com

#127296

You must be logged in to reply to this topic.