Jump to content

soundog

Members
  • Posts

    1,982
  • Joined

  • Last visited

  • Days Won

    58

Community Answers

  1. soundog's post in Latency when connecting Helix to Mac with USB... was marked as the answer   
    Latency mainly comes from the software (GarageBand) processing the audio. By the time its done, you hear a delay when monitoring through the software. Its not a bug in the Mac or software, just the way DAWs and audio software work. You can usually reduce the latency in the software: here's an article on GarageBand: https://ourpastimes.com/how-to-adjust-latency-in-garageband-12594258.html
     
    Since you have the Helix hardware, its always best to monitor through the hardware (zero latency), and record either the processed guitar or raw guitar to process later. Or both! The Helix manual explains this pretty well (USB recording).
  2. soundog's post in Pan the Mono Guitar/Amp? was marked as the answer   
    Doh! .... just found the ticket (a Pan block) under Stereo blocks for Volume/Pan. Works as it should.
  3. soundog's post in Helix Native : insert ir's plugin between path 1 and path 2. Possible? was marked as the answer   
    @MrViv: FYI, there is a separate Helix Native forum. But since you asked here, @bsd512 is correct that you could use 2 instances. It could be done with a single instance if Helix Native supported digital Send and Return blocks (similar to the hardware units, but for allowing signal routing in and out of Helix Native to external effects plug-ins, without requiring two instances of the plugin). There are plenty of free IR-hosting plug-ins that you could route your Helix Native signal to. If you like, you can vote for the Send/Return feature in IdeaScale:
     
    Here's the link https://line6.ideasc.../idea-v2/915257
    and here's the Idea Scale submission:
    It would be useful to have a "send" block to route the digital signal out of Helix, where the user could then route through external DAW plugins, and then back into a Helix "return" block. This would be similar to using Sends and Returns in the hardware unit to use external pedals.
    Example: Track 1 Helix Native (amp + cabinet) ---> virtual Out Port 1 ---> Track 2 other plug-ins ---> virtual Out Port 2 ---> back into Track 1 Helix Native (after the amp + cabinet blocks) --> final Out User could, for example, use a third-party IR loader that access a larger library of IR files, without having to load them into Helix Native. Or, user could use favorite high end compressor EQ, or effects plug-ins within the Native Helix chain (rather than being restricted to before or after Helix Native).
  4. soundog's post in Using Helix with Helix Native was marked as the answer   
    Latency can certainly be an issue when tracking guitar through Native only. It depends on your processing power, your DAW, and the tracks you are playing while recording. A hardware Helix + Native is the best total solution — so you can monitor your tracks with zero latency and full FX/amp + IR, etc. Nothing gets in the way (other than more hardware and wires to deal with).
     
    I usually record in Logic Pro X at 88.2/24, so if I get too many tracks +  intensive virtual instruments running I can't run Logic tight enough to get <10 ms latency, which is a no-go for me when tracking precise guitar parts. So...if I run into that barrier, I bounce the project with no guitar parts down to a stereo file, then bring that into a project with Helix Native, running the smallest buffer possible, and record the guitar tracks for use in the main project. A bit of a pain, but not insurmountable especially given the awesome tone out of Helix Native.
×
×
  • Create New...