Helix Bug Reports

[datacommando]

3 hours ago, Dawo84 said:

I have the following problem with HELIX stomp:

 

I have the following problem with HELIX stomp: if I have selected a preset and want to switch to another preset via the HX Edit selection, the sound stops. No sound is generated anymore. Even manually I cannot select a preset sound using the controls. The HX Stomp is completely muted! 

. Does anyone have any idea how I can solve the problem. The device is in the factory setting and has been updated to version 2.92.

I’m a little unclear as to what you are describing, because when using either HX Edit software or the HX Stomp unit, when you switch from one preset to another, the unit has to ditch one lot of settings and load in another fresh set up. It is a computer after all - a very specialised one, but still a computer. 

Snapshots were added to allow changes within a single preset to avoid such issues and trails were added to delay and reverbs to avoid them cutting off abruptly when switching Snapshots.

 

I may be missing something and I’m not in the studio until tomorrow, but I think that’s the way it has always worked. I’ve been using a Helix floor for years and I have never regarded swapping from one preset to another being a problem. 

If you mean, when you swap to another preset, you no longer get any sound whatsoever, even when switching back to the one that was working before you switched, then that’s a whole different thing!

 

After updating to v2.92 did you reset your Stomp and let it rebuilt the presets?

[fish95]

I´d like to post just a wish for the next HXedit:

I´ve got a HX rack and the FC, but usually, sitting at my desk (tweaking patches, aso), the rack is a bit away and the FC either.

 

Is there any chance to add a button to the HXedit / software main screen which enables the tuner? Or some entry in the drop-down menus?

Like "file --> tuner" or "edit --> tuner"?

Kind of a luxury problem, for sure, but it would be awesome.

 

tia

stay healthy 

regards to you all

[datacommando]

17 minutes ago, fish95 said:

Is there any chance to add a button to the HXedit / software main screen which enables the tuner? Or some entry in the drop-down menus?

Like "file --> tuner" or "edit --> tuner"?

Kind of a luxury problem, for sure, but it would be awesome.

Ha ha ha... Oh! where is “spikey” when you need him?

 

Tuner in the editor - absolute classic!

 

You must be kinda new around here.

 

 

 

[fish95]

22 minutes ago, datacommando said:

Ha ha ha... Oh! where is “spikey” when you need him?

 

Tuner in the editor - absolute classic!

 

You must be kinda new around here.

 

 

 

yes, I am. But maybe another 500 posts like this, will change something :-)

 

[datacommando]

1 hour ago, fish95 said:

yes, I am. But maybe another 500 posts like this, will change something :-)

 

Too late!

 

Those other 500 posts like that have been and gone. (Mainly from “spikey” -  paste "tuner in the editor" into the search at the top of the page - all the way back to 2016)

 

T’aint gonna happen.

 

Think about it logically - it’s an editor and librarian, it does not process any audio.

[MonkeyXT]

If I'm not mistaken, I think fish95 was actually asking for something simpler; an on-screen way of long-pressing the Tap button in order to engage the tuner on the hardware.

That's how I read the original post.

 

[datacommando]

5 hours ago, MonkeyXT said:

That's how I read the original post.

Ah! Now you mention it, that might be the case. 
 

Yes, I can possibly understand that idea, although it’s a bit of a first world problem, as noted by “fish95”.
 

It’s just that there has been so much debate about a tuner in the HX Edit software, I jumped right in. 
 

Still, if that is the case, I think moving the FC board closer is one solution.

 

And for others who really do want a tuner in the Editor, why not clip one on the headstock of your guitar or stick a Peterson Strobe into your iPhone instead, then they are always close by.

 

 

[shmaque]

On 6/9/2020 at 11:08 PM, xpios said:

Helix 2.92 Bugs!!!! AHHHHH!

 

So, after talking with customer support regarding the issue with my presets going completely blank and overwriting/losing all my settings, per their instructions I did a backup. Did the button 9&10 reset. Then restored from backup. Then restarted and let it rebuild presets. Ok

 

So then I started crafting the tone on a preset with three snapshots. A clean tone, a dirty tone, and a lead tone. This is a blues tone. I used the looper at the end of the chain and all seemed well. I spent over 5 hours over the last couple days crafting tone and using the looper and all seemed good. GREAT! I thought it's all better and fixed.

 

However, today after putting the final tweaks on the preset I had built that I was extremely happy with, I saved the preset. Great. Now I also save a preset I'm building to another different slot in regular intervals just in case the current preset blanks out before I have a chance to backup my Helix Floor. So, I saved a version of the preset to another slot.

 

DISASTER! AHHHHH! This last time I saved the preset to a different preset slot, for some reason the saved slot went completely blank. No worries I thought. I'll just go back to my original preset and try again. Not so fast! Now the original preset slot was also completely blank! OMG! I just wasted 5 hours of my life crafting a killer tone and now it's all gone. Jesus F'ing Christ!

 

THIS IS NOT what I call a reliable gig worthy piece of equipment, no matter how good it sounds or how convenient it's supposed to be.

 

I can't even send the preset to customer support because it's GONE! The only thing to note of difference on this preset that might help debug is that the preset has NO PREAMP, AMP, or Cab. This is because I'm using the preamp and power amp of a real amp in four cable method out to a real cabinet and just running overdrive pedal blocks and EQ into the front of it and after an FX loop block some delay and reverb and finally the looper.

 

Is anyone else running into presets just randomly blanking out? I don't think this is caused by the looper now. I think its just some random bad behavior/bug that can occur at any time.

 

Wondering if this is in some way related as in this person's post to the Fx loop send/return I have in my presets.

 

https://line6.com/support/topic/56190-sendreturn-corruption-bug-under-blank-preset/?tab=comments#comment-335978

I’ve actually had a similar support ticket open for the better part of the last year. Just had it bite me again tonight (still on 2.82 because I’m waiting for the 2.9 new bugs to settle). Mine always happens when copying a preset to a new slot *from within HX Edit* - I’ve never had corruption from saving to a new slot directly on the unit. It seems like the sysex command (or whatever wrapper they use to send commands down) gets a corrupted length value and just plows over massive sections of flash. My ONLY fix has been to reset all set lists to factory default with buttons 7&8 and manually start restoring from backups again. It’s freaking infuriating. 

[shmaque]

On 5/21/2020 at 5:10 AM, Chris-7777 said:

I hear a strange pitch shifting effect with some amps. It is very pronounced with the Matchstick Ch1. When I play a D4 on the 7th fret of the g string, which is 293Hz, there is a very pronounced bass harmonic tone at about 150Hz, which is half the frequency of D4, but not quite. That bass note does not sound and behave like a natural harmonic tone, though, because when I move one or two frets down or up on the same string, the bass note is moving, too, but it is not at 50% of the note I play anymore. It sounds like a broken Octaver or something. Doesn't sound right at all.

 

I am on firmware 2.92 and I can not say whether this effect was there before I upgraded. I recently switched to new headphones, and it might well be that I do now hear things better across the frequency range than with my old headphones.

Talked to a friend who had experienced the same thing w/ this model in the 2.8 fw range - he said try tweaking down the Hum parameter; on his end it was actually the modeling of line hum that was causing this odd harmonic to show up.

[twsammons]

I have upgraded to 2.92.  Everything is great, EXCEPT when I switch from one tone to another the volume does some crazy things...Sometimes the volume is gone and I have to tap the volume foot pedal for it to come back to the volume level I have it set at.  This is a disaster when playing live switching from tone to tone quickly and all of the sudden it is muted until I tap the pedal.  Am I alone here?  I read through the comments and found nothing of the sort.  Sorry if I missed it.  Need to fix this fast!

This is a Helix floor unit

[phil_m]

5 hours ago, twsammons said:

I have upgraded to 2.92.  Everything is great, EXCEPT when I switch from one tone to another the volume does some crazy things...Sometimes the volume is gone and I have to tap the volume foot pedal for it to come back to the volume level I have it set at.  This is a disaster when playing live switching from tone to tone quickly and all of the sudden it is muted until I tap the pedal.  Am I alone here?  I read through the comments and found nothing of the sort.  Sorry if I missed it.  Need to fix this fast!

This is a Helix floor unit

 

Did you do a restore from backup after doing the update? The update changes the global settings, and this particular issue sounds like it's related to the setting in Global Settings>EXP Pedals>EXP# Position. If it's set to Per Preset or Per Snapshot, the Helix will ignore the position of the pedal until you touch it. So it may be that you accidentally saved those presets with the volume pedal at zero.

[xpios]

Having a slightly different issue with the tuner. 

 

Im on 2.92 and noticing the sound changes after going in and out of the tuner.

 

It may be easier to hear this through a real amp/cabinet, than using monitors because the real amp/cab is much more present and full sounding, but I will try it on my monitors in a bit.

Here's the issue. When I first turn on the unit and play on that preset, I hear the expected sound of my guitar and the preset. Then I press and hold to bring up the tuner. Whether I use the tuner or not, when I press the tuner stomp switch again to return to normal play mode, the tone of the preset/guitar is noticeably attenuated in upper and lower frequencies. The odd thing is, if I then immediately press and hold to go back into tuner mode then press the switch to return back to normal playing mode, the sound is back to normal. If I do it again, the sound is attenuated again. I'm not sure if it's attenuated or if the volume is dropping ever so slightly which causes the change in acoustics and then returning back to normal when I go into tuner and back out again. 

It doesn't work the same way on each preset either. On some presets it immediately attenuates when I go into tuner and back, and on others it does not immediately do it, but does it the second time I go into the tuner and back and so forth. 

It's really odd.

[jeremystern]

2.92 Update changes global settings for snapshots from Discard to Recall

 

I believe there is an update issue that should be communicated to Helix users: I had my snapshots global settings set to Discard but when I updated to 2.92, the settings changed to Recall. This made an absolute mess for me as I kept inadvertently saving things to my snapshots that I didn't intend to. 

 

[silverhead]

55 minutes ago, jeremystern said:

2.92 Update changes global settings for snapshots from Discard to Recall

 

I believe there is an update issue that should be communicated to Helix users: I had my snapshots global settings set to Discard but when I updated to 2.92, the settings changed to Recall. This made an absolute mess for me as I kept inadvertently saving things to my snapshots that I didn't intend to. 

 

•  

Yes, updating the firmware restores the Global Settings to their factory defaults. That’s why the installation instructions require you to create a system backup before updating the firmware, and also instruct you (In red font so that you’ll note it’s importance) to restore the backup after updating. Restoring the backup resets the global settings to what they were before updating. Following firmware update instructions is important.

[jeremystern]

9 minutes ago, silverhead said:

Yes, updating the firmware restores the Global Settings to their factory defaults. That’s why the installation instructions require you to create a system backup before updating the firmware, and also instruct you (In red font so that you’ll note it’s importance) to restore the backup after updating. Restoring the backup resets the global settings to what they were before updating. Following firmware update instructions is important.

Thanks and ouch...I'm always pretty meticulous when updating so I'm not sure how I missed that but I don't think I did. We'll see again when I update to 3.0 :) 

[silverhead]

Sorry - I didn’t mean to cause an ouch. I guess I’m just sensitive to the importance of following the update instructions because I see SO MANY post-update issues that are self-inflicted due to not following the instructions. 

[iamatypeofwalrus]

Dropping this here in lieu of a support ticket, but I noticed that the Helix 2.92 release notes that "In very rare cases, leaving the unit on for many hours can sometimes cause reverb models to cease outputting audio" was included as known issue.

 

For what it's worth, this has been a long standing issue for me as I tend to leave my Helix on for weeks at a time and it wasn't introduced in recent memory (2.7  and above). Maybe that will help the devs git bisect :-)

[HonestOpinion]

4 hours ago, iamatypeofwalrus said:

Dropping this here in lieu of a support ticket, but I noticed that the Helix 2.92 release notes that "In very rare cases, leaving the unit on for many hours can sometimes cause reverb models to cease outputting audio" was included as known issue.

 

For what it's worth, this has been a long standing issue for me as I tend to leave my Helix on for weeks at a time and it wasn't introduced in recent memory (2.7  and above). Maybe that will help the devs git bisect :-)

 

Since it's easier on the Helix, the environment, and your electric bill not to leave it on for that long the workaround seems pretty painless unless this happens within the span of a gig or recording session.

[shmaque]

Help me out here - I rarely use the Vintage Digital Delay, but in 2.92 I'm noticing that if you select 6, 8, or 16 bit depth (6 is especially gnarly due to the bit corruption), it will infinitely oscillate the noise floor after processing any sound (even if you immediately then ground the input or put a volume block at 0% immediately preceding the delay) with anything > 2% for a feedback setting on the delay. 10,11,12,14, and 24 bit do not do this. Flipping to another preset and back kills it until you play something else, as does moving blocks around in HX Edit.

 

Is this some quirk that's accurately being modeled or a bug? I've never encountered this before, and I swear I've used 16 bit before.

[HonestOpinion]

44 minutes ago, shmaque said:

Help me out here - I rarely use the Vintage Digital Delay, but in 2.92 I'm noticing that if you select 6, 8, or 16 bit depth (6 is especially gnarly due to the bit corruption), it will infinitely oscillate the noise floor after processing any sound (even if you immediately then ground the input or put a volume block at 0% immediately preceding the delay) with anything > 2% for a feedback setting on the delay. 10,11,12,14, and 24 bit do not do this. Flipping to another preset and back kills it until you play something else, as does moving blocks around in HX Edit.

 

Is this some quirk that's accurately being modeled or a bug? I've never encountered this before, and I swear I've used 16 bit before.

 

Does it still do this if you increase the Headroom parameter to max?

[shmaque]

30 minutes ago, HonestOpinion said:

 

Does it still do this if you increase the Headroom parameter to max?

Yes. Interestingly, increasing headroom to max just seems to increase the volume at which the oscillation happens. 

Even more interestingly - I just tried to recreate it in Helix Native and can only replicate the issue if I select 6 bit. The other bit depths all behave properly, while 6 hangs out with a steady ~-50 to -48dB (depending on the headroom setting) circuit noise repeat forever.

<EDIT> I take that back - I switched to a slightly noisier stock setting for sanity check (01B Essex A30) and added the vintage digital right at the front of the chain. 6,8, and 16 bit all exhibit this behavior even in Native.

[davej46]

On 6/13/2020 at 10:54 AM, twsammons said:

I have upgraded to 2.92.  Everything is great, EXCEPT when I switch from one tone to another the volume does some crazy things...Sometimes the volume is gone and I have to tap the volume foot pedal for it to come back to the volume level I have it set at.  This is a disaster when playing live switching from tone to tone quickly and all of the sudden it is muted until I tap the pedal.  Am I alone here?  I read through the comments and found nothing of the sort.  Sorry if I missed it.  Need to fix this fast!

This is a Helix floor unit

I just receive my new Helix from Sweetwater and had a similar problem.  When switching presets, the output audio would cut out.  Input seems to be ok as I can see the icon on the screen flashing.  By output I am monitoring headphones and USB 1/2.  It happens if I am using the foot switches or scrolling using the Preset knob.  Have written to Sweetwater to see what they suggest for a remedy.  Have not registered w/Line 6.  Waiting so see what develops.  Shouldn't

be a heat problem.  I would say it was on less than an hour.  Maybe a 2.92 bug?  There are several Helix users on YouTube.  Haven't heard any of them complaining.

 

I have had several Line 6 products starting with the DuoVerb so I am a fan.  From my experience they seem to be pretty good with support.  We'll see.

DaveJ46

[chrisakinhan]

On 6/17/2020 at 6:15 PM, xpios said:

Having a slightly different issue with the tuner. 

 

Im on 2.92 and noticing the sound changes after going in and out of the tuner.

 

It may be easier to hear this through a real amp/cabinet, than using monitors because the real amp/cab is much more present and full sounding, but I will try it on my monitors in a bit.

Here's the issue. When I first turn on the unit and play on that preset, I hear the expected sound of my guitar and the preset. Then I press and hold to bring up the tuner. Whether I use the tuner or not, when I press the tuner stomp switch again to return to normal play mode, the tone of the preset/guitar is noticeably attenuated in upper and lower frequencies. The odd thing is, if I then immediately press and hold to go back into tuner mode then press the switch to return back to normal playing mode, the sound is back to normal. If I do it again, the sound is attenuated again. I'm not sure if it's attenuated or if the volume is dropping ever so slightly which causes the change in acoustics and then returning back to normal when I go into tuner and back out again. 

It doesn't work the same way on each preset either. On some presets it immediately attenuates when I go into tuner and back, and on others it does not immediately do it, but does it the second time I go into the tuner and back and so forth. 

It's really odd.

 

So, I tested this and found out there is a little over 1db drop in volume after engaging and disengaging the tuner. It goes back and forth. The volume drops after you engage and disengage, and then the volume comes back after you engage/disengage again. I recorded the wave form into my DAW to capture this. See image. You can see that not only does volume drop, but the distance between the first two peaks is reduced indicating perhaps some compression going on as well. This happens on all or most my presets. I generally use at least a PowerAmp (NO CABINET) Delay and some Reverb on each preset. If someone wants to try replicating this into their own DAW on 2.92.

[sd_kirk]

On 6/18/2020 at 4:51 PM, silverhead said:

Yes, updating the firmware restores the Global Settings to their factory defaults. That’s why the installation instructions require you to create a system backup before updating the firmware, and also instruct you (In red font so that you’ll note it’s importance) to restore the backup after updating. Restoring the backup resets the global settings to what they were before updating. Following firmware update instructions is important.

 

Interesting, I've never had to restore the system backup after updating firmware, my Helix Floor always remembers the global settings exactly as they were.  Is it automatically restored as part of the update, or are you supposed to do this manually?

[datacommando]

On 7/8/2020 at 11:08 AM, sd_kirk said:

 

Interesting, I've never had to restore the system backup after updating firmware, my Helix Floor always remembers the global settings exactly as they were.  Is it automatically restored as part of the update, or are you supposed to do this manually?

 
Mmm...

As “silverhead” noted: - “Following firmware update instructions is important.”, so I would guess you didn’t bother to read the important stuff, which explains you have to restore from a backup.
Line 6 must think that it is very important because on the download page the info is printed in red type.
EXAMPLE:

 

IMPORTANT! Carefully read and follow the update instructions below. If you don't—and then run to the forums asking why it's not working—the interwebs will make fun of you.

 

Updating Helix/HX Firmware to 2.92

Helix Floor, Helix Rack, Helix LT, HX Effects, HX Stomp

STEP 1—Updating HX Edit to 2.92 (assuming you haven't done this already)

1. Log onto line6.com, download, and install HX Edit 2.90:
   • macOS: https://line6.com/software/readeula.html?rid=9732
   • Windows 7/8/10: https://line6.com/software/readeula.html?rid=9731

 

STEP 2—Updating Helix/HX Firmware to 2.92

1. If you have Helix Rack/Control, turn off Helix Control. Also, shut down all Line 6 software or any programs that use audio, like DAWs, iTunes, Spotify, video games, etc.
2. Connect your Helix/HX device to a Mac or PC via USB (do not use any sort of USB hub, which may include the front USB ports on towers) and turn it on.
3. Launch the new version of HX Edit 2.92 you installed in Step 1 above. If you're not signed in, click "Check for Updates" in the lower right corner and sign in. If you're already signed in, a dialog panel appears, indicating an update is available.
4. Click "Update Now." A window appears, asking you to back up your Helix/HX hardware. Click OK, optionally rename the backup and/or choose a different destination folder, and then click "Create Backup." IMPORTANT! Note the location where you've saved the backup.
5. Continue following the prompts. Once updated, the window reads "Update Complete" and your Helix/HX hardware begins rebuilding its presets; wait for this to complete and click "Back to HX Edit."
6. From the File pull-down menu, click "Restore from backup..." A dialog appears. Click "Restore Backup" and then "Yes."
7. Once the restore has finished, turn your Helix/HX product off and then on again.
8. If you have Helix Control connected to Helix Rack, turn on Helix Control. Helix Rack reads "Helix Control must be updated to work properly." Press Knob 6 (OK).

  

[sd_kirk]

Yeah fair shout there datacommando!!  I think because the Helix said update complete and was working as expected then I inadvertently skipped that stage, but will definitely do that going forwards!!  Consider me told!!  :-)

 

I guess my question should then be, what is the purpose of restoring the backup?  Without doing this stage, everything works fine, the new models etc are all loaded, all my saved patches are there as they were etc, so why is this stage needed?  I don't use IR's (still learning all the capabilities etc with the inbuilt cabs before opening that minefield!), would that impact the need to run this stage?

[Julian16]

14 hours ago, datacommando said:

 
Mmm...

As “silverhead” noted: - “Following firmware update instructions is important.”, so I would guess you didn’t bother to read the important stuff, which explains you have to restore from a backup.
Line 6 must think that it is very important because on the download page the info is printed in red type.
EXAMPLE:

 

IMPORTANT! Carefully read and follow the update instructions below. If you don't—and then run to the forums asking why it's not working—the interwebs will make fun of you.

 

Updating Helix/HX Firmware to 2.92

Helix Floor, Helix Rack, Helix LT, HX Effects, HX Stomp

STEP 1—Updating HX Edit to 2.92 (assuming you haven't done this already)

1. Log onto line6.com, download, and install HX Edit 2.90:
   • macOS: https://line6.com/software/readeula.html?rid=9732
   • Windows 7/8/10: https://line6.com/software/readeula.html?rid=9731

 

STEP 2—Updating Helix/HX Firmware to 2.92

1. If you have Helix Rack/Control, turn off Helix Control. Also, shut down all Line 6 software or any programs that use audio, like DAWs, iTunes, Spotify, video games, etc.
2. Connect your Helix/HX device to a Mac or PC via USB (do not use any sort of USB hub, which may include the front USB ports on towers) and turn it on.
3. Launch the new version of HX Edit 2.92 you installed in Step 1 above. If you're not signed in, click "Check for Updates" in the lower right corner and sign in. If you're already signed in, a dialog panel appears, indicating an update is available.
4. Click "Update Now." A window appears, asking you to back up your Helix/HX hardware. Click OK, optionally rename the backup and/or choose a different destination folder, and then click "Create Backup." IMPORTANT! Note the location where you've saved the backup.
5. Continue following the prompts. Once updated, the window reads "Update Complete" and your Helix/HX hardware begins rebuilding its presets; wait for this to complete and click "Back to HX Edit."
6. From the File pull-down menu, click "Restore from backup..." A dialog appears. Click "Restore Backup" and then "Yes."
7. Once the restore has finished, turn your Helix/HX product off and then on again.
8. If you have Helix Control connected to Helix Rack, turn on Helix Control. Helix Rack reads "Helix Control must be updated to work properly." Press Knob 6 (OK).

  

thanks for the example, really useful!

[datacommando]

2 hours ago, sd_kirk said:

I guess my question should then be, what is the purpose of restoring the backup?

 

Hi, 

 

During the process of updating the firmware in your Helix lots of settings are restored to the factory defaults. One of the major ones is your "Global" settings. It may not matter if you haven't modified them, but many users do change them and consequently after an update run off to forums to decry Line 6 for having screwed up their hardware.

 

Think of it as a safety net.

 

Oh, yeah, all that "loud stuff printed in red" wasn't me, it was originally written by "Digital Igloo" (Eric Klein -Chief Product Design Architect at Yamaha Guitar Group, Inc.)

 And this has just made it to 2,000 replies in the Helix Bug Reports - yay!

;-)

 

 

[sd_kirk]

2 minutes ago, datacommando said:

 

Hi, 

 

During the process of updating the firmware in your Helix lots of settings are restored to the factory defaults. One of the major ones is your "Global" settings. It may not matter if you haven't modified them, but many users do change them and consequently after an update run off to forums to decry Line 6 for having screwed up their hardware.

 

Think of it as a safety net.

 

;-)

 

 

 

I think this is the bit that has confused me - if the global settings had been reset to factory defaults (which I was expecting to happen having read about the update before carrying it out), then I would have gone back through the instructions, spotted my mistake and reloaded the back up, but as all the global settings retained my adjusted settings I didn't double check.

 

Maybe it just depends what you're updating to / from or something, but needless to say I'll be more careful next time!  Better safe than sorry...

[HonestOpinion]

On 7/10/2020 at 9:52 AM, sd_kirk said:

 

I think this is the bit that has confused me - if the global settings had been reset to factory defaults (which I was expecting to happen having read about the update before carrying it out), then I would have gone back through the instructions, spotted my mistake and reloaded the back up, but as all the global settings retained my adjusted settings I didn't double check.

 

Maybe it just depends what you're updating to / from or something, but needless to say I'll be more careful next time!  Better safe than sorry...

 

An upgrade that retains the global settings cuts down on a huge number of errant "my HX device is broken or different from before the upgrade" support calls and posts. Although the restore of the global settings may have been Line6's only objective and the only reason they posted that in the update instructions I did not make that assumption. You will notice they did not instruct you to uncheck your user/factory setlists(that is a restore option) and only restore the global settings.  For all I know there might have been some additional piece of processing that ensured a smoother upgrade on your setlists if they were restored as well.

 

I actually was curious as to whether the intent was just the globals or if restore was also necessary for reprocessing the presets to be compatible with the new firmware when I saw the instructions on my last upgrade. Without more detailed guidance from Line6 I try to follow the upgrade instructions to the letter. Since Line6 did not include  the reason for the restore, that included the setlists/presets.

[Phase100]

HX Stomp

 

I too am having tuner problems like those reported on pages 45 and 50 of this thread. When I enter Tuner mode shortly after booting the pedal, the Tuner sometimes does not register any signal. I have to reboot and then wait 20-30 seconds before touching any switches. This problem began after I updated to 2.9 and continues now after an update to 2.92.

[Cmv120]

My helix keeps automatically turning the tuner on when Im in my DAW and I have 0 clue why. It randomly started one night in the middle of a recording session and hasn't gone back to normal. It doesn't do this when Im not in the DAW, only in the DAW. Ive tried updating it, Ive tried downgrading it and then updating it again. Ive tweaked the tempo/tap send and receive settings. I cant get in touch with customer service and when I texted the customer service people I got no reply. I cant record while the tuner is on. Someone please explain what is going on and how to fix it. Ive been heavily discouraged. 

[datacommando]

6 hours ago, Cmv120 said:

My helix keeps automatically turning the tuner on when Im in my DAW and I have 0 clue why. It randomly started one night in the middle of a recording session and hasn't gone back to normal. It doesn't do this when Im not in the DAW, only in the DAW. Ive tried updating it, Ive tried downgrading it and then updating it again. Ive tweaked the tempo/tap send and receive settings. I cant get in touch with customer service and when I texted the customer service people I got no reply. I cant record while the tuner is on. Someone please explain what is going on and how to fix it. Ive been heavily discouraged. 

Hi,

 

I understand you are not happy with the issue of the tuner stopping you from recording, but when you are seeking assistance from other users, it helpful to us to know exactly what computer configuration, OS and DAW you a having this issue with.

 

There are too many options to simply guess what is causing this problem. Sadly, we also have zero clue, therefore no one here can help without this information.

 

Hope this helps/makes sense.

[jdomine]

6 hours ago, Cmv120 said:

My helix keeps automatically turning the tuner on when Im in my DAW and I have 0 clue why. It randomly started one night in the middle of a recording session and hasn't gone back to normal. It doesn't do this when Im not in the DAW, only in the DAW. Ive tried updating it, Ive tried downgrading it and then updating it again. Ive tweaked the tempo/tap send and receive settings. I cant get in touch with customer service and when I texted the customer service people I got no reply. I cant record while the tuner is on. Someone please explain what is going on and how to fix it. Ive been heavily discouraged. 

 

This sounds like your DAW is sending MDI CC 68 to the Helix to activate the tuner. Try changing the midi channel in the global settings on the Helix. You can also use a midi message monitor to see if you daw is sending CC 68.

[dheran]

Hello all. I've noticed a weird thing about the multi band compressor. While playing a few chords with my acoustic guitar (through a looper block), and having the multiband comp with all three bands at 0db threshold and gain (supposedly no compression at all), the sound clearly differs when comp is on or off. When on, the midrange honkiness goes away. However, the meters show no compression (as it's supposed to be).

 

If I do the same with other blocks, there is no change in the sound... But the multi band comp makes that colouration. Is this normal?

[chrisakinhan]

5 hours ago, dheran said:

Hello all. I've noticed a weird thing about the multi band compressor. While playing a few chords with my acoustic guitar (through a looper block), and having the multiband comp with all three bands at 0db threshold and gain (supposedly no compression at all), the sound clearly differs when comp is on or off. When on, the midrange honkiness goes away. However, the meters show no compression (as it's supposed to be).

 

If I do the same with other blocks, there is no change in the sound... But the multi band comp makes that colouration. Is this normal?

 

There are both "Level" and "Gain" settings as well that can boost or reduce volume. That may be what's happening when the pedal comes on.

[dheran]

22 minutes ago, chrisakinhan said:

 

There are both "Level" and "Gain" settings as well that can boost or reduce volume. That may be what's happening when the pedal comes on.

Yes, forgot to say that level control was at 0db too. The block shouldn't have any effect with my settings. BUT, I think the only thing going on is a level loss of about 4 db. If I add those 4db to the level parameter, thinks seem to be right. Maybe the level is mostly remarking that mid frequencies.

 

So the question should've been: did anyone noticed that 4db loss in level through the multicomp?

[Cmv120]

On 8/17/2020 at 6:29 PM, jdomine said:

 

This sounds like your DAW is sending MDI CC 68 to the Helix to activate the tuner. Try changing the midi channel in the global settings on the Helix. You can also use a midi message monitor to see if you daw is sending CC 68.

Hey thank you, I will check this. And for the other guy before you I am using a Mac mini OSX.. and Logic Pro X. Sorry I forgot to mention that. Also sorry I was so pissed hahahaha 

[datacommando]

2 hours ago, Cmv120 said:

Hey thank you, I will check this. And for the other guy before you I am using a Mac mini OSX.. and Logic Pro X. Sorry I forgot to mention that. Also sorry I was so pissed hahahaha 

Hey, the MIDI CC 68 could well be the solution to your problem. Also, I fully understand the annoyance of the tuner kicking in unexpectedly, but as you said that this started “randomly” during a session, there could well have been other factors involved.
Knowing your OS and DAW can help narrow the field when troubleshooting mysterious glitches.

Hope this helps/makes sense.

Let us know how it goes.

Good luck

[fremen]

Wondering if someone here experienced such a bug :

Yesterday I helped a customer to install presets & user cabs (he purchased my presets) via Team Viewer and HX Edit - we're in different countries. His Helix is under firmware 2.92, my presets 2.82. Impulses installation went well, however, there was some bug while installing the presets : Their names on the HX Edit editor panel were fine, but the left part, with the presets list, was still displaying the names of the presets that has been overwritten. There was also an error message, see the screenshot. In some cases, the original presets stayed, despite being overwritten with new presets. Is that a known bug ?