Value Historian load .plist

It'd be nice to be able to load from a folder of .plist files as a structure of files. I guess this could require a new "plist" patch that outputs the structure of files, and an input on the Value Historian.

Right now I believe the only way to use multiple files is to create multiple Value Historian patches with different files loaded to each, then switch between them.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

usefuldesign.au's picture
Re: Value Historian load .plist

A file path input for read and write like Structure File Tools would seem more logical to me. Then existing directory scanner and queue tools could be used to read in multi-file based structures. Existing Structure tools could split a QC Structure into various files for writing multiple files (inside an iterator?).

gtoledo3's picture
Re: Value Historian load .plist

I never understood much point of it being file backed, but as long as there is discussion about that direction, it should also be able to save to file via boolean input and a filepath (same for loading - load from file path true/false, and a file path string input). That way you could have one saving files, and another one for playing back, and read the file paths with directory scanner dynamically.

What's more pressing(pun intended) for me and that plugin is it catching keyboard up movements more accurately. Sometimes I have to do a smooth /rounding thing to get it to register the key presses correctly.

It's already fairly flexible in being able to effectively get multiple "takes" in one historian. All you need to do is make each successive "take" a very large amount of time from the last, and then play separate sequences back, by controlling patch time.

dust's picture
Re: Value Historian load .plist

kineme structure to file and from file are basically value historians. you can record what ever parameters down to file. let's say x y z and time then read the file back fairly easily. that way you are no limited to the value historian.

gtoledo3's picture
Re: Value Historian load .plist

Yeah, that's why I never quite understood the point of Value Historian being file backed. I thought the whole good point was that it was embedded and you don't have to worry about files, and you can multiplex, etc, if you want to route different VH's. You can even add more inputs dynamically, so that you could have multiple "takes" in a patch in that way...

jersmi's picture
Re: Value Historian load .plist

Ah, I see about the Structure to File concept. Hadn't dealt with it in this way yet. Glad I posted this. :) Maybe should have been a question, but it would be nice to have the VH a little more reliable, as it is an all-in-one, I guess.

Still looking for a decent save / load preset idea.

jersmi's picture
Re: Value Historian load .plist

"gtoledo" wrote:
I never understood much point of it being file backed
Here's a point:

When I can create individual files, then I can see what I have done, I can edit / trash / reorganize individual files more easily than one giant .plist with a bunch of takes. If I delete a file, the structure count updates, done. Clear and simple.

Or maybe I'm not getting something, which is certainly possible (for ex., developing some solution using the struct to / from file patches).