Jump to content

HonestOpinion

Members
  • Posts

    4,976
  • Joined

  • Last visited

  • Days Won

    71

Everything posted by HonestOpinion

  1. You will not be rolling back the "cakewalk driver". You will be rolling back the Helix 1.97 driver to 1.96. Available from the Line 6 download page.
  2. So true! The latency between your guitar and the output of your modeler, is a different measurement than the one from your modeler's USB output to the DAW when using your modeler as an audio interface. Also, just the physical distance from your sound source introduces latency. Approximately 1ms per foot. That means if you are, for example, five feet away from your monitors, then the 5ms you just improved by tweaking your audio interface, ASIO/driver settings, could just as easily have been picked up by wearing a pair of headphones :-) You're probably using headphones but just saying. A fair amount of latency can be introduced even when you are using your combo amp, FRFR, or even studio speakers, depending on how far you are from them.
  3. One possibility is that you never did the backup, factory reset, and backup restore, or that something went wrong in that process. If so, your global settings may now be back to the factory default. You could try restoring your global settings from a backup. Uncheck everything else. Also, the usual advice about making sure you are using the correct EXP input and try reseating the cable for the expression pedal, if you removed it for the upgrade. Swapping out the cable is never a bad test either. Murphy loves to have a cable fail right after an upgrade.
  4. Great chart, thanks! Are those numbers across the bottom milliseconds? If not, the chart doesn't really indicate when latency becomes audible.
  5. I wonder if your issue has anything in common with the issue some users were having with Cakewalk after the 3.50 update. If so, those users got around it by uninstalling the Line6 version 1.97 driver and (if it was no longer installed) reinstalling the 1.96 driver which you can find on the downloads page. I guess those users are now hoping for a 1.98 update to the driver but until then... Btw, you stated you already tried updating drivers but I'm not sure which ones, so apologies if this is redundant. If you have not already, I might try reinstalling my ASIO driver or download and reinstall the 1.97 version driver from the HX Edit 3.50 update. Line 6
  6. Probably not the issue but just in case something in your globals got changed after the update, also wanted to draw your attention to the manual entry regarding 'Stomp Select' under Global Settings --> Footswitches. Might be interesting to try testing after changing this setting from, for example "Both" to "Touch", or vice-versa. "Stomp Select When set to “Touch,” touching a Stomp mode switch selects its assigned item(s), but pressing doesn’t. When set to “Press,” pressing a Stomp mode switch selects its assigned item(s), but touching doesn’t (helpful if you insist on playing barefoot). When set to “Both,” either touching or pressing will select the assigned item. The default is “Touch.”"
  7. Probably right about a hardware problem but I would still try doing a backup and factory reset and backup restore anyway. If that doesn't help I would follow-up by repeating the entire firmware update with factory reset and backup restore. That doesn't do it, contact Line 6 support.
  8. Both your points are well taken. There is absolutely a dependency between certain devices (e.g. digital modelers) and the computer that can hobble the device if OS upgrades or hardware changes on the computer no longer support the older device. At least there is the option to keep an old OS version around on one of your computers to keep your older drivers and apps still working. I have had a few devices along the way that I have made the decision to do this for. That way I can upgrade my hardware on my own schedule and have multiple computers, a more current one for current devices, and one which is designated for legacy devices. PITA but I have found it necessary at times. Also agree that the way OS upgrades work with their resultant driver and application incompatibility in the Windows, iOS, and even Android universe to some extent, is absolutely geared towards forcing you into a constant, and IMHO too frequent, hardware upgrade cycle for tablets and phones and sometimes even computers.
  9. If you restored a backup that you took after doing a factory reset, you can end up with the default factory global settings. Another possibility is that you unchecked the Global settings when you restored your old backup.
  10. If this really is only a matter of what is essentially an old limit embedded in the code being unnecessarily triggered by the new code, perhaps they did not have time to get to it for this firmware release. They may be able to remove this limitation in a future firmware upgrade. I guess time will tell.
  11. Btw, it would be great to see a post from Line6 with links for the new factory/template setlists each time they get updated. Something like the post below that @Line6Tonyput up for the 3.0 firmware would probably be helpful and nice to have around as a sort of factory/template setlist archive. Again, this is from the 3.0 firmware, not the current 3.5.
  12. The high likelihood is that when you restored your backup you also restored your old Factory and Templates setlists. Try the procedure detailed in the video below. Make sure you get backups first! You may find this video helpful, particularly starting at about 5:10 in. He demonstrates the method for doing the factory reset (on the Helix, use the one specific to your device) and then restoring the user setlists without overwriting the new Factory/Template setlists. Start with a factory reset after getting backups. The trick is, after opening a restore backup session, to expand your setlists and uncheck the ones you want to be restored to Factory from your new firmware. Often the two 'Factory' setlists and maybe the 'Templates' setlist as well. Alternately, any setlist that is checked will be restored from the backup file you selected. Worth mentioning - it is the factory reset that loads the new Factory and Template setlists for your current firmware level to your device. To elaborate on the above, if you then proceed to do a backup restore (as per the firmware release update notes), and do not uncheck the factory/template setlists, you will be restoring the old firmware's factory/template setlists, from your previous backup. This has applied to pretty much every firmware update. Whatever you decide, to retain your old factory setlists, or overwrite them with the new ones from the factory reset, you absolutely should restore your setlists, don't skip this step! Note: As the fellow in the video mentions, individually extracting any Factory or Template presets you may have edited "in place" is a good idea during your initial backup if you want to reload them after the factory reset loads up the new factory/template setlists. If you neglect to do this though, you can always use the 'Extract Files from Backup' command, on your previous backup, to recover individual prior factory presets.
  13. That relay theory seems to have some supporting, or at least correlating, evidence. Thought I would throw the following out there as well. Don't know if this applies to this problem on the HX Stomp (does it use ribbon connectors?), but improper seating on many devices that use ribbon connectors internally can cause intermittent issues. Changes in temperature, being transported, or a slight bump, such as the one caused by a footswitch can cause the cable to move in relation to the contacts' "seat".
  14. Have you resolved this yet. Maybe something in your global settings has changed. I can't open the .php file you uploaded. Can you upload a screenshot instead?
  15. Did you create a backup, and then do a factory reset and backup restore?
  16. I'm in the same boat, after a career in IT, the Line 6 install seems incredibly simple and laudably straightforward to me. That is not the case though if you are not particularly computer savvy, have connectivity issues, have a language barrier, or have problems with the outcomes on things like science experiments and recipes :-) Can't take the time to read the release notes for an update. Be prepared to potentially spend hours unraveling things after it fails. Much easier to take five minutes on the instructions. And yeah, if you embark on an update without a backup, on a device you have spent countless hours programming presets on, well welcome to the wild, wild, west. You are definitely tempting fate. Just don't do it! All I can say is that the forum community has been incredibly good at assisting users in making it through the updates unharmed if perhaps a little traumatized on occasion. Users can take comfort in the fact that the odds of bricking a Line 6 device during an update are incredibly low. Low as in, I think it almost never happens. Also, if tussling with an update is the price for getting a device that has just steadily improved by leaps and bounds for years now, I think most of us should gladly take the hit.
  17. Did you do the factory reset and backup restore after updating HX Edit AND the firmware?
  18. An unselfish view of the forum and a very much appreciated invitation to musicians here to provide feedback about what information might be most helpful to them as well as providing a feedback loop for keeping content accurate and up to date. Wanted to make sure forum users, particularly newer ones, were aware that a 'Follow' feature was available for any content/topic they want to keep up on. In fact, I just clicked the button myself :-)
  19. The only way to get a truly bulletproof update process is for it to require no update release instructions whatsoever. If something fails, the process stops, without hanging, and the device rolls back to a stable state before the update was started. Bad example I know but think about how a Windows update proceeds. Can you imagine how many calls Microsoft support would get if every update actually required people to follow ANY instructions other than pushing the update button, or horrors, their computer was in an unusable state after a failed update (yeah, I know, that never happens - heavy sarcasm). Microsoft probably has a team of people who work on nothing but the update process. Line 6 does not have that level of development resources and even if they did, we would not want their time spent solely on the editor/firmware update process. The update process does not force a one button, no instructions, update. It is close, but not quite there. There is still sometimes no recovery back to steady state when something goes wrong. Thankfully there is the Updater using the flash/firmware file locally that recovers proper operation for 99.9 percent of users. If Line 6 could find a way to integrate it into the automated update process, under the covers, after returning to the device's pre-update state with no user intervention, that would probably reduce the failed update threads substantially. Can the factory reset and restore be integrated into the automatic update? Skipping this step probably increases the number of failures both during subsequent operation, and updates, for users who fail to execute these two operations. Is the LOA required to incorporate all this into an automatic update worth the return? Perhaps in the long run it is. Line 6 has put a lot of time and energy into the update process. I have reservations about how much more development time I want to see them spend on it. What percentage of users even experience a failed update? How much time would be required to streamline and bulletproof the update process for large core changes like the 3.50 update, such that for example they don't require a simple "Resume"? I would hate to see fundamental changes to the Core delayed substantially just to make sure they can be handled seamlessly by the update process when following a couple of simple directions generally works just as well. Anyway, the map to getting to a smoother update process seems fairly clear if not easily implemented. Have to assume that they have made some decisions regarding resource allotment, or we would be there. If that is not the reason, time to find an update coding guru.
  20. Did you remove all Line6 software/drivers before reverting back to 3.15? Did you reinstall the 3.15 version of HX Edit as well as going back to the 3.15 firmware? If that doesn't work maybe reinstalling Cakewalk might work. Might even be worth trying a Cakewalk reinstall after the Line6 HXEdit and firmware 3.50 install/update.
  21. I'm wondering if some people are updating the firmware before or without updating HX Edit. Could see that as one potential point of failure. Another is people not reading the release notes and therefore not hitting "Resume" when it pops up in the editor. Instead, they maybe reboot or restart the install process. There are probably a few other ways to screw it up as well as going directly to using the Updater, instead of starting the process by updating the editor from within HX Edit and then the firmware. Poor internet connectivity interrupting the process. Then there's problems that show up later, after the fact. Like ignoring the instructions to do a factory reset and backup restore, and subsequently having presets or backups that hang or misbehave. Problems with reauthorizing Marketplace downloads that can probably be caused by busy servers or poor internet connectivity. Still not a bullet proof process but reading the release notes and following the directions closely will get most people through with no hassle. My install went exactly as the release notes directed. No issues.
  22. If you are on the Helix it is FS 9 & 10, middle two, bottom row. If another HX device, check here - Reset Options | Helix Help
  23. Love that this firmware update upped the cabs sound quality! Hope they decide to get comprehensive and get around to upgrading the rest of the legacy cabs as well in a future update. Wouldn't want to trigger any OCD by only seeing the current partial selection from the legacy cabs in the new upgraded cabs list. Right now though I am way too busy seeing how many extra blocks I can stuff into every preset thanks to the DSP optimization in the new cabs and IR management :-) From release notes: "Due to further improvements to Helix Core, new Cabs and 1024-point IRs use roughly 66% less DSP as in 3.15 or earlier. Even the new IR > Dual block uses less DSP than a single IR block in 3.15. 2048-point IRs use roughly 80% less DSP, although they still use a lot of memory, so they're still limited to one instance per path. NOTE: Older Hybrid cabs use the same amount of DSP as in earlier firmware."
  24. This message probably means you already have CIMI set to On. Set it to OFF as @Musiclaw indicated by typing "Windows Security" into the Windows search box under the Windows icon, select the 'Device Security' icon, go to the settings and turn off 'Memory Integrity'. I feel like a disclaimer is required so, as stated here already, this may introduce some vulnerabilities to Windows so have the proper alternative security measures in place. Whatever those may be? Hopefully Microsoft and/or Line6 will get this resolved at some point.
  25. Are you talking about being unable to load IRs purchased from the Line 6 Marketplace. Check out this thread:
×
×
  • Create New...