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


  • Posts

  • Joined

  • Last visited

  • Days Won


bsd512 last won the day on November 26 2018

bsd512 had the most liked content!

Profile Information

  • Gender
    Not Telling
  • Location
    North Carolina
  • Registered Products

Recent Profile Visitors

1,424 profile views

bsd512's Achievements


Proficient (10/14)

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

Recent Badges




Community Answers

  1. bsd512

    Helix 2.9

    Past the mid-way point, so ... shorter than it has been.
  2. bsd512

    Helix 2.9

    I'm not exactly "meh". I'm always happy with some new amps and pedals. The IR thing should be nice for folks that use IRs. I used to be all-in on IRs but now I prefer the stock cabs. But I do agree that Helix is pretty near perfect the way it is. I'm so happy with the Helix and everything it does, unless they have something I haven't even considered planned for 3.0, I'm thinking Helix is more on a slow evolutionary path. If they changed it radically, I may not like it anymore! So I'm perfectly happy with incremental new amps/cabs/pedals, bug fix and polishing updates. I would really like something like a FreqOut pedal built-in.
  3. No problems with iPhone here ... until I tried to use one to control amps and gear settings. So maybe implementation of those particular apps? I'm not opposed to the concept, just that the ones I've personally used left me disappointed and I wished for good old regular tactile buttons and dials, and left me with a distrust of touch screens which seemed instead to serve the product price point (quality buttons and knobs are expensive and can't be easily changed) instead of making it more usable for me. If they work reliably, sure, let the company save some money by not having to put on physical controls like humans with fingers and opposable thumbs were meant to manipulate and turn our fingers into glorified computer mice instead. :-) My preference is physical touch and tactile feedback, though. It's just my preference, and I'm probably in the minority - people seem to be clamoring for bluetooth iPhone control of their gear, so I'll eventually have to deal with it.
  4. I have to admit, though, it does look really nice. $1600, though ... pretty steep, but looks pretty featureful, comparable to Helix so maybe that's not out of line. A lot can happen between now and September. But it does look like if you back out of the pre-order, you don't lose anything so you're not fully committed financially if you pre-order - you get a full refund of your deposit. But I wonder why they announced so early?
  5. Hmmm ... from that article: ... In the end, though, capacitive touchscreens are not foolproof. Living, breathing people with thick callouses on their fingers—think guitar players or carpenters—struggle with these touchscreens because the dead skin on their fingertips prevents the flow of electricity. ... Lol :-) So ... maybe not the best interface marketed to guitarists with our calloused fingers. :-)
  6. Too unreliable for control - like I mentioned before in using it for Amplifi (and other products, not by Line 6), touch your finger to a control point and slide, etc - it doesn't register. Your slide slides nothing. Try again - doesn't register again. Maybe it works the third time. Makes the whole device and interface feel cheap and cheesy. I remember watching and Anderton's review of a product like that and it was happening to them every other time they tried to use it, and even though they didn't comment on it, it was painful to watch them try and adjust simple things, like BMT on an amp. And I experienced the same thing on the Amplifi product that uses an iPhone as the touch screen. The advantages aren't worth the hassle - just my opinion, of course. A button or rotary is way more reliable when working on the device itself. And these issues don't present themselves when connected to a computer and using HX Edit. So I see it as fluff that cheapens the device and actually diminishes user experience. You did mention the graphic EQ - I think that would be great, but you don't need a touch screen for that. The Global EQ is like that when using HX Edit with the Helix. I wish the normal EQ blocks worked the same way in HX Edit. No need for a touch screen for that, though. EDIT: I forgot to mention, it would also be a real pain for folks with vision issues. We have a couple of blind folks on this forum using the Helix and can work the interface by remembering how many rotations, clicks, etc using the physical knobs to get the job done. So accessibility for folks that can't see the screen is an issue, too.
  7. I must be the only one that is glad the Helix does not have a touch screen. Or bluetooth. I used to have a Line 6 Amplifi that used a bluetooth app on an iPhone touch screen. Using it was an exercise in extreme frustration with constant bluetooth disconnects and the screen not registering slider actions - go to slide a slider ... nope. Try again ... nope. Third time - ok it worked. Then it disconnects arbitrarily. Try to reconnect ... nope. Exit the app, got to iPhone settings bluetooth. Reconnect. Re-open app - "app not connected to bluetooth". Arrrgh! Please please please do not do the stupid bluetooth and touch screen thing on Helix. :-) The capacitive touch switches are genius, though!
  8. I didn't say you had a problem. I'm glad you don't. And dealing with it in your own way - sure, I don't think anyone expects otherwise. Shedding light on issues is certainly allowed and appreciated. Not sure where you got the impression it wasn't allowed. If it wasn't allowed, a moderator would have come along and deleted your thread. Seems like there's a failure to communicate clearly here. If I can attempt summarize what your want out of this ... and you can correct me. 1. You wanted to shed light on a problem. You did so effectively - thanks to the help of fellow forum members who took the time to follow your instructions which take many hours to execute. 2. You don't want any help or solutions to it. You didn't state that up front. 3. You want it to be known that you brought this up to Line 6 support, and they - I'm a bit confused on this part - they acknowledged the problem but then told you to go pound sand? Or they couldn't reproduce the problem? I'm not sure.
  9. I can see losing a little confidence in something that has a (minor) flaw. However, extrapolating that minor and easily rectified flaw to a larger or more frequent and higher probability failure leaving you silent at a gig doesn't make a lot of sense to me. Also, it tends to indicate that you are not prepared to deal with any issue, like a bad cable or similar. No product is perfect, stuff happens. And you can extrapolate that statement to all aspects of life. Move on to another product if you must. I don't see a fan club here, I see people confirming the flaw and offering work-arounds so you can navigate it. If you do move on, be prepared to deal with different flaws from the different products or rigs you go to next, or you'll be jumping from modeler to modeler and spending a lot of time and money unnecessarily.
  10. bsd512


    I think once 2.82 starts showing up on new units in the store, a lot of these complaints will go away, simply because Line 6 changed the defaults for all stock cabinets to set the lo-cut to 80 and hi-cut to 8KHz. With these settings, the defaults generally sound much better and largely addresses what I think most people refer to as fizz. Sure, there's more folks can do to polish things up if they want from there, but from a stock defaults standpoint, that's a much better starting point for people going through FRFR PA speakers than the previous defaults in earlier firmwares of no lo-cut and no hi-cut - resulting in the dreaded "fizz".
  11. One thing I always do when upgraded is to first do my backups, then I reset my Helix back to factory default, clearing all setlists, IRs, reset global settings - the full factory reset. Then I do the upgrade. While I'm sure Line 6 goes to tremendous effort to translation prior settings and so forth, my reasoning is that there's probably a lot more testing going on starting from factory defaults -> upgrade. After the upgrade, then I just restore my setlists. And I don't make very may global setting changes, so I just take care of those manually. Not sure if resetting to factory defaults before upgrading actually makes a difference or not, but if something does go sideways, I know I took all reasonable measure to avoid problems. And coincidentally, I've never ever had a problem with a Line 6 Helix upgrade, and I've owned my Helixes for 3+ years and have never skipped an update.
  12. You're preset(s) would likely be a gold mine for the firmware developers for squashing these bugs. Please open a support ticket with Line 6 and include your setlist/preset(s) with instructions for how to reproduce the errors. I'm sure they could then run this whole thing under a debugger and figure out exactly what is going sideways and fix it.
  13. My issue is solved. Totally my fault. I'd been using that beta driver since 2016 with no issues. And I missed that a new one was release along with the 2.8 firmware. In my defense, the 2.8 release notes are 423 pages long and the audio driver is down below it, so ... I missed it. Installing the new driver (1.0.7) fixed everything for me.
  14. But the driver doesn't appear to have been updated by the 2.8 installation: [bsd@yyz]:/bsd- ls -ld /Library/Extensions/L6Helix.kext drwxr-xr-x 3 root wheel 96 Apr 13 2016 /Library/Extensions/L6Helix.kext/ [bsd@yyz]:/bsd- The driver I'm referring to is the one you get when select the "beta" checkbox on the Line 6 Downloads page, with hardware=Helix, software=All Software, and os=Mac OS X. That driver is needed to get output controls, i.e., volume control when using the Helix as the Mac system output device. That stopped working after the firmware update. Without it, instead of controlling the volume using the system volume level, you have to control the volume using each individual application's volume control. For example, bring up QuickTime to play an MP3, it plays full blast and ignores the system volume level setting without that driver.
  • Create New...