Hi,
I did lights and music for a theatre-performance last week. Stage lighting and sample playback should be tightly syncronised so I made a rather simple lighting desk in pd. (using an Enttec DMX USB Pro) The core of a lighting desk is the ability to fade the brightness of several (hundreds of) lamps over given times. I could not find a line object for lists of integers within a short research so I decided to make one. I used dynamic patching because I didn't want to connect up to 512 objects by myself.
Here is what I ended up with (helpfile included):

list-line-i.zip

It worked reliable in the rehearsals and shows, but I'd like to get some opinions: Is this the way to solve this kind of tasks?
It feels like a hack somehow. The dynamically created subpatch is hard to maintain. For example once I realized it needs behavior like max's | pak | or every line-object should only output integers I got a sudden headache...
I'd just like to know if this kind of programming is the way to go in puredata or are there some smarter techniques I don't know?

best regards

(by the way if someone likes to get the whole DMX-lighting patch let me know.)

Hi
I would do as attached. You'll find a very simple lighting desk.

On each tick of the main clock :

• each [example-dmx-dimmer] sends a message containing its value and its ID to a table, where "value" is stored at the index "ID"
• then the table is dumped

The value of each dimmer goes through a [ *], where it's multiplied by the master, before being stored into the table.
This way on each tick, you get all your values modulated by your master.

Edit : reuploaded the right files

My vanilla can't create [list-drip] (which can be replaced by zexy's [drip] I guess) and [list-rot 1]. I guess the latter does some kind of rotation? Don't really know though. Anyway, can't make it work without those. Can you provide them?
Thanks

@alexandros here are complete list abstractions from Pd extended.list-abs.zip