Fender Studio Pro 8.2 - Discussion Thread

[MisterE]

Here's a crazy concept: Give users a choice.

You have the same freedom of choice as I do, as in I'm still on v6. No one put a gun to your head to be an early adopter of v8.2. And as Lucas has written and demonstrated many times, you can have as many versions of S1/FSP available as you want simultaneously if you install the various versions the way he clearly shows in his videos. I've also been around virtually forever, starting with V2. There are some directional choices Fender makes I'm not at all fond of. That said, as I'm not a full time engineer constantly tackling new projects for clients who request latest and greatest features, there's not a single feature that's been added in 7 or 8 that's a difference maker in how my songs are going to turn out, because the writing and performances are always going to be where it's at in the end. Sure someone on 7 or 8 might get there marginally faster than I will, or be able to set up shortcuts that will expedite workflow for future projects, but there is an infinitesmal amount of listeners who care or could possibly tell if a song was created in 6, 7, or 8.

I know the choice you were talking about concerns the way developers implement new ways of working, that you want them to not only implement these changes, but give someone like yourself the chance to choose between the old way or working and the new way—which would make their task exponentially more difficult. That must be a realistic ask for you. You might be on an island with that viewpoint, though. But other choices are available for long term users as well...

 

[Vocalpoint]

What a spectacular way to destroy years of trust and goodwill.

What a spectacular way to crash onto the forums with such a lucid and upbeat first post.

If you don't like the product - that's fair. But a quick reality check - no one forced you buy anything or upgrade anything.

Many other solid choices out there.

VP

 

[Crossinger]

Many other solid choices out there.

The weakest argument in a discussion: If you don't like it here, then just go somewhere else!

 

[Sebastian Holtzer]

No, not at all.

But the performance was much better. It's still slow motion here. I don't know what's wrong but the daw is still laggy as hell. You can't work with it anymore as bigger as a project becomes. Even if you freeze. Something with multicores must be broken. Changing buffer size doesn't help a lot. 7.2.3 was fine with performance 8.2 is not.

 

[sintil8]

The tragedy here is that this release also contains >50 bug fixes, which is a ridiculously high number anyway, given that we are in a stable branch 10 months after initial release.

Often upon reading the bug fix list there are fixes for a number of issues I never knew existed, or ever experienced.
Maybe my use of SO/FSP is not as intensive or as deep as other user's, but the Dev team are finding them and working through them, so as far as tragedies go it's more work for the Dev's.

IMHO. Bit of a thankless job snagging errant code, the demographic of user's and system diversity and keeping folk satisfied with innovation and new trends, a hard road to travel. The best we can do on this forum is to call bugs out when we find them. That requires a structure to replicate and confirmation to move forward.

@Ken Morgan raised a question about not needing more silicon, advancements in tech is driving a system of redundancy. That is where we are.
Y'all gotta keep up kind of headache.

If you find a Ver. that gives you everything you need, stick with it is a good maxim.

Just thinking aloud about some of the things I see.

Kindest regards to all.

 

[Crossinger]

This discussion isn't just about bugs, crashes, or reproducibility. I've been in the software testing business for 20 years and know its mechanisms. No software is perfect—the grass on the other side of the fence isn't greener.

However, there are two things that have been major concerns for me for years (likely since v5) and are increasingly driving me away from Studio One:

1. Regression bugs. Issues that were once marked as "fixed" in the changelog and then reappear in one of the following versions (sometimes even the next major version) in the same or similar form. Melodyne and Fades is an example. And not just because it may not be 100% reproducible using a checklist. And with this example we address my second point, which is almost more important to me:

2. Trust. I've already written about this in the old forum, which caused frowns and rejection. Yet I stand by it: Reproducible bugs (misbehavior) and crashes are one thing. The other are errors where it works 9 out of 10 times and on the 10th time, an error occurs. Reproducible? Nope. This can lead to data loss (I had to recreate tracks within my song from scratch) or it magically works again after I close and reopen the file. And these events undermine trust: can I rely on a function I use to do what it's supposed to, or does it lead to creeping data corruption of my song project? Openly speaking, I'd rather have an honest crash.

These two issues are absolutely driving me crazy right now with Studio One. And I have to admit: I’m at a loss. Because a simple “Just move on and use DAW x, y, or z” can’t be the answer. And that’s why I now find myself in a somewhat frustrating situation: I’m sticking to Studio One 7 (and am constantly afraid of doing something wrong), trying to wait out the problem, and figuring out how to regain my trust in the software.

 

[wdkbeats]

[BUG REPORT]

Fender Studio Pro 8.2.0 (Windows) does NOT recall UAD plugins settings. Even when you drag a plugin from one track to the next it reverts to default preset. Works fine in version 8.1.2.

 

[sintil8]

@Crossinger

I will keep it short.

I see your concern point 2 coming off point 1 makes sense, and sticking with Ver 7 is a wise decision if that is stable for you.
The creeping project data corruption is something that I have seen and difficult to overcome once it starts, as it's somewhat nebulous as to what caused it in the first place.

As a forum tho' we have little leverage to change the direction that SO/FSP is going. Unless folk are looking to send a mass petition to Fender as a group I do not see how we could have any impact.

Your comment is very valid and an honest crash can be soul destroying and costly if you are making a living from a DAW, so stability becomes prime in such scenarios.

Kindest of regards

 

[Ken Morgan]

For further consideration -

Just a relatively few short years ago, people purchased things (tools, autos, whatever) with the intention of keeping them for a long time. It was pretty unheard of to abandon a tool or whatever as soon as the next model was released.

Nowadays, people will stand in line for days to get the latest iPhone, and trade in their vehicles after 24 months to get the latest model. Far too many DAW users (I've been guilty as well) will upgrade as well, dropping what has worked brilliantly for the very latest release without knowing if it will work better for them or not (or at all?) in their specific need. We just jump on the bandwagon.

This, I believe, is an annoying albeit harmless scenario, for those who dont use DAWs to pay mortgages or feed a family - like me at this stage of life. But it can be an expensive error for those who do, the same people who don't spend any time on these forums. Those at that level of output tend to stick with what works for them, regardless of what platform, what release version, and so on. If it works, it works, and don't fool around with it.

 

[BobF]

[BUG REPORT]

Fender Studio Pro 8.2.0 (Windows) does NOT recall UAD plugins settings. Even when you drag a plugin from one track to the next it reverts to default preset. Works fine in version 8.1.2.

Create the simplest song that demonstrates this and file a report with Fender support. If you're looking for repeatability from other forum members, create a separate post specifically for the problem you are experiencing. This gives your post the greatest visibility.

 

[Stuart Welwood]

Create the simplest song that demonstrates this and file a report with Fender support. If you're looking for repeatability from other forum members, create a separate post specifically for the problem you are experiencing...

As a retired software developer, this is music to my ears. The coder may even sing your praises out loud!

 

[sintil8]

For further consideration -

Just a relatively few short years ago, people purchased things (tools, autos, whatever) with the intention of keeping them for a long time. It was pretty unheard of to abandon a tool or whatever as soon as the next model was released.

Nowadays, people will stand in line for days to get the latest iPhone, and trade in their vehicles after 24 months to get the latest model. Far too many DAW users (I've been guilty as well) will upgrade as well, dropping what has worked brilliantly for the very latest release without knowing if it will work better for them or not (or at all?) in their specific need. We just jump on the bandwagon.

This, I believe, is an annoying albeit harmless scenario, for those who dont use DAWs to pay mortgages or feed a family - like me at this stage of life. But it can be an expensive error for those who do, the same people who don't spend any time on these forums. Those at that level of output tend to stick with what works for them, regardless of what platform, what release version, and so on. If it works, it works, and don't fool around with it.

Computer tech is a stranger in this, how many times have you heard "no longer supported", following advancement in Chip design, Ram, HD tech, all becoming more advanced. Software also... Windows incarnations, Mac flavours and updates. Can all be seen as driving this need for the latest.
That's my take on inbuilt redundancy being pushed by tech advancing.

I do agree, that these days there is a societal element we all have of wanting the latest and greatest, I suppose the human condition is not perfect.
So be it.

I am retired now and after selling off some vintage gear have funded a system that will hopefully see me until I drop.
For my sins, I do not stand in any line for the latest iphone or gadget, but I do like new tech GAS is my addiction if I'm being honest.

Anyway kindest regards

 

[Ken Morgan]

Indeed computer tech is a stranger to longevity, sadly. Earlier this evening I found out why.

Cannot use StudioPro, ProTools, or Logic without an active internet…perhaps if Fender would take the leap forward and come up with some way to license specific machines instead of the phone home, it would help put them over the top?

My electricity is ALWAYS more reliable than my internet

 

[IndigoBeatz]

I just reverted to the previous version , i was having problems with looong loading times with my projects.And had a couple of crashes ... much more that i ever had previous.

I normally dont go back but i just reverted back , and bam .. it loads as quick as it ever did

 

[sintil8]

Indeed computer tech is a stranger to longevity, sadly. Earlier this evening I found out why.

Cannot use StudioPro, ProTools, or Logic without an active internet…perhaps if Fender would take the leap forward and come up with some way to license specific machines instead of the phone home, it would help put them over the top?

My electricity is ALWAYS more reliable than my internet

Ken
I don't know your system and I could be way off base and wrong about this, but have a Google for, "Fender studio pro offline authorisation" the license file should install to your machine?

It's been I while since I did it but it used to be for folk that run bare bones systems with no internet connected. Some Vsts have similar arrangements Spectrasonics Omni being one I know of.

Kindest regards

PS... On reading again myself, Pro+ subscription cannot do this, after 3 days; if offline for more than 3 days, access pauses until reconnected, and membership verification occurs every 30 days.

Well I never knew that, go figure.