pipelineaudio1

To be fair, some formant controls would do wonders for everyone complaining about the harmonizer (though I find the harmonizer to be fine as is)

For reaper, assuming windows: (and depends on how you want to monitor, Firehawk drivers are absolute pieces of total crap compared to POD drivers, which aren't great, but are much more functional) Install Firehawk Software Plug your Firehawk outs to your studio monitors Open REAPER, click the sample right indicator at the top right corner (might show "audio device closed" or similar instead of a sample rate, depending) Chose Audio System ASIO Chose ASIO Driver Firehawk ASIO Drivers Close preferences Right click in the left track control panel area (TCP) and chose Insert new Track (or click menu insert new track) Click the round red button (assuming stock theme) in the new track to arm the track. Don't bother turning on the monitoring icon, Firehawk drivers are total crap and won't allow you to disable direct monitoring in the hardware. Get used to the idea that you have no confidence monitoring or the ability to record the unprocessed input while monitoring the DAW's processing Hit record on the transport, upload your hit song to Distrokid and be the envy of your peers

That is some awesome sweat equity! I love apples to apples testing seriously

In REAPER either go to options/preferences/audio/device or click the sample rate indicator on the top right hand corner of the reaper screen For Audio System, chose ASIO For ASIO Driver, chose the firehawk one Click ASIO COnfiguration and you will see some other options. Don't set the sample rate here (usually). Set the sample rate in Project Settings, but DO set it

Power really hasn't been the issue since the i-series intels. Helix native optimization on the other hand :( You're looking at around 60 samples just by running one instance in series from that particular plug

Sounds like something else (possibly your metronome app) is grabbing the sample rate and changing it. What DAW are you recording in and if you are on windows, are you using the ASIO drivers? Be aware that the Firehawk drivers are absolutely pathetic both in speed and functionality compared to even the decades old POD drivers, so you will likely have to rely on direct monitoring while playing your guitar to stay sane, and that means turning off input monitoring on the track you are currently recording to (output monitoring should be fine)

And then some! So crazy many levels of functionality difference there. Forget any sound differences, though the HD500 does have workarounds for some of the extreme basics that many other Line 6 devices can't handle, such as the proper dual output path for guitar amp vs PA system simultaneously, the Helix covers this by design

Did you try enabling multicore for live in preferences? I'd be really interested in how you are making your setup portable. I'm working with several manufacturers about case mounting, pedalboard (with a carry bag) mounting, and tentatively, with a mini/micro/nuc type thing inside a pedalboard with a 5" monitor I'm really appreciating any ideas people have for this side of it Let me look into why the Helix Native is making so much trouble for you

In the case Of some motus and some behringer gear, though the claims were about audio, the BLA stuff actually made the gear more reliable.

I have a carvin 727 I’d offer up in a contest if anyone could reliably abx between a modded and unmoderated one at a rate greater than chance

Well, to do that you'd be changing your chosen audio device, which windows will likely do if you turn off the pod, but reaper will still be looking for your pod until you switch it...But that's a good thing not a bad one... In reality, Line 6 has given you a very workable audio interface. If you haven't got another real one, you would definitely be better off using the pod as your main interface Way way back in the REAPERMobile days, I ran around the country with a KB37 and a set of studio monitors which worked out really well as a basic studio on wheels. And an impromptu chance to record a guitar player who had only a few days to hang out from Canada...Portable and powerful (back in the Core2Duo days Ironing board? Check! Computer speakers from the motel lobby? Check Changing table? Check Recording on!

I mean if you try the same thing with the Fastrak does the same thing happen? Trying to tell if its a driver thing or a host thing. I see the tricks out there to keep it running in windows 10. If it all possible it would be good to use. The drivers are MUCH faster than the Line 6 drivers http://kailuamusicschool.com/tech/round-trip-latency-roundup/

THAT is scary. Something should most definitely show its not plugged in. Does your Maudio do the same thing?

That is a REALLY good trick! Same way we used to use a DI and a amp locked together, with only the amp signal being monitored. When it comes time to edit, the dry signal seriously looks like snare drums, really easy and simple to tell exactly what's happening when. Yet its editing the amp sound at the same time, so it all works out Turning on spectral peaks view in the newest versions of reaper makes it even easier

Ahh what a bummer, looks like the 500 driver is MASSIVELY crippled compared to the older POD XT drivers and the toneport drivers. Line6 seriously, what's with all the backwards steps? The Firehawk and Amplifi have worse drivers in every single way than the older drivers. I'm getting to the point where I am about to remove Line 6 products from my FAQ's and recommendations. raiyanhrid. OK, so as silverhead said, just make a dry patch Turn "hardware monitoring" off, all the way to the left on your "inputs and recording" tab of the line 6 driver control panel Ad a track in REAPER, arm it, set it to input 1, and turn on the monitor icon for that track. Unless Line 6 COMPLETELY blew it on this driver and actually stepped back more than a decade (which at this point, and man, I'm really, really disturbed by this, wouldn't actually surprise me), this should work out perfectly

I could tell you how you do it in reaper, with either of those drivers (and even asio4all if you wanted to hurt yourself for some strange reason)

Your reaper settings look correct, but you need to look in the settings that you get when you click that "Asio configuration" button. That's where you will set your buffer size (try to get it to 128) and your choice of inputs (if available between unprocessed and processed) and your direct monitoring if available which should be set to off, or like in the case of the xt live, all the way to the left so turned down all the way. Direct sound is going to be horrendous latency, I think 35 or 50 miliseconds. Same as WDM....sometimes WASAPI is ok, but if you have ASIO, use ASIO by all means

I made a latency chart here http://kailuamusicschool.com/tech/round-trip-latency-roundup/ You can see the pod drivers are ok-ish, though I didn't get to test the 500 specifically, the pod driver family seems pretty consistent from model to model. 13 miliseconds is the critical listening threshold, as confirmed by oodles and oodles of ABX tests, though you will hear every alleged expert and pretengineer on the forums screaming about how even 2 msec is too long (even though, given a substantial reward for guessing latency better than chance, they consistently fail that on an ABX test). The Pod drivers are a bit slower than that, but much better than the standard 20-25 miliseconds every iOS guitar app user is getting and seeming to be happy with Set it to 128, make sure monitoring in reaper is on, and if possible that direct monitoring on the 500 is off and see what happens, should be fine, and nothing to die over

inside reaper, right click the top right corner that shows sample rates. It will bring up the audio devices. Make sure its set to asio, make sure the asio driver is the line 6 one. Click "asio configuration" panel near the bottom of that window, that should bring up your line 6 asio control panel Now I'm not sure what the 500's looks like specifically, or if it is a crippled piece of crap like the Amplifi and Firehawk ones are, but most of the pod series had a few different tabs you could switch to. One would allow you to chose input type, between the effected signal or the dry input, which turned the device into an actual audio interface Some of the Pod drivers took it a step further, and mad a monitor fader so you could completely shut off the send from the devices input to the output, and let it ONLY send REAPER's output to the device's output. This way you can hear 100% exactly what's coming out of reaper, including all your plugins and whatever, and be 100% sure of what it is you are getting here's an example of using the old XT Live in a similar way

I'm wondering if the 500 allows you to ONLY output the return from REAPER the way you can in the older pod drivers and the pod xt live Also, in the older drivers and xt live, you can chose as input source "unprocessed only" in the ASIO control panel...It makes an excellent audio interface AND MIDI controller. Not sure if the 500 does that as well

No no, its terrible, please let me help you out and take it off your hands, I'll send you an amplifi 150 for it :) Might be a slight bit lava singed if this damn mountain doesn't turn off soon, but hey

Here's a test run

Now you just jinxed yourself and invoked Murphy's Law :)

There's really only one thing to turn on in this setup, the power strip. Its mostly based on some systems we have been working on for the past year, and loosely based on the REAPER Live setup used in hundreds of shows about 5 years ago, when computers were a lot less powerful. If you look, there's actually far, far, far fewer wires than the typical guitar player's setup: Guitar to interface, interface to computer, interface to speakers Most of what I expect to go wrong has to deal with the bleeding edge things we've been working on, scripts that are rather sketchy, and plugins to handle seamless switching. I have a LOT LOT LOT less software issues with this setup than with the Firehawk hardware, I can sure tell you that! Plus it switches instantly and has auto engage for the wah. Helix's snapshots really make this more easily doable. Revalver standalone's Gig Mode is even better, more secure and faster switching, but it has some lacking utilities that at the moment make Helix Native more viable. We have some insanely good scripting in a REAPER project to really make the most of this stuff, even for people not wanting to use Helix Native. With the old 1 wire iOS setup I could be up and running, and even out to the PA in less than a minute. This one is going to take longer because you will also have to run an XLR to the personal monitor speaker, and in this case, stick the computer in the tablet, that's why I'm thinking case mounted, with everything already in place and plugged in would be better

How do you have the two switches set?