Dante

Is it possible to create a list message for line object such as: start at -2.5 and go to 2.0 in 5secs and then go to 20 in 5secs and then to 50 in 2secs.

I thought I saw something like this in the tutorials at one point but cannot find it again.

If this is not possible what is the best to to create something like this.

Is it possible to create a list message for line object such as: start at -2.5 and go to 2.0 in 5secs and then go to 20 in 5secs and then to 50 in 2secs.  

I thought I saw something like this in the tutorials at one point but cannot find it again. 

If this is not possible what is the best to to create something like this.


help-with-basic-long-list-line-object

I haven't tested it a lot, but I think its working.

You can send same messages like the audio rate [line~] (like "0, 1 500 0 500"

I haven't tested it a lot, but I think its working.
You can send same messages like the audio rate [line~]  (like "0, 1 500 0 500" 

Thanks for your help Nikolas! I'll have keep practicing those Zl objects

Thanks for your help Nikolas!  I'll have keep practicing those Zl objects


When managing and processing list, the [zl] family is necessary!

When managing and processing list, the [zl] family is necessary!
Keep up the good practice!


[I thought I replied here, but it doesn't seem to have worked.]

Just having some problems with longer lists and shorter times...

list and line.maxpat

This is great, thanks.
Just having some problems with longer lists and shorter times...


you need to set lowest line grain for faster speeds,

you need to set lowest line grain for faster speeds,
minimum is 1 ms
line 0. 1


Back a year later at this problem... really just wish [line] would accept lists the way [line~] does :/

The solution I shared earlier works, but continues to send the last value over and over. Maybe this isn't a problem but I thought I should install a gate to block the loop from infinitely repeating.

So when you first send the list there is a trigger that opens the gate, and when the list is down to its last element the gate is closed again. This solution seems to work totally fine in isolation, but when I plug it into a larger patch it produces stack overflow warnings.

Why don't I get these warnings when it's working by itself?

Back a year later at this problem... really just wish [line] would accept lists the way [line~] does :/

The solution I shared earlier works, but continues to send the last value over and over. Maybe this isn't a problem but I thought I should install a gate to block the loop from infinitely repeating.

yep it is confusing that it does not work the same way.

i´d say i do the first 40%and you do the rest. :)

start with a [zl reg] and a [counter], then copy what you see below.

grafik.png


yep it is confusing that it does not work the same way.

i´d say i do the first 40%and you do the rest. :)

start with a [zl reg] and a [counter], then copy what you see below.



max v2;
#N vpatcher 513 175 1473 722;
#P hidden newex 396 465 108 196617 bgcolor 150 250 50;
#P newex 783 246 99 196617 110.defarg 25.;
#P newex 783 78 99 196617 f $2;
#B color 15;
#P newex 783 43 99 196617 loadbang;
#N comlet ramp;
#P outlet 335 465 15 0;
#N comlet list in [line~] format & other messages to [line];
#P inlet 29 43 15 0;
#P newex 655 151 99 196617 expr ($i1*2)-1;
#P newex 655 335 47 196617 + 3;
#P newex 709 335 47 196617 + 2;
#P newex 655 301 226 196617 t i i 2 i 1;
#P newex 451 212 130 196617 t l l;
#P newex 571 301 56 196617 t l 0;
#P newex 655 411 56 196617 t 0 b i;
#P newex 571 429 56 196617 zl nth;
#N vpatcher 30 70 430 370;
#P newex 183 78 50 196617 t 1;
#P outlet 183 155 15 0;
#P outlet 124 155 15 0;
#P inlet 124 62 15 0;
#P connect 0 0 1 0;
#P connect 0 0 3 0;
#P connect 3 0 2 0;
#P pop;
#P newobj 29 115 61 196617 p td1;
#P newex 571 465 202 196617 zl group 1;
#P newex 233 246 84 196617 prepend clock;
#P newex 131 246 84 196617 prepend set;
#P newex 388 133 116 196617 counter 0 0 999;
#P newex 451 246 70 196617 zl slice 2;
#P newex 335 264 63 196617 line $1 20;
#P newex 29 194 318 196617 route list set clock;
#P connect 16 0 7 0;
#P connect 7 0 0 0;
#P connect 0 1 4 0;
#P connect 0 2 5 0;
#P connect 4 0 1 0;
#P connect 5 0 1 0;
#P connect 0 3 1 0;
#P connect 2 0 1 0;
#P connect 6 0 1 0;
#P lcolor 16;
#P connect 1 0 17 0;
#P connect 20 0 1 2;
#P connect 1 1 3 0;
#P lcolor 13;
#P connect 7 1 3 2;
#P connect 0 0 11 0;
#P connect 11 0 2 0;
#P connect 11 1 10 0;
#P connect 10 0 8 0;
#P connect 9 1 8 0;
#P connect 8 0 6 0;
#P connect 10 1 8 1;
#P connect 9 2 8 1;
#P connect 9 0 8 1;
#P connect 3 0 15 0;
#P connect 15 0 12 0;
#P connect 12 0 14 0;
#P connect 13 0 9 0;
#P connect 14 0 9 0;
#P connect 12 3 9 0;
#P connect 12 1 13 0;
#P connect 12 2 6 1;
#P connect 12 4 6 1;
#P connect 18 0 19 0;
#P connect 19 0 20 0;
#P pop;



This can be done more simple, also without sending the slider to zero

at the end which I guess is a mistake in your posted patch.

and here version with list pairs, destination - ramptime

actually should work without zlclear but it is there for safety as

it seems you get some execution timing problems in larger patches.

@ exeterdown
This can be done more simple, also without sending the slider to zero
at the end which I guess is a mistake in your posted patch.

and here version with list pairs, destination - ramptime


actually should work without zlclear but it is there for safety as
it seems you get some execution timing problems in larger patches.


help with basic long list, line object