TimC340
Well-known member
I'm not running any version of Visual Studio on this computer. And never have.
-
Hi and welcome to the Studio One & Studio Pro User Forum!
Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by Fender. Learn more in the Welcome thread!
Fender Studio Pro 8.2 - Discussion Thread
- Thread starter Lukas
- Start date
OutrageProductions
Active member
Keep us informed pls.
CTRL/SHIFT/ESC restart Explorer is my workaround for now.
Last edited:
TimC340
Well-known member
I just checked UC (my version is up to date) and all of a sudden it can't see the PreSonus 26c interface that I use on this computer, saying "The service required to connect to your devices is no longer available". Not sure if this is related, but the interface is working fine as the default sound source . There is Something Afoot!! Two tickets in one evening - I think that's a record for me!
Last edited:
OutrageProductions
Active member
Check that you don't have at least a version of <Microsoft Visual C++ Redistributable> in your <Programs and Features> CPL. I know for a fact that Universal Control and Adobe Acrobat won't run without it.
TimC340
Well-known member
Yes, I have v14.51 of C++ Redist.
OutrageProductions
Active member
Same here. Seems we have discovered an issue that started with SP v8.12 and persists. I don't have any issues with a session that DOES NOT contain any Kontakt/KK instances (at least so far). Still testing.
My SP will close completely, but the program icon persists in the task bar, I lose the ability to RMB on the task bar to launch Task Manager, and have to either CAD or CSE to open it.
I can restart the largest instance of Explorer in task manager (even with SP open & running) to regain Task Bar function, seemingly with no ill effects. This one has puzzled me for a while, and seems to have manifested itself with Windows Security updates from 9/12/26 in my case. [KB5126052, KB5124008, and KB5129195]
My research led me to believe that something in the background is not releasing the RAM associated with certain plugins (NI in my system). Still working on a solution.
I don't think that it is specific to SP as much as Win interaction with NI plugs, Cubase does the same thing.
Last edited:
I'm not seeing this on MacOS 27.
Kell9
New member
Feels good on Mac. Works stable with a bunch of Synchron Players and Kontakt Players as well – no crashing or freezing and closes normal ...
Gary Shepherd
Active member
The Dim Solo is excellent.
The new Stem Separation is not that great. Guitars cut out in places and are still mixed in with the Other stem. Bass, Drums, Vocals still okay as before, but the new separations of Guitars and Piano are not that great and need refining. I don't use it that much but even so ......
The new Stem Separation is not that great. Guitars cut out in places and are still mixed in with the Other stem. Bass, Drums, Vocals still okay as before, but the new separations of Guitars and Piano are not that great and need refining. I don't use it that much but even so ......
Vocalpoint
Well-known member
Thanks for the update. I believe we have a Windows issue here.
Update for the crew. Working with Fender support - I was asked to strip the entire Settings directory back to almost empty and restart FSP to let it create another baseline.
Even after all that - stripping SP back to just the license key and the Extensions folder - and then starting a clean new session and adding Kontakt, then Zebra2 and then Mai Tai - messing around for a bit and exiting - Studio Pro.exe still remained in memory.
Support asked me to roll back to v8.12 but that is not in the cards - at least for now.
So - a favor to ask - if you have NOT yet installed v8.20 - and still have v8.12 and are running on Windows 11 25H2/26H2 AND have Kontakt 8.13 on board - if you can do some quick "clean" session testing and add an instance of Kontakt 8 then maybe a Mai Tai and maybe something like Zebra 2 or whatever your usual go-to synths are - mess around in the new session - exit out of the session without saving it and when you return to the Start Page - check Task Manager. It will show in the top tier as running. Then bounce out of SP8 by clicking the "X" and then check Task Manager again.
This time you will need to scroll down to the programs list (to the "S" area) and tell us if FSP is still running.
VP
Does anyone know if stem separation is Fender developed or a third party app? The reason I ask is the stem separation in UA Luna is from Moises and it has the same issues described here.
Vocalpoint
Well-known member
I think there are only two companies out there writing these things - and then they license that tech to everyone else.
Very likely that the big player in this space - zPlane - handles this for Studio Pro 8:
VP
8.2 is running without any issues on my M4 MBP, macOS 27.0.1. It's a lean machine, with just HALion 7.x and EZ Drummer as the primary sound sources with a few Steinberg instruments installed but not used. I'll report back on the M1 which is the main music-making machine.
Last edited:
Vocalpoint
Well-known member
Update...
I decided to restore a full sys image and rolled right back to v8.12 - just as it was before this mornings update.
Opened a blank session - added the usual suspects - Kontakt 8, then Mai Tai and finally Zebra2 - messed about, removed each of the them in reverse order so the session was the same as it was when first reopened.
Closed the session back to Start. Examined Studio Pro.exe in Task Manager and then finally clicked the "X" to exit Studio Pro.
Low and behold - Studio Pro v8.12 is exhibiting the same oddball behavior - still running in the background. (see attachment)
Apparently - I have had an issue for longer than this new update. More to come...
Update 2: Not only does this instance of Studio Pro stay in memory - if I start another new session, add either Komplete Kontrol OR Kontakt 8 itself - this specific session - when closed - will join the other one already in memory.
Can also confirm now - without any doubt that this condition needs Kontakt 8 (v8.1.3) to be in the session for the issue to manifest.
Will now hit up NI and see what they know..
VP
I decided to restore a full sys image and rolled right back to v8.12 - just as it was before this mornings update.
Opened a blank session - added the usual suspects - Kontakt 8, then Mai Tai and finally Zebra2 - messed about, removed each of the them in reverse order so the session was the same as it was when first reopened.
Closed the session back to Start. Examined Studio Pro.exe in Task Manager and then finally clicked the "X" to exit Studio Pro.
Low and behold - Studio Pro v8.12 is exhibiting the same oddball behavior - still running in the background. (see attachment)
Apparently - I have had an issue for longer than this new update. More to come...
Update 2: Not only does this instance of Studio Pro stay in memory - if I start another new session, add either Komplete Kontrol OR Kontakt 8 itself - this specific session - when closed - will join the other one already in memory.
Can also confirm now - without any doubt that this condition needs Kontakt 8 (v8.1.3) to be in the session for the issue to manifest.
Will now hit up NI and see what they know..
VP
Last edited:
On a similar note, since apparently we'll never know beforehand whether Fender is working with Native Instruments on developing deep integration, can any great minds on this forum tell me exactly what competitive advantage Fender gained by not revealing they were ramping up MIDI 2 until now? Please correct me if my thinking is way off, but by not announcing it, couldn't that only result in driving potential customers to other DAWs who did announce it in advance? How exactly did maintaining this level of secrecy invite a single person to buy the program?Now if we could just get that Native Instruments Komplete Kontrol v2 Firmware integration....tap...tap...tap
VP
TimC340
Well-known member
Yes, I can do that in the morning.
Vocalpoint
Well-known member
You and I have had our moments discussing this at length - but I stand by my original tact.
MIDI 2.0 is simply not a thing until the hardware catches up. Which will be years from now.
It is a moot point for anyone to care whether MIDI 2 is there (or not) when deciding if Studio Pro is for them.
And make no mistake - there are no "other" DAWs out there who are even close to have this working either. From the 8 or 9 threads I have seen in the last 6 months - It's a crap shoot everytime some decides to flip that MIDI 2 switch - usually in Logic - just to see everything come tumbling down - especially when paired with Komplete Kontrol hardware.
Even the lead manager on Komplete Kontrol surfaces on the NI forums every so often telling users to not bother with MIDI 2 - for a long while.
VP
Vocalpoint
Well-known member
Tim
Thank you but no real need now for you to test.
I tested on my v8.12 build (after sys restore) - same behavior is present for me - Studio Pro.exe is hanging when Komplete Kontrol OR Kontakt 8 is introduced into a session.
It appears this has nothing to do with SP v8.1.2 or v8.2.0. Also confirmed Studio Pro.exe exits cleanly from any session that does not use KK or Kontakt 8.
This is looking more and more like an NI problem. Have reached out to them for comment.
And I am frankly stunned I did not notice at all since mid August when Kontakt 8.13 dropped...
VP