When you start using abstractions it gets slightly more complicated...well, there are more options

Arif's solution there is useful for initializing state when the abstraction is created. This could be furthered by using more messages with values, then using [sel 0 1 2 etc] to fire the preset message:

[hradio]
|
[sel 0 1 2 ]
| | |
[0.521 8 4.320( [0.521 8 4.320( [0.521 8 4.320(
| / /
[unpack f f f ]
| | |
etc
sorry for the shite diagram. This could give you 3 'factory' presets built in to the abs

But you want the presets saved globally. For this you can use SSSAD in pd-ext - pretty straightforward and versatile. Or you can create your own system by giving the sends and receives unique names based on the creation argument you give when you create the abstraction.

To get some ideas i take a butches at Obi's Waveshape synth (more for the preset writing/recall) mechanism http://obiwannabe.co.uk/html/music/6SS/six-simple-synthesisers.html

I have a loop that makes a recording during each pass.
At the moment the files are named sound%d.wav, where %d is the counter value.

Now, I want to get more logical filenames based on two parameters. One to dermine a preset and the second, based on the counter value ,to determine the second part of the filename. The problem is the second part not having an equal length for each preset.

For Example:

when preset/first part is set to:
* A1 the second part will be: X1, X3, X4 (counter 1->3)
* B1 the second part will be: Y6, Y-4, Y-1, Y3 (couter 1->4)
* C1 the second part will be: Z4, Z-3 (counter 1->2)

In other words (as I think I the above is not really clear):
I want to do some conditional (?) selection

when preset is A1 and counter 1 -> A1X3.wav
A1 and counter 2 -> A1X3.wav
etc
C1 and counter 1 -> C1Z4.wav
C1 and conter 2 -> C1Z-3.wav

.. but how?

edit: Only need to run the loop for one (a priori chosen) preset !

I cannot answer this if I haven't a full working Memento, anyway as far as I can see, Memento is oriented to store several presets and quickly switch among them.
The same is possible with SSSAD as well.

You can store several presets by creating a number of subpatches named as you wish (e.g. pd preset1, pd preset2, ...). Then, when you want to save the "preset1" state, you have simply to apply this argument on the "datastore" abstraction and press "save" button.

Once you have saved your presets, send bangs to the messages stored inside subpatch preset1, preset2, ... in order to switch among different presets.

I cannot say more about Memento but I think I will continue to use SSSAD.

Bye

E

ok, with SSSAD module I can make independent presets, and change only those I need.
Perhaps somebody doesn't know sssad or my method can be little obscure,
therefore I prepared an example patch where you can see my method.

In the old version of example-preset I used three abstractions from s-abstractions (by Chris McCormick), one of them I modified to include the SSSAD module (s-varenv). All the stuff you need should be in the attached folder.

the example is very simple but is useful for real time performances, (for instance using midi controllers).

The new version of example preset (english and italian version) is a basic tutorial for creating multi-preset patches

http://www.pdpatchrepo.info/hurleur/example-preset.zip

I do the following :

• each patch has its own presets. Not in a table but via (rather large) messages.
• my master patch also has presets which actually sets the correct preset on each patch

Probably not as elegant as a table solution - especially the saving to/load from files is missed - but its simple and it works. I've also been thinking about table based solutions, but then i've noticed that, although i initially always think i'm going to need 100 presets for a patch, i always stick to the same 3 or 4 presets (per patch).

Nevertheless hardoff, any chance of a valid windows archive?

Thx,

D.

I'm designing a flexible preset system for my live setup. Basically(!) it includes a couple of looper/slicers, a flexible drum machine, a few effects/filters and probably a mixer of some sort....you know the usual

I was thinking it would be cool if it had the same sort 'Scene' functionality a la Live's session view. i think it would be best to store the presets into tables that can be saved off as text files

Would it be best to have a preset table for each component? Then save each chosen preset into a master table for the 'Scenes'. What if I had to store a list of sample filenames? I want to build this right from the start ya see

cheers

in the past couple days i have built a very extensive saving system that didn't work, and now i'm back to the drawing board. it's okay, because i looked at the documentation for qlist and textfile in max/msp. you really do get what you pay for. i'm now working on using qlist to assign each drum sound a dedicated line in the file, and then have qlist navigate to the correct line and make changes. this seems necessary to prevent the creation of a new line each time a change is made, which is what happened with my first idea.

my questions are:
is there a way to tell qlist (or textfile) which line to go to? i know that you can in max but those commands don't work in pd. maybe a port of max's qlist and textfile objects is in order.

is there a way to automate repetition of messages? i could navigate to the correct line by sending "next 1" to qlist x times where x=the number of the line i'm trying to navigate to.

are there any other objects (including third-party) that can manage textfiles similarly?

thanks, leo

Hi List,

I'm new to PD, GEM and computer video but am familiar with midi in max. I have a few questions. PD and gem seem like truly wonderfull and amazing tools but I need to get my bearings.

Is there any way to start up PD so it knows my audio and midi prefs - so I dont have to reset this if it crashes (I'm using the wish&tc&tk shell installation)? Maybe something in the terminal when I run it? Is there some preference file for the mac components I can tweak?

So what's the best strategy for dealing with presets in patches as there is no preset object? I noticed that there is no preset module like in MAX. I read the "differeces from max/msp" section but am still unclear. Do I need to make lots of message boxes and click all of them?

Is there any Show/hide for cables?

Is this the best place on the web to hang out and ask questions to learn about PD and GEM?

Also is there any place I can see where inlets and outlets go to or what signal they want?

Thanks a lot in advance.
-b

okay .
A little complex form now. I have to practice a little more.

But it's an impressive job !

I've discover the jimmies-objects : see

the object pbank is quite powerfull to save preset. my abstraction

I think Qlist, textfile, pbank are objects to store preset. but store a streaming of data. Wich way use ?

hello I've done some abstractions to use the object QList as a preset recorder and player. It allows to record a stream of number too.
The help is in french. I'll do an other better in english.

the differents views:
1 - - - view one.
2 - - - view two


downoad all