Yup! (Sorry for the double post, but I figured this warranted a new one. )
Pulover’s Macro Creator can actually just check for an image every so often. Meaning no more setting a generous timer to avoid problems.
Right now it works like this.
1: Start up process
2: Manually open , and close it again. ( So that the next time it opens, it starts with the ‘done’ button highlighted. )
3: Script runs, sets settings to 360 stereo + desired resolution.
4: It starts the render.
5: pauses for a second
6: starts checking if the ‘Snap’ button is green again, once a second. (It’s greyed out while rendering.)
(It does this using the image/pixel search macro function. Allowing it to check a region of the screen for a specific image. like the snap button being green.)
7: once the render is complete, and the snap button is green. It waits for a few seconds.
8: Then closes , and presses tab, to make time progress by a frame.
9: then it loops.
The only thing I need to wait for now is step 7, when the render is done and where processes + saves the rendered image.
Because if seems to slow down the processing a lot if you’re rendering something at the same time (understandable.), and if render 2 is done rendering before render 1 is done processing, it’ll just throw out 1. On my pc, reading from and saving to a normal 2.5 ssd, it seems to take approx 4-5sec to save a 360 8x8k jpg. Massively longer for an .exr.
While if I render while it’s processing, it’ll easily take 10-15 seconds, aka long enough for the next render to interrupt it.
With 4x4k images I only need to wait around a second before progressing to the next render.
Still, that’s massively more flexible than the old way where you had to account for how long it might take to render.
Now it’s just waiting for the render to complete, then waiting a few seconds for the image to process, then on to the next one.
(It doesn’t matter if the render takes 5 seconds or 500 seconds.)
Image: how it’s set up.
At instruction 50: Space to start rendering.
51: wait a couple seconds, since there’s no point in checking if it’s done rendering at <10 seconds.
52: starts checking for the green snap button / the render being done, once every second.
53-61: After render, wait for a bit, close window. End of macro, so that it can loop once it’s done.
nice idea. can u make video on how u manage all stuffs, specially that image/pixel search macro function in process. and i have one big doubt. do this process support cinecamera.