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

HonestOpinion

Members
  • Posts

    5,002
  • Joined

  • Last visited

  • Days Won

    71

Everything posted by HonestOpinion

  1. No issues, don't care who answers these if it helps the forum user get quick assistance.
  2. I concur with datacommando's advice. This is exactly how I would proceed. If after experimenting with a simpler preset with basic, and I would suggest mono routing, and minimal blocks, you still get the same results with the looper hopefully someone else can confirm your results from an uploaded file. At that point opening up a ticket with Line6 describing the potential bug would probably be the way to go. Btw, when you test this with a simpler preset, if it does not demonstrate problems with the looper, you can build the preset back up, block by block, to resemble the preset that is having problems with the looper. This approach might help you determine exactly what causes the looper to impact the preset when used in Native. Have you tried removing the looper in that preset directly on the Helix(rather than Native) and seeing if the sound changes? If it does the issue is probably not with the looper but elsewhere in the preset or even on your device. Could be anything from something off in the routing for that preset, a wider problem with your latest firmware install, or mismatched versioning of HX Edit, the firmware, or Native. It is important that you check your versions of HX Edit, your firmware, and Native and make sure they are matched. Otherwise moving presets between the Helix and Native is bound to manifest issues.
  3. Also check in HX Edit under 'Help' --> 'About HX Edit' and make sure your firmware and editor version are matched(e.g. 3.11).
  4. If you upload your preset someone here, someone will more than likely take a look at it and might be able to pinpoint the problem.
  5. As you are aware, the Helix sets the volume block to 'EXP 2' by default. My suggestion is that as a best practice, you leave it at the default unless you have an incredibly compelling reason not to use that setting. Fighting it is prone to user error and It seems to often lead to problems with assignments. It also means you can't go with the default assignment to 'EXP 1' for example when you add a Wah block. Why put yourself through those gyrations? It is also worth checking to make sure your global settings --> 'EXP Pedals' --> 'EXP 1/2/3 Pedal Position' is set correctly to your preferred behavior.
  6. LOL, I have had and used both the L2m and L3t speakers with my Helix for years and I am actually preferring my Powercab+ right now due to its innately more traditional guitar cab vibe along with its hybrid FRFR approach. Who knows though, maybe at some point I will switch back. They all work well with the Helix.
  7. ^^This! Update your firmware to 3.11. You should be able to do that via the 3.11 version of HX Edit you installed. Look for an update in the bottom right hand corner of HX Edit or go to 'Help' --> 'Check For Update'. Do a backup, global reset, and restore, as detailed in the firmware update notes. Check 'Help' --> 'About HX Edit' and make sure the firmware and HX Edit versions are the same when you are done.
  8. As far as I know there are no EQ blocks on the Helix that have a low-pass(high cut) filter that goes below 1khz. The only thing I can think of that might work is somehow using the 'Split Crossover', which goes down to 25Hz, to maybe rig something up to your liking. I guess another approach would be to get tricky and have the expression pedal work two or more parameters simultaneously on the Parametric EQ. The 'Tilt EQ' also has a 'Center Freq' parameter that can be set as low as 100Hz. Don't know of any way to explicitly set the curve to logarithmic for any block other than 'Volume'. Note: The Helix EQs do have the high pass(low cut) filter available down to 20Hz but you were probably already aware of that.
  9. My first notion would be that you have the wrong version of HX Edit loaded. Were you working on HX Edit or the LT when this happened? Check 'Help' --> ' About HX Edit' in HX Edit and make sure your HX Edit version matches your firmware(3.11 hopefully). Load up the correct version of HX Edit if they are not properly matched. Don't forget to do a backup, global reset, and restore afterwards. If you do have the correct matched versions of the editor and the firmware you could also try a backup, global reset, and restore.
  10. You can have trails when switching snapshots to, for example a clean sound within a preset. The easiest method is using one of Helix's onboard delays and set the trails parameter on. If you rely on the Maxon in your loop for delay then per your post regarding your routing, if you switch to a snapshot that does not include the loop with the Maxon delay then of course you will be cutting of your trails as well. Perhaps there might be a way around this by putting the Maxon's loop on a parallel path so that when you switch to the clean snapshot you could turn only it's send off but leave the return on allowing the Maxon to continue sending any trails but not receiving any new signal in the clean preset. This might allow whatever was last sent in the previous high gain snapshot, before the switch to clean, to trail through. Don't know, have never tried anything like that.
  11. I actually think this setting was a welcome and extremely useful addition. I used to assign my impedance('Guitar In-Z) value to snapshots and switch it according to which block was the first active in the snapshot, so for me the 'First Enabled' option gave me an automated and more elegant solution, active in every preset/snapshot, that does not require additional snapshot editing.
  12. Seems like snapshots are working on some presets so this is probably not the problem but just to check the basics... Are you sure the parameters that you are changing from snapshot to snapshot, e.g. the Drive on an amp, are assigned to snapshots? If they are properly assigned they should be showing up with square brackets "[ ]" around the parameter's value. Hate to offer up the usual procedure but if all else fails I would try a backup, global reset, and if that does not fix things then download HX Edit again and use the Line6 Updater to reflash the firmware, again followed by a backup and global reset (Update: just noticed phil_m suggested this as well). It is a best practice after importing presets or even copying them to restart the LT and let the new presets go through the rebuild process before editing them. Also, check in HX Edit under 'Help' --> 'About HX Edit', and make sure that both your firmware and HX Edit version are matched.
  13. Things have changed since the earlier impedance discussions in this topic. As many are aware of, later firmware versions added a global setting to allow the player to set the 'Auto Impedance' parameter to either 'First Enabled' or 'First Block' ('Global Settings' --> Preferences --> 'Auto Impedance').
  14. Although as you mention you can change the Output block's level with snapshots you can also change it without switching snapshots. First assign the 'Level' parameter of the Output block to a footswitch and then, for example, set the 'Min Level' = "0.0 db" and the 'Max Level' = "+3.0 db". Clicking the assigned footswitch on will then boost the Output block's gain in any snapshot to +3db. That approach works well for me as I have my switches set to 'Snap/Stomp', top and bottom row respectively. Nothing wrong with using a 'Gain' block either though. Some players prefer, at least for some presets, using one in front of their delays or reverbs as bypassing or activating the Gain block then does not impact the volume of the reflections or repeats for the last note(s)/chord(s) played before the 'Gain' block is activated/bypassed.
  15. Just don't get something less than you need or expect to need in the near to mid term. I have the Helix and have never regretted getting a model with all the bells and whistles. The Rack is appealing too. If cost is not the determining factor, you love scribble strips, a heftier and slightly larger build, headphones level knob, and you think the additional I/O options might come in handy get the Helix. If you don't need the options unique to the Helix Floor/Rack, get the LT, it is less expensive. Can't go wrong with either IMHO and they both have the same processing power.
  16. One piece of advice I have seen when dealing with a parallel loop, don't know if it will help, is "When using a parallel effects loop, you’ll want to be sure your effects are able to be run 100% wet". So on an HX device that might translate into any effect running into the amp's parallel loop having the Mix parameter at max. Maybe also on the Helix set the 'Dry Thru' parameter on the Send to 0.0db and the Mix parameter on the Return set to 100% (=wet) as well. Don't know if these or some combination of them will do the trick but worth experimenting with. I don't run 4CM but maybe someone who does can run with these recommendations and further elaborate. https://www.sweetwater.com/insync/use-amps-effects-loop/ https://killerrig.com/4-cable-method-definitive-guide/ For the DIY'er: https://www.vertexeffects.com/diy-buffer-4cm-wet-dry
  17. And don't forget to run the 'File' --> 'Extract Files From Backup' command in HX Edit before each time you upgrade your firmware(and any other time you please) to keep your own Factory and User preset archives going forward. It will automatically extract all your device's individual presets into well ordered directories from any backup. Btw, this command has the almost unique distinction in HX Edit of being able to be run even when your HX device is not on, connected, or even plugged in!
  18. Worth noting with effects like this, and you see a bit of this in the video, is that anything you can do to adapt your playing technique closer to one that might be used with the instrument you are trying to emulate will really help to improve the illusion. I have found the same principle applies when using a guitar synth to emulate instruments other than the bass. For example, playing a passage with a crisp fast attack when trying to emulate an instrument that is usually played with a more legato approach is inherently going to sound less convincing.
  19. Exactly, start with firmware/software, eliminate that as a possible cause then move on to hardware. Have to say though, I can't begin to count(a lot) how many users I have heard proclaim with 100% assurance and finality that they suspect or definitely have a hardware issue only to find out it is related to the update process not being executed properly or some other non-hardware related issue. In this case I agree though, looks like @Maxy71 did what he needed to do on the firmware/software side and this is quite possibly a hardware problem. Just pays to eliminate the stuff you can do yourself first that may save you a return/repair and downtime on your device. It would be interesting to know what percentage of devices returned for repair or even refund, are simply victims of a failed update. Grateful to everyone on this forum who shares their knowledge and experience. What a great resource! Oh, and thanks for the entertainment during the quarantine!
  20. I noticed you said you did a factory reset and then reinstalled the 3.11 firmware. You also need to follow a firmware update with a factory reset and restore. Otherwise, weird bad stuff can ensue. Looks like you already took this in for repair but you may or may not have needed to depending on whether you did the reset/restore after the firmware upgrade. I think the next step in the ongoing evolution of the Line6 update process should include an automated factory reset and restore. Don't know if is possible for them to do an automated factory reset via the update process(rather than the user initiating it by holding down switches and powering up) but if it is, this would cut down dramatically on users reporting issues. Remarkable to me how many people neglect to do these steps after a firmware upgrade.
  21. An eminently rational and sensible conclusion and one with a high percentage chance of aiding you in tracking down the source of the issue. Happy troubleshooting!
  22. An interesting link on the topic. You can purchase IRs for mandolin and violin as well. https://www.3d-varius.com/impulse-response-acoustic-instrument/
  23. More free IRs: https://www.joshuacasper.com/blog-post/convolution-reverb-impulse-responses/
  24. I was suggesting changing the global settings 'Ins/Outs' --> 'Output Level' = "Inst" on both of the HX Stomps. This sounds like you changed to a different input on the PA(which is also worth trying). Have you tried any of the other suggestions? You should be able to run several HX Stomps at the same time. If you haven't had the opportunity yet it is worth walking through the HX Stomp to PA setup step by step as well as the settings on the Stomp and the mixer and systematically eliminating possible causes. Not saying it isn't possible but looking for a magic bullet in someone else's dual Stomp setup may or may not yield results. The usual suggestions regarding eliminating ground loops, perhaps fluorescent lights, and other sources of noise apply. DI and hum eliminator boxes have been a solution for some users with noise issues. Also worth trying plugging both stomps in the same power strip or different strips. There are several topics around here on the subject of noise if you can search them up. Good luck with this!
  25. Hate to ask but if you did a firmware update did you do a factory reset and restore afterwards? If not, start there.
×
×
  • Create New...