codamedia

Here is a post I made in another thread... relevant here as well so I will just cut and paste. --------------------------------------------------------- Go to JAVA.COM and download/install the latest stable version of 32 bit JAVA When downloading Workbench from the L6 site, the older Workbench will not show as an option when you choose "Windows 10" as the OS, you need to set the OS Version to Windows 7/8. No worries, the version of workbench this search will display is the one you need for Windows 10. Install it! (Remember, you DO NOT WANT WORKBENCH HD! When installing Workbench.... uncheck the box what would install JAVA (you already have it step 1).

Other than the number of inputs/outputs no, I don't believe the USB acts much different. BUT - your Floor has "SPDIF" and you are utilizing it.... that changes things as the STOMP (and LT) do not have SPDIF. It appears you may be using a specific solution that works for you, but isn't necessarily the solution for the OP. Your workaround is very clever, but to accomplish it you need "SPDIF Out on the Helix" and "SPDIF IN on the second interface"... the OP doesn't have either luxury. If you want to experience the limits myself and rd2rk are talking about, and what the OP's problem is... try this. Disconnect your spdif In Reaper, assign Helix as the INPUTS In Reaper, assign your second interface as the OUTPUTS

On Windows... only one ASIO device can be used at a time. If you set the Helix as the Asio Device, then the DAW can use it as inputs, but it will also use it as the output. If you set another interface as the Asio Device so you can use it's output, then the DAW will only see that Devices inputs as well... not the inputs from the Helix (or HX Stomp) That is not a limitation of the Helix... that is a limitation of Windows. On a MAC you can aggregate devices and use them all.

If you are on Windows there is no way to do this. I know someone will jump in and suggest "asio4all" drivers... but that is a solution I would not use myself. I never go direct with my Helix, I always take it through my mixer and interface. I don't see it as degrading a prestine signal, if it is changing the signal it's what I am hearing so I would never know :)

This problem is not normal.... The Helix does not distinguish between what is plugged in, it simply treats the signal it is sent. The signal from the Bass is obviously lower than the guitar.... apparently much lower. Make sure you test everything equally. Use the same input for both the guitar and bass... Use the same cable for both (eg: unplug one to plug in the other) Test "levels" with the same preset! One will certainly be louder than the other (no two guitars are the same level) but they should be within the ball park of each other. If you don't do this.... how would you know it isn't just the presets that are different levels. Compared to what? Have you plugged in another bass to see if it's the same level? Have you plugged your guitar into that bass amp to see how loud it appears? FYI: By design, the AUX input is much quieter than the guitar input is. RELATED: If you attempt a "return block" make sure the return is set to instrument level in the global settings. Please explain this one? If you hooked it up the way this sentence suggests you would blow your Helix into oblivion :) That would indicate an active bass. If there is a compressor near the front of the chain, maybe it is clamping down to hard on the signal. If wouldn't matter what you put in front of the compressor for volume, the compressor would just squash it even more.

The IR names are strictly for human understanding... The Helix (and HX Devices) only considers the IR location when loading. If you buy a preset that comes with an IR you always have two choices.... Load the IR into the exact IR location the preset is calling or Load the IR wherever you want, but change the preset to load the new IR location

If you tones are created to sound good at the FOH and in Monitors then they will work in a set of quality headphones/in-ears with no change, or very little change. IEM's should be fed from a monitor mix.... that mix should have some basic EQ on the strip. Any adjustments more than a couple DB here or there would indicate the preset is not as prepared for prime time as you think it is.

My helix goes direct.... all of the time. I hear myself through my monitor mix, and sometimes through an FRFR. I never touch the global EQ, I actually re-purposed it as a variable PAD for the XLR outputs. IME... If the stage monitors are EQ'd properly I know the Helix will sound good with no further adjustments. If they are not EQ'd properly - I'll ask for some adjustment on the channel strip. If I am using an FRFR and need anything other than flat, I'll do a small adjustment on FRFR itself. Those types of small changes can be done in the moment... even if you do use the global EQ. That tool (global EQ) isn't for tone shaping, it's a general case of "roll off a little here or there"... at most I can't see it saving more than 15 seconds in any given room. Just my 2 cents... :)

Absolutely. You will be limited to routing and DSP limits... but there are 32 blocks available. In the studio I'll create more complex paths with stereo and parallel options... I'll hit DSP limits long before I use up the blocks. My live presets however are just one long serial path that I keep in mono... I can get a lot more blocks loaded in those for quick options via snapshots & stomps.

DISCLAIMER: I do not own a stomp. I believe there are TWO Sends and TWO Returns, but they are labelled L/R instead of 1/2 like the other HX devices. I see they also label one...potentially as a AUX return. I am assuming each send and return/aux can be inserted as blocks independently. If I am wrong in this assumption then my suggestions below may not work. I also know that the L/R Sends share a single TRS output... you will need a splitter (Stereo (TRS) > 2 Mono (TS)) in order to send each send to a different direction. Now on to my suggestion :) ------------------------------------------ You say you have 3 blocks left... and that you only used 1 effects loop. That should leave one "send/return" pair available... so this is how I would approach it. This will all be done on a single path... keeping it really simple. The trick it to rid yourself of the notion that the Stomps "output" has to be used for the amp. Remember, a SEND is just another output that you can insert anywhere you need it. Insert the remaining SEND block after your last effect. SEND that signal to the amp and set the "dry thru" so no signal continues down the path toward the output. Insert the remaining RETURN block after that.... have the monitor mix fed to this return With one more spare block... optionally you could even add a reverb, EQ, or compressor after the return if you want to sweeten the monitor mix a little. The result.... the monitor mix (return 2) should be the only signal reaching the headphone output. Here's another trick you could use to make use of the last spare block mentioned in #3 above.... Move that spare block in front of the return Insert an amp block... or if you don't have the DSP power, insert a cabinet block of choice. Turn up the dry thru from your send block to allow your guitar signal to continue on to the amp sim. This will not effect the tone you send your amp, but it will give you an amp sim in the Stomp that you can BLEND with the monitor return. To adjust the amount of guitar in the headphones.... simply adjust the MIX control in the return block NOTE: This option is very handy if there isn't enough monitor mixes to allow you to get the guitar level you want/need in the monitors. You will hear the amp sim in the headphones, the FOH still gets your mice'd up amp.

No luck trying that on my end either.... I can toggle between effects... but the LED is either on or off (or on/dim depending on global settings) Are we all running a 2.8 variant of firmware? Perhaps this is something that worked on a previous version.... even if it wasn't intended?

I am pretty sure you just press the letter "d" to reset a value to it's default. There is a list of HX Edit shortcuts starting on page 28 of this HX Edit guide. https://line6.com/data/6/0a020a3f991d5a1de0bc033cb/application/pdf/HX Edit Pilot.pdf It may not be 100% accurate as it's a 2.3 guide and HX Edit is now 2.8x... but it might help a little.

What Variax model are you using? 1st Gen (300, 500, 600, 700), or 2nd Gen (JTV, Standard, etc...) I'm interested in hearing any responses... I once attempted this with my 1st gen 300 and HD500 and I encountered the same problem you are seeing. I'd be interesting in knowing if this is a 1st gen limitation, a problem that effects all Variax guitars, or if there is a work around.

This should be easy with the Helix.... I don't use Ableton to I can't help you on that end. Connect your Helix to the computer via USB Global Menu > MIDI > Midi over USB (< Make sure this is turned on) Command Center Choose EXP 1 or EXP2 whichever one you run your wah on Set the midi channel Choose the MIDI CC # that you want to transmit Now match the midi channel and CC# in your DAW to record the movement. When you are sending the messages back to the Helix.... you need to set your wah to understand the midi message from the DAW Open your patch Select the wah block Push and hold "position" Set controller to "midi cc" Set the CC number you wish to use note: be sure to double check that the Helix is listening on the correct midi channel As for the digitech bass whammy... can't help you there, but the principle should be the same.

What firmware did you have previously? Maybe it was a bug that you and your friend took advantage of :) If so, going back to the previous firmware and restoring your backup should bring it back. Of course... then you would lose the Friedman Amps. Actually... what you are describing for operation sounds like a great option. You could make a feature request at ideascale (line6.ideascale.com)

This problem is a little disturbing but I sure would like to see more details surrounding it's occurrence. It "stopped working" is pretty vague :) When this happens.... Did this occur when the Helix was hooked up to the computer? Did this occur when HX Edit was running? Did this occur when disconnected from the computer? Regarding attempts to resolve..... Has anyone attempted to reload the current firmware to see if that corrects it? Has anyone attempted to reload a previous (eg: before 2.8) firmware to see if that corrects it? Has anyone tried inserting a return block to see if the signal gets in that way? Has anyone tried inserting a really high gain noisy amp or distortion to see if any "noise" is generated at the output? Let's clarify that to avoid confusion on the forums. Line 6 is not offloading this aimlessly. You live in Canada... Yorkville is the distributor for Canada and through agreements they handle all service and warranty for Line 6 products in Canada. Their "sub contractors" are actually all Long and McQuade stores across the country. Yorkville and Long and McQuade are the same entity... so they are not exactly "sub contractors".

It is actually a very practical request... Having this ability allows you to setup paths very similar to "Aux Sends" on a mixer. Anyone with experience in mixing/engineering knows that keeping certain effects on separate sends has huge benefits. One very practical example of this is keeping a reverb and delay on separate "sends" so one is never processing the other. No need to create a new request at ideascale.... there is already one you can up vote... (adding another just dilutes the voting pool) https://line6.ideascale.com/a/dtd/Multiple-Parallel-Paths/860595-23508 ... and there are several others that suggest more advanced options in the parallel path that will virtually allow the same thing.

At the Upper Left corner of edit is "send & receive" boxes.... The patch you load or edit will be in "italic text"... Highlight that patch (click on it once), then under SEND press "selected" It will then be saved to your HD500 I hope I understood the problem. I am in Canada :)

Great tip.... I'll have to try this myself!

If you are clipping... turn down the output in Helix Native.... then google "gain staging" :)

Breath Read the Instructions... Read the instructions again... Attempt update If you run into problems... contact support WITH SPECIFICS... not just "it doesn't work" IME... those steps work nicely for almost anything that fails to work as expected, not just a Helix update!

Although I am a huge fan of FRFR I can understand those that prefer the "amp in the room" tone from a standard cab rather than FRFR. I'm not so sure the standard Powercab would give you any real benefits since you have to manually change the settings.... but the Powercab Plus (or the newer 212) has the ability to jump between several speaker simulations and full range (FRFR) from preset to preset on the Helix.... that is a huge benefit. Imagine a Marshall amp model pumping through a Celestion Greenback or Creamback... change to a VOX model and the powercab shifts to a Blue Bell... change again to a Deluxe Reverb and the powercab shifts to a Jensen. If you ever play acoustic instruments... you will love setting a patch on the Helix and having the powercab use the full range (FRFR) mode. Another benefit is that you can take a direct out from your powercab straight to the PA... no longer having the need for another live mic on the stage.

As flexible as the Helix is, sadly you have hit on the one limitation within the routing that I have also noticed. There is only one parallel split per path and the "dry through level" of one block will have an effect on the following block(s). I don't think you can do this with individual block on/off, but you can utilize snapshots to accomplish this. Stomp mode is quite limiting compared to Snapshots... that's the nature of this beast. Different options for different jobs. Within a preset.... an assignable parameter or on/off state can be controlled by "1 stomp" or by "8 snapshots". Preset: Loads the blocks with specific effects. Snapshots: Sets the parameters and on/off state of those blocks.... with very few limitations. Stomp Mode: Manual control over a limited number of on/off states or parameters.

Real amps? Not all effect loops in real amps are line level. If it isn't stated in the manual of the amp, then you need to check with the manufacturer. Helix AMP Models will have no bearing on whether or not the effects loops are instrument/line. The loops are set separately in the global settings. Regarding Instrument Level, Consumer Line Level (-10), Pro Line Level (+4) and even Mic Level. The key word is at the end.... "level"! Aside from "instrument vs line" for the Helix Loops, each also has a "send and return level" you can use to compensate for the many differences that can occur.

That is a key statement ... Can we assume you used the SAME expression pedal (with the same settings) when it didn't happen in 2.7? If so, something has changed in the firmware which might explain past threads where some people get that expression pedal to work, and others can't. Well, I don't really want to be "that guy" but someone has to - LOL! It's actually pretty complicated. Line 6 products generally want an expression pedal with a TS connection and a 10k pot, wired a certain way... although it will work (hit and miss) with a variety of others as well. There are several different ways to wire an expression pedal... that is why a company like "mission" makes them specifically for certain devices. Blindly buying an expression pedal is a crap shoot unless there is a claim that the devices are compatible. This is the wiring diagram for a Line 6 expression pedal...