silverhead

The editor is called HX Edit. You will find it in the Downloads section of this website (see top of this page). Make sure you use the same version as your device firmware v2.82. You should try to register your Helix when logged in to your account. If you get a message saying th device is already registered contact Line 6 to help get it properly registered to you.

Yes. And in your DAW make sure you turn off the Record Monitor feature. Otherwise you will hear some latency - a kind of doubling of the sound. Give that setup (using only the Stomp; no amp, no laptop audio ins/outs) a try using headphones first. Once you're comfortable with things and understand how it's working you can then invest in a pair of FRFR studio monitors. There are many options and price ranges, and many threads here on that topic to help you out. Don't be surprised when you find the sound /tone you hear through the headphones is different from what you are used to hearing through your amp. But understand that this is much closer to the sound that is actually being recorded. You may find you want to tweak your tone so that it sounds better through the headphones. And again, more tweaking may be desired when you add the studio monitors.

Disconnect the amp and only use the monitors/headphones. Why would you need /want your amp involved if you are using monitors or headphones? Note that the type of amp you are using has a definite colouring effect on the sound/tone. The tone you are recording is different from the tone you hear through your amp. This colouring effect is minimized by using good quality FRFR (full range flat response) studio monitors. The sound quality produced by your Stomp, especially if your are using a cab/mic combination or IR in your preset, is at its best when monitored through FRFR rather than through a normal guitar amp.

You would connect your monitors to the Stomp audio outputs. As for doing what you are trying to do.... it seems you want to have the DAW use your Stomp for audio input but your computer's soundcard for audio output. That can't be done using a fully compliant ASIO driver. It could be achieved by using a pseudo-ASIO driver such as ASIO4ALL but I recommend against it for two reasons: 1) The ASIO4ALL driver may not work well with the Stomp, and it is not supported by Line 6 - meaning that if you have issues and seek Line 6 support the first thing they will tell you is to get rid of ASIO4ALL, use the Line 6 ASIO driver, and call back if you still have issues. 2) The Stomp device is almost certainly a better audio interface device than your internal laptop's soundcard. That means the quality of the audio playback will be inferior. Why not use your Stomp and get better quality as well as full support? What's the reason for wanting your laptop output?

That's correct. It's part of the technical specification of the ASIO protocol. The same audio device must be used for both input and output. Yes, connecting headphones to the Stomp should fix it, but note that it will still play back through your amp if it is also connected to the Stomp's audio outputs.

This seems like an operational issue with your use of Cubase. There must be some basic written information that came with Cubase, or at least a pointer to an online manual. Did you see a section describing how to record a track?

I'm not familiar with Cubase but in general you must arm a track for recording and select a record input/source before hitting the record button. Did you do those things?

You say you 'get nothing'. What do you mean by that? What are you expecting to 'get'?

He means the Line 6 Driver for Firehawk. You'll find it in the Downloads section of this website. Select Firehawk FX in the Hardware field and Drivers in the Software field.

Well, it is the way it is. The Up button navigates you in the direction of increasing (upwards moving) numbers, and vice versa for the Down button. There's no real up or down - just an ordered presentation that your brain can flip if it wants. I'm a bit confused by your concept of 'descending thru the patches'. Given that the numbers are increasing I would say you are ascending. Or perhaps your brain is locked into the ordered list of the HX Edit program where there is an up/down presentation that is different from the presentation on the Helix device itself. In any case, one man's ceiling is another man's floor...... Just ask any apartment dweller. And your brain can handle it. It already flips the optical image from your eyeballs so that we don't see the world as being upside down. .... or do we?.....

Have you tried the other preset display option? You can have them displayed as a Bank/Slot combination (e.g. 1A-B/C/D through 32A/B/C/D) rather than the numbers 000 to 127. See Global Settings -> Preferences -> Preset Numbering.

I suspect this is a doubling effect of some sort coming from some other piece of equipment in your setup. Try this to test using only the HX FX: - connect your guitar directly to the HX FX Guitar input - connect headphones to the L/Mono output of the HX FX - to protect your ears set the Global Settings -> Ins/Outs -> Output Level to Instrument - select an empty preset (New Preset) - turn your guitar volume knob down to zero. Slowly increase it as you play single notes until you can clearly hear the notes through the headphones Do you still hear a delay effect?

It depends on your Pod Farm license. If your license came bundled with your UX purchase the answer is no. If you purchased a Pod Farm hardware independent license separately from your UX the answer is yes.

'Soon' means whatever you interpret it to mean; Line 6 rarely offers specific release dates. Same with specific features and bug fixes; they will be described in the release notes when the update is released.

What versions of Helix firmware and HX Edit are you running?

It's likely a dirty contact point in the saddle where the piezo sits or a failing piezo. Try moving the string aside and applying some electronic contact cleaner to the piezo surface, If that doesn't resolve things you may need to replace the piezo - sometimes they fail. If replacing one I would replace the whole set; the rest may not be far behind in terms of failure. Contact Line 6 for availability.

Nobody here knows. Only Line 6 knows - and they won't tell. Anything you hear here will be uninformed speculation. You can choose to believe it or not.

The POD XT Live supports all Variax models up to, but excluding, the Variax JTV series. In other words the more recent Variax guitars (JTV, Standard, Shuriken) are not supported by the POD XT. While a POD XT and a Variax JTV combination is not supported some aspects of the VDI connection will work (e.g. power and audio). However, command and control data over VDI (e.g. Variax model selection in a preset) is spotty at best and other features (e.g. alternate tunings in a Variax JTV) are completely unsupported.

Aye, there's the rub. I have not yet been motivated to test anywhere near all the IRs I have purchased, and my IR library contains mostly ones I've loaded, tested, and am not using. There are only a few IRs that I actually use and they represent the small set of IRs I liked the best from among the relatively few I've actually auditioned. I'm not discounting the value of IRs and I'm not advocating against their use. They can make a huge difference but I think that's mostly for people who have definite preferences in real-world cab/mic selection/mic placement combinations, and the patience to figure out the different naming conventions among various IR suppliers to identify those preferred combinations. That's not me. I find I can get tones I really like with the stock cabs. The audition/test activity for hundreds and thousands of IRs is simply too cumbersome for me to bother with given the minimal added-value in my experience.

Not sure why you want 10 Snapshot footswitches when there is a maximum of 8 snapshots per preset. Why/how would this be useful?

With the VDI connection you do not also need an analog output cable from the V300 and yes you can control V300 model selection from the XT Live preset. The VDI connection carries the audio and the command/control data as well as power for the V300).

In Reaper, turn OFF the Record Monitor feature for the track when you are recording.

I'm just trying to get people to be specific about what they're asking for. I think most people, when they think it through, come to realize that what they actually want is to get a copy of New Preset to replace the preset they want to delete. But that's already easily achieved. The new Delete feature would save a whole two mouse clicks compared to the existing copy/paste feature. Personally I'd rather have the developers working on things that add features and capabilities.

So .... nothing. No preset name. No Input block, no Output block. No parameters or settings of any sort anywhere in the preset. Oh, you say, .... well those things go without saying. What else goes without saying? In fact, perhaps the preset should disappear completely and be replaced with the 'following' non-deleted preset which move up to take its place. No trace of the deleted preset at all. Not what he had in mind? What, then, exactly should the state of the preset be, and those around it, after deletion? I don't think the answer is so obvious. Please describe it in full detail.

Can you describe exactly how you envision the delete operation? What exactly would you want to see/observe after it is complete?