- ALESIS Q49 NOT CONNECTING TO PRESONUS STUDIO ONE PATCH
- ALESIS Q49 NOT CONNECTING TO PRESONUS STUDIO ONE CODE
On a more optimistic note I have discovered that Ampire 2 is very good - a more limited palette than other sims but very good usable sounds - and I have at least matched, if not bettered, some of the amp and FX patches I was using in Helix Native. However other 3rd party plugins have also caused crashes in S1 - Bias FX2 and Reason 11 Rack to name the main problems. Presonus do not think it is a problem with Studio One. Line 6 did agree there was an issue and escalated it up the line to their tech development team - I have not had a reply back for a few weeks but have kept the ticket open and prod them every week or so for progress.
ALESIS Q49 NOT CONNECTING TO PRESONUS STUDIO ONE CODE
They seem to think the problem lies with Line 6 and the Helix Native code - despite not having a problem with other DAW's and Helix Native.
![alesis q49 not connecting to presonus studio one alesis q49 not connecting to presonus studio one](https://getinthemix.2dimg.com/1/alesis_q49_rear_media_b3b9a50ad1.jpg)
ALESIS Q49 NOT CONNECTING TO PRESONUS STUDIO ONE PATCH
I raised several tickets with Presonus over the constant crashing of S1 when editing a Helix Native patch - they did agree to test (which as they didn't have a copy of Helix Native to test meant they contacted Line 6 to get one - which suprised me as it appears they did no previous testing). Please raise a Support Ticket with both Presonus and Line 6 - and then maybe someone will believe there is a problem with Helix Native and Studio One (which does not seem to exist with Digital Performer of Cubase). Why is the Helix Native performance so bad in Studio One and is there a way I could improve it at the same buffer size? Tests with Izotope Neutron and amp simulators from Kazrog performed very similarly in both DAWs, I could ran the same or almost same number of instances before dropouts occured. tried the AU, VST2 and VST3 versions of the plugin (again with all other services disabled)Ī comparison between the two mentioned DAWs with other plugins didn't reveal such a strong difference. disabling all services in Studio One except Core Audio and VST support disable Turboboost (some people seemed to be able to prevent Dropouts in Studio One with this) I tried to improve the situation with the following: The computer is running the bare minimum of software, network connections disabled. Mac Mini 2018, i7 3.2 GHz, 64GB RAM, UHD 630, SSDĪudio Interface: Native Instruments Komplete Audio 6 (the old version, MK1) I did NOT use low latency monitoring (not possible with these settings in any case).
![alesis q49 not connecting to presonus studio one alesis q49 not connecting to presonus studio one](https://images.reverb.com/image/upload/s--Vmv7ayDR--/t_card-square/v1578315004/tuqgcecfsxizjgbrjcdm.jpg)
![alesis q49 not connecting to presonus studio one alesis q49 not connecting to presonus studio one](https://images.richtonemusic.co.uk/product/YYAMAHA88197.jpg)
In both DAWs audio buffers of 64 samples (in Studio One I also set the Dropout Protection to Minimum). I was very surprised that I could only run 3 instances of Helix Native in Studio One 4.6.1 before getting dropouts and crackles, while I could run 13 instances in Ableton Live 10.