-
Posts
2,925 -
Joined
-
Last visited
-
Days Won
45
Everything posted by duncann
-
Sorry. My mistake. I thought you were talking about something else. Lol. But I see what you mean now, and it does look like an oversight, since the color can be changed on these two switches when in command center and editing on the device, but not by using HX Edit. I'd probably report it as a bug either by the bug thread up top, or by opening a support ticket. Edit: Oh. It looks like d0stenning just posted in the bug thread.
-
Window -> Command Center... or Control+Shift+M
-
Practice more. :) I like a nice high action, 3mm at the 12th fret, and do a lot of fast tapping. But like you say, everyone plays differently and has their own preferences, developed over time. Some people probably even have preferences they don't even know about.
-
There's several of these ideas on ideascale. On one of them, https://line6.ideascale.com/a/idea-v2/813697, Digital_Igloo commented on why no offline mode: Offline mode wasn't omitted as much as it's indicative of how Helix and the editor communicate with one another. Without the hardware, the editor has no idea what's going on—no information on models, paths, parameters, etc. Nearly all data is being sourced from the hardware in real time. To support offline mode, we'd literally have to create a duplicate Helix engine for both Mac and PC. Not impossible, but certainly a notably larger scope than any editor-related requests we've received. So I guess the answer is, as pointed out above by HonestOpinion, that there is an offline editor and it's Helix Native. I get that that's not exactly what people are wanting, but I wouldn't hold your breath for a free, standalone, offline preset viewer.
-
Sure thing: https://www.thegearpage.net/board/index.php?threads/line6-helix.1586637/page-2275#post-25296691 For anyone who can't access the link, here's the text from the post in question by SHwang_Guitars:
-
Haha. What's worse is doing that for an entire session, saving, and thinking you made significant progress, with only the remote possibility of your mistake being revealed the next day...
-
Thanks for the suggestion. I don't really have any wordclock options on any of my other equipment. Helix Floor doesn't either. Helix Rack does. Besides that, it's been sort of unofficially confirmed by one of the support staff that these dropouts are something that may be corrected by a future firmware. There should be a topic on these forums somewhere.
-
Thanks. It looks like this technology has improved somewhat since the last time I took a look at it. Expensive though.
-
I too use the Floor version. I was under the impression to reset/clear the Helix (Floor), you had to hold foot switches 9 and 10, not 5 and 6. I know holding down encoders 5 and 6 on the Rack version resets/clears. Are there two different resets for Helix Floor? Take a look here: https://helixhelp.com/reset-options/
-
Glasses have to be one of the most aggressive annoyances there is. I can't wait for the day when it's discovered how to grow eyeballs in the lab and have one's eyes transplanted. Human eyes are one of nature's malfunctions I guess.
-
There are an awful lot of frequencies between say 1100Hz and 1200Hz. Or even between 100 and 110 for some blocks. This could be very detrimental in practice. The 4 OSC Generator might be an example, as someone else mentioned. Or perhaps the AM Ring Mod. What about the wahs that have frequency adjustments? Also, it's not just the editor. Editing on the device has the same selection values. It is possible to get better resolution the way it is now, but you'd have to text edit a preset. Yuck. I did notice that dB values have increments of 0.1 between ±6dB, then 0.2 between ±20dB, then 0.5. So it's not always 0.2 as I said above. Hopefully they'll rethink this change.
-
This isn't just for the 4 OSC Generator, but probably any block that has frequency. Also, any frequency above 1000 and the increment increases to 100, which includes the 4 OSC Generator. My guess is this decision to lower the resolution was done to make twisting the encoder knobs on the device easier and more predictable.
-
Sometimes the obvious completely passes me by. I now remember I have autohotkey laying around somewhere.
-
It's actually the area where I spend the most time - the parameters area. On multiple occasions, if the selected parameter is the one at the top of the list, and I go to decrease this parameter by automatically hitting the LEFT arrow key (consistently and incorrectly thinking the LEFT arrow decreases a parameter because that's what I see should happen when I look at the screen), now the focus is on the panel to the left of the parameter panel, which I usually have showing the effect icons instead of the list, and as my thinking gets ahead of itself, I may hit the LEFT arrow again, momentarily oblivious of selecting a completely different block. The previous block is now gone, POOF!, with no way to get it back except to reload the entire preset. I've also noticed that the + and - keys on the numpad (numlock is on) don't adjust a parameter anymore. And one other thing I noticed: frequency values on EQs, cabs, etc., has increments of no less than 10 when the frequency is below 1000. Above 1000, and the increments are 100. And what worse, if you type in 1194, the frequency goes to 1100. If you type 1195, then it goes to 1200. Internally, I don't what it could be doing, but from what I see on the HX Edit interface, this seems less than ideal. dB values are another: you used to be able to input dB values in increments of 0.1. Now it's no less than 0.2. EDIT: The EQs, or blocks with frequencies, having poor resolution may be somewhat dire, because when viewing the text of a preset, the value saved is the value seen in the editor, meaning poor resolution.
-
Great improvements to the editor overall. But there is one thing that I seem unable to get used to, and that is parameter selection and adjustment using the keyboard arrow keys. Whoever thought it was a good idea to make: Left (visually Up): select parameter towards first listed Right (visually Down): select parameter towards last listed Up (visually Right): increase parameter value Down (visually Left): decrease parameter value A more intuitive layout would be: Left (visually Left): decrease parameter value Right (visually Right): increase parameter value Up (visually Up): select parameter towards first listed Down (visually Down): select parameter towards last listed To make matters worse, this is the area of the editor where, for me at least, most of the time is spent. So it's a constant mental stumbling block.
-
I understand what you're saying. The hum and ripple parameters I never touch either, because any changes seem nearly imperceptible. Too many insignificant parameters can quickly clutter things up and make it overcomplicated for little to no effect. It would be useful for Line 6 to at least slightly document parameters that are named something different than on the original models so we're not poking around nearly blind. But in any case, it's still fun to just mess around with to see what everything does. The other new effect, the doubler modulation, has some parameters with not much of a clue as to what they do. But I did read a post on tgp by someone from Line 6 (not Ben Adrian) explaining this effect. Stuff like that is most helpful.
-
I think the random delay stab might be related to the splice parameter; if it's zero it might not be so prevalent? I also notice that this effect doesn't have much headroom, especially if placed after the amp. Try putting a weaker signal into it. I agree that the other parameters you mention are difficult at best to tell what they are doing. I find this effect works best with cleaner tones. And also, if you want a wide stereo field, which it lacks by itself, use two of them in parallel.
-
Works fine here. I'd maybe try doing a global reset: hold 5&6 while powering on (for the floor model).
-
Haven't tried it yet, but I suppose since this effect (the original) may be designed for a narrow field, two of them placed at the end of the chain, each on their own path and panned left and right, may produce a more stereo-like sound. Quickly tried this and it does indeed widen the stereo effect considerably, with the added benefit of an increased array of options to tweak between the two cosmos echos. Also, no need to use two stereo versions, but instead just the mono versions.
-
Listening with headphones, the stereo in the stereo version is so narrow that it may as well be called mono. It really seems like it's not performing as it should, or at least could.
-
Just a guess, but possibly a corrupt or bad preset? Assuming the backup process goes sequentially and that it stops at 30% during the preset backup, that would be around the 51st preset in the 3rd setlist, so perhaps start there.
-
Hmm. From your description, it doesn't sound like it. The Double Take has: Doubles: 1-4 Slop: 0.0-10.0 Sensitivity: 0.0-10.0 Source: mono, stereo, left, right Dry level and Wet level It can make some interesting effects. For the purposes of doubling, it doesn't sound all that different from using a dual pitch block. But the effect seems much more versatile than that because of all the parameters. Another interesting effect in the modulations is the Bleat Chop Trem. It's fun to mess with to create some funky patterns.
-
Just had the first dropout on version v2.30.
-
There is no type of spread, just a spread parameter that goes from 0 to 10.