soundog

The Helix platform is a flexible and powerful MIDI device. Way more so than any guitar device I've encountered. The thing I've learned about MIDI is this: it follows rules exactly and precisely. The sending device must be set up perfectly and aligned with the receiving device, which also must be set up perfectly. There is no room for error. If there is a problem its normally because 1) you've set something up wrong, 2) you have a bad cable or connection. Oh ..... and old-school MIDI (5-pin DIN) is easier than PC USB MIDI because PCs introduce more chance of error due to drivers, USB hubs, ports, protocols, and software bugs.

Yes, its easy to do this sort of toggling between 2 blocks.

Probably best to take youse lollipop and leave.

When it comes to Hi-Z input, sometimes they are geared more for active pickups. But sometimes not. Just use the inputs that sound best to you and you'll be fine...

All the time? Even after a reboot of everything?

Are you wanting to keep your audio effects for vocals separate from your guitar effects? (Helix processes all guitar stuff and guitar looping, and VL3 for vocal stuff and vocal looping?) If so, all you need is to take your raw, unprocessed guitar signal from the Helix into the VL3 so it can detect your chords (with no effects or distortion which would confuse it). You can use a send block from the Helix, before amps and effects, out a send in the Helix into the guitar input on the VL3, and adjust levels properly. Use a separate output(s) from your Helix and VL3 into your mixer, so you have guitar and vocal channel(s). If you need to loop both guitar and vocals in synch, things get more interesting. Your loops have to be synched via MIDI clock or you'll have an audio mess. The VL3 has quantized clock synch for loops, the Helix does not. So VL3 would need to be the master, and Helix the slave. Use MIDI out from VL3 to MIDI in on Helix, and read the manuals to figure out how to synch the two via MIDI clock data. Not for the timid, but you should be able to do it. Another choice to avoid the complexity of operating two synched loopers (and tap dancing) would be to simply take guitar input from Helix and loop it in the VL3 along with your vocals. Or take vocal input from VL3 and loop it in the Helix along with your guitar. I think the looper in the VL3 is better so use that one. [UPDATE: I just reread your question, and sounds like you want to loop both guitar and vocal in the VL3. Good choice! If so, you will probably want to have two outputs from Helix into VL3; one with unprocessed guitar for the chord detection, and the other processed with effects for the loops. For unprocessed, use a Send as mentioned. For processed, you could use a send, and XLR out, or a 1/4" out (if you're using mono guitar signals to amp and VL3). Lots of ways to get the signal, but keep it simple. Wow, lots of fun with the setup you have!

sounds like you're doing things correctly. Are you sure you don't have any MIDI filters turned on in MIDI OX (other than, say, sysex or clock)? Also, I'm a Mac user so not sure how MIDI ports work on Windows, but make sure MIDI Ox is set to the correct MIDI port.

Yeah, that's a faulty unit. There should be no (or barely audible) change in noise when you turn the loop on. Refer to @codamedi's comment about returning the unit. Looks like you're in the U.S., so I'd open up a support ticket asap.

looks like send/return 1 is plugged into something?

That sux. Yeah, it would be good to pin this down. Platform? OS? DAW? WTF. Requiring an internet connection to use a plugin after its authorized is a huge no-no in plug-in land. Found a gearslutz thread where some were having this problem, but others were not .... but there was no conclusion re platform, os, or daw cause. Also found this related, older L6 forum thread that may have clues:

I almost always buy my music electronics and instruments used, though from a seller I trust (usually Craigslist, Ebay, or open box). These days most electronics stuff is solid chinese circuit board with peripheral stuff (LED display, switches, knobs, ins and outs) connected. I've never had anything major go wrong. If a wire should separate or a switch or plug go bad, I can open the thing up and fix it (I've gotten dangerous with a soldering iron). No worries about voiding the warranty cause there isn't one! Like @specracer986, I take care of my equipment, new or used. If I resell the thing, I usually recover around 80—110% of what I paid, versus 50—80% if I bought it new. That said, I have a feeling an official Line 6 repair out of warranty would be expensive and if you're overly concerned, consider buying an open box or refurb unit with full warranty.

Its been a long time since I used Cubase. But it could be a corrupt project file. Try these, perhaps: Temporarily rename your plug-in folders so no plug-ins load when you launch Cubase to see if a plug-in is the culprit. Then try to figure out which one. Try starting Cubase in Safe Start Mode, then try loading the file. Trash your Cubase preferences file.

@silverhead ... I just double checked and I can definately run HXN with no internet (on a Mac). Maybe something is amiss with some sort of authorization file. You could check with Line 6, or maybe back up your presets (if necessary), de-authorize, do a fresh reinstall, and then reauthorize. Page 5 & 6 of the Pilot's Guide covers authorizing and de-authorizing.

Yes, you need to be online when you authorize the plug-in, but after authorization you do NOT have to be online to use it. I can't remember how the demo behaves (whether the demo time-out is stored on you computer or at the Line 6 website).

Dunno. All working here, but I recall that others have encountered problems in the past. See if you can find clues on these threads:

Make sure you have a good internet connection and your Line 6 user name and password are working smoothly. HXN needs an internet connection to authorize, even for the trial. Also, Mojave is really fresh, so not sure if that could be an issue in your case and with your setup.

Also, 1) make double sure Reaper is sending the correct commands to Helix. Use something like free MIDI Monitor (Mac) or MIDI Ox (PC) via USB to see. 2) Have sufficient delay between MIDI commands so Helix has time to implement the patch change before receiving the Snapshot CC. 3) When working with MIDI, drink plenty of fluids and get sufficient rest.

...the Course tuner is great for playing out live when you have to tune FAST and close enough is good enough!

Good tip! Seeing the Scanner Vibrato reminded me of our guitar player trying to figure out how to fix his amp back in the early 70's and we were amazed that the reverb unit was a weird motorized paint can containing oily stuff and other strange parts. I just looked it up ..... wasn't familiar with the "Tel-Ray Oilcan reverb/delay". Insane:

I use HXN as a plug-in for recording, so create automation on the timeline. I record my raw/dry guitar tracks, then tweak away during mixing. But if I needed to I can also switch Snapshots "on the fly" with any of my MIDI controllers .... Logic Pro X lets you map external controller switches, knobs, or faders to plug-in parameter using what it calls "Smart Controls."

.... yeah, sounds like you got a dud, but as Phil_M sez, you might want to reconsider and get is swapped out. It really is a great pedal. Re: the power problem, sometimes that happens when using power bricks and certain pedals, I've run into the same problem with various pedals over the years, and sometimes ended up having to use the stock power supply to fix it.

Keep in mind GR5 "just works" with your controller because it was designed to work together ..... all made by Native Instruments.

Things to know that may (or maybe not!) be helpful.... Use a free software MIDI monitor to see exactly what is being sent from your controller: https://support.native-instruments.com/hc/en-us/articles/209544729-How-to-Monitor-the-Input-of-a-MIDI-Controller. Without a monitor, you're shooting in the dark. Most modern DAWs have a feature to map controller buttons and knobs to plug-in parameters. That's the key to using an external MIDI controller to control a plug-in on an audio channel in the DAW. For your DAW, read up on how to map an external MIDI controller to plug-in parameters. Google is your friend. You don't have to use a DAW. Mac and PC both have "plug-in host" software apps that will run a plug-in without all the other bells and whistles. Some good, some bad. For something like a "Snapshot foot switch" that turns on a specific Snapshot in HXN, you want the controller switch to send "momentary" data (a value when you push the button, one time), rather than "toggle." A toggle is OK if your controller uses them properly (toggles between a group of switches and lights an associated LED). You don't HAVE to use CC69 for a Snapshot command (thats specified for hardware Helix); you can use any CC# and value, or even a Note On MIDI command. Use the DAW mapping controller mapping feature to map whatever your controller sends to a HXN parameter . Use your MIDI monitor to see what your controller is sending when you press each button, and write it all down. Map a given controller button to a single HXN Snapshot Index. For example, CC10 Value 3 mapped to Snapshot 3. Or a G3 Note On mapped to Snapshot 5. Whatever... If all is working, pressing a controller button will activate the mapped HXN Snapshot.

Sounds like there's a gate in their somewhere ... either in the plug-in, or in your DAW channel. Also, in the plug-in, check your Host parameters (left-most part of the chain) and make sure the Input Gate is off.