Re: Refreshing a Variable when Using Scene Port & Case Switc
Posted: 25 Nov 2014, 19:43
Thanks for that Christian. I took a look and have since amended my Master Scene file, as well as adding another background vis scene and a couple Info scenes.
As this is an exercise for me to learn Ventuz, I made it a point to use certain nodes in the project so I can get more familiar with their usage; The scene port was one, as my thinking in using it was so that I could use it with the Case Switch for use with multiple scenes for background Vis designs and multiple song info scene designs. Thus, making it more modular. I was also assuming that it may streamline the overhead by only having one scene active, as I think the non-active scenes would tax the machine if all scenes were loaded at the same time. If I am thinking about this incorrectly, please let me know. But, that was my inexperienced Ventuz thinking.
Below are the updated/added scenes (first 3 in this post and the remaining 2 on next post—5 total). I have added simple animations and tried to program around the minor issues from the original scenes.
I welcome any-and-all critiques. The visual design is crude and simply for function. Thus, not-so-elegant, which I am not concerned about at the moment. I plan on going back and making things prettier once I have the functionality a bit more elegant. Please comment on the logic, the functionality, etc. I am interested on what active Ventuz users would do, or would have done. What nodes, techniques, logic works, what doesn't work, etc.
So, anyone/everyone, feel free to take a look and pass-along your comments. I would appreciate anyone looking at what I am doing. Refer to previous posts in this thread for interaction instructions and link to the original project that contains the assets (~150Mb). Simply update with the updated scenes and open Music_Master_Try-10.vzs.
Thanks,
-- Dondi
(Post 1 of 2 of updated VZS files)
As this is an exercise for me to learn Ventuz, I made it a point to use certain nodes in the project so I can get more familiar with their usage; The scene port was one, as my thinking in using it was so that I could use it with the Case Switch for use with multiple scenes for background Vis designs and multiple song info scene designs. Thus, making it more modular. I was also assuming that it may streamline the overhead by only having one scene active, as I think the non-active scenes would tax the machine if all scenes were loaded at the same time. If I am thinking about this incorrectly, please let me know. But, that was my inexperienced Ventuz thinking.
Below are the updated/added scenes (first 3 in this post and the remaining 2 on next post—5 total). I have added simple animations and tried to program around the minor issues from the original scenes.
I welcome any-and-all critiques. The visual design is crude and simply for function. Thus, not-so-elegant, which I am not concerned about at the moment. I plan on going back and making things prettier once I have the functionality a bit more elegant. Please comment on the logic, the functionality, etc. I am interested on what active Ventuz users would do, or would have done. What nodes, techniques, logic works, what doesn't work, etc.
So, anyone/everyone, feel free to take a look and pass-along your comments. I would appreciate anyone looking at what I am doing. Refer to previous posts in this thread for interaction instructions and link to the original project that contains the assets (~150Mb). Simply update with the updated scenes and open Music_Master_Try-10.vzs.
Thanks,
-- Dondi
(Post 1 of 2 of updated VZS files)