silverhead

I suggest you open a support ticket.

The POD Farm VST plug-in uses the same era of Line 6 modeling technology. I don’t know if the modeling is exactly the same but it’s at least very similar. However it is not directly compatible with the Pod XT. You can’t upload an actual XT preset into POD Farm. What you MIGHT be able to do is inspect the XT preset using its editor (not sure what that is, or whether it runs without a physical XT connected) and then manually recreate the settings in a POD Farm preset. I know you like your old XT sounds but the modeling technology has improved a lot since then. If you’re going to be looking at purchasing a plug-in you might consider Helix Native. Most would agree that the sounds are superior to the XT/POD Farm era.

OK - that makes sense now. You're right - those are your basic options, but 4CM offers you the use of either a Helix amp model or your physical amp if you set up your presets appropriately.

If there's no house audio, where does the mic in front of the amp go? Have you considered using the full Helix amp and cab modeling, removing the mic and amp, and connecting the Helix outputs to wherever this mic goes? You could then use an FRFR speaker (not a guitar amp) as your stage monitor, unless wherever that mic goes also supports stage monitors. But then I'm confused, 'cuz there's no house audio....?

I find the sonic quality of the POD Go to be superior to the POD HD series. Others have a different opinion but I think must users would agree on that the POD Go (and Helix) provide better tone. But that alone may not mean you should make the move. A couple of things to consider: - was the HD500X your first experience with a digital modeler? If so I expect that the vast majority of your learning curve was the adaptation from analog to digital. The move to the POD Go will be much easier. On the other hand if you were already familiar with the digital modeling world when you got the HD500X you might find the learning curve for the POD Go to be similar. - are you a heavy DSP user with the HD500X? Do you use dual paths a lot, and/or multiple instances of the same type of FX in your preset(s)? If so you will find the DSP capacity and routing capabilities in the POD Go quite restrictive. On the other hand, if your HD500X presets are typically single-path and involve just a few well chosen FX then the POD Go should be great for you.

I moved your post to the proper sub-forum - Helix. It will get more visibility (and perhaps replies) there.

I know you don't need your Helix LT connected when using another audio interface. Helix Native is a device independent plugin. However, I'm not familiar with Apple, UA, and Logic products. How is your Apollo audio interface connected to your computer? I notice from the UA website that the Apollo 8 interface comes integrated with the LUNA Recording System, which presumably is not Logic Pro. Have you tried it?

The setup for using Helix Native in Logic Pro is described in the HN manual on page 9. It would be helpful to know exactly where in that procedure things are failing for you, or are working differently than described. Please provide more details with efrence to the documentation. Also check pg 10 re: Live Input monitoring if you are not using a pre-recorded track.

I’ve seen many reports here lately about the Ideascale site not working properly. This may not be something you can do anything about, other than wait for it to be fixed. Perhaps others can chime in about the current operating status of Ideascale?

Unfortunately I don’t think that can be done. A quick read of the relevant sections of the manual describes a Global Setting that allows you to choose between Dim/Lit and Off/Lit while in Stomp mode. This option is not available for Snapshot mode, meaning the LED is Lit for the currently selected Snapshot but the other Snapshot LEDs are Off, not Dim. You could add reflective tape or something to the top of the POD Go to provide a visual marker for your footswitches in dim light.

Try turning off the track’s Software Monitoring feature in Reaper.

No, at least in terms of affecting only one string. However, you say you only play notes, not chords. Depending on your tempo and foot-tapping accuracy you may be able to use a Pitch effect that detunes all strings the appropriate amount. Then you turn that FX block on/off as required each time you play the single note that you want detuned. Not sure how practical this would be but it is a technical solution.

You’re right - HX FX is the appropriate product for your needs. You can obtain an external expression pedal if you wish. With the Helix LT you get the expression pedal but you are also paying for amp/cab modeling that it seems you will never use. I don’t know what the cost comparison is in your geographic region.

I believe MGW-Alberta is referring to the iOS app called Numbers. It is the iOS version of Excel and it seems some Excel features and/or data are unavailable or not being translated properly into Numbers. Nothing you can do about that.

It seems you are trying to import a setlist file rather than a preset/patch file. Use the filter in Customtone to make sure you are downloading a preset that is compatible with the HX Effects device? Presets that are compatible with other Helix or HX devices are not compatible with the HX Effects.

Thanks for clarifying. Yes, a local search option would be manageable. Glad to see it's already up on Ideascale. And yes - I agree who people who use IRs in their Customtone posts should identify its use and origin. I'm also curious to see over time whether the new cab features in Helix v2.5 will have any affect on the overall desire for Helix users to purchase 3rd party IRs. It certainly has removed any desire/need that I have.

Interesting idea.Maybe one for Ideascale? Can you expand on this? Do you mean that HX Edit should dynamically search for all IRs in the public domain every time a missing IR is encountered on loading a preset, and keep that function up to date as new IRs are constantly offered by all vendors? And since specific IR names are generally not mentioned publicly - vendors release IR packages with public names, but do not list the hundreds of individual IR names contained in the package - HX Edit should apply some heuristics to guess which vendor package might contain a specific IR name? That seems like a daunting task to me. How is what you have in mind ‘as easy as that’?

This question is asked all the time, for just about every current Line 6 product. The answer remains the same: Only Line 6 knows, and they don’t talk about it. So for all of us users the answer is also the same: An update may or may not be coming. If it is, it’s coming ‘soon’.

Don’t know where you got that impression. That cannot be the case because it seems to imply one of two things: - Helix presets designed to maximize DSP usage without the Variax connected would somehow suddenly be able to find additional DSP to run the Variax modelling when the Helix is powered up with the Variax connected; or - the Helix device is over engineered in terms of DSP, reserving a dedicated and rarely used amount of DSP sufficient to run the Variax modeling for the relatively few Helix owners who also own a Variax. The first option requires magic. The second is a costly and inconceivable waste of DSP for most Helix users. Helix presets store Variax data. Helix does not perform Variax modeling.

Not sure I understand. Helix does not perform any guitar modeling, it just stores some Variax information in its presets and passes associated commands to the Variax guitar when the preset is recalled. The Variax guitar continues to do all the guitar processing. Although both the Variax and the Gibson use a CAT5 cable I strongly doubt that the data protocol between the two is compatible. The Variax uses a proprietary data protocol over the CAT5 cable, not standard IP protocol. For one thing, the Variax VDI cable carries power. If the Gibson is not expecting to receive power on that connector pin it could cause damage.

I would open a support ticket. Sounds like hardware. not firmware. Perhaps some component is starting to fail and taking a while to warm up to proper operating temperature.

I’ve heard many reports that people prefer the pre-HD Variax models, and there’s no refuting personal preference. I wonder… in your A/B comparisons and testing did you ever try importing an old Variax Workbench preset/model into Workbench HD? If that works and sounds good then you could ‘upgrade’ to the new features and still retain the old models. I’ve no idea whether it does work but might be worth a try.

Yes, I would position the Drop pedal before the POD Go. I expect that the detuning done by the Drop pedal will be more accurate with a raw signal than with a processed signal.

There is a feature of the X3 called Lock Tone 2. This feature does result in Tone 2 carrying over to all presets. It is intentional and very convenient for a singing guitarist who wants to use the same vocal tone across all guitar tones. It is easily unlocked to restore full Tone 2 functionality. I don’t know if that’s what’s happening to you but it’s worth investigating.

No. The HX units lack the VDI input, essential for digital communication between any Line 6 device and the Variax guitars.