Posts posted by gbr13697
Nothing is "dummy-proof" to a sufficiently qualified dummy!
My Dell XPS15 updated to Windows 11 a few days ago. No problem connecting to HX Edit.
I usually find that a 15mm square at each corner of a normal pedal is enough. It will lock down with a definite click, and I need to get a blade under to prise it off.
I use the expression pedal with most of my amp models as a gain control. For instance, I may have the pedal set to increase gain and treble, whilst also decreasing bass and channel volume. Today I was tinkering with an AC30, trying to solve the perennial problem of ice-pick bridge pickups on Strats and Teles. With the pedal heel-down, I increased the Tone Cut until I got acceptable tone from my bridge pick-up. I checked that I wasn't over darkening the neck pick-up, and kept adjusting the treble and cut to get a nice clean tone.
Then I put the toe-down on the pedal, and found that my gain had vanished! After a while it clicked that the Cut control is not part of the pre-amp tone stack, but operates further down the line. If you use too much cut, it also drops the signal and reduces overdrive. A bit more fiddling, and increasing the maximum gain to 10, got me a decent compromise.
Incidentally, I also found that swapping the AC30 Bluebell cab for Greenbacks or Creambacks, and using a ribbon mic further out instead of dynamic close in, also helps.
It still sometimes comes as a surprise to find that the modelling works as it should!
I never had a problem with USB connection to my Helix Floor with 2 previous laptops, but I have with a new Dell XPS15 that has only USB-C slots. This obviously means that I have to use a hub or adaptor. I have always used long cables without issue, but the cable that works fine with my older laptops would not work on the new XPS. I tried the shorter cable that I use with another Multi-FX and that failed as well, along with a couple of other cables. I dug out all my printer cables and tried them in turn. One of the 1m cables, and a 2m cable worked fine, and I then found a 5m cable that worked. A bit of cable swapping, and everything is working again with the cable lengths that I need. There does not appear to be any logic to it - around half the cables I tried worked, and the other half didn't. Length did not appear to be critical - just luck. In case it helps anyone, 2 cables that worked (including the longer one) were DTech Shielded - the outer is clear plastic and you can see the shielding through it.
30 minutes ago, CraigGT said:
What about the part about updating HX Edit?
I did the update last night. I saw the instruction saying:
How do I update to 3.10?
Any chance you've already updated HX Edit to 3.01 (released on Feb 2, 2021)? If so, just connect Helix/HX to your computer via USB and launch HX Edit. The software will walk you through the entire procedure, including updating HX Edit 3.01 to 3.10 and backing everything up to your computer.
I opened HxEdit and started the update process, and it did update the Helix firmware. I assumed it had also updated HxEdit but, when I checked this morning, HxEdit was still on 3.01. I had to download and install the 3.10 HxEdit update separately. I don't think this is working as intended, but it does explain why RChatfield1977 isn't seeing the new amp.
The method I use for "do-it-all" stomp box patches is to divide the paths almost throughout. I have a divide as the first block, so 1A and 1B flow through to 2A and 2B before merging near the end. The divide and merge blocks are set to switch on each alternate snapshot, with all through 1A and 2A on odd numberered snapshots, and all through 1B and 2B on even numbered snapshots. Then I populate each of the 2 paths with similar blocks in respective positions, e.g. FuzzFace, EP Boost, Klon, Flanger in Path A, and Muff, KWB, TS808, Tremolo in Path B.
Each pair of pedals is switched on and off by the same footswitch (marked on the scribble strip FuzzFace/Muff etc) but only the pedal that is in the active chain has any effect on the signal.
I would generally use only Snapshots 1 and 2 (Paths A and B) for humbucking pickups, giving me 2 different ranges of 8 pedals. The snapshots for 3 and 4 are identical, but I have a 5db boost at the start to equalise the volume for single-coil pickups. Snapshots 5-8 are repeats of 1-4, but all the time based delays and modulations are set for dotted 8th instead of quarter note. With one guitar, 2 snapshots are all you need to get 2 ranges of 8 pedals - 16 in all. With carefull positioning, choice of pedals, and descriptive scribble strips, you can get a reasonably user friendly pedal board with 16 effects. How you make use of the other snapshots is up to you - I use them to equalise for different guitars and to give me more options for tap tempo with time based effects. If I am using amp emulations the 2 paths merge in front of the amp and cab combination, and I might also have reverb, EQ, compression, etc in this position, effecting both chains. You obviously can't have 16 effects at the same time, but you can choose complimentary combinations. You would rarely need a compressor and a wah at the same time, or 2 fuzz types, or a flanger and tremolo together, or a Klon and a Tube Screamer together. Snapshot 1 or 2 will get you in the ballpark for a range of 8 pedals, and you only have to click up one snapshot to get another complementary selection.
Save the preset to your Templates bank, or to another safe location, as well as to your working preset bank. You can then copy the effect from the template, and paste it into a new preset.
The Heir Apparent and Tone Sovereign you mention are emulations of the AnalogMan Prince of Tone and King of Tone pedals. The King of Tone is essentially 2 Prince of Tone pedals in one box set up as a 2 stage drive. Either side can be set for Boost, Overdrive, or Distortion. There is a huge waiting list for the King of Tone, and I recently got mine after 3 years and 3 months on the waiting list (Yes - you did read that right!). I am currently using my Helix into a Katana Artist Mk11, though I also have a couple of nice valve/tube amps. Unfortunately I have a very electrically noisy house, and I just can't cope with the constant background noise from the valve amps when used in the house, particularly when using the Effects Loop and the 4 cable method which seems to make the noise 3 or 4 times worse. I had to return a PRS amp because the noise made it totally unusable - 60db! - it was fine in the shop. The Katana is quiet unless the gain is way up.
I have tried the Helix emulations against the actual pedal, putting the pedal in a loop in an otherwise empty signal chain in Path A, and 2 Heir Apparents in Path B. My King of Tone pedal is set for Overdrive into Boost, and I adjusted the settings so that I was getting 3 nice options of Boost, Overdrive, and Overdrive into Boost. I then replicated the settings onto the Heir Apparent emulations, and A/B tested each of the options just by switching between Paths. My ears are not the best, but I could not detect any appreciable difference. In fact, I frequently lost track of which path I was using. It is quite possible that there are significant differences between the real pedal and the emulations at more extreme settings, or using the Distortion setting, or into different amps. I am sure that tone freaks, or those averse to digital modelling, would only want the real thing. However, for me, the difference is too insignificant to worry about, and I would use either. I will probably use the King of Tone in a mostly analog pedalboard into my valve amps, and use the Helix into the Katana.The Helix is a perfectly reasonable alternative to a 3 year wait, or the double-the-retail prices for second hand pedals.
It will only ever be worthwhile if you have two separate poweramp/speaker systems - stereo, wet/dry, clean/dirty - whatever. Just having two amps in Helix and mixing them together into one mono sound output will never really achieve anything.
I have an Artist Mk2 and the Power Amp in works OK, but you are still working with a guitar amp speaker so it won't be FRFR. Good enough for most purposes. I tend to just put in a pre-amp block rather than an amp, cab, IR etc, on the basis that the Katana power amp and speaker will colour the sound anyway. It gives a variation of sounds, but not necessarily an accurate representation of the amp/cab modelling. I normally use the 4 cable method, and I actually can't hear much difference between the Power Amp input and the Effects Loop Return. Using the Power Amp In means that I have to unplug the Guitar In and move the Helix Out from Katana Effects Return to Power Amp In. If I leave the 4 cable method wiring as it is, I can just switch from a Helix preset with a Send/Return to one with a pre-amp, and not bother switching cable around.
Hank also used a multi-head tape echo with everything. Different delays for every song. You really need to nail down the times of each delay. On Apache there are two - one at around 450ms, followed by another at 150ms that also repeats the first. Most are set at a level that you don't really notice them, but you really do notice when they are not there!
I am also getting the "The Helix device failed to recall snapshot data properly" message occasionally. It does not always happen, and seems pretty random, but only when I am connected to Tone Studio. The message appears as an error over the Tone Studio screen. Nothing happens on the Helix itself - that just freezes. I have to reboot it to correct the problem. I It will reboot into the same preset, and I can change snapshots without any problem. Other freezes when not connected to Tone Studio may be due to the same problem, but I obviously don't see the message. It is not a frequent issue, but enough to demonstrate that there is an issue.
Using the Helix to control the Variax has always been rather unpredictable in my experience. I have this tuning as one of my custom models on the Variax. This means I can customise the body and pickups etc, and just switch tuning between Model and Standard (which is just a one click position change on the Variax Tuning knob). I also have one of the Variax custom models set to Rick Parfitt's version of Open G with both the Low E and A strings tuned to G - it saves having to avoid the low D of the normal Open G and gives a real low end thump on power chords.
17 hours ago, leebee said:
Looks like I am not the only one with this problem!!
Exactly the same but only on last 3 presets in 1 of my setlists
I have left the following comment for the YouTuber - might be useful for others (assuming it works!)
You obviously have some corrupted presets, and it is hard to tell how it might affect the setlists in which they reside. There is nothing to be gained by leaving them in place, and you need to get rid of them. My advice would be to export ONLY the presets you want to keep. Highlight them by selecting the first in a run, the hold down Shift whilst selecting the last. Then click on Export at the top of the setlist, and save them in a safe place with a filename that will identify them. Repeat the process for other blocks of presets that you want to keep in that setlist, and for other setlists. Make sure you exclude any of the corrupted presets and, to be on the safe side, exclude blank "New Presets". Once you are confident that you have everything you need backed up, install the new 2.8 Factory Presets and Templates. This will overwrite everything, and Helix will Rebuild all presets when it restarts. You can then Import all your saved presets into setlists and positions where you want them, and re-evaluate whether there are still any problems with your Helix.
2 hours ago, cruisinon2 said:
Interesting analysis... but whatever it is, I don't think it's either the old factory presets or templates themselves that are causing the problem. I don't even remember what firmware version I had when I first got my Helix, but I've still got whatever presets and templates came with it. Never touched any of them, and never bothered to load the new ones, with any of the updates I've done...so the ones I've got are well over 2 years old. I have had the occasional corrupted patch that just stopped working properly, for whatever reason... I'm guessing that's what happened in your case. You probably just had a handful that went on tilt. But in my case neither 2.8 nor 2.81 had any problem rebuilding factory patches that are older than dirt.
Possibly there is something else interacting, or it was just the Factory sets that came with one particular update. They were definitely not the ones that came with 2.7, but somewhat earlier. Certainly the repeated Rebuilds on every start-up corresponded exactly with the Factory Presets and Factory Templates that were on my system, and the few presets that I had adapted from them. The rebuilds always included 0-220, 897 on, and a few others. These were all Factory Presets, Factory Templates, and user presets derived from them. Once they were gone, the problem was also gone.
I was just pleased that it was none of my own carefully constructed presets that were causing it - they were all fine.
4 hours ago, leebee said:
Thanks for all the suggestions. This is a great community. I have now gone to 2.7 [Perfect] and will again try to go to 2.81 soon. The only thing I have not tried is saving all [one by one] in the Helix after rebuild.[surfsup] But I seem to remember on one of my many upgrades to 2.81 the last 3 patches were already corrupt and by saving them it crashed the Helix. gbr13697 comments are a worry though as although I have no factory presets currently in my Helix I originally used some as starting templates. [3 years ago - 2.1] God knows which ones now.
If 2.80 or 2.81 rebuilds on every start-up, it will show the numbers of the presets it is rebuilding. They do go by pretty quickly, but they can be read. This will give an indication of which presets are causing the problem. There are 128 in each setlist, and they all go up sequentially from 0 to 127. 128 will be the first preset in the second setlist. So preset 500 would be the 116th (500-128-128-128) preset in the 4th setlist, or Preset number 115 counting from 0. I quickly found that 0-220 (Factory Presets), and another range starting 897 (Factory Templates), and a few others dotted around, were rebuilding every time I switched on. The Factory Presets and Templates were easy enough to get rid of by backing up all the setlists, installing the 2.80 presets, and then restoring my User setlists. This left just a few that were rebuilding each time. Once I deleted those the problem was resolved. These were presets I had created a long time ago, and were derived from old Factory Presets or Templates, and I no longer used them. Of course, if you have a lot of working presets derived from old Factory presets or templates, it will be rather more of a problem.
The update from 2.6 to 2.7 did not cause me any problems. This all started with 2.80. Presets created from scratch rebuild OK, and I assume Factory Presets from 2.7 and anything derived from 2.7 Factory Presets or Templates are OK or a lot more people would have problems. It is just much older Factory Presets, Factory Templates, and anything created from them, that screw up.
I had the problem of 2.80 constantly rebuilding presets on every start-up, and I have contributed to a couple of threads about constant rebuilds and corrupted presets. I isolated the problem to "old" Factory Preset and Factory Template setlists, AND any user presets that were derived from those old Factory Presets or Factory Templates. I don't know how old they were because, at some stage, I stopped installing the Factory Presets and Factory Templates with each successive update. They were certainly earlier than 2.7, and leebee implies that he was still using 2.6. Some of the presets he is using may have been created from Factory Presets or Templates earlier than that. As far as 2.80 and 2.81 are concerned, these earlier Factory Presets and Templates are corrupt, and they will not work. 2.80 and 2.81 will try (and fail) to rebuild them on every start-up.
My solution was to get rid of the "vintage" Factory Presets and Factory Templates bu overwriting them with the new 2.80 sets. I also had to delete the (thankfully few) user presets that were based on these old factory presets or templates. You can isolate the problem presets by noting which ones are rebuilt on start-up.
I got this problem after the update to 2.80 after restoring my setlists. They included some old Factory Preset and Template setlists, and some presets in my User setlists that were based on some of these old factory presets and templates. They were probably earlier than the ones that came with 2.7, but I don't know which firmware update they came with. For the last few updates I just updated the firmware and BTS, and did not bother with new factory presets.
To stop the Helix rebuilding on every switch-on I had to install the new 2.80 factory presets and templates, overwriting these old ones, and I had to delete any derivatives of these presets and templates from my own user setlists. Rebuilds then stopped. I updated to 2.81 without any problems.
It does seem that older Helix presets do cause this problem, and the same may well apply to presets imported from other Helix hardware.
Problem solved, for me at least. I weeded out the Factory Preset and Factory Template copies and derivatives from my User Setlists, and backed up all my User Setlists.
I then installed the 2.80 Factory Presets and Templates. To save some space I moved the new Templates to unused presets in Factory Preset 2 setlist. I then imported back my User Setlists, and my own Template setlist.
On restart the Helix rebuilt everything other than the new 2.80 Factory Setlists. Then on a subsequent restart - no rebuild.
It appears conclusive that the problem was caused by, presumably corrupted, Factory Setlists and anything copied or derived from them. I don't know which firmware update these Factory Setlists and Templates came with. I have had the Helix since December 2017. I probably installed new sets of Factory Setlists with some firmware updates, but skipped them later on.
In any event, I am pleased that the problem was not caused by any of my own carefully crafted presets, but by presets supplied by Line 6!
It is probably a good idea to regard installation of the 2.80 presets as preferred rather than optional, but do back up first because the 2.80 presets will wipe everything else in all setlists.
I will retain copies of the problem Factory Setlists and Factory Templates in case they are of any use in solving compatibility issues.
28 minutes ago, silverhead said:
That is not expected behaviour. These presets should not be rebuilt at every startup. I would open a support ticket.
I have opened a Support Ticket:
"Helix is rebuilding presets on every start-up. These appear to be all Factory Presets that came with a firmware update earlier than 2.80, or copies of some of these presets copied to other setlists, or modifications of Factory Presets in other setlists. On advice of Silverhead in the forum I switched on and noted rebuilt presets, and switched off without touching anything else. I have repeated this process more than 5 times with the same result. Presets 0-220, 520, 897-915 are rebuilt every time. These are all Factory Presets from earlier firmware, or derivatives from them. I have not installed the 2.80 Factory Presets. Silverhead recommended opening a Support Ticket as this is not "expected behaviour". I fully expect this problem to disappear if I install the 2.80 Factory presets or at least get rid of the old ones and any derivatives. However you may wish to revise your advice as to whether installing 2.80 presets is optional, and whether it is advisable to restore or import any presets that are based on old Factory Presets."
1 hour ago, silverhead said:
I suggest the following test for each of you:
- turn Helix on and observe the rebuild you are reporting here.
- IMMEDIATELY turn Helix off. Avoid touching anything; in particular make sure you do not edit any preset. Don't even switch to another preset.
- turn Helix on again and observe whether or not any presets are rebuilt.
--> if so, open a support ticket with Line 6. This should not be happening nad you may have one or more corrupt presets;
--> if not, then the presets are not in fact being rebuilt every time you turn Helix on. There must be something you are doing in each editing session (e.g. importing presets) that is causing a rebuild at the next startup.
I have done as Silverhead suggested.
Helix rebuilt 1-220, 520, 897, and 900-915. I repeated this 5 times with exactly the same result each time.
1-220 are the first 2 setlists - i.e.Factory Presets, which remain in situ from the last time that such presets came with a firmware update. I have not imported the new presets that came with 2.80. 897 and 900-915 are "selections" from the Factory Presets that I copied to a "User Template" setlist as I thought I might use elements from them at some time. I'm not too sure about 520, but it is possible that it started out as a Factory Preset that was subsequently edited.
It appears that all of the presets that are being rebuilt are Line 6 Helix Factory Presets (or modifications thereof) that came with a firmware release earlier than 2.80.
Should I raise a support ticket, or just delete them, or overwrite them with the new 2.80 Factory presets?
HonestOpinion - It is quite likely that I moved presets around, created new ones, or edited existing presets. I have certainly not done anything with over 200 at a time though. A preset move would normally only involve relocating a preset within the same setlist - say up or down 20 positions. I can't tell which presets are being rebuilt - it starts at 1 and goes up to wherever - a few hundred at present, and then throws in a few more with higher numbers. There does not appear to be any way of identifying which are getting rebuilt. The setlist I am working on at present is in the middle of the list of setlists, in which case I would expect the rebuild to start at a much higher number.
I am also finding that presets get rebuilt every time I turn on Helix. It seems to be a few less each time, and now it only seems to go up to the first 200 or so, and maybe a few random ones after that. It certainly doesn't stop after the first boot-up following the update.
Wireless to Helix (Deranged Master)
Many fuzz boxes and other effects are sensitive to input impedance. Wireless systems intrduce a buffer, so the fuzzes were unable to see the impedance of the pickups, and the fuzzes sounded crap. Initially this was a problem with the Helix because some of the effects were similarly sensitive. You could always adjust the input impedance, or set it to Auto which matched the input impedance to the first block in the chain, whether that block was active or not. That meant you could put the fuzz in as first block, making the impedance around 22k, and the fuzz sounded fine. Trouble was that the low imput impedance badly affected subsequent effects and the amp when the fuzz was off. Many of us devised a solution where the stomp button for the fuzz also switched the impedance to low, and switched it back to 1M when the fuzz was turned off.
After some long and heroic battle by a few users, Line 6 introduced an update so that the Auto Impedance could be set to that of the first Active block, not just the first block. This meant that the impedance changed automatically as the fuzz was switched on and off, so the problem was solved.
If the treble booster emulations in the Helix are impedance sensitive (though I have never noticed this), they should be fine as long as you place it where it will be the first active block when it is on, and set the Auto Impedance to "First Active Block".