
That explains why, after updating to 2.80, users are stuck with the 48,000 sample rate and no volume control. It appear s that the “ required 1.0.7 M ac Driver” is not installed b y default. Inside the “ installer.pkg” there are 2 sub packages - one consists of the Helix Editor application and the ot her is the latest Line 6 Updater application.
#What is mac core audio mac os x#
I looked inside the “HX Edit 2.80.dmg” when it mounted on a Mac OS X computer.

This info is a little late, but it is important as this thread was linked in a post elsewhere in this forum discussing a similar issue. For example, bring up QuickTime to play an MP3, it plays full blast and ignores the system volume level setting without that driver. Without it, instead of controlling the volume using the system volume level, you have to control the volume using each individual application's volume control. That stopped working after the firmware update.
#What is mac core audio driver#
That driver is needed to get output controls, i.e., volume control when using the Helix as the Mac system output device.
#What is mac core audio install#
You shouldn't have had to install any driver as the drivers needed by the Helix would have been installed when you ran the install for HX Edit.īut the driver doesn't appear to have been updated by the 2.8 ls -ld /Library/Extensions/L6Helix.kextĭrwxr-xr-x 3 root wheel 96 driver I'm referring to is the one you get when select the "beta" checkbox on the Line 6 Downloads page, with hardware=Helix, software=All Software, and os=Mac OS X. Most of this is more than likely due to the driver being screwed up. I would also guess that your recordings sounding “gibberish” could be that they were attempting to playback, but using the wrong sample rate i.e. It will try and create an audio device from whatever else it knows is available, usually the internal Mac sound option, although I have had it try to configure itself to use Soundflower. You just need to switch to whatever is actually connected, for example when I physically disconnect my Helix, Logic creates a “temporary” thing until I tell it to use the U-phoria UMC204HD even though it was already hooked up to the Mac. That “temporary” or something, that you mention occurs when Logic Pro X cannot detect the audio interface that was previously connected. So it might be kinda flaky, but it eventually works. I also unplugged my helix after the 2nd install and plugged it back in after the reboot and after starting Logic. I reinstalled the driver (2nd time) and rebooted again, and so far it's been working (I've recorded multiple takes on several different projects and all seems to be working finally). I wished I paid better attention to that because I just selected the helix input device and the temporary one disappeared (it had been selected).

I noticed when I went into logic and looked at the audio devices, the helix was there and there was another helix called 'temporary' or something. After I typed my first reply, it stopped working (for a bit).
