silverhead

The most common explanation for this is the output connections from Helix. I believe Jason’s presets are designed for direct output to studio monitors, FRFR speakers, or mixer/PA system. If your Helix output is connected to the input of a regular guitar amp it’s almost guaranteed to sound like $hite. Describe your output equipment and we’ll ty to help.

Yes. I think if your first few taps are not right you’re best to wait at least 2 seconds and start over. Then try to do three or four accurate taps. You don’t really need 10 as long as you’re paying attention at the start.

You’re welcome. Glad you got it sorted out.

. Actually I call myself CDO now. I can’t stand that they’re not alphabetical! ;-)

2 seconds according to my observations.

The Input-Z parameter is only available through the 1/4” Guitar input on Helix. It is an analog circuit and does not affect the VDI input.

One of the bugs in v2.90 was Tap Tempo. I believe it's now fixed in v2.91 but I never really noticed the bug so can't confirm that it's been fixed. However, the discussion at the time left me with an unresolved question: How many 'taps' in sequence are considered in the calculation of the tempo that is then applied to time-based FX? Clearly if you only tap twice that defines a specific tempo based on the one interval between the two taps. But what if you tap 3 times? Does it take an average of the two intervals or only use the final interval? And if it takes an average of a sequence of taps, what is the maximum number of taps/intervals it uses to calculate the final tempo? So I did some further testing. My initial (poor) testing told me at the time that only the final two taps were considered and I stated that wrongly in one of my posts. Time to correct myself. Further testing shows that Helix takes an average of up to 10 (yes, 10) taps! That surprised me. To test for yourself use a metronome at 60bpm. Test#1: Tap the full beat once. This requires two taps. (counting 1...2) Observe that the tempo is set to 60bpm (more or less depending on the accuracy your tap timing). Test #2: Tap the full beat once followed by two half-beat taps (1...2.&.3). Notice that the tempo calculated up to any point is displayed immediately after each tap. Observe that the final tempo in this test is set to 90bpm, the average of the three intervals created by the 4 taps. The final tempo is not 120bpm which is the duration of the last two taps that define the third and final interval. Repeat this test reversing the intervals. (1.&.2...3). The average is still 90bpm. Test#3 and onward: Continue tapping the half-beat after the first full beat for multiple different trials (1...2.&.3.&.4), then (1...2.&.3.&.4.&.5). In each trial observe that the final tempo increases following each tap until you have completed at least 10 taps, after which the calculated tempo finally ignores the first long tap and settles at 120bpm (again depending on the accuracy of your tapping). So what does this mean? For those of us who use Tap Tempo in a live setting we should tap at least 10 times to get the best accuracy. In particular, DON'T make an erratic first few taps and then stop after you've tapped accurately 3 or 4 times. Those first few badly timed ones will count and throw your time-based FX off tempo! And yes, I am a bit OCD. This was just bugging me!

Indeed. Those hippos are just so damn greedy and selfish.

Just an FYI.... The Helix Native manual has been update to v1.90 (compatible with Helix v2.90). Many of the features and operations are similar if not identical. The Native manual might help with features that have been introduced to Helix since v2.0.

The message you are getting is correct. The device presets are not compatible. You can’t load a Helix preset into the POD Go. The POD Go uses Helix models and DSP algorithms and the sounds are virtually identical. That doesn’t mean the presets are compatible. It does mean that if you manually recreate a simple Helix preset in the POD Go the sound of the two presets will be very close if not identical. I say a ‘simple’ Helix preset because the POD Go preset structure is much more limited than Helix. That’s why the presets are incompatible. ... and no, there is no preset converter.

I didn’t know about that freebie..... Thanks hurghanico.

Since at least a couple of people have found this analogy useful, let me expand on it to answer a question that comes up repeatedly: How can I delete a preset? Not just overwrite it - I want to DELETE it! As described above a setlist is an organizer. A shelf holding 128 little boxes can still be quite disorganized with boxes piled in any manner. So let’s subdivide each shelf into 128 identical compartments, in a 32x4 grid. And let’s index each box so that it has its own location in the grid and never moves. You can choose one of two index methods - number them 000-127, or consider rows and columns from 1A to 32D. The point is that each box is ALWAYS in the same location. You can put a temporary name on a box and change the contents of the box at any time, but you can’t change it’s location and you can’t pretend that it’s not there. It’s always there. You can empty the box but you can’t throw it away. Copying New Preset (a preset with no blocks) into any box is deleting the preset.

They’re both good choices. Check their product descriptions, figure out what features are important to you, and make your choice.

Have you purchased the bundle?

Setlists are nothing but organizers. They have no special properties. They hold up to 128 presets each, and that’s all they are. Imagine that your Helix storage is an 8-foot tall cabinet that holds exactly 1,024 little boxes that are identical in size and shape. Each little box might or might not actually have something in it - but the box itself is always there. You could just dump all the boxes on top of each other in one big pile, or you could build 8 shelves with each shelf holding 128 boxes. A setlist is one shelf. A preset is one box.

Better than what? Not sure what you mean. The HXFX and the POD Go are apples and oranges. The main difference is that the POD Go includes amp and cab models and the HX FX does not.

I’m no longer OCD. I’m CDO now. I couldn’t stand that it wasn’t in alphabetical order.

Ummm.... yes you do. You always have 8 of them. Three of them (#1, 2, and 8) come pre-populated by Line 6 and they are the subject of this post. But the others still exist. Perhaps what you mean is that you don’t really use setlists as a concept. You just have a bunch of presets that you use and they’re all that you really need to backup and restore. You can do that in a single operation by exporting / importing the setlist that contains them rather than by dealing with each preset individually.

Glad you got what you wanted.

Yes, but as pianoguyy says, your ears are not hearing what the audience hears. So the question becomes: whose ears should decide? Yours, for your benefit alone, or the sound guy's, for the benefit of your audience? Are you playing for yourself or for them?

Yes, this preset is very heavy on amp and cab blocks. They are critical to the sound which means they can't be deleted and they are also very heavy consumers of DSP. So there really isn't much DSP left after all those amps and cabs are included. However, I have a couple of observations: - Path 1 includes a noise gate and an EQ block at the end. If you remove the noise gate you will have several options of Delay blocks to add. If you also remove the EQ block you will have several more options. You already have an active noise gate in the Input block so this additional gate seems a bit redundant. Also to my ears the EQ block doesn't seem to make much difference to the overall tone. Then again I'm not a really high gain tone kind of guy so perhaps my ears are not a good judge. But it seems to me you probably can get what you want by removing these two blocks. You will be able to choose from all mono delay blocks except for two of them. You will have a few selections of stereo delay blocks available and also many in the Legacy section. Also, I notice in your preset that there is already a delay block in the first path. Are you wanting to add a second delay block? If so, and if removing the above blocks is not what you want to do, you might consider using snapshots to adjust the parameters of this delay block to achieve different delay effects in different snapshots. There is also sufficient DSP without removing any blocks to change this delay model to one of several other models. Perhaps a different model, using snapshots, can get you what you want.

Sounds like the block you chose to delete is one that greatly affects the tone. Have you tried deleting other blocks that might not have such an effect? I should have time to explore your preset later today and will get back to you.

Not sure I understand. In your first post you said you love the preset, now you say it sounds really bad. Are you talking about the same preset? Can you explain what you mean by ‘on anything I put out’? Describe your setup. Are you using a regular guitar amp to receive your Helix output? Speakers or monitors? A PA system?

You are in the right place. It seems you have some sort of corruption with presets in Setlist 7, or setlist structure itself. You need to remove the corruption and the best way to do that is a factory reset. There are different options is performing a reset. The details for doing it on each Helix device are described here: Before resetting the device make sure to backup / export all your custom setlists that you want to restore later. (e.g. Blues, Rock, ...). I would start by choosing the reset option that just restores the factory setlists and leaves your IRs and Global Settings in place.

When an FX block, like your delay, is greyed out and can’t be selected it means that the preset is close to the DSP limitation of the Helix and adding the FX block would exceed the limitation. Hence it can’t be added. In order to add the delay block you will first need to remove another block or blocks (thereby freeing up DSP capacity) until the desired delay block is not greyed out.