PierM

It will never happen. :)

Yep seems working. 

Full backups working fine here. 

On 12/29/2022 at 4:13 PM, Aged_Cheddar said:

 

I don't do this, I was just inquiring where one would find the patch volume...I'm sure it's there, and I just over looked it.

That's a good starting point

On 12/29/2022 at 3:36 PM, Aged_Cheddar said:

... and additionally through the output block on my patch".... 

 

 

That's not a good approach. You should not use the output block level as this is a boost (post gain), which means pulling hiss from noise floor and squeezing headroom.

It's odd but not impossible. That's why you have the option to buy matched studio monitors, which means the two units are identical and produced in the same batch.

Said that, could be they got a very different use (and a different speaker breakup during the first period of life of the speakers, might be the cause of a slightly different timbre or response).

On 12/29/2022 at 1:51 PM, poppa1 said:

@PierM

 

Sorry if I sometimes don't express myself so precisely.

 

I know that the HELIX LT has no SPDIF. Therefore I wrote: Going with the HELIX - Output into an Audio Interface, which I then have to buy, and then with this AI into my PC/DAW. Too, I wanted to know, what is better: AI into PC via USB, or via SPDIF. In the last case I have to buy an AI with SPDIF and a PCIe Soundcard with SPDIF.

 

 

 

AI and soundcard are the same thing, and you cant aggregate two interface without getting terrible results, especially on a PC (also not possible with native drivers).

You just need an audio interface with better drivers. USB is fine, just try to use a port which isnt part of a chipset hub. Not mandatory, but does helps reducing potential extra calls.

**Unless you have pro grade expensive stuff in mind, an Internal PCI-e audio card is a thing from the past.

On 12/29/2022 at 12:25 PM, poppa1 said:

I think I'm beginning to understand.

 

I want to play backing tracks in the DAW and record my HELIX LT guitar sound on another track.

No re-amping, but the finished sound (with effects, etc.).

 

I would then like to listen to both tracks live.

 

I found a PCI soundcard with SPDIF, Guitar Z, Micro etc. input (ESI Maya). Would it be a solution to go with the HELIX into an AI -> via SPDIF into the sound card -> DAW -> and then also take the output of the AI?

 

Or can low latencies also be achieved with USB?

 

By the way: Thanks for the quick and great help. I'm 62 and it's my first time using a DAW.

Your Helix DOES NOT HAVE SPDIF, so you cant use that connection.

There are many variables to consider, and these are different for every single machine, so we cant tell you for sure what it will give you a solid, low latency click/pop free experience. Latency is just the relationship between buffer and sample rate (this is a simplification I know), but there are many other factor to consider, that could make a great driver unable to deliver its best performance due other system bottlenecks (DPC calls, hard pages faults, CPU spikes, I/O speeds etc...).

To make it simple, I would just buy a cheap and solid Scarlett 2i2, (using standard connections, so it's gonna be Helix(A/D/A)---->Scarlett (A/D/A). 

That said, Im sorry, but I doubt you can go under 10ms for a complete round trip with all these conversions.

Another option could be Native VST, running on that DAW, and being processed by a Scarlett 2i2. At that point you'd get pretty much the half of the round trip latency at buffer/sampling parity, because you removed the first ADA cycle from the LT.

WiFi 2.4Ghz pollution is crazy high these days. Hard to find a place with a clean channel, and consumer products like the G10 arent able to filter out interferences, so they are extremely sensible to that aspect.

G10 is 7 years old product, and when it has been released the situation was way better than today.

Also, this is even worse on those countries with edge channels restrictions.

I was a very happy customer for the G10, with 3 of these toys, but these days they are all parked in a closet because the continous drops (g10S even worse).

Helix Drivers are terrible for LIVE playing, that's all you need to know. :)

I never use them as latency is way too high, even on top performance machines. I have few other audio interfaces (MOTU, Scarlett, Behringer), and all of them outrun the Helix drivers. Scarett is the one that gives me the best buffer/latency in terms if reliability.

As for the Helix drivers, ASIO4All to the rescue. ;)

Action too low

Fret buzz/rocking frets

Pickups too close to the strings

@datacommando Ideascale seems working fine now.

Happy Christmas everybody!

EDIT; No, I was wrong. Still not working.

Tactile microswicthes soldered on a PCB are just a good way for these companies to streamline the production and cut the costs. I cant think of any benefit in terms of lifespan, or purity of the contact (these are in fact the worst in terms of electrical switch bouncing). Also, for heavy stompers, this system does transfer energy from the kick to the PCB, which isnt helping. The tap tempo issue that many are facing with these devices, is also caused by the electrical switch bouncing from these tactile swicthes.

Said that, there are good tactile swicthes and bad cheap made in china sub level, tactile swicthes. Those in the Helix are the last. I can easily prove that, so Im not just talkin out of my a++. :)

Line 6 should hire some german engineer, like from LEHLE, to learn how to design a footswitch..  Yep they cost 15$ each instead 50 cents as those used in the Helix, but I'd rather pay the extra instead being scared and worried to use it...

On 12/21/2022 at 11:46 PM, DJ5D said:

I simply cannot believe that anyone would prefer twisting a knob 10 times instead of just once. I've found this to be one of my favorite update features. 

The hardware talk is about the browse knobs (presets, blocks etc..), not the params encoders under the displays.

On 12/22/2022 at 1:27 AM, datacommando said:

Community is set to Read Only. Any update operation is not allowed.

 

Not sure if IdeaScale is working for you, but I (and others) haven’t been able to register a vote for the last couple of weeks. See above. ^^^^^ I’ve also seen a post from a guy who tried to register to post a suggestion and has had nil response for over a week. AFAIK, @PierM sent a PM to Frank asking for a status report - awaiting a reply. Yawn.

 

Not only do Line 6 staff not bother to visit here, it appears they no longer take any interest in IdeaScale. I tried to email the contact on IdeaScale and got the email bounced. When I checked his profile on LinkedIn, he ceased working for Line 6 way back in 2015.
 

Jeeziz! Maybe time to move on over to TGP full time! 
 

link:

 

Unfortunately no answers. Ideascale still looks abandoned, pretty much like this place.

On 12/21/2022 at 12:55 AM, HonestOpinion said:

 

I suppose another more remote possibility would be that different parts were used on one or more production runs and the new firmware doesn't play nice with them. Unlikely, but possible. Just seems like more units would have been impacted.

 

Not saying this has anything to do with these failures but I would not be surprised if this kind of firmware update incompatibility pops up more frequently as manufacturers seem to be more likely these days to be forced to find alternative parts to keep their production line and assembly moving.

Implementing "code side" rotation ballistics on a low resolution 24 step mechanical encoder (tons of switch bouncing), is plain nonsense. I will keep saying that. If they did it, it was a mistake. Even if seems working fine for you guys, adding a ballistic/logic code to a 24 step encoder is a terrible idea. (while it's a good move on the high res encoders under the display).

Switch bouncing is already a potential cause of misfiring in a 1:1 behaviour...add to this a ballistic code and there you have a recipe for rotary farts. :)

If you really want to do so, you should go for a different and arbitrary (no logic) solution, like pressing a button while rotating to switch from high speed to detail 1:1 speed).

You could fill an entire island with all these defective parts from L6 stuff...LOL!

Mic cable isn't a mic cable as soon as you ignore the second signal wire. It's balanced vs unbalanced. As soon as you place a mono/TS jack on both ends of that "mic" cable, that's just another (BAD) unbalanced cable, with a useless third wire (which won't help with EMIs). You typically want a balanced cable for very low level signals at low impedance, as MICs, because they will be much more sensible to EMIs and they needs that third cable for hum cancellation, and also they won't suffer long wires, so wire capacitance isn't an issue. As soon as your path is at instrument level (and high impedance), you don't need a mic cable and you should not use it. A mic cable (especially if it's a long cable) could alter the parallel wire capacitance, usually cutting on the highs - and also, as said before, acting as a EMI catcher.

Said that, if you are happy with the sounds of it, go ahead... ;)

On 12/19/2022 at 10:42 AM, matsraknerud said:

guitar -> helix -> fx loop send -> amp -> speaker output -> attenuator -> attenuator line out -> fx loop return -> 1/4 inch output -> power amp -> guitar cab. 

Please explain why you are doing such a crazy routing. I really can't get the point, apart the fact it looks like a perfect recipe for a noise/hum fest...

On 12/18/2022 at 9:22 PM, hd500xguy said:

Axefx 3 is better.

And by the name, 3 times better!! (and 3 times more expensive too).

On 12/17/2022 at 3:06 PM, codamedia said:

I think this update has exposed encoders that are not 100% healthy.

Cheap hardware, that's it. 

Seriously, the only machine that gave me all these various "glitches" along last 10 years, is a Helix/HX. I do have racks coming from '90 with buttons and knobs still rolling without skipping a beat.

Sorry useless rant, but a bit tired of these problems.

I still dont understand the point to add the dynamic ballistic to the preset knob. Doesnt make any sense to me.

Ballistic is a great help for params encoder, like to set quickly an high value on a param that has a wide min/max range.

On 12/16/2022 at 5:01 PM, datacommando said:

 

We await a reply from Support regarding this.

Don't hold your breath. Support replied to my ticket with the usual "global reset etc etc". :)

Funny is my ticket started saying "Global reset doesn't solve"...oh well, no news.

Hi,

we are reporting similar issues with HX stomp, where that excessive speed is skipping blocks and presets when rolling. Please read the thread and open a ticket if you think it's the same issue. The more we are doing so, the better.