zolko60

c. Use 1.4" instrument level as output for Path 1 for all "before amp" effects. Use Return 1 line level as input for Path 2, place all loop FX there and use Send 1 as output.

In others words: You would like to have option of setting Returns globally to chosen output to avoid in messing with patching within presets.
If I am right, so please submit it to ideascale, I will upvote it.

1 hour ago, DunedinDragon said:

 It seems much simpler if you don't want a block affected in a snapshot then simply leave it alone.

"Leaving it alone" in the current implemetation means they are not left alone or am I missing something?
Bypass state is always affected by snapshot and it's change in one snapshot never affects another.
Let's limit the idea of "snapshot safe" to bypass state of DSP block. It's bypass state would remain unchanged with snapshot change. Eg. if you switch on Reverb DSP and make it "snapshot safe" - it will be on all the snapshots. It should be really easy to implement. Users not willing to use new functionality will not touch this option. Nothing will change for them.

Send me your preset. I will try to fix your swapping lights. I am curious how it can happen to you.
Stomp switches are in fact midi toggles - what additional midi toggle can resolve?
Why are you sticked to that "verse chorus bridge" pattern? When I use Helix Native, I have controller that can only toggle beetween two snapshots. This is also overkill setup.
My snapshots are "clean, crunch, metal" - first three are initial "minimal" state. I turn right "amp" on then additional stomps on. This is my workflow, everybody can invent one's own way. 

I am aware of snapshot power and how to change their behavior in Global Settings. However there is one feature that I miss in this logic.
"Snapshot safe" setting for DSP block bypass. it is used in digital mixers. When you load a snapshot you can choose which channels are not affected - safe.
Choosing "snapshot safe" setting would cause no bypass state change while changing snapshots.
What do you think?

So, how you make it right now?
Changing amps with A/B split and tap dancing?
How A/B split is swapping for you? It never swaps for me.
I usually play on 3 amps/3 IRs presets. To change them, I would need 6 stomp switches, so 2 (HxLT) left for my stomps? No way. Snapshots give me possibility of switching with no single stomp switch devotion.
Maybe logic of snaphots needs some upgrade. I think of "snapshot safe" setting for bypass ot some other parameters. Still they are very powerfull tool.

http://artproaudio.com/product/dti-dual-transformer-isolator/#specs

TH30 indeed has no power amp volume. This is why when TH30 channel volumes are set low they can drive instrument level stompboxes, but set high give hot line level signal. My solution would be setting TH30 channels volume quite high to line level Hx Return (and never touch them again) and then drive Hx 1/4" output high to TH30 FX return. It's up to you if you use either Hx Volume knob, Hx EXP pedal or additional volume pedal as TH30 master volume.

12 minutes ago, PeterHamm said:

(...) they've explained why that's problematic, (...)

What I've heard they were fired year ago. ;)

3 hours ago, pvdm68 said:

It would be great if you could build a preset with a Pre Amp and a Power Amp.

https://line6.ideascale.com/a/dtd/independant-power-amp-sim/897075-23508

8ms Class Complaint RTL vs 12ms on ASIO driver at the same buffer means 50% better latency performance. YMMV!

Actually it is not DI box, it is isolator. You can use it when you have issues with built-in DI box or you want transformer sound. You can also connect it with TRS 1/4" outputs. They are impedance balanced. Do whatever makes sense to you.

1. Yes, it prevents. Art DTI is passive, transformer based. Albeit it is step down 3:1 transformer. You connect high impedance unbalanced, line level signal to get low impedance 9dB lower "mic level" balanced signal.
2. Don't bother.
3. Nothing happens. Line 6 clearly states that no damage happens when phantom is applied. The manual is more restricted.
4. It depends on the design. If "phantom blocker" is transformer based, it should be no step down.

"Noticeable" - "no noticeable" depends on personal feeling, experience. This is the thread about Ubuntu. You can easilly prove me wrong in RTL thread I liked.

How can I confirm my RTL measures are right or how you can check it without any special equipment?
1. Let's take any DAW (in my case it is Pro Tools 12 HD) set Helix ASIO driver to 64 samples buffer 48kHz
2. Let's make a new Hx preset with Path USB3/4 input USB 5/6 output, FX Loop in beetween (preset attached) RTLcheck.hlx
3. Let's make two tracks: 
First (named DI) with 7 input (default Hx guitar DI out), 3 output
Second (named RTL) with 5 input, 1/2output (default mixed to Hx Multi Out)
4. Connect guitar to guitar input and record
5. Measure the offset of two recorded tracks.
What I get here is about 512 samples (10.6ms). It is RTL when no AD/DA conversion is measured (AD/DA conversion latency is present but the same in both cases and not "visible")
This is usefull knowledge when you do reamping with Helix - 510 samples should be the offset to align reamped track with DI.
If I switch FX Loop on (via patch cable) i get 600 samples (12.4ms). This is exact value of reported, measured by Utility RTL value. Additional AD/DA latency is 90 samples (1.8ms).

I do not want to mess in the thread which can end up with successful Class Compliancy (in Ubuntu terms) of Helix but...
Centrance measurements in case of Hx are total bulllollipop. It also shows me readings several samples higher than driver (CPU) buffer. I don't take it seriously.

1. Try to swap USB cables.
2. Check if your laptop is properly configured for audio work (DPC latency check, system optimisations)
3. If nothing works, consider:
a. upgrade to 8GB RAM, 
b. buying a new laptop, 
c. keeping using laptop audio connected to AUX

Additional questions:
1. Is HxEdit stable on your laptop?
2. Does any DAW output also break?

On 12/7/2018 at 12:36 PM, thebassman80 said:

Thanks Zolko60 - Do you know of any ideascale topic that adresses this?

No. I haven't found it. But overriding only this (Mainstage does) in not enough. HxN does not transmit any midi outside so, even if you have omnipotent MIDI controler with 100 switches an 7 pedals, when you change a patch (preset) or snapshot your switches initial state will not change.

You have "Level" slider in each wah. Also you have "Mix" not present in real wah world. 

30 minutes ago, rd2rk said:

Gee, I use W10 and have no noticeable latency.

Can you then comfirm the reported RTLs values in that thread? 

As far as I understand, making  Helix Class Complaint (in Linux means) would be a way to get to Class Complaint (OSX) Round Trip Latency timing.
Both systems are Unix based, right?
You can use your OSX/Win vst plugins on Linux, right?

It could be possible when you make phisical MIDI cable loopback (MIDI in/out connected). You can program any button in any mode by Command Center to control anything inside Hx. 
It is just an idea I have not tried it yet.

On 12/4/2018 at 9:50 AM, MarshallArts said:

•  
• If you want to use an additional footswitch (which will show up as FS5 (!) in the HX) you need to get hold of the ring and the sleve of the TRS cable and connect a momentary footswitch. I found the easiest way to do it was to add a mono (TS) jack to the volume pedal and connect it to the jack PCB as shown.
•  

Do you mean you double existing Footswitch 5  by doing this?

You are right thebassman80. No multiple assigments per automation handles in HxN :( Overriding with DAW/host can be difficult to archive.

Indeed. There are machines suffering from various issues like high DPC latency. Sometimes there is a need to isolate and update driver that gives high DPC spikes. What I am writing about are properly configured and optimized for audio use Windows machines. They happen to have replicable RTL figures.

People do care. 7 years lasting thread:
https://www.gearslutz.com/board/music-computers/618474-audio-interface-low-latency-performance-data-base.html