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

HonestOpinion

Members
  • Posts

    5,003
  • Joined

  • Last visited

  • Days Won

    71

Everything posted by HonestOpinion

  1. Not quite sure this is the case without stats to back it up, "many of us" might be a bit more accurate than "most of us". It certainly is good but this issue does need to be addressed.
  2. The first thing I would try is a high cut at anywhere between 5-8khz in either the cab sim or in an EQ block after the cab sim. You can experiment with where it sounds best for the preset you have selected. After you get the high end tamed you can start fine tuning the EQ and amp settings.
  3. It might be worth going through the global reset process or even completely reinstalling again and trying to restore your presets. If that does not work you may want to consider rolling back to the version of the editor and firmware you used to backup your presets. Then back them up again, go through the upgrade process one more time, and restore your presets. Depends on how much work you want to put in to preserve your presets. Good luck!
  4. You are correct, you still need to run the Updater to install the latest firmware but the Helix App will install the latest Windows driver, Updater, and the Editor as long as you leave the checkboxes checked (they are by default).
  5. If you have not already, make sure to run the global reset after doing your firmware update.
  6. I would suggest downloading the latest version of the Helix app 1.11.1. It is still marked beta so you will have to check the "Beta" checkbox on the download page. Let it install everything. I don't think it is getting a certificate error, but if it does you can ignore it.
  7. This would be great but until they change the USB design and protocol to collapse the USB Type "A" and USB Type "B" into one Type "A/B" device, we are going to see manufacturers forced to make the difficult choice between providing one or the other, or when we get lucky and at increased cost and risk of equipment damage, both. The two types design ("A" or "B") was originally intended by the USB designers as a safety feature to prevent one device from shorting another but it definitely has its unintended consequences. I had this same complaint when I got my Behringer XR18 which allows recording to a DAW but does not allow recording directly to a USB dongle. A feature that is ironically available on the lower priced XAir mixers. However, although the lower priced XAir mixers can backup or record to the USB stick, they cannot connect to a computer for use with a DAW. A compromise we are stuck with for the moment and not one that has been dictated by Line6. Line6 chose to give us the ability to use the Helix as a soundcard and controller as part of a DAW through the USB connection. Probably by far the preferred option given a choice of the two ways to implement a USB connection. The only way I know of to get around this is to include both types of USB jacks and this does currently increase the chance that someone will use them improperly and short out the Helix. Here is a good article on the two USB types. http://digital.ni.com/public.nsf/allkb/0E543C70602423C486256DB8006208DE
  8. Let me first say that I am a big fan of the new editor. I hate to be redundant but I just want to keep this suggestion in the Line6 hopper if at all possible. Please consider implementing dropdown menus for text based parameters. Graphical bars are for numbers, they have no place being used for multiple textual options where you need to see all the choices at once. Adding graphical switches for places there are only two options like on/off would not be a bad idea either. I know you want to keep a consistent interface with other products and someone decided that using all bars would look really nice but it is actually IMHO a big miscalculation on how to implement a good editor interface. A combination of pulldown menus, switches, and graphical bars would be a much better way to go. Given the genius of the scribble strips, cap sensitivity, and all the other unique UI features on the Helix and how well they display useful information it seems like a huge step backwards to ignore the utility of dropdowns and switches in the editor. One of the places the Helix excels is in its user interface and I see no reason the editor should be any different. I added this idea to Ideascale and I hope it is not too soon as I know we are still in beta and the editor is still changing. Just thought it might help in getting an idea of whether or not people would prefer this approach to all bars. I have added this to IdeaScale here: http://line6.ideascale.com/a/dtd/Dropdown-menus-for-text-based-parameters-switches-for-on-off-or/814861-23508
  9. Oh yeah, how could I forget scribble strips, any mixer or MFX that does not have them or some textual equivalent is not even on my radar any more! This is the difference between having to remember what some random numbered input (on a mixer) or footswitch (MFX) represents rather then having them meaningfully named, potentially across over a thousand presets. Scribble strips or something like them are destined to become the norm. No more having to remember that input #6 on my mixer is the rhythm guitarist or that footswitch #3 on my Helix is the "Teemah" distortion. Masking tape and magic marker, feh!
  10. So if I understand your point correctly (and I well may not, I have not read the entire thread), even if the Helix can't anticipate what you are going to be playing it through, and allowing for different output options (FRFR, PA speaker, guitar amp), "why are there 'unpleasant' frequencies present in an amp and/or cab model regardless of its final destination, particularly at the high and low end where they would be easy to cut in the emulation?". If that is what you are getting at I kind of wonder the same thing. I guess we do get a huge measure of flexibility in return for not building these cuts into the amp/cab emulation as we can always dial them in ourselves. I can also see where getting some of the nuances of a mid-bump or other EQ nuances in the 75hz-5khz range would be almost impossible to get consistent across the huge variety of speaker/cab/mic destinations available to guitarists. I think it would be great if there was some kind of global EQ options where you would designate whether you are using a full range speaker or a guitar speaker and the emulations would automatically be master EQ'd accordingly. If you wanted to take it to its logical conclusion you would have a database of amps and speakers that would actually include their top and bottom end frequency range specs as well as any other mid bump or other EQ characteristics unique to that equipment. You would dial in your PA speaker or amp and cab, e.g. "Mesa Boogie Mark V combo" and the global EQ would adjust all the presets for your amp/cab/FRFR/PA speaker. Just speculating on what would be cool to have on a future modeler of course, not expecting anything like this with the Helix. But down the road it sure would be awesome. Kind of like Logitech Harmony universal remotes which have a database of all other remotes and can automatically dial up the IR codes for any remote you have.
  11. When I look at the frequency response charts on for instance the Celestion speaker website the frequency range is usually in the neighborhood of 75hz - 5000khz. The rolloff on gutiar speakers on the high end starts much sooner than 14khz, it actually starts at 5khz and rolls off steeply for almost every guitar speaker they make. The frequency response on Eminence speakers tend to be in that ballpark as well, at least for 12" speakers. I use Celestion as a sort of general rule of thumb as they make some of the most used and most musical guitar speakers out there (subject to personal preference of course). I find that by the time you get to 14khz direct through a full range speaker such as an FRFR or PA speaker you can have some real icepick high end going on. I usually cut in the 5-7khz range. http://celestion.com/product/16/G12M_Greenback/ http://www.eminence.com/pdf/EJ_1240.pdf
  12. You could probably just reformat the USB drive and copy over the latest Helix pdf and any other support documents you want to the provided USB drive. That would give you the updated manual. If not I am sure Line6 would have no issue with sending out a replacement USB drive.
  13. Perhaps some other intrepid Helix users will give it a test. I am not quite ready to go down that road yet as my whole motivation for getting the Helix was to consolidate my rig but for some users this may be the ideal workaround while L6 works on latency and spillover. Thanks for the suggestion, I may avail myself of it yet.
  14. I have to agree, the built in expression pedal, all-in-one approach was my prime motivator for getting the Helix. I am on a constant quest to streamline my rig. That combined with the easy to use UI and plethora of input/output options are what have me using the Helix way more than the Axe-FX.
  15. A less than ideal as you say workaround but a great idea nonetheless. I would think as long as the decay on the reverb is long enough you should be able to somewhat mask the preset change gap with an external reverb unit as long as it is the reverb's output (not the Helix) which is connected directly to the guitar amp or PA. Otherwise, when the Helix switches it may momentarily mute the reverb. You may not get the trails within a return loop although I would certainly give it a try. Please let us know how it goes.
  16. A simple solution would be to use the min-jack (3.5) headphone output on the iPad with a commonly available cable that goes from mini-jack and splits to two 1/4 male connectors. Just plug these into two return jacks and you will have a stereo input. You would then set up an input block and path that uses the returns you plugged the iPad into. Set the output block for the iPad path to whichever output you are using for your guitar amp. If you wanted an even simpler method, and don't care if the iPad is in stereo, you could use a mini-jack to 1/4. stereo out of the iPad headphone summed to a single mono 1/4 output plug. As you are going out to a guitar amplifier you probably want the iPad summed to mono anyway. I think this should work just fine. Mono to a single return input http://www.sweetwater.com/store/detail/CMP110?adpos=1o1&creative=54989267161&device=c&matchtype=&network=g&gclid=CLLzvdmE-csCFRJZhgodys0ADQ Stereo to two Helix return inputs http://www.sweetwater.com/store/detail/CMP153
  17. Another possible solution is to use the Helix as your sound card, the benefit of this is there is less latency then the sound having to go from the Helix to your PC's sound card. Just plug headphones into the Helix or you can even connect the Helix to your computer's powered speakers directly.
  18. 110% agree. Could we please get this pinned! It would be mutually beneficial for users and Line6 alike, and should save Line6 a lot of time answering questions and having to respond on the forum.
  19. I also like the ability to be untethered and work offline in an editor but it might be a synching challenge for L6 (not that it can't be done). Your best alternative for working remotely with an iPad right now might be this although you would still be required to have your PC connected to the Helix and the Helix turned on: http://line6.com/support/topic/19535-control-helix-app-from-ipad-or-android-tablet/
  20. I did intend for it to be on the Helix itself as the editor was not even out yet when I posted it to IdeaScale. Plus, I see this as most valuable for practice and gigs through the PA where you are more likely to encounter feedback and less likely to have an editor set up. However, it would be nice to have it in both places.
  21. I considered that as well. I have no idea how much an RTA consumes in terms of resources, you could well be right that it could be a hog. Even if I had to bring it up in a preset of its own it could be a valuable resource for finding feedback. If it is not too resource intensive it would be awesome if it could be turned on/off with EQ blocks.
  22. +1 Awesome! Ultimately it might be helpful to see these grouped under headings like "EQ", "Effects Settings", "Amp Settings", "Routing", "DT", "Variax", "Live Performance", "Recording", etc.. I like the way you credited the contributors by including their screenames!
  23. Those will be fantastic additions! I would still love to see scenes on the list for the editor, even if it is somewhere down the line. The editor seems like it would be the easiest and most natural place to implement them. I think it would be one of the greatest possible uses for the editor. Great beta though, lovin' it!
  24. Here we go again... If your song requires complicated sound changes, there is no scene functionality to accommodate it, you will have to tap dance. If your preset requires two or more scenarios that use a lot of DSP, you need additional presets as you won't have enough DSP to split within one preset. All of these arguments have been made over and over. It makes no sense to me to insist to people with a different set of requirements that they should change the way they are playing or that they can do everything they want within one preset. Can we please just acknowledge that for some (many?) users lower latency and spillover enabling preset switching would be a very desirable objective. For players without those requirements, I am perfectly able to see that the Helix is working for you. Why is it so difficult to see the other side of the street? I don't get it.
×
×
  • Create New...