Leaderboard

The Guitar Input is only available as an Input Block, you can't place the Returns before it. You COULD place a GAIN Block just after the Input Block, followed by Return 1 and Return 2 Blocks, and use Snapshots: Snapshot 1/Cable - Gain 0db with both Returns BYPASSED Snapshot 2/Wireless 1 - Gain -120db with Return 1 Active and Return 2 Bypassed Snapshot 3/Wireless 2 - Gain -120db with Return 2 Active and Return 1 Bypassed

A new model with more DSP & Memory is inevitable.... when, we don't know. Here is what I know TODAY! My Helix sounds great, and I don't face any bottlenecks in horsepower or memory even though I am aware some do. When a new Helix is introduced my Helix will still sound great! As a gigging musician.... my Helix makes my life easy and also makes me a good chunk of change. Why would I put all of that on hold waiting for something I "expect" to be coming at "some point". Maybe EVH should have waited 2 more years for the JCM 800 instead of using that 10 year old Super Lead :)

In case it missed your attention there has been a global pandemic over the past couple of years which has had an impact on the supply of various parts. One of the major things to be hit was the manufacture of microchips. See the blue banner at the top of this page - “Impact of Global Materials Shortage”. You give the impression that, as you put it, “3 generations in” you are expecting no more development of this line? Over on TGP, it has been noted that Digital Igloo has mentioned yet more firmware for the Helix is still in progress. Nothing makes sense in 2023 - waiting for the next big thing to come rolling down the tracks is an exercise in futility. You could wait forever! You really should buy what’s available right now to get the job done, or wait in vain. I love the way that you describe how easy it would be to create this mythical beast of Helix 2 - “install newer DSPs, a modern heatsink and some extra memory DONE!” - Wow! I’m surprised that Eric hasn’t thought of that one already and told the team to just get on with it. Yeah, right!

Frankly I find these DSP spec comparisons a little bit silly given the purpose of DSP which is simply to do digital signal manipulations in a real time processing setting. The purpose is to transform a digital signal representation of the results of a given (usually analog) circuit. DSP limitations aren't typically about the quality or precision of the transformation (although it could be in some cases) but rather the amount of latency in that transformation given this it meant to be used in a real time signal processing environment. If the transformations are reasonably accurate, faster transformations won't likely make them MORE accurate in any distinguishable way, but it could reasonably result in less latency allowing for more transformations. In practice none of this affects me since I never run low on DSP because I use the DSP efficiently and have for over 8 years. In my opinion and practices adding faster or more DSP only services the needs of people that don't use the DSP efficiently.

Helix was overbuilt from the beginning in the areas that mattered the most for future updating. The design goal was specifically to create a platform. The technology is always less important than what you do with that technology. I have many digital devices from decades ago (e.g., Lexicon PCM-60) that use "antiquated" technology by today's standards. Yet they still sound as good as they did decades ago. The main reason for wanting faster/more expensive/hotter-running DSP is to speed up the rate at which operations occur. If you find the latency in Helix unacceptable, then you may need a unit with more powerful DSP (of course, regardless of the DSP, there will always be the latency involved in A/D and D/A conversion). However, DSP alone isn't the only factor. The efficiency of the coding is crucial. Based on 3.50, it's pretty clear Line 6 has managed to increase the efficiency dramatically, or we wouldn't have better cabs that require significantly less DSP. The question is simply whether Helix produces the sounds and effects you want. If not, then you need to find a unit that does. However, if you like a different unit better, it may have nothing to do with the underlying technology, but with the people who did the coding.

I guess it all depends on what the next Helix actually is and what it does, but I personally have no plans at all regardless of what it does at this point. I personally think the natural flex point in the processors used for modeling application was reached back when Helix was coming out as a competitor to Fractal's offerings primarily. Since then not a whole lot has changed in the DSP market but there area a LOT more competitors which would insinuate my theory of the natural flex point of the technology is probably correct. As has been noted previously, what modelers do and their processors can't be compared to the progress made in general purpose CPUs used in desktops and laptops, so you really can't think of them in the same way. I could always be surprised by some real innovation in that particular part of the industry, but even were that to be the case everyone would be scrambling for many months/years in product development to get their systems launched. Again that's another big difference between DSP and general purpose CPUs which actually are a composite of multiple processors including graphics and I/O processors. The best market representation would probably be how long it took Apple to actually develop and launch computers into the market using their new M1 architecture after they first began working on it about 10 years ago.

When weird things happens, it's always a good practice to break down the problem into smaller parts. In your case means unplugging the HX Stomp from everything (so no Mac, no HX Edit, nothing but the HX Stomp alone). Now try doing the same preset directly on the unit, starting from a blank preset. If it works like I think, means something were happening within HX Edit (maybe just user errors). Also, test stock presets. If those are working, then it's something odd you are doing while editing.

Moving to 21569 means redesigning the entire board and a good part of the software framework. Isn't really like swapping the cpu on your PC motherboard. Said that, I believe there would be a solid market for a Helix MKII.

Hi, First up - Is your HX Stomp running the latest 3.50 firmware? If it is - after installation did you preform a factory reset as per the Release Notes recommendation? If not - do it now, to see if this fixes the problem. Also, check the HX Stomp 3.0 Owner’s Manual - page 21 - Block Order and Stereo Imaging. Furthermore - when you are describing weird and bizarre things happening to your presets, it’s great help if you upload a copy of the preset that you are having this issue with. Having in example preset would allow other users to check it out on their hardware to see if they can track down the cause. Hope this helps/makes sense.

To follow up...obviously I didn't get it done for December, but that's because the book's 1.2 update has had "scope creep" :) The section on mics has been redone completely, and I have a new way to do frequency response analysis that I've applied to the new amps, new mics, and old mics. I also got permission from Line 6 to consolidate all the release notes since 3.0 as an Appendix (thanks Line 6!). The updated book is done, all that remains is updating the presets that come with it. So it's not too far away. Also, it will be a free update to anyone who has the 1.0 or 1.1 version.

Wait! Re: "This mode applies different tonal characteristics of the selected speaker model to the system's coaxial driver, with the following adjustable parameters." I'm pretty sure the "system's coaxial driver" refers to the whole coaxial speaker, not just the tweeter, which is referred to as the "high frequency compression driver". I'm pretty sure the tweeter is only on in Flat:FRFR or IR modes. In the section describing the speaker models, the manual also says: "HF OFF / Natural – This is the natural sound and feel of the speaker in the Powercab with the high-frequency compression driver disabled and no EQ of any kind applied". This might leave the impression that the HF might be on for other speaker models, but it is not. I just tested my Powercab 212 in Speaker:Normal and Speaker:Cream. Adjusting the Global HF Trim through its full range makes no difference in the tone. The HF compression driver is definitely off. The same HF Trim sweep in Flat:FRFR makes a huge difference indicating the tweeter is definitely on. There should be no need to use a tweeter to EQ the Eminence speaker to sound like another guitar speaker as the EQ delta should be fairly small. All the speaker model EQs are applied to Flat:LF Flat, and that, like Flat: LF Raw doesn't use the tweeter. A guess, but I think Flat:LF Flat just EQs the Eminence speaker in a "standard" way so that Line6 could adjust Flat:LF Flat EQ to use with different speakers (i.e., in Powercab 212) and reuse all the speaker models, since their EQ is all applied to the same normalized Flat:LF Flat. I also tested and Flat:LF Raw and Speaker:Natural don't sound the same. There is some EQ processing that makes Speaker:Natural sound a bit more scooped and brighter than Flat:LF Raw, and not in a pleasant way. LF Raw sounds better to me. So I think you've been right all along. And I really appreciate your contribution and insights.

I've got 2 laptops, both are the same brand but different models one is working with hx edit just fine, the other was ok until it just have stopped opening the HX Edit app and since then no progress... ....ok. I've read this, and it was my sollution: I found the answer on reddit. There's an SD card in my card reader. When I eject the card, HX Edit runs. When I insert the SD card again, HX Edit does not run. .....maybe someone like me will need this info. ..thank You and all the best

I am looking at buying another Helix Floor but it doesn't make sense in 2023 on hardware. (3 generations on) an updated DSP and some additional memory are needed at least. R&D costs of the hardware were made back 7 years ago. DSP chips are cheaper and 4 times more powerful in 2023. An extra 8gb of memory costs what $100? no hardware dev needed.... install newer DSPs, a modern heatsink and some extra memory DONE!