Title: I/O for fragmentarium Post by: Patryk Kizny on June 14, 2015, 01:17:27 PM Hey,
Just a quick question. Not sure if it's easily doable or implementable. As always looking for integration with VFX pipeline and stuff... That's just me. I would like to do the following: - import an external file (ASCII, CSV or a waveform) and get access to the data from fragmentarium to either parametrize animation or animate camera - export selected parameters of animation per frame - along with saving the sequence of JPGs I wish I could select parameters to be exported and it would save them as a set of files or a single file CSV data (columns would be fields and rows would be frames) Is that doable? I guess the latter needs adding options on a C-side, but maybe the first part is already there? Title: Re: I/O for fragmentarium Post by: Syntopia on June 14, 2015, 10:47:07 PM The easiest way would be to put your data in an image (.hdr is supported), and load the image as a texture. Then you could read the values in the GLSL script.
Otherwise you'd need to add C-code. Title: Re: I/O for fragmentarium Post by: Patryk Kizny on June 15, 2015, 10:46:49 AM Thanks!
Actually I found a simple way of working around the input - instead of rendering to bitmaps, I save out to CSV, text-convert to array data type and just include arrays in on the GLSL side. Pretty usable for smaller amount of data and does what I need. Title: Re: I/O for fragmentarium Post by: Patryk Kizny on June 17, 2015, 01:18:52 PM How about exporting?
Is there any trick to dump parameters for each of frames to the debug text window or an external .frag file? Title: Re: I/O for fragmentarium Post by: 3dickulus on November 11, 2015, 11:09:39 PM With QScript control you can save parameters or frag every frame tick if you want :)
Title: Re: I/O for fragmentarium Post by: Patryk Kizny on November 12, 2015, 06:55:27 PM Gotcha, thanks.
Title: Re: I/O for fragmentarium Post by: 3dickulus on November 13, 2015, 04:02:17 AM I added app.saveParameters(fileName) to the script commands, saves parameters like in the "Parameters" menu but without a file dialog, you will have to generate incremental filenames just like when saving images from a script animation. If the save fails it will open a warning dialog and will halt until "Ok" button is clicked, I know, not a great thing for a remote render but at least it won't just continue to render 5000 frames wrong. app.loadParameters(fileName) is already available in v1.0.14, save will be in the next patch release v1.0.15 :beer: |