silverhead

I think you mean the latest version 2.11?

Very cool suggestion. I am experimenting with some IRs these days, and trying to compare with stock Helix mics/cabs. I notice some of the IRs I am playing with mention a boost at the 113Hz mark, along with some generalized statements about Lo/Hi cuts/boosts. I plan to test these things to see if I can get the stock mics/cabs to sound as good as some of these IRs. At the moment I am leaning towards IRs.

The first thing Support will likely suggest is that you update to the recently released v2.11. In addition to some listed bug fixes, the release notes state that it also fixes some other minor bugs. No way to really know if the bug you're describing has already been fixed until you test out the new firmware. To update, start with the Helix app (editor) package which you will find by going to the Downloads area of this website under the Support tab above. On the Downloads page select Helix in the Software (middle) field, not in the Products (left) field. Download the installer file and follow all instructions carefully.

Yes, interesting concept. After further experimentation I prefer using the full Helix Amp model with the I-version of the IRs rather than the Helix preamp model with the T-version of the IRs. But both seem more clear and crisp than using the Helix cabs. That may say more about my lack of understanding and ability in tweaking the Helix cabs (e.g. juggling mic distance and early reflections, neither of which are IR parameters). To me it's simpler to just plug in an IR, once you've weeded through the many possibilities and their meanings.

I use a Variax JTV-59 connected via VDI. I too was having both issues with v2.1 that you mention. Both issues are now fixed in v2.11. The Input block is a straight up fix. The alternate tunings issue wasn't fully resolved until I disconnected and reconnected the VDI cable at both ends/devices. Can't explain why but I haven't had any alt tuning issues since the disconnect/reconnect.

I found a little bit of magic this morning. I took advantage of this offer and downloaded a package that includes the JIMI cab. I tried the Tube Amp version (interesting concept!) of the CAB mix with the SM57 mic paired with the Helix US Double Nrm preamp - not full amp. WOW! With the Variax Spank model The Wind Cried Mary for a while there! I A/B'd this with the corresponding HELIX full amp and what I believe is the closest matching cab (the Greenback 25) using the Helix SM57 model. I used both the Low Cut and High Cut filters at the same setting in both the Helix cab and the IR for the comparison. I've gotta say I much preferred the Helix preamp with the cabIR.eu IR. It just seems tighter, more punchy, and breathes more like a tube amp - just as described. I'll be doing much more testing before the Dec24 refund deadline but right now I think it's a keeper.

I know it's in the plans but I don't think it's imminent. We'll have to get along with our ad hoc manual system until then.

What do you do when you add an IR to the set/folder? Presumably it's name places it somewhere other than the end of the alphabetical list. Do you then have to edit each preset that references an IR that is now further down the imported new alphabetical list?

No new features. I have the Helix Rack which was not affected by the EXP pedal issues so can't comment on that. All other bugs identified as fixed in the release notes are, indeed, fixed as far as I can tell.

It's fine to download the firmware first as long as you use the latest Updater program (the one in the editor package) to install it 'From File'. The problems start when you download the firmware file and immediately install it using the previous version of the Updater program rather than the current one - which is bundled in the editor package that you haven't yet downloaded. :angry: :(

It was released and announced more then two hours ago. The initial updaters have usually provided feedback by now. Let me be the first.... My update to v2.11 editor and firmware went smoothly (following instructions of course :P ) Don't forget to start by downloading and installing all components of the editor installation package. Don't start by downloading the firmware.

The LTD 150 is itself an amplifier (actually a bass amp) with a bass cab included. It's primarily designed to accept a bass guitar as input. There's no way that I can see from its description to bypass the preamp. Even if you have the controls to neutral and turn off the FX the selected amp type (Clean, R&B, etc.) will colour the sound. The Firehawk is doing its own amp/cab modeling. Connecting that to the LowDown amp input is doubling up on amps and cabs. It won't sound good. The best combination would be to use no mic/cab on the Firehawk preset and select eh Clean amp on the LTD 150. Put all tone controls to neutral and don't use any LTD FX. But I still wouldn't expect it to sound great - using an EQ in the Firehawk preset might tame some of the low end frequency response that is built into the LTD. It is a bass amp, not a regular guitar amp. But you should use a different sort of speaker to connect the Firehawk to. For best results you could use an FRF (Full Range Flat Response) speaker like a studio monitor or a PA speaker. You could also use a keyboard amp - it's probably cleaner than the Clean setting on the LTD, and it certainly has a more guitar-appropriate frequency response in the cab.

You will find it in the Downloads sectoin I this website (under Support tab above). Enter Helix in the Software (middle) filed, not the Products (left) field. Follow all instructions carefully and reinstall the v2.1 firmware as described in the instructions. It seems you have already installed the firmware without following the instructions so it is unlikely to work properly in combination with th editor. They go hand in hand and you should begin with the editor.

Have you also updated the editor app to v2.1?

I think I misinterpreted your original post. What you say here is correct. The Variax Preset/Global parameter in the Input block of every preset is, in fact, a global parameter. I'm not sure why it is associated with every Input block rather than being in the Global Settings, but there it is. If you change that setting from Global to Preset then the remaining Variax-related parameters in the Input block, including the tuning Don't Force, are applied on a preset basis and you have to adjust it in every preset. If you change the parameter setting from Preset to Global then all the current Variax settings will be applied to all presets, even as you switch among presets, until you change the parameter back to Preset - which you can do at any time in any preset.

Is the Drop-d on the Variax built into the model using Workbench, or is it using the Alt Tuning knob? It should work in both cases with the settings you describe, but in the case of the Workbench modified model you have to have the Alt Tuning knob set to Model, not Standard. As an aside, I was having some alt tuning issues with my JTV and v2.10. These issues disappeared after I disconnected and reconnected my VDI cable at both ends (which I had not done since updating). Go figure.

I don't think there should be a separate sub-forum for non-FRFR topics, for a few reasons: - many users are both FRFR and non-FRFR in different circumstances and for different reasons. It's a disadvantage for them to have to look in two places. - even users who are strictly FRFR and those who are strictly non-FRFR can learn from posts about the other. Personally I am strictly FRFR yet I have learned a lot by reading non-FRFR posts. Just today, for instance, I am experimenting with some IRs that have different options for signals that don't go through a power amp before hitting the IR. From my forum-based knowledge of amp outputs I am going to try using a preamp rather than full amp with these IRs. Don't know what the results will be but I'm pretty sure I would not have considered that if the non-FRFR topics were in an area I didn't visit. - it's not a Helix specific concern. If it makes sense for Helix presumably it makes retrospective sense for Pod HD, X3, xt, ...and all future guitar multiFX devices/forums. Forum management and overhead would be more cumbersome and require more effort for, I think, little advantage. - lastly, and perhaps most simply, ...... if you're not interested in posts about FRFR then don't read them. ;) And if you want to hear only from non-FRFR users in a particular thread you open then make that request politely (without offending FRFR folks) in your opening statements. No need to complicate things with extra layers of forum structure.

You caught me! I confess-I don't' always read the entire thread before jumping in!

I think the way to do that is to include multiple instances of the model type (e.g. Include both a Vermin and a Minotaur) in the signal chain during the comparison stage. I know this consumes DSP but it allows you to retain the settings for each as you enable/bypass them. Assign them both to the same FS to turn them on/off inversely and you can compare easily while you play (or use the looper in pre position). When you've decided which one you want to keep you can delete the other, or keep them both if you don't need the DSP. Of course this strategy becomes more difficult as you approach the DSP limit, and/or use DSP-intensive blocks like amps, cabs (especially dual cabs), and IRs. On the other hand, when building presets you normally start with the amps and cabs/IRs before moving on to the FX. Doing so allows you to duplicate things with as much DSP available as possible.

So I think that implies that what HonestOpinion is contemplating is, from a technical perspective, no different than using multiple presets. In other words, having any amp/FX block defined but not 'active' in a preset is equivalent to having two presets, one with the block inactive and one with it active. The lag involved comes from the 'loading/activating' that is required in both cases. The fact that the block exists in the same preset or in another preset is irrelevant. In other words, the existing Snapshot ability takes the concept as far is it can go technically without introducing a lag/gap in the sound.

That's an excellent offer. Thanks for your consideration and response Markus. OK non-Facebook folks - we can't ask for better than that. It's no risk to take any on of the IR packages for a test drive for 10 days. I'm off to do that right now. It's up to us to be fair to Markus. If we like it, keep it and make a positive comment. If not - stop using it, delete it, don't share it, send the email as described and get your refund ..... don't screw him! (Now we may hear from the non-Paypal folks ....... whom I would encourage Markus to ignore. Enough is enough! :lol: )

The dry track is mono. Default setting in Helix is Guitar input on 7 and mic input on 8 though you can change those. In Reaper you need to set up two tracks for recording, one stereo for the default input of USB1&2 and a mono track for the dry guitar. Once you arm the tracks for recording you can select the Input Source for each track. Select USB7 for the dry track.

I agree with PeterHamm. The volume level of audio coming from your computer is controlled by your computer sound settings. I have had to lower my default computer sound volume significantly to jam along with backing tracks or to avoid having my ears blasted when Helix starts up.

Why not contact Line 6 directly via support ticket? Or post the suggestion on ideascale? Sounds like you can make your case better yourself than asking someone else to do it for you.

I'm out of suggestions. Hopefully you support ticket will yield a good result.