silverhead

There is no 'best' way. Whatever sounds best to you is the best way for you.

You are correct on both questions.

The display alerts you when you approach the DSP limits. Selections that would exceed available DSp are greyed out in the display and unavailable for selection. Accordingly, you should never get into a situation where you crash or hang the device due to excessive demands; you are prevented from making those demands.

I'm willing to give it a shot, but technically I'm not exactly sure about the file transfers required. I would PM you about these questions because others may not be interested in the details, but I've decided to continue to communicate publicly here for two reasons. First, others who might want to do a similar thing in future may be interested in what we discover. Second, other knowledgeable M20d users may be able to help us muddle through this. So, my questions and concerns..... First, we need to understand that the the recording occurs post-trim and pre-fader. That means you need to pay attention to your input trim levels on all channels in order to have a proper incoming signal for processing. That's where the Auto-trim feature is helpful. Without a good signal at this stage you will be limited in producing a good output. Nobody can recover a poorly recorded signal. If you did not pay attention to this it is worth retrying everything on your end. You may find that you don't need help - you just need a good signal to begin with. If you're satisfied that your input levels are good and you still want help we need to transfer the files. But what files? Playback of a recorded segment requires all channel files. They will be numbered in a separate folder on your recording media. Sending these files individually by email shouldn't be a problem as long as you don't rename them. I should be able to reconstruct the folder on my end on a media card. The piece I'm not at all sure about is the Setup. Playback requires that the same Setup used to record the file is use to playback the recording. That means I will need your Setup file. I think the only way to obtain that is for you to make a full system backup and send me the entire backup file. I'm not sure how big that is - it may require compression on your end and expansion on mine. Then I will need to make my own backup of my current settings before replacing them with yours. Not a problem. So it looks like I need two things to begin: - a set of channel files with proper input trim levels, and the name of the folder on your media card in which those files are stored. - a System backup file that contains your Setup, and the name of the Setup to use. What do you think? Still want to try?

Not if you have the global setting for snapshot changes set to Discard.

Are you using Windows 10 and Explorer 11? There have been several reports about this browser being unable to open installer files. Can you try another browser?

You can retain a loop among different patches as long as all involved patches have the same type (mono/stereo) Looper block in their signal chain. You cannot retain recorded loops between power cycles.

You do that from your recording program. Simply lower the playback level of the recorded track(s).

There's nothing to address, really. The fact that there are two inputs for signal processing is a fundamental design element and that won't be changed. The fact that you can use the same physical input for both processing inputs is also part of the design. The only 'issue' is that the factory presets use Same as Input 2, and that this is also the default assignment when you create a new preset from scratch. Some people like this arrangement, others don't. It's not something that L6 is going to change. You can change it yourself in any preset.

What do you mean by the L6 install file? If you are talking about the Helix editor/app, that installer can be run directly on your computer. If you are talking about the Helix firmware, that file is not run directly. It is run by the Line 6 Updater program which is also installed when you install the editor. If you are trying to install the latest firmware update you need to follow the installation instructions carefully. Start by downloading and installing the editor, Line 6 Updater, and the latest driver. Then run Line 6 Updater to install the Helix firmware on the device.

It's hard for a 3-piece band in a pub to afford a sound man. That's one reason that the M20d is a good choice for mixer. You can have the mixer on stage for control of mutes, scenes, monitors, intermission music, etc. And you can record a sound-check segment while all three of you are playing before starting the gig, then take your iPad with the StageScape app and tweak it from the house during playback of the sound-check recording. Then you're ready to go.

1) Hit the Menu button. Select Global Settings . Select Footswitches. Choose which display mode you would like to see. Experiment with them until you find the one you prefer. 2) Press the Presets knob. Use the Joystick to navigate full left to select a new Setlist if desired, then right to display the Preset names. Rotate the joystick to select a preset named New Preset. P.S. rather than spending time on YouTube, try reading the manual. You will find it under Support -> Technical Support -> Manuals.

You could experiment by using reamping on Helix vs. VSTs in your DAW. Record the guitar part without EQ or compression. Then compare by adding the EQ and compression to the recorded track using both methods. Pick the one you like best.

Firehawk FX has limited flexibility in its signal chain and FX assignment. In particular there can only be one Reverb type FX per patch. The details are contained in the Remote Application section of the user manual. The highlights are here: C. Signal Flow Pane - Each icon button represents a Processing Block and shows the routing order and bypass state of all e ects for your current tone. Tap on any Block here to select it and the Block's options are displayed within the Inspector Pane below. D. ProcessingBlocks - Each of the several Block types offers its own properties and functions. Many Blocks are moveable within the signal chain, as indicated below. To move a Block, press, hold and drag the Block left/right in the signal chain - vertical line indicators show all available locations where you can "drop" the Block. • VariaxInputBlock-ProvidesoptionsforaLine6Variaxguitar.See the following Using a Line 6 Variax section. • Standard Blocks - The Amp & Cab Block contains your choice of Amp & Cab models, and the others include a " xed" e ect (Comp and Gate). Standard Blocks cannot be moved. • FX Blocks - Contain a dedicated e ect type (Volume, Wah & Reverb) and have some moveability. • Flex FX Blocks - Can change the FX type they contain (Stomp, Mod, Delay or Pitch/Synth) and have more exible routing capabilities. • Looper Block - Displays its Volume and EQ parameters below. The Looper can also be assigned to any one of the FS1-FS5 footswitches and can be moved to either the start or end of the signal chain - see the Using the Looper section for details.

A global option is a good idea - is it on ideascale already? Just to note, though - the old tuner operates on flashing lights also. They flash red until it's green. When that happens, stop looking and turn it off. ;)

No, but if you ignore the top row of the display you have the old tuner display in the bottom row. As long as the bottom row bar is green you are in tune as far as the old tuner is concerned. The top row is only for fine tuning +/-3 cents when the bottom bar shows green.

Connect the Pod's outputs, either 1/4" or XLR, to the external card's inputs. You could also use the s/pdif connections if your card has an s/pdif input.

It probably won't show up on a POD or Helix device. Those devices and their editors are probably not able to read the custom name - I believe only Workbench can do that. The devices use the standard naming convention.

OK - so I've had a chance to test this. Zooey is correct - when you disassociate an output from the Vol knob it changes to a default value. It does not retain its current setting. Thanks for prompting this, zooey.

Like you I haven't tested that specifically, so I guess it could go either way. I guess the question is: when you disassociate an output (either 1/4" or XLR or other) from the big volume knob what does Helix do with the volume level? Set it to some hidden default value or use the current (last) setting? I don't know. Anybody tested this (I'm not at my Helix right now)?

That's correct. The VDI communication uses the same hardware (RJ-45 connectors/pins) as a standard ethernet connection. Each pin does a specific job - one or two carry power, others carry digital audio, and others carry command & control data. If one pin is bent some function or other will get messed up. Before opening a ticket inspect the VDI connection on your JTV. Look inside to see if you can detect any bent pins. If so, try fashioning a J-hook out of something like a twist tie and use it to carefully hook underneath the pin and gently bend it back into place.

Using the app, when you select the mod FX there should be a button at the top left of the frame that's either text (saying 'Type') or maybe it's just an icon. It's immediately to the left of the FX name. Hit that and you should be able to change the FX from a Mod to another type.

You can use one of the other assignable FX blocks as a distortion rather than a mod or delay. Select an existing mod or delay and change its type to distortion then select a model.

The PF1 tone files (which you were using with the UX2) are fully compatible with PF2 (which is the hardware independent version). You should have no issue. The reverse is not true - PF2 tone files are not directly compatible with PF1. I suggest you make a backup of all your existing PF1 tone files first. Once you use and save them in PF2 they will be converted to PF2 format.

Once it's set to a good level (before you reassign the VOL knob) let the FOH control it for mixing with the band. All you should need to do is control your monitor/FRFR.