silverhead

Here's a test I just did and the result: Systems: Win 11; Helix Rack v3.80; HX Edit v3.82; JTV59 v2.10 (later versions don't apply to JTV59) Settings: Helix Variax Per Preset; JTV59 model Chime 2 (12-string), Standard tuning. Preset #1: anything in standard tuning that's not an Acoustic 1 model Preset#2: Helix model Acoustic 1, Custom Tuning Drop D Preset #3: Helix Model Don't Force; Tuning Don't Force Steps: 1) Select Preset #1 2) Select Preset 2. Confirm that model and tuning are as prescribed by preset 3) Select Preset 3 Expected behaviour: Don't Force settings should allow physical JTV guitar settings to be applied; Model Chime 2 (12 string) in Standard tuning Actual behaviour: Acoustic 1 model in Drop D is retained. My understanding of the term ‘Don’t Force’ is that Helix makes no changes to its current Variax settings. Specifically it does not seem to query the Variax guitar and apply its physical settings. Conclusion: The observed behaviour may be a bug. It may also be design intent. I noticed this years ago but didn’t report it because I assumed it was design intent and there is no documentation refuting that. The manual states: When set to “Don’t Force,” Helix respects the Variax current setting. This is ambiguous to me. Does it mean it respects the currentI Variax setting within Helix, or the physical setting on the guitar? It actually does the former, not the latter, so I presumed it was intentional. @psarkissian Is it worth reporting this since Helix Stadium has been announced? Won't likely be addressed in Helix even if it is a bug.

That's what I initially thought and it makes sense. However, during my testing I recall that the actual behaviour is that the Variax retains its current settings even when Don't Force is specified. It does not seem to revert to the actual physical guitar settings. Perhaps my memory is faulty or it was a bug that has since been fixed. I will do more testing and report back when I have time. Sorry if this causes confusion.

This subject has been confusing for me. Keep in mind that I’m describing my understanding based on my experience in trying to figure it all out in the past. I’m not aware of any official detailed documentation about this.

The Don’t Force setting applied to a Helix preset means that the Helix will make no changes to the existing tuning when the preset is loaded. So yes, it will prevent different tunings from being applied. However it says and does nothing about the existing tuning.

The Custom tuning capability in Helix works in a relative, not absolute, manner. In other words it does not tune each string to the standard EADGBE frequencies. It applies a relative offset to the current string tuning. So a “-2” setting for a Custom tuned string means the incoming string frequency is lowered by 2 frets. If the guitar is currently in standard tuning then a “-2” setting on the 6th string means the adjusted note would be D. However if the guitar is already in Drop D tuning the resulting note would be C. This applies to all strings. The Variax guitar’s Alt Tuning works the same way. When the knob is in Standard position it does not make any adjustments to the actual physical tuning of any string; the assumption is that the guitar is physically tuned to standard. So the Drop D position does exactly what the previous paragraph describes.

Here’s my understanding: What you’ve described will ensure that the Helix processing does not make any tuning changes using that preset. As you mentioned the overall Variax setting should be per preset. That means the tuning you hear is the signal received at the Helix input. Since you’re using a Variax the selected model could already be in an alternate tuning defined in Workbench HD. Or the guitar itself may already be in an alternate tuning.

Yes, it can. Open a support ticket.

Which Helix device are you using?

Make sure your Settings->I/O Config parameter is set to Stereo. See manual for details if necessary.

I think you should open a support ticket. Meanwhile someone who might have experienced something similar may respond here.

You don’t mention having checked the Global Settings on your HX stomp as indicated in my earlier reply. Did you do that?

Sorry. I must have misunderstood.

Eric’s post earlier in this thread states that Focus View will be in the Helix Stadium app.

See Global Settings -> Ins/Outs -> Volume Controls

No but you may need to authorize your computer. Update your Line 6 account to add your new computer and run the Line 6 License Manager utility.

Check to see if there was an associated app update.

If you mean will it receive any further updates the answer is almost certainly no.

Make sure you are logged into your Line 6 account within Helix Native (see bottom left corner of HN window). Then HN will be able to see the license in your account just like you can.

Save to Hardware will overwrite it.

The official way to submit your request is here: https://line6.com/support/discover/unread/- https:/line6.com/company/contact/productfeedback/

Your ‘Hmmm’ suggests you may not be satisfied with the fact of it. But I think the design reflects the fact that a Reverb FX is generally more DSP intensive than your average Delay or Mod FX. Accordingly, allowing more than one Reverb FX would really restrict available remaining DSP for the other Flex blocks. At the end of the day it’s all about DSP capacity, and the Firehawk FX design prevents a second Reverb FX because it would likely cost two Flex FX blocks. The preset would become very handcuffed. Just my assumptions about DSP management reflected in the design.

Where’s Walt’s Trout Hut?

Interesting analogy, but the producer in the studio is capable of creative, non-regenerative, thinking and musical ideas. Will AI-generated songs, being grounded in exisiting material, stand up to copyright issues? Has this been tested in courts yet?

Someone copied your post in a lazy and uncreative attempt to make a first time post here, which requires moderator approval. Their post contains a hidden link (at least really small font) which I expect they hope will drive traffic to an external site. That’s been a recent trend here in moderator world and we try to be on the lookout for it. The post should not have been approved since it violates the Terms of Use here but the link is easily overlooked.

No. The Reverb block is one of the Fixed blocks and you can’t assign a Reverb model to any of the Flex blocks.