silverhead

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?

No.

Sorry for any misinformation. Does the iOS or Android device need to be running the Line 6 app?

Your turntable is looking for a device that transmits/receives audio over Bluetooth. The Amplifi does not do that. It uses Bluetooth to transmit/receive command and control data to the Line 6 app running on a mobile device. They will not pair.

Yeah, sorry.... humour can be tricky in written form especially in a second language. I'm guilty of doing it probably too often.

Also, after downloading and installing HX Edit v2.82 you should update the Helix device firmware to match. Your new Helix is likely running outdated firmware that is incompatible with HX Edit 2.82

As I indicated, my response was not serious. I simply made up a number. Is it accurate? Only Line 6 knows, and they likely won't say...... And yes, a Variax you buy today will be obsolete in 20 years, in the sense that there will be superior products available by then. Just like any other electronic product. But it will probably still do then what it does today, just like the original Variax guitars produced 20 years ago.

You can't keep trails when changing presets but you can when changing snapshots. Each FX block that has trails also has a parameter named Trails that you can set to On or Off.

Can you provide more details on exactly how you would like this delete function to operate? Here is the current procedure to replace a preset: 1) select the replacement preset (in this case, presumably a New Preset) 2) Click on the Copy button 3) Select the destination preset (the one you want to replace) 4) Click on the Paste button 5) Confirm your intent to replace the preset Seems to me that steps 3 through 5 are still necessary for a Delete operation, except the Paste button would be replaced by a new Delete button which would have to be added somewhere to the set of clickable things. A new button is required because you don't want to remove the Copy/Paste function which is useful for more than deleting a preset. So the 'timewaster' is Steps 1 and 2. Essentially you want the Delete operation to automatically load a New Preset in the Paste buffer for you in readiness for the replacement? Two extra clicks doesn't seem like a big deal to me and not worth the implementation effort, especially when you consider that you can do bulk replacements (select several contiguous New Presets and in one operation Copy/Past them over another set of the same number of existing presets). But feel free to add it to Ideascale. What you DON'T want to do is physically delete the preset from the list and start moving other presets around (e.g. to delete preset 1A, have 1B 'move up' into its slot and have everything from 1C to 32D move up with it, creating a New Preset in 32D.