phil_m

If you aren't actually wanting to use it for something specific, it's probably better to leave it off. The thing is that there's all sorts of stray MIDI messages flying around when you start interconnecting stuff to a DAW. If it's off, it's just one less thing to worry about troubleshooting.

It depends on how you select the files to begin with. If you just grab them all with the mouse, they won't automatically be sorted. If you have them in the order you want on the screen you're dragging from and select the first one and then hold Shift and then select the last one, and then drag them in, they should drop in in order. That's what's worked for me, anyway.

Do you have MIDI Over USB turned on under Global Settings>MIDI/Tempo on the Helix?

I'm guessing he's talking about this thread: http://line6.com/support/topic/29965-want-a-great-strat-to-go-with-a-great-strat-sound/ It actually was deleted, but I just restored it... There's nothing objectionable in it. If one of us or someone from Line 6 deleted it, it was by accident, I'm sure. The other thing is it's always possible for the OP to delete their thread. So it's possible that he did that be accident.

The Helix can accommodate IRs with 2048 samples... One way to look at that is that at 48kHz, that an impulse of 42.7ms. That works for emulating things like miced guitar cabs because all the information we want is generally in that short burst. For convolution reverbs we want the whole reverb tail of an entire space, and that will be a lot more samples than 2048. The Logidy EPSI offers up to six seconds of convolution, so that translates to 288,000 samples at 48kHz. I don't think it's necessarily a linear relationship between DSP required to process an IR and sample length, but it would still take a lot more DSP to process a convolution reverb than what it takes to process a 2048 IR.

If you're using both processors, i.e., both path 1 and 2, you should have plenty of power to run all those things on the Helix hardware... If you're hitting the DSP limit frequently, I'd bet you're not using both processors.

You have have to treat the Variax model (and string pitches, if you want to control those per snapshot) like any other parameter you want to change with snapshots. They have to be tied to the snapshot controller. On the unit itself, just push and turn the knob under the parameter, and brackets will appear. You can now set specific values for each snapshot.

If you're monitoring through you're DAW, trying to do an effects loop like that probably won't work because you'll be experiencing two rounds of throughput latency... If you're wanting to add the effect after the fact, you can actually do it with just about any interface. You'd have to send the USB out from the PC back to the interface, then connect the 1/4" out from the interface to your effect, then go from the effect's 1/4" out back to the interface's input. Of course, if you wanted to do stereo, you'd need a 2-in/2-out interface at minimum.

Sounds like it's a loose ribbon cable connection or something like that inside the unit. But, yeah, open up a support ticket, and they'll take care of it.

Are they all blank? I've seen it quite a few times where people inadvertently get into Stomp Mode and don't have anything assigned to the footswitches, so all the scribble strips are blank. The MODE and TAP switches would still have text above them, in that case, though.

I think you're looking at the wrong way... If people sell their hardware after buying Native (technically it's supposed be at least 180 days before you sell the hardware, btw), they get to keep a fully functional copy of Native that they only paid $99 for... Seems like a good deal to me. As far the used market, I don't think Line 6 has any responsibility as to what goes on there. I guess you could make the argument that any promotion has the chance of impacting the sale price of used Helixes.

Line 6 doesn't allow gifting with Native. The license you have is permanently tied to your Line 6 account.

You wouldn't be able to control the 6505 directly from the Helix without having some sort of breakout box or cable. This thread talks about how the pinout for that 7-pin connection works: http://voodoolab.com/forum/viewtopic.php?f=9&t=4945 Even with that, the Helix would only be able to control two of those functions. The other option would be the Voodoo Lab Control Switcher: http://www.voodoolab.com/controlswitcher.htm I believe the "Multi" jack on it is compatible with these Peavey amp. With that and the Helix, you could control everything with MIDI.

Native doesn't have direct MIDI control yet, but you can still automate parameters using its automation lanes. These will show up in the DAW, and you can, in turn, set those to be controlled by the MIDI CC from the Helix's expression pedal.

What product are you trying to load tones onto?

That essentially does the same thing as what I proposed with the Send block... It's just that using the Send block solution means you don't have to give up an entire path just for the looper block.

Well the thing is the looper block will always out the dry signal coming into it, and there's no way to really control that on it's own. One thing you could do is put a Send block right before the looper block and use that 1/4" send as your "dry" output and then use the left 1/4" out as your wet output (this output would be the looper side). If you want to kill the "dry" guitar going to the looper block, you could tie the Dry Thru parameter in the Send block using an expression pedal and turn it down to the minimum when you want no dry thru going to the looper block.

What "deal" are you referring to? I mean, not trying to be too blunt, but Line 6 has never promised anything in the way of firmware updates in their marketing materials or website other than the times they've announced certain updates at NAMM or something. They generally don't give out information as far the future plans. I'm confident there's a lot coming, and I know some details of the roadmap for the platform going forward that I can't share. But it's not like Line 6 has made promises like, "there will be firmware updates every three months" or anything like that. It's true that people have a lot of expectations for these products now, and Line 6 understands that. But even if they never offered another firmware update again, they couldn't really be accused of not keeping up their end of the deal...

You don't have to do anything to the Helix. Just install the editor on your new computer, and you'll be good to go. You can create new backups with the editor on you ur new computer.

Well, perhaps there is some sort of audio difference depending on where the conversion is happening, but they are still being converted.

1024 sample IR files use less than stock cabs, but 2048 sample IR files use more DSP than the stock cabs. Also, the Helix converts all IR files to 48kHz when they're imported, so it doesn't matter if he's loading 96kHz IRs as they would be down-sampled anyway.

By "existing editor", they just mean the version of the editor that you were using before the latest firmware update. If you were running the latest firmware and editor prior to your laptop was destroyed, all you have to do is install that version on your new computer, connect the Helix to it, and back up your presets from the Helix. You'll be good to go.

Chill out, man... There are updates coming soon. And, really, one update over the course of six months is perfectly acceptable... Line 6 owes nothing to any of its customers in the way of updates regardless how much people expect them. There are a lot of things in the pipeline, but the attitude of entitlement gets old. Line 6 is never going to release source code for the Helix, so you might as well give up on that dream...

I doubt it will ever happen... The whole point of the AMPLIFi series is the wireless integration with mobile devices. If people want to edit with a PC, the Spider V offers virtually the same feature set as the AMPLIFi with both mobile (via a wired connection) and PC editing.

Try holding down footswitches 9 & 10 while starting up. That will initiate a total system reset. Some vendors install the latest firmware before shipping the Helix and forget to do this step. It can cause some weird behavior. If it still persists, I imagine it could be something hardware related.