Hey all,
I’ve got an issue with the above controller and Cubase15/Halion7. Just to clarify, I have the most recent versions of Halion, Cubase and, of course, the script/firmware . . .
Controller works as advertised while running in cubase! When I try to load an instance of Halion I get error loops that render both Halion and Cubase un-useable. In the Halion script panel I get the following errors constantly and it will run without end. I’m forced to force quit the app via task manager. Below is what I get.
I’m hoping someone here has experienced this and resolved it and wouldn’t mind sharing the result. Many thanks - I know this is a long-shot as browsing this forum and the google is not returning much - and what it’s returning is what I’ve already done.
Now for the long explanation - here’s what’s been done:
Did reach out to Steinberg/Yamaha support and some testing was done. I also have an open ticket with Nektar . . . still waiting on a response. Halion7 opens fine in Reason and Live Suite - no script barfs with the controller enabled and working. It works in standalone mode with no barfs (but I found out via Stein support that the controller script is not in use at that point) Interesting thing is that if i disconnect the Nektar and launch Halion in Cubase - no probs. Pref files for cubase were removed - no help
The Nektar: removed/re-installed as a controller in Cubase. Factory reset of the device - tested new usb ports on computer (and it’s not connect to a hub - it’s directly to computer) and ensured the firmware is latest and greatest.
I have re-downloaded and installed Halion7 . . .
Thanks in advance for help/fresh eyes
Joe
Hi,
Get in touch with the script author, please. An ‘error in error handling’ is quite funny. 
Speaking of “funny” I tested out that Halion Sonic launches and behaves just fine. I can control synth knobs all with no script barfs. It never occurred to me to test out just the player. . .
I am so at a loss.
Hi Joe,
Contacting Nektar support is always the correct way to go. Support have been able to reproduce the issue, and sent me the details, so I will look at a fix ASAP. Thanks for catching this, and sorry for the inconvenience.
Good to know that it doesn’t happen with HALion Sonic.
Best,
Tim
Thanks, Tim. Yup. Of course I did. I was just posting in case someone else had encountered this and has a fix.
But to update: as per Nektartech it seems to be a Windows only issue and he was able to replicate it by browsing patches at it broke. I’ve been hammering away at this for several days and here’s my temporary fix/workaround (about to mail this off to nektartech in a few. . . ) until a more stable fix is found. I don’t promise this will work should anyone need to try this, but it worked for me. He asked me to send a cubase file with the error in question. I couldn’t as Halion would poll every two seconds and was constantly in focus not allowing me control of cubase nor would it allow me to close out Halion. Everything became verry sluggish I might add. . .
Open a blank empty project - did a file save as before loading any instruments or doing anything. Opened up an instance of Halion 7 (latest and greatest) got the error. I was able to pull off a ctrl-s in the milliseconds between closing the error log and having it pop back up. All the while still being unable to close Halion but was only able to close the error log… Forced quit via task manager and opened the file to confirm that it saved with only that track. . .
No errors! Exit Cubase
Relaunch - new empty file - new halion instance - no errors. It’s been error free for yesterday and today so far (knock on wood) I’ve been gingerly using Halion this a.m. and going to work a little more at it, but I’m happy with it so far. I’m just waiting for it to happen again.
N.B. I have not opened up any projects with Halion in it as I’m deathly afraid of possibly corrupting any files. So, I haven’t fully tested it . . . all of this to say is that I don’t consider this a fix so much as I feel I just got lucky.
