rizzy

Yes, it's a preset for bass and includes a bass amp. Ok, that explains it. Thank you for the info, Craig.

Thanks for your reply, silverhead. Apologies for not being clear - in fact, I'm running Helix Edit 3.52, the LT runs on Firmware 3.50. Is there a 3.52 Firmware for the device ? I thought 3.50 is the latest.

Hi, not sure if this has been mentioned already somewhere. I tried to import a preset from Helix LT 3.50 into Helix Native 3.52 and Helix Native responded with 'unknow error, code [-1102] and crashed the DAW. This does not happen with Helix Native 3.51 or 3.50.

Interesting. I think Line6 should repair that for free, even if the unit is out of warranty. This issue should be treated like the broken pedal issue is (lifelong free replacement). A broken LED after such a short period of time in such an expensive unit is unacceptable.

The DI track you recorded needs to be raised by 6 dB in level to get the same results as if you were playing live into your Stomp. When you save the preset back to the Stomp and you are running that DI track through it, it still has to be risen by 6 dB. Mind you, this is valid for Cubase. Phil_m pointed out somewhere above that the reamping works just fine with standard settings in Reaper. I checked that and figured that Reaper handles audio track levels via aux differently than Cubase does. You've got to try for yourself if this problem is existing in Pro Tools - my guess would be that it is. I've contacted support regarding this issue. Their first reply was that this behaviour would be normal - to which I replied that there's no way that this level drop could be intended and that it'd be nice if the firmware would be updated accordingly. Their second reply suggested that I should set the 2nd path to no input at all, because otherwise the volume would be split. I tried that on my Helix LT but there's no volume split happening at all, no matter if the 2nd path is set to multi, guitar, USB etc. or X. So I reported that back and then the support ticket got auto closed.

Hi, unfortunately -as far as I know- it's not possible to update via MIDI. Just out oft curiosity - what happened to your USB Port ? 5 months is not long ago. Is there a possibility that there's a warranty on the repair ?

Thx for the hints about the discount on HX Native. It is possible to configure MIDI controls for automation in a DAW. Since HX Edit has all the controls preconfigured, I thought it would be easier to use those as compared to setting them up and dealing with MIDI implementation charts - especially for non experienced users. I see that this idea led to a partly heated discussion here. It's just an idea. If it doesn't make it no one will get hurt and life will go on.

Oh. I didn't even know I was allowed to vote for my own idea, thx for the hint - and for your vote of course. Guys, thx for your opinions and input.

I never said it should be free. I said I don't want to buy Helix Native as I have the hardware unit and it would be cool to automate it using a plugin dedicated to that. How you are getting to the conclusion that I think Line 6 should drop everything else and whatnot is beyond me. All good. I totally get where you guys are coming from. I just thought it would be cool to have another option on the table for the non Native users.

I don't own the Native software and would like to be able to automate things while reamping through the hardware unit using the HX Edit GUI as a Plugin. I don't want to buy HX Native and think this way would be easier than to set up dedicated MIDI controllers in a DAW. It would be like doing automation you'd do within Native but using the Hardware unit. This possibility does not exist in the suggested way right now.

Well, I thought having the HX Edit user interface as a plugin inside a DAW would make automation of the hardware unit easier - i.e. if one wants to program changes of parameters that should happen at a given point in time while reamping through the hardware unit. It would be easier that way as compared to setting up controller components inside a DAW and sending MIDI events from them, as HX Edit already comes preconfigured for that task. Think of it like doing automation inside HX Native but doing it via HX Edit using the hardware unit.

I'd love to see an additional HX edit version as a VST/AAX/AU plugin. That way parameters could be automatized within a DAW and reamping using the hardware unit would step up a few levels. line6ideascale - HX Edit as VST/AAX/AU Plugin

You might be on to something here....I was thinking that the Helix would kind of autosense which connections are made to it - but maybe it doesn't.

Hey phil, I was fiddling around with Reaper lately. I was wondering why the '6 dB problem' didn't occur to you while reamping. Reaper is unique in that it's using a one track fits all approach. All audio tracks are 2 channel tracks. In order to get a mono track being placed center, it is internally mapped onto those two tracks. Both tracks are equal in level. When routing such a track to the Helix via USB 3/4 those 2 channels are summed together which results in a level rise of 6 dB. This signal reaches the signal chain in the Helix and gets attenuated by 6 dB as I've described. So in the end the Helix output signal is equal to the live signal. This works only using Reaper and only if one doesn't change the routing settings. If the Post-pan in the routing dialogue is set to full right or full left, it will send a 'real mono' signal, meaning the level sent to the Helix will drop by 6 dB. The same happens if one's choosing USB 3 as an output - only one of those two mono tracks is sent to the Helix and the signal's level is 6 dB too low. Cubase (ProTools and Logic Pro as well IIRC) don't behaves like that. There are dedicated mono and stereo tracks. If I route a mono track to the Helix, it is that one track that goes there. If I choose USB 3/4 as an output, it gets only fed into USB 3, because it's mono. I can mimic that Reaper behaviour by routing two equal mono tracks to USB 3/4, but then again I could simply raise the gain by 6 dB which results in the same outcome. I hope this makes sense and is somewhat understandable.

I let my DAW compare the RMS values of the recorded tracks (live track through the Helix and DI track via USB through the Helix), that gives me an indication of the ballpark the tracks are at levelwise. If necessary for getting the exact value, I then try to null the tracks - flipping the phase on one of them and panning them center (using just one track if they are stereo tracks as this only works in mono). I raise or lower the level of one of the tracks, if the level of both get into the area of being equal, the two tracks cancel each other out almost completely. In order to make that work, the tracks have to start at the exact same point in time. During my testing I found out that the Helix ASIO USB driver, which is only relevant for Windows user, doesn't report the correct latency to the host (DAW). That resulted in a negative 1.9 ms latency for the reamped track compared to the live recorded track at a sample rate of 48 kHz. Very interesting that you have to lower the level at the Native's input by 6 dB. That is very interesting as well. I'm using Cubase. What I found baffling is that when I don't put any effects in a chain on my Helix LT - just in > out - there doesn't happen any attenuation to the level of a DI signal that is fed into it via USB channel 3. As soon as I put a preset in there or build some signal chain, the 6 dB drop happens. For me, this behaviour ruled out that Cubase has something to do with it.