Fender Studio Pro 8 Released

[heliacal]

I think this is called procrastination...

[jamcat]

Since I get those failures with VST3s as well, I guess I will just write this one off for the time being.

Did you have ChatGPT analyze your crash log?

[SeeingInMidi]

did they remove the copy/paste plugin state buttons, or am i blind?

[thievedletter]

did they remove the copy/paste plugin state buttons, or am i blind?

Check for a Cogwheel, or downwards arrow top right of the plugin window. For some reason there are two levels to open now, for controller and other stuff. I really don't like, or understand this change. Just more clicks for no reason.

[bk]

Everything else sounds like Stockholm syndrome to me.

Since I get those failures with VST3s as well, I guess I will just write this one off for the time being.

I'll leave you to your "DAW" of choice now.
Enjoy.

Yeah. You're a real peach, and we're all deluded that FSP8 works for us.
Before the Stockholm comment, I was gonna say I was sorry it didn't work for you, but now, good riddance. Don't let the door hit you on the way out...

BTW, I've been running FSP8 since it launched without a SINGLE crash. Tons of plugins. VST2, VST3. Whatever, doesn't matter. It must be my imagination.

[J Veronica]

Deleted

[Vocalpoint Studios]

I open it… and it crashes.

Hold SHIFT - and then double click to start the program. You are now in Diagnostic mode.

Here you can disable all plugs. Gather logs - all sorts of cool things to determine exactly what your issue is. Almost a 100% guarantee - it will be a plugin.

Find out which one - then report it. And then - for the meantime - disable it within Plugin Manager and all will be well.

There is nothing wrong with the program.

Takeaway: No vendor out there - including Fender can "program around" a poorly written third party plugin (or plugins)

VP

[jrwaltb]

[Crossinger]

That's too general for me

[EnGee]

I had my 2nd crash with SP8!! It is the same one related to chords track. I insert it and begin to change the chords, then boom!
I will see if I can reproduce it without any plugin loaded! (although I think it is not related to a specific plugin).

[jamcat]

That's too general for me

I think he got a null at render.

[BONES]

Well, when none of my plugins crash in all other DAWs I have but do so in a very weird way constantly (many of them, all high quality plugins) in Studio Pro, I tend to disagree about what the issue is.

Really? I have one or two very specific plugins that will crash Studio One/Pro when I attempt to close a song but Fender/Presonus seem to have done a great job of sorting that out, such that I think the crashes in Pro 8 are down by 80%-90% compared to v7. In the last 3 months or so I reckon I've probably had a dozen or so, when I used to have almost that many a day. It's always predictable, though, and I never lose any work. I have never had Studio One/Pro crash while I've been actively working on anything. OTOH, Cubase used to crash fairly regularly.

Definitely the most unstable DAW I ever used.

What OS are you using? If you're having all those issues and clearly the rest of us aren't, don't you think that maybe the problem isn't the DAW? Which plugins are giving you problems? Maybe we can test and see if it's the same for us?

[BONES]

Presonus/Fender have never acknowledged it as a bug or made a single comment about it.

Have you opened a support ticket or just complained about it on their forum? I find support is really good, up to a point, if you open a ticket. They don't have every plugin in creation to test with but they're quite responsive and they will do their best to help you. Even though I am on the other side of the world, I'll often get two or three responses in a day, which I never get from anyone else.

[BONES]

This is where I'm at (because I'm way past arguing the toss about whether it's audible - it is).

Well that's interesting because you never said that it was audible when I asked you about it, you went into detail about inverting and summing two signals, which led me to assume that was how you realised it was happening.

What I haven't quite got to the bottom of yet is how it affects the final mixdown and I'm still testing that. But it's far more complex and there are far more variables to contend with in a full mixdown.

If the difference is audible, then you should be able to detect it easily in a mixdown, shouldn't you? The rendered mix won't sound the same as the "live" mix in Studio Pro. If you can't detect it, then why worry about it? I understand that just knowing it is there can be annoying but it's also easily ignored if it's not hurting anything.

In terms of whether it matters then it's up there with anti-aliasing, linear phase filters, limiting (particularly high end acceleration type limiting) and things like high end microphones. Some people won't notice those things, some people will notice but not care and some people will notice and care.

That comes down to a matter of taste. If you know it's happening, there has to be a way to compensate for it. I never even think about any of those things when I'm working. It's technical bullshit that only matters when you have a problem with it. i.e. All of those things can contribute to your final sound, they don't have to be problems. What, for example, is the difference between unintentional phasing and doing it deliberately, via detuned oscillators or an effect? It's the kind of thing I would tend to lean into, not try to get rid of. Harder to do with recorded parts but it's the mindset I am trying to illustrate.

I see mixing as a creative process, not a technical one, so I try not to complicate things by looking too deeply at that kind of schizz. If something's not working, I don't always try to fix, I might try to incorporate it if I can, or hide it with a bit of saturation/distortion (it doesn't take much to change the signal enough to fix those kinds of issues) or I'll just dump it and try something else entirely. Again, easier when working entirely ITB but, also again, it's a mindset that lets you get on with things, not get bogged down in minutiae. I suppose it's the old "we'll fix it in post" mentality from my work, where you don't let little problems bog down an expensive film shoot.

I mean it clearly does a lot if your layering a melody with different synths and 1 synth is off / as you said if you parallel mix plugins in you will get comb filtering.

Not unless they are playing exactly the same patch, in which case why layer them, why not just turn it up? If the signals are even slightly different, it won't matter.

Seems like the weirdest bug as they can just put a hard fix in to move it back 1 sample.

I think the problem is that it's not consistent, otherwise everything would be one sample out and it wouldn't matter. It's only a problem when one track is out of time with another.

[BONES]

Not a single crash here only using VST3. Makes Cubase feel like a slug...

It's weird because I used to have all sorts of problems with VST3 in Pro v5 and early versions of v6 but as the minor updates to v6 rolled out, it seemed to shift so that VST3 got better and VST2 got worse. I don't use many VST2 plugins any more (I used to use them to maintain compatibility with Orion) but VST3 support is definitely more robust today. I've only got two or three CLLAP plugins installed and they don't even show up in my plugin list, even though they haven't been quarantined by Plugin Manager. They just don't show up in the Browser.