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

Fender Studio Pro 8.0.2 - Discussion Thread

Maybe your keyboard is on its way out.
Or needs cleaning or dodgy connection.

Scan for viruses too. Some apps also record keystrokes.
 
v8 has been very stable for me. My entire setup is so stable and workflows working that I almost never want to update anything again :p
 
Or batteries!

I think used wireless for about a week..I'm sticking with my 25 year old Dell wired keyboard.
 
I think used wireless for about a week..I'm sticking with my 25 year old Dell wired keyboard.
I use wired keyboards also (2) but not sure about Stuart (OP).
 
I use wired keyboards also (2) but not sure about Stuart (OP).
I use a Logitech MX Keys S wireless keyboard. It doesn't seem to be at fault here, as the entry was wiped out in the SP8 Keyboard Options. I reset it to undo. No other programs have been affected. Bizarre.
 
Another incident of odd behavior with FP8 just happened. I was working on the stems extracted from an old recording that I made when the solo buttons on the FaderPort 16 just stopped working. They did nothing. Same with the solo buttons in the Console view. Both buttons were synced together, but zilch, zip, nada when it came to any action. After restarting FP8, they now work normally.
 
I use a Logitech MX Keys S wireless keyboard. It doesn't seem to be at fault here, as the entry was wiped out in the SP8 Keyboard Options. I reset it to undo. No other programs have been affected. Bizarre.
Yep that's strange. Have not seen anything remotely like that in FSP however. Unlikely it could be a keyboard issue. My vast technical skill tells me it's either ghosts or gremlins (🙂 which is to say sorry - got nuthin')
 
Have
Another incident of odd behavior with FP8 just happened. I was working on the stems extracted from an old recording that I made when the solo buttons on the FaderPort 16 just stopped working. They did nothing. Same with the solo buttons in the Console view. Both buttons were synced together, but zilch, zip, nada when it came to any action. After restarting FP8, they now work normally.
Maybe if this is happening with some regularity, running a project with the faderport out would point to a hardware issue there (by omission).(?)
 
It happened again. This time it's the Q key that was assigned to quantize by default. I cleared it, only because I tend to hit it by accident when editing with Melodyne, which uses the 1 through 6 keys as tool selection shortcuts. It came back by itself. I wonder if it has something to do with the coordination of the shortcuts between the Melodyne plugin and SP8.
 
Last edited:
Fender Bender 8.03 seems to be out. For download on the account page. However, update function within the DAW does not work, there is also no news feed anymore. Obviously some snafu at the moment. Curious about a changelog.
 
Curious about a changelog.
You can always access the release notes here: https://s1toolbox.com/releasenotes/

...or in this thread:

 
Fender Bender 8.03 seems to be out. For download on the account page. However, update function within the DAW does not work, there is also no news feed anymore. Obviously some snafu at the moment. Curious about a changelog.

I can't check but you may want to temp disable your firewall and try again, then re-enable. If that works update your firewall rules.
 
Fender Bender 8.03 seems to be out. For download on the account page. However, update function within the DAW does not work, there is also no news feed anymore. Obviously some snafu at the moment. Curious about a changelog.

Just updated mine from within the app. The news feed is working fine. The only bit that doesn't work on mine is the display of my 'artist profile' - it's blank. But it's been like that since v7.1, so I've given up caring about it!
 
Fender Bender 8.03 seems to be out. For download on the account page. However, update function within the DAW does not work, there is also no news feed anymore. Obviously some snafu at the moment.
The update seemed to stall for me, too. Then a few minutes later I found an installer dialog box was behind the other windows. It worked.
 
I do find dialogue popup windows (in Windows) end up in odd places especially with dual monitor/multi resolution situations/dragging stuff around. Somebody at Fender needs to do a full QA on popup windows, where they end up and how they interact with other windows. It's one of the weaker areas and it's a bit annoying. Help window/search as most people know often stops responding if other popup windows are showing.
 
I do find dialogue popup windows (in Windows) end up in odd places especially with dual monitor/multi resolution situations/dragging stuff around. Somebody at Fender needs to do a full QA on popup windows, where they end up and how they interact with other windows. It's one of the weaker areas and it's a bit annoying. Help window/search as most people know often stops responding if other popup windows are showing.
I believe this is due to the modal nature of the windows being used.

Windows dialog boxes, which default to modal mode, are serviced by a different event loop than the main window. Modal mode is when a dialog box prevents the user from interacting with other windows. This is done by the OS preventing any messages other than those that request to paint the window, and a few other special types, to get through to the windows behind the dialog box. A separate event loop is created by the OS to process the dialog box's event queue. It is the this event loop that allows the user to fully interact with the dialog box's window.

As far as solutions, it certainly depends on the specific coding, but my guess is that they range from simply changing some base classes, and dealing with the aftermath, to hacking into the event queue. I had to do this once to fix a very busy window that could not be made to draw its controls in the desired order. Using the Windows API PEEK and POKE functions in a Windows hook function, I changed the order of the paint messages in the event queue.
 
I believe this is due to the modal nature of the windows being used.

Windows dialog boxes, which default to modal mode, are serviced by a different event loop than the main window. Modal mode is when a dialog box prevents the user from interacting with other windows. This is done by the OS preventing any messages other than those that request to paint the window, and a few other special types, to get through to the windows behind the dialog box. A separate event loop is created by the OS to process the dialog box's event queue. It is the this event loop that allows the user to fully interact with the dialog box's window.

As far as solutions, it certainly depends on the specific coding, but my guess is that they range from simply changing some base classes, and dealing with the aftermath, to hacking into the event queue. I had to do this once to fix a very busy window that could not be made to draw its controls in the desired order. Using the Windows API PEEK and POKE functions in a Windows hook function, I changed the order of the paint messages in the event queue.

There are lots of Windows in Windows ;)

Overlapped Window.
Pop-up Window.
Child Window.
Layered Window.
Message only window.

And
Parent/child relationships.
Owner and Owned windows

There are issues here in Studio Pro and their screen positioning.
 
Last edited:
Back
Top