I've just installed Studio One 3.5 on a new computer - totally fresh installation. Every time I start the app, it can't get past the initial plugin scan, it just keeps crashing over & over & over...
If I remove the plugin it was scanning when it crashed, it'll just crash on another plugin. No other DAW I've got installed has any issues with scanning any plugins I have installed either, so this is something that's just happening with Studio One.
Any tips on how to handle this?
Mac Pro 2013
By the way---I've had to "ADD" all of my previously installed External Devices since updating to 3.5. My Windows Audio is also acting weird since updating. Other than that, I don't regret updating.
vancemusgrove wroteI've just installed Studio One 3.5 on a new computer - totally fresh installation. Every time I start the app, it can't get past the initial plugin scan, it just keeps crashing over & over & over...
I submitted a ticket to the support and I'm waiting for an answer.
Seems more a osx issue.
The first time I got a crash I can remember a warning about the integrated
audio engine that didn't start correctly.
After a fresh install now crashes during the scan of plugs.
Two days and I cannot even open studio one.
You can debug your song down to a plugin or a set of plugins with this procedure if you are stuck.
I'm not trying to open a song but just start studio one.
I'm in the same boat. OSX, just updated Studio One Pro and I can not open it. It hard crashes before it gets to the main screen. I've submitted a support ticket and thankfully, don't have any pending projects, but I've been on Studio One since V.1, and this is the first time an update chunked on me like this.
First open a ticket.
But if you are willing to do your own debugging...
Warning proceed at your own risk:
Assuming it is crashing on VST plugins.
In that same directory (settings folder) under X64 or X86 depending on if you are 64 or 32 bit, you will find services.setting file.
With S1 off open it in a text editor and change:
<Attributes friendlyName="VST 3 Plug-In Support" enabled="1"/>
<Attributes friendlyName="VST 2.4 Plug-In Support" enabled="1"/>
Set a service the enable="1" to "0" to turn it off for debugging.
Then S1 will open with no plugins.
Once opened you then you want to edit the same file and turn 3 or 2.4 vst back on to isolate the failing service.
Also check all your location path once open.
You can do the same thing with other services if it it is something else.
jpettit wroteFirst open a ticket.
Thanks but didn't work for me and No answers from the tech support.
This is more astonishing than the release of this update.
Probably no consolation but my installation on Windows 7 64 Bit went along as usual without a hitch and everything was retained as it was including all the thumbnails and I didn't even need to re-establish my midi hardware. I think the key thing is to create a new installation sub folder for 3.5 and install the program there, and have all other relevant and dependent files held separately in the main containing folder. This way, you can always fall back and / avoid / solve issue's.
Mixing different versions of products in the same installation folder is going to cause unforeseeable problems. Another point to make is to avoid creating duplication of VST instruments and effects from different installations, because you can create conflicts which will prevent VST's ( instruments / Effects ) from loading up. You should only really have one instance held of a VST / Effect held in the main path to call from on any particular drive. This information is based on my own experience and problem solving.
THE INTRANCER- Digital 2D & 3D GUI / Music Artist |- Full Orchestral -Trance - Ambient - Film Scores 27 on S-Cloud 7000+genuine plays | 16 on S-Click | Studio One 3 Concept Re-Designs - Sample One XT | Reason X | S-O-3 Pro | Reaktor 6.0 | Reason 7 | C4D | CS6 |Win 7 64 Bit-Intel I7 email@example.comGHz,Focusrite Pro 14, ATH M50's, Casio XW P1&G1 Producer 20+ years - FOH - UK Stadium / Festivals) >>Studio One 3D GUI's<<
What do you mean it did not work?
Still scans and hung on a plug-in?
Also what is your ticket number?
Also, it seems to hang up on the built in Audio driver, not on a VST or other plug. It gets through all of the plugs in the startup scan and doesn't crash until "Starting Audio Engine..."
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
From the reports here, it looks like the issue is an Apple/Mac one.
mrpicholas wroteAlso, it seems to hang up on the built in Audio driver, not on a VST or other plug. It gets through all of the plugs in the startup scan and doesn't crash until "Starting Audio Engine..."
You are right.
I'd like to know who is beta testing studio one
on the mac side!
But that does not compare to 60,000 S1 uses with 59,999 configurations.
If you don't want to wait for a support ticket you can do this:
Proceed at your own risk:
So, ultimately there is a way to delete ALL settings from Studio One 3.
1. Open Studio One.
2. Click Help > Open Settings Folder
3. Close Studio One 3.
4. Delete all files except the "user.license" file in the folder.
5. Open Studio One 3 again.
NOTE: This resets ALL settings and values. Not suggested if you don't want to "start over" again setting every macro, MIDI instrument, etc. again.
You are right about the various configurations but however is the first time a daw
works this way on my system.
studio one is not my main daw I was just
curios about the new project page and I own studio one pro just for that though
a day could replace sound blade for the last stage of my work.
I don't know How to open studio one without incurr in the 100th crash of the day.
The tech support confirmed the issue on 10.9.5
"We're seeing this issue that appears to be linked to OSX 10.9. We are forwarding this for review. We assume this was not happening on 3.3.4 and doesn't happen if you revert to 3.3.4."
Don't know about the topic starter who has Sierra installed.
Let's wait for the next up-date
seems the tech support found a workaround.
"you can create an aggregate device on your Mac that incorporates your built-in output with your built-in microphone.
Once you have created the aggregate device in the Audio MIDI Setup, the first time that you launch Studio One it will crash. The second time that you launch Studio One, you can tell the program not to use the built-in output, and it will automatically switch to the aggregate device"
Users browsing this forum: pawelhebda and 6 guests