codamedia

I'm going to return to this thread and agree with the OP... something is amiss, at least with mine (I'm not saying everyone). I've been so busy playing since I got my HX about 6 weeks ago I've never had a chance to really dig into to using the extra sends/returns/loops, but today I have. They are noisy and they should not be! I have never heard this type of noise from my X3, HD500, amp loops, etc... Time to troubleshoot and see what I can come up with... OK - here is what I have found... In combination with any overdrive, or dynamic (comp) block the RETURNS and LOOPS are adding noise. It doesn't matter what the order is. I use the Teemah! as example only... and I am keeping the overdrive down and volume at unity. On it's own (no return/loop engaged) it is noiseless... just great tone when I play. Turning on the return or loop does not change any volumes (no boost, no cut)... the only difference is added noise. I know LINE 6 has a sticky in these forums about some units being noisy... I suspect I may have one of those, as the OP may have as well. I'm going to log a ticket with them and see what they think.

You can get POE injectors at different voltages... I've never been able to find anything on the FBV so if you say it is only 8v, that's all I have to go on. Where did you get that data? Yes, I know it isn't ethernet as such... but ethernet cables use 4 pins for data, and the other four are usually open. POE uses those other four. When the FBV is powered from the amp does L6 approach it the same... or are they using a completely different configuration of the 8 pins? Since my stand alone devices have USB midi and this the FBV does USB midi I was hoping that might work. However, as I dig deeper I have learned that the FBV doesn't seem to be class-compliant, therefore it likely won't work :) Computers often power a USB line, stand alone devices normally don't.

Does the FBV ethernet port use the industry standards for POE (Power over Ethernet)? Can I just buy a typical "POE Injector" and use that to power the FBV Express MKII and just use it as a USB midi controller to stand alone devices?

It's really easy to over think snapshots :) I'd recommend that you open a test patch, switch to snapshot mode, and start experimenting. By default, when you first create a patch all 4 snapshot locations store the same core settings and they should all sound the same. Then in "snapshot mode" you customize each snapshot as required by turning effects on/off, adjusting parameters, etc...etc..

Before I purchased the HX Effects I read the official FAQ's on this page... which is a formal L6 statement, not user forums. https://line6.com/support/page/kb/effects-controllers/helix/hx-effects-faq-r883/ Near the bottom of those FAQ's is this Q&A.

This is exactly the behavior I was expecting... but it doesn't work with my unit. I've tried this dozens of times - exactly as you wrote. When I change presets and come back - the wrong state is shown. Even when I do get the state to work... simply saving the patch again without any changes breaks it. I'm OK with things now. I have found a way to get it to stick, and Line 6 has acknowledged there is a bug they are fixing. I appreciate you taking the time... and I'm glad to hear it seems to work with your setup. Maybe adding a third item (like yours) is the key... I never tried that, but I really don't need that either.

The footswitches are irrelevant to the effect chain, they are not tied together. Simply enter the "Signal Flow" page and move the whammy before the delay. The switch will still be assigned to the delay and the whammy still won't have a switch... exactly as you had it set to begin with.

Yes - it is quite easy to accomplish this. In the final block of your chain, insert the IR In the "signal path view" drop the IR to path B.... this should be the only item in PATH B and the "input Y" should come directly before it. If the input Y is too far to the left, highlight it and move it as needed. There is no need to EDIT the Input Y, just make sure it is located in the right place. Staying in "signal path view" scroll over to the Output Y to edit it. Adjust the pan settings for the output Y. Direct Path A to to the Left output, and Path B to the Right output. Path A (left output) will be everything except the IR Path B (right output) will be everything including the IR

Just in case anyone else encounters this problem and comes upon this thread... I have already received an update from Line 6 to the ticket I submitted a couple hours ago. It appears this is a bug they are aware of... this is the response. "Hi, I'm sorry about the trouble with your gear. This is a bug we are aware of have logged it for a fix in the next firmware update. Thanks for your patience while we work this one out. Will - Line 6 Support"

I've got it down to a point now that it is very predictable and has a relatively easy "work around" that works. You additional step of changing the overall state seems to be the key to getting around it. However, since it requires extra steps and is not intuitive I don't believe L6 intended it to work with way. I have opened a support ticket and provided them with a recipe to test... and also a recipe for the workaround. I can live with it as it is, but I hope it ends up being a confirmed bug that gets fixed in a future update. Thanks again for your help.

On further tests.... your solution does work.... sometimes :) But as soon as I save the patch again (change a parameter elsewhere) it reverts....and I have to go through these extra steps one more time to get it to stick - which doesn't always work on the first try. BUT - thank you... it does give me something to work with.

Thanks for the tip... I will try this in real time.... For the record, this is what I have been doing to this point. OK, this is a step I have never tried. Reverse of what I want, but let's see what happens. NOPE: Same results. When recalling the patch, the LED is lit up showing the state of the COMP (in this case, lit up)... I would like the patch to recall showing the state of the overdrive. (yes, the overdrive was the block showing when I saved)

Well - no luck with this at all. Now it never works as I expect... I'm not sure how I ever got it to work to begin with - LOL! To clarify.... I am combining a "Teemah" and a "Red Squeeze" on one footswitch I want the "Teemah" ON, and the "Red Squeeze" OFF when I save the patch. (loading the patch will always have the "Teemah" on) I want the LED to show the state of the "Teemah"... therefore when I recall the patch the LED should LIGHT UP. This is never happening... it always shows the state of the "Red Squeeze" which is LED off. Extras I have tried... I have reversed the order of the two effects in signal flow. I have reversed the states hoping that might help... but the LED still loads showing the "Red Squeeze" state. I have tried this on blank patches, and existing patches I have tried this on a few different footswitches I have tried this with different effects.... it always wants to default to just one of them whether that state is ON or OFF. As a final note... it's minor, just an irritation. I don't want to name the switch "Comp"... I want to name it "Overdrive"... and I want the LED to come on when the overdrive is ON. But it is not working... Any further suggestions?

I can't assume anything - LOL After saving the patch, are you sending it to the HD? I ask because it's not enough to just save it in Edit alone. If you are, then this could be another EDIT bug.... it has a few. Try making the change on the HD500 itself and saving it.... does that solve the problem?

I hope this doesn't get me banned... but I'd like to try and politely point out that most people that don't live in the USA find a comment like this very offensive, arrogant and ignorant in the purest sense of the word. It's not based on jealously, it's because they live in great countries as well :)

I'm with the others... I'd love to see a separate forum for the HX Effects. Lumping the HX Effects in with the Helix is the equivalent of lumping the M5/M9/M13 in with the POD HD... which is something they didn't do!

^^^ THIS ^^^ That will confirm whether it is the HELIX having a latency issue... or if it is something further down the XLR chain (mixer, effects, speakers, distance, etc... etc...) causing the problem.

This is an old thread, but since it's been re-opened I'll add my thoughts on the MIC input. For some people the HD is their primary Audio Interface for recording... having the mic input is no different than having a MIC input on any other interface. It's great for someone doing a single act. Carry the HD and a powered speaker... that's all you need. Setup a dual path (one for guitar, the other for the mic) and send them to the powered speaker... no need to carry a mixer. As a multi-instrumentalist I find it never hurts to have another input. None of my additional instruments use mics but that doesn't matter... I often plug my mandolin or dobro into a direct box, then run an XLR from the DI to the mic input.... adjust trim as needed. Added features are never a bad thing... even if you don't see the immediate value in it.

Unfortunately, there is no way to assign the MIC input to a return only. What you are looking to do can be done using dual paths but it will be MONO only (each path uses one side of left/right) and you will need to be careful not to create a loop by properly adjusting your pan controls in the HD mixer. EXAMPLE: Upper path set to guitar input.... add effects to taste, send that side to the amp/iso cab. Lower path set to mic input (adjust trim for appropriate gain) .... add processing to taste, send that side to the Board/Monitors. WARNING: The 1/4" outputs collapse to MONO if only one side is plugged in. If you are sending to Board/Monitors via XLR, you need to insert a dummy jack into it's 1/4" output or the mic will also get sent to the amp and the results will be a continuous feedback loop - it could hurt :)

The difference between a Floor Pod and an HD500 is that the exp pedal and toe switch are not "fixed" to anything on the HD500. You can assign these to anything you want making it extremely flexible. More options can make it more difficult to figure out at the beginning, but it is worth the effort. What you are trying to do is possible... and it does work flawlessly. Close.... very close. But why assign the WAH to a footswitch. Assign it to the TOE switch that is located under the pedal.

Sorry, I don't own a Kemper and can't give specific examples, but I'll try to help. If you are new to midi then you will want to keep this simple. You can do a lot with MIDI but my advice is to walk before you run. By default, devices will usually setup MIDI to listen on all channels (omni mode) and program changes will be on. If you hook up a midi cord from the "midi out" of the HX to "midi in" on the Kemper every time you change a patch on the HX the Kemper should follow. That is the easiest way to line things up... just store your amp presets in the corresponding patches that follow the HX. If the Kemper does not follow the HX program changes, you may have to set the midi channel. You will need to check the Kemper documentation to see if you can turn on Omni Mode.... if not, just set it to channel 1 and make sure the HX global Midi is also set to communicate on Channel 1. The HX Effects operates very similar to the Helix... so if you can find videos or topics about controlling the Kemper with the Helix most of it will apply.

If you are not, then I apologize.

Do these L6 forums have a policy about starting new accounts with new handles for the sole purpose to troll the forums? It doesn't take much effort to figure out that "northerntwang" is "ddmilne".

Can the editor do this yet for the HX Effects? I didn't think it could... Be careful with presets... they are created with different guitars, different amps, different monitoring situations, etc... etc... With past devices I have NEVER succeeded in finding something I like from someone else's preset. Even with the HX - the moment I got it home I loaded a blank patch into every location so I could start fresh :) I don't mind seeing peoples chains and settings as a guideline... but I'll use that info to build my own patches because I know "their settings" will not work with my gear! I was just looking at the settings in a text editor and see Variax settings, two DSP's, etc... etcc.... Isn't that a Helix preset? I thought the OP was asking about the HX Effects?

An FX loop with nothing connected to it should produce a dead signal (no sound) unless you set the mix control to allow the dry signal through. If you were to patch a short cable between the send and return there should be no difference in the sound when engaged. No added noise, no lost signal, etc... etc... I'm confused because this contradicts what you said earlier "I dont even have anything connected to it". That's a very logical assessment... I just want to share my past experience with loops. A loop with just a small patch cord is a very transparent cut/boost when you adjust the in/out levels... and it uses very little (pretty much zero) DSP power.