How much time does render takes? How many tracks, instruments and inserts do you have? In what format do you render?
Please attach screanshot with rendering window

This happened to me awhile back... but not sure it's the same issue with you.

I usually only render when mixing down to .wav or mp3. When doing so the pop up window shows something like "3.8 times faster than real-time rendering". My issue was that I accidentally put "Pipeline" on a track. It also happens with (I believe) any external effect that has to be tracked with the song during mixdown.

From the S1 manual:
Note that when Pipeline is inserted anywhere in a Project, it will no longer be possible to render audio exports offline for CD burning, disc-image creation, or digital-release creation. Real-time processing will be used, as this is required to incorporate your hardware insert into the audio export.

Dmitriy_m2m wroteHow much time does render takes? How many tracks, instruments and inserts do you have? In what format do you render?
Please attach screanshot with rendering window

My CPU power cannot handle all tracks in the same time (because i use hungry plugins), so i oftenly during working on songs convert tracks to audio and back.
Even converting one track to audio takes long.

But i record at 192Khz/32bit at double persigion and all plugins a runned at max quality.

I have a base model of Mac Pro late 2013.

So is this my CPU power is too weak or it indeed uses only one core?

I cannot post picture in good resolution because on this forum u have restriction on posting images more then 800x600 but i have 1440p monitor.

But sometimes rendering goes to 1.4 real time on a single track.

I think S1 can't render one track using multithreading just because you have plugin chain on this track. So S1 needs to wait one plugin rendering before rendering next one. Here is no way to parallelize one track rendering.
I'm not famaliar with mac, but can you monitor cpu loading while rendering?

192KHz is your problem.
In my opinion, recording at 192KHz is totally pointless, but even setting that aside, you are doing roughly 4 times as much work as mixing down at 44.1/48KHz.
I bet you can't hear the double precision either, which is another 2x the work. So you're using 8 times as much CPU as you need.

Dominic

Dmitriy_m2m wroteI think S1 can't render one track using multithreading just because you have plugin chain on this track. So S1 needs to wait one plugin rendering before rendering next one. Here is no way to parallelize one track rendering.
I'm not famaliar with mac, but can you monitor cpu loading while rendering?

I have the latest version of Studio One.

dominicwperry wrote192KHz is your problem.
In my opinion, recording at 192KHz is totally pointless, but even setting that aside, you are doing roughly 4 times as much work as mixing down at 44.1/48KHz.
I bet you can't hear the double precision either, which is another 2x the work. So you're using 8 times as much CPU as you need.

Dominic

I do the best i can!!!