Question

Because Studio One is pretty CPU heavy and if you put a couple of plugins on a track  you run into performance issues, where Ableton and Logic dont with the same plugins.
You can solve this by using a background process that renders each track (think of it as an auto freeze function) to an audio file behind the scenes. Like the auto-render function in Final Cut Pro X.

Of course if you change something to a track in the timeline, it needs to render again. 
By using a background process you can go ahead with editing so it doesnt interrupt your workflow. 
If the rendering isnt done yet when the user hits play, S1 can use the 'live' (cpu intensive) version - as we do now-.
If you walk away from the computer (to get a drink or take a break) it renders all the tracks in your song for you automatically.
You can also lower the latency that way

Answer 1

Thank you for the feature request. 

If anyone else agrees or disagrees, then please vote it up, or down. 

To vote:

In agreement click on the thumbs up.

In disagreement click on the thumbs down.

The developers pay close attention to those that are voted on the most. 

You are allowed one vote. 

Just viewing and agreeing but not clicking on the vote does not help the issue. 

Please click on one or the other. 

Answer 2

sounds like an interesting concept. video editors are doing this for years now. could be cool to have such a feature.

Answer 3

AWESOME idea. I LOVE it.

I'm just worried it might have lots of potential to lots of bugs with plugins that use live input dependent on other tracks, such as sidechaining or plugins that internally side chain with other instances of itself (Soundradix Pi, Autoalign, iZotope Neutron, etc)