soundog

My understanding was that you had to own the hardware for at least 6 months to qualify for the discount (and retain rights to the software). If the OP owned it for a year, he's free to sell it, and keep Native (even if he had just bought it). Of course, when you sell the Stomp, the new user will not be able to buy Native on the special pricing discount. .... it can only be applied once with a given Helix.

If that clean sound is straight through your babyface into a DAW track, yeah you got something wrong. Isolate the guitar signal first. Check the wiring. Check your cable. I'd try to isolate guitar and cable first (plug into an amp) before you start adding other pieces to the puzzle (like your interface, computer, DAW, plug-ins). If the guitar sounds bad through an amp, fix it or seek a good tech.

Therein lies the dilemma. Home recording softwares (e.g. DAWs, virtual instruments, audio plug-ins, etc) are more powerful than ever and are always evolving .... but keep requiring more powerful CPUs, graphic processors, RAM, etc. Its always just a matter of time before we have to upgrade once again.

Well, there ya go...

Useful info for Reaper users, thanks! I don't use Reaper, but FYI ... Native now supports Program Changes. In Logic, though, I have to use Native as an plug-in in an Instrument track rather than an Audio track. Then its a matter of getting audio in, and recording the audio. For Reaper, I'm not sure how that is done. Maybe this thread would be helpful for that: https://forum.cockos.com/showthread.php?t=153147

You could try the usual tricks .... like making sure nothing else is running on your Mac (even in the background ... use Activity Monitor to see). Also no bluetooth, no wi-fi. No nothin'. And make sure you aren't running up against memory constraints (also use Activity Monitor to check "memory pressure."). If none of that is helpful, it may be time for a different plug-in host, a different plug-in, or (I hope not) a different computer.

Exactly! Native has plenty of MIDI hooks, but you have to figure out how to get the MIDI to it from within your DAW. In some cases, Native needs to be placed on an "instrument" MIDI channel; in other cases it can reside on an audio channel. Another factor to determine is .... do you need real-time MIDI control, or is automated control via DAW playback OK? Line 6 should do its customers a favor and explain achieve MIDI control (including preset changes) for the major DAWs, and distinguish between real-time "live" control vs. traditional DAW project automation control. Or, they should provide a standalone app with its own MIDI setup for those who want to play Native "live."

You bet I will! I don't want a madman determining how much I have to pay for my guitar modeler!

Well, yeah .... but the driver quality is a constant; the buffer setting is a variable (you can control it and it has a direct effect on the latency). It has not been my experience (on Mac_ that its mostly about the driver quality .... maybe for Windows? On a related note, this very long (8 years running) on gearslutz contains a lot of useful info on audio interface latency, including a database of measurements and info on how to test your own. https://www.gearslutz.com/board/music-computers/618474-audio-interface-low-latency-performance-data-base.html

...another latency workaround that doesn't involve buying more hardware: 1. Bounce the song you're working on to a stereo track (a stereo export/rough mix of all tracks except the guitar you want to record. 2. Open a new project. Make two channels: #1 import the exported bounced tune; #2 a blank track with Helix Native plug-in (with software monitoring on). 3. Set your DAW buffers as low as they will go. (32? 64? try it!) 4. Record your guitar track dry (monitoring through Native). Latency shouldn't be a problem with such a light cpu load. 5. Close your temporary project, open your original project, import the new guitar track into a new channel. 6. Set your buffers (ie latency) as high as needed, and apply Native to your new dry track as needed. This sounds like a lot of steps, but it goes fast and easy when you get the hang of it, and is useful for systems that are bogging down on more complex projects.

If you own the hardware, then you can't beat the hardware/Native integration. Top notch.

I'm surprised that Native doesn't run as a standalone app. My other amp sim, S-Gear, does. As long as you own Logic, though, you might as well just launch it and use it. When you're jamming out and find a riff you love, you can just hit the record button. Another plus is that you can use some tracks for drums and bass for jamming.

Also check out other virtual amps: S-Gear (for blues, rock, traditional, indie, etc) or Neural DSP stuff for metal.

There are plenty of "plug-in hosts" that run on Mac that will allow you to run Native without a DAW. Examples are Hosting AU, GigPerformer, Soundsource, LiveProfessor. Some are free; full featured hosts for gigging are around $150. And, yeah, with Logic you can create a Project that has a channel with Native as a plug-in. Name it, save it, and it will launch quickly whenever you need it. If you want to control Helix Native with hardware (footswitches and pedals), you'll need to do some more work, and the way it is done varies between plug-in hosts.

This forum of full of other folks with the same problem. I understand companies trying to devise copy protection schemes when pirating is so common, but in this case Line 6 obviously did a bad job. So, for you #1 comment, I and many others totally agree. And, for #2, (in my experience) after you authorize the plug-in, it the darned thing stops calling home.

The MIDI capabilities of the Stomp are sadly lacking compared to all of the other Helix devices. I returned mine after I found that it didn't include the MIDI Command Center features. Update (a year later): I bought another one after Line 6 add the MIDI Command Center features upon my request. I convinced them it would be good for their profit margin. ;-)

LOL --- I was wondering this too until I tested the lollipop thing. It seems every time you use any lollipop cuss word the lollipop forum exchanges the lollipop cuss word for the lollipop lollipop word "lollipop." It lollipops me off.

Don't forget you can also use a blank preset as a header name. I put dash lines in front and behind my headers. - - - Devil Tones - - - Cauldron Pitchfork Goat Herder - - - Angel Tones - - - Halo White Wings Pearly Gate Its a handy method for making small groups and easy to create, organize and read using the Helix Editor. MIDI is the fastest and easiest way to find to a tone....push a button and go straight to it. Use an iPhone and a camera connect kit to interface it to the Helix MIDI port, and there are plenty of apps available.

That Akai will work great as a controller--- the faders, pots, and switches can send CC info, the pads can send program changes. Of course, it would be hard to use when your hands are full of guitar. I have an Akai MidiMix that I opened up and wired footswitches to; you could do the same (but need to know a little about electronics and be handy with a soldering iron, and not opposed to voiding the warranty. But even with no footswtiches, use the knobs and faders sure beat using a mouse!

Its ugly and its old, but if you can find a decent used Behringer FCB 1010 works nicely. I don't recommend it for gigging because its so honking big. And the manual is in Martian, so its best if you are MIDI-versed, or a very patient person. Plenty of online info, users, and youtube vids, though. Outside of that, there are all sorts of controllers out there, but a couple of things to keep in mind: * Newer controllers are MIDI through USB, which is perfect for computer/plug-in control use. If you get an older controller (5-pin DIN output/input) with no USB, you'll need a MIDI interface with 5-pin for your computer (or a 5-pin to USB converter cable ... but a good one, not those $5 Chinese flea-bay ones). * The FCB 1010 includes an expression pedal. Otherwise, you can shop for a MIDI footswitch and pedal separately. Figure out how many switches you need ... the price goes up as you add more. * For any controller, make sure its programmable and capable of sending CC messages. If you want to perform preset changes, make sure it will also send PC commands (preferably programmable, rather than increment/decrement). * If you're a decent hacker, there are videos on hacking cheap controllers (like Korg minikontrllers, etc). There are also plenty of MIDI "brains" or Arduino/Raspberry pi that can be wired up with foot switches and programmed to do what you want. Pretty geeky, but cheap. * A lot of MIDI controllers are way overpriced. The used market is a good way to go.

@jorge -- this is an old discussion and hypothetical question (does Helix and Native sound and behave identically), and its never resolved because of the system variables for Native (PC, audio interface, drivers, etc). plus you'll always get different opinions and arguments. [my own opinion is they sound and behave identically if the input path and A/D quality is similar and buffer setting is low.] are you trying to decide between buying one or the other? what would you use them for? that's a discussion that can be solved and put to rest...

There is some weird copy protection voodoo in the trial, which can cause problems. Make sure the demo is able to log onto your line6 account (password and user names OK), so no firewall or Little Snitch or similar that could prevent background log-ins.

I appreciate your spirit and wish you all the luck. Pack plenty of rations and wool socks.

You've shattered his dreams — he may never be the same. But he had to face the truth sometime....

There are more ways for noise to get introduced into the signal using plug-ins/DAW than using Helix hardware. On top of that (as you have discovered) you have more places where you have to make sure you're not introducing digital clipping or overloads.