godoq

My solution in M1 1. Helix Native AU validation failed in Logic Pro 2. Run Logic Pro as Rosetta Mode 3. Helix Native is working (No fail) in Logic Pro / Rosetta 4. Exit Logic Pro 5. Run Logic Pro as Native (Non Rosetta) 6. Helix Native can now be used.

Line6 is already preparing to sell the G10T II (probably the problem has been solved by hardware), and will sell it with POD go wireless. You can see leaked photo in https://www.thegearpage.net/board/index.php?threads/hx-stomp-xl.2221270/page-29#post-31900505 Because the photo resolution is not high, it is difficult to see, but the color has changed from black to dark gray, and the battery appears to be a little larger.

If a 1-year-old battery lasts only an hour, it means that the new transmitter (when used similarly) can only go an hour after a year. (Based on Line6's explanation) I loved the Relay g10 because it was the most convenient wireless device I've ever used, but it's too sad that the manufacturer ruined the quality because of legal issues. My logical solution for now is going back to GLXD-16 again which was very reliable.

For reference, I have been using the G10 for more than 2 years, And it has been a few weeks since I bought and used the new G10s at a local shop. I loved the simplicity and ease of use of this product. :) However, after the firmware update (Both for the Relay g10s Receiver and Transmitter according to the guidelines of Line6), I found that the battery life was apparently reduced. Only one indicator remains on my G10s receiver before I use it for less than 2 hours from the full battery state - 3 indicator in receiver & solid green transmitter LED. This doesn't seem to be the only case for me. I found several people complaining of the same symptoms here in Forum, Facebook Page, and TGP. If you look at a few support tickets or answers, Line6 may says, "You have a problem with your battery and need to replace it." I would like to hear a clear explanation from Line6, but I guess it will be difficult. There is no notice in Recall Page that the usage time will change after Update. However, Line6 has already changed the description of "8 hours" to "6 hours" on the product page and manual (Partially). (Honestly, I wish I could use it for 6 hours ...) -> Existing users obviously made purchases based on advertisements and specs, but there are no notices, rewards, or countermeasures. If you report this problem, Line6 will probably tell you to create a Support Ticket, and you will be asked to replace the unit because there is a problem with the battery. -> I wonder if the G10T that Line6 will resell is an improved hardware. Maybe that's why Line6 is driving replacements, otherwise people who buy new products will complain a lot. Do you guys have any problems with battery life after firmware update? I can't believe that my unit (Used for a few weeks) suddenly broken after firmware update.

I also felt that the battery life of the transmitter was significantly reduced, after updating all the firmware of the G10s. I suspect that the Line6 simply reduced the maximum charging limit itself to prevent overheating. If I knew that the battery duration would change, I would never update since i never had a problem :( If this is obviously due to the firmware, I need a way back to the previous firmware. I also need to create a support ticket. BTW, Will they change the battery life specification in the package and manual???

I'm not in front of my computer so I'm not quite sure. Try to create some kind of "dry" preset with output option of USB 5-6. Then change input channel of your DAW to Input 5-6.

Even without Helix Mac Driver 1.0.4 (in Class compliant mode), I can use all 8 I/O (incl. re-amp) as well as MIDI functions via command center. I think one of important feature of Helix Mac driver is solution for USB audio problems in some OS X versions.

Please check attached Logic Pro X screen shots. It shows better roundtrip latency when Helix Mac Driver NOT installed (using Helix as USB class compliant mode) Yes I know that with Helix Mac driver, i can change sampling rate and control system volume in OS. But Is it ok to understand that Helix Mac Driver still not well implemented for recording performance as an audio interface? * Without Helix Mac Driver (Class Compliant) Device Name : HELIX Audio Roundtrip : 7.9ms Output : 3.4ms Buffer size : 64 * With Helix Mac Driver (1.0.4) Device Name : Line 6 Helix Roundtrip : 16.9ms Output : 9.4 ms Buffer size : 64 EDIT : data fixed :)