DunedinDragon

Just to clarify for you, it's physically impossible for anything that "plugs in" to a device other than possibly plugging directly into an internal bus on a circuit board to operate as quickly or as efficiently as an internal chip built into a circuit regardless of what marketing fluff you might read. It's the difference between moving at the speed of an electron or moving at the speed of a communications processor....that's not even a close race. In this case we're talking about a specialized math processor that's required to do high density mathematical transformations so quickly that the latency is imperceptible to a human being. That's why it can only live within a circuit board and can't afford to endure the latency caused by even the fastest external communications device. Bottom line. There's marketing...and then there's engineering. In the end, engineering is always the true limit.

You realize no one from Line 6 will be reading your suggestion on this forum don't you? That's why Ideascale exists.

Actually, I came to this post because I was astounded by the absurdity of the suggestion. You may as well suggest that mobile phone manufacturers come up with some plug in doohicky that will allow your existing phone to be 5G capable because that's what you're fundamentally asking for. A DSP chip isn't a plug and play architecture, it's a core component and the circuitry is built around it just like the CPU in your computer, or the engine in your car. More importantly you decided to buy the limited version of the Helix rather than the full version and now you want someone to fix your bad decision for you. If you really want to fix the problem, sell or trade in your stomp and get a full sized Helix. Problem solved.

I use a preset per song, but I doubt I'll ever use this as I really don't need a seamless change between presets. But I know it was a highly voted on entry in IdeaScale because some of the other modelers do it, so I think that's what prompted it.

This same thing happened to me on my Helix floor. I could do all other operations other than press it. It's a fairly common solder point problem. If it were related to the update you wouldn't be able to do the operation in HX Edit since HX Edit depends on the Helix firmware to actually accomplish that action. If you can do it in HX Edit then the Helix firmware is working fine.

The key question is, can you select things and add them to your signal chain in HX Edit? If so, the problem is in your joystick hardware and has nothing to do with the upgrade. Call for a service repair ticket.

Well if you follow the instructions you updated HX Edit, then run the new HX Edit which takes care of the rest of the upgrade. If you want to be an outlaw, do it anyway that tickles your fancy but plan to get totally reamed on the forums if you do. Sometimes odd combinations can work. I just did my 3.0 update on a Windows 10 machine. Babysat it through the initial HXEdit installation. Ran HXEdit, chose the upgrade, went off to do some errands, came back in 30 minutes and it was all done. But......I FOLLOWED THE INSTRUCTIONS.

As cruisinon2 stated, that's exactly how you're supposed to use global EQ. That being said I never use it for the following reason. If your guitar sound is being affected on certain frequencies, every other instrument and voice in your setup is being affected in the exact same manner, so they all should be tuned for the room. It's also important to understand the stage may have a different effect on your monitor system than the house is having on your mains. This is most often true in open air or larger venues. This is what the final EQ just prior to the main faders is used for, to adjust the EQ globally across the mix. This may or may not be that important in your case. My mixing board (QSC TouchMix 30) comes with a built-in Real Time Analyzer (RTA) and Feedback Wizard for notching out problematic frequencies which I use for both the main feed and the monitor feed for room adjustments. These types of facilities can also be an add-on to other mixing board setups as well. Just something to be aware of.

All of these things are really dependent to a large degree on where you and your company sit in the pecking order of beta's. Larger companies with bigger market shares come in very early in the process and are more focused on platform stability. This makes sense when you consider they have their own release cycles they're planning so they do as much as they can to preclude touching their software which is sometimes in the process of being developed for it's own release and don't want this to affect their schedule. As you move down the scale to smaller market shares it tends to be a lot more give and take as generally the platform stability is relatively solid. Every once in a while there's something that's uncovered but unless it's a pretty invasive bug, they're typically put off until a maintenance release. What's atypical in this case is vendors stepping out into the public on the public release of a new OS with statements encouraging their users to not do the upgrade yet. THAT is what's not very normal these days with the way OS's are incrementally improved and the users annual licensing fees pay for those incremental improvements that are often just downloaded and installed automatically rather than purchased once and installed as used to be the case. What is different in this case is they've made some MAJOR changes to core elements such as the user interface, and major upgrades come with bigger risks of not finding all the show stopper bugs. I personally have no idea where L6 sits in this hierarchy but I would imagine they're not at the top nor at the bottom. The problem being they're currently in a time crunch to get 3.0 out the door which is probably significantly limiting what they might be willing to do to accommodate this release. That would explain the public announcements.

Okay...we're done here. I'm tired of playing the the children. How could I possibly know that? No manufacturer publishes what bugs are affecting them and how, especially L6. Apple is certainly not going to publish the list of bugs until they have a release that fixes them. I don't know what planet you're from but it's apparently not one with computers.

From 9 to 5 Mac: macOS 11 Big Sur has been widely seen as the least stable of the major new Apple software releases this year during the beta period from June until this fall. Common issues have included graphical issues like problems with external display support, apps freezing, and random reboots. Stability has improved over the course of the beta period and Apple had longer this year with macOS Big Sur launching in November instead of September or October, but bugs and performance issues aren’t totally resolved yet. So there are a few things to consider when wondering “should I upgrade to Big Sur?” TL;DR: if you have any concerns about app stability, performance issues, and other bugs, hold out at least for the next bug fix update before upgrading (but maybe even a later update depending on your stability tolerance). macOS Big Sur actually launched as 11.0.1 (after 11.0.1 RC 2 just two days ago) and the next build will likely fix initial issues with the first release available to the public. If you have critical apps that must work, make sure to check for Big Sur compatibility before upgrading whenever you choose to (again initial release not recommended if you have crucial apps) If you’re cool with initial bugs and issues, go for it! Ideally, if you have a secondary Mac, install Big Sur on that for now

This is incredible. It's like talking to a wall. The point of a beta release is NOT done to help you prepare YOUR software for the new OS. It's about finding bugs, reporting them back to the OS development team, and stabilizing the OS. The LAST thing you would want to do is to try and re-tool your software to work around bugs in the OS. If, and when, the OS manufacturer states explicitly that the "bug" is not a bug but is the way it's designed to work by necessity, then and only then would a 3rd party software manufacturer take steps to fix their software, or choose to alert their customer base there are problems with the new OS and not upgrade as they did in this case. What is stunning to me is that you insist on blaming Line 6 for not doing their job, for which you have no evidence and which is exactly the opposite of what is happening here. They fulfilled their duty to you as their customer to alert you to the problems and try to protect you instead of placing the blame where it deserves to be placed...on the OS manufacturer that didn't adequately test their software and is causing problems with MULTIPLE 3rd party companies. And yet in spite of all of this evidence you still choose to point your finger at all of those manufacturers than the ONE SINGLE SOURCE causing all the problems. And you're doing it with a clear and evident lack of any knowledge about software development or computers in general. So let's get down to the brass tacks here. What is the single most compelling feature that is FORCING you to upgrade to Big Sur? What is the feature you can't live without? If you can't answer those questions then all of this is mute. Apple is nowhere near big enough and prominent enough in the industry to be able to dictate the development schedules of all the companies that have built software for it's OS at the drop of a hat. And that's why they have a long history of filing for bankruptcy multiple times.

Yes...that makes it MUCH easier to characterize. My favorite amps are the ones that best match the style of song I'm playing. But in your case: Clean and slow jazz - I used to use only the Jazz Rivet (Roland JC120), but I've pretty much moved from that to the Archetype Clean. Acoustic guitar tone is best done without an amp model. Follow Jason Sadites recipe on YouTube for piezo-acoustic guitar tones. Southern rock crunch like Fogerty - I tend to go with the WhoWatt (Hiwatt) and sometimes the Interstate Zed (Dr Z Route 66) Hendrix and AC/DC are quite different, but classic rock I tend to use the Placater Models (Friedman) or sometimes the Litigator. Brit Plexi Brt for older classic rock.

I personally know for a fact the Microsoft does, as did IBM in it's mainframe heydays as well as Digital Equipment Corporation (DEC) in it's releases of new PDP-11 updates. It's all a part of being in the operating systems business, and your business is dependent on not breaking the things that depend on your operating system. For the most part this is done through partnership agreements and early BETA testing (long before there are "open" Beta releases). I can't speak to how Apple does it. But I can speak to how Microsoft does it and there are far more employees in testing and QA than there are in development on any given product (roughly about 3 to 1). As far as IBM and DEC I was working on products that ran on those systems and was tasked specifically with BETA testing their operating system updates with our products. Those products sometimes were off-the-shelf commercial products and some were in-house specialized company programs. In spite of all of this, anyone can have a bad release. But because you have a bad release doesn't relieve you from your responsibility to fix it if you're in the operating systems business. To be honest given the general responses of people to the Mac OS releases I often wonder if Apple still sees itself as a small specialty operating system since they really don't play in the bigger business market where Fortune 500 companies are betting their business operations on an operating system. And that causes them to be less diligent in their approach to testing.

The fact that YOUR mac is working fine isn't any indicator at all that the Big Sur release isn't without some significant problems. In the world of operating systems it's up to the manufacturer to thoroughly test their OS to determine if it works with third party software or what it's limitations are as well as what the base requirements are for the Mac to be able to run it correctly and efficiently. This is done during the different phases of bench testing, unit testing, performance testing, integration testing, capacity testing and so forth...LONG before it's released as a BETA to the public. It's very clear from all the press and responses on the internet there are significant issues with this release. If manufacturers are alerted about things that will no longer be supported on the OS, they can fix it. If they don't do thorough enough testing to even determine such things that falls into Apples domain to fix. Product testing, especially when it comes to core software such as operating systems, is not something that doesn't have multiple decades of history and procedures about how to do it right, so there's really no excuse for not doing it correctly if you care about your installed base of users.

Some audio interfaces support USB inputs, but they wouldn't have a driver capable of recognizing the Helix, so it's not really something that could be fixed by Line 6, only by the audio interface manufacturer.

If you're using the Simple Pitch effect which would likely work best, you just adjust the Mix parameter so it's at 100% leaving only the octave below. Or maybe it's reversed...I've never used it that way but try both.

Yes. Not because of the modeler but because I got much more adept at how to arrange and use blocks in my signal chain, more informed about how to use cab/IRs and the choice and placement of mics, more informed on how to best use EQ and compression to fine tune my sound and most importantly how to appropriately gain stage all the elements in my presets and snapshots. Modelers just do what they do which is mathematically simulate real world circuits on amps and effects. The rest is up to me.

As noted above, if you're just coming into modeling you're going to need some time to master it and understand it because it's probably not going to be like anything you've worked with before. At the high end level it's going require a fair amount of knowledge and skill to get the hang of dialing in tones you like and understanding what's involved in that process. Most of the things you mentioned in your post were only problems for people that didn't understand this process and got bad results not based on the modeler, but on their lack of familiarity with it. What I'd suggest is spending some time familiarizing yourself with what the Helix does, the concepts and how to achieve great tones with it and the best place I can point you to is Jason Sadites YouTube channel for dialing in the Helix. https://www.youtube.com/channel/UCvhdK4-QIzo76Y_RIbxZctg

Do you have any evidence you read the OPs original statement which lead to my wry response to his broad characterization of the Dumble and the kind of people that like it? Better yet, maybe you should concern yourself more with what YOU say (which is the only thing you're entitled to control) than attempting to censor what other people say that you don't like....

So the ear bone's connected to the hand bone which is transmitting the audio into the guitar to produce the sensation in your fingers??? Or....maybe you just find that particular tone inspiring....

....And not liked by young users who have limited skill and experience in tones used across a wide variety of genres and styles.

How do you get sensations in the fingers if you're only using headphones???

So....the OP plays ONLY at home on headphones. Given his vast experience, how foolish it would be of everyone not to take note of his professional evaluation of what defines great sound.....

A modal dialogue is a window that you can't get past without doing what it's asking you to do. Given that you got the update to work on your laptop it could very well be your desktop PC has either some problems with some of it's USB ports actually being hubs which tend to cause problems, or you also may have problems with some other devices that are attached such as a Logitech hub which has been known to cause problems. Glad you got it all sorted out though.