Helix Bug Reports

[SaschaFranck]

And to bring this to an end, here's an MP3. A duplicated (not doubletracked) guitar track. Original recording and a re-amped version playing simultaneously. 2 bars aligned and 2 bars with 2ms offset for the reamped version (which is the offset you'd get when reamping through a physical amp with the Helix under macOS).

Tight vs. phasey mud.

In case that doesn't bother you and you still fail to see the reason why recordings should be lined up properly (even if 2ms aren't noticeable in the timing realm for most humans, which I never even argued with), well, more power to you. Or maybe you're just saying the Helix shouldn't be used for reamping purposes. I must have misunderstood some of the Line 6 marketing then.

2ms.mp3

[PeterHamm]

It's the "face mite" of bugs...

 

[phil_m]

7 hours ago, SaschaFranck said:

And to bring this to an end, here's an MP3. A duplicated (not doubletracked) guitar track. Original recording and a re-amped version playing simultaneously. 2 bars aligned and 2 bars with 2ms offset for the reamped version (which is the offset you'd get when reamping through a physical amp with the Helix under macOS).

Tight vs. phasey mud.

In case that doesn't bother you and you still fail to see the reason why recordings should be lined up properly (even if 2ms aren't noticeable in the timing realm for most humans, which I never even argued with), well, more power to you. Or maybe you're just saying the Helix shouldn't be used for reamping purposes. I must have misunderstood some of the Line 6 marketing then.

2ms.mp3

 

Just to be clear, are you using the downloaded Mac drivers or the Core Audio driver?

[SaschaFranck]

41 minutes ago, phil_m said:

 

Just to be clear, are you using the downloaded Mac drivers or the Core Audio driver?

The downloaded ones. Otherwise HX Edit wouldn't even work.

 

Fwiw, too bad, because 2.7/2.8 broke class compliance under OSX, so I can't use the Helix with my old MacBook.

[reginaldStjohn]

Having corrupted presets here. Using Helix Edit 2.82 and matching firmware form my helix floor. I had some presets be corrupted. Names all weird. I can't do anything with them. So I exported the setlist and tried to re-import it. It seemed to import fine but then bigger blocks of presets are now corrupted.  I am going to try to do  global reset but I am afraid my saved presets might be corrupted as well.  

 

Now when I load a setlist it stops with my Helix and the Helix screen goes blank. I have to restart it and it rebuilds presets.

 

I have noticed others in the forum with similar issues. Has Line 6 had a trouble/bug report logged for something like this?

 

 

 

 

[SaschaFranck]

2 hours ago, reginaldStjohn said:

I have noticed others in the forum with similar issues. Has Line 6 had a trouble/bug report logged for something like this?

 

I think corrupted presets and setlists are on Line 6s agenda. Or well, let me put it that way: If they weren't, it'd be just horrible. IMO the corrupted preset/setlist issue (which is absolutely wellknown) is by far the most horrible thing in Helix land. I can safely say that in case this doesn't get fixed and happens more than just 1-2 times over the next months or so, I will go for another modeler. If anything, I need my tools to work reliably. And as many people are saying the Helix is a computer, so you should expect the same things as from a computer - well, yes please. My computer never corrupts files out of the blue.

 

 

 

 

[brune]

Bonjour la communauté
, Désolé pour mon anglais aproximatif. Je suis Français. J'expose ici, un problème, désormais récurrent, malgré les nombreux Maj, que j'ai toujours fait scrupuleusement, et que j'ai depuis un certain temps pour ne pas dire un certain temps, avec "les offres de configurations midi" en hélice. .... J'ai un plancher hélicoïdal et j'essaye de contrôler quelques fonctions basiques midi d'un microkorg xl + via l'hélice. Procédure. 1-Par preset, je lance un changement de programme (switch instantané PC, utilisation de l'onglet du bas = nombre simple x) + 2 ou 3 notes midi avec le switch 8/9 + CC (CC6 on / off l'arpégiateur et CC 64 Old fonction) avec le switch 10/11 tout ça vers le korg .. (je pense avoir compris le fonctionnement du comand center .. affectation midi pour preset ou snapshot ...) 2- Problème: l'affection du contrôleur ON / OFF de l'arpégiateur Korg (commande midi CC6) à un comportement erratique et plus aléatoire 'EX: Il faut une fois le preset chargé du Korg via l'hélice, actionner manuellement le bouton de l'arpégiateur (korg) donc que la "connexion-reconnaissance" avec le commutateur dédié, CC6 de l'hélice, (malgré la sauvegarde du preset avec l'arpégiateur ON sur le Korg). Ça ne marche plus pour l'usage ... BOGUE sur Bug pas de stabilité .... Désolé .. mais ça fait ... Plus que dingue ..., un autre résultat fatal de ce comportement, les notes, avec la mauvaise fonction du cc6, restent bloqués .... De plus, le commutateur Notes affecté s'allumera momentanément ou pas du tout. Je suis en quart de travail 2.82. J'ai également réinitialisé l'hélice via les commutateurs 9 et 10, rien n'a changé. ... Finalement, J'ai tenu et j'ai pris le risque de faire un concert hier avec une telle configuration. ..C'était dire. ... Les mots me manquent pour écrire mes ennuis ...;) ... Merci d'avance, pour tout partage d'expériences midi helix et toute aide ..

[MatthewMcGhee]

I'm using Helix Floor on 2.82. I'm in stomp box mode and every few times I change patches some of the patch names will remain replacing the stomp box names. Any tips? 

[AppleTreeChen]

Why does this happen?

[datacommando]

On 12/9/2019 at 3:11 AM, AppleTreeChen said:

Why does this happen?

 

That looks to me like some sort of glitch.

 

I would suggest that you make sure that you have a backup of all your presets etc., them perform a reset on your hardware to see if the glitch is cleared. If a reset doesn’t work, then your other option is to raise a ticket with Line 6 support.

 

It also helps to know what firmware revision you are using and if this is only a problem with the hardware or is the HX Edit display also screwed up?

 

Backup and then try a reset x these are your options:

 

HX Stomp

Button Combination	Description
All 3 Footswitches	Clears all presets/IRs
FS1+2	Resets presets and IRs
FS 2+3	Factory restore (globals, presets, IRs)

 

 

 

 

[osios]

Firmware: Firmware 2.82
Bug: When I edit some preset/snapshot settings the main control knob stops responsing to press after some (not always the same) time. It starts working again after I save the preset/snapshot.

Note: If this is the intention, it would be nice to show it to user on display like "You have to save, before continue." 

[AppleTreeChen]

On 2019/12/10 at PM11点26分, datacommando said:

 

在我看来，这有点像小故障。

 

我建议您确保已备份所有预设等，它们会在您的硬件上执行重置，以查看是否清除了故障。如果重设不起作用，那么您的另一选择是在第6行支持下加票。

 

它还有助于了解您正在使用的固件版本，以及这仅仅是硬件问题还是HX Edit显示屏也被拧紧了？

 

备份然后尝试重设x这些是您的选择：

 

HX践踏

按钮组合	描述
所有3个脚踏开关	清除所有预设/ IR
FS1 + 2	重置预设和IR
FS 2 + 3	恢复出厂设置（全局，预设，IR）

 

 

 

 

Thanks, the 2.82 firmware has been reinstalled and everything is ok now

[AppleTreeChen]

On 12/12/2019 at 8:56 AM, AppleTreeChen said:

Thanks, the 2.82 firmware has been reinstalled and everything is ok now

Very depressed. Despite resetting the firmware, the same failure occurred again and again

[tochiro]

I experienced a bug with my Helix at my latest gig Friday night - My foot switches are all in snapshot mode and when I changed from one preset to another the switches kept the snapshot names of the previous preset, although the name of the preset changed to the new one on the screen.

[datacommando]

On 12/16/2019 at 4:35 AM, AppleTreeChen said:

Very depressed. Despite resetting the firmware, the same failure occurred again and again

 

Because this is still happening after reinstalling the firmware it may indicate there is a hardware issue. Contact Line 6 Customer Support and raise a ticket. If it is quite new it may be possible to return it to the store you bought it from and have them swap it for a new one that works correctly.

 

Sorry, you are unhappy about the situation, but occasionally things go wrong.

[MatthewMcGhee]

On 12/16/2019 at 4:36 AM, tochiro said:

I experienced a bug with my Helix at my latest gig Friday night - My foot switches are all in snapshot mode and when I changed from one preset to another the switches kept the snapshot names of the previous preset, although the name of the preset changed to the new one on the screen.

 

Did you figure out any solution to this? I'm hoping mine doesn't do this during a gig. I've been experiencing the same thing. 

[Chris-7777]

 

On 11/29/2019 at 10:04 AM, SaschaFranck said:

Helix Floor as an audio interface causes a negative recording offset of 90 samples at 44.1kHz on USB 1/2 or 7/8 (empty preset, but that shouldn't matter). So all recordings will be delayed by around 2ms.

Some (maybe most by now) sequencers allow for a global compensation of such offsets, in case someone cares and wants to look it up.

Should be corrected on a driver level by Line 6, though.

 

 

On 11/30/2019 at 11:49 AM, SaschaFranck said:

Version 2)

Or are you entirely bypassing the Helix' hardware and rerouting the USB "stream" internally? You know, the "hardware Send in Reaper" part is a little confusing - I'm not familiar with Reaper, is that a Reaper terminology to integrate additional I/Os or are you refering to the Helix' sends?

Anyhow, in case you were bypassing the Helix' hardware, yet sort of emulating a hardware environment within Reaper by utilizing the additional USB routing options as kinda virtual audio cables, then your assumption might be correct.

 

I am for now assuming that (2) is what you meant.

However, whether the 90 samples in your example (which would match the value I've seen in opposite order) are "proving" that this is a defined value the Helix will have to report to the host regardless of platform is beyond me. It might as well just be coincidental. In case it's not a coincidence, it could of course tell us that the ASIO driver for Windows is in fact reporting the correct values to the host (which would be what you concluded already) so recordings are lined up properly whereas the Core Audio version comes with an offset.

Could you do the same test I did, just re-recording something from the Helix' main out into the guitar in and compare things again? In case these recordings would line up properly, we should've nailed down the culprit, namely the Core Audio driver (which may or may not be of informational value for Line 6).

 

I am experiencing a recording offset with Logic Pro X, too. I am sending a DI track (sine wave, in this case) to USB 3/4 of the Helix and record USB 1/2 to a new audio track (empty preset). This is the re-amplification method according to the Helix manual. As you can see in the screenshot, there is a negative offset in the re-amped track. Through adjusting the Logic recording offset settings in the audio preferences by trial and error, I determined the offset to be -28 samples.

[guitphil]

On 12/16/2019 at 6:36 AM, tochiro said:

I experienced a bug with my Helix at my latest gig Friday night - My foot switches are all in snapshot mode and when I changed from one preset to another the switches kept the snapshot names of the previous preset, although the name of the preset changed to the new one on the screen.

 

10 hours ago, MatthewMcGhee said:

 

Did you figure out any solution to this? I'm hoping mine doesn't do this during a gig. I've been experiencing the same thing. 

 

Fwiw, I had a freakout issue with switches going a little haywire during last gig.  I have my Helix Floor setup to run in snapshot mode (8 buttons) and Bank up/down.  What I did was switch the global settings to up/down buttons = presets so I could just advance through my presets by song according to set list.  For whatever reason it was not advancing correctly so I switched back to bank up/down mode and every time I would tap on the bank switches it would go to the last bank no matter which bank I was currently on.  In addition to that, the mode button (#6, top row counting from left to right), was dead.  i.e., I could not toggle between stomp and snapshot mode.  Fortunately for me, the particular gig only required me to hit snapshots which I've programmed extensively.  The latter problem of the mode switch (#6) wasn't revealed until I fired the unit up at home to troubleshoot and try to get it configured correctly.

 

Where I'm at now with this issue is I backed everything up and did a reset (the button 5 & 6 one) and that got all the switching back to normal and the mode button is working again.

 

Next I went ahead and updated HX Edit and my Helix Floor from 2.81 to 2.82.

 

I've got some Christmas gigs, BIG ones starting tomorrow and then a couple worship services on Christmas Eve so I'm spending some quality time running it through the paces to make sure it is working properly.  At last gig where the button chaos happened I'm just really glad I wasn't in a situation where I had to go to stomp mode.  Love this thing and when it's working right it is truly amazing but when stuff like this happens it can be a disaster.

[Chris-7777]

On 12/22/2019 at 10:42 AM, Chris-7777 said:

I am experiencing a recording offset with Logic Pro X, too. I am sending a DI track (sine wave, in this case) to USB 3/4 of the Helix and record USB 1/2 to a new audio track (empty preset). This is the re-amplification method according to the Helix manual. As you can see in the screenshot, there is a negative offset in the re-amped track. Through adjusting the Logic recording offset settings in the audio preferences by trial and error, I determined the offset to be -28 samples.

 

I stand corrected. I did more tests, and the recording offset seems to be bigger. I also noticed that in the MacOS Audio MIDI Setup, the Helix Ins/Outs sample rate is set to 44.1kHz, while in the Helix global settings it is 48kHz. I can not change the sample rate in the MacOS Audio MIDI Setup, but in the Helix Global Settings. I re-amped the sine wave with two different sample rate settings, and that leads to a different recording offset.

 

Helix Ins/Outs Sample Rate 48 kHz (MacOS Audio MIDI Setup: 44.1kHz)

 

Helix Ins/Outs Sample Rate 44.1 kHz (MacOS Audio MIDI Setup: 44.1kHz)

 

 

The negative offset is significant in both cases, and in the latter example it causes phase cancellation that is audible, obviously. 

I am on the latest Helix driver (Line 6 Helix Driver 1.0.7), which I downloaded and re-installed two days ago just to be sure.

[datacommando]

On 12/30/2019 at 9:14 AM, Chris-7777 said:

I also noticed that in the MacOS Audio MIDI Setup, the Helix Ins/Outs sample rate is set to 44.1kHz, while in the Helix global settings it is 48kHz. I can not change the sample rate in the MacOS Audio MIDI Setup, but in the Helix Global Settings.

 

Hi Chris,

 

Try installing the Helix Mac Driver 1.0.7 once again to access the higher sample rates - download it from here:

https://line6.com/software/index.html

 

Here you see can Mac Audio MIDI Setup and Logic ProX have access to the higher rates (the italic numbers in LPX mean that the rate is unavailable) - attached pix.

 

 

 

 

 

 

 

I know it doesn't help with the "out of phase" thing, but hope it helps in other ways.

 

[Chris-7777]

Thank you. I do see these sample rate options in the Audio MIDI Setup, but everytime I tried to set it to something else than 44.1kHZ, it bounced back to 44.1. It did not seem to matter what the sample rate setting in the Helix global settings menu was, btw. What I just noticed is that this happens only when Logic Pro X is running. In any case, as you said, it does not help with the recording offset.

 

[phil_m]

On 12/30/2019 at 3:14 AM, Chris-7777 said:

 

I stand corrected. I did more tests, and the recording offset seems to be bigger. I also noticed that in the MacOS Audio MIDI Setup, the Helix Ins/Outs sample rate is set to 44.1kHz, while in the Helix global settings it is 48kHz. I can not change the sample rate in the MacOS Audio MIDI Setup, but in the Helix Global Settings. I re-amped the sine wave with two different sample rate settings, and that leads to a different recording offset.

 

Helix Ins/Outs Sample Rate 48 kHz (MacOS Audio MIDI Setup: 44.1kHz)

 

Helix Ins/Outs Sample Rate 44.1 kHz (MacOS Audio MIDI Setup: 44.1kHz)

 

 

The negative offset is significant in both cases, and in the latter example it causes phase cancellation that is audible, obviously. 

I am on the latest Helix driver (Line 6 Helix Driver 1.0.7), which I downloaded and re-installed two days ago just to be sure.

 

I'm wondering if this isn't so much a bug but rather just a side-effect of doing this sort of re-amping completely in the digital realm. I just tried this in Reaper on Windows 10, and I get a slight negative offset for the re-amped track as well. I think what's happening is that the driver is telling the DAW to compensate for latency from the converters, but in this case the converters aren't coming into play since the input for the preset is coming over USB. I don't know that there would be anything in the driver that would be able to tell the DAW what input the Helix is actually using for any given preset, so it may just be something that you have to correct manually by sliding the track over.

[MatthewMcGhee]

On 12/8/2019 at 3:49 PM, MatthewMcGhee said:

I'm using Helix Floor on 2.82. I'm in stomp box mode and every few times I change patches some of the patch names will remain replacing the stomp box names. Any tips? 

I did a full reset and restore from backup. All was fine for a week or so but it happened again. Must be something with the firmware. The word “Cancel” comes on the upper right switch and if you hit it it usually corrects this issue. I hope they address it. Not fun to be on stage and have this happen. 

[Chris-7777]

14 hours ago, phil_m said:

 

I'm wondering if this isn't so much a bug but rather just a side-effect of doing this sort of re-amping completely in the digital realm. I just tried this in Reaper on Windows 10, and I get a slight negative offset for the re-amped track as well. I think what's happening is that the driver is telling the DAW to compensate for latency from the converters, but in this case the converters aren't coming into play since the input for the preset is coming over USB. I don't know that there would be anything in the driver that would be able to tell the DAW what input the Helix is actually using for any given preset, so it may just be something that you have to correct manually by sliding the track over.

 

Good point and great advice, Phil. It is also good to know that this occurs in another DAW, too. I am still puzzled because the Helix sample rate settings do seem to affect the recording offset. It might also be that I am not experienced enough to know that there always will be an offset and that I have to adjust re-amped tracks accordingly. If this can't be solved through improving the drivers, a hint in the Helix manual would be tremendously helpful.

[pinetrax]

under global settings in my Helix, 2.82.0, i have    MIDI PC Recieve     turned off, yet, when i switch guitar sounds on my variax, helix sends those patch changes out to my computer, this needs to work correctly please., 

[phil_m]

33 minutes ago, pinetrax said:

under global settings in my Helix, 2.82.0, i have    MIDI PC Recieve     turned off, yet, when i switch guitar sounds on my variax, helix sends those patch changes out to my computer, this needs to work correctly please., 

 

Set MIDI Over USB to Off in Global Settings.

[kkinerk_line6]

On 12/7/2019 at 5:29 PM, reginaldStjohn said:

Having corrupted presets here. Using Helix Edit 2.82 and matching firmware form my helix floor. I had some presets be corrupted. Names all weird. I can't do anything with them. So I exported the setlist and tried to re-import it. It seemed to import fine but then bigger blocks of presets are now corrupted.  I am going to try to do  global reset but I am afraid my saved presets might be corrupted as well.  

 

Now when I load a setlist it stops with my Helix and the Helix screen goes blank. I have to restart it and it rebuilds presets.

 

I have noticed others in the forum with similar issues. Has Line 6 had a trouble/bug report logged for something like this?

 

 

 

 

 

Brand new Helix.  2.82 and I am experiencing this exact same issue.  

[reginaldStjohn]

Send in a support ticket so they are aware of it.

[pinetrax]

On January 2, 2020 at 11:54 AM, phil_m said:

 

Set MIDI Over USB to Off in Global Settings.

no, i use usb to send patch changes from helix, as well as continuios controllers, i was able to filter the patch changes Variax sends out in my program, but this still needs to work as advertised.

[pinetrax]

On January 2, 2020 at 11:54 AM, phil_m said:

 

Set MIDI Over USB to Off in Global Settings

[pinetrax]

no, i send patch changes and cc messages from helix, i was able to filter out the patch changes on channel 16 using my program, but this should work as advertised.

 

also, snapshots in 2.8.2 are buggy as hell with my variax 500, not recalling or displaying or both the different variax guitar models.

[phil_m]

27 minutes ago, pinetrax said:

no, i use usb to send patch changes from helix, as well as continuios controllers, i was able to filter the patch changes Variax sends out in my program, but this still needs to work as advertised.

 

Well, it was advertised, kind of. There was a note in the release notes for the 2.21 firmware when they added the Workbench HD support.

 

- If a Variax guitar is connected to Helix, MIDI channel 16 should never be used, as channel 16 is how Variax Workbench communicates with the guitar. This is by design. On a related note, Variax Workbench should never be used while MIDI tracks are armed or playing back in your DAW

[pinetrax]

still should be able to disable it if you want

[MatthewMcGhee]

So I came across a different bug today. I changed patches (stomp box mode) and all the names of the bottom stomps were gone. I wasn't able to change patches or anything after this. I had to power down the unit and restart it. This would be terrible if it happened on stage. Any suggestions? I just did a full factory reset a few weeks ago. How do I get a response from Line 6? 

[Racknee]

I encountered a possible bug during programming snapshots with different imput impendance.

 

1)I set snapshot 1 with 10K impendance on input block, going into fuzzface.

2)I set snapshot 2 with 1mil impendance, fuzz is bypassed.

3)When I switch between the two snapshots, everything is ok.

4)Save whole preset while snapshot two is engeaged.

5)Test it again, switching between two snapshots is fine.

6)Switch into different preset and then back to this one.

7)Test it again and here it is - when you load the preset at first you arrive on snapshot 2 with 1mil impendance - as it should be. But..

8)When you switch to snapshot 1 and back to snapshot 2, snapshot 2 is now set to (default) "auto impendance", not 1mil. Going back and forth, snapshot 1 stays saved at 10K as it should, but the one you first arrive at when you load the preset resets to "auto".

 

Helix LT at 2.82.

[swanny8777]

46 minutes ago, Racknee said:

8)When you switch to snapshot 1 and back to snapshot 2, snapshot 2 is now set to (default) "auto impendance", not 1mil. Going back and forth, snapshot 1 stays saved at 10K as it should, but the one you first arrive at when you load the preset resets to "auto".

 

Helix LT at 2.82.

 

I don't have my Helix in front of me to know for sure, but I've encountered a similar bug with delays, reverbs, and amp settings:  pretty much anything that I set to utilize snapshot parameters.  I don't have a solution to my problem, nor yours, but I have dug and seemed to see what may be one of the issues.  The .hlx file that presets are saved as are nothing more than text files using JSON formatting, which just means you can open the .hlx file in a simple text editor to view preset information on your computer if you've used HX Edit to save it from your Helix to your computer.  When you look at the file there's quite a bit of information, that can be broken down as follows (picture a tree that branches off into more detailed branches):  a data field which leads to a tone field which has several different fields under it:  dsp0, dsp1, snapshot 0, snapshot1, snapshot 2 (thru snapshot7, which would be your 8th snapshot), global, and controller.  Basically, the information is stored to tell your Helix what the preset should load when you switch to it on the hardware, and there is separate information stored for each snapshot that you have saved in the preset.  

 

Let's for the sake of argument say that the preset is saved so that when we switch to it, it loads on snapshot 8.  When it loads the preset (and subsequently snapshot 8), it loads everything correctly because the default information for the preset stored under dsp0, dsp1, global, and controller are correct (it stores the information in these fields based on what blocks were on/off, where parameters were, etc. when you hit save), however, even if I change to no other snapshot, but merely hit to go back to snapshot 8, I might find that instead of the channel volume on my amp block being set to a hypothetical [5.0], I might find that it jumps to [0.0] or [10.0].

 

 When I peeked into some of the preset files that were giving me errors I found that the default figures were correct (as mentioned above), but when I go to the dropdown for snapshot7 (snapshot 8 on the hardware), and cruise down to the block info for my amp (in my case, block6) and look at the ChVol parameter, I see be saved as either 0, or some number greater than 1.  Here's why this last part is important, the .hlx file saves values as very long decimals, so my default preset value for amp channel volume (and also preset7) should be 0.5 to give me the volume of [5.0] I'd expect to see, but it may be something like 0.49999998275 or 0.50000001023 to still yield the same result of the channel volume being at [5.0].  I have found that when I experience errors with snapshot values (for instance, channel volume drops to [0.0] or [10.0] when I switch to the snapshot), the saved value in the .hlx file may be 0.0 (resulting in [0.0] when selecting the snapshot) or something strange like 45 (resulting in [10.0] when selecting the snapshot--remember that to get this value the saved value would only need to be 1.0 or even 0.9999 or something similar).

 

That is A LOT to say this:  I bet if you open your .hlx file, or share it with me so I can check it out, if "auto" is the minimum or maximum setting you can have for your snapshot value, then you may be experiencing a similar bug.  I have reached out to Line6 about this before and I guess because it didn't happen to them when building presets (even though they could open my preset, either on an actual Helix unit, or by observing the .hlx file internally), they kind of just brushed it off as a corrupt preset, which may be all that it is.  So I have rebuilt presets before when dealing with this issue, but it also makes me VERY leery of using snapshots at times.  You may need to rebuild your preset, or you can manually adjust the level in the .hlx file, save it, and reload it into your Helix (the latter idea makes some people nervous thinking that it might brick their unit, but anyone with any IT background I know say that this is highly unlikely if at all, so if that makes you nervous, just rebuild the preset from a New Preset and save over your trouble preset).  Hope this helps, sorry for the book I gave you to read lol.

 

If you'd rather see me coming to these conclusions in real time, here's a video:

 

[TV-OD]

Hi, i had a strange time with my Helix floor last night at band practice, I tried to select a preset i have not used for a good while and my Helix freaked out, it fail to show the scribble strips and then the screen went black like it had switched off, it came back on then blank screened again. so I switched the Helix off and on and it was ok after that. I have noticed in the past that sometimes when i select a preset the scribble strips are totally wrong like from another preset or they are just blank, i have to re select that preset again to fix the issue. I gig with my Helix most weekends, i can deal with just re selecting a preset, but blank screen and shut downs will be a problem, anyone else having these issues.

 

Cheers Roy

[otnooishphoo]

Tempo Sync Delays are broken on multiple delay models.  1/1 1/2 1/4  etc are ALL always 8th notes.

 

 

[PeterHamm]

47 minutes ago, otnooishphoo said:

Tempo Sync Delays are broken on multiple delay models.  1/1 1/2 1/4  etc are ALL always 8th notes.

 

 

Latest firmware? I haven't seen this. Which models may I ask?

[MatthewMcGhee]

On 1/30/2020 at 1:17 PM, TV-OD said:

Hi, i had a strange time with my Helix floor last night at band practice, I tried to select a preset i have not used for a good while and my Helix freaked out, it fail to show the scribble strips and then the screen went black like it had switched off, it came back on then blank screened again. so I switched the Helix off and on and it was ok after that. I have noticed in the past that sometimes when i select a preset the scribble strips are totally wrong like from another preset or they are just blank, i have to re select that preset again to fix the issue. I gig with my Helix most weekends, i can deal with just re selecting a preset, but blank screen and shut downs will be a problem, anyone else having these issues.

 

Cheers Roy

This has happened to me as well for months now. They just tell you to do a global reset but that still doesn’t solve the problem. Mine completely locked up the other day. I had to do a power cycle. I’m on the newest firmware and did a complete reset a few weeks ago.