Quit the scene automatically after rendering..

[DeadMusik]

Hey D-rel here again sorry if I overlooked this on the manual, but the title says it all..

I like to do my renders while I go to bed and the render duration changes with scene complexity. I fall asleep and then my computer just stays hot and chugs all night, is this something I'm overlooking.

Maybe a go black feature where your gpu can go back to a normal load.

Thanks guys and I'm about to post some footage, peep the user submitted

[Eric]

I think that sounds reasonable. But perhaps the better option is to allow the app to exit completely when the rendering is done?

[Sadler]

Apart from a new option to exit the app (which would require saving the comp, no?), you try these two work-arounds.

Assuming your complex scene is responding to music, then you can disable nodes based on volume. You could do this for one node just before the magic node. That would stop much of the processing.

A second work-around is by using the playlist. If you have the editor with an empty scene active, you can still render out the playlist and when it's finished it would go back to playing the empty scene.

[DeadMusik]

Thank you booth for the reply's...

Eric -

That wouldn't be bad, but when I wake I usually have another playlist waiting to be fired up and I start rendering while I then go to work. so for me the black out or some form of idle but magic is still running works and the computer is able to go into rest mode.

1. Exit application when done rendering would be lovely...
2. Dark mode after rendering...

--- Screen saver works (if you forget to turn off the monitor)

Sadler -

Genius idea... so your saying insert a blank active scene at the top of your playlist, and start the render on [1] to lets say 5 total slides...
render goes from [1 - 5] while [0] is a black active scene, it renders then will iterate back to [0].

Am I getting this right?

Then since your computer is at an idle state with a blank scene my gpu will go back down to idle and love me again?

But wouldn't that affect live performances I mean this is a SMALL hiccup but if I didn't remember to remove that black as an active?
then all my screens would go black as I advance, would suck if I wasn't by the booth.

--- No screen saver (I usually have some beers before bed and my monitor is blazing with the comp in the early mornings )

Sorry for my limited computer knowledge but when I give that render name a save location and click enter isn't that saving the comp? I am kinda lost on that aspect.

[Sadler]

so your saying insert a blank active scene at the top of your playlist, and start the render on [1] to lets say 5 total slides...
render goes from [1 - 5] while [0] is a black active scene, it renders then will iterate back to [0].
Am I getting this right?

Almost. You have one or more complex scenes open in your current project. Add what you want to render to the playlist. Then add a new empty scene to the end of the playlist. The render time has to be set to land on the empty scene.

I thought, incorrectly, that Magic would return to its currently active scene after the render had finished, but instead it stops at the last scene rendered in the playlist. I tested this time

[DeadMusik]

Okay that is a feasible workaround right now, for my renders..

So add a blank active scene at the end..
5 slides total, tell it to render only [0-4], if the total duration is 2:00 minutes and the black screen would start one second after.
you'd cap it at 2:00 flat, and magic then will roll into the next slide which will be an active black screen? at 2:01...

Thanks