zolko60

Hmm, I don't know much about Apple Class Compliancy but Class Compliant idea is there is not installable driver. It is hanshaking driverless protocol. By "preclude" you mean CC usage option is no longer present in OSX? The new Core Audio driver decription suggest the driver is required for 2.80 firmware compatibility what not neccessary must be true.

So if the two "drivers" happen to appear in OSX sound panel something is wrong? What happens if somebody has older driver installed? It becomes not compatible? BTW: After the 2.80 update Class Compliant name of the Helix changed from "Helix" to "Line 6 Helix".

Nope.

HX Effects 2.80.1 Hot Fix is avialable for download.

Installing a Helix Mac Driver is a workaround (or maybe it is not because "1.0.7.is a required update"?) Helix Mac Driver is Core Audio driver not "Apple Class Complaint" usage which requires no driver instalation and gives much lower latency at the expence of other than 48kHz sample rates. 48kHz is the only sample rate Helix can work with as the "Apple Class Compliant" device. The question is: Can OSX users test if "Apple Class Compliant" usage works with respect to the Helix as audio input device. Just try to record anything and report. Testing and reporting means to provide data such as: OSX version, hardware type, Helix type.

If this is true and Helix lost its Class Compliancy with 2.80 (!!!) than you have optional multi sample rate Core Audio driver.

That headroom can be shocking for somebody used to "just under the ceiling recording" and loudness wars veterans. It is proper however. +11dBu full scale level is used to model devices and check them with various guitars. If you play using hammer you also have right to expect unclipped AD conversion. If you happen to have 20dB analog clean boost the headroom is not sufficient anyway.

Some L6 employees claim on some places that bug will be adressed in 2.81 to be released ASAP.

What would you you like to discuss? -18dBFS for distorted sound can be much louder than -10dBFS clean because it usually means peak value. 5dB input pad basically lowers amp gain. Nobody cares about unity gain when amp modeling is involved. The unity gain on your picture is just the particular preamp design. To what scale "U" relates? -20/+20 or -15/+65 ?

What makes you think guys an interface is relevant? Antelope Zen Tour RTL is 2,5ms Thunderbold and 5ms USB (@44kHz 32 smpl buffer) and 12/15ms at 256 buffer. What is Hx Native 1.8 latency?

What latency HxN 1.8 is reporting in PT? What makes you think changing buffer size affects the latency caused by plugins? Helix Native 1.71 AAX version reports 16 samples of latency (checked at 48kHz) and PT 12.5 Windows on ASIO drivers set this value for latency compensation.

It seems the new driver can not be downloaded and installed separately of Hx Updater (Edit?). Maybe there are two new Windows drivers - Helix ASIO 1.93 and WinUSB 1.0.0.3? In "driver downloads" drivers are called Line 6 Driver2 with version numbers like "1.91" https://line6.com/software/index.html

Great! Awesome! :D Is it that the example L6 CS knows the answer because it is the "Known Issue" or "FAQ"? So my question is: Why can't it be added to "Known Issues" and/or "Knowledge Base"? Everybody willing to help would link to that reference. Why not make world better with such a little effort?

This is common to all modellers (or even clones). Some simulations sound even better than original, some comparable, some not enough.

I don't have the Stomp, but on the Stomp diagram USB 5/6 inputs do not bypass any DSP blocks and 1/4" out is hardwired to USB 1/2 inputs.

Thank you! 2.80 firmware for me is the (non?) public beta quality. I appreciate it was released, but to make an aware decision to be a beta tester I would rather have "Known Issues" section of the release notes to be complete.

The 2.80 EXP bug confirmed. I can live with that but I can also understand a pain of those using EXPs more complicated way.

2.80. It works! Thank you! Snapshot Bypass Helix Floor, Helix Rack/Control, Helix LT, Helix Native, HX Effects, HX Stomp, HX Edit There may be situations where you don't want Helix's snapshots to control a particular block's bypass state; that is, you'd prefer to turn it on and off manually. For example, you may want manual control of a boost pedal at any time without worrying whether a particular snapshot might turn it on or off. Depending on your type of Helix/HX product, follow the procedure below: Helix Floor/Rack/LT—Select a processing block, press ACTION, and set Knob 5 (Snapshot Bypass) to "Off" to disable snapshot control of that block's bypass state HX Effects—Select a processing block, press ACTION, and press the "Snapshot Bypass" switch to disable snapshot control of that block's bypass state HX Stomp—From Edit view, select a processing block, press ACTION, press PAGE >, and set Knob 3 (Snapshot Bypass) to "Off" to disable snapshot control of that block's bypass state Helix Native/HX Edit—Right-click (Mac: control-click) on a processing block and uncheck "Snapshot Bypass." Alternatively, right-click (Mac: control-click) the Bypass button to uncheck "Snapshot Bypass."

Done! Weird things happen! Eg. not writting manuals, release of public betas as legit updates, skipping 13th versions... :D

If you think this is worth to submit to ideascale I will upvote it.

I think going 1/4" to DI is the best way. DI boxes usually have pads (like 20 and 40dB), they provide phantom power potection and good ground isolation. If you don't want to pad at DI box you can switch 1/4" output to instrument level. It is only 8dB lower. BTW: 1. If you don't use Global EQ in your monitor path you can use it as attenuator. 2. There are also Di boxes with XLR input avialiable on the market.

When you change the target loudness by adjusting only output level than yes the linear character of digital to analog relationship will change the level by the same value. Albeit loudness meters have their scale called LUFS which is somewhat similar to dBFS RMS but weighted and windowed. So it is frequency dependent and averaged. As you may have read Helix XLR mic level is quite hot - it gives 7dB louder signal than 1/4" line level output thru -18dB DI box. But not all DI boxes are the same. Neither are mic pres and stageboxes - "unity gain" term is usually valid with line level signals padded to mic level.

What do you mean by "relationship" in case of analog and digital outputs? If how the digital level is translated to analog here is the answer:

No EQ needs "mix" parameter because EQ phase shifts would make completely new EQ curve.

This is awsome! With the addition of STL Tones Libra every guitarist will have the convienient tools for making his/her own unique IRs collections. What I miss in Mikko is Z dimension (distance) view switchable from XY view.