datacommando Posted December 9, 2020 Share Posted December 9, 2020 1 hour ago, Totogv said: Hola! Después de la actualización 3.0 se presentó un problema en mi Helix Floor, la actualización se hizo sin problemas pero luego de estar usando la Helix una hora, se puso en rojo el nivel de entrada de la guitarra que se muestra en la pantalla de la Helix y el audio se fue, tocaba la guitarra pero no sonaba, luego se sentía como que quería retornar la señal pero de pronto se apagó y comenzó a parpadear los led, apagué la Helix y luego lo prendí y seguía parpadeando los led y no arrancaba. Al día siguiente encendió sin problemas y la pude usar pero luego de un rato comenzó otra vez el mismo problema. luego de unos días pude hacer la actualización 3.01, pensé que con esa actualización se corregiría el problema pero de igual modo después de un rato ocurrió la misma falla. Después de un día lo prendí y realicé nueavamente la actualización a 3.01, previamente lo resetee, la actualización a 3.01 se realizó sin problemas, cabe indicar que la primera actualización a 3.01 lo hice a través del Edit siguiendo los pasos de instrucción de Line6 y la segunda vez que actualicé a 3.01 lo hice del Updater y se actualizó sin problemas, sin embargo después de un rato de uso nuevamente se pusó en rojo la señal de entrada de la guitarra y se fue el audio y se apagó y parpadeaban los led, adjunto video. El 18 de enero de este año mi Helix Floor tuvo una falla similar, generé un ticket y me derivaron con el distribuidor para que lo revise el técnico, el técnico lo revisó y después de varios intentos pudo solucionarlo pero como verán se ha vuelto ha presentar después de la actualización de 3.0. La verdad me preocupa esta falla recurrente en mi equipo, ya generé un ticket a Line6 y estoy a la espera de la respuesta, en caso conozcan esta falla por favor su ayuda para solucionar este inconveniente. Muchas gracias! Ernesto Hola, Eso parece ser algo muy serio y necesitará un técnico para arreglarlo. No estaría contento con esto, porque ha sucedido antes, pediría que lo reemplacen. Espero que esto ayude y sí, soy extranjero. 1 Quote Link to comment Share on other sites More sharing options...
grehula Posted December 10, 2020 Share Posted December 10, 2020 (edited) Hello, i've recently updated my Helix LT firmware to version 3.0.0 and there were no problems. But then I've got an email, that one should update to 3.0.1 to avoid some audio problems. Since updating, I'm having disconnecting issues with Helix edit. Today an audio coming from connected MacBook broke in the middle of the song with some strange noise and never came back (reconnect or restart helped then). Is this a known issue? I'm planning to downgrade to 3.0.0, for me it was working just fine. Regards, Alexander Edited December 10, 2020 by grehula Added missed info Quote Link to comment Share on other sites More sharing options...
danowen46 Posted December 10, 2020 Share Posted December 10, 2020 I've only just picked up a HX Stomp, but after updating to 3.01 I've noticed that when scrolling through snapshots, after going from 1 to 2, then back to 1, all the blocks go on. It doesn't revert back to the saved setting, it just turns them all on, and the rest of the snapshots in the preset also have all the blocks stay on. Has anybody else had this issue? Quote Link to comment Share on other sites More sharing options...
datacommando Posted December 11, 2020 Share Posted December 11, 2020 2 hours ago, danowen46 said: I've only just picked up a HX Stomp, but after updating to 3.01 I've noticed that when scrolling through snapshots, after going from 1 to 2, then back to 1, all the blocks go on. It doesn't revert back to the saved setting, it just turns them all on, and the rest of the snapshots in the preset also have all the blocks stay on. Has anybody else had this issue? Did you restore your Stomp from the backup file you made before updating the firmware to 3.01? The update will have reset you Global settings, and the Globals determine your snapshots behaviour. Hope this helps/makes sense. Quote Link to comment Share on other sites More sharing options...
mstrong916 Posted December 11, 2020 Share Posted December 11, 2020 I have the Helix LT. It has been updated to Helix 3.01. I own an Alienware I9 with 2070 super nvidia, windows 10 all latest updates - I say this because, I am getting the blue screen of death when I have the Helix plugged into my computer or Helix LT plugged into my Presonus Audiobox USB 96 that is plugged into my computer. Does anyone else have problems like this? Quote Link to comment Share on other sites More sharing options...
AnEscapeKey Posted December 11, 2020 Share Posted December 11, 2020 I am fairly certain that there is an issue with MIDI on the 3.0/3.01 on the HX Stomp Command Center. I've been going CRAZY about it. I am trying to sync up a midi controller with a command that set, and it's working half the time. My head is about to explode now, but if there are any midi gurus here, I could go into deeper details. I'm stuck right now. I feel I have tried every combination to rule out other possible culprits, but others may know of better ways to solve this.... Basically, my stomp is set with one preset = one song. I want it to recall certain "panels" on my Soleman Midi controller, that will sometimes have song-specific panels, or other times generic panels. I programmed most of them, but when trying to change from one preset to the other, it works for a few presets, then it stops working and the soleman stops answering to the messages. So weird... Quote Link to comment Share on other sites More sharing options...
datacommando Posted December 11, 2020 Share Posted December 11, 2020 8 hours ago, mstrong916 said: I have the Helix LT. It has been updated to Helix 3.01. I own an Alienware I9 with 2070 super nvidia, windows 10 all latest updates - I say this because, I am getting the blue screen of death when I have the Helix plugged into my computer or Helix LT plugged into my Presonus Audiobox USB 96 that is plugged into my computer. Does anyone else have problems like this? Hi, What you’re describing seems to be very odd. I can understand, if you have your HXLT connected directly to your computer via USB, there could be a problem that causes you to encounter the BSOD. Although, if this happens when your LT is connected to the audio inputs on the front of your AudioBox, and the PreSonus is hooked up to the USB, that would indicate the problem is more likely to be something is not right with your computer and/or the USB. When using the LT into the AudioBox then that is simply an audio signal, nothing really to make the PC collapse. Hope this helps/makes sense. Quote Link to comment Share on other sites More sharing options...
mstrong916 Posted December 11, 2020 Share Posted December 11, 2020 Well, it has happened since Windows 10 most recent updates (October and November). It happened to my POD XT Live as well. I thought it was just old, but I am wondering if part of the windows fixes has somehow interacted with DAWS or ?? The other day I was connected directly from the Helix LT to my computer playing in Studio One software. I unplugged it from my computer as there is no option to eject it and then it happened. 1 Quote Link to comment Share on other sites More sharing options...
glennsong Posted December 11, 2020 Share Posted December 11, 2020 With 3.0 output block no longer displayed/accessible in Helix Edit Quote Link to comment Share on other sites More sharing options...
HonestOpinion Posted December 11, 2020 Author Share Posted December 11, 2020 1 hour ago, glennsong said: With 3.0 output block no longer displayed/accessible in Helix Edit Sounds like you need to download and install HX Edit 3.0. The output block remains visible(circle with an arrow). At least on the Helix. Quote Link to comment Share on other sites More sharing options...
lulu_m Posted December 12, 2020 Share Posted December 12, 2020 Hi, data: HX floor 3.01 HX Edit 3.0 Windows 10. I found something weird in the bass amp section since I'm using the 3.01 version, I don't know if it happened already in older versions. I use a lot the Agua 51 bass amp for my fretless tone (who doesn't want to sound like Gary Willis.. lol) and I discovered that when I set the mid tone all up to 10, the patch stops outputting signal (sometimes I have to wait a few seconds, before the silence kicks in). I have tested and repeated it several times on a clean patch. Amp+cab or just amp, connected with HX editor...., not connected to computer and edit directly on the HX floor... All the same silence? Can someone confirm this is a bug? Thanks, Lucien Quote Link to comment Share on other sites More sharing options...
datacommando Posted December 12, 2020 Share Posted December 12, 2020 11 hours ago, lulu_m said: Can someone confirm this is a bug? Hi, I have just tried to see if this would happen for me, but no. I selected a blank preset slot and add the Agua 51 amp and cab and played through without and issues. Cranked the Mid up to 10 and just the same - plays fine no glitches, dropout or silences from here. Played with it for a while - seems O.K. Helix floor 3.01 HX Edit 3.0 Mac OS 10.13.6 High Sierrra You could try a reset or even a re-install Quote Link to comment Share on other sites More sharing options...
clumsylover78 Posted December 13, 2020 Share Posted December 13, 2020 Is this a bug? On HX Edit block is shows as a mixer but none of the parameters are editable, on the hardware you can tweak them and it is reflected corretly on HX edit.. Quote Link to comment Share on other sites More sharing options...
phil_m Posted December 13, 2020 Share Posted December 13, 2020 31 minutes ago, clumsylover78 said: Is this a bug? On HX Edit block is shows as a mixer but none of the parameters are editable, on the hardware you can tweak them and it is reflected corretly on HX edit.. Does it makes any difference if you tweak the parameters? To me, what's being shown on HX Edit makes sense because it's not really mixing anything in this configuration. Quote Link to comment Share on other sites More sharing options...
lulu_m Posted December 14, 2020 Share Posted December 14, 2020 On 12/12/2020 at 5:35 PM, datacommando said: Hi, I have just tried to see if this would happen for me, but no. I selected a blank preset slot and add the Agua 51 amp and cab and played through without and issues. Cranked the Mid up to 10 and just the same - plays fine no glitches, dropout or silences from here. Played with it for a while - seems O.K. Helix floor 3.01 HX Edit 3.0 Mac OS 10.13.6 High Sierrra You could try a reset or even a re-install Thanks so much for testing! Weird though.., I'll test further to see what it can be. 1 Quote Link to comment Share on other sites More sharing options...
clumsylover78 Posted December 14, 2020 Share Posted December 14, 2020 On 12/13/2020 at 6:18 PM, phil_m said: Does it makes any difference if you tweak the parameters? To me, what's being shown on HX Edit makes sense because it's not really mixing anything in this configuration. Good point, no tweaking parameters do not make any difference. Quote Link to comment Share on other sites More sharing options...
AppleTreeChen Posted December 15, 2020 Share Posted December 15, 2020 Tap LED of HX stomp flickers irregularly Firmware version: 2.92-3.0-3.01 Every time the tap LED is switched from other modes to stomp mode or scroll mode, the tap LED will flicker irregularly for a period of time, and then return to normal I believe this is a bug, because other friends around me also have this problem Quote Link to comment Share on other sites More sharing options...
Strut73 Posted December 16, 2020 Share Posted December 16, 2020 Hello! after firmware My Helix to 3.1. , the rotation function on the joystick stopped working, i can turn over the blocks only by moving the joystick in 4 directions, but the rotation does not work. Quote Link to comment Share on other sites More sharing options...
datacommando Posted December 16, 2020 Share Posted December 16, 2020 3 hours ago, Strut73 said: Hello! after firmware My Helix to 3.1. , the rotation function on the joystick stopped working, i can turn over the blocks only by moving the joystick in 4 directions, but the rotation does not work. Hi, The Global setting will have defaulted to the factory set when you did the update on the firmware. Before updating you would have made a backup of the content of your Helix. Open HX Edit 3.0 and from under the File menu select “Restore from backup” and you can select to restore just the Global settings which you had previously. Hope this helps/makes sense. Quote Link to comment Share on other sites More sharing options...
Strut73 Posted December 18, 2020 Share Posted December 18, 2020 Helix FLOOR. Joystick on the right side stopped working in rotation mode. This happened after installing update 3.1. Mechanical movements are OK. But the switching functions on the display do not respond to the rotation of the joystick potentiometer. When the joystick is moved forward, backward and to the sides, the functions are triggered. Several times I did restore all backups. maybe I need to go back to version 2.92. and check the rotation mode? Quote Link to comment Share on other sites More sharing options...
datacommando Posted December 18, 2020 Share Posted December 18, 2020 (edited) 7 hours ago, Strut73 said: Helix FLOOR. Joystick on the right side stopped working in rotation mode. This happened after installing update 3.1. Mechanical movements are OK. But the switching functions on the display do not respond to the rotation of the joystick potentiometer. When the joystick is moved forward, backward and to the sides, the functions are triggered. Several times I did restore all backups. maybe I need to go back to version 2.92. and check the rotation mode? Hi, once more, Because you’re asking the exact same question - I will give the exact same answer as above. Restore your Global settings from your backup the you made prior to updating the Firmware. HX Edit v3. From under the File menu item and select “Restore from backup”. In the window that opens next, select the backup file with the most recent date. Then only select the Globals to be restored. You could also select the “Pac-man” function from within the Global Settings Menu on your hardware unit. Preferences > Joystick encoder > Selection. You could revert back to 2.9x, but if that fails you may need a tech to check out the solder joints on the joystick. Hope this helps/makes sense. Edited December 18, 2020 by datacommando Quote Link to comment Share on other sites More sharing options...
theElevators Posted December 18, 2020 Share Posted December 18, 2020 Today my HX edit crashed, also along with that... in my preset I have the EXP 2 control the wah pedal automatically: meaning if it's below 5% it turns off, if it's 6--100% it is on. When HX edit crashed, the wah-wah on/off value got flipped. So now the wah was on when it was under 5%, and off when it's 6--100% percent. Basically it's flipped. I could not replicate this issue. As a developer I can say that line 6 does not store proper on/off values. It's basically effect.OnValue = !effect.OnValue. So if something happens, some glitch, or whatever, then your on/off values can get flipped. There was a more serious bug with the momentary switch a few versions ago where it was very easy to flip the value if you are not wearing shoes... yep shoes. Anyway, I haven't reported this because it's impossible to replicate it again. Quote Link to comment Share on other sites More sharing options...
andymccraw Posted December 20, 2020 Share Posted December 20, 2020 New bug with 3.01: When adding either the Arbitrator Fuzz or the Pocket Fuzz (could be true with other pedals, I haven't tested all) everything works fine when that pedal is engaged at first. When you turn off the pedal, then the amp/cab acts like it's been bypassed as well (it's a little tough to tell if the cab is doing this as well). Definitely sounds like the amp is bypassed. If I swap the Arbitrator Fuzz for something like the Compulsive Drive it fixes the problem. Again, not sure if this is an issue with other pedals, but those two exhibited this problem. Quote Link to comment Share on other sites More sharing options...
unguis Posted December 22, 2020 Share Posted December 22, 2020 Hi all, I am not sure if this has been already reported or not, so please excuse me if that's a duplicate. After update Helix Floor to 3.01 I have a problem with bank switching, being more precise from bank 2 to 1. When I am on preset 2A-2D and would like to switch back to 1A-1D, pressing BANK DOWN switches 2 banks to 32A-32D. I have to press then BANK UP to be back on 1A-1D. This issue occurs only when switching from bank 2 to 1. All the others (3-2, 4-3 etc.) work fine. Of course after the update I've done full Helix reset. Regards 1 Quote Link to comment Share on other sites More sharing options...
datacommando Posted December 22, 2020 Share Posted December 22, 2020 1 hour ago, unguis said: Hi all, I am not sure if this has been already reported or not, so please excuse me if that's a duplicate. After update Helix Floor to 3.01 I have a problem with bank switching, being more precise from bank 2 to 1. When I am on preset 2A-2D and would like to switch back to 1A-1D, pressing BANK DOWN switches 2 banks to 32A-32D. I have to press then BANK UP to be back on 1A-1D. This issue occurs only when switching from bank 2 to 1. All the others (3-2, 4-3 etc.) work fine. Of course after the update I've done full Helix reset. Regards Hi, Yes, what you have encountered is a known bug and a fix is currently being worked on. Here is a thread discussing the issue. Hope this helps/makes sense. Quote Link to comment Share on other sites More sharing options...
PerS Posted December 25, 2020 Share Posted December 25, 2020 Hi Writing this as information about BSOD involving Helix and Hx Edit. After have hade a whole bunch if problems on my old PC, that I solved, built a new one on which one problem persist, BSOD when turning my Helix LT off. Future will tell if I’m right or wrong… Short story – In >95% of the cases when I turn my Helix LT off and have HX Edit running I get a BSOD. If I close HX Edit before I turn the Helix LT off, never a problem. Most often with different error codes. My conclusion – If HX Edit is running and has an established connection to the Helix LT my PC crash/BSOD, most likely due to HX Edit losing connection to the Helix LT. I guess the drivers and/or the HX Edit causes conflicts resulting in the BSOD. The BSOD happens sometimes immediately when turning the Helix LT on and sometimes it can take a few seconds. But it happens… In September I build myself a new PC with a gen 10 processor and all hw new. Running Win 10 (latest version and updated drivers for motherboard), 16 GB RAM, M2 C:\-OS disk and separate SSD-disks for storage and recording. Optimized for audio/sound recording and do not use it for gaming. So, no G-hub, no mouse or keyboard drivers (HID) etc. Some connected devices using dedicated USB-ports, eg my Helix LT, Focusrite 18i6 (with drivers from September 2020) and from yesterday also my PC+ 112. Connected via USB are also mouse (wireless), keyboard, a USB-hub in the screen, all connected to one USB-port with one hub. On my old PC (gen 3 processor running Win10) I had some other problems too, some causing BSOD and some causing freezing/extremely slow, eg G-hub driver problem, Microsoft updates screwing up my soundcard and some other applications, Focusrite drivers that had problems even causing BSOD etc. Those problems I solved, but the BSOD with HX Edit are the same on both the new and the old PC, this I can’t find another explanation than what I wrote above. There is on more common point that I can’t prove not being involved, the graphic card (NVIDIA). Different cards but the same driver platform (GeForce Experience). Have no graphic issues, but you never know. As long as I remember to turn off HX Edit I have no real problem with this issue. I can wait for a bug fix and hope this can be a part of finding a solution. So why do I bring this up? Haven’t seen this described before and I think this can be one of problems generating BSOD for some or other interruptions eg during sw-updates. Well, other things can cause that too, like not reading instructions/manuals, PC not in shape, USB cables, USB-hubs, bad USB-ports etc. But this happens to me on two completely different hardware platforms (and I do read manuals and instructions :-). That’s more than a coincidence and has the potential to even cause other problems, other than the one I have seen. One thing I can’t explain is that I never have had a problem to run an update, have never ever had a failed update. I would expect a failure eg. when there is a reboot involved… but never. My best guess is that the Helix LT doesn’t lose power during reboot, so the drivers are still “active/not released” on my PC. But this maybe be different on different PC’s. So, my speculations in a nutshell... I have opened a ticket on this and reported my conclusions/findings to Line6. And now document it on the support forum hoping it can helps to save someone from a BSOD :-). If you have any ideas on this I gladly take your feedback. Thanks for reading this dreadful long post and wish you a continued Merry Christmas. Take care… //Per Quote Link to comment Share on other sites More sharing options...
phil_m Posted December 26, 2020 Share Posted December 26, 2020 23 hours ago, PerS said: Hi Writing this as information about BSOD involving Helix and Hx Edit. After have hade a whole bunch if problems on my old PC, that I solved, built a new one on which one problem persist, BSOD when turning my Helix LT off. Future will tell if I’m right or wrong… Short story – In >95% of the cases when I turn my Helix LT off and have HX Edit running I get a BSOD. If I close HX Edit before I turn the Helix LT off, never a problem. Most often with different error codes. My conclusion – If HX Edit is running and has an established connection to the Helix LT my PC crash/BSOD, most likely due to HX Edit losing connection to the Helix LT. I guess the drivers and/or the HX Edit causes conflicts resulting in the BSOD. The BSOD happens sometimes immediately when turning the Helix LT on and sometimes it can take a few seconds. But it happens… In September I build myself a new PC with a gen 10 processor and all hw new. Running Win 10 (latest version and updated drivers for motherboard), 16 GB RAM, M2 C:\-OS disk and separate SSD-disks for storage and recording. Optimized for audio/sound recording and do not use it for gaming. So, no G-hub, no mouse or keyboard drivers (HID) etc. Some connected devices using dedicated USB-ports, eg my Helix LT, Focusrite 18i6 (with drivers from September 2020) and from yesterday also my PC+ 112. Connected via USB are also mouse (wireless), keyboard, a USB-hub in the screen, all connected to one USB-port with one hub. On my old PC (gen 3 processor running Win10) I had some other problems too, some causing BSOD and some causing freezing/extremely slow, eg G-hub driver problem, Microsoft updates screwing up my soundcard and some other applications, Focusrite drivers that had problems even causing BSOD etc. Those problems I solved, but the BSOD with HX Edit are the same on both the new and the old PC, this I can’t find another explanation than what I wrote above. There is on more common point that I can’t prove not being involved, the graphic card (NVIDIA). Different cards but the same driver platform (GeForce Experience). Have no graphic issues, but you never know. As long as I remember to turn off HX Edit I have no real problem with this issue. I can wait for a bug fix and hope this can be a part of finding a solution. So why do I bring this up? Haven’t seen this described before and I think this can be one of problems generating BSOD for some or other interruptions eg during sw-updates. Well, other things can cause that too, like not reading instructions/manuals, PC not in shape, USB cables, USB-hubs, bad USB-ports etc. But this happens to me on two completely different hardware platforms (and I do read manuals and instructions :-). That’s more than a coincidence and has the potential to even cause other problems, other than the one I have seen. One thing I can’t explain is that I never have had a problem to run an update, have never ever had a failed update. I would expect a failure eg. when there is a reboot involved… but never. My best guess is that the Helix LT doesn’t lose power during reboot, so the drivers are still “active/not released” on my PC. But this maybe be different on different PC’s. So, my speculations in a nutshell... I have opened a ticket on this and reported my conclusions/findings to Line6. And now document it on the support forum hoping it can helps to save someone from a BSOD :-). If you have any ideas on this I gladly take your feedback. Thanks for reading this dreadful long post and wish you a continued Merry Christmas. Take care… //Per Hmmm.... I've never had a BSOD in Windows 10 while turning off one of my devices before closing HX Edit. I don't have an LT, but I have the Helix Floor, Rack, Stomp, and HX Effects, and there's been many times when I've powered them off while HX Edit is still running. I just a message that says "Connection Lost" on the bottom of the screen in HX Edit. Quote Link to comment Share on other sites More sharing options...
PerS Posted December 27, 2020 Share Posted December 27, 2020 Hi Phil Yes, it’s strange. And to be honest, not sure if it’s a Win10-problem or drivers. I have two completely different PC’s and the new one is really slimed, nothing extra on it then basic apps (Office 365, two DAW’s some performance utilities). I can add that if I start HX Edit before my Helix there is no problem, it says – “No device connected” and connect after turning on the Helix. It only crashes when turning off. I have hade my LT a bit more then 3 years and it is just a piece of joy. Those problems started about a year ago, on my old PC. I can only speculate what started it. I suspect a Microsoft update/upgrade could be one cause. One of those gave me problem with my Focusrite and some other apps too. I hade to reinstall drivers for the LT and Focusrite. Focusrite released a new driver a bit later and since then I have not hade any problem with that. I know that Logitech G-hub was involved, that I found pretty quick. I know that during this time I could get BSDO both on tuning on and off the Helix LT. Main problem causing this was the G-hub. Since May the only problem left on the old PC was this problem when turning off the LT when HX Edit was running. I hoped it was some kind of hw related problem, but it was the same on the new PC. My old PC was 8 years, but still running well. I decided to build a new as it started to get old, no updates of bios and drivers, some performance issues etc. This was a Win7 from the start and upgraded to Win10 when it was released. Almost sure I reinstalled Win10 short after due to instability, no problems after that. Can admit I have tested some apps on it, but I have kept it in good slim shape all the time and as said earlier not one Line6 update has failed for me, not on Helix, not on Pod HD Pro and not on PodXT (last one on an even older PC :-). The problems I hade has bin related to a broken SSD-drive and the problems I described above. As stated before – Its no problem for me really as long as I close HX Edit before shutting down Helix, annoying though. So, hoping for a fix off cause. Question though is if this problem can be related to what other users relate to problems in updates, Edit losing or can’t find Helix etc. I have not had those problems, on my PC or on PC I have helped friends to install Helix and Stomp. PC comes in many configurations and different conditions… and behaves different. Anyway, at this point I don’t know what to test so I see what Line6 come back with. Let you know //Per Quote Link to comment Share on other sites More sharing options...
Vic_Winters Posted December 27, 2020 Share Posted December 27, 2020 HX Stomp - FW 3.01 HX Edit - 3.00 Laptop OS - Win 10 Headphones connected to HX Stomp I've come across a recurring issue that after switching through a few presets in HX Edit the guitar signal coming through the headphones just cuts out and won't come back until you restart the unit. HX Edit stays connected, and computer audio still passes through without issue, but there's no guitar signal whatsoever. Edit 1/4/21 I tried a factory reset, but the problem persists. The input block will light up when there is signal coming in, but won't pass the signal from either input, and the tuner does not register any notes. Quote Link to comment Share on other sites More sharing options...
donkelley Posted December 28, 2020 Share Posted December 28, 2020 I friend of mine (super serious tone freak guitarist) recently picked up an HX Stomp to replace his boss cab simulator which had certain issues. He's finally, after a lot of work and analysis of the before and after responses, gotten it dialed in well and really likes it, when he's now finding that after switching back and forth between two presets, after about 10 switches the volume drops, as though eh LA compressor disabled or something. He has to powercycle to recover. I think there are recurring bug reports about similar, possibly related, issues? This is with FW 3.0.1. Cheers Quote Link to comment Share on other sites More sharing options...
merdenoms74 Posted December 28, 2020 Share Posted December 28, 2020 Can Line6 fix the disconnecting issues with HX Edit and Big Sur already? Major PITA! 1 Quote Link to comment Share on other sites More sharing options...
datacommando Posted December 28, 2020 Share Posted December 28, 2020 8 hours ago, merdenoms74 said: Can Line6 fix the disconnecting issues with HX Edit and Big Sur already? Major PITA! As Line 6 posted a notification at the top of this page in a bright orange banner, which reads: “MacOS 11 Compatibility with Line 6 Software” it goes on to explain - Currently, Line 6 software products are not compatible with macOS 11 Big Sur. Major PITA for those who didn’t bother to read it. 1 Quote Link to comment Share on other sites More sharing options...
jcspirited Posted January 2, 2021 Share Posted January 2, 2021 I have updated to firmware 3.0 twice. Same thing happens. When switching presets, or just re selecting the same preset. There's this modulation effect. I attached a small audio clip. Anybody else have this? The audio file I had is now added Track_1,_Rec_(2).wav Quote Link to comment Share on other sites More sharing options...
phil_m Posted January 3, 2021 Share Posted January 3, 2021 6 hours ago, jcspirited said: I have updated to firmware 3.0 twice. Same thing happens. When switching presets, or just re selecting the same preset. There's this modulation effect. I attached a small audio clip. Anybody else have this? Helix_3.0_Preset_Switch_3.wav 2.23 MB · 0 downloads Your wav file seems to be blank. Quote Link to comment Share on other sites More sharing options...
flop54 Posted January 6, 2021 Share Posted January 6, 2021 hello, Is it normal? I use a midi clock before the Helix. When i engage the clock the helix changes his tempo and my effects after too. When i disengage the clock the helix returns on his snapshot tempo but not the other effect (strymon). Another strange think with midi clock. If the helix is midi thru when you use a midi clock before. The externe midi clock and the helix midi are adding her clock so the tempo on the other effect are doubled. I post this on another subject : We need : - the LFO to start from the beginning of the sweep as soon as I activate the relative snapshot - the LFO to start from the beginning of the sweep as soon as we hit the tap tempo switch (it have to work with CC 64) - The same with a midi clock send on the helix I hope it's could be on the next update because some sounds with LFO are very cool but unuseless like that Thanks Quote Link to comment Share on other sites More sharing options...
kotaroz1971 Posted January 11, 2021 Share Posted January 11, 2021 Have some cracking sound when move expression pedal if you assign effect parameter to exp pedal and set tap tempo to transparent. Quote Link to comment Share on other sites More sharing options...
aklein Posted January 12, 2021 Share Posted January 12, 2021 (edited) Hi Helix gurus The new 3.01 Helix firmware seems to have broken the "Simple Pitch Shift" key change ability. It now sounds warbled, like there is some weird delay or effect going on when I just want to simply shift up/down a semi-tone or more. "seems worse when shifting lower" Everything worked fine in sound before 3.0/3.01 This is really important to my live performances as it is now unusable on stage and I need to tune my guitar instead of using the feature. If this could please be given some attention, that would be fantastic, as I now need to have multiple guitars just for key changes when a capo is not going to work. Also, the Looper seems to have a slight delay processing now and cuts off the start of the beat when pushed to record, like a slight delay? Actually, even changing patches seems slower and has audible drops before the selected patch allows audio again. *Addition My Bass player also has a Helix LT and has now confirmed the exact same issue after upgrading. So that's Helix and Helix LT that have the same issue. Hope that helps. Thank you! Edited January 13, 2021 by aklein Addtional information. Quote Link to comment Share on other sites More sharing options...
realtwang Posted January 13, 2021 Share Posted January 13, 2021 On 12/5/2020 at 10:24 AM, dyba514 said: I updated from FW 3.00 to FW 3.01,... now my helix floor cannot control my PowerCab plus 112 anymore ... I can hear the audio signal, but the parameters of the output block do not change anything on the PC+ anymore. The powercab plus is up to date (FW2.001) , I tried to change the cable, but the problem persist. Any idea ? Edit : --> I restored the factory settings (power up while pressing buttons 9 & 10), then restored a backup, and now it seems to work again. I have the same issue, and the reset and restore of the Helix did not help. It still seems to select whatever the hell preset it feels like selecting, not the one I programmed. This needs to be fixed! Right now this setup is completely useless for gigging. 1 Quote Link to comment Share on other sites More sharing options...
aklein Posted January 15, 2021 Share Posted January 15, 2021 On 1/13/2021 at 5:20 PM, realtwang said: I have the same issue, and the reset and restore of the Helix did not help. It still seems to select whatever the hell preset it feels like selecting, not the one I programmed. This needs to be fixed! Right now this setup is completely useless for gigging. I have the same issue, and the reset and restore of the Helix did not help. It still seems to select whatever the hell preset it feels like selecting, not the one I programmed. This needs to be fixed! Right now this setup is completely useless for gigging. Yep. I have found that to save things properly, don't use HX Edit 3, it's broken. Do what you need to do to get yourself setup the way you want and which screen is displayed on the floor unit and then "use the floor unit" to save the patch, not HX Edit. Don't downgrade either. the older HX Edit is not compatible with 3.01 either apparently. The Pitch shift and looper delay stuff is killing me more than these issues. Total performance breaking bugs. Gone back to carrying multiple instruments. Really nasty update unfortunately. Quote Link to comment Share on other sites More sharing options...
realtwang Posted January 16, 2021 Share Posted January 16, 2021 On 1/14/2021 at 9:19 PM, aklein said: I have the same issue, and the reset and restore of the Helix did not help. It still seems to select whatever the hell preset it feels like selecting, not the one I programmed. This needs to be fixed! Right now this setup is completely useless for gigging. Yep. I have found that to save things properly, don't use HX Edit 3, it's broken. Do what you need to do to get yourself setup the way you want and which screen is displayed on the floor unit and then "use the floor unit" to save the patch, not HX Edit. Don't downgrade either. the older HX Edit is not compatible with 3.01 either apparently. The Pitch shift and looper delay stuff is killing me more than these issues. Total performance breaking bugs. Gone back to carrying multiple instruments. Really nasty update unfortunately. Yes, I tried setting up the commands and saving the patch with the floor unit alone, and I still get the same issue. This leads me to believe it’s a bug within the Helix firmware, not HX edit. Whatever they did to the MIDI portion of the code in the firmware royally screwed things up. I don’t even know if it’s possible to downgrade firmware to a lesser version on the Helix. What a horrible situation. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.