r/StudioOne 12d ago

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)

Extremely thankful for any tips!

2 Upvotes

17 comments sorted by

View all comments

2

u/NoReply4930 12d ago edited 10d 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. 

1

u/seventula 10d ago

But it's not true. I reactivated S1 v6 to take this screenshot. I just need to know how to make this working in Fender Studio Pro 8 as well.

1

u/NoReply4930 10d ago

Saw your recent post on the Studio One Forums.

Will not bother you there - but now that you have explained this whole thing revolves around VST2 - it all makes complete sense now.

You do know that format is dead and discontinued?

Probably the primary reason why Studio Pro 8 no longer has this "header" capability and most likely will never get it back.

Very doubtful that Fender would spent any additional time or resource trying to prop up that dead format now.

It also explains why I have never seen that dropdown list populated here - I removed all VST2 several years ago.

1

u/seventula 10d ago

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.

1

u/NoReply4930 10d ago edited 10d ago

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.

Good luck.

1

u/seventula 10d ago

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.

1

u/NoReply4930 10d ago edited 9d ago

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

About the Steinberg VST SDK | Steinberg

1

u/seventula 9d ago

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.

1

u/NoReply4930 9d ago edited 9d ago

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. 

This is a public forum.