simonp54

I have mine setup so that when I plug in a cable... that is effectively the "transmitter pack"... so it replaces the feed when you plug in... but i think you can set it to "ignore" the aux in, until selected in a scene.

This seems like a good comprehensive answer, but where has this been checked against the product? or rather, where is the specification of the EXP jacks for HELIX defined? or is it in the manual we haven't seen yet... if others have had sight of this then thats fine for me...

Mounting underneath other gear, certainly isn't as recommended in the G70 manual. It could be this causing your dropout issues.

Simple query... I have two of these on my current rig and want to know if they will work correctly with HELIX RACK CONTROLLER. I did a search but couldn't find the answer easily. Thanks

Hello, I'm not sure what the conditions for my G70 loosing all it's SCENE configurations, but i has happened a number of times to me. Fortunately I only have two configured... if I had more than this it would be a major worry before a gig if it lost the config... Is this happening to other users? and if so, do you know why and what to do to stop it happening? Many thanks

Hi DI, I didn't start out to have anything like a "negative" exchange about this fantastic looking product... I have a particular viewpoint which is probably shared by a number of potential customers of "Helix". So please don't imply that I want to undermine or criticise the work that you guys have done, which I think from a product centric perspective is excellent. My original question was a fairly "minor" bug bear of mine and actually now I think about it, it is one of the reasons that I don't use my DAW to control HD PRO X, because it gets confused very quickly between device state and requests from the DAW (I'm talking during playback/take recording etc, think looped section where there is a footswitch toggle in the middle) I sincerely hope that the unit ships soon so that, we the consumers, can get a handle on what it can and can't do "out of the box"...

DI please... come on... I can't stress enough how I'm not gonna spend an additional £500 on a floorboard I already pretty much have that is gig proof... Oh and I own all the code for... and IPR etc... I don't care during a show whether it says "BOO" or "T808" or whatever... and im sure as hell not gonna be using the cap sense during a gig. I am a bit surprised you have "put down" 3rd party controllers like this...

Thanks DI, that does clear up not only the current implementation confusion but also the way you see it "if" implemented. I also note that you are talking about the "remote footswitch" being the feature being exposed, which obviously inherits some "HELIX CORE" functionality/baggage... not an FX BLOCK control... all makes sense... all fits with the product line(s)... but could be improved... ;-)

So DI this is where the confusion sets in... Is there ONE or TWO CC messages involved here? if it is ONE message then I infer the following (please correct me if i'm wrong) CC sent with 0-127 ----> HELIX interprets as TOGGLE (IF FX BLOCK is not a momentary) -----> and or HELIX interprets as OFF <=63 and ON >=64 (IF FX BLOCK is a momentary) the important thing here is that the CONTROLLER needs to be in control... AKA if it sends ON, then HELIX should make sure it is ON, if the controller sends TOGGLE then HELIX should toggle it... HELIX shouldn't impose any "rules based decision" when reacting to a MIDI message. (excepted that this creates an issue with multiple fx blocks on the same "footswitch", however can be considered ON or OFF as a group with their initial states flipped if necessary) Like i said in the ideascale... The midi implementation should be separated from the "HELIX" logic. I would have HELIX expose its "core" functions via the MIDI interface... The way the product works "out of the box" via the internal features could be different to the way it reacts with a 3rd party controller.

in that case is momentary mode implemented with a different CC number?

I have added idea to ideascale as Idea#2602 http://line6.ideascale.com/a/dtd/HELIX-MIDI-implementation/781277-23508

SO just to be sure... DI, you are saying it is currently a TOGGLE... like HD series...?

phil_m I'm not sure I understand why the implementation would be like you describe... are you saying that e.g. 1) FX BLOCK is OFF in preset saved 2) controller sends CC OFF 3) the BLOCK comes ON? doesn't seem to be very useful like that... I can see why Line6 might have compromised to this solution based on the multiple blocks being assigned to a single footswitch, but this really means its just a TOGGLE...?

so do we get an ON and an OFF message because in HD series we only got TOGGLE via MIDI

hey Phil_m... im talking about the rack unit implementation when you aren't "forced" to buy the Line 6 controller... if you are saying there is NO MIDI IMPLEMENTATION for the switching of FX BLOCKS then that is a serious mistake!!!!! i understand the floorboard wouldn't "need" this kinda feature but the RACK unit will... thoughts?

yup which kinda screams that the ON/OFF messaging should be supported... but no manual to back that up *yet* I'd be happy (ish) even if there were specific values for doing various tasks like momentary on/off (126, 127) or whatever, because I have my own custom designed floor controller. All that I do ask tho is that these features are "exposed" by the MIDI interface. I'm hopeful Line6 won't drop the ball here, with such a great unit, it should all be available via some midi messaging.

I agree... i wasn't saying there "isn't" a place for TOGGLE... just it should be complemented with ON and OFF... if you have a 3rd party controller... it doesn't tend to KNOW which block is ON or OFF at preset load time... The ability to be able to definitely say "ON" or "OFF" also opens up the ability for "scene" type functionality, where a floor controller sends multiple ONs and OFFs to make sure the rig is in the correct state... by ONLY implementing a TOGGLE... this is not possible with any degree of certainty...

Its getting close... so hoping this can be simply answered, but understand the guys are probably busy. Will Helix have MIDI support for telling an FX Block to be specifically ON. (or OFF) this is usually achieved with a CC and a VALUE. The VALUE <= 63 for OFF and >=64 for ON. this would greatly enhance the product over the current rather clumsy "TOGGLE" that the HD series has. Many thanks for a reply Simon

Having done some checks this morning I think I have answered this... 1) The "mode" (studio/direct:combo pre:combo post:stack pre:stack post) is done right at the end of the POD HD signal chain, just before being presented on the "outputs" (either the Balanced or Unbalanced) 2) In order to run BOTH a sim amp and a real amp, you need to tap off the signal for the real amp by using the FX Loop Send. (the FX loop can be placed anywhere in the chain) to get desired result. (btw NucleusX, I want to have POD HD effects before the amp so the dry out is not an option)

one amp and one FRFR

thanks. yes i have an FR speaker... basically the desire is to run two separate chains, one using a SIM and one not. But the chain with the real amp shouldn't have the Studio Direct "flavouring"... (flavoring for you USA guys...) :P Why would I need the 4cm? couldn't I just have the FX send to the AMP?

Hi, I want to run my real AMP on one feed from the HD PRO X and also I want to run a second path through an AMP SIM. Question is what settings should the "mode" be? for the AMP to be fed from the output it needs COMBO PWR or COMBO PRE, but this will screw with the AMP SIM on the other path... which should need STUDIO/DIRECT? the fundamental question is: WHERE is the "STUDIO/DIRECT : COMBO PWR : COMBO PRE mode" applied... ??? many thanks S

I have always used Line6 Monkey for my various products... i have the G70 on order... is this a different piece of software to update the G70?

Having upgraded to 2.62, my HD PRO X is now reporting a USB FW:V0.00... that seems wrong...

I saw another thread on here after posting and saw it said about it working on all the outputs I have but its interesting that others are having similar issues. I have raised a ticket Unit is a POD HD PRO X