silverhead

Are you using the latest version of HX Edit (v3.0)?

Thee are a few considerations here, depending on what you are trying to accomplish. First, the M20d is not designed to be an audio interface for general DAW purposes. It should be recognized by GarageBand for audio input purposes, but only to record the stereo mix of all M20d inputs. In other words, you should be able to record the same mix that appears at the M20d main outputs. You will not be able to record the individual input channels (dry or wet) onto separate DAW tracks. Further, the latency between the M20d and your computer/DAW is too great to do anything with the recorded track on playback. You won’t be able, for instance, to add a track to the recording using the M20d with any sort of tempo sync. You should be able to record to the SD card if properly formatted (Class 10 SD, FAT32, max 64Gb I think). Only one digital channel is available at a time - USB drive, SD, or USB to PC. So if trying to record to the SD card or USB drive make sure only one of them is connected to the M20d and disconnect it from your PC. Once you’ve recorded the individual channel tracks onto the SD card you can then import them as individual tracks from the card into your DAW for further plug-in processing but, as described earlier, you won’t be able to effectively add or re-record tracks using the M20d. Consult the Recording chapter in the manual for more details. For further help here please describe what you are trying to do in more detail. What is your purpose in recording?

To duplicate/ copy a preset you SAVE it to a new location, as described in manual page 11. If you’re not sure where the ‘Lower Knob’ is see manual pages 4 and 5.

Click on the Downloads link at the top of this page. On the following page select HX Edit from the drop down menu in the software (middle) field. Hit the Go button to the right of the three selectable fields. On the following page, scroll down through all the information (several pages) until you see the blue Get Download button. Click on it. The file you download is an installer file. Run it to install the HX Edit program as well as other components. Select to install all components. After installing, connect your Helix device to your computer via USB and run the newly installed HX Edit program. Then follow the instructions provided by the program.

I am not getting that error. I’m using an iPad and Safari. What OS and browser are you using? Can you try another?

That means there is not sufficient DSP available to add these very DSP-heavy FX. To maximize your DSP make sure you are using both Paths 1 and 2. If you’re already doing that you will need to remove (not just turn off) other FX blocks in the preset until you see that these are not greyed out.

Yes, I guess it’s a 50% DSP thing rather than a single/dual chip thing. Thanks for the explanation.

Perhaps the vids were made with older firmware and the “E” appeared in later firmware? Perhaps it only appears in one of the Views and not others? Perhaps..... (insert explanation of your choice here)...... What you’re seeing is simply the way it works now. It’s not a bug and there’s nothing you can do about it. You’ll feel better if you simply stop letting it bug you.Try not to be too CDO about it (I prefer the letters in alphabetical order). Personally I’ve already spent too much time on this. Good luck in getting over it. :-)

I'm not sure either. It's normal. As described earlier you have changed the preset by switching snapshots. Can you show us an example of this not happening to others?

That’s strange. The default amp model vs. your favourites version should use the same amount of DSP, meaning neither or both should be greyed out. Is it possible that your favourites version (greyed out) is the amp+cab model while the available model (not greyed out) is amp only?

If by ‘the first time’ you mean the attempt using HX Edit, that suggests an Internet or USB connection issue. HX Edit downloads the firmware file from the internet while (simultaneously?) updating using Line 6 Updater in what appears to the user to be a single uninterrupted operation. If this is failing, while the manual processing of separating these two activities succeeds, it points to a connectivity or USB issue. Try a different (non-hub) USB port in case the USB connection is timing out while HX Edit downloads the firmware file. Also (somewhat risky) try temporarily disabling your anti-virus utility while updating via HX Edit.

I suspect you pressed the Up and Down switches simultaneously. This engages Snapshot Mode. Do it again to change back to your previous mode. This, and much more, is clearly described in the manual. It’s worth reading.

Try one of the device reset procedures listed here: Some of these procedures will reset your Global Settings and/or IRs/presets. Since your device is not starting up at the moment you have no opportunity to make a backup. Hopefully you have recently made a system backup (e.g when you updated to v3.01) so once you get it started up again you can restore whatever portions of the backup that you need. Start with the least destructive reset options. As a last resort, start in Update mode and use the Line 6 Updater program to reinstall the firmware.

Personally I agree with you. But Line 6 implemented this so it appears there were enough users requesting it on Ideascale to warrant it. Which means lots of users are willing to sacrifice 50% of the DSP in their presets to be able to have true preset spillover. Go figure. Fortunately those of us who don’t want to use this don’t have to! Nothing wrong with an advantage for some that doesn’t disadvantage others.

As of firmware 3.0 Helix does support true spillover between presets - but only if each preset uses only one signal Path. That’s because it dedicates one of its 2 DSP chips (paths) to each preset. So, yes, preset spillover is directly tied to number of DSP chips. The POD Go device likely will, in the next firmware update, get some of the new goodies in Helix firmware v3.0. Preset spillover will not be among them because of the single chip limitation.

This is normal behaviour. Delay and other trails do not continue when you switch presets; they cut out immediately as you are observing and there’s nothing to be done about that for technical reasons (a single DSP a chip in the device). The Trails On/Off setting only controls the behaviour within the same preset when you switch those FX On/Off.

Any preset can have a maximum of 8 snapshots. A different preset can have another set of 8 different snapshots.

Does that mean your problem is resolved?

In Global Settings -> Footswitches there are a couple of things you can do. 1) Using knob 2 you can arrange for the display to show 4 or 8 footswitches to access snapshots. 2) Using knob 5 you can arrange for the Up/Down switches to move to the next/previous snapshot in the preset. You can also assign any Stomp mode footswitch to select a specific snapshot. The manual provides details on all of these options.

How are you calculating which preset(s) are the affected one(s)? There are 32x4 = 128 presets in a setlist. Hence preset #433 is the 49th preset in Setlist #4; probably preset 13A. Accounting for preset numbering maybe starting at 0 instead of 1 (as computers often do) I would remove presets 12D through 13B and try again.

Don’t just edit the preset. Replace it with a copy of the factory New Preset. Export a copy of the preset first if you wish, but it is likely corrupt and unuseable. Best to recreate it manually later once you’ve resolved this issue.

Create a dual path preset with the Input block of Path A set to Guitar and Path B set to Mic. Add whatever processing blocks you wish in each path. Pan the Output block of Path A fully L and pan Path B fully R. Connect the L (guitar) and R (vocal) outputs to your mixer’s two channels. Yes, you need to do this on a preset basis. Unfortunately you can’t have a global vocal path and change just the guitar channel. The best you can do is create a preset that is pre- built with your preferred vocal settings (a template) and copy/paste that as the starting point for any new preset. Of course if you change your vocal template for future presets you will have to manually change all existing presets accordingly.

The are actually two drivers for Helix. I believe one (called WinUSB) is only required for a Windows platform and it handles general audio over USB on Windows. The most recent version was released in July 2019 but it may show a May 2019 internal date that your system is seeing. There is no corresponding driver required on Mac; Helix uses something called Core Audio I think. I believe the other (called Line 6 Driver2) handles more application specific (e.g.DAW) audio and its most recent version is July 2020 on both Windows and Mac platforms. And yes, reinstalling HX Edit will update the drivers but you may already have the latest version.

Make sure you are using the same type of Looper block (1 switch vs. 6 switch, mono vs stereo) and that it is in the same path in the two presets.

I believe the Don’t Force setting leaves the setting in its current state. It does not force the setting to another value. Specifically it does not force/reset the value to the physical setting of the knob. If the current value, based on a previous forced setting, does not match the physical setting of the knob it remains the same, disregarding the physical setting. Don’t Force means Don’t Change. Of course the setting will change to match the knob setting as soon as you physically move the knob. Not sure if or how this relates to the topic, but I believe this is how it works.