Please ensure Javascript is enabled for purposes of website accessibility Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by twpmeister

  1. thanks,twpmeister.i've checked out the link,i've read on the site that only 1 vst can be loaded with Savihost,does that mean if I download it to my amp sim,i can't include the cab impulse,which is a separate  .dll,or am I misunderstanding this.?

    You can use cab IRs directly in Native no need for more plugins

  2. thanks,twpmeister.i've checked out the link,i've read on the site that only 1 vst can be loaded with Savihost,does that mean if I download it to my amp sim,i can't include the cab impulse,which is a separate  .dll,or am I misunderstanding this.?

    Savihost is indeed simply a host to run a single plugin - which is a nice easy way to trial Native. If you actually need a DAW to record multiple tracks and use additional plugins then no it is not what you are looking for. Your original query suggested the most straightforward way of hearing Native was what you wanted, which Savihost would be perfect for.


    Edit. I've just re-read your original post 'is there a way of getting Native working as a sort of stand alone editorand Savihost is exactly what you asked for, but now you seem to want something to load several plugins????

  3. Kdog that only helps if you are using separate amp and cab blocks, from op's question I assume he's talking about a combo block. On helix edit if you selected the head of the same amp as you already had as a combo it would retain any amp settings already tweaked, you could then simply add an IR block. I haven't experimented to see if native likewise keeps the settings if you swap between combo and head.

    • Upvote 1
  4. You simply download savihost and copy the vst or dll of native to the same folder, rename savihost.exe to Helix Native (x64).exe and launch from the renamed program. Then choose devices at the top and, wave, and point the output to whatever asio drivers your soundcard/interface Are. If you need drivers asio4all are apparently very useable.

  5. Not using floor as my interface as the huge selling point of native for me was to be able to use it without needing to transport the hardware with me. The idea of keeping the meter within a certain range doesn't make sense as it would level out the variations between different guitar outputs which is NOT what we are trying to achieve. We are trying to get native to see the same input as helix not the same input from one instrument to another. Thanks for your input all the same.

  6. When creating patches in helix editor I often found it useful to copy a block from one patch and past it into another (work around for having default favourite settings in fx etc.) Unfortunately this doesn't seem to work in native (at least not in reaper). I can copy and paste within a patch but I cannot copy a block I like in one patch and paste it into another - is it just me?

  7. Automation is described a little in the manual, but I've yet to understand it well enough myself to know if I can do the simple task of using the number pad on my pc to select bypass states etc as a replacement for the hardware footswitches. Following to see if anyone shares any wisdom.

  8. Use the most recent driver for your interface- 2nd gen drivers will work and give better latency even if your solo is 1st gen. In asio settings put your buffer size as low as it will go without getting pops and clicks, this might take some trial and error. You may also find that the drivers work best at a higher sample rate, mine prefers 96khz to 44.1khz giving latency as low as 1.9ms but variable up to about 5ms

  9. There is a section in the helix native manual that explains exactly what you're asking.

    The manual has some general guidance but there is still the likelihood of the input gain being significantly different to the helix hardware. Let's put it like this - I want my strat to sound exactly the same on a patch installed to both the hardware and native. I have input pad set to off. How should the input knob in my interface (which is set to instrument but still has adjustable gain) be adjusted to ensure the model on native is seeing the same level input as the helix floor? Likewise if I use the floor input pad where do I then set my interface for that? What is the idiot proof way of doing this? To be clear we are not asking how to normalize input of different guitars we are asking how to match native input to floor input as exactly as possible


    • Upvote 2
  10. If you're still using a 32-bit operating system in 2017 you're a bad person and should feel bad... :D

    I prioritised buying an extra Helix LT before buying a new PC., because I got impatient waiting for Native Now I'm regretting that decision lol. Any UK people want a slightly used Helix LT?

  11. Total respect to D.I. for the answer above. It would be easy to jump on the Amplifire bashing bandwagon, especially coming from a representative of a competing company. I have to agree, I owned an AA prior to changing for helix lt and I honestly believe they are comparable products tonewise. Add to that the fact that andertons themselves have previously released some excellent amplifire demos then I'd say something is very off here. Whether accidental or deliberate user error this video is NOT representative of how the Amplifire sounds. For the record I still own my pod 2.0 and yes it is still usable but it IS NOT up there with Helix or Amplifire- they have evolved far more than this video suggests.

  12. Spring came and went can we please get an updated ETA which is more informative than "it's in beta" ? When will the rest of us be allowed to try/purchase this? Thanks.

  13. I just wanted to add that potential customers who are trying to decide between the Helix and the LT may find the $100 price for Native just the incentive they need to go for the Helix. They are looking at a $300 discount for the software when they buy the hardware. Similarly, hopefully those who are interested in Native may purchase the LT so they can pay $200 for it instead of $400. It seems to me that the proposed pricing for Native acts as an incentive that helps sell Helix and LT devices. As exciting as the prospect of Native may be, the Helix and its continued development, longevity, and support still remain my first priority and this pricing scheme appears as if it will help boost sales. I think everyone wins, Line6 and their customers.

    just wondered where you get the $200 figure from? I thought lt users had to stump $299 so only a $100 discount
  • Create New...