codamedia

I did miss that.... and don't agree with that comment at all. I can see where you are coming from when responding to that. I would still like to have a meter block though :)

Then I am disappointed that they were removed from the plans :) I can understand not making it part of the hardware, or "fixing a certain amount of resources" for it... but surely as a moveable block the person can decide to use or not wouldn't be hard, nor would it be detrimental to the unit. If I person fixates on meters and a poor sounding patch results from it.... that's on the user, not the tools. Fixating on a delay, or a reverb, or a distortion, or a compressor, etc... etc.. would have the same results :) @kringle... if you are recording with your Helix.... do you have a DAW at home? If so... set it up with a meter on the channel and use that for metering. I use my home studio console for the most part, but I also use a meter in the DAW now and then as well. Both work equally as well. My tones are extremely consistent regardless of what I am plugged into. Important to note: I use meters to get in the ballpark, and keep myself in the ballpark. In the end, it is your ears that do the final adjustments.

This is the political answer you create when you are called out for not having it on your device to begin with :) The single "most voted for" feature request on ideascale is meters, the 2nd is a digital clipping indicator (aka... input clipping at the AD conversion) That speaks volumes as to what the people would like to see.

Yes, those are two different scenario's.... and having it on the Helix is a third scenario. My point was not to suggest the benefit is the same in all situations, just that meters are useful in general. A closer look at the sentence I bolded. EXACTLY! The Helix itself may not clip internally, but eventually that sound will land on another device (console, FRFR, interface, amp, etc... etc....) and it is best to stay within certain thresholds when it does!

I would love to have a metering block that I could insert wherever I wanted in the chain to monitor the level, when I felt the desire to. The Helix is not the same as a "pedalboard > amp"... it is "pedalboard > amp > cab > mic > post EQ/effects". When I mix live, I monitor meters When I record, I monitor meters Why wouldn't I want to monitor what is happening in the Helix? I've never understood the denial of a good tool! Monitoring a meter does NOT MEAN I am a slave to that meter! I look at a meter like I do a speedometer in a car. Sure, I can get a good feel of what is happening without looking, but every now and then it is nice to look down and take a snapshot of reality! Sometimes I'm doing 75 when I thought I was doing 60 - 65 :) As for "use your ears". Tone and metering are not directly related. Why not both? Why deny anyone of a tool they want, especially when you are not forced to use it if you don't want to. That's like denying someone the desire for a high gain amp they want.... just because you don't have any interest.

I can see what Line 6 support has given up on you! The goal posts have once again moved in this thread. It started with 3 hours, it was altered to "30 minutes - 3 hours" and now it's 30 seconds? I am beginning to find this very unbelievable. Please post the configuration (effects on/off & snapshot settings) that can make this happen in 30 seconds? That would be a lot easier to troubleshoot than the 3 hours manifestation I have ALWAYS seen with your preset. There is an easy solution/workaround to your problem that I KNOW would work 100% based on all the tests/time I have spent with your preset over the past 2-3 days. Save your preset into a 2nd location (or more) and seamlessly switch between them every couple of songs. The problem is... I'm beginning to think you don't want a solution/workaround.

With a good set of Studio Monitors the LT will serve you well. Do you have an interface for recording. or were you planning on using the Helix? If this will be the job of the Helix keep in mind the LT has less inputs/outputs than it's bigger brother, and also does not have a MIC input. Other than that... they are virtually the same. FEATURES THE HELIX HAS OVER THE HELIX LT Only you can decide if any of these matter 2 additional sends (4 instead of 2) 2 additional returns (4 instead of 2) Scribble strips (LT compensates this with performance view) Separate headphone volume Microphone input with switchable phantom power Option of re-assigning 2 additional foot switches to stomps (10 stomp mode instead of 8) Digital I/O (spdif) 2 Expression Pedal jacks (LT has 1) External amp output (LT has to reassign EXP jack for this) CV output Sturdier construction....

When troubleshooting problems, it is important to go through the process of elimination. If you just repeat the same processes over and over you will never know what the culprit is. Do yourself a favor and don't do any copy/paste in HX Edit... do it on the unit itself and stay disconnected. If everything works on the Helix itself.... then it starts to break down when using HX Edit. BINGO.... it's a problem with HX Edit and/or a communication breakdown. But were you connected when this problem first showed up? Once HX Edit takes a dump it does so directly into the Helix because of how they sync. IMO... it is very important to take HX Edit out of the chain for a while to see how the UNIT is actually running on it's own. Like I said... I have not seen the hardware hiccup or fail on it's own, I have seen some anomalies when using HX Edit.

I find that ludicrous... I'm sorry! As I stated earlier... thousands of these machines are used every day on stages and in studio's around the world.... that would not be the case if they were as unstable as you seem to think they are. YOUR PROBLEM rears it's head over a long period of time.... up to three hours. The solution is to reload the patch that takes 1 second at most. If you can't work around that, then I suspect you will not get along with any piece of computerized gear... Using those presets from scratch it is running 100% in my Helix native without an issue - about 6 hours and counting now. The patch you shared failed after 3 hours consistently.

If you restart the unit without being connected to HX Edit... what do the set lists look like on the UNIT itself? I ask this because HX Edit is just another interface in the chain...and is subject to USB port communication errors! It is IRRELEVANT to the unit itself other than being a fancy interface.

I had some down hours with my gear... and although I consider this minor, I do think it's a bug. Some day this bug might effect me and others! Therefore I try to lend a hand in helping to isolate the problem. That's how this community works and I am very sorry to hear that you want to give up! Let me keep trying! How were your editing your preset that Line 6 sent you? On the unit In Helix Native Through HX Edit IME: Whenever I encounter odd behavior with presets/snaps/settings it is when I edit with HX Edit. However, I am well aware that HX Edit is nothing more than an interface for the unit, and it is dependent on a solid USB connection and subject to communications errors. Whenever I do my editing in Native... or on the unit itself - I have never had an issue.

One final update from my tests over the past couple days.... My own patch... which is more complex yet built in a similar manner to yours did not fail after 11 hours of operation. I then built your patch from the images you posted.... I didn't tweak every single setting exact, but I was careful to insert every single block in it's correct place with the correct effect/amp/split, and with the correct orientation (mono, stereo, legacy). Then made sure all effects were on that were on in the preset you shared. After 10 hours, that preset is still operation fine! At this point... I am suspecting a corrupt preset. although It's mild if it is just losing volume in a three hour window rather than freezing the unit like some corrupt presets can do. That's not a fair statement. There are thousands of these units on stages and in studios. Just a couple examples... they are on the Vegas Strip with Shania Twain, arena's and concert halls with the Doobie Brothers and in studio sessions from LA to New York including stops in Nashville. Do you really think these players would use it if it wasn't stable? It's a computer! They way you use it seems to be triggering something unforeseen. There is no question you have found a bug... whether it's in the software itself - or in a method of turning a preset corrupt. However - This is not a widespread problem, and when it happens it is extremely easy to remedy (reload the preset). It's an annoyance, just like Pro Tools is (or any other DAW) when it decides to crap the bed in the middle of a session, just like an amp is when it decides to go "poof" mid song, just like your smart phone is when it decides to drop a call or lose wifi, etc... etc... etc... Complex gear has glitches... IMO, if you can't learn to live with the small ones then maybe complex gear is not for you!

Yes, I'm in Winnipeg.

If I had a modern (JTV or newer) Variax I would test this for you... but sadly my Variax is 1st generation so it won't respond to volume changes. Have you checked the JTV forum? Maybe it is discussed there? On a side note... what part of Canada are you located?

@ekrasts Can I ask.... how is Phil's response "not exactly what you were after"? :) it was created by Line 6 to solve the very problem you were having! Or was it just the terminology that throws you... not the function of it?

Have you made the suggestion to ideascale? https://line6.ideascale.com/ IMO the most logical change would be the MODE switch operation. Currently it only rocks between the "preset mode" (which we all know can be altered) and "Stomp Mode". It would be nice if you could change what the mode does... Preset > Stomp (as it is now) Preset > Snap Snap > Stomp (yes that is possible by setting the preset mode to 8 snaps... but comes with the drawback of no permanent view of presets) Preset > Snap > Stomp (why not the option to simply toggle between all three screens)

I never even noticed them on the front until this thread. I can't imagine having any use for them... I don't like dangling stuff outside of a case. My initial thought was pen/pencil/sharpie. But only a sharpie holds, and it's too long to be a practical storage spot for it.

Another update ..... The lower path of Path A was failing regardless of whether any effects in that lower path were on, or what splits were being used. As soon as I moved those effects to a different location, or deleted them (either option eliminated the path) the signal came back to full strength. Even when I simply tried using the split to re-route to the top path it would not bring the track to life... that lower path had to be eliminated. Of course, reloading the preset always brought it to life, but I was trying to avoid that for troubleshooting the dead preset. In all three tests I did it took more than 3 hours for this to happen. I also checked every resource I could on my system, and memory was NOT an issue, so I don't believe this is a memory leak. CPU usage also remained consistent when the problem occurred so that eliminates resources. My next test. I run a mega serial path for my live presets which utilize Path A in a similar way your preset was setup... except mine has even more added. I just loaded that up in Native to see if this problem happens with my preset. It will take several hours before I know.

UPDATE FROM MY END.... At 1.5 hours it was still working. At that point I had to go out and didn't get back for another 5-6 hours. It had dies somewhere in that time. I am running another test right now... it is currently at 1.5 hours and still going. I did make a change, but don't want to announce that until my test is complete. Memory leaks are SOFTWARE, not hardware. Since this problem occurs on both HARDWARE and NATIVE, that automatically rules out hardware as the issue.

Your right, not comparable. It is completely unreasonable to suggest Line 6 be held to the same standard as Boeing or Air Bus. I also find it is in poor taste all considering...

You never said that at first... The devil is in the details... :) For the record... I am at 35 - 40 minutes now with no signs of problems. I know that doesn't mean anything, I'm just providing an update.

I highly doubt it... Keep in mind that generic phrases and terms, even when it's a direct quote from the forum can still generate generic results. Google also does not index in real time other than for company's that pay them for that. Generally it takes 1-7 days for new items to show up on a search. You can ALWAYS search just a single site with search engines. EG: Simply add "site:<siteURL>" (site:line6.com) after the search. Then Google only returns results for the site you want searched. Here are 5 Random examples I just grabbed from this site.... Problem: sound chopping abruptly Shows up #1 in Google 2.80 Stomp Upgrade wiped out names? Shows up #1 in Google all seems fine Except all the Preset Names disappeared (random line from the headline above) Shows up #1 in Google Lots Of Niggles crept in since 2.8 Helix Floor Shows up #1 in Google Error message, Device has not been initialized properly. This does not show up on Google because it is generic and can relate to many products. However.... as mentioned it is simple to add "site:line6.com" behind the search and it immediately brings up that specific thread at #1.

EDIT TO ADD: I have a question now that I loaded this up. The majority of the effects are off on this preset you shared. Will the preset you shared FAIL in the state that you shared it... or do we have to turn certain effects on to make it fail? ------------------------- Thanks... I will load this up into Native and check in on it throughout the day. Pure speculation.... but when I saw this type of thing in Sonar several years ago it was narrowed down to a memory leak in one of the plug ins. I think this problem will turn out to be nothing more than one misbehaved effect.... that when left on for 3 hours at a time rears it's ugly head. Since most of us change presets more often than every 3 hours, we don't encounter that :) I will say that if it takes 3 hours to show up & returning to the preset solves the problem then I don't understand why you consider it "serious". I consider that type of bug an annoyance at worst. I'm not suggesting it shouldn't be fixed... but it sure would't ruin my day if I encountered it.

You have stumbled on the conspiracy. Line 6 pays Google and Microsoft (bing) millions of dollars every year to make sure nothing "bad" ever shows up in search results virtually guarantying they can see 1000 more units with the same flaw they know about but refuse to fix.

Then please share the preset, not images. I will load it up to try it once you actually share it.