Please ensure Javascript is enabled for purposes of website accessibility Jump to content

Search the Community

Showing results for tags 'm1'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community Support
    • Multi-Effects Units
    • Variax Instruments
    • Amplifiers
    • Computer Based Recording
    • Live Sound
    • Pedals/Controllers
    • Dream Rig - Line 6 Product Integration
  • General Discussion
    • Tone Discussion
    • Line 6 Lounge

Categories

  • General FAQ
    • Operating System-specific Information
  • Tutorial Videos
  • Effects/Controllers
    • HELIX/HX
    • DL4 MkII Stompbox Modeler
    • M5
    • FBV Controllers (MKII / 3)
  • Amplifiers
    • Catalyst
    • Powercab
    • Spider V
  • POD
    • POD Go
    • POD Express
    • Pocket POD
  • Guitars
    • JTV / Shuriken / Variax Standard / Workbench HD
  • Relay G10 Digital Wireless
  • Recording
    • Helix Native
    • Metallurgy
    • Echo Farm/Amp Farm
    • POD Farm 1/2.0/2.5
    • Computer Audio Set Up and Troubleshooting
  • Legacy Products
    • POD
    • Amps
    • 1st Gen Variax Guitars / Bass / Workbench
    • Effects and Controllers
    • AMPLIFi Series
    • Live Sound
    • Digital Wireless
    • Mobile Products
    • POD Studio / Tone Port / GuitarPort
    • Software
    • Dream Rig

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Registered Products

Found 8 results

  1. Today (my second day of Catalyst 100 ownership) the Catalyst Edit software on my M1 MacBook Pro would not see the amp. The Mac's "Audio Midi Setup" saw the Catalyst as both a valid midi host and as audio input and output. The Edit software itself took a very long time to load whether the amp was connected or powered on or whatever. This was odd because yesterday, upon initial setup, everything worked as expected. I was able to back up the default settings of the amp to my Mac, create new Presets and same them both to the Mac and the Catalyst. I tried many things (new USB cable, reinstall of software, factory reset of amp). No love. The solution - Go to Applications and find the "Catalyst Edit" app. CTL, Click and select "Get Info". Click to select the box labeled "Open using Rosetta". Launch the app It now works great! Are we ready for the super odd part. I can close the app, turn off the "Open using Rosetta" setting and it still works! Not to creep the scope of things too much in this thread, but... Catalyst Edit was also not working on my iPad Air with Apple silicon over USB today. However, after the above procedure, it also now works without any changes on that device. At any rate. I hope my experience helps some unfortunate user of Apple silicon with this app. Tom
  2. Background Apple has pivoted away from using Intel-based CPUs with its computers, instead favoring the Apple Silicon processor, also known as the M1/M2 Chip. Later Intel and and all Apple Silicon systems run on macOS 12.0 Monterey and macOS 13.0 Ventura. 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/M2 systems at this time. We encourage you to please check with the manufacturers' websites of your music system’s hardware and software for M1/M2 compatibility. Workaround on M1/M2 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 Software status on M1/M2 systems running macOS 12 Monterey and macOS 13 Ventura Metallurgy Collection: working as expected Helix Native: working as expected Echo Farm 3.0: requires Rosetta workaround Amp Farm 4.0: requires Rosetta workaround POD Farm 2 (Plugin): requires Rosetta workaround POD Farm 2 (Standalone): working as expected POD Farm 2 (Elements): working as expected HX Edit: working as expected POD Go Edit: working as expected Powercab Edit: working as expected POD HD Edit: working as expected POD HD500 Edit: working as expected POD HD500X Edit: working as expected POD HD Pro X Edit: working as expected 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: working as expected Helix Hardware Driver: working as expected POD Go Hardware Driver: working as expected Audio-MIDI Driver 1.0.0 (TonePort/POD Studio/GuitarPort): working as expected Software that 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 HD 300/400: Audio Drivers, Updaters, Control Panel app and License Manager Line 6 Monkey Line 6 Hardware status on M1/M2 systems running macOS 12 Monterey or macOS 13 Ventura: The following hardware products are being tested for general compatibility with macOS 12 Monterey or macOS 13 Ventura running on M1/M2 CPU systems when using the latest available Line 6 driver or the macOS 12 or 13 class-compliant driver, as applicable. AMPLIFi 30/75/150: working as expected AMPLIFi FX100: working as expected AMPLIFi TT: working as expected Firehawk FX: working as expected Firehawk 1500: working as expected Helix Floor: working as expected Helix LT: working as expected Helix Rack/Control: working as expected HX Effects: working as expected HX Stomp: working as expected HX Stomp XL: working as expected POD Go: working as expected POD Go Wireless: working as expected PowerCab 112 Plus: working as expected PowerCab 212 Plus: working as expected Catalyst Amps: working as expected DL4 MkII: working as expected Relay G10: working as expected Relay G10S: working as expected Relay G10T: working as expected Relay G10TII: working as expected Relay G70: working as expected Relay G75: working as expected Relay TB516G: working as expected Spider V 20/30/60/120/240/240 HC: working as expected POD HD: working as expected POD HD 500: working as expected POD HD 500X: working as expected POD HD Pro: working as expected POD HD Pro X: working as expected Sonic Port VX: working as expected Variax: working as expected Variax USB Interface: working as expected Mobile Keys 25/49: working as expected TonePort DI/GX/UX1/UX2/: working as expected POD Studio GX/UX1/UX2: working as expected
  3. Is there any news on the Line 6 drivers for Apple M1 series? It's been two years now that Apple released the new computers with the M1 chip, but until now no support from Line 6. An Ear deafening silence. I'm a bit afraid I need to sell my HD500X and use effects software with my DAW software.
  4. 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.
  5. We can confirm that the Sonic Port VX is a functioning audio interface on an M1 Big Sur MacBook pro at 44.1 and 48kHz. The device enumerates in the system sound preferences, streams audio and records in Pro Tools as both a microphone (mono/stereo) and a direct electric input.
  6. 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
  7. I recently purchased a set of M1 iMac and had it Logic Pro X installed. This M1 iMac is Big Sur based computer, by the way. Along with also newly purchased Symphony Desktop from Apogee, I tried to use my Helix Native, version 3.1.1, which I had been using on my Intel Macbook Pro as well. Only problem is, while, plug-ins provided by Apogee for Symphony Desktop seems to work fine on my M1 iMac, I just cannot load the Helix Native 3.1.1 in Logic. So, I went back and forth, uninstalled the Helix Native plug-in from my M1 iMac, and reinstalled, but I got a message saying, it "couldn't be opened" in the plug-in manager. I just want to confirm, that I am not the only one with this issue. I mean, I just want to know if this is a on-going issue, i.e. Helix Native 3.1.1.'s compatibility issue on M1 Macs. If not, I would really appreciate a word of advice on this.
  8. I was wondering to which date would Line6 be able to support the new Macs coming out. They've got the new Apple M1 processor, so the old drivers wouldn't work, I think. Without these drivers, you can forgot the new Mac, regarding the usage of Line6 products. The operating system Big Sur is compatible with most products, as stated here: Another page with Big Sur compatibility from Sweet Water: https://www.sweetwater.com/sweetcare/articles/macos-11-big-sur-compatibility-guide/ Yet another very good page for the compatibility on M1 and music production software in general (unfortunately without mentioning Line6): https://isapplesiliconready.com/for/music For my original question from Nov, 2020 there is still no official answer from Line6 or anyone else. There are news about the upcoming M1X or M2 processors, for which the very same is true: no new drivers, no native support. Similar questions to my original question: https://www.thegearpage.net/board/index.php?threads/line6-not-supporting-apple-anymore-is-native-a-dying-product.2245162/ In this german forum a guy says he had no latency or any other issues with MacBook Air M1 / Big Sur 11.4 with the software Helix Native: https://www.musiker-board.de/threads/helix-native-in-logic-pro-auf-m1-macbook-air.721520/
×
×
  • Create New...