Hello,
I’m using Fender Studio Pro 8 on a Mac mini M1 running macOS Tahoe 26.2. By now, I’ve encountered the second very strange bug, both of which I was able to fix using the same workaround. I’d mainly like to understand how this can be explained and where I should start looking for the root cause.
Issue 1:
When switching tracks, the channel strip in the Inspector is not updated and still refers to the previously selected track. Additionally, once this happens, it is no longer possible to show the channel strip again. This seems to occur primarily on instrument tracks.
Issue 2:
When I have several chord events next to each other in the Chord Track and open the drop-down menu on one of those chord events, FSP simply crashes without any error message.
Both issues occur only sporadically, and they happen both in sessions originally created in FSP and in songs that were started in Studio One Pro 7.
In both cases, the issues can be reliably fixed by opening a new empty session and fully importing the session data. I don’t see any data loss afterward.
Could this point to a hardware issue (all my data is stored on external M.2 SSDs)?
Or is it more likely that these are still bugs in newer FSP features that start to appear as sessions grow larger?
I’m using Fender Studio Pro 8 on a Mac mini M1 running macOS Tahoe 26.2. By now, I’ve encountered the second very strange bug, both of which I was able to fix using the same workaround. I’d mainly like to understand how this can be explained and where I should start looking for the root cause.
Issue 1:
When switching tracks, the channel strip in the Inspector is not updated and still refers to the previously selected track. Additionally, once this happens, it is no longer possible to show the channel strip again. This seems to occur primarily on instrument tracks.
Issue 2:
When I have several chord events next to each other in the Chord Track and open the drop-down menu on one of those chord events, FSP simply crashes without any error message.
Both issues occur only sporadically, and they happen both in sessions originally created in FSP and in songs that were started in Studio One Pro 7.
In both cases, the issues can be reliably fixed by opening a new empty session and fully importing the session data. I don’t see any data loss afterward.
Could this point to a hardware issue (all my data is stored on external M.2 SSDs)?
Or is it more likely that these are still bugs in newer FSP features that start to appear as sessions grow larger?