silverhead

What exactly does a deleted preset look like? There is no delete function. You can overwrite/replace them but there must alwasy be a valid preset defined in each preset slot. You can overwrite/replace them with what you consider to be an empty preset if you wish. All factory installed USER setlists are full of 'empty' presets.

I would test the headphones on another piece of equipment. There is no special setting for the headphones output - it always puts out the processed signal. After confirming that the headphones are good, make sure your X3 input and output settings are appropriate. For instance, if you have your guitar plugged into the Guitar In jack, but your patch has the Mic input selected you won't hear anything. Same thing if the X3 Volume knob is set too low. Also check the Line/Amp switch on the top right side of the X3 front panel. If that switch is somehow set in the middle position rather than clearly one side or the other it acts as an overall Mute switch for the device.

No. It's better. ;) :)

Maybe the thread title should be 'change of feel after update...'? Sounds rather nebulous. If a controlled recording as suggested shows a difference then there's a difference. If not, there's no difference. On the other hand, your feeling can't be wrong despite what the recording shows. ;)

That would be my suggestion too. No point in arguing who's right/wrong. You're not going to change him and you've got more well-paying gigs coming up with him. Best to give him what he wants with minimum impact on your tone, and I think this is the easiest way to do that - and cheap with an FRFR monitor rental.

Yes to the first question, subject to DSP limitations. As for the second question I think the order of the blocks in the signal chain might also be a factor. I've never tried it. I expect the design intent was to copy within a preset but it may transfer to an identical preset configuration. I'm not sure it would be any advantage though - you might as well just copy the entire preset and then change the snapshots as desired in both presets. EDIT: Upon further reflection I can't imagine how it's practical to copy a snapshot between presets. In order to do that successfully the presets would have to be IDENTICAL with respect to the assigned snapshot controllers. Not only must the presets have the same amp/FX blocks in the same order but the parameters defined as snapshot controllers (up to 64 of them) must themselves be identical in both presets, with just their parameter values differing. What's the best way to ensure that the two presets are IDENTICAL in that respect prior to getting the desired snapshot in the other preset? Copy the preset, then edit the snapshot. Much simpler, quicker, and more reliable than manually editing/comparing the presets.

Go to the Downloads page. Select Helix in the middle (software) field - not the left (product) field. You will see a page with big red letters containing the update instructions. Follow them closely. The first thing to do is download the edit program (see the Get Donwload button in the bottom right corner of the instructions window). Run the downloaded installer file. This installs the edit program as well as two other key pieces: the most recent driver and Line 6 Updater program. Then you use the just-installed Updater program to update the firmware. The fact that you don't have the v2.11 editor suggests that you did not use the proper versions of the driver and Updater program, which in turn means that the update may not have been installed correctly. I would start at the beginning, follow the instructions closely, and perform the update again.

That's strange. I just downloaded and inspected the preset. The inputs are: Input 1: Guit+Aux+Varx Input 2: Same I don't see the need to change the inputs. This ensures that the patch will work for Variax users as well as those who might use something like a bass guitar in the Aux input. If a user is knowledgeable enough to be using different inputs they can surely edit the input settings appropriately for their situation.

Try disconnecting and reconnecting the VDI cable at both ends. I was having a similar symptom after an update and this resolved the issues. I guess the moral is that we should disconnect the VDI cable prior to updating.

I tested this on one of my presets that displays this pop/noise symptom when switching snapshots. The associated snapshots do indeed involve a substantial change in the gain structure, involving the amp Drive and Channel volume levels, a Minotaur distortion that is off and on, and also two different IRs with significantly different Mix and Level settings in the different snapshots. The pop/noise is evident when switching from snapshot 1 to snapshot 2. I copied the preset to another location and Saved them both - one with snapshot 1 active (let's call it preset A) and the other with snapshot 2 active (Preset B ). As expected switching from Preset A to B does NOT display the pop/noise symptom. Why? Because the DSP is reloaded when switching presets, interrupting the signal momentarily. It is this interruption that hides the pop/noise that can be heard when you switch snapshots within a preset where there is no DSP/signal interruption. It's the dramatic change in the active FX blocks and parameters from one snapshot to another that causes the pop/noise. As for it being a detraction from the chief benefits of using snapshots, I guess that's debatable. But I can imagine a similar thing happening if one were to make analogous instantaneous changes with 'real' analog amps and pedals, with no interruption in the signal flow.

Aaah... that's why I was confused. Your reference is to a comment from phil_m, not from me.

I think I just lost your reasoning. Isn't Variax control using non-Line 6 setups (in terms of switching Variax models/parameters) the whole and only reason for the interface you're suggesting? How is this device useful if it doesn't provide such control - if it's just a bonus for advanced users? If you just want an alternative to battery power for the Variax there's already a stand-alone solution for that. http://store.line6.com/accessories/power/jtv-variax-cable-power-kit.html

Yes as long as your Roland audio interface device allows for independent selection of its L and R 1/4" inputs in your DAW.

I don't think the interface device would require the 1/4" connection - the Variax already has that. So the interface device would require only midi in/out ports. That makes sense as long as the current VDI protocol is midi. Otherwise it would require Line 6 to convert the existing proprietary protocol to midi and that's not likely to happen. Another problem/issue could be power. Right now the VDI connection provides power to the Variax. That would also have to be incorporated into the interface device because Line 6 recommends against using the battery and VDI connection simultaneously. But the power is probably a minor implementation issue - the nature of the current VDI protocol (midi or not?) is the determining feasibility factor I think.

Yes - if you followed the instructions in the giant red letters you started the update by downloading and installing the Helix editor, which also installs the correct versions of the driver and the Line 6 Updater program. So you should already have the Helix editor/program. If you don't already have it you should start from the beginning again and reinstall the firmware update (following the giant red letters this time).

Here's a patch designed for this. The patch structure is the important part - you can edit all amp/fx blocks as desired but don't change the structure. http://line6.com/customtone/tone/217206/ (P.S. - I moved this thread to the Pod HD forum from the Helix forum).

That would be very useful. Have you posted this on ideascale? Please elaborate on how you see the 1/4" connector/cable working with a non-Line 6 device. Where exactly would you plug it in to the other device? Would the other device need to be capable of sending midi commands through that connector? Are most other devices able to do that? Wouldn't you also need midi in/out ports on the stand-alone VDI interface? I'm not even sure that the Variax VDI communication is midi. It might very well use midi but I don't think I've ever come across a midi implementation chart for Variax, or even a discussion of such. It could be a proprietary Line 6 protocol. If so your request would require Line 6 to move to a midi protocol. Not likely.

Very true. Doubling up on the FX block is only an option if you have the required DSP available. If one is in the habit of maximizing DSP utilization in all presets then I guess it's a matter of priorities and preferences like it is in all situations where the DSP is nearly maxed out. What's more important - avoiding the warbling by doubling up the FX, or including an additional and different FX? Presumably you've already made the decision about what to include when you first built the preset and reached the DSP limit. Now you need to revisit the decision with the new requirement - trails with no warbles.

Actually I think the entire reason for snapshots is to avoid having to reload the DSP. The reload is responsible for the momentary dropout of the sound when switching presets. Snapshots permits changing the on/off states of FX blocks and their parameters within the same preset, eliminating the dropout. This means the change in parameter settings in any given FX block can be heard, and that's what's happening here when trails are on. Can't have it both ways. Either use separate presets and lose the trails as well as suffer the dropout, or use snapshots. If using snapshots, either turn the trails off or hear the warbling as the parameter values change as you're listening. (Edit: I'm interested to hear the results of your experiment with the Mix and Feedback parameters.) A solution would be to use two different instances of the same FX in the different snapshots. Turn trails on in both but do not use the snapshot controller with the offending parameter.

Yeah - something's wrong. A reflash might work. I use a JTV-59 with Helix. As of v2.11 the interaction seems fine. The only thing I wish would work differently is the default behaviour when Helix starts up. On my JTV-59 the startup setting is forced to Variax Mags (modelling off) even though the startup Helix preset is set to Force a specific model. As soon as I switch presets the modeling is turned on and works fine. If I don't switch presets I have to turn modeling on manually.

No.

I should add a bit here.... it is possible to get some Pod Farm v2.5 presets imported into Pod Farm v1.x. To do so you need to select the Pod Farm v1 file format option when Exporting/Saving a preset in Pod Farm v2.5. This generates a v1.x-compatible file for the preset. You will lose any incompatible elements that may exist in the v2.5 preset (e.g. some routing options); they will be stripped out of the preset in order to generate the v1.x compatible version.

The Gobal Reset changes the global Variax setting from Preset to Global. You need to change it back to Preset manually. You do this in any Input block in any preset. Changing it in one preset changes it in all others until/unless you change it back (or do another global reset).

You don't mention it but I presume the Toneport UX2 came bundled with a version of the original Pod Farm program, v1.x. Please advise if this is not true. There are a few things to note here: - the Pod Farm v1.x that came bundled with your Toneport will not run without the Toneport device connected; the license is tied to the hardware. And vice-versa - the bundled Pod Farm v2.5 license requires your Studio GX connected. That means neither version of the software will run without its licensed device connected. - Pod Farm 2.5 is not backwards compatible with Pod Farm 1. You can import Pod Farm 1.x presets into Pod Farm 2.5 (which includes a preset conversion utility) but you cannot import all v2.5 presets into v1.x because v2.5 has additional routing capabilities. - All of the available expansion Model Packs in v1.x are included in Pod Farm Platinum v2.5, not in the basic version of Pod Farm v2.5 that is bundled with your Studio GX. For full flexibility you should upgrade your Pod Farm 2.5 basic license to the hardware independent Pod Farm Platinum v2.5 product. That will give you all amp/fx models and will run on both your Toneport and Studio devices with full interchangeability of presets. http://line6.com/support/page/kb/_/recording/pod-farm-pod-studio-toneport/pod-farm-20-upgrade-paths-r261

Yes, the FH 1500 and the FH FX are the same in terms of DSP and amp/FX modeling. The 1500 is essentially an FX packaged with a power amp and FRFR cab. You could think of the 1500 being a combo amp with a head (the FX) and a separate power amp+cab. The analogy is not exact because the FX includes cab/mic and FX modeling, but conceptually the 1500 is the FX + amp/cab. They should sound the same using the same preset, bypassing the 1500 cab and going direct to another FRFR speaker system.