rd2rk

I fear that I've been foiled by a dreaded "Thread Priority Bug". Hopefully they'll fix it in v3.11 (3.2? Baffling version numbering system...)

Are you doing this: Push knob and release Joystick left so only the banks are showing Rotate knob to select bank If YES Then do a factory reset. If that doesn't fix it open a support ticket. It's not a bug, as there's no such problem on mine.

Wrong forum. This is where you go if you're serious about suggestions for changes and improvements: https://line6.ideascale.com/a/index Before posting a new idea, please search to see if it's already been proposed. If 100 people vote on the same idea presented 20 different ways, it looks like only 5 people care about it! Also, post your ideas one at a time. I for one NEVER vote for multiple combined suggestions.

Reply to my Support Ticket: From one of our software engineers: âSo this technically does work, but there seems to be some sort of thread priority bug. I am seeing that even when the CC69 is sent after the PC, the actual time it takes to load the preset can be longer than the CC69 being received depending on what is in the preset, which would result in the snapshot not being loaded as expected. Using the wait parameter in command center set to 150ms or higher would avoid the issue. Or if an external device has a wait feature, using it there to send the CC69 to Helix/HX would work as well. To Clarify, it is the CC69 that should be set to wait 150ms or so, not the PC message.â ----------------------------------------------------------------------------------------------------------------------------------------------------- IOW - there's a new WAIT parameter in Command Center, but if using an external controller, it must be capable of adding it's own WAIT command. EDIT: I haven't had a chance to try this yet, but I'm thinking that if you use CommandCenter to assign the Preset/Snapshot load to a FS using the WAIT command, then trigger the FS from the external controller instead of sending the PC and CC, that might work I'll try it later and report back. EDIT EDIT: Of course that doesn't work. What was I thinking? Need more coffee.

Reply to my Support Ticket: From one of our software engineers: âSo this technically does work, but there seems to be some sort of thread priority bug. I am seeing that even when the CC69 is sent after the PC, the actual time it takes to load the preset can be longer than the CC69 being received depending on what is in the preset, which would result in the snapshot not being loaded as expected. Using the wait parameter in command center set to 150ms or higher would avoid the issue. Or if an external device has a wait feature, using it there to send the CC69 to Helix/HX would work as well. To Clarify, it is the CC69 that should be set to wait 150ms or so, not the PC message.â ----------------------------------------------------------------------------------------------------------------------------------------------------- IOW - there's a new WAIT parameter in Command Center, but if using an external controller, it must be capable of adding it's own WAIT command. EDIT: I haven't had a chance to try this yet, but I'm thinking that if you use CommandCenter to assign the Preset/Snapshot load to a FS using the WAIT command, then trigger the FS from the external controller instead of sending the PC and CC, that might work I'll try it later and report back. EDIT EDIT: Of course that doesn't work. What was I thinking? Need more coffee.

Just for giggles I re-flashed my Floor. Although my presets were still there, the Powercab REMOTE setting had changed to OFF. Restoring my backup returned everything to normal though. Don't know about the Variax thing, not a Variax guy and I didn't check it before and after the test. Wonder if that's at least one of the reasons for the specific instructions to backup before and restore after the update? Anyhow nice catch. I don't know why I'd change the Powercab setting from PRESET to OFF or GLOBAL, but nice to know that if I did it would affect ALL my presets.

Did support ever get back to you?

No. Presets open in whatever view is currently active, and Global Settings are...Global.

But he sure can play guitar!

I had to go back and edit the # of blocks I stated in my previous post. My problem - trying to type while playing the new Rockerverb with the new Rat and Dynamic Hall Reverb. I'm effected, effected......

2.5ms is one of those "generally quoted" numbers. It wouldn't make me sad if you were right about it being 1.8ms. I've never measured, as the only thing I use the FX loops for is 4cm on those rare occasions when I break out a tube amp for nostalgia's sake. :-)

Don't know if it's still an issue, but some people have had problems with drag and drop. Just export your Impulses, then import them in Native. Do the same with your setlists.

I'm with the "no" group. As to more snapshots for the HXS, go here: https://line6.ideascale.com/ Do a search and vote for all of the requests placed by those who didn't search first :-)

It's your memory. You need to insert an FX Loop Block to add external FX. The main advantage of the increase from 6 to 8 blocks in v3.0 was that you had two extra blocks for low DSP uses such as FX Loops, essentially accomplishing the same thing.

Each round-trip AD/DA conversion is around 2.5ms. Helix through latency is, IIRC, <2ms. Add the number of conversions +2 for your total latency. IOW - guitar>Helix>amp - one AD/DA conversion + 2ms = <>4.5ms. There's a paper out there somewhere in which they researched people's ability to detect audio latency. 10ms was the threshold for DETECTION, approximately 20ms before it became a bother. The number was lower for singers and horn players due to bone conduction. Also, Steve Vai can detect 2ms. :-) Latency affects the FEEL of playing the guitar. If you're a shredder playing 99 notes per second, it's more likely going to bother you more than someone playing soulful blues.

Sometimes a Windows update will do it too. If you're using Reaper, sometimes after a Reaper update you need to reinstall HX Edit to get the drivers working again. The mysteries of the digital wonderland!

There's a guy in Seattle, WA, named Satya Nadella. He works at Microsoft, some kind of big deal. Send him an email and tell him all about it. I'm sure he cares.

Same problem, same solution. It's just the way Windows works.

Note that this time I didn't include the boilerplate. Some days I care more than others. OP - don't be offended. There's certain things that get brought up constantly, and for those of us who are regulars here, we're only human. :-) The boilerplate includes instruction to do a search first to see if it's already been suggested (it has).

Log in | Line 6 Ideas (ideascale.com)

You've just discovered that you need a full sized Helix. While you can put a HXFX in the FX Loop of the HXS, you're adding the latency of the additional DA/AD conversion (twice if you use both loops), and you still don't have as much DSP as if you had the full sized Helix. Also, by the time you put it all on a pedalboard with the two big Power Supplies and an Exp Pedal (and all those extra cable failure points), how much room have you saved over the full sized Helix? Nor have you saved much money. Get the full sized Helix, you'll be happier down the road. Unless you live on the edge of civilization, you'll have no trouble selling the HXS. If you haven't had it long (but too long to return it), remember that the warranty is transferable.

Assuming everything is still on your Helix, just plug it into the new computer, load HX Edit 3.1, and go!

Don't forget to choose the correct OS.

I've been playing with this for a while now. To make the situation even worse, depending on which preset you're coming from (001-000; 002-000; New Preset-000), sometimes it works, sometimes the SS# on the display flashes the desired SS before switching to either the saved SS or, in some cases, I've seen the display for SS3 flash (or not) before going to SS4! FWIW - I'm running a MIDI Monitor while I test, and my FCB is sending the proper message in every case. Also FWIW - In 3.01, if I placed a WAIT between the PC# and the SS#, it worked fine. I haven't tried this in 3.1. There's a BIG problem with this algorithm.

Confirmed. It does not work. It's supposed to be fixed so that this is not necessary: New and Improved MIDI Implementation Helix Floor, Helix Rack/Control, Helix LT, HX Effects, HX Stomp, HX Stomp XL Switches in Snapshot Footswitch Mode can now have custom labels and colors. MIDI Snapshot changes on CC69 that are received during preset loads will now be buffered and executed once the preset load is finished. This means that you can send a MIDI Snapshot change immediately after a PC message to effectively load a preset with a different Snapshot than it was saved with. EDIT: Support Ticket opened.