• 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!

StudioPro 8 and StudioV 2.2.0 broken?

froggo

New member
Studio V 2.2.0 not able to load with ARA in Fender Studio 8.0.0, just displays a panel of no help and that's it!

Anyone else?

Running Windows 11 (up to date)
 
This problem was reported in the Dreamtonics forum for the Beta versions of SynthV 2.2.0

Because of that I have not updated to the Beta’s or the official SynthV 2.2.0 release so I cannot test it with Fender Studio 8; however, I suspect it is the same problem which carried over to the launch version. Strange they would not have fixed this given it was reported in Beta?
 
I believe this is because Dreamtonics uses a "whitelist" approach to allow specific DAW names to use the ARA function, and Studio One is renamed to Studio Pro, which is likely the root of the problem. In fact, the internal name of Studio One/Pro has always been fixed within the ARA standard, so most ARA plugins shouldn't have this issue. I suspect Dreamtonics is using a non-standard method to identify the DAW. Let's wait for future updates.
 
I believe this is because Dreamtonics uses a "whitelist" approach to allow specific DAW names to use the ARA function, and Studio One is renamed to Studio Pro, which is likely the root of the problem. In fact, the internal name of Studio One/Pro has always been fixed within the ARA standard, so most ARA plugins shouldn't have this issue. I suspect Dreamtonics is using a non-standard method to identify the DAW. Let's wait for future updates.
Makes sense.
 
Is this an issue that have to be solved by Dreamtonics or by Fender?
 
Dreamtonics, I think.

I have Synth V 2.2.0 on one setup, but I haven't yet tried it in SP8. It's working fine in SO7. My other rig has SynthV 1.11.2, and again I haven't tried it on SP8; looks like a job for tomorrow as I'm hoping to pick up the new choir bundles for Synth V 2.
 
I believe this is because Dreamtonics uses a "whitelist" approach to allow specific DAW names to use the ARA function, and Studio One is renamed to Studio Pro, which is likely the root of the problem. In fact, the internal name of Studio One/Pro has always been fixed within the ARA standard, so most ARA plugins shouldn't have this issue. I suspect Dreamtonics is using a non-standard method to identify the DAW. Let's wait for future updates.
I posted this on the Synth V forums - but wanted to "close" this here. Aifu is exactly right, and just as an FYI for anyone who doesn't want to wait for a proper fix, renaming the . "Studio Pro.exe" file to "Studio One.exe" allows one to load the ARA version of SV2 2.2 into FSP8.01 for me. Caveat Emptor, etc.
 
I posted this on the Synth V forums - but wanted to "close" this here. Aifu is exactly right, and just as an FYI for anyone who doesn't want to wait for a proper fix, renaming the . "Studio Pro.exe" file to "Studio One.exe" allows one to load the ARA version of SV2 2.2 into FSP8.01 for me. Caveat Emptor, etc.
I tried this, but it totally messed with my file associations and the registry associations in Windows 11--I never could straighten it out.
 
I posted this on the Synth V forums - but wanted to "close" this here. Aifu is exactly right, and just as an FYI for anyone who doesn't want to wait for a proper fix, renaming the . "Studio Pro.exe" file to "Studio One.exe" allows one to load the ARA version of SV2 2.2 into FSP8.01 for me. Caveat Emptor, etc.
Just an additional note: This workaround is only necessary if you want to use Full ARA mode. However, Bridge ARA mode works fine with Studio Pro 8 without any filename changes.
 
Back
Top