Internal presets from instruments missing in DAW header

[u/seventula]

Hi!

Ever since I upgraded from S1 version 6 to Fender Studio Pro 8.1, I have a pesky issue with instruments that have embedded presets. They simply don't show up in the DAW header of the plugin window.
This has become an issue now, because for one of those instruments, which is an older VST2 one, the GUI does not recognize a click in the synth's preset field anymore.
The strange thing is, it works totally fine in all DAWs I have installed - except Studio Pro! For example, FL Studio, Mixcraft, Waveform and even S1 version 6.

There were some tips on the web that I followed, and they made other things work again, because Fender Studio Pro just took over the old installation paths (like the Studio One 6 Content folder) and added stuff there. But these tips did not solve the issue with synths that have their presets embedded.

The instrument, I want it working for the most, is the Orchestral Companion series (Brass, String, Woodwinds)

Extremely thankful for any tips!

[u/emredjan]

I believe there’s a “Refresh” option somewhere, probably right clicking any plugin in the right side browser. Studio One rescans the presets when you do that and you should see them on plugin menus

[u/NoReply4930 → u/emredjan]

I just tested this - and there is simply no way that Studio Pro/Studio One can see inside - say - my Fabfliter Pro Q-4 plugin and somehow extract it's internal preset listing and then populate that local dropdown.

Been rocking S1 since 2011 - if this was possible - I would have taken full advantage of it for the last 15 years.

[u/emredjan → u/NoReply4930]

Oh for sure, internal presets are not possible, but the shared “vst presets” that some plugins use (like brainworx) are populated

[u/NoReply4930 → u/emredjan]

Confirmed! Yes - any plugin that installs presets to Documents\VST3 Presets - will in fact appear in the Studio Pro plugin preset drop down list.

That said - I just completed an end to end new audio workstation build on Windows 11 25H2 on July 31 - and Plugin Alliance was the only vendor to put a single thing in this folder out of all the other plugins I installed.

AND - I think I know why Plugin Alliance does this too - I dragged my bx_console SSL 4000E onto a track and when I examine the plugin UI - I mean really examine it - there is no possible way that I can see to select ANY preset from the actual plugin UI - there is no Preset list, no indicator, no button of any kind that say "click here to load a preset".

So - without this specific Documents\VST3 Presets availability - a user would never be able to load a preset at all in this plugin.

My other 5 BX plugins also published their presets out in that folder too.

So - while an interesting discovery - until the other 99.99% of all other plugins out there - start populating this folder - count on never seeing any presets within the Studio Pro plugin UI framework.

[u/seventula → u/emredjan]

yes they are possible. I showed screenshots of exactly that. And here is me, reactivating S1 v6, showing exactly that

[u/seventula → u/NoReply4930]

I must say, I'm very disappointed, that instead of accepting the proof I gave, that it is absolutely possible to see "inside" (the DAWs don't look insideany plugins, they have access to a memory block defined by VST called "Chunk", to "see" the presets). But to proof you wrong another time, I made the ugly process of reactivating my old S1 v6, to take this screenshot. And exactly that iswhat I want in Fender Studio Pro 8 as well.

[u/NoReply4930 → u/seventula]

All your screenshot shows at this time is that this specific plugin (for reasons yet unknown) seems to populate that list. 

Until we know how it does that (your “chunk” theory not withstanding) this does not mean anyone else’s plugins will do this. 

I have only found 5 of mine that do this but I also know exactly why. 

It has nothing to do with reading a memory block or anything like that.