WILLIAM J MACKWOOD, BFA (UVic), MFA Design (UVic):
William is Co-Artistic Director of the innovative, multi-disciplinary company Out of the Box Productions. Over the last ten years he has co-created and lead the design team for productions of Opera Erotique, The Third Taboo, Prior Engagement, Sound in Silence, and Bugzzz~ a cautionary tale.
On faculty in the Department of Dance at York University, he teaches ‘Dance Production’, ‘Dance Video’, ‘Lighting Design for Dance’ and ‘The Interactive Stage: explorations in electronically mediated performance’.
The heart of his research lies in ‘sustainable design on demand’, which has lead him to his current interest, pursuing a rigorous investigation of digital interactivity in live performance.
William is a member of the Associated Designers of Canada and is currently serving as the Graduate Program Director of the MFA Dance program.
I am starting a discussion rather than a reporting a bug as I'm not sure if it's something I'm doing incorrectly.
I have included a very simple composition that saves an entered value to a data file (.txt). As a VUO composition it will both 'save' and 'fetch' from the named file in the root directory (the same directory that the composition file is in.
However, when I export an App, it no longer saves to the file that it creates in the 'Contents/Resources' folder, but rather, saves the data to a file it self-creates on my desktop.
●●●○ — It prevents me from completing a specific task with Vuo.
Steps causing the bug to occur:
Select export to Mac App
When 'compiling' VUO crashes
Having spent many, many hours building this lighting interface for my studio, I would like to run it as an app. I would be very appreciative if you are able to tell me what the problem is, and how I might be able to change the composition so that it will export as a Mac app.
I'm hoping someone can help me with this as it's driving me a bit crazy . . . and maybe I'm missing the obvious. As I'm building more UI compositions switching outputs to various ports becomes valuable. However, the 'Select Output' nodes do not have the option to change the output without sending the current 'In' value. As I'm using VUO to control devices, this creates problems.
I would really like to be able to switch output (sending no value) and then make changes to the 'In' which are sent to the selected output.
I too would like to see a text/number input UI node. This would be very helpful for the 'lighting visualizers' I create in VUO. These would not need to be complex, just a graphic box that accepts either text or numbers when highlighted, and fires when 'enter' is hit.
Not a super high priority, but very helpful for interactive compositions.