Line6Tony

Important Information About the G10T Transmitter · The recommended charging temperature range of the G10T Transmitter is specified as 50° F to 86° F (10° C to 30° C). · The recommended operating temperature range of the G10T transmitter is specified as 32° F to 122° F (0° C to 50° C). · Line 6 recommends charging the G10T transmitter at least every 6 months, based on best practices for lithium-ion batteries. · The functionality for Yamaha THR10II Wireless and THR30II Wireless users to update the G10T to version 1.06 firmware is also available. · For G10T transmitters on firmware version 1.06, LED behavior is now as follows: G10T Transmitter (Docked in G10/G10S Receiver, POD Go Wireless, Spider V amp or THR10II/THR30II/THR30IIA Wireless amp) LED State Condition Red (slow flash) Charging, less than 30 minutes battery time remaining * Green (slow flash) Charging, more than 30 minutes battery time remaining * Green (solid) Fully charged † Dim Red/Pink, may turn off G10T is not docked properly – Try un-docking and re-docking 5-10 times Red (three quick flashes, repeating) G10T charging has stopped due to exceeding supported temperature. Charging will resume after 5 minutes at 50° F to 86° F (10° C to 30° C) ‡ Orange (solid) Docked and connected to Mac or PC, firmware update in progress Off Receiver not powered (G10T enters sleep mode after 4 minutes if receiver power is disconnected) G10T Transmitter (Connected to Instrument) LED State Condition Green (solid) Transmitting, more than 30 minutes battery time remaining Red (slow flash) Transmitting, less than 30 minutes battery time remaining Off Connected to an instrument but not enough battery to transmit § or Removed from instrument * All values stated for amount of battery time remaining are approximate, and the exact amount of battery time remaining when an LED state is indicated may vary slightly between charges. When the G10T flashes red, it may have up to 60 minutes of battery time remaining. † If the G10T reaches a full charge (solid green) and remains docked, the G10T LED may eventually flash green again. This is expected behavior as the G10T may discharge slightly after reaching a full charge, and its LED may then flash green until it again reaches a full charge. ‡ If the charging lockout indication continues for over 10 minutes, please stop charging and try again in a cooler environment condition. § When the G10T has insufficient power to transmit, its LED may indicate a pattern of five quick red flashes when connected to an instrument and audio is detected. This is expected behavior. G10 Receiver (G10T Transmitter docked) LED State Condition White (solid) G10T charging or fully charged White (flicker) System has auto-scanned and is changing its channel Red (flash) G10T not docked properly – Try undocking and redocking Pink (pulse) Connected to Mac or PC, Line 6 Updater open Pink (solid) Connected to Mac or PC, firmware update in progress Off No power to receiver G10 Receiver (G10T Transmitter un-docked) LED State Condition White (solid) G10T transmission received, more than 30 minutes of runtime Red (slow flash) G10T transmission received, less than 30 minutes of runtime White (pulse) Receiver on but no G10T transmission received White (flicker) G10T transmission dropout (RF mute) Off No power to receiver G10S Receiver (G10T Transmitter docked) LED State Condition Battery LEDs Green (cycle 1-2-3) G10T charging 3 Green LEDs (solid) G10T fully charged RF LEDs 3 Red LEDs (solid) More than 75% interference (not usable) 2 Red LEDs (solid) 50% interference (usable, but only for short range) 1 Red LED (solid) 25% interference (usable, also indicates G10S power on) Battery LEDs Off RF LEDs On Battery LEDs – Off RF LEDs – Red (cycle 3-2-1) G10T not docked properly – Try undocking and redocking Battery LEDs – Off RF LEDs – 3 Red LEDs (solid) Connected to Mac or PC, Line 6 Updater open All LEDs Off No power to receiver G10S Receiver (G10T Transmitter un-docked) LED State Condition Battery LEDs 3 Green LEDs (solid) G10T transmission received, more than 4.5 hours of runtime 2 Green LEDs (solid) G10T transmission received, more than 3 hours of runtime 1 Green LED (solid) G10T transmission received, more than 1.5 hours of runtime 1 Red LED (solid) G10T transmission received, more than 30 minutes of runtime 1 Red LED (flash) G10T transmission received, less than 30 minutes of runtime RF LEDs 3 Green LEDs (solid) G10T transmission received, good signal strength 2 Green LEDs (solid) G10T transmission received, average signal strength 1 Green LED (solid) G10T transmission received, poor signal strength 3 Red LEDs (solid) No G10T transmission received, more than 75% interference (not usable) 2 Red LEDs (solid) No G10T transmission received, 50% interference (usable, but only for short range) 1 Red LED (solid) No G10T transmission received, 25% interference (usable, also indicates G10S power on) Red (cycle 3-2-1) G10S channel knob has been changed from its setting since G10T was last docked All LEDs off No power to receiver

If Helix Native / HX Edit crashes or loads with an empty screen on your Windows computer, check to see that your system drive is assigned to Disk 0. We have seen numerous reports of this working for customers running into this problem, as shown in this forum post: https://line6.com/support/topic/49342-hx-edit-281-and-helix-native-starting-with-with-a-blank-screen-and-crash/?do=findComment&comment=330021 The workaround was found and reported by user Camelot_One, and his post goes into detail on checking your drives and ways to rearrange them so that one of them shows as Disk 0. Microsoft Surface Book/Surface Pro users and HX Edit: Some users have reported that ejecting their internal memory card slot on the Surface book/Surface Pro has helped solve this issue. If HX Edit is having trouble opening, it's a possible work-around.

Issue: Sectigo Root Certificate expiration prevents Mac OS X 10.11 and earlier users from connecting to Line 6 servers Description: Trusted certificates are required to enable secure communication on computers. These certificates always have a built- in expiration date. One of the certificates included in Mac OS X 10.11 had an expiration date of May 30, 2020. Only Apple can update this certificate. We believe they won’t update it because this operating system is no longer supported by Apple. As a result, any software using Apple’s system for secure communication, including ours, is no longer be able to connect to its targeted servers. Below are a couple of examples of what a user subject to this issue will run into: Impact: As of June 1, 2020, macOS 10.11 (and earlier) users: · will be warned by Safari that the connection to Line6.com is not private · will not be able to install Helix Native or Helix Marketplace licenses on their macOS computer after they make their purchases on the website. Users that have already made purchases and already installed their licenses are not affected. It is only *new* purchases made from this date forward. · will not be able to install/run the trial version of Helix Native. · will not be able to use the Line 6 Updater to inform them of the latest firmware releases. Users will have to go to https://software.line6.com, download the firmware file using a web browser, and use Line 6 Updater in Offline mode. · will not be able to update their Helix firmware using HX Edit. · will not be able to update their POD Go firmware using POD Go Edit. Resolution: Beginning with macOS 10.12.2, the updated certificates were installed as part of macOS. Therefore, we recommend to our customers that they upgrade their OS to macOS 10.12.2 or above in order to resolve this issue. There are other resolutions to the issue and they are publicly available, but due to their complex and potentially disastrous nature, we cannot support them nor discuss how to implement them.

Issue: Sectigo Root Certificate expiration prevents Mac OS X 10.11 and earlier users from connecting to Line 6 servers Description: Trusted certificates are required to enable secure communication on computers. These certificates always have a built- in expiration date. One of the certificates included in Mac OS X 10.11 had an expiration date of May 30, 2020. Only Apple can update this certificate. We believe they won’t update it because this operating system is no longer supported by Apple. As a result, any software using Apple’s system for secure communication, including ours, is no longer be able to connect to its targeted servers. Below are a couple of examples of what a user subject to this issue will run into: Impact: As of June 1, 2020, macOS 10.11 (and earlier) users: · will be warned by Safari that the connection to Line6.com is not private · will not be able to install Helix Native or Helix Marketplace licenses on their macOS computer after they make their purchases on the website. Users that have already made purchases and already installed their licenses are not affected. It is only *new* purchases made from this date forward. · will not be able to install/run the trial version of Helix Native. · will not be able to use the Line 6 Updater to inform them of the latest firmware releases. Users will have to go to https://software.line6.com, download the firmware file using a web browser, and use Line 6 Updater in Offline mode. · will not be able to update their POD Go firmware using POD Go Edit. Resolution: Beginning with macOS 10.12.2, the updated certificates were installed as part of macOS. Therefore, we recommend to our customers that they upgrade their OS to macOS 10.12.2 or above in order to resolve this issue. There are other resolutions to the issue and they are publicly available, but due to their complex and potentially disastrous nature, we cannot support them nor discuss how to implement them.

Issue: Sectigo Root Certificate expiration prevents Mac OS X 10.11 and earlier users from connecting to Line 6 servers Description: Trusted certificates are required to enable secure communication on computers. These certificates always have a built- in expiration date. One of the certificates included in Mac OS X 10.11 had an expiration date of May 30, 2020. Only Apple can update this certificate. We believe they won’t update it because this operating system is no longer supported by Apple. As a result, any software using Apple’s system for secure communication, including ours, is no longer be able to connect to its targeted servers. Below are a couple of examples of what a user subject to this issue will run into: Impact: As of June 1, 2020, macOS 10.11 (and earlier) users: · will be warned by Safari that the connection to Line6.com is not private · will not be able to install Helix Native or Helix Marketplace licenses on their macOS computer after they make their purchases on the website. Users that have already made purchases and already installed their licenses are not affected. It is only *new* purchases made from this date forward. · will not be able to install/run the trial version of Helix Native. · will not be able to use the Line 6 Updater to inform them of the latest firmware releases. Users will have to go to https://software.line6.com, download the firmware file using a web browser, and use Line 6 Updater in Offline mode. · will not be able to update their Helix firmware using HX Edit. · will not be able to update their POD Go firmware using POD Go Edit. Resolution: Beginning with macOS 10.12.2, the updated certificates were installed as part of macOS. Therefore, we recommend to our customers that they upgrade their OS to macOS 10.12.2 or above in order to resolve this issue. There are other resolutions to the issue and they are publicly available, but due to their complex and potentially disastrous nature, we cannot support them nor discuss how to implement them.

The two common usage issues seen with Helix Native are: After a full Helix Native license is authorized, Helix Native is in Trial Mode when opened within a DAW Helix Native is crashing when attempting to open on an audio track within a DAW A blank screen after logging into your Line 6 account when opening Helix Native What has helped many users in these situations is the following: Disable WiFi Launch your DAW Insert Helix Native on a track. The login page should pop up. Turn on WiFi. When you sign in, Native gets reauthorized. Another potential resolution: ad blockers, firewalls, network monitors, etc. need to recognize line6.com and line6.net as legitimate domains. Adjust or disable such software accordingly. CPU Usage: Another common issue that may be noticed on some systems is Helix Native's CPU usage reading higher percentage than what would be expected. Helix Native is a CPU intensive plug-in, some of our systems show readings between 27-30%, the actual usage meter will vary from system to system. Increasing the H/W playback buffer size in your DAWs settings can reduce CPU usage to a degree.

When Studio One is in Low Latency Monitoring mode, parameter changes are not passed to Helix Native v1.90+ until LLM is disabled. Firstly, Helix Native is stable and functions normally in Studio One as well as any other VST3/ AU host. Studio One’s Low Latency Monitoring mode is different in that it keeps a plugin’s processing active, while Low Latency mode in other DAWs such as Logic and Pro Tools bypass plugins that incur latency above a certain threshold. This mode is only used during tracking, and while edits made to Helix Native in this state don’t take effect, Helix Native does process audio and allows tracking with low latency. If Helix Native parameter changes are desired, toggle the low latency monitoring option.

This article will be used as a container for model list documents as firmwares are released. The Helix Native Pilot's Guide lists the models released included with each firmware update. Helix_Native_Pilot's_Guide_v1_50_RevE_ENGLISH.pdf Helix_Native_Pilot's_Guide_v1_60_RevF_ENGLISH.pdf Helix_Native_Pilot's_Guide_v1_70_RevG_ENGLISH.pdf Helix_Native_Pilot's_Guide_v1_71_RevH_ENGLISH.pdf Helix_Native_Pilot's_Guide_v1_80_RevI_ENGLISH.pdf Helix_Native_Pilot's_Guide_v1_81_RevJ_ENGLISH.pdf HelixNative_PilotsGuide_v1_82_RevK_English.pdf HelixNative_PilotsGuide_v1_90_RevL_ENGLISH.pdf HelixNative_PilotsGuide_v1_92_RevM_ENGLISH.pdf

USB connectivity is a common issue with a failed update process: Make sure to check all cable connections, and USB ports for proper connectivity. The Pod Go should be connected directly to the laptop or computer with USB 2.0. No hubs or secondary connections. If it's a desktop computer (standing tower), then you may need to connect to the back of the computer near the power source. Proper USB 2.0 ports will provide enough USB bus power for your POD update. For Windows PC users: with all newer updates, it's always helpful to install the latest Pod Go Edit software FIRST, before you continue. This will include the latest Pod Go drivers for proper USB connectivity. Download here: https://line6.com/software/ 1. Disconnect the USB cable connecting the POD Go to the computer. 2. Boot the unit into "Update Mode" Press and hold PAGE > (page right) and then power on POD Go 3. Reconnect the POD Go to the computer, preferably trying a different USB port than before. 4. Launch Line 6 Central. 5. If POD Go connects, it will ask you to identify the device and you will have to select POD Go from the list. 6. If the unit does not connect, close Line 6 Central, connect to a different USB port on the computer, preferably with a different USB cable as well, and relaunch Line 6 Central. 7. If the unit then connects, reinstall the firmware. 8. If the unit does still not connect, there may be a configuration issue with the computer. Please try a different computer. Another common solution: If you're having trouble installing the latest update in Line 6 Central, you may want to revert back to the previous update version. Install firmware 1.40, and then once the Pod Go is booted up again - install Pod Go 2.50 or the latest firmware with Line 6 Central.

POD Go is fully compatible with the Line 6 EX-1 and Mission Engineering's EP1-L6 external expression pedals. Other pedals may work with POD Go, although they may not be fully compatible or tested, such as the Dunlop DVP1XL. In some cases, the pedals internal dip switches may need to be adjusted to ensure proper polarity. If you experience trouble with inaccurate expression pedal swing, try adjusting any internal or external dip switches the pedal may have. Also note that any expression pedals that appear to work backwards can be set to work properly by setting Global Settings > Switches/Pedals > EXP 2 Polarity to “Inverted.”