Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Registered Products

MikeMcK's Achievements


Apprentice (3/14)

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

Recent Badges



  1. MikeMcK


    Why? A see this a lot, especially on TGP, and I always wonder why. It reminds me of a friend who used to be near the front of a very long line every single time Apple released a new anything. He'd get up early, drive wherever (usually Manhattan from central New Jersey), wait and hand over his money. I finally realized it was kind of a hobby. When he'd had the latest iPhone for a while, another friend asked him what it could do that his old one couldn't. He came up with a few things, but when she said, "but you don't do any of that", he just got frustrated and a little angry. I've only had my LT for a few months, and after a few dozen gigs, I've homed in on a small set of patches (mostly Fender, Marshall, Vox amps, plus one whole bank just for acoustic gigs). To be frank, I need to spend more time tweaking these patches that I use all the time, and couldn't see learning a whole new set of capabilities. I get that there are power users, but at some point, don't you get wistful about being in a studio that had 5 amps or on a gig where you had one? Or has the tool become the end game, where using a Helix is more of the focus than playing music?
  2. MikeMcK

    QSC K10.2 Issue

    This has been discussed a lot recently and it's a real problem. I know someone who ran into this with new 10.2s. The long story short is that it started with a fairly recent firmware revision. For those who don't know, once it happens, the only way to reset is a procedure which involves test tones playing through the speaker. The big issue is that it's not a firmware bug... it is supposedly a correction because they were getting too many blown-out speakers under warrantee repair. But the guy I know who had this happen has mixed professionally for a long time & does know his stuff. He's actually anal about sound and brings more speakers so he can keep gains and volumes right in their sweet spots. He swears the two of his that went had gain controls at high noon, that the signal to it was well in range and EQed (for use as monitors) with cuts only. It also happened in an air-conditioned hall (this was in the summer, and some claim it's heat-related) where he was mixing a wedding band at a reception. The only saving grace was that he'd originally planned to use them at the ceremony, and kept imagining 150 people, including a bride, waiting while the speaker blew through a set of test tones. No good. I had a close call when one of my 12.2s fell and died. It was just a loose wire, but word is that authorized repair centers are required to update firmware to the "Protect Mode 4 failure" version whenever they repair a K1x.2. I was ready to eat the cost of new EVs or something else rather than risk it on gigs.
  3. OK, I posted this one a few weeks ago. It's got a whopping 7 votes today, but I frankly think it'd be really helpful, especially to those of us who gig. I also think it'd be a relatively easy dev effort, whether they decided to add it to HX Edit or write a stand-alone app. It's a "setlist documenter" for when you'd like to print out a "cheat sheet" showing what's in your setlist... for each preset it would export data showing what FX are available, whether there's a wah, what the footswitch assignments are, etc. It's basically just a matter of someone exporting JSON preset data into a CSV format that can be manipulated and printed from Excel or Google Sheets. I'm fairly new to Helix and have done this manually, but I know there's an easier way.
  4. Newbie question for sure... I downloaded a couple of presets that had snapshots and used them on a couple of gigs. Tonight I wanted to create a patch for a song where the guitar cleans up and a chorus turns on for verses, and I figured 2 snapshots would do it. I was able to set them up in HX Edit and got them sounding like I wanted, but unlike the ones I'd downloaded, when I stepped on a Snapshot footswitch, the display reverted to stomp box mode. In order to go back to the other snapshot I had hit the bank switches again. The ones I'd downloaded don't do that... once in Snapshot mode I'll see 3 snapshots and I can select them at will... the display stays in snapshot mode until I hit a Bank switch to go to another patch. I saw in the manual, " NOTE: If you don’t want Snapshot footswitches to disappear after selecting one, set “Global Settings > Footswitches” > Knob 4 (Snapshot Mode Switches) to “Manual Return.” In this case, Helix LT stays in Snapshot footswitch mode until you press FS6 (CANCEL). " If that is the solution, then why do the patches I downloaded stay in Snapshot mode even though I never touched the global setting?
  5. I agree and that's the plan for now. I did post it on the ideascale page. It does seem like the L6 coders, who already have the JSON HLX schema defined in code and also have code to decompress HLS files into HLXes could crank out an HLS-to-CSV thing in no time at all. Might be an ideal challenge for an intern if they have them.
  6. That was the plan, but because I need the flexibility my main pedalboard is pretty large... multiple drives, delay, the Mobius as several mod pedals. Even then, I swap pedals in and out to match the gig, i.e. if it's an 80's band, I'll replace an OD with a Rat. I know I'll be winnowing down the number of patches I actually use, but that's another reason to wish I could quickly output a list of patches & footswitch assignments from a setlist file.
  7. That makes sense, and I went through some of this when I put a Mobius on my regular board years ago. I spent some time tweaking presets and moving them to the first 10 or so banks, and eventually memorized the locations after a couple of weeks. The issue for me is that I regularly gig with 4/5 acts, plus I do a lot of pickup gigs and sub in for people in a variety of genres. Even the guys I work with a lot don't stick to set lists and will tailor the set to audience response. Sometimes I don't even know going in whether it's half acoustic or all electric (I got a couple of 3Sigma IRs so I can use the Helix for acoustic instead of setting up a separate DI). That's why I got the Helix, so I don't have to load in an amp, electric pedalboard, acoustic, acoustic pedalboard with looper, etc. I did spend some time setting up USER1 with the patches I thought I'd use, but that's still a lot to keep track of. If a singer takes a request for "Money For Nothing", it's frustrating to know I have the perfect patch in there...somewhere, or to know I'll want a wah on a solo or a Leslie on a chorus, but not remembering which patches have them. For now, my low-tech approach was to type out a spreadsheet and laminate printouts, but I know my USER1 is going to change. It's awesome that a couple of people have reverse-engineered the L6 JSON schema to the point where they could code the graphical tools linked by @Hey_Joe above. But I could really use a subset of that so I could print some text data.
  8. I just went through this because I got an LT. The Thomann case for an LT was a slightly more palatable $135 + $65 shipping, but I spent a bit of time looking for alternatives in the US. I found things that were comparable at twice the price, and got the Thomann. That Gator looks nice, but (at least for an LT) the wheels seem like overkill, especially if you load in with a cart. In the meantime, the Thomann case was the best option, at least for me. I don't love the handle or clasps they decided to use, but the case does what it's supposed to do. Note that my whole Helix experience is still just a week or two old, so I have no idea how it will hold up over time. I was hoping to find an EWI case from audiopile.net. I have a few of those that have held up for years. The Thomann case seems almost on par, though the handle and clasps don't seem to be as heavy-duty as what you'd get from EWI.
  9. That they are, and I got frustrated enough to look into trying to code something myself. Once upon a time it would have been fairly straightforward to parse the .HLX files, I think, especially with some kind of JSON library, but I last wrote code decades ago. And from what I read, the .HLS (setlist) files are just zlib-compressed collections of HLX files. I definitely appreciate the effort of those who came up with the graphical HLX viewers. It'd be ideal for me to output a spreadsheet-like printable table that I could laminate and gaff to stage... something like: block0 block1 block2 block3 block4 block5 EJ-CliffsDover PanVol LAStudioComp Minotaur Brit2204 IR 1024 PingPong THE Sound Brit2204 IR 1024 RetroReel TubeComp SimpleDelay Glitz Maybe I'm asking the wrong question... for anyone who gigs and has "fluid" set lists, how do you deal with finding the right patches quickly?
  10. Interesting. I'll try that tonight. Thanks
  11. I just got my LT last week and this week (Thurs., Fri., Sat.) will be my first gigs with them. One thing I got excited about was the built-in 12-string effect... I use a Mosaic a lot (and still will on band gigs; the Helix is just for duo and trio gigs). When I set up a couple of patches, the first thing I noticed is that it must use a lot of CPU... as soon as I select it in HX Edit, a lot of FX names go gray... is that your experience too or am I missing something and doing something wrong? Also, and in IMHO, I think the Mosaic might sound a bit better, and I spent some time tweaking the effect. The most obvious answer is going to be, "get a Variax". I have one (gigged it for a couple of years) but prefer to use my regular guitars. So have any of you been using the 12-string effect on gigs and been happy with it? Any tips or tricks I should know about? One more piece of info that may be important, I don't know... I'm hoping to switch between electric and acoustic, using the Helix for both (I set up a couple of presets using a 3Sigma IR), and would love to get a decent acoustic 12-string sound on a couple of these gigs.
  12. Summing to mono on the left output makes the most sense, and is what I assumed when I bought it. But I thought I'd read something that said that was not always the case. Thanks.
  13. I feel like this should be a question that's probably asked and answered, but I couldn't find it by searching. Apologies if I just missed it somewhere. I got my LT last week and spent some time creating a decent-sized set-list of stereo patches. I got it for gigging and I can get away with a slight stereo spread on my PA, but house-sound gigs are almost entirely mono, so I'd like a set list of the same patches but in mono. Ideally, I'd like to copy the entire set list to another one and somehow convert them so they'll be usable in mono. I understand that I'll definitely have to do some tweaking, but it would be easier than going through each patch to add some mono block at the end of the chain.
  14. Thanks for the help here. I wound up copying the patch names from HX Edit (it saved as a single string) then using formulas in Excel to break the string into separate patch names. It saved time over typing the whole thing out, but I still wish there was a more automated way to do it. Eventually I'll settle in on the handful of patches I use on gigs and then I'll be able to remember them.
  15. I got my first Helix (LT) yesterday and spent some hours moving the presets I want to use to a USER setlist and then tweaking them. Is there any way to output a patch list from the unit or from HX Edit? Like "01A, DlxRvb..."" etc? The idea is to bring a printout until I start to remember which patches are where. It would be even better if it could include some info as to the FX in the patch. I exported the setlist and a few patches to see if I could make sense of what was in there, but no dice. I can't be the first one to ask for this, but I couldn't find anything on the forum or in the FAQ.
  • Create New...