jdomine

On 11/25/2023 at 8:29 AM, datacommando said:

 

Hi,

 

Yes, I just checked with my Helix floor and it does appear that the Glitch Delay is suffering from some sort of "glitch". Obviously, as the update is exactly the same, this also affects Helix Native.

The thing that is really strange about this is, I loaded up an old project that featured a "Glitch Delay" into Logic Pro which had both a fully processed stereo recording along with a dry mono version of the track. I set Helix Native to play back using the same preset that I had used in the Helix. Cross fading between the original and the re-amped Native track, they seemed identical, until I made any change to the Time or Delay Divisions, etc., within Native then the Glitch Delay would not function as expected and went screwy.

 

I then tested the same preset in Helix, which seemed to work fine until, once again, any change made to any of the parameters would push it off kilter and make it unusable.

 

I am going to raise a ticket with support regarding this and suggest that anyone else who encounters this should do the same. The more reports, should make for a quicker fix - the squeaky wheel, etc.

 

 

 

 

Hello. I can confirm there is some sort of issue with the Glitch Delay in 3.70. Comparing it side by side to 3.60, it is very obvious. On 3.70 after changing the Time parameter to Note divisions it seems to essentially stop working completely. I have attached audio examples of what I'm hearing. Do they line up with what you're experiencing?

I have logged a bug for this. It will be addressed in a future firmware update.

Thank you for the report.

On 5/26/2023 at 10:26 AM, dav1dmaes said:

Command center settings are not copied correctly when you copy a preset.

Alright, so you this one is a ffffd up one, because there is a chance you don't see it until you're on stage and your equipment will not do what you expect it to.

I'm using:

    Helix Rack
    Helix controller
    Mission Line 6 pedal (the crybaby thingy)

Here is how to reproduce:

    Make a few snapshots I use 1-6
    Use the command center to make the EXP toe switch switch between snapshots
    Make this different for every snapshot:
        snapshot 1 goes to 4
        snapshot 2 goes to 5
        snapshot 3 goes to 6
        snapshot 5 goes to 3
    Note that you have to both set press AND release to these settings as it otherwise won't work at all
    Test your setup and make it switch between snapshots.
    Now copy the preset to another preset (I did this via HX edit)
    Be amazed at the fact that no matter which snapshot you're in, your EXP toe switch will now just use the same value to go to every time. There is no distinction between snapshots anymore.

I really hope you guys fixed this, because I had this happen to me live. And instead of the whammy, it went to wah. I winged it, but ffffing hell, I only realized later it was not me ffffd up during the gig, it was the equipment.

I am able to reproduce this and have logged a bug for it. Please note that this also occurs when exporting/importing a preset or when restoring from a backup. Thank you for the report.

On 6/1/2023 at 8:14 AM, jackwagner said:

An issue that I reported on September 14, 2017 regarding loss of volume over a period of time is back.

 

On 5/26/2023, I update the firmware on my Helix Rack from 3.15 to 3.60. I have a preset for bass that has 2 paths:

 

Path 1 has an input, compressor, amp+cab, compressor, volume, and output blocks. Input come from Return 1; output is MULTI. This path processes the neck pickup from my bass.

 

Path 2 has an input, Mic Preamp, and output blocks. Input comes from Return 4; output is MULTI. This path processes the bridge pickup from my bass.

 

When I select the preset, everything works as expected for a few minutes. After a few minutes (maybe 5 or so minutes), I no longer get any volume from Path 1. I don't really notice that it gets quieter over time, just that any signal/volume from Path 1 is gone after a while. When I switch to a different preset and then back to this preset it works as expected again. For another few minutes.

 

The issue may not have been introduced in 3.6 since I upgraded from 3.15 to 3.6.

 

--jack

Hello Jack,

If you could post the preset here I would be happy to check this out and see if I can also reproduce it.

On 5/1/2023 at 10:10 AM, alighton said:

 

Same here. Driving me nuts.  Updated to 3.6, copied an existing preset with a wah with toe down bypass to make a GSG 100 preset, and now the behavior on every preset with a wah is heel down bypass. Real PITA to fix, have to open every preset, modify, and save.  In the future, before copying a preset with a wah in it to make a new one, I'm going to delete the wah before copying it.  Maybe that will keep the behavior from propagating to every preset.

Hello. I am able to reproduce this. It seems to be an issue tied to HX Edit. If I duplicate a preset by saving it to a new location using the hardware itself, the change to Heel Down does not happen. It only occurs when copying and pasting a preset with HX Edit. I will log a bug for this. Thank you for reporting it.

On 11/4/2022 at 5:34 AM, 52dmk said:

Bug in 3.5 FlexoVibe.

Rate parameter does not have option to change to note subdivision in HX edit, but can press knob on Helix floor to change Rate to note subdivision. This then breaks link between HX edit and Helix floor, with changes made to Rate on HX edit not affecting Rate on Helix floor, and changes made to Rate parameter not changing knob position in HX edit.

Pressing Rate knob on Helxi floor returns Rate to numbered speed and allows HX edit to control Rate parameter again.

Same behaviour occurs for mono and stereo versions.

Good find. I have logged a bug for this and the 4-Voice Chorus. Thanks for reporting it!

2 hours ago, C4TH said:

3.15 update - Using Ext Amp (EXP 2) Instant Commands with My HX Effects, and changing the command from tip, ring or whatever to change amp channels, seems to effect (EXP1) My expression pedal in EXP1 stops working on all presets.

I am able to reproduce this and have logged a bug for it. It seems to go all the way back to 3.00.0 if not further.  It does not seem to happen if you use EXP1 for the ext amp control and EXP2 for expression. For now I would recommend using this configuration as a workaround.

2 hours ago, boynigel said:

I've posted this in the Bugs section too, but figured i'd put it here as well in case any one already knows of a fix:

 

My LT has locked up/froze several times now while trying to get to a certain preset.  The only fix is to reboot and try again, but subsequent attempts yield the same result until I found a workaround.  Here are some details:

 

So far, it only seems to happen when I try accessing a certain preset.  If it matters, the preset I’m going to has a new 3.15 addition, the Tesselator.  In addition, this preset contains Shuffle Looper and some CPU-intensive effects like the Poly Capo.  Safe to say that this preset is on the brink of being “maxed out” in terms of CPU availability…if that could be part of the reason.  That said we ALL have some presets that are maxed, or near-maxed.

 

Here’s how it all goes down-  I’ll be on a given preset and then I’ll use the bank footswitches to get to the back that holds the preset in question.  When I tap the preset’s corresponding foot switch, nothing happens, and then it freezes up.  Doesn’t matter what footswitch or button I press, the screen is locked showing all of my presets in that particular bank.

 

Through trial and error, I’ve found that I can access the preset via the Preset wheel/knob, but there’s just something about using the foot switches that it’s not liking.  Sometimes it lets me, but most of the time it doesn’t.  I know it isn’t the footswitch (that corresponds to the preset) itself, because the switch gives me no issues within other banks.

 

FWIW, this isn’t a case where I had just updated to 3.15, created the new preset, and then all of this started happening.  I updated weeks ago, and created the preset within a few days later, so there’s that. 

If you could email the problematic preset to me at jdomine@line6.com or attach it here I'd like to test this out. 

Thanks guys. I can reproduce this using the attached presets and have logged it as a bug. Appreciate your report!

18 hours ago, lou-kash said:

Bug or a "feature"…?

 

With Poly Pitch block active, it's not being bypassed if I have set my Stomp's global preferences to DSP Bypass type, and activate the latter.

Haven't encountered this with any other block so far, including Poly Capo or Poly Wham.

 

Firmware 3.01.0, no other issues that I'm aware of.

This is indeed a bug. I have logged it for review by the team. Thank you for the report!

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.

On 4/25/2020 at 6:56 PM, droe5577 said:

Same here on LT.  Was working in HX Edit for about an hour, and somewhere along the line everything locked.   Edit could not save the patch to the unit tand the unit was completely unresponsive despite producing tone and responding to edits from HX Effects the entire time.

If you unplug the USB cable after it has become unresponsive does that snap it back into functioning?

33 minutes ago, geetarsparkie said:

I seem to be having an issue with 2.9 that I dont think I've seen anywhere else. Could be mistaken. Apologies if so. 

 

If I start the helix floor with a midi keyboard plugged in via the helix midi in port. It boots as normal the screen comes on then goes off completely and the helix freezes. Restart without midi cable plugged in and it worked fine. So I plugged the midi cable in whilst the unit was on and within 5 seconds or so. The helix screen went back off and the unit froze. Havnt plugged it back in since as doesnt appear to be working and seems to be an issue. Just reporting so someone st Line 6 might be aware of the issue which I've never had in any other previous versions. Thanks

Is your keyboard sending out MIDI clock or any other MIDI data constantly when powered on? Simply having something plugged in via MIDI din should not matter but I could see flooding the MIDI stream with clock and other things could theoretically cause an issue.

I am able to reproduce this easily. I noticed that if I deleted the looper block at the end of path 2B the problem goes away. Do you use that looper at all? If not I recommend deleting it from the preset until the bug is fixed.

The bug seems to be that if you load a preset with a looper on a B path after coming from another preset with a looper on a B path audio stops passing.