• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

Transfer to Realtime Audio does not restore pan settings...

S

Sayat Nova

Member
Hello Everyone,

I am going back to adjust rendered/frozen audio tracks, and so far none of the tracks restores the pan settings, just restore to the default centre setting (it was set when frozen...)... Also, any tracks that had dual mono as the spanning setting are restored to the default pan setting, and not the dual pan it was set for when frozen...

Can anyone with a Mac please verify this? Perhaps this is more issues with Console One System... Man, I hope not.

How do I submit a bug report to Presonus?

Thank you.
 
Can you post an example of the before and after screenshots for what you're seeing?
 
Similar to your previous thread:
studiooneforum.com

Keep Pan and Volume same after Transform To Rendered Audio?

Hello Everyone, I am in the middle of mixing a project and have maxed out my CPU. So, I am now "Transforming To Rendered Audio" all of my tracks to freeze them and save/regain CPU. It is working fine, however, each time the track finished processing, it prints the audio with the volume level...
studiooneforum.com studiooneforum.com
 
Yes, and no:
The previous post was about finding a way to not have the pan and volume info set to defaults after a freeze.
This post is about pan and volume not being remembered on rendering back to realtime audio...
Similar, but hopefully relevant enough to post this second message.

I believe we were asked to post separate potential issues/bugs in their own threads by the Mods, so I did so.

Do you have something constructive or helpful to add?
 
Last edited:
Sorry for the delay: life got a little busy, unexpectedly....

So, last night I returned to the studio. I started up the same project that has been maxing-out my CPU and creating problems, and then turned all plugins off via the universal enable/disable button in S1. I then turned on just the Instrument tracks I needed to re-visit and adjust. When I was done with these and re-froze them, I tried to use the universal enable button to turn-on all of the inserts at on time and it did nothing. Inserts would not all turn back on from this button. Had to go to each track and turn them all on again, one-by-one... Figured I would just shut-down and re-boot the system to see if that would help. Also wound-up rebooting the Console 1 Fader and Console hardware, for good measure... I also turned off the "use efficiency cores" and I was able to get the heavy session to play without pops and clicks (CPU meter is at 90%, drop-out protection set to maximum)... and this is after all tracks have been bounced to save CPU...

Once re-booted, the pan type and values, along with the fader levels are now returning to their set states when being rendered back to real time audio... I guess that is good news? I have no idea why this now works, but it does. I'll take it.

That said, writing automation is still not working correctly for me with e Console 1 Fader as the input device, as noted in my other thread.
 
Sayat Nova said:
I was able to get the heavy session to play without pops and clicks (CPU meter is at 90%, drop-out protection set to maximum)... and this is after all tracks have been bounced to save CPU...
Click to expand...
It just seems that you're having to jump through hoops to support your projects...
Do you need to upgrade to a system with better performance and more resources?
 
You are on an M1 and that should still be powerful enough to run even the biggest session. Unless you are on the verge of running out of CPU and in my case the M2 offers better performance. (the M1 only has 4 performance cores and 4 efficiency cores) so getting your M1 working with the efficiency cores is your best bet without freezing any tracks at all.

Checking Use efficiency cores does work for sure. I have got an M2 Max with 8 performance cores and 4 efficiency cores. Getting the other 4 to work is excellent indeed. I have found sessions that may have not played well without this ticked certainly playback smoothly with this feature engaged. You need to experiment by trying different combinations of buffer settings and DP settings too.

You can open one of two CPU meters that show you core usage. The normal window is there but there is another one. In Activity Monitor go to Window then check CPU Usage. Also Check Keep CPU Windows on Top A smaller CPU window now shows up but its better. It refreshes much faster and at any given instant gives you a good quick reading of how the CPU cores are being used. You can now stop, change buffers and DP etc and then go into play and see the immediate results. Its a better window for tweaking settings. With the right combination of buffers and DP I always got a better result with the efficiency cores option checked.

If the session plays well without the efficiency cores then checking this option won't do much. It comes into its own when the session is on the brink of breaking up without this option checked. Then when checked it will play nice especially after some buffer/DP tweaking. Best to just leave it checked all the time.

I have found though experimentation there is a sweet spot in terms of buffer settings and DP settings and using the checked efficiency cores option. Using the smaller CPU cores window helps with this. In my situation I am using a combination of software synths and audio tracks with plugins etc.. I found going too high in the buffer settings worsened things and the same applied to the DP settings. I get a great result with buffers at 128 and DP set to minimum. Also don't assume a certain setting will apply for every session. Try tweaking the settings for individual sessions.

Choose a buffer setting and try different DP settings and watch the smaller CPU core window. Do this at 128, 256, and say 512. I found I landed in a sweet spot where I got a very heavy session to play every time with efficiency core option checked. Without it checked the audio broke up etc.. I don't think it is a big concern though either as the performance cores alone on the Mac Studio will handle just about everything you care to throw at it. But I am happy to say I believe it works because it can get you just over the line in terms of getting a big complex session to play well before you start rendering things down etc...

I am still on Sonoma and everything is just working super smooth on that for me. You do not have to update your Mac OS to the latest version.
 
Last edited:
Very frustratingly, I am dying to try these suggestions out, but I am unexpectedly busy with my day-job right now. However, I just wanted to reply here and say thank you all for the info and great suggestions. I am also baffled why in S1 I have no cores showing more than 30% usage, yet I am getting crackles and a 90%+ CPU hit globally?!

BTW: I am on an M1 Mac Studio Ultra... So, I actually have a 20 core CPU... But, still having issues. I hope fine tuning settings following Jenmusics' advice will help.

Just some more info: I mix at 24/96k. I use quite a few groups and busses. Also, I often use parallel processing on busses.
It also seems like when I place any plugin on the master track, I get a massive hit in CPU for the project. So, I have been creating "pre-master" busses for things like "All VOX:, and "All Instruments" and doing my buss processing there because I can't seem to do it on the Master buss. Again, not ideal. Granted, I am using some heavy CPU plugins like the "Unfairchild", the "821 MDN Tape" from Pulsar Modular, DMG "Multiplicity", etc, but this seems not normal?

I am also using a good grouping of UAD-2 plugins (have 2 Octo satellites...), and I read somewhere on the Persons website that all of these get put on a single core in S1? That seems not ideal: how can you spread the load for the CPU in the project if you can"t control where the UAD plugins get allocated? The whole point of the satellite is that you don't hit the CPU of the computer, yes?...

Thank you for any thoughts and replies to this, as well...;-)
 
Last edited:
Sayat Nova said:
Very frustratingly, I am dying to try these suggestions out, but I am unexpectedly busy with my day-job right now. However, I just wanted to reply here and say thank you all for the info and great suggestions. I am also baffled why in S1 I have no cores showing more than 30% usage, yet I am getting crackles and a 90%+ CPU hit globally?!

BTW: I am on an M1 Mac Studio Ultra... So, I actually have a 20 core CPU... But, still having issues. I hope fine tuning settings following Jenmusics' advice will help.
Click to expand...
Do you have efficiency cores enabled in the Preferences (Preferences -> Audio Setup -> Processing -> Use efficiency cores)? If so, turn this setting off.
 
You have got a serious machine there and there is no way you could be running out of CPU surely. Have you opened the devices window to see what is consuming the CPU power and how it is distributed. There must be something that is creating the bottleneck. What model do you have. eg Laptop or Mac Studio?
 
I'm going to back up what Lucas wrote, as that's my direct experience with my M4 Mini Pro. I had zero issues with spiking prior to the intro of efficiency core support. In fact, I did a test where I loaded it up to the absolute limit with a ridiculous number of plugins and a 64 sample buffer, and it failed gracefully with periodic dropouts, but no spiking whatsoever.

When efficiency core support was added, it was defaulted to "on". All of a sudden, I was getting spiking even on simple projects. Once I realized what was happening, I disabled the efficiency cores, and the spiking went away.

In my case, the only application that needs the power cores is Studio One. Every other application I have is running on the efficiency cores (I checked). When you enable efficiency cores for Studio One, it's sharing those cores with any number of applications that aren't necessarily well behaved from an audio perspective.
 
And unlike some of you I have experienced the opposite where checking the efficiency cores actually got me over the line in terms of getting a session to play correctly. (it was a very heavily loaded up session) But it took the right combination of buffer settings and DP settings to achieve it. Something that some of you are not prepared to try it seems. Using the small CPU window in Activity Monitor is good for this because its fast in terms of updating what it is showing you. Overall though you should not need it.
 
You must log in or register to reply here.
Back
Top