@cfry To get around each command needing the same format the easiest is just to make them all the same, have a null argument like bang.

Now we can just skip the commas and have as many commands per line as you want. If you want to run the command "stop" you just make the message "stop bang" and it sends a bang to [r stop]. Would probably want to add a [list prepend $1] between the [list split] and the message and make the message [; $1$2 $3( so you can pass the parent patch's $0 and prepend it to the symbol but that might not be needed for your use?

If you want commands with more than one argument things get more difficult since you don't want to always have to type in all those null characters or symbols, but it is not that difficult to create a simple editor which does it for you, especially now that we got [list box), I have one somewhere from when I made a tracker like thing years ago, I will see if I can find it later if you want to check it out.

If you really want commands with an arbitrary number of arguments and no nulls, use commas and exploit the right outlet of [text get]. This does complicate things regarding line number vs message number but making that [sel 1] into a [sel 0 1] and using the 0 outlet to bang a second counter for the line number might be enough?

@cfry I was thinking you were using [list split] in place of [unpack] to deal with hex being made up of both floats like 11 and symbols like a1. I can't quite figure out what you are doing with the [list split],. I suspect you just need to develop a more complex counter and maybe tweak how your data is stored and you will be able to make things cleaner. Providing some more information might help in offering alternatives, the format of your data and how you need to access it, perhaps a simple mockup of your patch.

@cfry Dealing with hex is almost always irritating in pd, I generally try and make the hex UI only and keep it as floats under the hood, but that is not always practical. The comma behavior is fairly useful, just need to format your data to exploit it and it makes sense when you think about it since if it did not work that way the object the [text get] is connected to would see a line like 1, 2, 3, 4; as four separate messages and not the single message 1, 2, 3, 4, it would be the same as [1, 2, 3, 4( into a [list] which generally will not give the desired result . That one caused me some grief at first until I learned to use it to my advantage.

@cfry Don't think you will find an external or abstraction which will be easier/better for this than [text] unless someone made exactly what you were looking for and even then it will only be easier until you decide to change things and start banging your head against the limitations of the external or abstraction. This is a pretty simple thing to throw together using [text] and [text get] or [text sequence] depending on your needs, a simple looping [text get] sequencer is not complex and easy to expand to a full tracker like interface even.

[text sequence] is even simpler but has some limitations, it is great when your needs align with it but almost everytime I use it my needs grow beyond its limitations and I switch to [text get]. [text get] also tends to result in neater, easier to read patches since you don't have all those messages going to one inlet.

Edit: Must not have been quite awake when I patched that moses in, bet I thought I was being clever.

@atux This should work for parsing the file, but you will need to add the stuff for resetting the counters/moses/max and before running it you will want to zero the arrays. Not 100% certain I got the order on the array sizing correct, the summer heat is melting my brain.
parse.pd

plot the four graphs on the same canvas?

Not completely certain about your intention here, do you mean canvas literal or graph? Are you trying to get it to look like your screen shot? or just a standard pd graph? If you want it to look like your screen shot but don't need it to be interactive you can easily use dynamic patching, if you need it to be interactive then data structures are probably your best bet but it can be managed without by hiding some sliders under a canvas. Need more info to offer help here.

@atux Your Y-range is is backwards, Y-range goes from Ymax to Ymin. Or is it that pd's Y-range is backwards? It has to do with data structures and GOPs and how they are drawn, left to right and top to bottom.

@whale-av That is the same as mine, I just updated list-inter to modern objects. But I think the goal is something along the lines of this:
list-interpolate2.pd

But there are many variations on this and I can't figure a way to effectively/efficiently cover all bases and not quite sure about @mezko's specific needs yet.

Edit: Fixed a couple errors in the patch but not the image.

@mezko It sounds like you are trying to implement a bandpass filter in the message rate to determine which partials should be on and how strong they should be? If so, a bandpass filter on the output of the synth would do the same thing and be simpler, more versatile and give better control over the sweep. Something like this but you probably would not want to use vanilla [bp~] and this would change how you would set the level of each partial but I think the same results could be gotten?

Or am I missing something? If I am missing something, some more details about your additive synth or sharing the patch would probably help.

Edit: it is probably too hot to think, I feel like I am missing something obvious.

@KoaN I have never experienced any midi latency of note with pd, I would expect it has something to do with your setup. Giving some idea of how long of a latency you are talking about, your midi setup and what OS you are on would be very useful if you want assistance in troubleshooting this latency.

@mezko Like this?
list-interpolate.pd