ppoceiro

That's interesting! Time based effects start timing when you play a note and not in sync with the tempo led? Never noticed that. But did noticed that even with the led out of sync from the metronome my delays and phasers sound in sync with my playing . So I guess you're totally right! Even so... It sucks not having the led in Helix sync with the tempo. By the way did you tried send the tempo from the saw to helix through midi? I noticed my helix froze when I did that and had the tempo set by snapshot.... Cheers

I realize the limitations but if you have a song with the same tempo from beginning to end and helix reports 118bpm instead of 120 you'll have big drifts by the end. How can I reduce these drifts without making tempo changes? I tried but wasn't convinced it worked. I placed more markers in the song, in the DAW with the same tempo to check if helix received that information but couldn't be sure it was... By "most of the time the tempo is correct but not in sync" I mean that helix reports the same bpm as the DAW but with tempo LED out of sync with the metronome from the DAW and it kind of sucks because it's distracting if your playing with the metronome but keep seeing the LED out of sync. But it's not a question of turning the LED of. I know I can do that. It's more a question of can I turn of the metronome and just look at the LED and stay in time with the band?

Hi. I own Helix LT with the latest firmware. I use it with my DAW. The Helix is set to receive tempo from the DAW via midi cable connections. It works but the issue is the tempo in Helix is not in sync with the DAW. Sometimes the tempo is spot on and in sync. Most of the times the tempo is correct but not in sync. Sometimes the tempo doesn't match by 1 or 2 bpm. Does anybody use this feature and working correctly? Is there a workaround? The exact same thing happened with my POD HD500X and I never got it to work. I ended up sending MIDI CC messages of tap tempo to the pod.

Hi! Yesterday I encountered some sort of bug. I have a brand new Helix LT updated to latest 2.21 firmware. All was working great and it started to freeze. Constantly... Before I bought LT I tried Helix native and came up with a few patches. I imported them to helix LT after all the updates and resets and rebuilds were made, following the L6 instructions. I don't know if the bug has something to do with the patches made in Native. I resolved the freezes when I remembered I'd change the global setting of the tempo to be assigned by snapshot. I went back and put it in assign by preset and no more freezes. I use helix receiving MIDI tempo from my PC via audio interface and midi connections. I suspect that this midi tempo being received and the option to have the tempo being assigned by snapshot together with the "Recall settings" for snapshots enabled is causing it to freeze. Also I resolved it because I noticed some snapshots had tempo of 0 after helix froze and after I rebooted it. Anyone encontered this issue? Is it known? Should I open a ticket letting them know? I know I should try to reproduce it again before submitting the issue but if someone has encoutered this before I won't have to. Cheers

I agree with you fflbrgst. But I have to stand with L6 also. It's like silverhead said. These were very rare situations by the few complaints this post had and from I gathered L6 couldn't replicate the problem for them to fix it. And from the replies it's not necessary to install another DAW and this is not a workaround anymore. The solution/fix is to install/repair Microsoft's Visual C++ Redistributable 2013. Windows normally already has this installed but in some systems it got corrupted somehow or with some files missing. So it's not exactly L6 fault. Anyway I agree they should warn about this issue in the installation notes or even force the installation. They already submitted this issue to the development team from what the L6 support guy told me in the ticket. About the constant internet connection you are totally right! I also use Reaper exclusively and offline. Hope they find another way to authorize Native. Cheers

Glad to hear it! I'm gonna mark this as solved. Just remembered... Last week I did try this but did'nt installed the 2013 version. Tried with 2010and some other older version. Just bad luck I didn't insisted with this. By the way. Something happened to your windows firewall also? Did it started asking for permissions?

Success finally!! I can't quite understand how I solved it. I followed your suggestion. Installed Studio One. Crashed. Installed FL Studio. Crashed. Then I installed Sonar Platinum Demo. And it worked!! Perhaps it has something to do with firewall settings or Visual C++ 2013 Redistributable. I noticed Sonar was the only one to install the VCRedis 2013. Since I have windows 10 it probably didn't install. But maybe it fix some faulty module. Then I started opening other software and started receiving popups from windows firewall to authorize the connections from the software. It's like the windows firewall settings were resetted! I noticed specially because I had Reaper blocked in the firewall with rules I created and those rules where gone. I didn't even logged in in Sonar. The UI appeared. I closed Sonar. Opened Reaper. Loaded Native and immediatly the log in screen appeared. So bottom line. For those having problems you can try downloading VCRedist2013 from microsoft. I'm not sure if it this was the fix or even if it was this version that was installed so do it at your own risk. If you don't want to risk it you can't try what I did and install Sonar. Again do it at your own risk. Worked for me despite loosing some firewall configs or those having been resetted. (the firewall is working normally in case you ask) Hope it works for those having this issue. Silverhead, Thank you very much for your input. It greatly helped! Hope you received a copy of Native for free being a beta tester! If not you should have! If you want I cant refer you when I reply this solution to the support ticket I opened. Cheers

Hi! Thank you for your feedback. I'll try what you suggest. I already tried with two other VST hosts but not another DAW. It crashed with savihost and opened just a small little windows with Cantabile but no crash in this one. If I understood correctly you used the other DAW just for the first time, for the registration process and then you used Reaper all the time with no issues? Is that it? I'll give it a shot. Thank you again. I'll let you know if it works.

Still have the issues and still no response from L6. Submitted a ticket a few days ago.

S***... Then my suspicion regarding the CPU is crap. Perhaps it's some internet issues... Thanks for the info!

It's the 5.40. And yes it's 64bit. Never had any problems with similar VST's.

Ok Thanks for your input. Still waiting for feedback from L6. If you come across a solution or workaround please share. Cheers.

Hi, Are your laptops recent and do they meet the requirements? Already tried with two other vst hosts with no sucess. Starting to think it's some incompatibility between my CPU which is 8 years old, and the Helix Native vst. Submitted a ticket to L6 and waiting for response.

Hi Anyone experiencing constant crashes of Cockos Reaper when trying to load Helix Native? I tried both VST3 and VST2 and always crashes Reaper. Tried disabling windows firewall and defender with no better results.

Hi. Well I guess I didn't explain quite right. I don't send midi CC's from 2 different sources. I usually send tap tempo and patch change commands. Some are sent simultaneously for the tempo of the pod to sync with the tempo in Reaper and for the patch change to happen at beat. But both midi sends came from Reaper using the UM-One. And without the pod acting as audio interface it handles quite well the simultaneous midi CC's. Despite the tempo not always fall in line... That's another problem... Even tough the midi tap tempo sends are on beats in Reaper the Pod tempo is always different and sometimes I have 2 or 3 bpm of difference which causes it to go out of sync just after a few bars... I'll try your suggestion with a different USB cable. Thanks.

I'll give it a try. I'm using the original cable that came with the Pod. It's the only one I have with the ferrite core... And I can't recall if I did that test. I guess not. I suppose it's all ok. Only happens when using both the usb connection and the midi connection, like I said. Also yesterday I did the test using asio4all and it also cause the pod to reboot. Can it be that the pod doesn't handle well 2 midi commands being send to it at precisely the same time? But only when also using it as audio interface?

Hi! I have a small problem with my pod. It reboots itself randomly when connected to the PC via USB. I use the DAW Reaper to send midi commands to the pod like tap tempo and patch changes. I use the Roland UM-One Mk2 for this. Doing this with the USB connected from the pod and using it as audio interface makes it reboot randomly. Using just the midi connection doesn't. Using just the Pod as audio interface no problems. Only happens when the two are connected, only in Reaper and only when playing a project. It reboots in various projects and sometimes it's happens a few minutes after I start playing and sometimes just doesn't happen or takes quite a while to happen. Also when it reboots itself Windows also crashes because it loses the soundcard it's using and it doesn't like that... Drivers and firmware are up to date. Using the Pod asio drivers. Using Windows 10 but also happened with Windows 7. Any ideias and workarounds? Thanks

Hi all! I've been using the Boss FV500-H for a few months. It's not perfect but I like it. Using a TRS cable you get the proper sweep. Using a standard cable the polarity inverts. I use it with the polarity inverted and changed all my patches swapping the min and max values for the parameters I use I use in the POD. I decided to go this way because I didn't like the behaviour with the normal polarity. It had no dead zone at the heel position and a huge dead zone at the toe position. Inverted I get a small dead zone in heel and no dead zone at toe. This can be controlled using the side knob in the pedal. The sweep sounds linear to me. Not sure if it is. And its a great pedal. Built to last. It was kind of noisy when rocking it but I manage to put some small cushions in the heel so now it doesn't make any noise and at the same time I reduced the initial dead zone. If you what a good alternative, this can be it but give it a try before if you can. You may not like it. Like I said it's not perfect. Cheers

Well. Can't help you with the looper function of the pod. Don't use it. However I've already spent a lot of time searching for this and I do recall people with that exact problem. But can't say if there's a workaround. Or if my method works with the looper. What I know is the pod does receive the tempo of the DAW, with a bit of fluctuation, not the exact tempo. But if you have changes in tempo during a song, the pod doesn't keep up unless you press a footswitch. It's strange and unusable for me. So the best method for me is to send CC messages to the pod with the tempo. If you think my method could help you out I can give you some more hints with that.

You're welcome. As i understand it, at least in the pod, the time based effects reset the tempo when you press the tap tempo so each time i send a CC midi message with tap tempo to the pod the tempo of the effect resets. The problem is you cannot send too many beats or else the effect creates strange sounds. Not noticible in delays but very noticible in phasers or flangers. I only send the minimum beats for the pod to calculate the tempo. Usually 3 beats is sufficient. Its not the exact tempo but if you have many preset changes or tempo changes it's not noticible. I also send CC messages when I change presets manually for the tempo to align correctly because you may not change the preset with your foot in the exact beat. This way it's always synced.

Hi. Didn't solve the problem and found no feedback from support or forums. I have a workaround that works pretty well. Requires a bit a work. Created a tempo track for sending tap tempo through CC midi messages to the pod and created midi for every tempo change and every patch change with just 3 or 4 beats. Works great. Just be careful with patches with phaser or similar effects because every tap tempo you send resets the effect and creates strange sounds. And turn off the tempo sync from the options. Cheers.

Hi! Did you found a workaround for your tempo sync problem? I just posted a very similar post reporting the same problem. Cheers

Hi, I'm trying to sync the tempo in the POD by sending the clock from my DAW (Reaper) via midi. I have two problems. 1.The POD only syncs the tempo when I go to the midi page in the system settings or when I press a footswitch. 2.The synchronized tempo always drifts by -/+0.2bpm and takes a bit of time to sync. I tried with both global and preset options for the tempo. Is there some workaround for these problems? What I'm trying to do is to play backing tracks with tempo changes during the playback and I would like the tempo in the POD to sync with the DAW without me having to press footswitches and without any drifting. Any advice or setting i'm missing in the DAW or in the POD? Thank you