works fine on mine, single of multiple notes.
-
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.1 - Discussion Thread
- Thread starter Lukas
- Start date
OP
OP
Is it reproducible? Does it always happen with the same session, plug-ins, and notes? If so, and if it’s a Studio Pro bug rather than a plug-in issue, please report it here in the forum (as a separate thread). In that case, it can most likely be ironed out easily.
You’ve seen the long list of bug fixes in this maintenance update. At the same time, the update was released extremely quickly (after two weeks instead of the usual 4-6 weeks for maintenance updates). Due to issues such as the automation rendering problem, there was a certain urgency. It’s therefore obvious that not all issues could be addressed yet.
The mute behavior - while I agree that it can be confusing - is clearly not a showstopper in my view, such as a crash or an issue with audible impact. That said, there will certainly be further updates on this topic. It just wasn’t addressed in this update.
SpongeBob
New member
Ah, thank you Lukas, that's the answer I was expecting and hoping for
I totally agree with you that there are more pressing issues to deal with, and I appreciate the long list of improvements made in the latest update.
In fact, since I've already migrated to FSP for good, I needed this information to know whether or not I needed to adapt my workflow, which relies heavily on mute management.
All the best!
Crescendo
New member
To me it was reproducible. On a Kontakt 8.8 (MacOS 15.7.3, Mac Pro 7,1) instrument track - interesting thing is that nothing played when it crashed. I simply moved a MIDI note in the MIDI editor an octave lower with the key command. For that no communication to the instrument/plugin would occur I presume that would trigger any function within the plugin. S1 quit. No crash log.
I restarted - did the same operation and the same crash occurred. Enough for me to back off at least for now.
It might need some additional testing to be able to document it better which I do not have the time for at the moment. I am in a project and I can't have crashes now. So I will continue on 7 for the time being. Therefore I am simply reporting my experience. Perhaps I can re-visit it at a later time.
I've installed the update and the latency compensation with sidechains is still not fully functional. But wasn't also addressed in the release notes. Would love to see some kind of official list of known issues. 
this would give some feedback if an issue is on the list for further fixing.
this would give some feedback if an issue is on the list for further fixing. 
Luny
New member
Hi.
The problem with the plug-in graphics has not been fixed!!!
I wrote to the support service for the second time!
Good luck to all!
Timo
New member
Am I misunderstanding something if I think that a frozen track consisting of multiple events should reproduce the events exactly as I hear them in real time, including all automation?But there was no mention of a bug here. He just misunderstood the freeze function a little. But if you find an audio-related bug that hasn't been addressed or mentioned yet, I'm all ears.
Number6
Active member
Bandybum
New member
Nice
madFloyd
Active member
I think we know that the probability of that was very high.
You can always choose to use v7 until the minor issues get sorted out. The great thing about Studio Pro is that it supports multiple versions on your PC.
Number6
Active member
Look up agile development. The method is "release early, release often".
If you want the least amount of hassle, do not install until a major point release happens, e.g. when 8.1.0 arrives, and then install the previously released version. Never install a major point release version without expecting bugs, which may or may not effect you.
Yes you can install multiple versions of Studio One (in case you run into trouble and want to revert, or just test it) but you need to be careful backing up your songs and projects as they may not be backwards compatible after being opened and saved in new versions.
Last edited:
You could also publish public betas for that purpose and release the product when it is reliable.
CodonAgitat
New member
"Celemony Tonalic Essential bundle version added " Where do i find that?
TimC340
Active member
Good plan. If you’re working across versions, it may be worth putting a clue to that in the song save title: ‘song_for_number6_v7’.
In your Fender account under additional products you can find the key and follow the instructions to register it. Than you can install it from the tonalic website and it adds itself to SPro. That's what I did.
Number6
Active member
Again, look up "agile development" which is pretty much the method all software developers use for consumer software.
And beta feedback may be useful, but it is overrated, I've never seen a beta test that hasn't ironed out all critical bugs, and many beta testers don't bother to report them, hence agile development philosophy, we are all beta testers now, but it can be avoided if you are fussy about what versions you install (as explained earlier).
Crossinger
Active member
I may be wrong, but from what I've heard, Bitwig has had good experiences with its long public betas.
Midiboy
Active member
I'm not going to say for who, but I do beta test work for a pretty popular plug-in company, and they do a GREAT job. The Beta community is very active, attentive and catches a LOT of bugs. We have a discord setup for it, and it works really well.