HonestOpinion
-
Posts
5,003 -
Joined
-
Last visited
-
Days Won
71
Posts posted by HonestOpinion
-
-
Absolutely you can place the RC500 after the Helix or you may want to place it in the Helix's FX loop for more control over what gets looped. Cabs/amps will work either way. You will definitely get more authentic sounding emulations of amps/cabs in 4CM but I don't believe your Mustang has an FX loop(?). To be frank that amp is a bit limited for what the Helix is capable of. You may want to turn off the cab and even the amp emulations when plugged in direct to the Mustang. An inexpensive and small FRFR like the Headrush FRFR-108 might be worth consideration and will definitely make it easier to preview presets for your church setup.
-
1
-
-
Dragging any block down in HX Edit or hitting 'Action' and then dragging down a block directly on the device will create that second path rd2rk referred to and as he indicated automatically create the split/merge.
-
3 hours ago, lou-kash said:
Overall size, weight and particularly modularity matter as well:
- For bands where I play bass guitar, usually I'm alright with just the Stomp alone. No need for a pedalboard at all. Just the Stomp, the power unit and two cables. Everything's transportable in my gig bag.
-
For bands where I play guitar, I need an expression pedal plus additional footswitches to change snapshots and Exp1/2 – the latter not directly avaliable on my old Roland expression pedal. But my "pedalboard" – a modified metal plate 26 × 32 cm that's originally been part of an office computer shelf – must accomodate all of it, and everything must remain loose so that I can always remove the Stomp when going to play bass. Hence I opted for Disaster Area DMC.micro which is "minimalistic" but flexible enough to do what I need plus having an extra footswitch input that I use for tap tempo. Those additional analog footswitches also come from my decades old "gear archives", i.e. apart from the Stomp and the DMC.micro I'm "recycling" material that I already had since decades.
As for DMC.micro vs MIDI Baby 3: DMC.micro can be programmed offline directly on the device, whereas for MIDI Baby you need an internet connection to change the settings. I definitely wanted the former.
In other words, even if the Stomp XL would have been already available last year, I still would have opted for the small Stomp because of modularity.
In other other words, there is no definite solution. Your mileage will vary.
All good points and for the scenario you lay out makes perfect sense.
-
Just thought I would mention that I have seen several topics regarding which MIDI pedal to get with the HX Stomp. Many here are trying to leverage functionality on an HX Stomp that they already own and I would probably be doing the same. I think it makes even more sense if you are controlling multiple devices(e.g. other effects, DAW, etc.) via MIDI. If you are adding a MIDI controller only for using with the HX Stomp I would probably opt for a small inexpensive MIDI controller that would not eat up too much pedalboard real estate or run up my overall expenditure on the HX Stomp. Feel like I am stating the obvious but if you have not purchased the HX Stomp yet though, and you think you will be wanting to add additional MIDI control to it, you should take a hard look instead at purchasing the HX Stomp XL or the Helix/LT.
The additional pedalboard space required, expense, and programming hassle involved in adding an external MIDI pedal might not be your best option when you could just be using a single HX device with more available switches as your MIDI control center. Might cost a little more initially but be worth it to you in the long run and in particular the step up to the Helix or LT brings many other features and benefits(dual processors, more I/O, etc.). I'm sure all this has occurred to may other users here as well.
-
5 hours ago, girore said:
I bought my Helix in 2017.
They had to repair the chip,? so it cost a lot of money. and it did work and i didn't do anything to harm the usb. So it was not a single usb repair. They also had to change the chip?
Grtz. Girore
If the shop that fixed it originally(was it Line6?) won't fix it uder warranty I would reach out to Line6. They are pretty good about repairs(sometimes even out of warranty) and even if they won't do it for free they may be able to do it more inexpensively or recommend someone who can. Sorry you are having to deal with this, what a PITA.
-
On 1/18/2019 at 3:53 PM, ledvedder5150 said:
Well, programming this thing to change the EVH channels isn't as easy as I thought it would be. I put the EVH into learning mode by pushing both channel select buttons. Lights start blinking. Then, in the HX Effects, I go to command center and select a footswitch. Set the command to bank/program command, midi channel 1, program 1. Press footswitch 1 on the HX Effects. Choose the clean channel on the 5150. Then exit the learning mode on the 5150. Then, I switch to channel 2 or 3 on the 5150 and press footswitch 1 on the HX Effects. Nothing happens.
Here is a YouTube video that I'm referencing.
This may not be what is causing your issue but I notice in your description of your sequence that you selected the clean channel on your 51050 after you put it in learn mode. That is correct according to the 5150's manual but the 5150's instructions for using learn mode seem to be indicating you are supposed to select the clean channel on the 5150 before you place the amp in learn mode as well. Pretty typical. Couldn't tell from your description if you did that first. That should put the clean channel on the amp in ready mode to learn whatever MIDI command you are sending from the HX FX for the currently selected channel. After you program the MIDI commands and click the footswitch on the HX FX then just follow the rest of the 5150's manual instructions for Learn mode. Repeat and rinse for the other 5150 channels.
Might also be worth trying a different program number for the HX FX in case "1" is causing the problem. Also does not hurt to save your preset on the HX FX as you go to make sure you don't lose your MIDI setup.
-
1
-
-
On 3/18/2021 at 10:21 AM, serneuro said:
I did that. If you put in front of the helix it makes a loud noise. If you put it after there is no noise. I would like to put it somewhere in the middle of the effect chain. Does anybody know how
22 hours ago, cruisinon2 said:If you're putting an external wah in the effects loop, then you can insert the loop anywhere you want in the signal chain... though why you'd want it anywhere but first is beyond me. Wah pedals expect a raw, instrument level guitar signal. If you start feeding it a signal that's already been processed in various ways with an amp model, distortion fx, etc, it's just gonna sound weird.
And, if you're just gonna be placing the fx loop first in the chain anyway, it begs the question, why bother using the effects loop in the first place? You're just using up DSP for no reason. Just plug the guitar into your wah, and then go straight into the input on the Stomp.
You're making this harder than it needs to be... see above.
Cruisinon2 is correct about general preferred placement for a wah and the potential benefits of not using the effects loop on the Stomp in this case if you don't have to. It might be worth figuring out why you are getting noise when placing the wah before the HX Stomp. Short of a defective wah pedal it could be a cable, battery, power supply or outlet, Input block level(Line, Instrument) on the HX Stomp, or even unshielded electronics on the guitar. Sounds like you have an alternative in place though should you need it.
-
1 hour ago, RitchieM said:
So, tried it, and the Stomp assignments work, but on mine AND the new presets, EXP1 / 2 are not assigned. Toe switches modes fine, but that’s it. Manually assigning to Volume or Wah and it’s all gravy, so going to rebuild / reset / reinstall. If I open an empty preset though and insert a volume or wah block, assignment to the pedal is correct.
also, the presets keep rebuilding, like all Factory 1, 2 and mine!
Yep, sounds like a global reset and/or another run at the firmware update are in order. Rebuilding all presets every time the device is restarted is definitely not normal and requires remedial action.
-
1 hour ago, girore said:
Hoi, my usb for helix doesn''t work. I brought it to repair, they did repair it but after 5 months it did not work again. To repair cost me 389 Euro's. So i am not going to do that again.
Is it possible to use MIDI to Upgrade the helix to version 3 instead of version 2.9?
Thanks
41 minutes ago, rizzy said:Hi,
unfortunately -as far as I know- it's not possible to update via MIDI.
Just out oft curiosity - what happened to your USB Port ?
5 months is not long ago. Is there a possibility that there's a warranty on the repair ?
Agree, I would definitely try to get them to repair it again under warranty unless the jack is showing gross mistreatment like having been stepped on and broken out. Btw, 389 Euros sounds excessive to me for a USB repair. That would be currently $463 in US dollars at which point I would have to laugh in the tech's face and promptly start my own repair service.
-
1
-
-
On 3/18/2021 at 11:36 AM, Nylander88 said:
If that doesn't work try a different cable, I have a noiseless cable that when connected to stomp and out to a monitor it cut's out sometimes, but when I use it with the stomp wearing headphones it's fine. also when I'm near my electronics it creates a bad noise, is this apart of your problem?
Agree, first swap out all cables and guitar and monitor as well if possible to isolate the problem to the HX Stomp. Could be your monitor starting to fail. Particularly if this does not happen with the headphones.
-
-
1 hour ago, arte7590 said:
As the title says...I installed HXEdit 3.0 on my Mac. Clicked check for update and it updated me to 2.92. When it finished, it was stuck at rebuilding preset 644. I pressed the footswitches 6&7 and it worked (although deleted all my presets, no problem thats why i backed up). Anyway, now i wanted to update to 3.0 but when I click check for updates it says "no new updates available". I bought my Helix in 2016 so I am thinking maybe my Helix is too old?? Or is there other reason for no update?? Thank you in advance for all suggestions.
27 minutes ago, silverhead said:Try installing and running HX Edit v3.01, which is the latest version.
This ^^^^! Also make sure you leave all the checkboxes checked when you install HX Edit 3.01 to ensure you get the drivers necessary to recognize your hardware. I got one of the earliest Helices also, that will not be an issue with the upgrade.
-
12 hours ago, RitchieM said:
Hi, thanks for the reply.
I restarted about 5 times and each time it was doing the rebuild, that’s why I was unsure if it was normal operation or not. I didn’t upgrade because I was a little worried about losing my tones, even though I backed them up, and then things kind of got away from me a little! Hahaha. As I say, I use Native, I just only use Floor for plying live, and my tones were always fixed for that.
i didn’t think of checking existing presets, will do that tonight, but my initial thing was why it didn’t just work. The pedals are engaging and seeming to “work”, it’s like they have been disconnected from the assignments. I will check again. As I said, wasn’t sure if it was a bug, and a search of EXP bugs only seemed to bring up the 2.8 era issue.
In terms of “backup”, the version of the software I was using, I couldn’t find that option weirdly enough (it was an EARLY v1), but did export tones and Setlists. Will have to investigate further.
As long as you do backups/exports you should not have to worry about losing your presets. The early versions of the editor did not include the full "Create Backup" option that exists now under HX Edit's 'File' selection on the menu. "Bundle" backups did come along at some point in the early versions of the editor. Good on ya for backing up your setlists and presets though. With 'Create Backup; and 'Restore from Backup' you will now have full and more extensive backup options that along with your setlists will also include your global settings as well as 'Favorites'(a recent feature addition you may find quite useful).
If wah assignment is working properly with either factory or newly created presets you can compare your old presets assignments and probably figure out what is wrong. Just restoring your old presets though might be easier and faster if it fixes the issue.
Make sure you have uninstalled the old version of the editor, downloaded and installed the latest version of HX Edit 3.0.1 and that the firmware version matches it. You can check that by looking at the top and bottom of HX Edit's 'Help' --> 'About HX Edit' screen.
Roughly how many presets are rebuilding each time you restart? Are they always the same ones? If so, I would back them up with the latest version of HX Edit and try restoring them to force a final rebuild. If you are getting a rebuild after five restarts as you indicated you are either moving/copying/importing presets each time you bring up the Helix or something is wrong, especially if all your presets are rebuilding. If the rebuilds persist I would start with a global reset and restore. If that does not work move on to another backup and repeating the firmware update and restore.
Btw, make sure you export a bundle in Native before you update it as well if you have not already.
-
8 hours ago, RitchieM said:
So, after all this time I have FINALLY updated my Helix from v1.06.5, brought my Setlist back in, but the Expression pedal doesn’t change volume or wah on my presets?? Clicking the toe switches between EXP 1 / EXP 2, the % changes, the wah engages, but it doesn’t sweep. Have I missed a simple trick from 4 years ago???
also, when I turn it on, it keeps saying “Rebuilding Presets”, is this normal??
I have searched, found v2.8 bugs, but can’t seem to find anything.
btw, have been using Native, so it’s not all a shock as to the new stuff!! Hahaha. But this little bit has baffled me.
thank you!
Ritchie
It is totally normal after an update for the presets to rebuild. You should restart the Helix and let that complete. They will only rebuild once with some exceptions. If you copy any of them to other preset locations or import backups, setlists, or presets, those will rebuild upon the next restart as well. Not all of your presets will rebuild however as they do after a firmware update. Until the rebuilds are complete don't bother expecting normal operation.
Not sure what is going on with your wah operation unless you are not fully engaging the toe switch or unless you have presets where you changed the wah's default assignment to something other than 'EXP 1'. Hopefully you made a backup before upgrading and you can try restoring that to see if normal operation is restored. Also be aware that your global settings have been set to their defaults so you probably want to review them. If you had for example Global Settings --> 'EXP Pedals' --> 'EXP1 Pedal Position' and 'EXP 2 Pedal Position' = "Global" before in your global settings you should restore that setting. Global settings from your last firmware can also can be restored from a backup.
Not sure why you are looking at 2.8 bugs. Maybe you are referring to the known issue with the expression pedal reported in the 2.8.2 release notes. If you updated hopefully you are on HX Edit 3.01, the 3.01.0 firmware, and Native 3.01. Btw, to each their own but I would recommend not waiting so long in between updates in the future. You have missed out on an incredible number of improvements, new pedals, amps, features and bugfixes. On the plus side this dramatic an upgrade should be like getting a brand new and improved 2nd Gen Helix.
You can always try a backup, global reset, and restore if the problems continue. If that doesn't work I might try updating the firmware again. Btw, does this problem with the wah occur only with your presets from your prior firmware or does it happen with the new firmware's Factory presets and/or new presets you create?
-
1
-
-
19 hours ago, zappazapper said:
Ha. Listen. You see this all the time, proprietary software being released into the public domain and developed by users and hobbyists. At some point L6 is going to abandon the Helix. Maybe we should start the campaign now.
Although it wouldn't open up the core functionality of a device like open source would, really when you think about it there are so many freeware or even paid VST/AU plugins available. All it would take is one of the current modeling companies enabling them to be run efficiently, relatively crash-free, and agnostically(e.g. any VST/AU from any company or developer that satisfied a general set of requirements or standard) and we would be halfway there. Obsolescence could definitely be delayed if you were able to just add plugins which are improving all the time.
You could potentially encourage existing industry leaders like Neural, Fractal, or Line6 to provide the equivalent of a Quad Cortex, Axe-FX, and Native plugin available to you to use simultaneously on your "open" floor or rack hardware. And again, there are mountains of freeware plugins available. Might take an optimized and powerful hardware/firmware platform but the technology seems to be getting there quickly. Some devices appear to be moving in this direction already.
It could be interesting to have an open source modeling platform at some point. Simple devices like the Behringer FCB1010 have had their capabilities enhanced by swapping out EPROMs/firmware. Phones, tablets, and video streaming devices have been rooted; the same with operating systems on other devices. I suppose it could be done. That or just develop a modeler with open source from jump.
The usual open source challenges would still exist. Security, support, code quality or lack there of, "curated" programming to maintain feature quality, etc.. Not to speak of the level of expertise both technical and musical required to pull this off and the willingness to give it away. Still, I suppose it could happen. No saying how satisfactory the results would be and separating the wheat from the chaff would be a monumental task. I personally am offering for a minimal fee a firmware chip mod that will convert your Helix from an impressive and capable modeler into nothing but an A/B switcher. Ah, simplicity. So far no takers.
-
2 hours ago, silverhead said:
I think it might be helpful to some if I provide my understanding of some details about what actually does and does not happen currently during a Helix firmware update, and some associated routine practices that one might want to establish. This post may hold nothing new or interesting for experienced users. Apologies in advance if I’m wasting your time. It’s intended for less experienced users who I hope will find it informative and helpful. It’s also lengthy and detailed so grab a coffee......
As of HX Edit version v3.01, available now, the Helix firmware update process has been significantly improved and further automated. This has not yet been evident, but we are promised that firmware v3.10 is coming soon. If you haven’t yet updated to HX Edit v3.01 you should do so now because it will make the pending firmware update simpler for you. If you’ve been frustrated by the update process in the past you might want to bookmark this post in anticipation of the new firmware.
NOTES:
A) The fact that I am posting this now does not mean that the firmware release is any more or less imminent than we already know it is, from Digital Igloo’s posts on The Gear Page. I don’t know exactly when it will be released any more than you do. But soon? Yes. That’s why I’m posting this now, so perhaps you can be better informed and prepared for a smooth update when the release happens.
B) This information is not from Line 6. As always it represents my own thoughts. This post does not provide firmware update procedures. The firmware update procedures published by Line 6 are sufficient and should be followed exactly as described. I believe nothing in this post is inconsistent with that. Rather, this post provides additional background for interested readers.
The HX Edit program now detects that a firmware and/or software update is available, prompts you to proceed with installation, and manages the process with a further series of prompts and actions. After the update process successfully completes your Helix environment is as follows:
- Your HX Edit program and your Helix firmware are both updated if required and are known to be in a mutually compatible state. This, imho, is the main improvement to the automated process - there should be no more problems due to incompatible versions of the firmware and the editor. This in itself should entice you to update to HX Edit v3.01 immediately.
- You have a system backup file created as a mandatory part of the automated update process.
- After the update you may notice a difference in the operations of your Helix device because the update process restored the Global Settings to their default values, which may be different from your pre-update setup. Details on how to handle this follow.
- Other than the Global Settings, nothing else on your Helix device has been noticeably changed. All setlists, presets, IRs, and Favourites remain in place as they were.
- All presets have been rebuilt to ensure that their structure conforms to any new features introduced in the new firmware.
Following the update you can proceed to use your Helix as you have previously. However, there are some habits that I have developed to take full advantage of the update and to minimize the potential for future issues. I do these things immediately after the firmware update as part of my routine practices. All of these are optional but I offer them for your consideration.
1. Perform a factory reset (restore) on your device. This is recommended by Line 6 although it is not automatically done as part of the update. This wipes out all custom data on your device including non-factory setlists, IRs, and Favourites (not a problem since you have the backup file) and installs the firmware specific factory setlists associated with the new firmware - Factory 1, Factory 2, and Templates. These were not automatically installed as part of the update process (some would say this is a benefit!) and nor are they installed by fully restoring your backup file. Unless you do this manually you don’t have any new or modified presets in these factory setlists. For details on how to perform a factory reset on your specific Helix device see:
Helix/Rack/LT/FX/Stomp Reset Procedures and Troubleshooting Tricks
2. Run HX Edit to restore your system backup. Choose to restore everything except the Factory 1, Factory 2, and Templates setlists. This restores your pre-update Global Settings as well as all your custom setlists, IRs, and Favourites. It retains the new factory setlists installed in the previous step.
3. Turn you Helix device off and then on again. This forces all presets to be rebuilt. Do this before you begin playing or editing.
Your Helix device is now loaded with all your previous settings and data, any new factory setlist updates, and with all presets rebuilt. You are ready to go with the new firmware.
If you had any customized presets in setlists #1, #2, or #8 prior to the update these were replaced in Step 1 above. You still have copies of them in your system backup file and you can recover these if you wish. I suggest you export a copy of the firmware specific factory presets prior to repeating Step 2 above to install only setlists #1, #2, and/or #8.
A final note about rebuilding presets: every time your Helix is powered on it looks for presets that need rebuilding and does so before it hands operations over to the user. It’s the final step of the firmware update procedure but only because Line 6 forces a system restart at that point. Why does Line 6 do this? I assume there are good technical reasons and that rebuilding presets is important. I neither know nor care why it’s deemed to be so important (presumably the rebuild makes any necessary changes to preset file structures) but, to me at least, the very fact that it’s a mandatory part of the startup process means it’s important!
This means that every time you import a setlist/preset that was last saved using previous firmware you know that - for perhaps mysterious reasons- the presets need to be rebuilt and that this is going to be done on the next startup. Why wait? As part of my routine operations I like to force this rebuilding to be done immediately. In other words, as my normal workflow involves routinely importing setlists and presets, I don’t begin editing any of them before I cycle the power on my Helix. This forces any required preset rebuilding to happen immediately, minimizing the likelihood of potential problems - however rare and mysterious they may be.
I hope this helps some folks when Helix firmware v 3.10 is released. Comments, corrections, and further suggestions are welcome.
Excellent advice and a great primer on how to safely and thoroughly execute an update! Now let's hope Line6 continues to perfect the process so most or all of these caveats and additional actions become unnecessary.
-
1
-
If I hack my Helix, write my own update, and turn it into a $1500 brick does that void the warranty?
-
4 hours ago, brue58ski said:
If I set the Helix so one of the row of preset buttons is presets and the other row is anything else; snap, stomp, etc. When I do this and bank down from the second bank (2A-2D) the bank it goes down to is the last bank (32A-32D) skipping the first bank (1A-1D). It doesn't skip any other banks otherwise. When I bank up from the last bank (32A-32D) It does go to the first bank (1A-1D). It doesn't skip anything when all of the buttons are presets. Before I put this in the bug reports, has anyone else experiences this?
This is a well established bug from the last update. I have to believe it will be addressed in the 3.1.0 firmware release. Actually shocked they didn't roll out a quickfix for it earlier. One of the benefits I am hoping the new more streamlined firmware/HX Edit update process yields is the ability to release those kinds of fixes rapidly without subsequent pushback from users who then have upgrade problems.
Update: Looks like Silverhead hit the buzzer first.
-
The release of the new firmware 3.1.0(notice NOT 3.01.0) appears to be imminent(rumor has it being released as soon as March 17th, please don't hold Line6 or me to that) and along with it I assume probably a new version of HX Edit to accompany it. This would be the time to upgrade to version 3.01.0 of HX Edit if you have not already so you can witness for yourself the modern marvel of HX Edit forcing an update of itself before updating the firmware. That should prevent a whole lot of newer users from ending up with their version of HX Edit and firmware being out of sync. Yahoo!
For anyone who missed it, this was in the release notes for the 3.01.0 version of HX Edit.
"HX Edit 3.01
HX Edit 3.01 includes bug fixes and an improved firmware updating procedure, and is strongly recommended for all Helix and HX owners. Doesn't matter what version of HX Edit you're currently running; you can go straight to 3.01.New Features- AFTER installing HX Edit 3.01, updating firmware for Helix and HX products is now more consistent and seamless. For example, the update process now forces you to update HX Edit before your Helix/HX hardware. (Imagine that.) Even if the bugs below don’t apply to you, we strongly recommend updating HX Edit to 3.01 so you’ll be ready to go for our next release."
-
1
-
1 hour ago, matsonf said:
Anytime I use Poly Capo, I'm hearing dissonance in the tone, where the original pitch in addition to the Poly Capo pitch comes through, e.g., +1 (to raise pitch by a half step). Secondly, and possibly related, the tone gets more corrupt sounding the farther from 0, whether plus or minus. Is anyone else experiencing this? Version 3.01 was to fix potential audio corruption, but maybe those were different issues.
Just wanted to mention that often with pitch shifting or harmony blocks people hear the actual sound coming off of their guitar strings in addition to the generated sound from their device output. This can lead to you hearing out of pitch sounds that your audience or recording won't. Other than that, next stop, "poly auto-tune" block being added to correct Poly Capo pitch drift(just kidding) :-)
-
21 hours ago, Rudie-k said:
I was cleaning up some files (Old setlists - bundles - presets) and I came across a file extension I didn't recognize.
I know that -
Presets = .hlx
Set Lists = .hls
Bundles = .hlb
the one in question is ".hxb"
is this a Backup file for when we updated Firmware ???
Yes. .hxb are the backup files created by the "Create Backup" command from HX Edit's 'File' menu or as you mention when you do a firmware update.
-
6 hours ago, CraigGT said:
Oh I just had a thought,
if you're using Send/ Return blocks is Dry Thru set to -120dB or if FX Loop is Mix set to 100%?
A friend fell foul of this at the weekend with phasing issues on a loop pedal.
^^^^This if you haven't checked it yet! Should have been the first thing mentioned. Many a user has run into this issue when using the FX loop.
-
11 hours ago, loydall said:
I found an old thread on this describing my experience but thought I'd resurrect the subject to see if there are any new approaches on this one.
I run my HX Stomp into the front of my valve amp. It sounds great. I also run my (real) overdrives into the HX Stomp. This also sounds fantastic. However - if I create an fx loop in my hx stomp and place my real overdrives in that, they sound awful. Unusable. I want to be able to do this so I can run some hx stomp effects before and after my real drives.
I assume that using an FX loop means the signal is converted to digital, passed through my drives and then again, that signal converted to digital. The difference is massive, not just a slight difference but the difference between clear, articulate, responsive overdrives and mush.
Is there anything I can do to improve the quality of using overdrives in the loop of the HX Stomp?
Cheers.
Yep, as schmalle responded levels would be one of the first issues I would look to. Not sure the extra D/A conversion when routing through the Stomp's FX loop could be responsible for the level of signal degradation you are describing. You still have D/A conversion even when you plug your stomp pedals directly into the stomp. I wonder if this could be at least partially impacted by impedance issues as zappazapper alluded to. Have you tried changing the order of which of your external stomps gets plugged in first in your FX loop? Maybe the first pedal you have connected to the HX Stomp's send doesn't like the input level it is receiving. Might not be your ideal pedal sequence but is is one more thing you can test.
I suspect it is more likely a settings or impedance issue but another thing to check is if you are using different cables to plug in via the loop rather than directly, I would try some others. Never hurts to start testing by swapping out some hardware. Might try swapping out the stomp pedals also. Are you getting the same excessive sound degradation no matter which stomps you try in the FX loop?
Another thing to pay attention to in your testing is what sequence you have the pedals in when using the HX Stomp's loop versus plugging them in directly. Is everything still in the same order in your signal chain when plugged in via the HX Stomp's loop? If not you might just prefer the pedal order when run in directly.
-
On 12/5/2019 at 8:15 PM, amsdenj said:
I wouldn't recommend it. The speaker models in Powercab are designed to work with the stock speaker. Using a different speaker might not necessarily sound bad, but it probably wouldn't sound like the speakers that were modeled.
Great point and doubtless true but I would still be curious to hear it. You could lose some modeling accuracy/authenticity but as you point out the result might still be worth it. It would be interesting if Line6 released a PowerCab down the line that had the F12-X200 speaker stock. Not that I want to see the one I already own devalued ;-)
Setlist corrupted ?
in Helix
Posted
Quite kind of CraigGT. Was hoping someone would do that for the OP, I don't have a Stomp. If the OP can't get things straightened out with global reset or a firmware refresh maybe someone else with a stomp could upload him back a working exported version that might be more stable than the OP's; or if feeling particularly charitable with their time, a zipped export of the presets. My guess is that if the underlying issues are addressed though it won't be necessary.
To the OP, I definitely think it is time to look into doing a global reset and potentially refreshing the firmware update. As others here have indicated make sure you upgrade to the latest 3.0.1 version of HX Edit. If you are able to export a healthy version of your setlist that is working on someone else's Stomp there is a good chance it is a global settings, global reset, or firmware issue on your end.