I've tried everyway of loading patches into HALion. I load up LIVE, Load HALion 2, Import a sample set, Save the FXP in LIVE. All is great so far.
Start a new LIVE set, load HALion, attempt to load the FXP that I just created, and LIVE completely dissappears. No error screen, no crash dialog, etc...
HALion 2 crashes LIVE 4.0.4
HALion 2 crashes LIVE 4.0.4
MacBook Pro (MacOS 13.0.1) i9 Processor, 32gb RAM, 4tb SSD
(STUDIO I/O) MOTU UltraLite mk5 (w/ADA8200), (LIVE I/O) Behringer X Air XR18
Ableton Live Suite 11 (Live performances), Studio One 5 (Studio Stem Creation)
(STUDIO I/O) MOTU UltraLite mk5 (w/ADA8200), (LIVE I/O) Behringer X Air XR18
Ableton Live Suite 11 (Live performances), Studio One 5 (Studio Stem Creation)
Same problem with Halion3 and Live 4.1
I have a similar problem with HALion3 and Live 4.1. Trying to load a program bank (.fxb) will partially crash HALion and Live. Live's CPU meter goes to 0% and both my MIDI controller (Creative Prodikeys) and HALion's built-in keyboard are disabled. I suspect other functions are disabled also, but I usually just reboot at this point.
I remember reading a Steinberg statement (which I cannot find now) that said the HALion program/bank loading problem was a Live problem, which, according to Steinberg, Ableton says will be fixed in an upcoming update to Live. But I can't definitely confirm.
Anyone else have an insight on this "known issue"?
I remember reading a Steinberg statement (which I cannot find now) that said the HALion program/bank loading problem was a Live problem, which, according to Steinberg, Ableton says will be fixed in an upcoming update to Live. But I can't definitely confirm.
Anyone else have an insight on this "known issue"?
-
Frank Hoffmann
- Posts: 771
- Joined: Tue Jan 28, 2003 6:01 pm
- Location: Ableton Headquarter
Do you really have the newest Halion update? There was a bug that Halion didn't remember presets, which was our fault and has been fixed.
Frank
Frank
Frank Hoffmann
[email protected]
[email protected]
Halion fxb files cause error in Live
I have downloaded and installed the latest HALion3 update from Steinberg. The problem still happens. BUT, I was wrong about the statement from Steinberg. In fact, the statement referred to the problem you mention, Frank (i.e. settings not being saved).
The problem I have is NOT a saving problem. I can save banks and I can load banks. But after I load a bank, my MIDI control is disabled and I cannot switch between views in the HALion interface. I can, however, save the live set (with the new bank loaded), and when I reopen Live, the correct bank (which I had just loaded, causing the crash) is present in HALion.
After Live/HALion crashes and I close Live, I try to open Live again and get the following message:
"Live has tetected another active ReWire master application. No ReWire slave application will be available for use with Live unless you quit the current ReWire master application and restart Live." (No other ReWire applications are running.)
Upon checking Windows' process viewer, I realize that Live is still a running process (even after I've clicked the "X" to close it). Once I terminate Live as a running process (or reboot my computer). Live will work again.
I hope this information helps and that my description isn't too confusing. If you would like clarification, please feel free to ask me.
The problem I have is NOT a saving problem. I can save banks and I can load banks. But after I load a bank, my MIDI control is disabled and I cannot switch between views in the HALion interface. I can, however, save the live set (with the new bank loaded), and when I reopen Live, the correct bank (which I had just loaded, causing the crash) is present in HALion.
After Live/HALion crashes and I close Live, I try to open Live again and get the following message:
"Live has tetected another active ReWire master application. No ReWire slave application will be available for use with Live unless you quit the current ReWire master application and restart Live." (No other ReWire applications are running.)
Upon checking Windows' process viewer, I realize that Live is still a running process (even after I've clicked the "X" to close it). Once I terminate Live as a running process (or reboot my computer). Live will work again.
I hope this information helps and that my description isn't too confusing. If you would like clarification, please feel free to ask me.