rd2rk

I don't own one, so I can't say for sure, but that's not usually how FX Loops work. What does the manual say? That's why I don't use noise gates. The input gate on my HXS/FLOOR is pretty good IMO, but even so I rarely use it. I'm not really a super high-gain guy, so I don't really need it. Try it both ways. If it SOUNDS good it IS good! Amp FX Loops are usually INSTRUMENT level, so make sure that the HXFX Loop is set properly. The FX Loops on the Helix line are known to add a small amount of noise which, when used with high-gain amp settings can be annoying. Be sure that the cables you're using in the FX Loop are high quality shielded cables no longer than absolutely necessary to minimize that.

It looks to me like you're thinking of the NS2 as two separate noise gates. What you're really doing is putting both the HXFX and the MT15 in the FX Loop of the NS2. The only gating you'll get is at the end of the signal chain. The net effect would be the same as just using the HXFX/MT15 in standard 4cm and putting the NS2 between the HXFX OUT and the MT15 RETURN. I don't have the HXFX (HXS and FLOOR) but AFAICT, unlike the HXS/FLOOR, the HXFX does not have an input gate, so you'd have to use a block for a gate, either at the beginning or end of the chain depending upon where you decide to place the NS2. On the + side, you're getting back the FX Loop 2 block, so total blocks remain the same. As far as placement, try it both ways. The NS2 might work better in one place or the other.

Not a function I've ever needed to use, but I also recalled that once upon a time that was possible. It's in the 3.0 manual, but not 3.80, which is when they added the CCs for the knobs. I'd assumed they'd dropped it. Sure enough, I just tried it from MIDIOX and it still works! @Digital_Igloo- take note! If there's ever a v4.0 and accompanying manual update, you might want to include this!

You tried it? It still works?

The "trails" parameter of the delay blocks needs to be ON. If you want "with no signal from A/with no signal whatsoever from B", THAT'S going to cut off the "tails". A/B Split blocks are either/or, no both. That's why I'm using the MIX block, because it is a MIXER. Attached is the same thing but simply bypassing the inactive block, thus leaving any "tails" to ring out. Test the examples when you get a chance and play with the settings within each block. siderealx2.hlx

Sounds like THAT preset was corrupted. It happens. Try recreating the preset from scratch.

Snapshots. Example attached. MIX Block Levels for both A and B are assigned to Snapshots. It's hard to hear the BBD over the Harmony, so mess with the settings, I just set them quick to verify that it works. Just remember that if Snapshot Recall is set to discard, you'll need to SAVE the preset each time you make a change, so you might want to set that to recall while you're messing with the settings. siderealx.hlx

??? Perhaps if you describe WHY you want to do whatever it is that you actually want to do?

Use an A/B Split Block and assign a FS to the ROUTE TO parameter. It will toggle between A and B. You can also do it with Snapshots by assigning the ROUTE TO parameter to SNAPSHOTS and then saving each Snapshot with that parameter set as desired.

In HX Edit, RIGHT-CLICK on the parameter. In the drop-down list that appears, scroll down to and select SNAPSHOTS. The parameter value will turn white and be enclosed in brackets. SAVE THE PRESET. In each SNAPSHOT that you plan to use set the desired value for that parameter in that SNAPSHOT and SAVE THE PRESET. EDIT: The PAN block does not have a GAIN parameter. RECALL simply means that you can change all of your SNAPSHOTS without needing to SAVE THE PRESET until you're done. It also means that while playing changes made manually to assigned parameters will be retained between SNAPSHOT changes until you change the preset but will not be permanent unless you SAVE THE PRESET.

Global Settings>Ins/Outs>FX Loop1 = INST Guitar>Helix INPUT>Helix SEND 1>5153 INPUT>5153 SEND>Helix RETURN 1>Helix L/MONO MAIN Output>5153 RETURN. Shielded cables all around. The FX Loop Block goes between the PRE effects (OD, MODS etc) and the POST effects (delay, reverb, etc). Of course, any kind of effects can go anywhere, that's just the most common way. If you're still having problems, attach a sample preset so we can see what might be the issue.

No.

You can also leave the USB disconnected unless you need it.

Set the CONTROLLER of the parameter you want to change to SNAPSHOTS. In HX Edit, RIGHT CLICK on the parameter to bring up the CONTROLLER options. In the SNAPSHOT where you want it to change set the desired value and SAVE the PRESET. The other SNAPSHOTS will remain at whatever value the parameter was at when you SAVED those SNAPSHOTS. IOW - you can now have different values in every SNAPSHOT

So, in HX Edit, from the MENU BAR, you select FILE>RESTORE FROM BACKUP, select a backup file and get that message? Or, in the restore dialog box you see the path to the backup folder and "Backup File: No Compatible files in selected folder" but when you use Explorer to go to the actual folder there are backup files there?

Here we are at the heart of the problem. After a cursory look at the HEX and NEKTAR manuals, this is how I'd do it: Set the HEX to accept PC (and CC if desired - see below). Set the HEX to MIDI Channel 2. On the HEX, save as many Loop combinations as you want. Save them to consecutive PC#s (for simplicity). On the HXFX, set Global Settings>MIDI>MIDI THRU = ON; MIDI PC Rx = MIDI; MIDI PC Tx = OFF; Snapshot CC Send = OFF. The last 2 - MIDI PC Tx and Snapshot CC Send - shouldn't really matter if you've set the MIDI Channels as described, but, "Best Practice". Leave the HXFX MIDI CHANNEL set to 1 (default BASE CHANNEL - check to be sure BASE is set that way). Set up as many HXFX combinations/presets as you want. In Control Center, in each preset, on SS1 (Snapshot 1), use the first Instant Command (IC1 - the first lightning bolt) to send the PC# for the default HEX Loop that you want to load with that preset when the HXFX preset loads. Be sure to set the Channel to 2. SAVE the Preset on SS1. Apart from that, forget Snapshots as controls for the HEX, just use them for controlling the FX on the HXFX in SS MODE or individual FX Bypass/parameter control in STOMP MODE. IOW - use the HXFX switches for their primary functions. The MODE needs only change if you WANT it to change and has NO effect on what's coming from the Nektar. KISS theory. NOTE - if you choose to use Snapshots like this, be sure that in each Snapshot IC1 is set to the desired HEX Loop. The ICs are sent each time you change Snapshots but won't RESEND the same message unless a DIFFERENT message is sent on that IC. The IC value on new Snapshots defaults to PC# 0 (zero) unless you manually set it in each Snapshot. So, in each SS either set IC1 to the SS1 PC# or to the PC# for the HEX loop that you want to use with that SS. Use the Nektar to select the HXFX Preset (on MIDI CHANNEL 1) which will then automatically load the default HEX Loop for that HXFX Preset. Set the remaining available Nektar switches to send whatever alternate PC#/HEX Loop Combinations you want available in that Nektar/HXFX Preset (MIDI CHANNEL 2). You COULD also have any or all of the Nektar switches call totally different HXFX Presets. Lots of possibilities. This gives you access to 128 HXFX Presets/FX configurations and up to 10 HEX Loops from every HXFX Preset vs 4 using Snapshots. You could also use CC#s 80-85, though I would see that as limiting vs using PC#s. Whatever floats yer boat! Anyhow, this method, while it may SEEM complicated, is the most efficient and flexible use of your HW. It allows you total control of HXFX Stomps and Snapshots on the HXFX and total control of HEX Loop Combinations with the Nektar. You never have to touch the HXFX or worry about the MODE unless you want to for Stomp/SS control. Of course, while VERY complex combinations of HXFX and HEX Loops are possible with this configuration, it can also be as simple as you want. I've attached an example preset to demo the SS IC configuration. I created it on my HXS, but it SHOULD load on your HXFX. If not, you can convert it with Native. I tested what I described using my Ampero Control and it all works as it should in terms of what gets sent when. Final Note: The Nektar Pacer allows for a lot of different ways to do what I've described. I'm not going to try to figure out a "best" way. The manual kinda sucks and, although there's a web-based editor available here: Nektar Pacer Editor by StudioCode.dev It can't be used without a Pacer actually connected, so I was unable to play around with it. When setting up your Pacer (or any MIDI controller) you should have a MIDI Monitor to verify that the controller is ACTUALLY sending what you THINK it's sending. If you don't already have one, here's a link to a simple one: MIDIView - Free MIDI Monitor tool for Win & Mac Of course, the Gold Standard is MIDIOX (Windows only): MIDIOX Questions? clausiii.hlx

As is often the case, the devil is in the details, and the six external fx/stompboxes weren't part of the original spec. At least, that was not clear. So, I'd need to know WHAT they are and HOW they're placed in the signal chain. If they can be controlled via MIDI, which it SEEMS like what you are implying, then everything I said above still applies. I'd like to help you sort this out, but PLEASE try to be VERY clear on the details.

Apart from being able to use the DEFAULT FS CC# instead of an ASSIGNED CC#, why is it important to remain in STOMP MODE? If you ASSIGN a custom MIDI CC (NOT the default FS CC) to the block's MIDI BYPASS function then it doesn't matter what MODE you're in, it always just works as expected. Even if you're using the FS to change parameters in other blocks/fx, those changes can also be assigned to the same MIDI CC# as the BYPASS. This is true of ALL MIDI assignable functions - preset, snapshot, bypass, parameter change - whatever. When using ASSIGNED MIDI it is not necessary to be in a specific MODE, and the ASSIGNED MIDI message does NOT change the MODE. IOW - you are DIRECTLY controlling the actual FUNCTIONS that you want to control, not using the physical FS on the HXFX to do so. Therefore, the current MODE is irrelevant.

As long as you're using the Cat as the ASIO device in the DAW it still works. The AUX IN hits the signal at the power amp where it mixes with the processed guitar signal. Or you could get a proper interface with enough inputs to allow you to do both at the same time. I know. Costs $, and then you lose the DI capability unless you also get an ABY box, more money, more wires. Of course, then you'd also be able to record the source material alongside your guitar. Compromises suck.

Set your Playback Device to the computer's sound card. Then you can use the app (Spotify, YT) to control the level. You'll need a 1/8" Stereo cable to connect the computer to the Cat's AUX IN.

As Bonnie said. I don't have the HXFX, I have the HXS which, for most intents and purposes, works the same way. I'm using an Ampero Control MIDI controller. I'm not sure what you mean by "MOMENTARY" in this context, maybe it's an HXFX thing, but the manual defines it the same way as for my HXS. If the following is not what you're after, maybe explain what you mean by MOMENTARY. Instead of using the default MIDI message for the FS, assign the Block Bypass to another MIDI CC#. EX: You want to toggle the OD Block. OD Block assigned to FS1 = CC#49 (default) - if I send this after a SS change (say, my default is SS1 and I change to SS3) it does whatever FS1 does in the current MODE, but does not switch MODEs. IOW - it only works if the MODE is STOMP. I think that is the problem you are describing? ALT: OD Block MIDI Bypass = Toggling CC#111 (any CC# not reserved in the MIDI Standard or HXFX MIDI specs). This works regardless and independent of the current MODE, and without switching MODES.

IRs (IMPULSE RESPONSES - the CABS in Helix) are how mic'd cabs (speakers) are modeled. There's a difference between FAR FIELD IRs (FFIR) and NEAR FIELD IRs (NFIR), and some people who have Golden Ears claim to be able to tell the difference (I can't), but it's not a big enough difference to convince IR vendors to adopt the much more difficult to record FFIRs. The VAST majority of commercially available IRs are NFIRs. If you're referring to an ANALOG CAB MODEL, they are basically static EQ settings. Most people prefer IRs, but when well done, are just fine for most LIVE work. The audience at Joe's Dive Bar and G ill can't tell the difference and, if you're doing your job right, they're too drunk to care ;-)

Good to hear! I don't see any reason for the MIDI Ch11 unless it's a MIDIPatchbay thing, CH1 works for me, and I tried it on Ch3 the other day and that works too. Whatever my earlier problem was, it's fixed. As long as it works for you, the MIDI Channel is unimportant unless you add other MIDI devices. Yes, whatever HOST app you use, DAW, MIDOX, whatever, needs to be kept running to handle the actual routing of the signals.

Just to clarify, since you originally asked about going to a PA (FOH) - Using Helix amps: a single amp with pre amp fx in MONO, stereo post amp fx out to dual guitar amps using their fx loop returns should not be a DSP issue. Using TWO Helix amps for end-to-end stereo will almost definitely be a DSP problem. In neither case would the FOH routing affect DSP.

I don't see any reason why you can't use the MC6 for both Songbook on the computer and Catalyst Edit and MIDI over USB on the Cat60 with the CME. Since you're going to use the computer for Songbook, you can test the Cat's MIDI by simply connecting the Cat's USB to another USB port or hub. The CME is only necessary if you're NOT using a computer or mobile device as HOST. Running any DAW should allow you to route MIDI from your MC6 to the Cat. Or you can use MIDIOX. Just use different MIDI Channels for Songbook and the Cat. The default MIDI Channel for both Songbook and Cat60 is Channel 1, so change one or the other. Yes, I use the MIDI messages defined in the Cat's manual. Whenever using MIDI and especially when controlling multiple devices/apps, you want to use a MIDI Monitor app to confirm that your controller is sending what you THINK it's sending to WHERE you think it's sending it. Some DAWs have built-in monitors, some require a plugin. What DAW do you use?