silverhead

No. The X3 editor program (Gearbox?) is only compatible with PC and Mac. It is not compatible with mobile platforms, iOS or Android.

I don't know any of the implementation details re: how HX Edit is designed vs. POD HD Edit but I know that it was (and still is) possible for the POD HD device and the POD HD Edit program to get out of sync. This would sometimes happen when the user made editing changes using both the program and the device itself during an editing session. I suspect that this behaviour is directly related to the capability of the HD Edit program to run in offline mode, where it presumably needs to maintain its own memory space (edit buffer) in some manner for preset definitions to permit offline operation. HX Edit, on the other hand, probably does not maintain the same sort of edit buffer but communicates instantaneously with the device to pass edit commands back and forth. There is a single copy of the preset data - on the device. This means there is no possibility for things to get out of sync, and also means no capability to run in offline mode. Again, just my perhaps simplistic and inaccurate speculation but seems to make sense to me. Personally I prefer the HX approach - no data loss or inconsistency.

Exactly. A digital signal either works or it doesn't; one cable doesn't work 'better' than another in terms of sound quality, A better quality cable is determined by the shielding and can be useful if the signal is being carried over long distances where things like electrical interference might make a difference in potential loss of signal. But for the short distances involved in your situation, and the ability to simply move th cable If interference is a factor, don't waste your money on more expensive so-called-better cables. Same with TV and HDMI cables - more expensive does not equal better.

I don't think this feature was carried over to Helix. You're right - it was a thing in the POD HD series. But Helix was not really DT-amp compatible until the latest update and I don't think the L3m model selection was part of the Helix v2.80 L6Link update. At least it wasn't mentioned in the very detailed and comprehensive release notes.

Did you create a backup of your HX Stomp before updating?

I expect it could be done using MIDI commands and cables but I'm not sure. If so you would have to program and assign the correct MIDI command(s) to the designated FS in every preset. I don't think you can do it globally.

Try re-installing the latest Line 6 driver.

Here is a link to the page to get the manual. https://line6.com/legacy/backtrackmic Here's a snip from the manual: Firmware Updates• The latest firmware for your BackTrack is available for download from www.line6.com/software. To update yourBackTrack’s firmware:1. Download the firmware file to your computer2. Click the Update Firmware button on the BackTrack Setup Utility (as illustrated on page 13)3. Locate the firmware file you just downloaded using the Open File window that is provided4. Follow the onscreen instructions to complete the update. You will need to download and install the Backtrack Setup Utility, also available from the Downloads area. Select it from the All Software pulldown menu.

Try downloading and installing the Pod HD ProX driver directly (not using Monkey) and then try Monkey again.

It's in the Downloads area of this website (see link at top of page). Select Backtrack + mic in the Products field and Flash Memory in the Software field.

Yes you can update directly to v2.81. Please read and carefully follow the update directions. No you do not need to make a backup. I suggest that you select to update the factory presets as part of the update procedure; this will provide you with the v2.81 factory presets, replacing the v2.30 that are currently on your device. You will encounter this option as you follow the update directions.

What happens when you use HX Edit v2.81 to attempt to add one of the new amp or FX models to a preset with the connected Helix device running v2.71 firmware?

Yeah I tend to agree with you. The difference in converters probably has a negligible impact on the sound. You’re probably right that any difference has to do with how the code is processed on the different platforms.

Perhaps, but don't know about that. We're comparing the sound of presets in both environments, monitored through the same speakers but routed through different A/D and D/A converters. The presets were initially created in either one of the two environments then imported into the other. Presumably we tweaked the presets to sound their 'best' in the original environment. In that case, any presumed deficiencies in the Helix converters would have been EQ'd out as much as possible. Then they would sound not as good even when the 'better' converters exposed the differences. (And the same would be true in reverse - assuming the Helix converters are 'better' :-) ) In any case, this is no more than a potentially interesting theoretical discussion. It sounds like what it sounds like - full stop. If there's a difference so be it!

I'm not 100% sure but I believe that icon indicates 'assets' purchased from the Helix Marketplace - whether presets or IRs. Did you purchase the 3 Sigma ones from the Marketplace or were they purchased (or free) before the Marketplace existed?

That would probably account for some difference I expect, at least re: the respective A/D and D/A converters.

And you're using Helix as the audio interface for your DAW on Mac?

Not sur about the HX Stomp, but in the Helix Rack and Floor models this behaviour is determined by a Global Setting. Check the HX Stomp manual to clarify.

You're facing a common situation for users who connect any Amp/cab modeling device to a guitar amplifier. If you select a cab model in your preset and then route the output to a guitar amp you then essentially have two cabinets in the signal chain - the modelled one in the device and the physical one. That rarely sounds good. You may even be using two amps if you connect the FH output to your regular guitar input on you amp. The fact that the sound from your amplifier sounds good suggests that your preset is configured to use no cabinet model, and perhaps no amp model. Hence, when you use headphones in the Firehawk you are hearing exactly what you describe: "Just sounds like there's no amp or cabinet modeling or anything." - because there probably isn't. And yes, this is what it will sound like if you connect your current preset output to an FRFR/PA speaker. The solution requires you to be aware of your signal routing and configure your preset accordingly. If you're using headphones (or connecting directly to FRFR/PA) you need to use an amp+cab model in your preset. If you are connecting to the guitar input on your amp your preset needs no amp or cab model. If you are connecting to the rear input on your amp (bypassing the preamp and using just the cabinet of the amp) then your preset needs an amp model but no cab model.

I believe he re-installed just the driver from the v2.70 HX Edit installer package. I think he is running Helix firmware v2.8, HX Edit v2.8, and the driver from the v2.7 package.

Are you monitoring the tones the same way in Helix and Helix Native? The tones sound identical to me from both sources as long as I use the same audio device and speakers for both outputs. I use my Helix Rack as the audio interface for my DAW, and I have two sets of speakers: the L6 Stagesource L3t, and a pair of studio monitors. My Helix Rack outputs are connected to both sets of speakers - L6 Link to the Stagesource and XLR to the studios. Only one pair of speakers is powered on at any one time depending on whether I am playing/practicing or recording. The tones from both Helix and Helix Native sound identical. I would expect them to sound significantly different if the Helix Rack output were routed to my L3t and my Helix Native output were routed to the studio monitors. I would also expect them to sound slightly different if my audio interface for the DAW was not the Helix device. I would expect the tones to sound dramatically different if, for instance, your Helix output is routed through a guitar amp and your DAW output is routed through a different audio interface and then to studio monitors or desktop PC speakers.

It's the Line 6 Updater program (not HX Edit) where you should see the 'Select Device to Update' message. Make sure HX Edit is not running when you launch the Updater program.

Glad to hear it. It was just a hunch based on some of my own driver glitch experiences. Made me wonder if this would work in some circumstances.

Try running the HX Edit installer package again - but only select to install the WinUSB Driver. De-select all other components.

Contact Line 6 - they will resolve this for you. (see Contact Us link at the bottom of this page)