phil_m

You can select the Setlist you want to save the preset in by turning knob 4 while in the Save screen.

There are no updates available for the Micro Spider. There's actually not even anyway for users to send updates to it.

I think there are a couple reasons the manual doesn't include those sorts of details. First, that's just a lot of information, and it could easily add like, I don't know, 10 or more pages to the manual. The longer the manual becomes, the more likely it becomes that people won't read it. The other issue is that many of the effects were added in updates, and Line 6 doesn't update the manual for incremental updates anyway. The translation issues make it time and cost prohibitive. Basically because Yamaha is a large, multi-national corporation, things like manuals have to made available in languages that are used in whatever countries the Helix is sold in. Right now, the Helix manual is available in 26 languages. So adding even more information makes that translation work even more daunting.

There isn't an official parameter guide that explains all of those idiosyncratic parameters. You can usually find discussion of them somewhere on the interwebs, though. Ramp, btw, on the Cosmos Echo model controls how quickly the tape speed changes when you go to a new delay time. Having it faster will tend to give you more high-pitched artifacts while having it slower where drag it out a bit more. Imagine what happens when you physically change the rate at which a tape is moving through a tape player.

It seems to me that you're making things unnecessarily complicated. I'm not sure I understand why you want to have a separate path in the Helix for your backing track. As long as the Helix is your system's audio interface, all system audio will be played back to it over USB 1/2. If you want to control the volume of that audio stream from the Helix, you can go to Global Settings>Ins/Outs>USB In 1/2 Trim. Better than that, though, would be to simply lower the fader for the audio track in Ableton. Then as far as the guitar, you shouldn't be direct monitoring that through Ableton - you should be hearing it in real-time through the Helix's outputs. So both the track and the guitar will be sent to the same physical outputs.

Officially confused now, as your first post on this thread talks about recording the Helix through an interface into a DAW... As far as the 2ms, that is the measured latency - it's been verified by a bunch of different people over the years. Adding more blocks does increase the latency, but it's in a negligible way. A preset with both processor paths near the DSP limit would be closer to the 2.5ms measurement than the 2ms. Again, it's not something someone would notice. If you're using an analog input into the Powercab, there would be another round of conversion there, so that might be another 2ms. So you're total latency would be up between 4 and 5ms. Again, generally not something you're going to notice while playing. The fact is, though, that there is some latency just because you're dealing with digital equipment. So you may notice a little weirdness just because you're dealing with an offset. It's the same reason that digital effects don't work well in parallel effects loops. So just to clarify, I'm not saying that a latency of a few milliseconds won't be noticeable when compared to a parallel analog signal with no latency. I'm saying that by itself, that slight latency won't be noticed. Most people can tolerate latency up 8 - 10ms, it seems. But if you creating a parallel analog path, you're setting things up to be problematic by design.

It sounds like you probably need to install the latest version of HX Edit. Once you do that, you have to sign into your Line 6 account in HX Edit. There's a link in the lower left hand corner of the HX Edit that says "Sign In".

The end to end latency through the Helix is between 2 and 2.5ms... It's not something that really anyone is going to notice. It should certainly not be an audible delay. I'm wondering if you possibly have direct monitoring turned in your DAW for the Helix track. In that scenario, the Helix's signal would be processed through your interface's converters and through your DAW, and then you'd hear it. In that scenario you can very easily have latency in the 20 to 30ms range, depending how you have your interface set up.

I see why this would be useful, but I doubt that it's possible from a hardware perspective. From my understanding, the headphone amp taps off of the D/A converter for whatever output its monitoring.

I'm not in front of my Helix at the moment, but I found this image using Google Image Search. You can see the 10 Stomps setting here, above Knob 3.

Just to clarify, do you have the Helix or the Helix LT? The 10 Stomp option is only available on the Helix Floor and Helix Rack, not the Helix LT.

Global Settings>Footswitches>Stomp Mode Switches is where you set that. You had it correct. You just set that to 10 Stomps. That setting only applies to Stomp Mode, not to any of the Preset Mode views that show both Snapshots and Stomps.

That FAQ was written well before the Stomp was released (I know because I saw the rough draft). It was written anticipating that people would be mounting the Stomp on pedalboards and they would naturally want to be able to use their power bricks to power it. I’d also say that it’s not necessarily the same sort of thing buying an OEM power supply for a piece of audio gear as it is for a random piece of computer equipment. There are other considerations. The quality of the power supply can great affect the noise floor and lead to other sorts of interaction with other gear.

I really don’t believe you’re hearing 2ms latency. It’s more likely that you’re hearing some sort of phasing or comb filtering.

No... The latency through the Helix is less than 2ms. It’s not anything that would be noticed by anyone.

That’s exactly what you’d expect. Any digital processor is going to have some amount of latency. You’re running your signal through another round of AD/DA when you run it through the Helix, so there will be a little more latency. If you want to record a set guitar track you’d be much better off using the Helix as your audio interface. You can send a dry track directly from the Helix’s USB audio connection,

What's difficult with designing line voltage power supplies (power supplies that take line voltage and convert to a lower voltage) for a produc tthat sells worldwidre is getting them listed with the appropriate testing agencies. Even in the US, getting something through UL can take several months. So then you have to something similar for the EU, Australia, Asia, etc... It's not impossible by any means, but it's not nothing. As far as the number of complaints, how does anyone have any idea? Only Line 6 knows. That fact that you see some complaints online is rather meaningless. The same handful of unhappy people can make a lot of noise in online communities.

In that case, yeah, you’re going into the power amp. Although, there is also 12AX7 preamp tube in the DT25 that might be active. Is that turned on or off in DT Edit? Are you using the full amp models in Helix or the Pre models? With the Powercab you’d want to use the full models, but with the DT25 you probably want to use the Pre models. You can use the full models, but they will be louder. In any case, the gain staging through the DT25 is different than the Powercab. I also have both, and I haven’t thought the signal seems too hot going into the DT. But I also have separate presets for each one.

The L6 Link connection to the DT25 doesn’t automatically bypass the DT25’s preamp. If your want to do that, you have to bypass it via MIDI. When the 2.8 firmware comes out, the preamp will be bypassed automatically. So it’s not that signal over L6 Link is hot. It’s just that it’s being boosted through the DT’s preamp.

Lol... Karen...

I think this dream needs to die... Line 6 simply isn’t going to give weekly updates on the progress of software development. Honestly, no company, other than perhaps a small mom and pop operation, is going to do that sort thing. I’m a beta tester and under NDA with them, and I don’t get these sorts of updates. I don’t expect them, either. I just know they’re working on it, and it will be ready when it’s ready.

As far as how the new models sound, describing those in detail is technically violating our NDAs. That's why I've tried descriptions I've given have been very vague. They don't want beta testers doing A/B comparisons between a new model and the real thing before it's released, because, even though it's unlikely, there's always a chance something could change with that model. Plus, I think they're trying to maintain some element of suspense, in away. But, anyway, I really don't think there's any reason to be nearly this pessimistic (end of summer, etc.)... I have no reason to believe there's going to be a substantial delay.

What is hard to understand about "with luck"? Obviously, it's not a guarantee of anything... A release candidate is just that - it may potentially be ready to go, but there's often a good chance that some unexpected may pop up. There are no estimates about the timing because literally no one knows until right before the release. It's not complicated. I was answering as many specific questions as I could over on TGP without violating my NDA because I was trying to be helpful. I'm not paid to do that (I'm not a Line 6 employee at all). I don't have to do it. I was doing it to be helpful. Frankly the idea of "managing expectations" over a free - FREE - firmware release is ridiculous.

I'm sorry, but I haven't done anything to incite a mob, and neither has DI... I mean, if someone is offended by my gratuitous use of monkey gifs, then I guess they have other problems...

If, theoretically, the devs were monkeys, they probably look about like this by now...