I started working on some compositions to do this this last year. Kind of wanted it to work like the patch bank on a synth, to save multiple states of a composition's inputs. I got the sample and send side of it working with bools, ints, strings, images and structs (not native colours) but never completed the write-to-disk and send-to comp side of it (so it's useless as it stands). It's eminently doable I think, I just got sick off spending so much time on it and hitting walls that needed workarounds.
Was hoping a coder would then use my work as a template to write a plug-in version which I think would have commercial value (it would be a $10 a pop goldmine!). (not looking at anybody kineme ;) ). If there is big interest in this I could be persuaded to throw some more hours at it. (I tend to need to spend days at a time to get my head QC oriented again as I mostly work in CS4). Also, I use the export image plugin in the dev folder with a signal patch as the trigger but it has image size limitations which are significant when you consider for print 300dpi is standard, not 72ppi. Does anybody know if the image size restriction is GPU based or QC inflicted. Alastair Useful Design On 29 April 2010 07:27, 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? > > Chris -- your suggestion is great for saving image/matrix, etc. data, but > is > making my problem more complicated than needed at present. Right now I just > want to save floats, indices, bools sent via a midi controller or patch ui > sliders, etc. my patch works well while qc is running but when i shut it > down or turn off/on the viewer everything resets to 0. > > I'm not giving up just yet. > > > > On 4/28/10 3:01 AM, "Chris Wood" <pson...@gmail.com> wrote: > > > I guess you could make something like a 'sample to disk and hold' > > patch, that works just like the sample and hold but has an additional > > input that asks for an ID key string. Then you can use multiple > > patches and have them save uniquely. By giving them the same key, they > > could share data (of course, you'd have to be very, very careful with > > this!) > > > > Also note that sampling high res images at high framerates = tons of > > disk writes and likely severe slow down in some cases. > > > > Chris > > > > On 28 April 2010 10:48, Achim Breidenbach <ac...@boinx.com> wrote: > >> Hi Jerry, > >> > >> I think there is no good solution for this. Your custom patch never > knows > >> about the QC file where it is living in (or even if there is one at all) > so > >> you can't store any data to it. Storing the data outside the QC file > might > >> work, e.g. to the preferences-folder but then you have to take care that > you > >> read in the right data for that one specific instants of the patch (your > >> patch may be used multiple times in on composition or in multiple > >> compositions, and so on). This is not an easy one... > >> > >> best, > >> > >> Achim Breidenbach > >> Boinx Software > >> > >> On 28.04.2010, at 10:56, Jerry Smith wrote: > >> > >>> 10.6.3 > >>> > >>> I'm trying to build a patch to save presets. In the attached qtz, is > there > >>> way to have the sampled value saved with the layout or when the viewer > is > >>> turned off/on? That is, it resets (samples) 0 and i want it to keep the > >>> last > >>> value in the sample and hold. > >>> > >>> Jerry > >>> > >>> <preset_test.qtz> _______________________________________________ > >>> 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/psonice%40gmail.com > >> > >> This email sent to pson...@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/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
