Has there been any progress on releasing [expr] and [expr~] under BSD license?

I hope that the ball started rolling again!

"The only ones that don't get sent are the ones that have never been adjusted. You could just connect a [loadbang] to all of the sliders"

That's what I ended up doing.

"What!? These are supposed to be vanilla friendly. What did you have to do?"

Sorry - hack was a strong word. I had the same issues ([prepend], [tabdump], and [tabset]) as the guy above... Any other issues I had were my own fault as I worked to refactor what you've made to work in the system I'm developing.

These are very helpful abstractions. Thanks again!

One other thing I've noticed...

If we take, for example, 'dump-example.mmb'... When I click dump, it only saves slider values that have changed since the last time I saved. What I really need is a snapshot of all slider values that I can store as a preset. If all slider values are not saved, the preset isn't very useful, as when I load it it doesn't represent the complete state of the object. The problem persists even if I use 'save2.'

It's possible I'm doing something wrong, but I don't think so...

You mention above that "if there's anything you think I should add to either the documentation or the functionality of the abstractions themselves, let me know."

Well, if I'm right, and this is in fact how the abstractions currently work, it'd be nice if they provided for an actual 'dump' message that would record the value of everything hooked into the save.me.mmb in question. If that's too much hassle, maybe just explain a way to actually dump all params hooked up to a save.me abstraction.

And if in fact I've broken something, please accept my apology. I had to hack a bit to get this running with pd-vanilla...

Thanks!

All of the major audio packages (ProTools, Logic, etc.) support automation - they let you write (and play back) changes to parameters over time.

Until now, that hasn't been in scope for this project, and it probably still isn't... But your nice abstractions made me start to think about it.

I think it'd be pretty tricky. For one, there's the question of the density of the data - how much would you need to read / write to get the job done?

What are your thoughts?

thanks...

Hi Maelstorm,

I'm using these abstractions and they work great!

I'm wondering if I'd be able to use them for automation - in other words, saving state over time.

Can you think of a way to do this? I'm new to PD, so I'm just looking for a nudge in the right direction...

Thanks!