HonestOpinion

You can't have spillover ("tails") between presets but you can have them when using snapshots.

Ah, on further examination I see what you are getting at. That in effect, using half the DSP for gapless preset switching and spillover is pretty much the same as using two separate paths and just switching between the two paths, due to the fact that the Helix uses one DSP chip for each path. I guess once again we are back at waiting until the hardware is so fast and powerful that you can't wring any more discernible sound quality out of it, you can use more blocks than you would ever hope to need, and you have enough processing power left over to also get gapless switches and spillover between presets. Until that happens Helix chose the right approach.

Agree and that was kind of my point. Optimizations may reduce the gap a bit along the way. Overall given the compromises required I prefer the Helix approach of max flexibility and sound quality with snapshots providing a great if not always optimal option for gapless switching.

How do you get gapless preset switching with the Helix? Snapshots is the only way I know and that is not necessarily substantively the same as a preset switch. The Headrush claims to have gapless preset switching with spillover but that feature came at the cost of a much simpler signal path that allows fewer blocks and amp, effect, IR options (and perhaps inferior sound quality?) so that they could dedicate half of the DSP to seamless switching and spillover between presets. For now manufacturers seems to be taking either the Digitech RP-1 or Headrush approach - sacrifice flexibility for gapless preset switching, or the Helix or Axe approach of max processing power for flexibility and superior sound at the expense of gapless preset switching. I still prefer the Helix's approach but a hybrid architecture that allowed either approach seems like it would be a great thing.

It used to be that in order to make guitars on a medium to large scale you required a dedicated staff of luthiers and a lot of elbow grease. Then along came computer and robotic aided production, laser etching, near flawless reverse engineering, and the rest of it, and the barriers of entry that formerly included extensive knowledge of guitar-making required to be a major quality guitar maker reduced dramatically. Guitars can now be made quickly en masse in factories by people who would have little chance of constructing a quality guitar by themselves but can run a machine on a production line This has probably flooded the market to some extent. Guitars have been morphing slowly to try and keep up with the evolving technology and shifting styles of pop music. We've got synth guitars, Variax, and lately we have seen several options for guitar add-ons that provide MIDI triggering pads and other innovations that broaden a guitar's potential role, and notably, require it to be played in entirely new ways. Maybe the next Edward Van Halen doing with this technology what Eddie did for tapping will help popularize these new technologies added to the guitar. I expect at some point some of these add-ons will be offered stock as built-in options. There are software alternatives that are also adding new capabilities to the guitar. I think there will always be room for the classic basic electric/acoustic guitar designs as well, even if demand decreases. It has been a long time since Beethoven and people still play the cello. Some interesting devices/software to add on to a guitar: http://www.musiciansfriend.com/amplifiers-effects/source-audio-hot-hand-3-universal-wireless-effects-controller?cntry=us&source=3WWRWXGP&gclid=CL29mKW55tQCFcmPswodJAEGDQ&kwid=productads-adid^156717928496-device^c-plaid^143209124442-sku^J01119000000000@ADL4MF-adType^PLA https://www.sweetwater.com/store/detail/GuitarWing?product_id=GuitarWing&campaigntype=shopping&campaign=aaShopping%2520-%2520Core&adgroup=Guitars%2520-%2520Electric%2520-%2520Other&keyword=%5B315663918608%3A*%2520%2F%2520custom%2520label%25202%2520%3D%2520%22in%2520stock%22%2520%2F%2520product%2520type%2520%3D%2520%22guitars%22%2520%2F%2520product%2520type%2520%3D%2520%22electric%2520&placement=google&adpos=1o1&creative=55280653081&device=c&matchtype=&network=g&gclid=CMqfmsq15tQCFctLDQodz8sJDA https://www.acpad.com/ https://www.jamorigin.com/

This is an intriguing and ingenious idea although I suspect Silverhead is correct about the lack of ROI for what would probably be an enormously intensive piece of development. I would love to see one of the modeling companies do this in the future. This would provide spectacular flexibility for the user allowing them a choice between more complex and DSP intensive patches with snapshots and spillover, or the alternative to use simpler less DSP intensive patches with seamless preset switching and spillover. You should write this idea up in IdeaScale! I agree with most of this comment and I would characterize snapshots as a great option to, but not a replacement for, seamless preset switching until (if ever) the hardware gets fast and cheap enough to provide both sufficient flexibility and sound quality in a preset and also allow seamless preset switching and spillover. I don't believe snapshots "meet almost all needs for lag-free switching" although I vastly prefer snapshots for fast switching and spillover to the current alternative. An alternative which, as others have pointed out including Line6 staff, hamstrings a device and forces much simpler presets with less DSP available for everything including amps, effects, cabs, and IRs. You can see the impact of this decision with the new Headrush device. This is why I think katerlouis's has a fantastic idea which would allow the user to pick the solution preferred for a given song, complex snapshots or simpler presets that dedicate half the DSP to lagless preset switching and spillover. Sounds like it would require a hella job of coding though.

I agree with everyone's signal chain suggestions. It might be worth setting up a couple of other Fender amp options in addition to the cab options twystedriffs suggested. Maybe even a Hiwatt or other clean amp alternative. The Fender Twin model may not be what he ends up preferring.

Returning the unit is an option but I believe the OP indicated it was working when he bought it and only started displaying the boot error message after he tried to upgrade. So it may not have started out as a brick which bodes well. If you got it "Open Box" at a good price it might be well worth contacting Line6 support to walk you through the firmware update process before returning it.

There is a newer firmware version, 2.21 and it is recommended to upgrade to it although you certainly don't have to. Upgrades always come with some level of risk and I assume your Ebay Helix is not warrantied. You will want to backup a bundle, individual setlists, and mass exporting (highlight all presets and hit "Export") your individual presets is not a bad idea either. You will want to do the backups with the 2.20 version of the Editor. This is the Editor version that matches your current firmware. This means you have to do the following: Download and install the 2.20 version (your current firmware version) of the "Helix" app. This will install the 2.20 version of the Editor, Updater, and Driver. Do NOT upgrade your firmware yet. Make sure you have the 2.20 version of the Editor installed by checking the Help --> 'About Helix' tab in the Editor. Now backup your bundle, setlists, and presets(recommended) as well as your IRs. Take a snapshot of your IR placement if you don't have them numbered. Take note of your global settings. Now download and install the 2.21 version (the latest firmware version) of the "Helix" app. This will install the 2.21 version of the Editor, Updater, and Driver. Start the Updater and follow the firmware release notes carefully to upgrade to the 2.21 version of the firmware. Do the recommended global reset process for your version of the Helix (Floor, Rack). This will overwrite the Factory and Template setlists with the latest from Line6 and wipe out your User Setlists and IRs as well as your global settings. Restore your User setlists. Restore your IRs to the same locations they were in before your upgrade. Don't restore a bundle unless you want to overwrite the latest Factory presets with your old ones. Reset your global settings. Restart your Helix at least once after your global reset. This will execute a rebuild on all the lists/presets you restored from your backups. Finally check to make sure you have the 2.21 version of the Editor installed (Help --> 'About Helix') and do another set of backups with your new 2.21 version. Don't overwrite your old ones as you may want them around in case you run into issues with the new firmware.

I think you could pull off your electric path with "clean, crunchy, and metal" using snapshots depending on what blocks you want to use in addition and how many amps/IRs. Take a look at this template. It essentially gives you access to up to 100% of the processing for both DSP chips and up to 24 blocks for your electric guitar but you will want to leave a bit of resources for your acoustic path which, for most users, requires way less DSP. This template was designed for people who wanted to actually switch guitars from an acoustic to electric within the same preset but it could probably be adapted by changing or removing one of the inputs if you are trying to get the electric and acoustic sounds from one guitar. There is always the Variax which could pull this off easily. http://line6.com/customtone/tone/1460280/

Ultimately I would leave it up to Line6 to refine the implementation but your proposal seems really well thought out and most importantly captures the major functions that would have to be translated to the switches.

Just make sure you have at least 2 blocks on a path and drag one of the blocks down. This will automatically create a second path. You can do this for a total of four paths.

I sympathize with your trials and tribulations. Line6 is working on a better update process but it is not here yet. Try this after you have downloaded and installed the latest version of the "Helix" app (Editor, Updater, Driver). Try the various restart options (as you have been) giving them ample time to complete. After each attempt try plugging in the USB cable, firing up the Updater, and if your computer can see the Helix after you have restarted, try updating the firmware again. Good luck, it may take more restart attempts but there is still a good chance you can get this updated with persistence. Otherwise call L6 support, they can be most helpful.

I appreciate your analysis and maybe you make some good points for a Line6 stockholder but not so much for a Helix owner. In general I don't see any percentage in encouraging manufacturers to double my price when other solutions are available. Additionally, the increased price could hamstring the product's initial sales. Quite simply, I don't run or own the Line6 company, I purchase their products and you are suggesting they double the price I would have to pay for Native, a proposed price they have already posted for Helix owners. That would be bad PR and make a lot of prospective customers quite unhappy. The reduced price for Helix owners is a perk for those who have invested in the Helix and an added incentive to purchase not only Native but also to purchase a Helix. The $100 price represents a low barrier of entry and makes it likely that there will be many early adopters of Native which helps to ensure its success and longevity. At $200 to buy Native for a Helix owner there may be dramatically fewer sales, I would assume they tried to factor in number of sales versus price when they determined the price to set. Additionally remember that the $100 means they have just sold a $1500 Helix. Of course, nothing is written in stone and prices can change. There are other strategies for stopping software theft that don't involve doubling the price of Native for many of its potential customers. I assume they have already thought about the pricing and will leave it up to them to come up with a solution that protects their intellectual property and product without doubling the price for Helix owners. Are you going to ask them for extra homework next? Spikey, 'fess up, did you sell your Helix? Just kiddin'. ;)

This happens for some folks during the update and the overwhelming majority of the time people can get the unit to update properly after trying the global reset options and finding the right USB port on the right computer. If I remember correctly the message you are getting usually does not indicate the Helix has bricked. Other folks have seen this and recovered although often it requires a different computer or USB port and multiple global reset restarts. The various reset options can be found here: https://helixhelp.com/reset-options/ . Safe boot mode option is a good one to try. Hang in there and you will probably be able to right the ship yourself, if not L6 tech support should be able to help. Some things to check: Make sure you are trying the reboot options without the USB cable plugged in. I noticed you said you downloaded the "driver and firmware" off the site. If you have not already make sure you download the version of the "Helix" app that corresponds to the firmware version you are upgrading to. The "Helix" app will include the Editor, Updater, and Driver when installed.

I know you are joking. Terrible idea!!!!! :(

If you have not used the system for prepending each IR name with a number that dunnedindragon mentions, you can bring the Editor up and capture a snapshot of your IR list and save it. Not a Helix "snapshot" but the one you get when you hit PrtScn (print screen) on your computer's keyboard.

Your cabling for the 4CM connections may not be correct. I can't tell from your path above what exactly is plugged into what. The connections you used are more easily understood when described in pairs and it should be clear which side of the pairs is the Helix and which is the amp. Nothing should be plugged into your amp's "Power Amp Out" other than the amp's speaker but perhaps you were referring to the Helix's 1/4 output? Here is a good video for 4CM setup with Helix. Keep in mind the alternate terminology used for amp FX loops used in this video and apply it appropriately to your Fender. You should be able to use separate Send and Return Blocks (as demonstrated in the first video) rather than the FX Loop block preferred in this video.

You need to see [square brackets] like the one around the text "square brackets" to ensure that your parameter, in this case the "Variax Model" is assigned to snapshots. Square brackets, not parentheses. Snapshot assignation is not automatic with the Variax model selection and neither are the square brackets, you have to explicitly assign the parameter. As others have mentioned make sure you have the parameter on the Input block, "Variax Settings" = "Per Preset" selected. You may want to try the Editor method below. Make sure you mouse-click per the instructions below on the Variax model parameter while you are using one of the methods below - Windows or Mac. You can also assign the parameter directly on the Helix by quickly pressing and turning the "Variax Model" parameter. If you have done it correctly square brackets will appear around the Variax Model. Courtesy of Phil_m and the release notes - Snapshot Assign Shortcut—OPTION-click (Mac) or ALT-click (PC) any Home screen parameter to quickly assign its value to the Snapshots controller - Unassign Controller Shortcut—SHIFT-OPTION-click (Mac) or SHIFT-ALT-click (PC) any Home screen parameter to instantly remove any controller assignment

http://line6.com/support/manuals/helix

Courtesy of Phil_m and the release notes - Snapshot Assign Shortcut—OPTION-click (Mac) or ALT-click (PC) any Home screen parameter to quickly assign its value to the Snapshots controller - Unassign Controller Shortcut—SHIFT-OPTION-click (Mac) or SHIFT-ALT-click (PC) any Home screen parameter to instantly remove any controller assignment

Wow, what a fascinating discussion this turned into. Talk about a "rabbit hole", I could spend days discussing whether free will exists but how could I be sure that conversation was not predetermined? ;) I had never heard that a piano has additional latency but I guess it makes sense. I am assuming this is due to the fact that when you strike a piano key you are not directly plucking a string. The piano key has to first activate a hammer which has to move through space and only then strikes the string. I wonder if experienced piano players get used to subconsciously playing slightly ahead of the beat to compensate for this. I think in addition to the physical cues that aleclee mentioned, knowing the mechanism underlying additional latency can make it easier to tolerate it. So in effect perceived physical cues and/or cognitive ones enable us to better compensate for environmental variables. In the case of a piano, awareness of the requirement of the hammer needing to strike the string, or in the case of a wireless far from the stage, knowing the physics involved with the speed of sound. How many people really understand the underlying reasons for why their driver or OS is causing additional latency and more to the point, where is the benefit? In the case of the piano or the wireless there are tangible rewards in exchange for the latency, e.g. the glorious tone of a good piano or the freedom of wandering around on stage or in the audience untethered. A transactional model can be applied in these cases where latency can be more tolerable if there is a benefit perceived, in effect it is a trade-off. One note - I have noticed that as the wireless signal level decays, particularly on some older wireless systems, the notes can cutoff at the amp/monitor more quickly than wired setups. This lack of sustain can make the latency more noticeable in wireless systems as it causes gaps of silence between notes/chords. Ultimately I can't help but think that it might be nice convenience to have a Helix USB audio interface (other than the Helix or LT itself) that had the same input/output and A/D conversion specs as the Helix for ensuring that the sounds designed with Native translate as seamlessly as possible to the Helix and vice versa. Until then for owners of both a Helix and Native you can just use the Helix as your audio interface for the highest level of portability between presets designed on the computer and those designed on the Helix.

:)

Awesome in every respect!

Good point and worth considering! Keyboard amps can make mic'ing trickier although there are certainly methods for mic'ing keyboard amps as well as the several makes of FRFR and PA cabs that have multiple speakers/horns.