• 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 One 7.1 - Discussion Thread

Now that we have the Transform to rendered audio through the bus will this render any mix fx plugins?
This is important to me as well. I like how the MixFX plugins sound, however, the way they just don't render apart from the whole mixdown export makes them unusable to me, since I'm required to provide proper stems. If the bus transform finally respects the MixFx plugins, it would be a viable way to use them again.

Furthermore, is the bug still around where it always bounces a stereo file when you try to bounce a mono track?
 
This is important to me as well. I like how the MixFX plugins sound, however, the way they just don't render apart from the whole mixdown export makes them unusable to me, since I'm required to provide proper stems. If the bus transform finally respects the MixFx plugins, it would be a viable way to use them again.

Furthermore, is the bug still around where it always bounces a stereo file when you try to bounce a mono track?
MixFX does get rendered in bus transform. MixFX affects many other tracks, but in bus transform, every track affected is forced to use that bus. Otherwise bus transform is blocked.
 
This is really not a good workaround - especially if one has made a ton of specific settings and has yet to back them up.

Just confirmed the Loops tab is all good here - but I am running perpetual - so this must be a issue with a subscription license

VP

If you look in the old settings folder you'll see files with very common sense names like userkeyscheme, usercolorcheme, PluginPresentation, RecentDocuments, etc. Just close Studio One and copy them back,
 
MixFX does get rendered in bus transform. MixFX affects many other tracks, but in bus transform, every track affected is forced to use that bus. Otherwise bus transform is blocked.
What exactly is 'MixFX'? I initially assumed it was whatever plugins you have on the bus (or its tracks) but now I'm wondering if its something different.
 
What exactly is 'MixFX'?

Mix Engine FX is a PreSonus technology. Mix Engine FX (or short: Mix FX) integrate directly into the mix engine, allowing it to process each channel within a bus before they are summed. Unlike regular insert effects, which only affect the final mix signal, Mix Engine FX has control over individual tracks inside the bus, enabling realistic analog-style interactions like crosstalk, saturation, and compression across multiple channels.

This makes it completely different from standard FX plugins.
 

Mix Engine FX is a PreSonus technology. Mix Engine FX (or short: Mix FX) integrate directly into the mix engine, allowing it to process each channel within a bus before they are summed. Unlike regular insert effects, which only affect the final mix signal, Mix Engine FX has control over individual tracks inside the bus, enabling realistic analog-style interactions like crosstalk, saturation, and compression across multiple channels.

This makes it completely different from standard FX plugins.
Thank you, Lukas.

I can't believe I didn't know of this feature, especially since the MixFX pulldown menu is just above the inserts.

Very cool.
 
If you look in the old settings folder you'll see files with very common sense names like userkeyscheme, usercolorcheme, PluginPresentation, RecentDocuments, etc. Just close Studio One and copy them back,

Well - I have done about a two week study on all these files when I built my DIY Studio One backup routine about a year ago (that mimics the "official" Backup that is part of Pro+) and some of these files - if copied at the wrong time - will make you crazy and potentially cause S1 to act strange when you least expect it.

And - for any user (which is about 99.998% of us) who have no idea what these are, where they are and what the implications of messing with them are - best to have Presonus make this work correctly so no user should need to be fishing around hacking system files.

VP
 
The most important thing is to communicate openly when something doesnt work.
Not really...
It's more important to let the developers know by submitting a Support Ticket (see link in my Signature) and include the steps to reproduce the issue.
 
Well - I have done about a two week study on all these files when I built my DIY Studio One backup routine about a year ago (that mimics the "official" Backup that is part of Pro+) and some of these files - if copied at the wrong time - will make you crazy and potentially cause S1 to act strange when you least expect it.

And - for any user (which is about 99.998% of us) who have no idea what these are, where they are and what the implications of messing with them are - best to have Presonus make this work correctly so no user should need to be fishing around hacking system files.

VP
You make it sound as if these files are some voodoo kind hocus pocus deamons which are best left alone. They are just the files where the settings are stored. And what do you mean with "when copied at the wrong time"? Just only ever touch them when S1 is closed. And keep a copy of the folder when all is running fine. Update the backup when changes are made/plug-ins are added/updated. Normal file behavior stuff IMO.
 
  • Like
Reactions: AAV
You make it sound as if these files are some voodoo kind hocus pocus deamons which are best left alone. They are just the files where the settings are stored. And what do you mean with "when copied at the wrong time"? Just only ever touch them when S1 is closed. And keep a copy of the folder when all is running fine. Update the backup when changes are made/plug-ins are added/updated. Normal file behavior stuff IMO.
Do what you gotta do.

VP
 
Do you guys not use the backup/restore feature in S1? It is so great... I run it once a week or so and all my settings, presets, i/o configurations, customizations, etc. are saved on my cloud account, all in one place, with one click. You can selectively backup/restore categories of elements, even.

Finding where user-defined data is saved and making backups (or transferring to other machines) was always a pain with DAWs. Try to figure out where all of that stuff is saved by Cubase, I dare you... ;)

S1 makes it so convenient now. A small feature for sure, but It's the small things in life you treasure most...
 
Do you guys not use the backup/restore feature in S1? It is so great... I run it once a week or so and all my settings, presets, i/o configurations, customizations, etc. are saved on my cloud account, all in one place, with one click. You can selectively backup/restore categories of elements, even.
Backup/Restore is not available to non-subscription licensees. So I had to build my own :)

VP
 
Do you guys not use the backup/restore feature in S1? It is so great... I run it once a week or so and all my settings, presets, i/o configurations, customizations, etc. are saved on my cloud account, all in one place, with one click. You can selectively backup/restore categories of elements, even.

Finding where user-defined data is saved and making backups (or transferring to other machines) was always a pain with DAWs. Try to figure out where all of that stuff is saved by Cubase, I dare you... ;)

S1 makes it so convenient now. A small feature for sure, but It's the small things in life you treasure most...

Whenever I think I 'know' Studio One, I learn I don't. I'll have to look for that feature!
 
Whenever I think I 'know' Studio One, I learn I don't. I'll have to look for that feature!
Just note what I posted above. If you are perpetual - this is a no go.

VP
 
Backup/Restore is not available to non-subscription licensees. So I had to build my own :)

VP

Oh, I did not realize that, sorry! I have the subscription which comes with the cloud storage, so I guess that makes sense. Well... I am way OCD about backups of my precious shortcuts and settings, not to mention the fact that my templates are made of large collections of presets. This cloud backup/restore is a big plus for me.

BTW I think the subscription is a fantastic deal regardless - I pay annually and it averages out to around one lunch at Subway per month for all of the PreSonus catalog and updates, the subscription content and the cloud services. The "workspaces" alone have become a central part of how I work with collaborators now. And it all tastes MUCH better than a lunch at Subway!
 
They also didn't mention that 7.1 doesn't make me a schnitzel and a coffee.

Not really...
It's more important to let the developers know by submitting a Support Ticket (see link in my Signature) and include the steps to reproduce the issue.
For what reason does this "discussion thread" actually exist? On my last bug report, you asked for a video, and when I took the extra time to make one and post it, you simply ignored it. You keep repeating yourself and trying to convince me how to report a bug. Thanks for your help, but I've known how to report bugs since Studio One 3. I'm basically here to discuss things that aren't working in order to potentially find a solution that helps. But I notice that, unfortunately, this doesn't sit well with you.
 
Back
Top