Jump to content


  • Posts

  • Joined

  • Last visited

1 Follower

Profile Information

  • Gender
    Not Telling
  • Registered Products

Recent Profile Visitors

1,093 profile views

SteveJohns's Achievements


Contributor (5/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare
  • Collaborator Rare

Recent Badges



  1. Added to IdeaScale: https://line6.ideascale.com/c/idea/1037406
  2. 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!
  3. 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)
  4. 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!
  5. 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.
  6. 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.
  7. 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!
  8. 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!
  9. Huh. Sure 'nuff, using MS Edge worked cleanly. Problem was when using Firefox 83.0 (64-bit). OK, onward. Thanks all!
  10. 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.
  11. 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!
  12. 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!
  13. 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!
  14. 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!
  15. 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!
  • Create New...