-
Posts
1,703 -
Joined
-
Last visited
-
Days Won
87
Everything posted by PierM
-
@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...
-
The hardware talk is about the browse knobs (presets, blocks etc..), not the params encoders under the displays.
-
Unfortunately no answers. Ideascale still looks abandoned, pretty much like this place.
-
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... ;)
-
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...
-
And by the name, 3 times better!! (and 3 times more expensive too).
-
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.
-
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.
-
These toys are useless these days. Too much wireless pollution that only pro grade wireless stuff can probably handle. I did the same mistake, buying a G10S with the hope to solve the connections issues I was getting with the standard G10, but was pretty much the same glitchy experience, if not worse.
-
Rolling back to previous firmware seems solving the issue, so it looks indeed related to 3.5. They needs more HX Stomp beta testers lol...
-
I opened a ticket. Will keep this thread updated if there is any fix...
-
Not sure what would be the point to implement a sensitivity curve to the preset/block knob (which I believe is just a mechanical encoder) . In fact I always thought the encoders affected by the speed of rotation are just the params encoders under the display. As for the support ticket; I do always do that, but when it's about hardware behaviour the answers are always the same by protocol.. Global reset, and then ship to service. :) I will report this as possible bug tho.
-
Of course it happens even when you are editing a preset, and scrolling lateral through a path. That's bloody annoying as sometimes it skips the block you need to edit. OT; i had the chance to hold an Ampero Stomp II and I wish Line 6 would make things feeling that solid. Smooth knobs, no wobbling pots, no clicky clicky FS, no cheap feeling...
-
Actually that's a valid doubt. Mine also started this just after the 3.5 update. Meh.
-
Yep, rotary encoder misfiring. I'm getting the same problem since last week. Not much you can do, as these encoders are sealed and I wouldn't suggest to attempt a contact cleaner approach. I'm using a midi controller now to browse presets as it's skipping one every four, or five...just random.
-
Sigh. Just dropped a message to Frank L. Let's see if he's aware, or he doesn't care. XD
-
Steve Devino was one of the guys managing the ideascale, and also Product Manager at L6. ...the mystery deepens...
-
Could be the product is on its EOP ramp (which would be expected after almost 9 years), and they are just wrapping things up.