Hello everybody, I am banging my head against something that I think it is easy but I can’t find a way to do it. I have basically 4 scenes, each scene has 3 cameras.
I want to show a scene for 3 minutes, and then go to the next one.
In each scene, the camera change every minute.
I have read about Clock, Timer, Timeline and a custom chop called Schedule. It looks like there are 10 ways to do this but none of them sounds clear to me. Can someone give me a suggestion?
I was thinking to build a DAT table with 3 column, one with the duration, one with the scene id and one with the camera id.
And then start reading from the first row when the application start, read the duration, apply scene id and camera, and goes to the next line when the duration time is elapsed. If the scene ID is the same, do not change it, but change the camera if it changed. In this way I would have a clear overview in the dat file about the schedule of my app and a central place where to edit it. What do you think? How would you do this?
TIMER.tox (3.1 KB)
This example uses noise top, just to simulate cameras
Ready! You only have to change seconds in every scene. Is that what you wanted??
Of course, for every scene or camera added you need to adjust the settings.
In order to use buttons provided…you need to have their viewer active (the plus sign bottom right corner of the node)
All we need is TImer… set its property accordignly, length (in sec) and cycle + restart when done. then we add 2 select nodes…one for timer and one for “done”. The “timer select” node goes to counter (adjusted accordingly) input and the “done select” goes to counter reset. Eventually, export counter to switch. And basicle you are done. Readjust and repeat for scenes.
Well @rhesus3000 , thank you very much for your time this is more that what I have expected. If you don’t mind I have a couple of questions regarding the timers, that looks like a flexible solution.
The timer in the upper level is set to length 15 seconds. I assume this timer defines how long each scene should be displayed. So, in case I want to make it longer, I simply have to increase this value, am Icorrect?
It is not clear to me how the timer together with select and count works. I have attached a picture with some question about it.
The timer in the upper level is set to length 15 seconds. I assume this timer defines how long each scene should be displayed. So, in case I want to make it longer, I simply have to increase this value, am Icorrect?
Yes. Exactly.
It is not clear to me how the timer together with select and count works.
We use “select” to “extract” values from node it has been connected to(in this case “timer”). Timer provides all sorts of values, but we need seconds only and done status to reset the counter. The counter itself has some conditions at which it knows how to count and what to do.
Why does count1 go from 0 until 2? how to add scenes?
As you can see we have a switch for 3 scenes. Switch value 0 correspond to scene 1. Switch value 1 correspond to scene 2 etc…
To add scenes you have to Add an actual scene and adjust “timer” maximun cycle to “n+1”.
Why do i need null?
We use “null” to kinda set the end. For example. If i connect the count to switch, but then need to add a “math” for some reason, i would have to do the connection all over again. Adding a null and connecting it to switch eliminates this problem.
Inside scenes the same logic applies. You can enter them by double clicking on “3_Cameras_1_minute” base and set the timer value accordingly (in each base of course).
Thank you @rhesus3000 for your reply. One thing is still not clear to me. I have copy and paste the last scene and I have plugged it to the switch, that correctly, in the Input OP section was showing 4 options. But the counter still goes from 0 to 2. So, How can I have a counter that, for example, goes from 0 to 3? How can I add a scene more to the component that you have posted?
The above field auto completes timer’s cycle. SO…add a scene then enter the sum of scenes in the field.
Iam sorry but i cant be more specific than that. From now on, knowledge is in your hands regarding scene timer.
this is more that what I have expected. If you don’t mind I have a couple of questions regarding the timers, that looks like a flexible solution.
and adjust “timer” maximun cycle to “n+1”.
