live.step - don't store current step position with pattrstorage
Nov 08 2016 | 1:51 pm
I think this might be a silly question, but..
I'm using some live.step objects and storing everything via the pattr system.
If possible, I want it NOT to store the current step position, so that when I recall a preset it will bring up the stored notes etc., but just keep going wherever it may happen to be. As far as I can tell, it does store the step position along with everything else, and I can't find a way to disable that.
Any ideas, anyone?
Thanks.
- Nov 08 2016 | 2:32 pmMake sure you have no [pattr] for your live.step. If you use [autopattr] use the outlet that says "exclude connection" to your live.step.
- Nov 11 2016 | 11:46 amThanks Musinou - the trouble is that I DO want to store the other information using pattr. I basically want to be able to recall sequences this way while keeping the playhead moving.
- Nov 11 2016 | 6:40 pmMaybe there is something possible to do with first outlet and first inlet of [pattr] to filter out what you don't need. And/or using (dump) and store that somehow.
- Nov 12 2016 | 8:03 pmI'd suggest temporarily storing the current step in a message box or int box, loading the preset, then outputting the previous step value. You'll probably need a gate between the live.step and the int object that is normally open, but closed while recalling presets.You might also look at the dumptodict functionalittly that live.step offers. You might be able to remove the current step from that, and then restore from the dict. (No idea whether it will fill in a default value in its place, but it's worth a shot!)
- Nov 14 2016 | 11:31 am@Peter - yes, I'd started to feel my way towards something like the first one already. I'll give it a go - I'm sure with a bit of tweaking it could work. Hadn't thought of the dump to dict thing but it might be worth a try. There are quite a lot of things in the pattrstorage, so it might be too slow..
