Hi there,
I hope for month that it gets solved friom update to update. S1 hangs for about 10sec on "Starting MIDI Engine". I disabled the service "Windows Midi Support" and bang. S1 startup finshed in about 1 sec (like S1v2 used to be) I removed all my devices from the surface data folder. But even with a complete blank list it still hangs. Running a SSD so speed should't be a problem. I start S1 really often so its important to get quick access. What can I look for?
PC: Intel i7-3770 4GHz | Asus P8Z77-LX | Corsair Vengeance LP 16GB | ASUS 960 GTX 4GB | Nesteq ASM-X Semi-Silent | Crucial SSD | Sasmung Spinpoint | RME HDSP 9632 | UAD-1 | WIN 10 Pro 64bit
DAW: S1 Pro 4 | Ableton 10 Suite | FL Studio 9 (hate the way they changed the piano roll in the new versions) Hardware Synth: Clavia Nord Rack Monitoring: GENELEC 8040A / Focal Shape 65 / Auratone (full threated room) | Own Mod Headphones (best / flattest Headphone on planet) Benchmark DAC1 USB | Mackie Big Knob |
This is a known problem with v3.3.0. They're currently working on it. I have the same issue. Studio One v.3.3 seems to have compatibility problems with number of MIDI drivers. (Re-)Install the previous version, v 3.21 for now.
Elson Trinidad Los Angeles, CA, USA
Web: www.elsongs.com Twitter: twitter.com/elsongs DAWS: Presonus StudioOne 3, Cakewalk Sonar Platinum, Propellerhead Reason 9 OS: Windows 10 CPU: Intel i7 3820 3.6MHz MB: ASRock X79 Xtreme4 RAM: Corsair Vengeance 16GB DDR3 Audio: Focusrite Scarlett 18i20 2nd Generation MIDI: M-Audio MIDIsport 4x4; M-Audio Axiom 61 |
have you guys installed v. 3.3.1?
Guitarist and composer:
---------------------------------------------------- https://itunes.apple.com/it/artist/davi ... d968493291 My system: ---------------------------------------------------- MacBook Pro i7, 16 GB ram Presonus Sphere |
dr4kan wrotehave you guys installed v. 3.3.1? Yes. As always I check the changelog and was hoping it got solved after reading it or at least got a bit better. 3.3.1 does seem to load the vst serives faster than previous releases. Its not an urgend problem so I don't want to raise a support ticket and I thought I got a screwed midi driver maybe.
PC: Intel i7-3770 4GHz | Asus P8Z77-LX | Corsair Vengeance LP 16GB | ASUS 960 GTX 4GB | Nesteq ASM-X Semi-Silent | Crucial SSD | Sasmung Spinpoint | RME HDSP 9632 | UAD-1 | WIN 10 Pro 64bit
DAW: S1 Pro 4 | Ableton 10 Suite | FL Studio 9 (hate the way they changed the piano roll in the new versions) Hardware Synth: Clavia Nord Rack Monitoring: GENELEC 8040A / Focal Shape 65 / Auratone (full threated room) | Own Mod Headphones (best / flattest Headphone on planet) Benchmark DAC1 USB | Mackie Big Knob |
tshadgett wroteI'm seeing this behaviour now on 5.02.60299. Only just started on this machine when loading it up today... Same thing just started for me on 5.2 |
Users browsing this forum: No registered users and 72 guests