7 posts
Page 1 of 1
Hey all,

Just adding this here so it can been seen and fixed if devs haven't seen it already...
https://forums.presonus.com/viewtopic.php?p=209033#p209033

If you look in the 4.5.2 discussion thread me and another guy have found the same issue...

I've had "Shift +s" mapped to Solo track for about 4 years as I wanted PT similar key commands and to match the "Shift +M" = Mute track function that was existing in S1 already...

Now in the latest 4.5.2 update, the Shift + S now Solo safes a track and there is no way to get it to work how it used to..

Would love to have this bug fixed as its a pretty important one for me and something I use thousands of times a day.

Thanks

Producer/writer
Mac Pro 5,1 - OSX 10.11.6 - Studio One v4 - Apogee Symphony - SSL Sigma - Cranesong Avocet - Faderport 1 - Console One
User avatar
by Nip on Thu Jul 18, 2019 11:03 pm
Only way to Solo Safe I know of - is holding mouse in console a little longer.
Quick click - just solo.

You are sure you make key command short enough, not to make repeat?
Some keyboard drivers start repeating really quick.

*** Windows 7 Pro * i7-860 2.8 Ghz 16 GB ram * RME HDSP 9632+AI4S+Audient ASP 800 * GT730 ***
User avatar
by Robdp on Thu Jul 18, 2019 11:10 pm
Nip wroteOnly way to Solo Safe I know of - is holding mouse in console a little longer.
Quick click - just solo.

You are sure you make key command short enough, not to make repeat?
Some keyboard drivers start repeating really quick.


Not sure I understand what you mean?

Producer/writer
Mac Pro 5,1 - OSX 10.11.6 - Studio One v4 - Apogee Symphony - SSL Sigma - Cranesong Avocet - Faderport 1 - Console One
User avatar
by Nip on Thu Jul 18, 2019 11:17 pm
If possibly a repeat of command would interpret as a long press of button.
It should toggle - but odd to repeat a toggle with maybe 10 Hz.

Just a wild guess....

It takes just a second to hold with mouse -. then solo safe activates, instead of solo.

I'll try to reproduce next time at daw...

EDIT - I can confirm - if reassigning shift+S to solo - it does solo safe instead.
If default S command - it works.

So seems it is implied that shift + the solo feature - do solo safe.


I would not call it a bug - since solo safe does not have it's own key command - but would be nice for everybody if it did.

*** Windows 7 Pro * i7-860 2.8 Ghz 16 GB ram * RME HDSP 9632+AI4S+Audient ASP 800 * GT730 ***
User avatar
by Bbd on Fri Jul 19, 2019 6:47 am
FYI, this issue has been reported.

Bbd

Please add your specs to your SIGNATURE.
Search the STUDIO ONE 4 ONLINE MANUAL. Access your MY.PRESONUS account.
OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET.
Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce.


OS: Win 10 x64 Home, Studio One Pro 4.x, Notion 6, Series III 24, Studio 192, Haswell CPU: i7 4790k @ 4.4GHz, RAM: 16GB, Faderport 8/16, Central Station +, PreSonus Sceptre S6, Eris 3.5, ELAC Sub, ATOM
User avatar
by Robdp on Wed Aug 21, 2019 5:55 pm
Any idea when this one is gonna be fixed????

Producer/writer
Mac Pro 5,1 - OSX 10.11.6 - Studio One v4 - Apogee Symphony - SSL Sigma - Cranesong Avocet - Faderport 1 - Console One
User avatar
by robertgray3 on Wed Aug 21, 2019 6:20 pm
Robdp wroteAny idea when this one is gonna be fixed????


Considering they typically group multiple bug fixes and incremental features in each minor update, probably somewhere within 1-3 months.

The only time I’ve seen them release a very fast update to fix a bug was when there were major bugs that impeded a very large group from using ge software, such as the recent offline plugin authorization timeout issue.

Mac OS X Mojave 10.14.4
Mac Pro (Late 2013)
3 GHz 8-Core Intel Xeon E5
32 GB 1066 MHz DDR3
Dual AMD FirePro D500 3072 MB
Quantum 2

7 posts
Page 1 of 1

Who is online

Users browsing this forum: No registered users and 10 guests