Leaderboard

To rant a little more this is the landing page for the European Line 6 authorized service center: Unreadable - didn't change in at least the last year.

Go to global settings Preferences --> 'Joystick Encoder' and change the setting. From the manual: "Joystick Encoder - Determines the joystick behavior when a block is selected within the Home screen - signal flow. For “Model” (the default), turning the joystick knob scrolls through available models for the selected block. For “Selection,” turning the joystick knob quickly navigates selecting blocks across the signal flow. SHORTCUT: Pressing while turning the joystick reverses the current joystick behavior"

Really? PMS Electronics??? LMAO!

There is a global setting introduced a few versions ago where you can change the behavior of that knob. I did that as well for awhile. I think you can change it to 'relocate' a block instead of 'choose' next block or something.

Hi, I'm not entirely sure that there could be a compelling reason not to follow the instructions. The process of updating will reset the Globals to default and the reboot/rebuilding presets is there to ensure that the presets are brought into line with the current firmware. This must be more relevant when there has been serious changes to the Helix Core. I have always been a rebellious type of person, but anyone who decides to ignore large sections of the "How to Update" instructions and then has issues that they describe as "bugs"... well, there is no help for them. As you have pointed out, after the update is complete and everything seems to function as expected, then you can be selective about when gets reloaded to the hardware. It's not complex and for most users it is a relatively pain free process. Ignore the rules and it becomes yet another "update bricked my Helix" post.

IMO... I would expect that to be intended behavior of the MIDI protocol. If an external midi device is not running (eg: song/part not being played) I'd want full control of the tempo on my Helix - so reverting back to global/snapshot/preset tempo (depending on choice) on song stop makes sense to me. If it didn't work like that, your Helix clock would always be controlled by the external device... which I think you would find very annoying.

Good point regarding the restore. The setlist that is currently failing to load when attempting to import, may well succeed upon a restore. @thedoctormoshould have a backup, particularly if the upgrade was done from within HX Edit, as it is part of the editor's upgrade process. Another possibility per the recommendation to do the factory reset, is that it may allow the import of the setlist, unless it is corrupt. @thedoctormoFollowing the release notes and just doing the backup, factory reset, and restore is the most trouble-free way to execute a firmware update. Winging it without a compelling reason has the potential to introduce complications. The factory/template setlists can always be unchecked during the restore to enable retention of the firmware version's new setlists/presets. Saving any presets in the current factory/template setlists the user wants to retain should be done before executing the factory preset.

If you advertise that you are a "Certified Repair Facility", doing the little PITA jobs comes with the certification. Where else you supposed to take it - "Joe's Lawn Mower and Computer Repair"? My guitar tech would rather be doing headstock repairs on Les Pauls, but he'll do a setup on your Squier Affinity too. It might take 3 weeks though...

Agree. This is just unprofessional. 100% unprofessional.

That is absolutely fine to say "we don't do this" or "no thanks". You don't instead agree to work on something, then after 4 days realize it's "PITA".

Yeah I didnt word that first part well. lol.... I took the presets that were not 'artist' inspired presets and deleted the FX out of those, leaving just the Amps/Cabs. I then went through the amps showcased in those presets and got every type of tone that I'd use and saved it as a new preset. For example, using the Placatar Dirty I got 4 tones out of it. Gritty/Pushed/Crunch/Rock. Labeled as Placatar Gritty/Pushed etc. But because this amp is so versatile, I also did a 'Saturated' version with a 2 at the end of the name. So I got 8 presets out of the Placatar Dirty Model. The cabs I have 5 that seemed to work well with each tone I was looking for. I got that idea from Steve Sterlacci (sp?). He did a review of the 3.5 update and the cabs where he just chose a solid cab/mic option and no matter what type of amp you threw at it, it sounded good with minimal tweaking. So I started there. All my cleans use the same cab combination, same with other tone styles. Is it perfect, no...but i'm basically creating 'better' starting blocks for me to be consistent with preset building. Time consuming you bet, lol, but I'm not done yet. Few amps to go, then going to try and best level them by ear (not perfectly but at least ballpark. As once you drop them in a song preset there could be other things to throw the volume off a bit anyway. Also gonna drop in the Dynamic Ambience on each preset from a favorite block I have. THEN...after that, resave the setlist as my Core Setlist. I'll probably go back through my saved presets list and narrow down what I've saved a bit and remove ones that seem to duplicate to another or really didnt dial in well. That will give me a nice libary to create some favorites from. I'm not really in a full project right now, so I have time...lol.

This is what you'll find in many professional shops. I've worked in broadcast media for 40 years and every place I worked at used this https://www.amazon.com/Hosa-D5S-6-DeoxIT-Contact-Cleaner/dp/B00006LVEU/ref=sr_1_2?crid=1E6TT47I10ZFI&keywords=deoxit&qid=1670244079&sprefix=deoxit%2Caps%2C322&sr=8-2

Hi, This is the probable cause of your issue. The Release Notes for the Firmware Update specifically states the factory reset, and restore from backup, are a required part of the update process. The reset/restore are essential to ensure your presets are fully compatible with the new firmware. This is even more important with the v.3.50 firmware as there were significant changes to the Helix Core. Hope this helps/makes sense.

I have similar issue. HX Stomp 3.50, HX Edit 3.51. I'm sending MIDI clock from BeatBuddy drum machine to HX Stomp. I configured BB to always send MIDI clock even when BB is not playing. However HXS syncs with BB only when BB is playing - HXS FS3 turns blue and blinking syncs with BB. But if BB stops playing, HXS FS3 turns back to red and blinking tempo goes back to global setting default. I confirmed BB keeps sending MIDI clock via MIDI analyzer. Upon further investigation, I found that HXS ignores MIDI clock until it receives MIDI Song Start system message, and ignores MIDI clock again after it receives MIDI Song Stop system message. That's why HXS goes back to default tempo when BB stops. I'm not sure if this is a bug of HX Stomp, or an expected behavior from MIDI protocol. Anyway my workaround was simple; I configured BB not to send Song Stop message, now BB and HXS are always in sync. Hope this helps analyzing your issue.

Try following the instructions at this link to use the Line 6 Updater to reapply the firmware. I might try this using safe boot mode if regular boot mode doesn't work.

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.

Yeah, you may be right. I'll run the test when I find some time. As you mentioned, I was trying to tell myself that they sound the same, when also convincing myself that I was wrong. Either way, it was in my head and the only way to really know is to test. If I find anything exciting (or hell, if I disprove what I assumed I was hearing), I'll reply with results.

I downloaded the Windows 8 version of Line 6 Edit (Version 3.06, Build 104) on my Windows 10 computer and ran the installer, but the installer was unable to retrieve and install the Java Runtime Environment required for Line 6 Edit to work. I decided, instead of using an old copy of JRE 6, to use the current JRE 8 (update 341) from Oracle at java.com by visiting their "Java Downloads for All Operating Systems" page then selecting the Windows Offline (72.73 MB) installer, not the 64-bit one. I am happy to report that Line 6 Edit (Version 3.06, Build 104) is now running just fine with a PODxt on my Windows 10 computer.