phil_m

Install the 2.91 hot fix.

You need to update HX Edit... Seriously, folks... I’ve posted this reply about a dozen times in this thread. If you don’t see new effects or amps in HX Edit, it means you’re running an outdated version of HX Edit. It’s literally Step 1 of the instructions for updating.

It’s too DSP intensive to be included in the POD Go, unfortunately.

Are you saying you can’t install the latest version of HX Edit? You should be able to do a factory reset and do a Restore from Backup.

Have you updated to 2.91?

You need to update HX Edit.

You can bypass this warning by right clicking on the file and clicking Open. It will give you a warning message asking you’re sure or something, and it will run. It has to do with Apple’s notarization thing. https://support.apple.com/en-us/HT202491

My advice would be to not try to direct monitor through Reaper with the HD500. You probably aren’t going to get the latency to levels that are acceptable. Line 6 drivers are really designed for situations when you’re monitoring the device directly, not through the DAW.

So what are you actually seeing on the scribble strips?

You probably should create a backup in Native before updating, but I’ve never had to use my backup when updating Native. Your settings and presets should all remain through the update. As far as updating Native, you just download and install the latest installation package. That’s all there is to it.

Yes, that’s possible. The Command Center settings are per preset... Really, in some ways they’re per snapshot, but what you’re talking is pretty simple to set up.

I’m not sure what you’re wanting to do with the expression pedal either, but you can assign a CC to an expression pedal connected to the HX Effects, and that in turn can control something on the external pedal. For instance, I used an expression pedal on the HX to control feedback on the Polymoon. But you could also use the HX Effects’ expression pedal to emulate the expression jack on the Meris pedal. That lets you control more than one parameter at once.

@rd2rk pretty much explained it, although, he's referencing the Helix, not the HX Effects. They basically work the same way in this regard, although the HX Effects only has two mono loops and four snapshots per preset. As far as controlling the Enzo or other pedals, it's very easy from the HX Effects. To be honest, the MIDI implementation on the Meris pedals is the trickiest thing to deal with. It was the main reason I ended up selling min. I used to have the Mercury7, Polymoon, Ottobit and Enzo. The problem is that they are kind of black boxes when it comes to MIDI. There's no way to tell what preset they're actually on at any given time, and there's no way to what settings are saved with a preset. So it makes programming very tedious. In order to save a preset to certain slot, you have to send the correct PC to them, which becomes kind of weird thing because you have to set up a way to trigger that PC in the HX temporarily... It's just too much. Right now, I use the Strymon TimeLine and Volante with my HX Effects, and those are much easier to deal with from a MIDI perspective - the TimeLine especially. MIDI controllable pedals with no screen or no visual feedback whatsoever are bad idea, imo...

Have you installed the 2.91 update?

Some of your Global Settings have changed. The easiest thing to do is go to File>Restore from Backup in HX Edit. That will get everything back to the way you had it.

The way IRs are indexed was changed in 2.90. They’re now all indexed by waveform. Meaning, it doesn’t matter what order you have them in the list. The Helix searches for the wav file when associating them with the preset. It looks like this preset is looking for IRS that have been deleted from the unit.

A morality tale told with chicken, porcupines, hippos and ducks... I think this quarantine thing has finally gotten to Eric...

Because the XT Pro was released over 15 years ago.

Thus all indicates that you’re not running the latest version of HX Edit. You need to download and install HX Edit 2.90.

Have you tried performing a factory reset and restoring from backup?

I’m not sure why this happens with Macs sometimes, but I think the solution is to delete the 2.82 installation package prior to downloading the 2.9 one.

Where are you getting 9 months from? Anyway, sometimes bugs pop up in new builds that weren't there before.

I like Windows 10 for the most part. I’ve not had any big problems with it. In my line of work, architecture and engineering, Windows is pretty much the only game in town. There are a few people who use Macs to run Revit or whatnot, but even those have partitioned drives with Windows installed on them for that purpose. There are a lot of things with OS X that I find confusing and kind of backwards, personally.

No, I’m saying Apple forces companies in the OSX ecosystem to jump through a lot of hoops. I’ve not seen anything that says Line 6 isn’t trying. It’s just that sometimes their hands are tied. The fact that Catalina dropped 32-bit support entirely, for instance, screwed a lot of people over. As far as the Line 6 guys using Macs goes, it’s certainly relevant. If most of the testing and development is being done with Macs, how can they actually just ignore it? Regardless, I’ve not seen widespread evidence that there’s some sort of universal problems with the Helix and Macs. I see just as many posts of people having issues with Windows machines. There’s enough variation in these systems, that there’s always going to be anecdotes of people having problems.

You think Line 6 doesn’t pay attention to Mac? Everyone I know at Line 6 uses a Mac... I think it’s harder for companies to keep up with Apple because they have more frequent OS updates, and a lot of updates seem to affect core functionality when it comes to audio, for whatever reason. The whole thing with the certification is kind of a non-issue, in that it can be overridden. It’s just kind of Apple throwing its weight around, trying to make the world play by its rules.