zolko60

I guess your main problem is midi controller usage with your computer software then HxN responce to properly setup midi controll.
For the second issue you will find some guide there:

Anesthesiologist you say... 
While you can make a serious surgery with no anesthesia it is not recommended for various serious reasons. ;)
"No DI" pathology treatment:
1. XLR mic level to mic input, pad on mic pre if too loud.
2. XLR line level to line level input (if present), trim if too loud (if present).
3. 1/4" outputs to 1/4" line inputs (TRS if supported)
Possible complications:
1. Phantom Power infection risk (XLR mic)
2. Ground currents infection risk.

I asked that question to one of the Line 6 firmware developers. I was also interested why Hx Edit can not rebuilt presets.
I was kindly informed this is none of my bussiness.

12 hours ago, cruisinon2 said:

This assumes that perception is a fixed, measurable experience for everyone. It isn't

Sure it isn't fixed!!! Eq. some hoomans are deaf. If they claim they can hear we can test their experience against the truth. We also have measuring devices to check this out.

Reapeating the sentence "music material can not be made equally loud using the loudness meter" 1000 times will not make that statement true.
Some demonstration backing up the claim could. It is XXI century. People fly to the Mars and use digital amp models.
 

12 hours ago, cruisinon2 said:

You're the smartest guy in the room.

Yes. I have spent whole night to think about the reference riff to be used as the world standard for leveling patches. ;)
So please play 4 bars "Smoke on the Water" thru the loudness meter, set the level of your patches and reveal the truth.
:D

On 7/17/2019 at 8:09 PM, brue58ski said:

meters don't really give a totally accurate display of what the level is because they don't show the actual loudness

The loudness meters give as accurate loudness representation as much as digital amp models represent sounds of analog amps.

On 7/17/2019 at 8:09 PM, brue58ski said:

Then there's the Fletcher/Munson curve

Irrelevant when comparing wide spectrum sounds at the similar monitoring levels. K weigting contais kind of conclusion of F/M curve influence. 

On 7/17/2019 at 8:09 PM, brue58ski said:

room EQ which will color your sound after the meters, making them another cause for the meters to be inaccurate.

Sure, but monitor/room EQ influence all sounds the same way at the same listening spot. To be nonsense precise one can make the loudness metering using reference mic at the listening spot (zone).
 

3 hours ago, cruisinon2 said:

There's no global way to level all your patches...

Yes, threre is. Recording direct signal, playing thru patches and adjusting their level accordingly. The software that makes a ping of the prerecorded signal and automaticaly adjust output level can be written.
 

3 hours ago, cruisinon2 said:

but the problem isn't technical, or a lack of features. It's your brain, and the way loudness is percieved.

Loudness metering is meant to minimize the particular brain and ears bias called perception. This is why LUFS measuring can be called objective and repeatable and ear leveling subjective and unrepeatable.

3 hours ago, cruisinon2 said:

A saturated high gain tone registering 90 dB on a meter will always seem louder than a crystal clean tone at that same 90 dB.

A saturated tone registered at -30LUFS should be precieved as equally loud as crystal clear tone at -30LUFS by average listening human target (dogs and bats would probably need a diferent weighting curve)
 

3 hours ago, cruisinon2 said:

There's nothing that can be done about this... we're all in the same boat. Everything needs to be leveled manually.

Something can be done about it - we can use the loudness metering to level the music material.

2 hours ago, Parapentep70 said:

Even for the same instrument, and conditions (tone knob or pickup configuration), if you have 10 patches perfectly balanced one day, they can be completely unbalanced next day no matter how accurate you want to "measure" loudness.Why?

 

Clean, uncompressed patches will sound much louder when you hit the strings much stronger. But heavily compressed and / or distorted patches will sound a tad louder... and dirtier.

You can not unbalance something balanced by playing. Leveling equally means you get the same loudness with the same guitar and playing with different patches. Different playing while leveling patches means cheating. However there can be some influence of the sample being used to make the leveling. 

I can be wrong of course.
If somebody demonstrates how three different patches can be set equally loud better with ear than with the loudness meter I can change my convictions easily.

If it doesn't change anything I would not bother. ;)

There is hardly anyhing to explain. If you use Helix Multi Output for monitoring, USB 1/2 outputs are wired to Hx outputs and to your DAW inputs and USB 1/2 input (DAW monitoring output) is also wired to that output "combo" .
The manual is self explanatory and has nice pictures.

STEP 1b—Backing Up Helix Native

If you don't currently own Helix Native, skip this step.

1. Open any instance of Helix Native 2.80 (NOT the new Helix Native 1.81) within your DAW and click the "My Account" button
    :)

What do you see in "I/O Setup"?
Did you try to reset to "Default"?

On 7/29/2019 at 2:48 PM, EnjoyRC said:

is it possible for Helix Native to send bypass MIDI info out?

It seems HxN can not send any MIDI from the plugin. Some DAWs can however map automation to MIDI out but I haven't tried it.

High? I used to have about 15% CPU load in Reaper on 2gen, 2core mobile i5 at 128 samples buffer @48kHz with Native Instruments Komplete Audio 6 interface.
Check your audio interface, maybe its performance is an issue.

S/PDIF is a protocol. XLR is a connector.. You can send AES/EBU. DMX, analog audio  and whatever using XLR equipped cable.

https://line6.com/support/topic/47456-helix-floor-footswitch-failing/

4 minutes ago, darshan said:

The guitar that has this problem is a Squier Telecaster with Seymour Duncan '59 humbackers, they shouldn't be that loud.. I don't understand.

IDK. When i connect classic PAF style humbucker (8kohm DC resistance) guitars to the Helix LT it is really hard to exceed -10dBFS peaks going direct.

1 hour ago, phil_m said:

Setting the 1/4” inputs to Line on the Stomp is functionally the same as enabling the input pad on the Helix. And, yes, the Stomp does have variable input impedance.

Sorry, my fault. The manual p.18 states "HX Stomp has an impedance circuit on its Main L/R inputs that affects tone and feel by loading your guitar's pickups as they would by an effect pedal or amplifier. A lower value will typically result in some high frequency attenuation, lower gain, and an overall "softer" feel. A higher value provides full frequency response, higher gain, and an overall "tighter" feel."
https://line6.com/data/6/0a020a4010c935bb66a4c0c44f/application/pdf/HX Stomp Manual - English .pdf
However the pad in Hx FL/RA/LT is 6dB what gives 17dB full scale vs 19dBu "line level".

BTW if the electic guitar exceeds 17dBu peak level I assume it has incredible hot active circut implemented and should be modded to conform to the standard levels.

This is what I mean. Guitar modellers and FXs can have audio interface feature but it is not their main purpose. Eg. Fractal AX8 has no interface feature and nobody cares.
Albeit the Helix hardware beats many audio interfaces sound quality wise. It does not matter to me they natively support 96 or 192kHz while their performance is inferior.
I have tested Behringer UMC202HD loopback - 89dB S/N ratio vs Helix 110dB.

Ouch! There is no pad in the Helix Stomp! No variable impedance neither. No info about "Line Level" impedance. :(

12 hours ago, soundog said:

So you think the Line 6 driver does some sort of software sample rate conversion?

Yes, I do. CC usage - 11ms Round Trip Latency, Driver - 19ms (48kHz, 128 samples buffer, 2.7 firmware).
Still on 2.7 aggregating CC was possible. Now datacommando claims it is not.

The answer is simple. Helix is not marketed as an audio interface. Its internal operation is 48kHz. Making USB transfer at different sample rates would probably require more ICs or DSP power.

1 hour ago, rucmas said:

Trash it?   how so? 

somewhat of a serial DFU error kind of a guy here= me. 

As datacommando has shown thrashing (unistalling) Core Audio driver brings back Helix Class Compliant usage. It should be safe.
USB 12 output is hardwired to Multi Output. You can not change it in Global Settings. Maybe you use different outputs for monitoring?

12 minutes ago, rucmas said:

Updated Helix driver for MAC too. 

Trash it! See what happens ;)

1 minute ago, datacommando said:

The previously listed item named "Helix" is no longer there when you install the 1.0.7 'required driver for Mac OS"

I thougt only Class Compliant naming changed (also changed?)
Now I understand why it is to hard to evaluate. To check CC you need to uninstall the driver.

2 minutes ago, datacommando said:

To use Helix as an audio interface for Mac® applications, it is not necessary to install any additional driver. Helix will utilize the Mac® 

That statement contradicts the driver description:  "Helix Mac Driver 1.0.7 is a required update to support Helix Firmware 2.80 or greater."

So to clarify: After instaling Core Audio high latency mutli sampling driver Class Compliant Helix usage is no longer possible.
Am I right?

4 minutes ago, datacommando said:

Soundflower is an open source kernel extension for MacOS, designed to create a virtual audio output device that can also act as an input. It is now superseded by Loopback - I need to update that, but because it’s virtual - no driver is needed.

I swear I don't know what you are talking about. :D
 

4 minutes ago, datacommando said:

don’t know what exactly the Line 6 driver “precludes”, but if it’s not installed you don’t get access to sample rates other than 48k, therefore that must be what it precludes.

 

Helix is 48kHz device so 48Khz is just expected as Class Compliant. If you want to use other sample rates and your DAW can not resample on the fly you have option to isnstall that high latency Core Audio driver which can resample on the fly.
I am asking if Class Complaint usage is still avialiable option after installing Core Audio driver or CA driver instalation "precludes" CC usage.