Please ensure Javascript is enabled for purposes of website accessibility Jump to content

ajfkeith

Members
  • Posts

    10
  • Joined

  • Last visited

Profile Information

  • Registered Products
    2

ajfkeith's Achievements

Rookie

Rookie (2/14)

  • Collaborator Rare
  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare

Recent Badges

2

Reputation

  1. Yeah the freezing happens while disconnected or connected to the MBP. It seems to be a bug in the 3.6 code rather than an issue with the actual upgrade process. It is strange I'm the only one hitting it apparently. Now that I'm back to 3.5 I'll probably wait for a later 3.6 release and try it again. Fortunately 3.5 has everything I need. Cheers
  2. @datacommando - thanks I appreciate you jumping in to try to help. Answers to your questions: 1. Computer and OS: MacBook Pro 2021; Ventura 13.3.1 2. By "successful" I meant to say the upgrade (via HX Edit) completed with no errors; auto-restarted/rebooted and rebuilt the presets; then continued to boot completely in 3.60. Once booted the system operated normally for a several minutes (and connected to and sync'd with HX Edit). It would freeze after several minutes. 3. Yes I restored from the backup bundle. I also removed all presets (first by overwriting them with New Presets, then later with reset sequence (below) in case an existing preset was causing the problem. Other things I tried: - Using Line 6 Updater v1.27 (thanks I used the wrong name for it) I "updated" to 3.60. Again the upgrade completed without error, but the problem (freezing later) persisted. So the Updater Tool didn't "fail" - that method just didn't fix the freezing problem. - I repeated the upgrade (again using Updater) after booting in safe mode. - I reset the system with no presets, no IRs (Power On with FS 5+12 pressed) - I reset the system to "reformat existing presets" (Power on with FS 10+11 pressed) - I opened a support ticket; they have advised me to install again using Updater (already tried this). If that didn't work they said take it in for repair. I'm using past tense here because I got the system working after using Updater to downgrade the firmware to 3.50. This failed twice ("Update Failed") but worked the third time. Now all is well, but I won't be updating to 3.6 any time soon. My Helix is quite old (I was an early buyer). Perhaps old HW revs have something to do with it.
  3. Same thing happens if not connected. I think the next thing I'll try is to delete all the factory presets - since that's all that's in there now - if I can do that before it crashes again.
  4. I successfully upgraded by Helix Floor. "Successfully", meaning the install went well, the new amps/effects are there. But after a few minutes the device freezes where it is and doesn't respond to footswitches, encoders, switches...nothing. The connection to HX Edit dies. It does continue to put out sound. A reboot fixes recovers the device for a few minutes until it happens again. I have tried all manner of factory resets, and attempted to re-install 3.60 using Installer 2.70. No luck. Has anyone else seen this? I have a support case open for this and waiting to hear back.
  5. If I'm not mistaken there's a preset in the TEMPLATES setlist that is specifically designed to control either logic or garageband. It was introduced in 2.8 if I recall.
  6. Thanks for the replies. So is it fair to way there's no real difference between doing this and just using a Y Block on the Helix where one signal chain stays on Path 1A and the other (1B) is pushed to Path 2 at the output block? Well...other than if I do the former I can use a gate on one path (fuzz) and no gate on the other (clean).
  7. I'm curious what is actually happening if my Helix is set up with a single input (in my case Variax VDI) into a preset where both DSPs are configured to take input from this device in parallel (e.g both set to "Multi"). Let's say on Path 1 I use a clean amp and on path 2 a crunchy one. Is this signal from the guitar shared/split in some way, or have I effectively created the equivalent of two identical guitars feeding two completely separate rigs? I'm trying to understand if this is the same as splitting a single path (Y or X/Y split) or not? Even if it is the same I suppose I could at least take advantage of additional DSP resources by using both inputs from the one source.
  8. There is an Ideascale posting for this. Here's the link to vote: http://line6.ideascale.com/a/dtd/Multiple-switches-for-1-block/801153-23508
×
×
  • Create New...