Fender Studio Pro 8.0.2 - Discussion Thread

[madFloyd]

No delay for me ....

 

[Number6]

Updated! It seems that it really isn't the case for everyone, but as I wrote above - I saw this in FSP8 reviews on YouTube and was very surprised. At the same time, everything opens as it should through the channel overview, so it doesn't seem to be an issue with the plugins or the system.

Well you are running Windows 10 so that's the OS out the way. Anyway create a ticket and maybe create a new thread with clear steps to repro. There is obviously some sort of condition, maybe it's hardware spec too (unlikely but possible, and no I'm not talking about just speed of hardware, could be display card/drivers or whatever).

 

[DoTheBeat]

Well you are running Windows 10 so that's the OS out the way. Anyway create a ticket and maybe create a new thread with clear steps to repro. There is obviously some sort of condition, maybe it's hardware spec too (unlikely but possible, and no I'm not talking about just speed of hardware, could be display card/drivers or whatever).

Why do these same plugins open instantly through the channel overview then?

 

[Number6]

Why do these same plugins open instantly through the channel overview then?

No idea. Ask support.

 

[carlosjuvandes]

Any issue about clicks after bouncing? I had some bounces with clicks and on v7.2.2 didn't happen..

 

[sintil8]

Installed yesterday. All running OK, so no complaints from me on the update.
I see it as a good sign when threads like this run without a flood of new issues and problems.

I still can't get used to Ari not popping up with the announcments tho'. No critisicm Lukas, it's just different after all the years.
Best of regards to the guys in the kitchen...

 

[FMN-Music]

Why do these same plugins open instantly through the channel overview then?

Could it be that in the mixer and in the inspector, FSP has to wait after the first click for the (very very unlikely) case that you wanted to open the Micro Edit crap with the second click, so that the plugin gui does not open prematurely?
This waiting time then might be dependent on the system's double-click speed setting.

 

[Vocalpoint]

In this thread also already confirmed this bug. It's just that with my workflow, it's very noticeable, and this made me give up on the 8.

Well to be clear - if it's truly an actual "bug" (IN the software) - there is a very high likelihood that it would happen to all of us.

Selective "issues" in the field is not necessarily any cause for a fix - for now - it simply means there is something different with your rig vs those of us who are not seeing issues. What that is - is unknown at this point.

Also Fender cannot test for every possible combination of hardware in the field. You (and others) may simply have the right combo of "things" that is causing this "delay". Hopefully we can pin it down - but if this ends up being your graphics card driver or a Discord session running on your rig WHILE using Studio One or any number of other infinite possibilities - there is nothing to fix until the cause is found.

For example - your graphics card dates to Nov 2018. Not that this is an issue by itself - but there a very strong chance that this card - would never (ever) be tested with Studio One v8. And if that's the case - how do we know this is not your cause? Just because you have been rocking an 8 year old card for 8 years - does not mean it's optimized for SP8

The fact that many of us are seeing nothing and some of you are seeing something - it makes it an investigation and troubleshooting session first and (possibly) an actual bug - way down the line.

VP

 

[Number6]

Well to be clear - if it's truly an actual "bug" (IN the software) - there is a very high likelihood that it would happen to all of us.

Selective "issues" in the field is not necessarily any cause for a fix - for now - it simply means there is something different with your rig vs those of us who are not seeing issues. What that is - is unknown at this point.

Also Fender cannot test for every possible combination of hardware in the field. You (and others) may simply have the right combo of "things" that is causing this "delay". Hopefully we can pin it down - but if this ends up being your graphics card driver or a Discord session running on your rig WHILE using Studio One or any number of other infinite possibilities - there is nothing to fix until the cause is found.

For example - your graphics card dates to Nov 2018. Not that this is an issue by itself - but there a very strong chance that this card - would never (ever) be tested with Studio One v8. And if that's the case - how do we know this is not your cause? Just because you have been rocking an 8 year old card for 8 years - does not mean it's optimized for SP8

The fact that many of us are seeing nothing and some of you are seeing something - it makes it an investigation and troubleshooting session first and (possibly) an actual bug - way down the line.

VP

As I stated earlier I managed to reproduce it too, so it's a real issue (that clearly doesn't effect everybody), although this really does not effect my workflow. BTW there are plenty of bugs that don't effect all users, so I'm not sure how we can jump to any conclusion like that (and besides, we don't have the code in front of us).

In retrospect I very much doubt it's the graphics card, as it's faster in one area of the UI but not the other. Again though, I don't have the code so of course I'm speculating like everybody else.

I would also just try to get this issue reproduced with as many of us as possible, and ignore all the other conjecture from us forum users as though we are part of a fantasy developer team. So talk to Fender and get a dedicated thread running with clear steps to repro, and see if we can find more steps to repro, or hardware similarities.

 

[Vocalpoint]

In retrospect I very much doubt it's the graphics card, as it's faster in one area of the UI but not the other.

But until you know - you do not know. Which would involve testing this card (and potentially many others)

So talk to Fender and get a dedicated thread running with clear steps to repro, and see if we can find more steps to repro, or hardware similarities.

Have you submitted a ticket? That's the official start. For any item to actually get to DEV - it needs to arrive via the proper channels.

While this thread is fine to discuss a potential issue - hacking away out here on a forum that has no connection to Fender whatsoever and has no DEV eyes on it whatsoever - won't get Fender involved if that's the real end game.

VP

 

[Number6]

In retrospect I very much doubt it's the graphics card, as it's faster in one area of the UI but not the other.

But until you know - you do not know. Which would involve testing this card (and potentially many others)

Well when you quoted me, you appear to have edited out the next comment. So here it is:

Again though, I don't have the code so of course I'm speculating like everybody else.

So I don't know why you bring up what I already stated. And I already said he should create a new thread so we can do comparisons.

If we have the same graphics card or some other hardware, maybe, just maybe that's an issue worth investigating. Otherwise testing random stuff is just like throwing balls in the air with your eyes closed and hoping it goes through the hoop.

Have you submitted a ticket? That's the official start. For any item to actually get to DEV - it needs to arrive via the proper channels.

I did not bring up this issue and I've already stated it doesn't effect my workflow. I've got other issues here to deal with which is taking a load of my time. I've said it a few times he needs to create a ticket so I'm not sure why you are asking me this question.

While this thread is fine to discuss a potential issue - hacking away out here on a forum that has no connection to Fender whatsoever and has no DEV eyes on it whatsoever - won't get Fender involved if that's the real end game.

Creating a thread to see if we can find extra steps and hardware similarities is not a waste of time, and that info can be submitted to support.

It's already been stated before that Fender does not monitor these forums not sure why it needs to be mentioned yet again.

 

[Vocalpoint]

I did not bring up this issue and I've already stated it doesn't effect my workflow. I've got other issues here to deal with which is taking a load of my time.

Fair enough.

A suggestion here would be this one should be broken out into it's own thread as trying to keep tabs on who started what is this long winding v8.02 discussion can be frustrating.

Maybe the mods can help out.

VP

 

[Number6]

Fair enough.

A suggestion here would be this one should be broken out into it's own thread as trying to keep tabs on who started what is this long winding v8.02 discussion can be frustrating.

Maybe the mods can help out.

VP

Yup..

 

[FMN-Music]

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

This is how you can reduce the lag when opening up plugin gui's.

 

[BobF]

Yup..

Too time consuming to undo messes. Much easier for everyone if the threads are started stand-alone. The release thread is getting old anyway.

 

[Funksta]

This is like "within a few ns" for me. The plugin appears instantly.

VP

NS is probably the better answer to be honest. It's almost instant unlike it was after the first change round waiting for anything to open after your click. Like you It's fine my end no matter were I open them unless ofc it's a plugin issue, they don't always open instantly. Kontakt used to be a pig around V7 for example but that was there fault.

 

[Funksta]

For me, creating an instrument track and clicking on the plugin on that track, the first time it takes a second or two for me depending on how resource heavy the plugin is. Then it gets cached into memory, and when I try to open again using the same method it's nearly instant.

"But when it’s opened from the mixer or the inspector, there’s a delay"

Trying this afterwards... yup there is a delay of about a second compared to opening it on the track. The difference is quite noticeable although it's hardly a workflow killer.

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

This is how you can reduce the lag when opening up plugin gui's.

Man I love Fircomp It's free now isn't it.

 

[Number6]

FSP8 - total crash - can anyone repro please

I can recreate a crash where FSP8.0.2 disappears completely, can anyone reproduce please - you will need Fat Channel with the Tube comp. Newly opened FSP 8.0.2 (I'm on MacOS 15.7.4 on MBP M1 Max) New blank session - 32 bit at 96KHz New mono audio track Open the Channel Overview (bottom right...

studiooneforum.com

 

[carlosjuvandes]

Undo command is broken sometimes. Does someone could check that, please?

 

[Lukas]

Undo command is broken sometimes. Does someone could check that, please?

Way more details needed.