Questions & Answers

Studio one 3.3.0 crashes when loading Midi Engine

+7 votes
asked Aug 26, 2016 in Studio One 3 by GUILLIEN (260 points)
edited Aug 27, 2016 by GUILLIEN

Since I updated to 3.3.0, Studio One 3 stops working when loading midi engine. Installation / Recovery without success

Back to previous version 3.2.2 and works fine well again

No problem with ProTools 11 on the same computer

PC + W10 - Focusrite Scarlett 18i20 (last updated drivers ok)

M-Audio Oxygen 49 and Akai MPD218 connected to PC. Work fine with PT11

What's wrong ?

8 Answers

+5 votes
answered Aug 26, 2016 by paulmalen (240 points)

I have the same problem with  3.3.0, Starts normally then crashes when loading the Melodyne Integration.  Running Windows 10.

+1 vote
answered Aug 26, 2016 by rfeltman (290 points)
edited Aug 26, 2016 by rfeltman
I am having the same issue.  Windows 10, Focusrite 2i2,Oxygen 49.

Starts and when it gets to "loading Midi Engine".....stops working.


UPDATE: here is what I have found...when I unplug my Focusrite one starts fine...yes it complains about my interface not loading and asks if I want to try again...I say no and then the program soon as I plug the Focusrite in and try to start it...Studion One 3.3 stops working.  So it seems as thought something has caused a problem with the Focusrite interfaces.  SAD FACE.....
+2 votes
answered Aug 26, 2016 by shaines (240 points)
edited Aug 26, 2016 by shaines

I too am having a problem where 3.3.0 locks up when hitting Melodyne Integration on Windows 10 64-bit (version 1607, build 14393.82).  WinDbg reports the following:

ModLoad: 00007ffc`ee080000 00007ffc`ee30a000   C:\WINDOWS\SYSTEM32\WININET.dll
### Warning: UCNET:Adding server via UDP discovery : tcp 52203 udp 64081 (alive event)
### Warning: UCNET:Server "Universal Control/" (id = "") resolved at host "", tcp 52203 udp 64081
(1078.24c8): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Program Files\Common Files\VST3\Celemony\Melodyne\Melodyne.vst3 -
000001fb`10f16512 48391b          cmp     qword ptr [rbx],rbx ds:00000000`12d3f8f0=????????????????

0:000> g
### Warning: Could not get Class Factory for C:/Program Files/Common Files/VST3/Celemony/Melodyne/Melodyne.vst3

+3 votes
answered Aug 26, 2016 by michaelormond (200 points)
I too am having the melodyne integration issue on Windows 10. The only way I can close S1 is via task manager end task. I tried running v. 3.3 in compatibility mode (Win 8) hoping maybe it would be a work around but no luck there. Hopefully there will be a patch update soon as it seems to be a issue more people are having. I thought I was going crazy, misery loves company I guess
+2 votes
answered Aug 26, 2016 by rodsanders (180 points)
Im having the same problem with the melodyne reingration.
0 votes
answered Aug 26, 2016 by arturkirakosian (160 points)
I think it's all about focusrite scarlett interface. Same issue here.
+2 votes
answered Aug 27, 2016 by john Gilleran (370 points)
i am having same problem with Melodyne integration. Please help.
0 votes
answered Sep 8, 2016 by connorguiberteau (18,180 points)
Best answer
This issue was fixed in 3.3.1

Release notes: [Win] compatibility issues with certain audio interfaces