-
Hi and welcome to the Studio One User Forum!
Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!
Fender Studio Pro 8.0.2 - Discussion Thread
- Thread starter Lukas
- Start date
Number6
Active member
That's a debate rabbit hole, rather than me or others respond here, I suggest a discussion on a new thread or point us to your existing thread so it can be discussed.
A clear YES or NO, Just facts are enough.
Number6
Active member
It's not that simple. Without you showing steps to reproduce and exactly what your issue is, what you click on, how you click on it etc, in specific and a lot more detail, a clear answer cannot be given. Just telling us that you have issues with the browser is not enough info if you want me or others to try to reproduce your issue. I don't see any issues myself but then I might be doing something completely different to what you are doing, and I'm not going to test until you precisely show me what the issue is.
Hence my strong recommendation is to start a new thread rather than have a discussion about it here and derail this thread (I know from experience of posting on threads like this one myself and sending others on a wild goose chase).
The other alternative is to wait for the demo to come out and test it yourself (release date TBC).
Last edited:
OP
OP
Which issue? "CPU spikes" couldn't be more generic - in a DAW that usually hosts several 3rd party plug-ins.
Please create a new thread as mentioned above and provide some more details.
Number6
Active member
If anybody has an Atom SQ (and even if you don't), please vote!
(This is workaround whereby we are able to see button labels clearly on the atom, currently that is NOT the case a lot of the time).
Also we can't see functionality that is toggled On or Off.
feedback-software.fender.com
(This is workaround whereby we are able to see button labels clearly on the atom, currently that is NOT the case a lot of the time).
Also we can't see functionality that is toggled On or Off.
Can't see Atom SQ user buttons properly - Have user defined labels as a workaround | Hardware Integration / Remote Control | Fender Studio Pro
The image (see image attached below) shows the ATOM SQ and some user defined buttons. 3 three buttons listed are to do with record mode (see monitor above): Replace, Takes to layer...
feedback-software.fender.com
Last edited:
Vocalpoint
Well-known member
While I could simply answer yes or no - the "fact" that you are still using v6 - is irrelevant as that version is now retired.
What we could really use is a comprehensive set of "facts" about your system (from OS to hardware and all things in-between) AND what exactly you are doing when you see "spikes".
As suggested - breaking this out into a new thread with steps to reproduce - would make this a whole lot easier to track
VP
the spikes, when using the s1 browser, is a long time reported bug, heck the tickt is still open, I don't go over it again in here.
Back to my question:
Anyone still get theses spikes in version 8 when browsing stuff in the s1 browser while playback? *please*
If not no need to spam the thread, thanks
Back to my question:
Anyone still get theses spikes in version 8 when browsing stuff in the s1 browser while playback? *please*
If not no need to spam the thread, thanks
Vocalpoint
Well-known member
No.
But then again - I have never seen spikes with any version of S1 to this point (since 2011)
VP
Number6
Active member
As stated earlier no, but you aren't supplying any decent information to repro.
We are not support either. We are just users here, contact Fender support if you want an update on your ticket, we have no idea about it.
Back to my answer.
Everybody here is asking you nicely to start a new thread with the specifics rather than piggy back on this one (Ten posts have been created here already about your issue which we have no real idea about).
Please do that or wait for the demo (or contact support).
BTW here in a good example (please do not post on this thread):
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
Last edited:
Number6
Active member
I've created a new thread for you and posted a video:
Plugin speed differences depending on whereabout the UI you click
Have they fixed the bug where, when opening any plugin window through the mixer or inspector, it opens with about a half-second delay? But when adding a plugin either through the channel overview or by clicking the track number, it opens instantly, as it should? This was posted on another...
studiooneforum.com
Please go ahead and regard this as your thread.
Anyone have issue with tempo automation if the time signature beat duration is dotted?
For example if the time signature is 6/8 with a 1/4 dotted beat duration I'm getting various bugs in the tempo track. Not being able to consistently create or edit tempo automation - sometimes it simply won't let me. Or not being able to select multiple tempo automation points.
Only happens if the beat duration is dotted.
SP 8.0.2
Win 10.
EDIT - I've just checked this on my mac and it's the same. Looks like a genuine bug to me.
For example if the time signature is 6/8 with a 1/4 dotted beat duration I'm getting various bugs in the tempo track. Not being able to consistently create or edit tempo automation - sometimes it simply won't let me. Or not being able to select multiple tempo automation points.
Only happens if the beat duration is dotted.
SP 8.0.2
Win 10.
EDIT - I've just checked this on my mac and it's the same. Looks like a genuine bug to me.
Last edited:
Gary Shepherd
Member
Had a funny thing where the update re-installed some of the soundsets under a Fender shared folder and then gave me a nag message everytime I opened SP8 and said they were duplicates. Soundsets were Deep Flight One, Sub Zero Bass, and Lead Architect. Had to move them from the Fender shared folder to the Soundset Folder. Seemed to work but why this happened is strange - seems again something linked to the name change.
Number6
Active member
Cannot repro but then I haven't reinstalled.
However it did lead to another issue, posted a separate thread:
Sound set paths, can't remove
In Pro Studio 8.0.2, menu: Studio Pro ->Locations Soundsets. I have one question and one issue. QUESTION What's the difference between the "Studio Pro" and "All Applications" path? PROBLEM I was able to remove folder location by clicking on the button and pressing remove, but I can't remove...
studiooneforum.com
carlosjuvandes
New member
Ops, this bug still persistARA / fades bug resolved
It cuts the audio when the fade is on (using Melodyne on ARA)
Last edited:
Nothing to do with audio interfaces. This is reported by several users, me included, and for sure we don’t have the same hardware.
It’s probably a hard fix requiring getting into the playback/recording engine code, that would be my guess on why they don’t touch it but it’s a fundamental thing in a recroding/playback enviroment. Plugin delay compensation is expected to work fully in this day and age otherwise don’t list it as a feature because it doesn’t work well. It may be a hard fix but other DAW’s have it nailed.
I REALLY want a setting to disable the micro-view thing. It just annoys me…
Number6
Active member
This is definitely a reproducible bug, I just need one person to say aye with 8.0.2 and an appropriate controller and I'll create a ticket.
studiooneforum.com
Controllers don't arm correct tracks when using folders
This is an issue since the beginning of time it seems, and I can reproduce this issue in 8.0.2 Windows (unfortunately!). If somebody could try to repro this with any Faderport or Mackie or Atom SQ (Song Button -> Page 2 - Rec) that would be great - thx! Here are the steps to repro: Create say...
studiooneforum.com
Last edited:
Hmm, I'm not quite sure, that this is a very hard fix because of the following: you can hack your way through this if you add the latency at the target position. And in every (hopefully) other case the latency gets compensated well, even in very complex routing scenarios.
Plugins report their internal latency needed for processing to the host, the host takes the latency, adds it up during the chain, distributes it to the routing and ensures that you end up at a summing stage with the correct timing. Which of course can look complicated in complex scenarios but in the end it's a more or less linear process where you work your way through the several summing stages. The only thing that matters is, that the data gets written at the correct position in the output stream.
And, most of the time when nowadays something goes wrong it's because the plugin does not report it correctly and the DAW is lost with a faulty information. And I don't want to blame plugin developers, but I know some examples where this happened.
But not here...There is a good chance, that it is the "simple" case that the latency just don't get reported through this specific situation, and, as I've written, the latency gets compensated, if you add it at the reciever stage. In the best case, there is simply a "0" where a value should be. Of course without knowing the code. But that's where I would take a first look
Anyway, if I've ever wanted to take care about this myself, I would still work with older PT versions.
