SteveJohns

I have inquired of LIne 6 support, in July of 2023. There is no way to configure the default startup volume(s). It would require a firmware change. Needless to say, this is highly unlikely on these discontinued products. Nevertheless, I will add that it would be a truly noble and helpful thing for LIne 6 to do for the exisiting user base. That and adding a way to save and load entire banks of 100 from the Amplifi at once (like all other Line 6 amps, yes?). I didn't "get" the Amplifi design when it first came out, but eventually I did "get" it and now have 3 of them! If this product line wasn't the success that was hoped for (?), then it is because a) it was ahead of it's time, and b) it was just short of fully realized in the ways that real players need in their daily use. FWIW, I would comment to LIne 6 the following: A. Finish the job on the Amplifi line, firmware and software-wise. There will be no $$ profit in this, but the repair in goodwill will be tremendous. B. Create a new updated product line with the same basic ideas (FRFR, Bluetooth, control by app, great sounds) implemented with the latest and greatest of what you've got models and FX-wise. C. In the new line, make sure there is a knob to do bank select on the amp. Bank select should be available from ALL 3 of Amp, Floorboard, App - whatever the user has available or finds most convenient at the moment! That's what we need in the field. Thanks. Cheers!

Added to IdeaScale: https://line6.ideascale.com/c/idea/1037406

I appreciate the comments and confirmations folks! Given the situation, It occurs to me that "Global Patch Input Override" Off | <input choice> might be a nice feature to add in a future Helix Floor update. The user could turn this on during a HW (Helix Floor) re-amping session and save a great deal of time and motion for the duration of the session. Then turn it off when done to revert to "normal" (as now). Cheers!

Hi, I'm digging in to doing some re-amping, with a choice of using either my Helix Floor or Helix Native for the job. I've got my routing working either way, and they both sound great, but it appears there is one compelling reason to do the majority of re-amping "discovery" in Helix Native. The reason is that, so far as I have been able to determine, checking out different patches via Helix Floor requires me to reset the Helix Floor patch input (e.g. to USB 3-4) every time I change to a new patch. OTOH, when using Helix Native, I can just click on new patches bing-bang-boom, no input resetting required. This is MUCH quicker! Do I understand the situation correctly, or am I missing the trick as to how to re-amp with Helix Floor without having to constantly set the patch input? (All the above using Helix ASIO driver, with a music mix playing back from the DAW)

Hi, Can anyone identify for me a commercially available-for-purchase (as of 12/2020) and known-to-work 2GB SD card for the JM4? The 2GB SD card I bought does not work. Buying card after card in a blind attempt to find one that works is just going to be too frustrating to attempt! Alternatively, does anybody actually *have* an old 2 GB SD card that used to be in a JM4 which they have parted with? I would be happy to arrange shipping and a fee to acquire it from you if so. I just want to get the most out of my JM4!

Hi. Did you get your JM4 to work with a 2GB card? I put a 2GB card in my JM4 but nothing I do makes it work.

Hi Brazzy. Did that new SD card work for you? I'm having the same issue - JM4 won't work with my SD card and I don't know where the fault lies.

Personally, I'm not asking or hoping for any in-Helix looper to become one-looper-to-rule-them all. I'm just requesting/hoping that what is in the box now could/might/will be enhanced to sync with incoming MIDI clock and start/stop (no more, no less). This is certainly a much more modest goal than designing and building the World's #1 Looper from dead scratch. It is still though a goal with great benefits to anyone practicing, or performing with Helix who wants looping to be part of what they do. BTW, I love the 3.0 FW update! Many, many fine additions there. I'm truly impressed. Maybe Helix looper MIDI sync could appear somewhere in 3.x ... (And please, don't put the whole team on it. (ref. The Mythical Man Month) ;^) Kudos to the Helix team!

Thanks. It is still strange because .hxf is not a defined format here to 'Open in Firefox'. However, it seems to do so anyway! Regardless, I've accomplished my update. Thanks again!

Huh. Sure 'nuff, using MS Edge worked cleanly. Problem was when using Firefox 83.0 (64-bit). OK, onward. Thanks all!

Hi, Thanks for your reply. I wasn't trying to open it, merely to download it, going thru the normal steps (as shown in the attached pics). The result should have been a file downloaded to my disk, not a page full of try {} code in the browser. This is almost surely an infrastructure / web-side error which needs to be corrected by Line6.

There is a problem with the Helix 3.0 firmware download page here: https://l6c-acdn2.line6.net/media/software/10067/HELIX_Floor_v3.00.0_0x07bc7e264_bundle.hxf I've attached a pic showing what happens (instead of a clean download). This is the attempt to download the Helix 3.0 firmware update file from Line6 Software Downloads here: https://line6.com/software/ I do not know if this problem would affect trying to update the Helix FW from inside HX Edit (but I'd rather wait for a confirmed fix than roll the dice). Please advise. Thanks!

Adding a string tree was certainly the job that was needed for my JTV-69 Variax. I chose the Black Tusq XL, and took my G&L Skyhawk as a guide. I marked off the desired depth of the pilot hole with painter's tape on my drill bit, tapped a dent at the desired location as a starter, then drilled the hole and screwed in the string tree. With the parts in hand, the job took only minutes. No more dud, thud, ping on the first string!! Honestly, I'd have to say it's a mistake not to have a string tree be stock on the JTV-69. The shallowness of the headstock angle calls for one. Otherwise though, it's a fine guitar. Neck is straight, and feels great. Action is low. And of course the magical Variax electronics! So, take it from a newly happy camper, if you are having dud, thunk, ping or ring problems on strings 1 or 2, installing a string tree is what you want to do. Cheers! -- Update: Decided to go all-in and install the 2nd string tree, for the 3rd and 4th strings. No regrets!

It would be a hugely useful enhancement if the Helix looper *could* sync to incoming MIDI clock. I too am a BeatBuddy user, and having BB come into a Helix return in front of the looper with the loop actually synced would be fantastic!

Installed Helix Edit 2.90, Helix 2.91 Firmware and Helix Native 1.90 (Win 10 64b). All installs and the backup restore went smoothly. No other issues immediately observed. Thanks Line 6 for a quick hot fix (2.91) and even more for continuing to evolve and improve the Helix!

I just want to say "Thank You" for this thread!! I was wondering why the '000 Flat' patch on my Powercab 112+ sounded anything but flat. Reason (as per posts above): the subsetting in the patch was not FRFR (it was one of the LF modes) and so the tweeter was not on. Doh! I had let this slide for awhile as I was loving all the other "speaker" sounds. However, one of my important applications does require an actual flat (FRFR) response, and I was really starting to wonder if the (my?) Powercab could deliver. This thread solved it for me. Many thanks!

So far (as of 20191021) you cannot do this. I would love to see stereo DT25/Powercab+ via L6 in the future! More info here: https://line6.ideascale.com/a/dtd/Allow-DT25-or-DT50-and-PowerCab-to-be-a-Stereo-Pair/966279-23508

I declared the question of wireless forever solved last month when I paid $40 for a brand new small send/receive pair that works great. I would have thought I was the last one to arrive at the party, but perhaps not!

FYI re: Helix and control of DT25/50: (as of Helix FW 2.82 and HX Edit 2.82) If L6 Link is connected, the DT25 disregards MIDI commands to the power section (Topology, Power Amp, Tube Config). This means the legacy Helix template preset 'DT25-DT50 Remote', which is programmed to offer footswitch commanding of the DT power section (via MIDI messages) *will not work* when the L6 Link is connected. So, be aware! You can, however, save 8 different power section setups (Topology, Power Amp, Tube Config) in Snapshots and recall them from the Helix over the L6 Link. You cannot (per my experimentation) command the DT25 power section via footswitch buttons (over L6 Link). Unlike most other parameters, the Helix won't let you assign these to a footswitch. In summary, using L6 Link, you *can* set up your Helix to give you DT25 power section variations at your feet, and that is (must be) done via Snapshots. This info was confirmed by both experimentation and consultation with Line 6 Support. Now you know (if you didn't already)! Since there are 8 Snapshots, but 16 possible combinations of Topology, Power Amp, Tube Config Topology (x4) Tight, Loose, ZNF, Resonance (I-IV) Power Amp (x2) A or AB Tube Config (x2) Triode or Pentode you won't be able to put every possible combination into a single preset. Attached are 4 preset files : DT25 cA 01.hlx 8 Snapshots of Class A setups, varying Topology and Tube Config DT25 cAB 01.hlx 8 Snapshots of Class AB setups, varying Topology and Tube Config DT25a cTri 01.hlx 8 Snapshots of Triode setups, varying Topology and Power Amp DT25a cPen 01.hlx 8 Snapshots of Pentode setups, varying Topology and Power Amp Enjoy! DT25a cPen 01.hlx DT25a cTri 01.hlx DT25 cAB 01.hlx DT25 cA 01.hlx

Yes, thanks, I'm aware of the Line 6 Ideascale, which I applaud. It's a great way to both capture/save the ideas and to provide the users perspective on how many ideas there are competing for consideration!

Thanks for the comments. Using snapshots to effectively turn off the paths I don't want to hear at the moment seems like it is probably the most efficient way, lacking that "magic check box". If each path ends with a gain block (during development at least) it's reasonably straightforward to set up the snapshots to effectively "solo" each path.

Hi. I wonder if there is a "wizard's trick" which can be used to allow quick monitoring of the path/block output at a chosen point in a complex Helix patch. IOW, I would like to *very quickly* check out the sound at a given point along one of my paths in order to judge what that path is contributing towards the total. In my ideal world, any block could be radio-buttoned-checked to have its output sent directly to the mains for listening, then un-checked to return things to normal. Since this functionality per se is not present, I wonder if anyone knows a tricky-trick to have a similar effect with minimal time/effort.

Still on the "Can't be done?" list (for confirmation or disproof): 1. Adding common post-processing to the 3-paths as shown above. 2. Same idea(s), but with 4 paths.

Yes, I like that. You've created the 3-path version of what I described. Thank you very much! I appreciate also the pithy comment re: how the the gain blocks are the key to creating the path splits. Being still new to the Helix, such little insights save me alot of potentially lost time.

Hi, What I would like to do with the Helix is to take the guitar signal in and process it with a block (e.g. a compressor, or the Wah), and then fork that processed signal into 3 or 4 separate FX paths (e.g. 1A, 1B, 2A or 1A, 1B, 2A, 2B) before having the final summed result go to the outputs. I realize I could get the sonic equivalent by duplicating blocks (e.g. 3 or 4 compressor,s or 3 or 4 Wahs) at the start of each line, but that is what I'm trying *not* to have to do. I get the impression that this cannot be done, at least not directly. Is that mistaken?