Plugin on disabled track remains disabled when track enabled

[parityflux]

I have an issue where:
- a Studio One 6 or 7 .song that has disabled tracks is loaded into Fender Studio Pro 8
- the track is then re-enabled
- the plugin on the track remains disabled (in my case it is ProEQ3 on every track); I didn't have any test cases with different plugins, or multiple plugins
- there is no discernable way to re-enable it: right-click 'enable" does nothing.
- instances of ProEQ3 on other tracks that were already enabled work fine (enabling and disabling the track results in proper function and maintenance of state)
- plugin nap (globally or per effect) does not affect this issue

I can drag an instance of ProEQ3 onto the existing one to replace it, or I can add a new instance to the track. However, the existing eq setting is lost as expected.

Has anyone experienced something like this?

Best,
John

 

[parityflux]

I was able to re-create the issue by creating a new song in S7, adding two unique Mai Tai instrument tracks, adding a ProEQ3 with a custom preset to each, and disabling one of the Mai Tai tracks. Opened in FSP8 and same issue. That file went over to support this morning. I will let ya know if and when it is resolved.

Also, and I would love to know if this happened to anyone else, but: I had not touched S7 since installing FSP8. FSP8 was uninstalled/reinstalled once trying to resolve the OP issue. I opened S7 and it had reverted to a default state as if I had never run it before. It registered me automatically and then took its sweet time scanning all of my plugins and all of my settings are gone, including my devices, which is really odd because they are/were stored in AppData\Roaming\PreSonus... I don't really plan to go back to S7, but man, this was unexpected nastiness. I am 100% sure S7 wasn't touched since the last time I used it.

 

[Vocalpoint]

Also, and I would love to know if this happened to anyone else, but: I had not touched S7 since installing FSP8. FSP8 was uninstalled/reinstalled once trying to resolve the OP issue. I opened S7 and it had reverted to a default state as if I had never run it before.

Never seen that here - but I make 100% sure I install a new version into a very specific "new" location if running in parallel.

And I am certain that no settings are shared between versions.

That said - I have seen reports here and there like your describe - one minute an older version is cool as can be and then the next - it's like it was being run for the first time.

I HAVE experienced super annoying "rollbacks" with one specific area thru the v5->v6 era and v6->v7 era and that was with my UI customizations file - where you can have specific elements showing (or not showing) based on your session templates.

Back when I "added" v7 (in parallel) to a long running v6 install - I distinctly remember opening V7 for the first time and instead of "bringing forward" ALL my v6 settings (like was always being promoted) my customization files were ruined and set back to default - IN both v6 and v7. Luckily I had backups - so it easily fixed - but yes if you were to ask me if the Presonus/Fender install routines are actually bulletproof - I would still say no.

Not sure what it is going to take - but I backup ALL my settings now - before each and every "update" be it major or minor.

VP

 

[Vocalpoint]

I take it all back - just got hit this 5 seconds ago....

VP

 

[parityflux]

I take it all back - just got hit this 5 seconds ago....

VP

Heard, and ... sorry.

I wish the file system was both tighter, and more flexible. I think it can be both.

-j

 

[parityflux]

Forum question: the posted issue is going to the devs and there is nothing else I can do at the moment. Do I mark this as "solved" or wait until it is actually fixed in a released sometime in the future? My inclination is to wait, since it is not actually solved at this time.
-j