HonestOpinion

Using an acoustic IR as others have mentioned is actually what is recommended in Line6's release notes for the "acoustic sim" block. Also echo the sentiments that adding a bit of compression, delay, chorus, and/or reverb, can help the sound along. I personally have found it difficult to get a natural sound with all manufacturers' acoustic modeling efforts designed to be used with an electric guitar. They can absolutely get you through a show without an acoustic, especially in a crowded mix, and if dialed in well can actually sound fairly convincing when used with fingerpicked passages. But... it is almost always on playing chords where they fall down on the job. There must be some very complex harmonics going on when an acoustic guitar is used for playing chords that just doesn't seem to have been modeled that well yet by anyone. At least not in a way that the average user can quickly(or even slowly) dial up. With that said I have heard some wizards manage to eke out some good chord strumming with an electric through acoustic modeling but I have found their results to be almost impossible to replicate and most still fall short to my ears. I think that Jason Sadites video datacommando posted is a great place to jump off. He does a fine job there. Maybe I just need to spend more time working with this; every time I try I find myself happier returning to just packing an acoustic guitar along with my electric(s). Hats off to those who are able to pull it off and thanks to Line6 for adding this block. It is a great addition. I know it will come in handy one way or another.

Thanks for posting this. What an interesting speaker. I was not aware of this Celestion's existence. I wonder if anyone will try retrofitting a PowerCab with one of these? Hard to get specific information on the stock "custom designed" speaker in the PowerCab. IIRC the initial literature on the PowerCab gave me the impression was that it might be an Eminence speaker with a Celestion HF driver. Strange when I poke around the web now though I see no mention of the Celestion driver or really much information at all on the speaker that comes stock with the PC. I wonder how the PowerCab's speaker would compare with the Celestion F12-X200. Or (looks to the side with a conspiratorial glance) are they one and the same? https://celestion.com/product/f12-x200/ I watched a couple of videos on that HoTone Loudster Portable Power Amp and at least in Europe it is very inexpensive. Looks like it is really basic, essentially no preamp controls just a power amp, so tone-shaping will primarily be coming from the Stomp or the rest of the pedalboard. There are so many nano, micro, mini, and "(power)amp in a pedal" choices out there now that your options are limitless if you want a small form factor amp to pair with your cab. If you have one of these already I would give it a go. Personally I think its possible you might be able to get a great sound with the F12-X200 in the right cabinet. I would expect to see some new FRFRs coming out with this speaker soon if they are not already. Strictly an uniformed opinion though as I have not heard one. Please post your results back if you end up getting one. Update: Looking around for information on the speaker in the PowerCab(I own a PC+ but have no intention of taking the back off) I saw someone else has started a topic with the same question I started with here:

There is a 'Save As' option under the 'File' tab on the top menu of HX Edit or you can hit the save icon at the top of the screen. When the dialog box appears with the list of presets simply highlight the preset location you want and hit 'OK'. You can even save to a slot in a different Setlist using this method by using the pulldown of Setlists at the top of the dialog box. You can also use the keyboard shortcut "Ctrl+Shift+S" to bring up the 'Save As' dialog box. Note: This is how it works in HX Edit for the Helix.

Resurrected an old thread here. Ah well, reduce, reuse, recycle. I can't necessarily tell you how to get a Bigsby whammy sound specifically but as far as getting you into the ballpark select either the 'Pitch Wham' or the new 'Poly Wham' block from the Pitch/Synth effects category and set to taste. The 'Toe Shift' and/or 'Heel Shift' is most likely the settings you will put the most focus on. The expression pedal assignment, at least on the Helix Floor will default to EXP 1 but you can change that assignment to whichever input you have your expression pedal on. Regarding setting it to global as the OP's topic title requests, set Global Settings --> 'EXP Pedals' --> 'EXP * Pedal Position' = "Global" on whichever EXP input your expression pedal is connected to. Btw, if you don't have a toe switch available to engage your expression pedal see the video below for how to auto-engage an expression pedal on the Helix. The video is for a Wah block but the same principles apply. The key to this is going to the 'Bypass Assign' screen and setting the 'Switch' parameter to the input for your expression pedal, e.g. 'EXP Pedal 1' rather than the toe switch. This will provide you with the additional fields necessary to set up the auto-engage. Line 6 Helix Wah settings TIPS and TRICKS. - YouTube

And yet a fair number of people remain convinced that some arcane change in the new firmware is responsible for their, for example, stomps not showing up in the bottom row any more or their output levels changing, rather than a change to a global setting. IMHO even if it is due to a user's lack of thoroughness any improvement to the update process that does not detract substantially from other more interesting developments is not a bad idea.

LOL, if people only read the instructions. And yup, it often comes back to resource allocation. Gotta get that new Helix Wireless out to market ;-)

As DunedinDragon indicated most updates on existing models will be to DSP efficiency. That or bug fixing. The problem with "improving" existing models is that you can change the sound of the block so profoundly that presets made with it prior to the change can suffer dramatically. As they improve their ability to model as the product matures, and they have said as much on TGP, they have more of a tendency to add new models rather than upgrade old ones as not to impact presets made with them. I would imagine their threshold for applying modeling advances to older blocks is to some extent how extensive a change in their sound the improvement might have. I would not be surprised if there have been some subtle enhancements to some preexisting models along the way that went totally unnoticed. Who knows though, maybe at some point they will more radically update some of the older amp models, more likely as an additionally available "version 2" amp or effect for those who want to take advantage of the latest and greatest.

The update can be an overarching process that first downloads the new firmware, does a backup(as it currently does), hands control over to the Helix for the duration of the device's firmware update, and then takes it back at the end to reconcile and restore the global settings. The fact that the firmware process currently prompts the user to do a backup indicates some knowledge of or ability to use the file system. Another approach would be to use the computer's RAM but if the update failed midstream that could mean losing the prior firmware's update settings stored only in volatile memory. Another potential complication is that until HX Edit updates its own version along with the firmware there will remain a certain number of users who have their firmware and HX Edit versions out of synch when they execute the update. Just batting this around as we are now though you can see it might not have been quite as straightforward a process to retain these settings as it might appear and hence their decision, for better or worse, not to. One note, the fact that you can currently manually restore your global settings from a previous backup points to some kind of reconciliation process already in place for prior --> new global settings. Maybe they don't anticipate this always being the case but if it were perhaps it could be as simple as triggering this manual restore process automatically at the end of the update.

I agree trying to make this happen could introduce some challenges depending on how a previous global setting was modified in a new firmware version. I think the lack of "scratch space" on the device could be gotten around as the update process could store your prior firmware's global settings in a temp/backup file on your hard drive and then restore them automatically as part of the update process after setting the global settings to the new firmware's defaults(stable state). Any global setting that was significantly changed in the new firmware might require some kind of message or firmware note(which half the users wouldn't read) though to the user informing them that they would have to set it manually in the new firmware. Again, maybe more trouble than Line6 thought it was worth to reconcile the old settings to the new, and programming hours better spent elsewhere. Still, many software companies face this issue with updates and err on the side of preserving as many global settings as possible between updates. Line6 may have good reason why they don't currently do this as I am sure they are aware it causes some churn after a certain percentage of users can't figure out why their device is functioning differently after an update .

Good question. I have always assumed that returning the global settings to their "defaults" was to make sure that global settings are updated to a stable state in the event that there were modifications to the global settings in the new firmware version. Returning them to a stable state after a firmware update could probably be done while retaining at least the majority of the user's previous firmware version's global settings but maybe Line6 deemed it not worth the programming effort or low priority.

Assuming you already tried different combinations of the values on the 'Select' parameter on the Ext Amp settings in Command Center. Maybe rewiring the TRS cable might do the trick. Believe I have seen some solutions posted along those lines before on the forum. Also, doubt if this will be of any help to you but found the note below on Helixhelp.com. The only way I can see this as being helpful is if it makes a difference whether you save the preset with the footswitch with the LED ring either on or off. NOTE When an Ext Amp command is assigned to Instant 1-6, the connection determined by Knob 2 (Select) is made when the preset is loaded. When an Ext Amp command is assigned to a footswitch, the footswitch's current state (dim or lit) determines whether or not the External Amp connection is made when the preset is loaded; when dim, no connection is made; when lit, the connection determined by Knob 2 (Select) is made. Subsequent presses of the footswitch toggle the connection on (LED lit) and off (LED dark).

I assume you are overwriting the existing block in the snapshot you are copying to rather than adding a new one. Is that correct? Unless there is a bug on certain amp models, possible but unlikely, my first guess would be that you are occasionally failing to save the preset before switching back to another snapshot. When I copy/paste a block between snapshots, as you said you do in your post, I can consistently recreate the loss of the newly copied block's parameter settings as you describe; but only if I fail to save before switching to another snapshot. As long as I save the preset first before switching, the parameter values from the block I cut/pasted get saved as well. Kind of interesting. The global Recall/Discard settings seem to work as described in the manual and the paragraph below when modifying parameters on a block between switching snapshots, but not when copying and overwriting an entire identical existing block along with its parameters to a different snapshot. Important to know if you construct your snapshots by cutting and pasting blocks within a single preset as the OP does. Although the setting described below does not seem to affect the behavior of the parameter value saving when copying and pasting blocks between snapshots(you still need to save before switching snapshots) it does impact preset editing in general. Copied over from my recent post on a different snapshot issue: "The Global Settings --> 'Preferences' --> 'Snapshot Edits' not only impacts how the snapshots behave while performing but also while editing a preset. If you have it set to "Discard" it is not a bad idea to save each snapshot before moving on to design the next one. Otherwise it is pretty easy to inadvertently lose the snapshots settings when you start switching around to edit other snapshots. With it is set to "Recall" you can save just once when you have completed editing the entire preset." Btw, you need to download and install HX Edit 3.0.1. I notice you are running the 3.0.1 firmware but HX Edit 3.0. You need to sync the versions up.

Just released, Helix Wireless ;-)

Pod Go Wireless available for preorder https://www.sweetwater.com/store/detail/PODGoWL--line-6-pod-go-wireless-guitar-multi-effects-floor-processor https://www.guitarcenter.com/Line-6/POD-Go-Wireless-Guitar-Multi-Effects-Processor.gc

Looks like there is a suggestion on Ideascale for this already. Voted!

You still have to manually download the new 3.0.1 version of HX Edit and install it. Updating the firmware does not do it automatically(yet). Hopefully having gotten your firmware and HX Edit back in synch will resolve this issue permanently.

Wow bummer! Was not aware this was not available on the Stomp as I don't own one. Would have expected to at least see it in HX Edit. It is there for the Helix. Hopefully it will get added for the HX Stomp in a future update. Thanks for the courteous responses. Sorry I couldn't be of more assistance.

The Airstep looks like a nice MIDI controller with a lot of capability. Another option at about the same price point. The switches look kind of close together and there is one less of them . Does not have Bluetooth and perhaps some other features the Airstep has either. It does have a feature I prefer like a screen(which it has) or better yet, scribble strips(which it doesn't) where you can use custom names(at least according to the Sweetwater video). https://www.sweetwater.com/store/detail/Soleman--source-audio-soleman-midi-controller-pedal

Ideas submitted to IdeaScale is the method by which an idea for a mod or feature has the best chance of getting implemented. You just have to create an IdeaScale ID and submit an idea. Don't be shocked if an idea such as this which is a little specialized or esoteric doesn't garner as many votes as you might expect. It is still worth getting it into the conversation over at Line6 though. Some ideas pop up in the firmware in fairly short order after being submitted and some take years to never. You never know. https://line6.ideascale.com/

Going to play around with it some more but I have to admit that short of perhaps some complicated MIDI solution to this I don't currently see a way to get the preset to behave the way you want. Maybe someone else has a solution? I think unfortunately that phil_m's answer waaaaay up at the top of this topic cuts to the core of it. As he initially stated, at least right now, the parameters for a block cannot be "fixed" across snapshots in the same fashion that the bypass state can. He clearly had a better grasp right from jump of what the OP and you were trying to do. To summarize it would seem to me that footswitch(not snapshot) assignments for parameters could essentially have an option to have the same "fixed" or isolated behavior available that can currently be established(via the Action switch), only for bypass state. I believe this change would address what you and the OP are attempting to accomplish. I suppose this could be implemented by perhaps adding the same sort of 'Snapshot Bypass'="Off" option for a block's parameters(again, currently only available for the block's bypass state). Seems like a prime candidate for an IdeaScale suggestion. I would vote it up.

Ok, great explanation, I think I understand you now. Apologize if I was slow on that. If you turn on FS2 or FS3 in for example Snapshot1, you want the parameters as well as the bypass state to be/stay as you set them in all the other snapshots as well; not just the snapshot you activated it in. Let me see if there is any way to get it functioning that way. Regarding using the "Customize" function for renaming. In the case of FS2 which has two blocks assigned to it, you will need to select the correct block to be able to see the "Customize" field under the “Bypass/Controller Assign”. HX Edit does NOT display the customize field for every block in a multiple assignment, only one. I believe HX devices default to displaying that field only for the first block you assigned to that footswitch when you initially set up the preset; even though the rename obviously involves the other blocks as well. So if you have multiple blocks simply roll through the blocks for that FS one by one until you find the block with the 'Customize' field. In the case of FS2 in your preset that would mean selecting the "Ping Pong" delay block in HX Edit, selecting the “Bypass/Controller Assign” tab, and then clicking on the "Multiple(*)" name in the 'Customize' field and changing it. This same behavior of only showing the 'Customize' field on one of the blocks in a multiple block assignment is also reflected when you customize the name on the device directly. That means that again, in the example of FS2, you will need to highlight the 'Ping Pong' delay block first, then bring up the 'Bypass Assign' options(on the device) menu. You should now see the 'Customize' option, at least on the Helix. Don't know if you have to maybe page over to see it on the Stomp. If you decide to modify the name in 'Command Center' instead, select the FS you are renaming and select 'Customize'. Probably easier to use Command Center when multiple blocks are assigned to a footswitch as you only need to know which footswitch you are renaming.

Nice catch and I suppose anyone who alters the tuning on their 'D' string should be aware of this until it gets included in the global settings backup. I am familiar with "True Temperament", have been wanting to get a guitar with TT frets for years, but thanks for acquainting me with the "TT Thidell Formula 1". "Bugs" is not really the right topic for me to ask this, wish they still had the direct messaging on the forum, but I am curious. If this blows up into a discussion maybe we can pull it out into a topic of its own. Do you use this tuning for a true temperament fretted guitar or on your standard fretted guitars? If you use it on standard guitars how do you find it in comparison to standard tuning? Is it worth the change?

Great troubleshooting steps already posted. I would get that factory reset codamedia recommend taken care of first as well as his other suggestions. Be prepared to rerun the firmware update as well. Make a backup before proceeding. Easy to do. https://helixhelp.com/manuals/universal/reset-options This could also be a corrupt preset(s) such that it is only happening when you shut the Helix down after having selected that preset. Have you noticed this happening on a specific preset(s)? If none of that works open a ticket as previously suggested.

Great video! I'm sure another one on setting up the FCB1010 expression pedals would be equally welcome. Btw, you may already be aware of it and just wanted to demonstrate how to do this with no additional software/hardware required but included are some additional FCB1010 resources below that can greatly streamline and simplify the programming process. Haven't used the FCB1010 with the HX Stomp but I will mention my one caveat. Using the FCB1010 with other devices can allow you to get switching working reliably but it can be tricky to have the FCB1010's pedal LEDs properly reflect the state(e.g. is a block on or off) of the connected device. Particularly for more complex switching operations. This freeware FCB1010 Editor makes programming the FCB1010 much easier and requires a lot fewer programming pedal presses. http://www.mtnsys.com/?path=faq-fcb/PCEditor.htm%3f There is also the UNO2 EPROM upgrade chip(very simple to swap in, no soldering required) for users who want even more control over the FCB1010. They offer an editor as well although it is not free. You do get a free editor if you purchase the EPROM. https://www.fcb1010.eu/ There is also the "Tiny Box" if you want to have even more advanced control over the FCB1010. https://shop.tinybox.rocks/ Update: See rd2rk's post below as that version of the EPROM is cheaper and may be all that many people need. I should have mentioned that one as well.

Preaching to the choir but this issue with HX Edit crapping out because of the presence of an SD card should get fixed already. Hopefully it will be in the next release. It appears they are working on improving the update process and hopefully this bug will be included in that overhaul. I cannot think of a good reason why HX Edit should be doing such a low level call to the operating system and hardware for something like drive numbering or disk type. At least not when it causes the app to crash.