Oh, I just read George's post about the image input patch and realised I was parroting him, sorry.
On 4 May 2010 15:46, Alastair Leith <qc.student...@gmail.com> wrote: > I don't see any great issues with saving input state data to external > file(s). It provides options for versioning and copying an XML or JSON or > what have you with a .qtz is no big deal from my perspective. > > QC files can save images drop onto them so I don't see why a plug-in can't > invoke some kind of data bundling(?) in a similar way. But then I can't > code Cocoa so what would I know :) > > On 3 May 2010 19:14, Achim Breidenbach <ac...@boinx.com> wrote: > >> Hello George, >> >> the problem I see is that, when you try to save data to the qtz file from >> a plugin point of view, you don't have any connections back to your >> container file where your plugin instance was originally extracted from. So >> I see no way for a plugin to find the host composition file to store data >> in. >> >> Any ideas how to solve this problem? >> >> Best, >> >> Achim Breidenbach >> Boinx Software >> >> On 03.05.2010, at 07:29, George Toledo wrote: >> >> >> On Wed, Apr 28, 2010 at 5:27 PM, Jerry Smith <je...@sonsmi.com> wrote: >> >>> Thanks for the feedback, Chris and Achim. >>> >>> I am writing before coming back to this -- I was thinking there could be >>> a >>> solution using logic/conditionals. The Signal patch could trigger a >>> Sample >>> and Hold on startup, right? Macros/patches keep their values, so why so >>> difficult? >>> >> >> Sample and Hold only has a Virtual input. Virtual data isn't able to be >> stored to file, or in-composition. Trying to store something across Open and >> Saves with Sample and Hold is going to be a gigantic time burner, and >> doesn't work. >> >> It would be technically possible to have a version of Sample and Hold that >> embedded data in the qtz, and it could do it with any data type, save for >> Virtual. The Kineme Value Historian is a version of this concept that will >> store many data types, but not Images, Virtual, Interaction, Structure or >> other non-standard types. Yes, it does have Virtual Inputs, but stores a few >> different data types through conversion. >> >> I don't think that Value Historian is configured in a way that makes it an >> instant replacement for Sample and Hold, but you may be able to make it work >> for you. It could very well be extended to save other data types, and you >> may want to file a feature request, or request a quote if there is some >> functionality that you need that isn't there. >> >> I don't believe Achim is correct that data cannot be stored in-composition >> with a custom patch. Any data type is able to be embedded in a qtz, though >> large file sizes can cause problems when attempting to run the resulting >> qtz. There shouldn't be a technical problem with recording user data to the >> actual qtz file, and having a patch have a setting to retrieve that data. >> >> >> Best, >> George Toledo >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> >> http://lists.apple.com/mailman/options/quartzcomposer-dev/achim%40boinx.com >> >> This email sent to ac...@boinx.com >> >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> >> http://lists.apple.com/mailman/options/quartzcomposer-dev/qc.student.au%40gmail.com >> >> This email sent to qc.student...@gmail.com >> > >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
