Jump to content

zolko60

Members
  • Posts

    594
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by zolko60

  1. The loudness meters give as accurate loudness representation as much as digital amp models represent sounds of analog amps. Irrelevant when comparing wide spectrum sounds at the similar monitoring levels. K weigting contais kind of conclusion of F/M curve influence. 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). 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. 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. 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) Something can be done about it - we can use the loudness metering to level the music material. 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.
  2. If it doesn't change anything I would not bother. ;)
  3. 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.
  4. STEP 1b—Backing Up Helix Native If you don't currently own Helix Native, skip this step. Open any instance of Helix Native 2.80 (NOT the new Helix Native 1.81) within your DAW and click the "My Account" button :)
  5. What do you see in "I/O Setup"? Did you try to reset to "Default"?
  6. 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.
  7. 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.
  8. S/PDIF is a protocol. XLR is a connector.. You can send AES/EBU. DMX, analog audio and whatever using XLR equipped cable.
  9. https://line6.com/support/topic/47456-helix-floor-footswitch-failing/
  10. 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.
  11. 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.
  12. 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.
  13. Ouch! There is no pad in the Helix Stomp! No variable impedance neither. No info about "Line Level" impedance. :(
  14. 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.
  15. 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.
  16. 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?
  17. 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. That statement contradicts the driver description: "Helix Mac Driver 1.0.7 is a required update to support Helix Firmware 2.80 or greater."
  18. So to clarify: After instaling Core Audio high latency mutli sampling driver Class Compliant Helix usage is no longer possible. Am I right?
  19. I swear I don't know what you are talking about. :D 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.
  20. 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.
  21. 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".
×
×
  • Create New...