Please ensure Javascript is enabled for purposes of website accessibility Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


gordwait last won the day on July 20 2014

gordwait had the most liked content!

Profile Information

  • Gender
  • Location
    White Rock, B.C.
  • Interests
  • Registered Products

Recent Profile Visitors

629 profile views

gordwait's Achievements


Enthusiast (6/14)

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

Recent Badges




Community Answers

  1. I agree, a metering feature would help with the gain staging. Since it's not a feature, you can work around it like this: (Much easier using Helix edit on the PC) 1) Load your patch, bypass every single block in it. 2) from the input to the output, enable and disable each block in sequence, adjusting the block level until there's no difference in the volume level. Move to the next block, leaving the leveled block engaged. One other idea is to use a send block to a spare output to a DAW and connect it to a meter of choice. You can then slide that send block along the chain to help with the leveling above.
  2. I did that, but it wasn't my issue, it turned out the stale 2.80 .dmg files were still mounted even though I couldn't see them on my Desktop. See my end comment below. All good now..
  3. Heh, soon as I state "It's not me" I work it out. The Mac install thing "mounts" the .dmg file as if it were a hard drive, which "I swear" I had unmounted. I saw three copies of the installer in /Volumes. I removed all of them and went for the 5th try, now it's ready to install 2.81.. Someone on Facebook had reminded me of this yesterday, but I didn't see the .dmg mount on my desktop for some reason. Using the command line I could only see the stale 2.80 copies mounted in /Volumes. Removing these fixed the install process. All good now, problem between keyboard and chair..
  4. No links back. I went in with the Mac bash command line (I've been a Unix nerd from 1984) and there's no links anywhere else. What is weird is all the files for HX Edit are dated 15 July (2019). I used the command line to fully delete HX Edit (fourth time?) and reinstall, 2.80 came back, and has th 15 July date. I think the .dmg file I'm downloading from Line6 is mislabelled on their server, and maybe it's a different server for Canada? Very odd.
  5. I'll check the link idea. I left the Helix off on purpose to make sure I wasn't seeing the version number from the Helix firmware (which is still 2.80).
  6. From the "About" tab in HX Edit, and from the "Installing HX Edit 2.80" installer screen. My Helix is turned off at the moment. Oh and from the popup in HX Edit "No Device Connected" it says HX Edit 2.80 at the bottom of the panel.
  7. Solved: The old 2.80 .dmg file was still mounted in /Volumes. It wasn't showing on the desktop (why Apple??). Found it using the bash command line and removed it. Now the install is proceding as planned with 2.81 .. Yeesh. ------------------------------------------------- And if I install it, it installs version 2.80. I have triple checked everything about this, deleted all traces of the original 2.80 files, but no luck. The HXEdit2.81.dmg file size is bigger than the 2.80 copy, so it's not like it's the same 2.80 dmg file accidentally renamed.. Of course I don't want to update the Helix firmware to 2.81 until I have a matching 2.81 HX Edit ready to use.. For anyone else on Mac who have updated to 2.81 can you check what version HX Edit reports when you open it to the "About" page?
  8. If you are careful to arrange all your patches so that the same features are always on the same buttons (lead boost, chorus pedal, etc) then you could do without the scribble strips. You could use a label maker to neatly mark each button. You would want to rearrange any downloaded patches to match your labels.. I opted to go for the strips, even though I am organizing my patches to my standard button pattern..
  9. Had the flextone II for gigs back in the day, it was good enough and bet versatile for live but not 100% there for home. I just got the Helix floor for gigging, I love the sound of my Mesa Boogie Lone Star with a Digitech rp1000 in four cable mode but I got tired of the weight. I am keeping the Lone Star for home, but here's the thing, I'm having a blast with the Helix at home! If you get one of the better patches I can't tell it from a tube amp. On YouTube is a comparison between a Mesa and the Helix, I guessed wrong trying to spot the Helix vs tubes. One thing though, when you compare at home, the Helix will behave like a studio recording of a tube amp, cabinet microphone and studio room, then playing out your stereo speakers, or monitors. That won't be the same as the big juicy sound of your tube rig in the room with you. A proper comparison would be to record your tube rig with similar settings as the Helix then compare them both recorded, back thru the same full range speakers.
  10. I just got the Helix this month, not all the pennies have dropped in my brain on what I can get it to do ;) I bought it mostly for live work so I can stop carrying around my 2x12 Mesa Boogie (great sound, damn heavy to lift!). The Tascam gives me up to 8 XLR in, for microphones etc, I'll continue to use it for analog in. It's more convenient in my little home studio for leaving microphones wired up permanently as I take the Helix off to band rehearsal and gigs. When I connected the Helix today, Logic asked me if I want to use the Helix as an audio device, so one penny dropped - I've been recording the Helix by going analog XLR out of the Helix into the Tascam, then into Logic. I realized I can just go in via USB from the Helix right into Logic (aha!). I'll likely try this out with the new Line 6 driver - I suspect the Tascam will continue to use the Mac drivers and things will be awesome.. #fingerscrossed Oh, and Line 6 released a new Line 6 Driver for the Mac, so the manual information is now obsolete..
  11. Typically, one doesn't have to install a driver for Mac audio devices, so I'm a little suspicious.. This line is concerning: IMPORTANT! Installing the Helix Mac Driver 1.0.5 precludes using Helix with the class-compliant OS X Core Audio driver. I have a Tascam USB audio interface I use with Logic Pro X, which is using the OS X Core Audio driver.. Red Flag!! If I install the new Mac driver for the Helix, and gain the benefits listed, will it potentially break any other USB audio devices running on my system? It would be cool to just run the Tascam and the Helix at the same time, and record guitar direct to Logic via USB..
  12. (Sits up!) Huh! Now that's a good idea! Our cover band tunes to Eb to give our voices some room, but it's a pain to tune back up to jam with other music.. hmmm
  13. After reading the sticky note above about corrupted patches messing up the Helix(!!) my request is that they add a standard checksum to the patch file format and have the editor reject it when the file is corrupt.. Hopefully the existing patches have a header with a patch version so that a change like this could still be compatible with the existing patches. Far more difficult would be to have the Helix editor sanity check the patch..
  14. We did share for a bit, but when we went to in ear monitors (IEM) it became a problem. Bass player wants the bass up loud, Guitar player wants his guitar up loud, and so on. I ended up grafting my old presonus rack mount mixer onto the side to make one more monitor mix for myself. Not at all ideal. With in ear, I also really want a stereo mix. The new Mackie has 14 output channels, fully configurable. We'll chew up 10 of those for stereo IEM, two for mains, and one for Subwoofer and have one spare..
  • Create New...