• 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

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.
This is a user forum. You should report BUGS to Presonus. If you are getting a reply here it's because someone is stepping up of their own volition to help you. In your post above you refer to BUGS that are not bugs at all, so you should probably submit a Feature Request (again to Presonus) if you feel so inclined. Up to you.
 
Please calm down everyone. Yes, this is primarily a discussion and support forum for Studio One users.

@Zikax
With the help of your video (mono event in stereo track in stereo bus) I was able to reproduce the Transform Bus bug. I have forwarded it to Studio One development. Thank you!

For matters that are feature requests and not bugs, please consider the new feature voting platform:

 
Last edited:
Updated today to 7.1, now ALL saved scenes of ALL my projects have disappeared??!
Yes, this is a bug in the recent 7.1 version. Will be fixed with an update soon.

Any way to roll back??
You can just open your previous version of Studio One unless you have overwritten it with the new one. In this case, you need to download and install the previous version (7.0.2) first.

I always suggest not to overwrite new Studio One versions but install them to separate folders.
 
Last edited:
Thanks, I have managed to roll back and my scenes are back.

I now have another problem which started when I upgraded and has persisted with the roll-back: I use a Mackie MCUPro, for which I have modified the device files in C:\Program Files\Presonus\Studio One 7\devices\Mackie\Control.

This has worked fine for many months.

S1 is not now reading the modified files from this location, because I only get the default Mackie behaviour not my modded behaviour.

However, if I delete the entire Mackie folder from the above location then my mods are back. Confused! Where can it be reading the files from?

EDIT: Just to be clear, I copied across my modded files after each install, so it wasn't just a case of the install replacing my files with the default ones.

Thanks again,

M
 
Last edited:
I now have another problem which started when I upgraded and has persisted with the roll-back: I use a Mackie MCUPro, for which I have modified the device files in C:\Program Files\Presonus\Studio One 7\devices\Mackie\Control.

This has worked fine for many months.

S1 is not now reading the modified files from this location, because I only get the default Mackie behaviour not my modded behaviour.

However, if I delete the entire Mackie folder from the above location then my mods are back. Confused! Where can it be reading the files from?

EDIT: Just to be clear, I copied across my modded files after each install, so it wasn't just a case of the install replacing my files with the default ones.

Thanks again,

M
With multiple Studio One instantiations and modifying device files, I'd recommend removing and re-adding the device in Options-External Devices.

External Devices.png
 
How many Studio One 7 instantiations do you have?
You're probably running into Studio One Settings or Registry issues...
 
One only. I have the folders for S1 5 and 6, but they are deacivated as far as I am aware, as I added a '-' to the folder names.

Everything worked fine until I upgraded today.

I did a C drive search for the file names in the Mackie/Control folder. It doesn't appear that they are stored anywhere else.

I really don't get why my modded files still work when they have been deleted.

I will certainly be installing updates to a new folder in future.
 
Did you check for your mods in the Surface Data[1] folder?

Surface Data.png
 
One only. I have the folders for S1 5 and 6, but they are deacivated as far as I am aware, as I added a '-' to the folder names.

Everything worked fine until I upgraded today.

I did a C drive search for the file names in the Mackie/Control folder. It doesn't appear that they are stored anywhere else.

I really don't get why my modded files still work when they have been deleted.

I will certainly be installing updates to a new folder in future.
What do you mean by mods? Presets? Mappings? What exactly.
Reason I ask is I won't be loading 7.1 depending on what this is.
Thanks.
 
What do you mean by mods? Presets? Mappings? What exactly.
Reason I ask is I won't be loading 7.1 depending on what this is.
Thanks.
I modded some of the files in the control folder e.g. mackieshared.js

For example, I changed the flip behaviour so that the faders flip between track volume and input gain. Default flip is between volume and pan, which is of no use for my workflow.

When I bring in a song to mix, I flip the faders and do a rough level mix with input gain so that my faders remain at zero for volume.
 
I see, so it's your Mackie js control file.

Just a thought on your changing gain to maintain faders at zero for volume (unity). Just be very careful as the need to vary volume (in a mix situation), will be far more important varilying your faders, than varying gain. But I believe your point being you have different HUI mix mappings for different setups with various equipment set from your Mackie so I get it. That's a bummer that version 7.1 is causing that. I'm wondering if I will experience similar issues with outboard MIDI equipment (MIDI pachbay, Yamaha automated mixer, etc). So I'm going to hold off until the cookie crumbs are out of the bed.
Thank you for noting and I hope your issue gets fixed very soon. 👍
 
Last edited:
I see, so it's your Mackie js control file.

Just a thought on your changing gain to maintain faders at zero for volume (unity). Just be very careful as the need to vary volume (in a mix situation), will be far more important varilying your faders, than varying gain. But I believe your point being you have different HUI mix mappings for different setups with your Mackie so I get it. That's a bummer that version 7.1 is causing that. I'm wondering if I will experience similar issues with outboard MIDI equipment (MIDI pachbay, Yamaha automated mixer, etc). So I'm going to hold off until the cookie crumbs are out of the bed.
Thank you for noting and I hope your issue gets fixed very soon. 👍
Hi,

I only use input gain at the very start to get a rough level balance, with an eye on the instrument bus and 2-bus meters. After that, fadera are switched to volume for the rest of the mix.

Just to be clear, I don't know for sure that 7.1 caused this. I needed to roll back because of the confirmed scenes bug in 7.1. I followed the same procedure to incorporate my mod files as foe previous upgrades, bit it didn't work this time.

Still don't get why deleting the Mackie control folder fixed it. S1 doesn't rebuild it, so it's simply missing. You can even add new Mackie devices when it isn't there.

Cheers,

Martin
 
Hi,

I only use input gain at the very start to get a rough level balance, with an eye on the instrument bus and 2-bus meters. After that, fadera are switched to volume for the rest of the mix.

Just to be clear, I don't know for sure that 7.1 caused this. I needed to roll back because of the confirmed scenes bug in 7.1. I followed the same procedure to incorporate my mod files as foe previous upgrades, bit it didn't work this time.

Still don't get why deleting the Mackie control folder fixed it. S1 doesn't rebuild it, so it's simply missing. You can even add new Mackie devices when it isn't there.

Cheers,

Martin
I see Martin, and thanks for noting the reason which makes perfect sense. Also that it may not be due to the latest 7.1 update. Much appreciated.
I typically wait on such things, so I'll keep to that for the time being.
Take care,
Lokey
 
I see Martin, and thanks for noting the reason which makes perfect sense. Also that it may not be due to the latest 7.1 update. Much appreciated.
I typically wait on such things, so I'll keep to that for the time being.
Take care,
Lokey
You're welcome, thanks again Lokey
 
Yes, this is a bug in the recent 7.1 version. Will be fixed with an update soon.
Hi! Even though there is this bug about scenes, if I don't have any scenes saved in my songs, can I anyway buy version 7 and update to 7.1 without any problems? Currently on version 6 Windows 10
 
There will always be bugs in every software. As v7 has a separate directory and separate settings, you are safe.
Just make sure to save your v6 songs under a new name, as v7 songs cannot be opened in v6 in case you need to roll back for whatever reason.
 
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.
Your video showed a bug, which is good. But this is a user forum and nobody here can fix it. I was merely a bit sarcastic about your wish of non existing features being mentioned by Presonus, which I find a bit weird. It was meant to be lighthearted, not to upset anyone.
 
  • Like
Reactions: AAV
Back
Top