- Nebula 3 crashing studio one while loading install#
- Nebula 3 crashing studio one while loading registration#
- Nebula 3 crashing studio one while loading windows 10#
(the firewall is working normally in case you ask) Worked for me despite loosing some firewall configs or those having been resetted.
Nebula 3 crashing studio one while loading install#
If you don't want to risk it you can't try what I did and install Sonar. I'm not sure if it this was the fix or even if it was this version that was installed so do it at your own risk. Loaded Native and immediatly the log in screen appeared.įor those having problems you can try downloading VCRedist2013 from microsoft. I noticed specially because I had Reaper blocked in the firewall with rules I created and those rules where gone. It's like the windows firewall settings were resetted! Then I started opening other software and started receiving popups from windows firewall to authorize the connections from the software.
Nebula 3 crashing studio one while loading windows 10#
Since I have windows 10 it probably didn't install. I noticed Sonar was the only one to install the VCRedis 2013. Perhaps it has something to do with firewall settings or Visual C++ 2013 Redistributable. I can't quite understand how I solved it.
Nebula 3 crashing studio one while loading registration#
If I understood correctly you used the other DAW just for the first time, for the registration process and then you used Reaper all the time with no issues? Is that it? It crashed with savihost and opened just a small little windows with Cantabile but no crash in this one.
I already tried with two other VST hosts but not another DAW. Please try the workaround described above (initialize Helix Native with another DAW) and let us know if it works for you. We anticipated that someone else might encounter this issue at some point. We never did track down the actual issue but there was clearly some initialization problem with my installation of Reaper in conjunction with Helix Native. We closed the new DAW program immediately. This somehow allowed the Helix Native files to initialize properly.
The solution to the problem ended up being to uninstall Helix Native, download and install another DAW (we used the trial version of Sonar Platinum), Download and install Helix Native again, and then use the new DAW to launch Helix Native for the first time. The problem was not repeatable by the Line 6 Beta Support team it was definitely something unique to my installation. This behaviour persisted through several different beta software versions and several different uninstall/reinstall cycles of both Reaper and Helix Native. If there was no instance of Helix Native in the project file Reaper would start up normally but would then crash on the first attempt to load an instance of Helix Native. Reaper v5.4 running under Windows 10 would consistently crash during startup whenever an instance of Helix Native was present in the Reaper project file. During beta testing I had a similar problem.
0 kommentar(er)
