Search the Community
Showing results for tags 'rosetta'.
Found 2 results
Background Apple has recently pivoted away from using Intel-based CPUs with its computers, instead favoring the Apple Silicon processor, also known as the M1 Chip. Both Intel and Apple Silicon systems run on macOS 11.0 Big Sur. As it stands, some Line 6 products are not fully supported on computers using Apple Silicon processors, so we cannot offer technical support for those products installed on M1 systems at this time. We highly encourage you to check with the manufacturers' websites of your music system’s hardware and software for M1 compatibility. Workaround on M1 Systems NOTE: Any workarounds offered are not official solutions. Issues experienced with workarounds offered cannot be addressed until official support is offered. Starting with Big Sur macOS 11, Apple introduced Rosetta v2, which allows applications to run in an emulated mode. Rosetta runs automatically with our software that is NOT a plugin. To use Rosetta with our plugins, locate your DAW in the Applications folder. Use command ⌘+I and check the “Open in Rosetta” box. You may have to rescan your plugins afterwards. Testing Applications and plugins tested (latest versions) on M1 systems running macOS 11.0 Big Sur: Helix Native: working as expected on DAWs running under Rosetta Echo Farm 3.0: working as expected on DAWs running under Rosetta Amp Farm 4.0: working as expected on DAWs running under Rosetta POD Farm 2 (Plugin): working on DAWs running under Rosetta, but takes a few seconds to appear after adding an instance of the plugin POD Farm 2 (Standalone): working as expected Ampeg SVT Suite: working as expected on DAWs running under Rosetta HX Edit: working as expected POD Go Edit: working as expected Powercab Edit: working as expected POD HD500 Edit: App launched properly, device was unable to connect POD HD500X Edit: App launched properly, device was unable to connect POD Pro X Edit: App launched properly, device was unable to connect Spider Valve Mk II Edit: working as expected Spider V Remote: working as expected Spider IV Remote: working as expected Workbench HD: working as expected Line 6 FBV Control: working as expected Line 6 Updater: working as expected Line 6 License Manager: installs as expected, yet devices do not populate in Line 6 License Manager. There is currently an open bug for this issue. Tested and available: M1-compatible Hardware Audio Drivers for: Helix Helix LT Helix Rack HX Stomp HX Stomp XL POD Go POD Go Wireless POD HD POD HD Pro POD HD Pro X POD HD500 POD HD500X Hardware Audio Drivers for most TonePort/POD Studio products (see below for exceptions) Will not be updated to support Silicon-based systems: StageScape: Audio Driver POD X3: Audio Drivers, Editors, Updaters, Control Panel app and License Manager POD XT: Audio Drivers, Editors, Updaters, Control Panel app and License Manager TonePort UX8: Audio Drivers, Updaters, Control Panel app and License Manager TonePort/POD Studio KB37: Audio Drivers, Updaters, Control Panel app and License Manager POD HD300/400 Line 6 Monkey
Changes to macOS Security Policy With Silicon processor computers running macOS Big Sur or greater, Apple has changed their security policy. These machines no longer allow third party drivers to be installed in the manner that they previously had. Driver installs now require the macOS security settings to be lowered before installation. As Silicon is still new to everyone, we expect to see bug fixes, changes and optimizations to macOS Big Sur and possibly subsequent macOS releases over the coming months. With that, the Silicon driver install process may change as well. As such, we encourage you to update your Silicon machine to the latest Big Sur version, which is currently 11.6, before installing drivers. Changing Security Settings Apple’s guide to changing security settings on a Silicon Mac are found at: https://support.apple.com/en-lk/guide/m … 8f7291/mac · Shut down your Mac · Press and hold the power button until you see "Loading startup options …". Your Mac will boot into Recovery mode. · Click Options (the gear icon), then click Continue · In macOS Recovery, you may need to choose your account and click Next. Enter the password and click Continue. · In the top menu go to Utilities...Startup Security Utility · Select the system on which you want to install the Driver. If the disk is encrypted with FileVault, click Unlock, enter the password, and then click Unlock. · Click Security Policy, choose Reduced Security and check the option to allow user management of kernel extensions from identified developers · Click OK. Enter the password for your account and click OK. · Restart your Mac from Apple menu Rosetta Installation When installing the Line 6 driver from the downloaded dmg file, you may be prompted to install Rosetta. · If so, click “Install”. Enter your password when requested. · If you see “System Extension Blocked”, go into System Preferences...Security and Privacy, click the lock, enter your password, click Unlock, and choose Allow. · Restart your Mac. Driver Removal It is advised that no programs are open, especially programs that may require the kext that is about to be removed. 1. In Finder, locate the kext file that is to be removed. Kext files are located in Library/Extensions. Keep this finder window open. 2. Open Terminal. Type the following command followed by the pathway of the kext that you would like to remove. Type without the quotes: "sudo kmutil unload -p /Library/Extensions/<Kext Name>". (ex. "sudo kmutil unload -p /Library/Extensions/L6Helix.kext") and click enter. 3. Enter your password. There should be no message after this. 4. Go to the finder window that was left open in step 1 and remove the kext file to the trash. You will be prompted to enter your password. 5. Restart your computer. 6. Go to Library/Extensions in finder and verify that the kext file is no longer in the extensions folder. If you see a message in Terminal (after Step 3), chances are there is another program open operating in the background that may interrupt the command. If so, restart your computer - verify there are no applications open and begin steps 1-6 again.