ppoceiro

Hi! I too am having problems with the Glitch Delay. Couldn't quite explained it and just tought to come here check if there's any report. As always you guys are on top of things! Nice thing they acknowlodged the bug so fast. Yay L6!! Let's hope they fix it soon. Cheers!

Right. I just overlooked that the fellow user that mentioned the line 6 driver may be using helix or other L6 hardware as an audio interface... Of course the audio driver of any audio interface may cause crashes with any plugin. I just thought if he's using native he's not using helix hardware so no point checking/updating helix drivers since he's using another interface. But of course he may be using helix hardware.

Hi. Have you installed the new update 3.51. My crashes went away with this new version. No issues so far. Sorry Silverhead but why would a driver affect a VST plugin? Does the driver package include more than just a driver for the hardware?

The crashes were happening only with the VST3 version. Only with the plugin window closed. Only with 3.50, not the previous. I double checked everything. The 3.51 update fixed the problem and it is the released notes. L6 fixed it fast since I reported it very recently!

Ok. Is it an external midi footswitch sending midi to Native? Please report back if its the footswitch causing your crashes. I have an opened ticket with L6. It would be "nice" if someone else has the same problem and has pinpointed the culprit.

There are other reports of Reaper crashing with 3.50 Native. Check the dedicated Native forum. https://line6.com/support/forum/90-helix-native/ I'm having crashes in Reaper also. My Reaper crashes when playing, not when inserting Native. It crashes when Native receives midi input from another track, for snapshot changes or other parameter and only if Native window is visible. If I close the window it doesn't crash. Only happens since 3.50 update. Do you have any midi hardware connected to reaper? Or midi tracks? Is the track where you insert Native receiving any sort of midi instructions? Unrelated to midi, maybe your Windows Security is protecting the folder where the vst or the rest of native is installed. Check if the controlled access folder is activated. Or maybe get rid of any native install you have. And clean the old and new installation folders. Fresh install may solve the problem. Maybe it's a conflict with both versions installed, a VST vs VST3 conflict or some leftovers from the old version still present. Always backup first. Cheers

Hi. I'm having crashes in Reaper also. Maybe it has something to do with your crashes. My Reaper crashes when playing, not when inserting Native. It crashes when Native receives midi input from another track, for snapshot changes or other parameter and only if Native window is visible. If I close the window it doesn't crash. Only happens since 3.50 update. It seems a bit far fetched but it maybe related to your problem. Do you have any midi hardware connected to reaper? Or midi tracks? Is the track where you insert Native receiving any sort of midi instructions? Unrelated to midi, maybe your Windows Security is protecting the folder where the vst or the rest of native is installed. Check if the controlled access folder is activated. Or maybe get rid of any native install you have. And clean the installation folders. Fresh install may solve the problem. Always backup first. Cheers

Also happens in Helix Native. DAW crashes after changing delay in new dual cab. Not sure if happened with mousewheel or draggin the slider. Doesn't crash when clicking or entering manually a delay time.

Maybe a bug with the send and return blocks. Or maybe it's already reported. While building a preset to work with guitar, mic and IEM, I added send blocks for the gtr and mic outputs to connect to FOH. And I also build a separate path for IEM using the input return 1/2. As per viewing an excellent video by Richie Castellano where he goes over a similar preset, I also decided using the sends instead of the 1/4" or the XLR to go to FOH for a few reasons. The bug itself happened when adding a Return 1/2 block after a Send 1 (or 2) block. Doing this I can spare the separate path for the IEM and get the same result. All was good after adding the blocks. Everything worked and had sound from all inputs. After saving, changing presets and going back to the preset it was empty and sounded like just DI. Turned off the Helix (Floor by the way, with the lastest firmware and no other bugs) and when I turned it on there it was. The preset was loaded like it was saved. Changing again presets and going back, empty again. I was able to change the preset and get the same result I wanted by adding the return 1/2 block in path 1 after another send block. All worked and cycling presets did not emptied the preset. More or less the same thing that I did in path 2 but no bug this way. I wasn't able to reproduce consistently the bug. Happened in two existing presets consistently. Happened often when building a preset from scratch. And I was trying now with my other unit, a LT, and happened again. Is this a known bug? Can any of the experts around take a look? Should I open a ticket? I'm attaching a couple of pics of the screen with a simple test I did yesterday on the Floor unit and the preset I was working now on my LT that exibit the same bug when adding the return and send blocks (in this case the mic input was replaced by Variax but the result is the same). KIM@MIC_bug.hlx

Hi! A bit off topic but related. Why my native plugin appears with its window cropped in Live? I can't resize the window, I can't resize native itself. I only get the left portion of the window so its totally unusable in live for me. Thanks.

Don't follow the light. For everybody that is reporting bugs with the tempo, don't base your argument on the tempo led. As said in other posts the led and the actual tempo run on different hardware clocks and they're like a stopped clock that's right twice a day. I don't believe this issue is something that can be fixed and I believe L6 are aware of this. Use your ears and the reported tempo in the helix for reference and not the led for your tests.

Someone correct me if I'm wrong but I think the led has always been out of sync with the tempo. I believe someone said to me about a similar issue with the midi tempo receive that the led and the tempo itself work in different clocks in the Helix so they will always be desynced. You have to trust your ears. In my tests way before this tempo bug in 2.90 my delays and modulation were synced either with midi received tempo or tap tempo but the led never was.

Hi people! So there's a bug with the tap tempo and delays in the 2.90 update. And probably a few others. That's quite unfortunate of course but it's L6! They are aware of it. They are fixing it as fast as they can and given the current conditions we are all in I think they deserve some appreciation on their hard work. Yes in normal conditions it's that kind of bug that affects many users but I'm very happy they could release this update with very nice implementations and new effects and a new amp for me to play with in these difficult times. I don't bother if this or other bug somehow slipped through the beta testing. My Helix didn't blow up so all is fine! And by the way this update was one of the smoothest so far for me. So thank you L6 and all the beta testers for your work and stay safe! You deserve some love from all of us!! And stay safe everybody. Go ahead and obsess with the new meters! Cheers

You can create a preset in such a way that you can have one output to XLR and another to 1/4" output and insert a volume pedal block in this parallel path. In the global settings you can make the XLR outputs not affected by the main volume knob. Also in the global settings you can choose which output you want to monitor in the headphones out. You can choose the 1/4" outs here. With the volume pedal assigned to the 1/4" out path you will control the headphones volume and not the XLR outs volume.

Reaper 6.0 is quite new. I already updated mine. If you want to try my method with reaper sending midi data to the helix, any version of reaper will do. The late ones say that have a better latency when working with midi. But I don't notice that.

Hi! I don't know about a midi controller that can do that. Probably exists. I play that song programming a midi track in Reaper and sending it to the Helix. It complicates the setup a bit but it as other benefits like playing always in time and also changing presets or snapshots automatically. Maybe there's a sequencer app for android or ios that can output CC Midi that you can connect the Helix into. That can do the job also. Cheers

I'm a big Muse fan and I tend to use the Industrial Fuzz quite a bit. Lately I setup a path with a gainy amp and a parallel path with only the Industrial Fuzz and a Hi/Low Cut block after, mixed with the other path. No amp or cab block. Love the sound! Before from my experiences with all the fuzz blocks, a very clean amp with high headroom and hi cut after worked great also except for the fuzz face. Too much gain even with the drive low.

I also use this method sometimes. If you want to save some DSP you can use only one amp and one cab and put a simple mono delay after the cab in a split path. Same settings: feedback 0%, 5 to 15ms, mix 100% and in the mixer block panned hard left and right. As said works very well with a stereo output. Be very careful when going mono because of the phase issues. Even if you're going stereo to one FRFR you will still have phase issues. If going mono just disable the delay. I tried the simple pitch with a few cents and a bit of delay and tried the double take block but ended up using my old method with just the simple delay. The simple pitch can have a few artifacts and the double tracking sounds like chorus to me and I can't get the stereo effect I get with the delay. Cheers

Hi! You can control footswitches, expression pedals, snapshots and presets via MIDI. If you intend to use the pitch shifter and harmonizer in the helix for voice I don't think you'll get good results. But never tried it. For guitar you can get good sounds with the pitch shifter if you don' go to extremes. Not convinced with the harmonizer. For your application, voice or guitar, maybe you can assign the each voice to one footswitch in momentary mode and engage the midi when you need it, through a DAW, keyboard or some other way. In the harmonizer mode as long as you pick the correct scale you shouldn't have to program anything but the sound is not as good as the pitch blocks. With the pitch shifter you would have to program the intervals via snapshots. Can't be done via MIDI. Hope it helps. Cheers.

Sorry. I did. I'll have to check for myself. Like I said it's an old issue so I'm a bit skeptical if it's really fixed. I sync the tempo in my Helix with midi so maybe it's a different kind of issue with the LED. If it is fixed that's great news and thank you Elf for your contribution! And L6!

That's an old issue. Happened also with the POD HD500. They always say the same thing. The LED runs on a different clock than the tempo so it goes out of sync. Just get used to it. The good news is, the actual tempo doesn't drift. If the LED is confusing I think you can turn it off and just use your ears. I don't think this can be fixed in future updates since they never fixed it in the PODs. We just have to hope they fix it in Helix MkII.

Hi. I also used the FV-500H for a while. After a few tests I used it with a TRS-TRS cable and inverted the polarity. Didn't had any issues with the calibration and no drops in the sweep. The pedal had a problem with the pot because the sweep was not smooth and I ended up buying the EV-30. I will try a TRS-TS cable has you suggest. The thing is, prior to the v2.81 update I didn't have any issues using the pedal with the TRS cable. Thanks for the input.

Update: There is however a bug still. The external pedal seems to loose its calibration from time to time. It's not preset dependent. Reconnecting solves it temporally. But after a while it no longer goes from 0 to 100%. It seems to go to 100% but at full sweep it backs up to 98 or 96%. For volume it's a minor problem but for whammy it is noticeable.

Hi. Did my update with some trouble from 2.70 to 2.81. Freezing half way through and Helix was not recognized anymore. After several attempts with different USB cables and different ports it was eventualy recognized and resumed update. Just a heads up. Be patient and follow the suggestions L6 posted. Try different USB cables, different USB ports, reinstall drivers. It wil work. About this bug. I always used an external exp pedal with the my LT. I use a dual exp pedal. Boss EV30 and always worked great. I always used a stereo cable despite L6 recommended TS cables because I don't have to invert polarities or mess around with the pedal settings. Did the update. The pedal worked great the first day. The second day and since then the pedal works only when I boot the Helix. After changing to any other preset it stops working. If I disconnect it the onboard pedal works. Connecting again the external it doesn't work. Reintalled the 2.81 firware, restored Helix to factory settings and the problem persisted. Tryied to change the cable to another stereo cable and problem persisted. About the fix. I tried just for the sake of it a TS cable and voilá! The pedal works again with no issues. So along the way L6 changed something in the new firmware that cause this. Don't know if they are aware but you now know. Had to invert the polarity in the pedal but no problem there. Just FYI. Some reported problems with the expression pedal but not clarifying if it's the onboard or an external pedal. I have no issues with the onboard expression pedal in 2.81. Just the external one. Also had some problems with a few presets freezing the GUI in the Helix and an error message in the HX Edit. Remade one of them. Didn't try the workaround already suggested to delete all the parameters assigned. After the firmware reinstall, complete reset and the presets rebuilt again I had no more issues with them. Hope this helps someone. Thank you for your dedication L6 guys! Loving the new amp models. Cheers!

Hi! Try repair/install Microsoft's Visual C++ Redistributable 2013. Worked for me and a few others with an older version of Native. If that doesn't solve the problem try to test Native on other DAW's. Try to uninstall and reinstall Native. Test an older version of Native.