Jump to content

HonestOpinion

Members
  • Posts

    4,996
  • Joined

  • Last visited

  • Days Won

    71

Posts posted by HonestOpinion

  1. On 12/4/2022 at 6:08 PM, thedoctormo said:

    Yes, 3.51 and 3.50.

     

    Usually after a firmware update, I do not restore a backup.  I make note of my global settings, export all presets to individual files, and update the firmware.  Then, I review and reset the global settings (and review any new settings) and import the presets.

     

    However, in this instance, Set List 3 contained presets that were created from scratch in 3.50.  They were not imported from a previous version.

     

    Set Lists 1/2 contain presets that were created with earlier firmware versions.  They imported without any issues.

     

    Just one set list of about 15 presets is corrupt.  However, I can't even get to any of the presets in that set list to remove a corrupt preset.

     

    When you say "reset the global settings", do you mean you manually set them from "global setting notes", or you do you execute a factory reset? If you are not doing a factory reset after firmware upgrades - bad plan and it could easily be the cause of your issue. The factory reset needs to be part of your upgrade process.

    • Upvote 1
  2. On 12/3/2022 at 6:28 AM, SaschaFranck said:

    And fwiw, I even wouldn't care if it was nitpicking (which it obviously wasn't) as I'm pretty good at those things myself. Give and take and all that...

     

    And fwiw #2: I didn't realize @datacommando mentioned this before already, sorry. Anyway, it's edited now.

     

    Just scrolled up and also noticed that @datacommandohad already mentioned this. Compliments to him for posting on this much earlier. I would say "good catch" but that might sound self-congratulatory :-). Thanks for correcting it!

    • Upvote 1
  3. On 11/30/2022 at 11:13 AM, Ldv07 said:

    Hello everyone, HX effects user, I use snapshots to modify my sound. I did the 3.50 update and that changed things at this level. Before I selected my preset, I click on the two buttons to enter snapshots and I could switch from one to the other, it was great. Now when I click on the two buttons I always go into snapshots mode but they flash and as soon as I select one it works but it immediately comes out to return to the preset mode which means that you have to click on the two buttons again to return to snapshots to change. I tried all the possible resets to unload/reload my presets but it doesn't change, my snapshots are still blinking and as soon as one of them is selected, it automatically returns to preset mode. Is there something I missed or is it a new mode in the firmware update? If anyone knows the problem, thank you in advance 

     

    Did you do the backup, factory reset, and then restore, as instructed by the 3.50 upgrade release notes? If not, the issue may just be that your global settings have changed or are not working properly. Make sure you restore from a backup that is hopefully recent but had your old global settings.

     

    Also, unrelated (probably) to the snapshots issue, make sure you download and install the 3.51 version of HX Edit that was just released, either from within HX Edit or from the downloads page. If you already did the backup, factory reset, and then restore, you do NOT have to do it again.

  4. On 11/4/2022 at 6:05 AM, SaschaFranck said:

    After posting the same advice over and over and over throughout the last years (and for several times just during the last hours), I decided to post this here, so I can just link to it (it's also missing in any official Line 6 documentation, at least in a direct, straight ahead form).

     

    So, your update to whatever firmware failed? The following steps helped TONS of people over the last years, so give them a try.

     

    Note: I am assuming that you've backed up your HX family device already. In case you haven't, now is the time. But as your update possibly failed already, you won't be able to do so, then just proceed (and let's hope you've backed up before).

     

    1) Shut down HX Native (using it was likely the reason for the update not to work in the first place, so don't use it this time). Windows users *need* (<-!!!) to make sure no traces of it are running in the background anymore. You can either kill the process by using the task manager, in case you don't know how to do that, just reboot your computer. Again: It is ABSOLUTELY mandatory for the following steps to work that there's NO HX Edit or traces of it running. ...

     

     

     

     

    This is without a doubt one of the most useful posts ever on the forum so believe me I am not nitpicking here. Under your first step "1)", thought you might want to correct the following text "1) Shut down HX Native" from "HX Native" to "HX Edit". Or I suppose you could mention not having either running. I don't think Native interferes with an upgrade but not a terrible idea to shut any running Native instances down. Anyway, thought you might have intended to put "HX Edit" there.

    • Like 1
    • Upvote 1
  5. On 12/2/2022 at 7:01 PM, datacommando said:

    .... If the Firmware was physically damaging specific parts of the hardware, I would seriously expect the internet to be alive with complaints.

     

     

    I get it. Human brains (zombie baiting) are big on pattern recognition. A useful survival mechanism since we crawled out of the primordial ooze. If two things occur in close proximity or time to each other, we often assume cause & effect or correlation. Sometimes confusing one for the other. But sometimes it is neither, just coincidence. Also typically, it is more difficult to prove a negative like "this firmware upgrade NEVER caused a hardware failure".

     

    Without more evidence I find it difficult to jump to the conclusion that this firmware upgrade caused a hardware failure. Particularly when it can't be remedied by either repeating the upgrade steps or rolling back to a previous version, as well as also lacking confirmation from Line 6. One possible exception perhaps would be a part/PCB that is so stressed already that just being reinitialized caused it to fail. In which case, it would have probably failed in short order under regular usage or perhaps the next time it was turned off/on. In other words, it wasn't the firmware update specifically that caused the failure, but more generally any action that addressed/stressed that part. I would think this to be an incredibly rare occurrence. 

    • Upvote 1
  6. On 11/29/2022 at 7:55 AM, theElevators said:

    And, I'm guessing you tried experimenting with the various parameters, like the X-fast is what I use.  What exactly is the issue with the Helix's poly capo in your opinion? 

     

    Just for fun, try other transposition blocks.  Before 3.00, I used Pitch Wham and it was decent enough to transpose my guitar into D standard.  Try out every single transposition thing that the Helix has and play around with parameters -- they can make a huge difference. 

     

    Also, where in the chain do you keep it?  Try in the beginning, and maybe even at the end of your chain (after the amp block).  In my experience, Helix transposition is very accurate, so much so that I use a 3-voice harmonizer that I place after distortion/amp/cab. 

     

    Try adding a compressor beforehand, etc... let us know!

     

    Good advice regarding working the parameters! Various reviews seem to demonstrate the Helix pitch blocks are excellent. I tend to use them infrequently. The question is, does this apply to bass as well as guitar? Are you using this with bass as @Aged_Cheddaris? Tracking for lower frequency notes has historically been more prone to latency or glitching for almost any transposition or synthesis effect, on any device, as the lower notes have a "slower" waveform. Maybe there is also more potential for glitching as there is lots of room for harmonics over the fundamental. 

     

     

    • Like 1
  7. It occurs to me that I have not seen a single user report back here that downgrading their firmware fixed the problem with their knob not working. Four possibilities immediately occur to me.

     

    1. No one has rolled back to a previous firmware version and reported back.
      1. We have no evidence that rolling back fixes these reported hardware failures and therefore no cause and effect with the new firmware can be concluded.
    2. Rolling back does not fix the hardware issue.
      1. As stated above, no one has reported here after rolling back but if the rollback does not fix the issue, it is highly unlikely the problem is the 3.5 firmware.
    3. The upgrade either damages the switches/knobs, or leaves something in place that impacts the hardware that is persistent even after rolling back.
      1. This seems so unlikely to me as to verge on the absurd. I categorically reject it but thought I would mention it in a universe of infinite possibility.
    4. This topic risks becoming a magnet for users with purely coincidental hardware issues, conflating them with the new firmware rollout. To me this seems like the most likely scenario for the affected users.
      1. Coincidence seems to me to be the most likely explanation for these hardware failures, at least currently, until and if more evidence becomes available, such as confirmation from Line 6.
      2. There are very few reports on the forum of hardware failure reports after the firmware upgrade. If this were a problem caused by the firmware update, I would expect to see many more.

    So, in conclusion, I have to trot out the tired old car repair analogy. You get your car back from the shop after a repair, and much too your chagrin, you notice something else on the car is no longer working. The temptation to assume your mechanic "did it" is overwhelming but not necessarily true. The same might be going on here. As of now, the evidence seems compellingly to be pointing to coincidence, NOT the firmware upgrade. I say this, not to discount these users' conclusions, but just to spare them and other users with hardware problems, potentially spinning their wheels looking at the wrong cause. If anyone discovers differently, please report back. Anything is possible, if unlikely.

     

    • Upvote 1
  8. On 11/18/2022 at 6:33 PM, craiganderton said:

     

    ...

     

    People often say "don't mix with your eyes," but I think Bart would have rephrased that as "mix with your eyes open," so you could correlate what you heard with what you saw. It certainly served him well.

     

    I truly appreciate the quote above! Would love to have had this at the ready every time I saw a comment to the effect of "only amateurs need gain reduction meters for a compressor". R.I.P. Bart Walsh!

  9. On 11/30/2022 at 1:09 PM, hillbilly92 said:

    How do I copy one snapshot from one patch to another patch to put into an empty snapshot block?

     

     

    If you are talking about copying a snapshot from one preset to another, you can't do that. The blocks may be, and frequently are, different from preset to preset so that action is simply disallowed. Even if the target preset has exactly the same blocks.

    • Upvote 1
  10. Heads up. A new bugfix editor version HX Edit 3.51, and Native 3.51, are now available for download. There is no 3.51 firmware version (yet?), so you DON'T have to do a factory reset or restore. Just download and install HX Edit via the editor or the downloads page, and Native 3.51 via the downloads page (if you own it or want to trial it).

     

    Would recommend downloading and installing these, particularly if you have one of the issues listed in the 3.51 release notes.

    • Upvote 5
  11. On 11/28/2022 at 12:47 AM, dickmannma said:

    Hi there.

    I upgraded to 3.5 and it seems I can no longer control the model of my Variax from the bypass control. As you can see in the screenshot below, I split my path A/B for electric or acoustic, assigned to footswitch 1. I also have a variax (preset) model assigned to footswitch 1.

     

    The expected behavior is when footswitch one is disabled, the variax is set to spank-1 and the top route is selected (wah, dist, amp, cab). When it is enabled, it switches to the lower path (comp, gain, eq) and sets the variax model to acoustic-5. The model knob on the variax can override the set models, but they will always reset when pressing footswitch 1.

     

    This was all functional before 3.5. Now the path switches, but the model never changes from what is set on the guitar knob. 

     

    PpUdaRZ.png

     

    Is there a new setting or something I am missing that is preventing the helix from setting the model?

     

    Thanks

     

    Did you take a backup and do the factory reset and restore after your upgrade? If not, execute those steps.

     

    In the Input block do you have 'Variax Settings' = "Per Preset" on the second parameter page?

    Note: Once set in one preset it is set in all.

     

    Btw, the following is a known bug in the 3.50 release notes

    • In some cases, the Input block's Variax Tone Knob setting is not recalled across preset changes

     

     

  12. On 11/23/2022 at 3:29 PM, themetallikid said:

    Oh yes, I apologize, I figured out it was the cable tone, but I was curious why it affected my acoustic snapshot/sound so dramatically compared to electric type sounds.    And has anyone ever graphed how the different settings attenuate the high end?

     

    Pretty good article on the impact of cable length on tone below.

     

    It would be interesting, strictly from an inquiring mind would like to know perspective, as you requested, to see some graphs as to what impact different simulated cable lengths has on various instruments. I think the rule of thumb is though, the higher the setting, the more muted the highs and high-mids get, and I suppose, depending on how the 'Cable Tone (length)' emulation is implemented, other parts or the whole of the frequency spectrum. Long cable lengths in the physical world can also attenuate the signal's strength in addition to altering the frequency range. I suppose that could also be being emulated by the 'Cable Tone' setting.

     

    So, the cable length can essentially attenuate the signal and change the frequency range being transmitted as more capacitance is introduced. You can see where, depending on the signal strength and content of the source (e.g. acoustic vs. electric), your tone could be impacted quite differently by the digitally emulated setting (or in the physical world by the cable length).

     

    This would lead one to believe that always leaving the 'Cable Tone' setting set to minimum/shortest would be the way to go as this would provide the maximum, cleanest signal. However, if for example, you want a quick and easy way to diminish the brightness of your tone, you might opt for a higher 'Cable Tone' setting. Similar to the way some players find that they prefer not only a certain range of length, but also a certain brand of cable because of the tone they get from it. Probably due to different materials, jacks, shielding, etc..  Not that the cable is necessarily inherently better quality, just that they prefer its tone.

     

    https://gearaficionado.com/blog/does-guitar-cable-length-affect-your-tone/

    • Like 2
  13. The new amps are great! IMHO this topic focuses on entirely the wrong issue. It is the potential of provoking an anxiety attack via grammatical OCD brought on by the egregious use of so many orphaned close parentheses in the new model names that we should be concerned with! It's a slippery slope from here to amp names with stranded closed brackets or curly braces, or in an ever more dystopian descent, and I shudder even contemplating it, multiple umlauts ;-)

     

    #Märshäll800}}}}]]]]]

    • Haha 2
  14. On 11/22/2022 at 10:56 PM, soundog said:

    If you own a Helix hardware unit (any model, I think), you can't beat this current deal. It's the cheapest price I've seen for Native. Price is good  through 12/5/2022.

     

    Definitely the least expensive I remember. Such a great piece of software. This is an absolute no-brainer for anyone who doesn't have Native yet, jump on it!

  15. On 11/21/2022 at 4:03 AM, tastyguitar said:

    Hey guys, 

     

    I showed up to my gig tonight, set up and noticed the volume knob on the back of the unit was missing, weird. Turned it on and quickly discovered the top 3 footswitches(bank up, and C, D) are not working. Turns out the sound tech on the ship gig I am currently on accidentally knocked my Helix off a piano it was resting on, so it took a pretty hard fall. aaarrrrggghh!! 

     

    I have 3 nights left on this gig and need all the switches to work for my patch setup.

     

    Any ideas? I tried to do a factory reset to see if it could help but that requires the C and D switches to work so no go there.

    I was able to move some things around to get me through the night but its a pain.

     

    Any ideas on a fix or workarounds would be very helpful as I only use this unit on travel gigs and dont know it that well.

     

    Thank you!

     

    Don't own the XL so this is coming from a Helix-centric perspective.

     

    • Create a backup and try a global reset. Maybe that will restore switch operation.
    • Edit a few critical presets to use the footswitches that are working. Reorder your presets for your set so everything can be reached using bank down. If you do this than also keep a laptop available per the next bullet point in the event that you accidentally jump a preset.
    • Keep a laptop available and connected at the gig with the editor up and running for things like bank switching or stomp activation.
    • If you are feeling particularly intrepid you might try opening the case and seeing if maybe a ribbon cable (if the XL has 'em) got knocked loose or something equally obvious.
    • Ask your sound tech to go buy you a new Stomp XL and restore a backup from your damaged unit to the new one ;-)

     

     

  16. On 11/17/2022 at 4:24 PM, llTheSystemll said:

    "you need to do another factory reset as the reset should follow the upgrade."

     

    Drained it!   

     

    I did a 2nd factory reset and the feature is now working.    Thanks so much.   Restoring my backup now.   Hopefully all is well after.

     

    Brian

     

     

     

    Glad to hear it!

    • Like 1
  17. On 11/16/2022 at 10:17 PM, Marcal said:

    I have a Surface Pro 8 that came with Windows 11 so there's no rolling back updates. I am unable to turn OFF the core isolation despite being administrator, so I can't use Helix drivers in my DAW.

     

    Weird that you are not being allowed to turn off 'Memory Integrity'. I wonder if you are not actually in as admin or if it is some kind of group security policy on your Surface. Try booting Windows into safe mode to turn off 'Memory Integrity'. 

     

    Btw, are you going to 'Device Security' --> 'Core Isolation' and then clicking on the 'Core Isolation Details' link to turn off 'Memory Integrity'?

  18. On 11/16/2022 at 5:19 PM, llTheSystemll said:

    ... The first thing I did was to factory reset and upgrade to 3.50.    I finally got around to trying the capacitive switch feature.  ...

     

    Clutching at straws here as you were probably just indicating that you did both the factory reset and the upgrade, but... Did you do them in this order? Factory reset first and then the upgrade. If so, then you need to do another factory reset as the reset should follow the upgrade. Also, did you do a backup first and a restore following the factory reset? If not, then try doing a restore.

     

    I would also try unplugging everything while testing the capacitive touch. Unlikely but maybe you have a cable/grounding issue that is interfering with it. 

     

    If none of this works, I would do another backup, use the Line 6 Updater to reapply the 3.50 firmware, and then do the factory reset and restore.

     

  19. On 11/15/2022 at 2:23 PM, brue58ski said:

     

    I was thinking it could be for a show or a play.

     

    It always struck me as a bit absurd when these requests for additional "pages" of snapshots would pop up on the forum on occasion, but I think this is probably a good guess. Another possibility would be long medleys with quick changes requiring different guitar patches. Uncommon, but I have seen additional snapshots requested.

  20. On 11/15/2022 at 6:34 AM, datacommando said:


    If you want to check out free IRs, check out this thread that was started yet @HonestOpinion way back at the dawn of Helix.

     

     

    Hope this helps/makes sense.

     

     

    Thanks for the reminder this is out there! With luck it will spur some new contributions or be a source for some players looking to try out some IRs.

    • Upvote 1
  21. On 11/14/2022 at 11:55 AM, boynigel said:

    asking for a friend who uses windows (i use mac, so i couldn't help him)

     

    He has a Stomp.  over the weekend he did the 3.5 update.  said he updated HX edit first.

     

    After completing both updates he's saying that he sees the Vitriol model in his Stomp, but not in HX Edit when he has the Stomp connected.

     

    Not sure if it's worth mentioning but given that my personal LT took all of the 45 minutes L6 said it would, his Stomp updated in around 5 minutes.  not sure if that's because the Stomp has less going on than an LT, or if this is a red flag to his woes?   Suggestions?

     

     

     

    Have him look at the version info in HX Edit under 'Help' --> 'About HX Edit'.

×
×
  • Create New...