• 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!

Studio Pro 8 - Discussion Thread

On the topic of Double Precision Processing:

If you'd agree, that 16 Bit audio processing precision is superior to 8 Bit, then why would you not think, that 64 Bit is superior to 32 Bit?

Despite the fact, that my productions and mixes usually suffer from far greater problems than Processing-Bit-Depth, I'd still rather have double precision turned on, as the degregation of audio quality per digital signal process (which includes even just a gain change) is supposedly further minimized.

And I kinda don't get the undertone argument, that if I do not use a feature, or think it is unneccessary, that it is ok, if it does not work or crashes the app... because ist's the other people's own fault for even thinking about wanting to use this feature.
 
Last edited:
For sure, I agree!

I'm in this rabbit hole now of tweaking/optimizing my workflow for efficiency...something I started in December pre-release of Studio Pro. Now having to make some adjustments. On the plus side, I enjoy this stuff and am learning a bunch (I mean, that's why I'm on the forum!)..on the other hand, it's cut a bit into time I would otherwise be making music, or I've been getting sidetracked!

All the best!

I'm getting familiar with Ver8 but mostly using Ver7, when I feel comfortable with my graps of V8 then I will move up.
Plus I'm picking my way through what folk are discovering and any issues others are throwing out on here. The forum is a valuable learning tool.

Best regards
 
On the topic of Double Precision Processing:

If you'd agree, that 16 Bit audio processing precision is superior to 8 Bit, then why would you not think, that 64 Bit is superior to 32 Bit?

Despite the fact, that my productions and mixes usually suffer from far greater problems than Processing-Bit-Depth, I'd still rather have double precision turned on, as the degregation of audio quality per digital signal process (which includes even just a gain change) is supposedly further minimized.

And I kinda don't get the undertone argument, that if I do not use a feature, or think it is unneccessary, that it is ok, if it does not work or crashes the app... because ist's the other people's own fault for even thinking about wanting to use this feature.
Pro's and con's. Have a look at this thread for some thoughts on the matter. If double precision is indeed more taxing to your system then at some point you may have to choose between number of tracks (or amount of processing) or keeping everything at double precision. As long as your system is fine then carry on! :)
 
Pro's and con's. Have a look at this thread for some thoughts on the matter. If double precision is indeed more taxing to your system then at some point you may have to choose between number of tracks (or amount of processing) or keeping everything at double precision. As long as your system is fine then carry on! :)
Fair point.
CPU tax is a factor to be considered.
 
Did a quick CPU Tax Test and could not find any disandvantages of using double precision. Test was made in v7.2.3 where double precision still worked.

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
 

sintil8

I don't have this button and menu, am I missing something?
Studio_Pro_0zR0FQKppi.png
 
update ..find it ....
Studio_Pro_Tk2yPFmgeW.png
 
but now you have to make a bunch of clicks, then find this VST instrument (and if there are a lot of them with the same name, the task becomes even more complicated).
The free Navigation Essentials from Lukas has an option „Apply track names to instruments”. This could help, especially when using many instances of the same plugin.

 
I checked it now.
Automation is working.
Created a wave file.
All the automation that was in the project has been preserved.
Yeah, this is actually a known issue. Many times the automation does NOT work after mixing down to a rendered file. Works great in the DAW, until you render. In many times, freezing the track before mixdown works, but that sometimes the automation doesn't work after freezing as well. So no, it doesn't work all the time. More times than not, it does not. It's been verified countless times, and Fender is aware of it and is already working on a fix.
 
Yeah, this is actually a known issue. Many times the automation does NOT work after mixing down to a rendered file. Works great in the DAW, until you render. In many times, freezing the track before mixdown works, but that sometimes the automation doesn't work after freezing as well. So no, it doesn't work all the time. More times than not, it does not. It's been verified countless times, and Fender is aware of it and is already working on a fix.

Hi.
Of course I checked after the render!
The Wave format.
The MP3 format works too!

The program is not ready for professional work yet!!!
Stable version of Studio One 7.

Good luck!!!
 
I agree its just a bit much to take in at first. The free plugin gifts are really good, its awesome they started improving Impact/Sample1 immediately, the amp sims are best in class and if they quickly fix the bugs I guess its really cool they put so much effort into continuing S1. This must of been a crazy project and if Fender has the money to really fix some of the PDC bugs with S1 I am all for it. I am a little surprised they went with Fender studio rather than S1 Fender but what do I know about branding.
Hello to all forum participants! I am a new user of Fender Studio Pro, but I am not new to audio recording. I am a long-time user of Digital Performer and currently use Reaper. I have purchased a license and am familiar with the program. Could you please clarify what problems arise with PDC and how I can test them in practice with Fender Studio Pro? This is very important to me, as I work with multi-microphone recording, etc. Does this apply to certain plugins, or is it a global problem with S1? Thank you.


Translated with DeepL.com (free version)
 
Hi.
Of course I checked after the render!
The Wave format.
The MP3 format works too!

The program is not ready for professional work yet!!!
Stable version of Studio One 7.

Good luck!!!
It appears to depend on the ASIO buffer size and dropout protection settings. When I set buffer size to max (2048 with my Quantum HD8) and disable dropout protection, automation renders. With lower buffer size (currently working at 32) and dropout protection enabled, it doesn't. What are your settings?
 
It appears to depend on the ASIO buffer size and dropout protection settings. When I set buffer size to max (2048 with my Quantum HD8) and disable dropout protection, automation renders. With lower buffer size (currently working at 32) and dropout protection enabled, it doesn't. What are your settings?
I set the following values ASIO Buffer 32 , Sample Rate 44.1 KHz
My usual setup ASIO Buffer 256
Sound cart AUDIENT ID 14 II

Wait for the program fixes.
It's still raw.
The program is not ready for serious work right now!
 
When using the freeze function on a track, the sample automation is not at all sample-accurate. This becomes apparent quickly if, for example, you have filtered an audio event (e.g., with the stock Pro EQ, even with a gentle curve just before the event); in the frozen version, you can clearly hear that the automation kicks in too late.

All other methods like mixdown selection are working.
 
Hello to all forum participants! I am a new user of Fender Studio Pro, but I am not new to audio recording. I am a long-time user of Digital Performer and currently use Reaper. I have purchased a license and am familiar with the program. Could you please clarify what problems arise with PDC and how I can test them in practice with Fender Studio Pro? This is very important to me, as I work with multi-microphone recording, etc. Does this apply to certain plugins, or is it a global problem with S1? Thank you.


Translated with DeepL.com (free version)
Because information of the various Plugin Delay Compensation Issues are scattered around this forum and not easy to find, I compiled them into one post:
 
It appears to depend on the ASIO buffer size and dropout protection settings. When I set buffer size to max (2048 with my Quantum HD8) and disable dropout protection, automation renders. With lower buffer size (currently working at 32) and dropout protection enabled, it doesn't. What are your settings?
For me, changing buffer size and/or dropout protection settings does not resolve automation rendering issues.
 
Because information of the various Plugin Delay Compensation Issues are scattered around this forum and not easy to find, I compiled them into one post:
Thank you very much!
 
For me, changing buffer size and/or dropout protection settings does not resolve automation rendering issues.
Same. Doesn't help me at all. I was hopeful when I read this, but then alas., disappointment settled in. lol. I know they'll fix it though.
 
Back
Top