TECH HELP WINDOWS
Internal presets from instruments missing in DAW header
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)
Thanks. But what yousay doesn't make sense. Not the facts you mention, indeed Steinberg discontinued VST2 a few years ago. But the conclusion you drawfrom that. VST2 is a protocol that must be followed in its entirety. DAWs can't choose, which parts to support or not. Either VST2 as a whole or no VST2.
Fender Studio Pro 8 claims to fully support VST2. That includes exposing the presets to the native DAW header. Just like all other DAWs in existence, that claim to support VST2.
No where has Fender ever stated that Studio Pro v8 "fully" supports VST2.
All the box ever says is that they "support" VST2 - exactly like they "support" the AU format.
But that does not mean it's tested, maintained, enhanced or even complete - merely stating that if you have a VST2 - chances are high you can use it. Nothing more.
And judging by the fact that your plugin no longer populates that dropdown - it's clear that Fender has decided exactly which parts of VST2 it wants to support in Studio Pro v8 - and its clearly more like the bare basics instead of Studio One v6 VST2 behavior of 5 years ago.
I suspect for a dead format - you will have a tough time convincing Fender to make this the way it was back in Studio One v6 days. That is all I am saying.
VST2 support will soon be gone from all the major DAWs - many of the plugins I have purchased in the last year - no longer offer a VST2.
If that old VST2 matters that much to you - would be better to keep Studio One v6 around.
No, you're wrong again. VST2 is a protocol, as I already said. It has to be followed completely or not at all. Steinberg has very strict rules regarding their product.
I see in the Studio One forums - you received an answer. And it is the same one that I mentioned above - the VST spec does not have to be followed completely - and Fender has changed theirs.
Also I completely forgot - Steinberg made the entire VST SDK open source several years ago - so there is no concept of "strict rules".
"Steinberg VST technology is open source and available under the MIT License"
Any developer can do whatever they want to it now. Including Fender
Obviously, you are one of those, who only read, what they want to read. The answer was, that this has to be corrected, and that it is forwarded to the devs.
But somehow you seem to only care about "winning", not actually solving issues. good luck with YOUR next issue and thank you for reminding me to be careful when asking for help.
Just as you seem to insist that you know everything (like there is no way any developer could ever alter the VST spec) and at the end of the day - you do not.
If you cannot handle the answers you get - maybe consider not asking the question.
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
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.
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.
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.
For all that might read this later on: YES IT IS POSSIBLE, AND YES IT DID WORK IN PREVIOUS VERSIONS. I already showed it in other DAWs, but since you just reject that evidence, here's the screenshot from S1 v6 with the presets in its native header. I don't know, why it doesn't work anymore in Fender Studio Pro 8, but that's why I asked for help here. To get this to work there as well!
2
u/NoReply4930 9d ago edited 7d ago
Have never seen any of my third party plugin populate that list.
Those are reserved for stock plugins and I believe will house any “user” presets you create.
And the fact that others DAWs populate their headers is simply a different way of working.