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

codamedia

Members
  • Posts

    3,327
  • Joined

  • Last visited

  • Days Won

    114

Everything posted by codamedia

  1. I'm curious... how did you accomplish a "global boost" with the HD500?
  2. Considering you just responded to a 4 year old thread that nobody has taken part in for nearly two years.... I'm not so sure I would consider this "common". Yes... sadly there are failure rates but no product is immune to that. It does suck when it happens to you, but that doesn't make it a widespread "common mistake" as you put it.
  3. A few simple rules for best practice Do not plug into a USB Hub ... this often includes front ports on a computer. Use a USB2 Port.... NOT USB3 Do not use any USB extender cables Most USB issues are PORT related at the computer. Ports are often matched in pairs (sometimes quad) and devices can conflict. Example: A USB2 port is backward compatible to match it's lowest level device so if a USB 1 device (keyboard, mouse, other basic devices) is plugged in to one port and you plug the Helix into it's matching pair... you are inviting trouble. This is one reason it is always recommended to try different ports on a computer when problems occur.
  4. Always remember.... you do not have the same guitar as the reference therefore it will never match. That difference is likely more about the pickups/guitar than it is about the interface used. Every interface will be different in this regard. IME: it is very easy to compensate a digital signals volume once recorded without degradation. If one is louder than the other, just adjust them to match once recorded. I am pretty sure that when the input is set to AUTO the guitar will be loaded with the impedance of the first effect in the chain... EVEN when recording dry. That is why earlier in this thread I suggested that the OP change the impedance from AUTO to 1M just to eliminate that as a possible culprit.
  5. Stupid question.... Did you follow the update instructions exactly as written or did you just run the updater and hope for the best? Most problems are a result of a missed step along the way. Here are the critical steps some people miss... take NOTE of these, don't follow them. Follow the actual instructions but keep these in mind! Install the latest version of HX Edit (2.82 as of this writing) During the install... on Windows you will get an option of items to install. SELECT THEM ALL and install them. This includes ALL drivers as well as the updater, etc.... DO NOT OPEN HX EDIT! Connect your Stomp.... then run the Line 6 Updater to re-install the 2.82 firmware Follow all instructions carefully
  6. I agree with the others. If you just updated Windows 7 to Windows 10 but you did not update HX Edit (including the drivers for the Helix).... start there. IMO: Since your firmware is 2.80.... I would install that version of HX Edit and "all" it's drivers. Get the Helix stable, then update everything to 2.82 as per the instructions.
  7. What measures have you taken to make sure the difference is NOT in your recording rig, but from the Helix itself? If you have used a stereo block toward the end of you path then the left/right output could sound different. Place a MONO gain block set to unity as the last item in the chain. That will force everything to sum to mono before the outputs.
  8. IMO.... Open a support ticket with Line 6 through your account... Give them your two presets you show here... Explain the problem in detail to them Optional: Point them to this thread If they find the problem in your preset they will let you know what it is. If they can duplicate the problem, they will verify it as a bug and add it to their list for fixing.
  9. Once you wrap your head around snapshots you will find they are intuitive and relatively simple. Well worth the effort of learning. Short answer, yes! Command center can be used to send a limited amount of midi commands at the preset change and the snapshot change. You can also assign a single midi command to a stomp switch.... IIRC.
  10. Yes... I always import. I drag and drop within the impulse window if I want to move/copy an IR to another location, but I use import to bring it in.
  11. I just did another check on my machine... the IR names are exactly what "I renamed them to" before importing. Sorry, I have no idea what is going on with yours.
  12. Just a curious question.... Why don't you compensate the different in IR levels at the IR block? By default an IR block loads a new IR at -18 (iirc)... which is a bit of a safety mechanism :) There is a lot of room up or down left to work with. Keeping it at the block makes sure any blocks "downchain" are actually hit with an appropriate level, not just turned up/down at the end. As for the names.... try importing them into "blank slots" and see if the name sticks. If not... then it is getting the name from within the file, not the file name itself. I am pretty sure I renamed my files and they uploaded as such... but I can't say that with 100% certainty. It's been a while.
  13. Your description is not detailed enough... but I "might" know what is going on. Are you using a Helix LT? Are you talking about "performance mode" on the LT? If so... keep the following in mind with performance mode.... Presets are always B&W Snapshots are always B&W Stomp Mode displays in color. When combining STOMP/SNAP/PRESETS on the preset screen... the STOMPS should display in color, everything else will still just be B&W If you are not using an LT and/or Performance mode is not the problem, you need to provide more details :)
  14. If the Headrush sounded great, and the FOH sounded great.... then it is the "Laney" I would be questioning. Do you have the Laney set to FRFR (full range) mode and does it appear to be working properly? On your LT... you could set the Global EQ to 1/4" outs and feed the laney from those. The XLR signal to the FOH will not be touched. Then just adjust the global EQ to make the Laney sound the way you want. Although IMO.... anything more than subtle changes points to a bigger problem. The LOOK can always be a PROP, it doesn't have to be something functional. That trick has been done for decades. Times are also changing.... I saw Skynyrd last year and they didn't have a single amp shown on the stage. That is something I wasn't expecting from them... amps were always a part of their "look". FWIW... at concert shows I don't use a PROP... but in small clubs where other musicians are present (and ever judging) I will often put an amp behind me for show. A fake amp always makes a modeler sound better :)
  15. So you took a heavily distorted preset from the Stomp and you are adjusting all your pedals to that? I wouldn't expect that to sound very good... no matter what I tried! IMO, that is completely backwards to how I would try and work the stomp into an existing pedal board. If you like the stuff you have.... integrate the stomp as an additional piece, not as the center piece... and certainly not as a center piece using a stock preset!
  16. codamedia

    Helix 2.9

    Aside from clipping indicators and output meters, 2.9 says it will also include "gain reduction meters".... Unless implemented in some very odd way, what you are suggesting is usually what those are for.
  17. Turn off Global PC Change within the Helix (it's in the global settings somewhere) When you want to change the reverb on the Lexicon... use the Command Center (in a given preset) to send a PROGRAM CHANGE via channel 1 (this is assuming the lexicon just worked on channel 1). or Change the Lexicon to a different midi channel (2 thru 16)... this should make it bypass the global changes from the Helix without turning them off in the Helix. Same as #2 above... but send the change over the channel you set the Lexicon to (2 thru 16)
  18. codamedia

    Helix 2.9

    In regards to output meters, we don't know how the meters will be calibrated so it's impossible to agree or disagree with your statement. Peak or RMS Slow or Fast Weighted or Not Weighted (this takes "bass energy" into account) Which meter system was used? I think it is best to wait and see how they have been implemented/calibrated before we write them off as useless :) Anybody familiar with meters knows how to compensate volumes for various tones/signals using those same meters. The more you do it, the better/faster you get at it. EG: I KNOW where I wan't my lead tone compared to my driven tone, clean tone, acoustic, baritone, wah, banjo, pedal steel, etc...etc... etc... Once I am familiar with the meter I am working with, I can make these adjustments with a 95% - 100% success rate every time. FOR ME, that process is WAY FASTER than the proverbial "use your ears". PLEASE NOTE: I did say 95% - 100% of the time. There are certainly times when a final adjustment is done "by ear" but only when in context... such as in a rehearsal or on a stage with the full band.... not isolated.
  19. Helix MIDI Out > Lexicon MIDI IN By default.... changing a preset on the Helix SHOULD change the preset on the Lexicon. If this doesn't happen you have to make sure both products are setup to the same midi channels (usually 1 or OMNI/All by default) and that the Lexicon is set to receive Program Change messages on that channel. Only after you get it all working and you are comfortable... I recommend that you disable "global program change" on the Helix, and learn how to set presets to change the Lexicon only when you need to using Command Center. IMO... MIDI is WORTH THE TIME! Learning the basics is not difficult, and will come in handy with many things.
  20. I hate to say it... but there is some really good reading over at TGP about the differences between the HX Stomp and the new POD Go. A lot of this info will apply to the HX Effects as well as the Stomp... of course minus the amps and interface options. https://www.thegearpage.net/board/index.php?threads/line-6-pod-go.2113195/ (jump to page 28 to see DI really dig in and explain some differences) Eric (Digital Igloo) has unleashed a lot of information about the POD Go over there that has not been stated here (that I can see). Aside from the obvious I/O differences and complete lack of MIDI, the main things you need to consider about the POD Go that has been made clear over there are.... There is no compatibility promise with other products in the HX line. It is not "unified" with the HX line (remember what 2.8 was all about). It will follow it's own update path and have it's own editor. You are not eligible for the discounted Helix Native upgrade price. The DSP is a little less powerful than the Stomps... (I don't know about the HX Effects). This may effect future updates compared to the HX line such as poly pitch shifting. There is only a single signal path... no parallel routing Many blocks are fixed... this means the EQ block can ONLY include an EQ model, nothing else. Same with Volume/Wah, AMP/Preamp, Cab/IR. There are only 4 wide open blocks for you to do whatever you want with. The looper is much shorter... but no exact length was given. Don't take my word for any of this... head over and read Digital Igloo's comments in that thread... they are quite insightful.
  21. I am very happy with the IR(s) I have in my "go to" list... but I will have to give your method a try... thanks for sharing. I could be missing out on some really nice IR's that I wouldn't think to listen to. I know that question wasn't for me, but IME... certain speakers are synonymous with certain amps. EG: AC30 and bluebells/silverbells, Plexi and Greenbacks/Creambacks, etc... etc... A speaker is 50% of the tone.... and those combinations create the sounds we are familiar with. That doesn't mean you can't or shouldn't experiment to find what you like, it's just good to know how those familiar tones are created. After saying that I must admit, I generally stick to one speaker for all my amps :) MIC choice and placement is very different. IMO that is all about experimenting to find what you like.
  22. If you attempt to try all IR's your ears will fatigue quickly and you will never find what you really want. The advice is already given in this thread so I won't go into detail.... but you need to research what you like (cab/speaker/mic/mic position) then zero in on those IR's within the package. Each IR is labelled to include those items so you just need to learn the lingo of the package.
  23. OK... so it's just a lack of high end clarity in your direct signal. Since you say it is happening with ALL of your instruments then it shouldn't be instrument specific (ie: a dull pickup) so I will suggest looking at general potential issues.... The greatest "common" tone roll off in any rig is the cable(s) being used. Have you tried other cables... preferably ones of different make/model and length? Did you set the input impedance to 1M (fixed) rather than auto as I suggested earlier? If AUTO is setting it to a lower setting, you WILL lose high end. Are you sure you are not processing your dry signal in your DAW in any way? If your DAW has "input plugin" capability, are you sure it is empty or at least bypassed?
  24. codamedia

    Helix 2.9

    I have no issues with my tone.... That said, I am looking forward to having the new metering options. Thanks for the heads up that even the mere suggestion of an improvement (if we even feel they need any) will be met with ridicule and shame from certain forum members.
  25. You and me both.... complete oversight on my part. Thanks for the update... glad you got it working.
×
×
  • Create New...