Ziweh Posted March 5, 2017 Share Posted March 5, 2017 Hey there! i was wondering if any of you had the same problem: When i use the "modulation chorus", tweak it, and save it, each time i recall the patch, it sounds as if i'd set the depth to 10, and what's even odder, is that i noticed i had to set again the predelay knob and not the depth knob, to make the patch sound as it was saved.. Don't know if i'm clear (my frenglish sorry.) Pls let me know what you think. Quote Link to comment Share on other sites More sharing options...
silverhead Posted March 5, 2017 Share Posted March 5, 2017 Does this happen with all presets or just in one specific preset? Are you using Snapshots in the affected preset(s)? Quote Link to comment Share on other sites More sharing options...
Ziweh Posted March 5, 2017 Author Share Posted March 5, 2017 It happens with all presets unfortunately.. I'm not using snapshots. For now, i found a solution by connecting the exp pedal to predelay knob, setting min and max to the desired (same) value. So when i call the preset, and if i move the pedal a bit, my settings sounds as they were saved. (sorry it's a bit complicate to explain..) Quote Link to comment Share on other sites More sharing options...
Ziweh Posted March 5, 2017 Author Share Posted March 5, 2017 Thx for replying btw! Quote Link to comment Share on other sites More sharing options...
HonestOpinion Posted March 5, 2017 Share Posted March 5, 2017 Hey there! i was wondering if any of you had the same problem: When i use the "modulation chorus", tweak it, and save it, each time i recall the patch, it sounds as if i'd set the depth to 10, and what's even odder, is that i noticed i had to set again the predelay knob and not the depth knob, to make the patch sound as it was saved.. Don't know if i'm clear (my frenglish sorry.) Pls let me know what you think. This suggestion may be off in left field as I have not tested yet to see if I get the same behavior with the chorus but the first thing I would check is to make sure you have the right Editor version for your firmware, especially if you have noticed other blocks not retaining settings properly. Quote Link to comment Share on other sites More sharing options...
Joepeggio Posted March 5, 2017 Share Posted March 5, 2017 Is this with Helix connected or not connected to computer. 1 Disconnect Helix from computer 2 reboot helix. ( off then on) 3 try chorus again Same results? Quote Link to comment Share on other sites More sharing options...
Ziweh Posted March 5, 2017 Author Share Posted March 5, 2017 It's without Helix connected to computer.. Quote Link to comment Share on other sites More sharing options...
Ziweh Posted March 5, 2017 Author Share Posted March 5, 2017 This suggestion may be off in left field as I have not tested yet to see if I get the same behavior with the chorus but the first thing I would check is to make sure you have the right Editor version for your firmware, especially if you have noticed other blocks not retaining settings properly. Thank you, this happens without connecting Helix to the the computer. Quote Link to comment Share on other sites More sharing options...
brue58ski Posted March 5, 2017 Share Posted March 5, 2017 I have had this phenomenon happen with another parameter (Variax model I think) and the only solution I found was to create another new patch. But sounds like you've already done that. Just wanted you to know you aren't crazy. I've had something like that happen to me. Quote Link to comment Share on other sites More sharing options...
HonestOpinion Posted March 5, 2017 Share Posted March 5, 2017 Thank you, this happens without connecting Helix to the the computer. In the interest of eliminating anything in the way of configuration that may cause the sound to change when you recall a preset.... Are any parameters associated with the tempo footswitch or expression pedal? If you have a parameter assigned to tempo or expression and either of these (tempo switch or expression pedal) are set to global instead of per preset I could see this causing it to sound different each time you recalled that preset. Probably not your issue but maybe worth mentioning. Quote Link to comment Share on other sites More sharing options...
HonestOpinion Posted March 5, 2017 Share Posted March 5, 2017 A couple of more questions for you? I wanted to test this out on my Helix. I am not aware of a block named "modulation chorus". Is this occurring on the modulation block called "Chorus"? Did you do a global reset after your last firmware upgrade? This is particularly relevant if this is happening with other blocks across multiple presets. If you have not done the reset make sure to back up everything per the many good instructions on the forum and in the firmware release notes before you do the global reset. Quote Link to comment Share on other sites More sharing options...
duncann Posted March 5, 2017 Share Posted March 5, 2017 A couple of more questions for you? I wanted to test this out on my Helix. I am not aware of a block named "modulation chorus". Is this occurring on the modulation block called "Chorus"? Did you do a global reset after your last firmware upgrade? This is particularly relevant if this is happening with other blocks across multiple presets. If you have not done the reset make sure to back up everything per the many good instructions on the forum and in the firmware release notes before you do the global reset. I would assume it's the Chorus block, since that's the only one with a pre-delay parameter. @Ziweh: I tried unsuccessfully getting the behavior you described. I'd try HonestOpinion's suggestion above about the global reset. Quote Link to comment Share on other sites More sharing options...
Ziweh Posted March 6, 2017 Author Share Posted March 6, 2017 Yes you're right it's the Chorus. My Helix is a second hand, got it since only two weeks (it's V2.12) so i haven't been that deep into it for now, i don't know how to make proper backup/global reset, i'll check.. (don't want to loose the few presets i already created..) Thank you all for helping me, i'll keep you posted when i'm done with the global reset etc.. Quote Link to comment Share on other sites More sharing options...
HonestOpinion Posted March 6, 2017 Share Posted March 6, 2017 Yes you're right it's the Chorus. My Helix is a second hand, got it since only two weeks (it's V2.12) so i haven't been that deep into it for now, i don't know how to make proper backup/global reset, i'll check.. (don't want to loose the few presets i already created..) Thank you all for helping me, i'll keep you posted when i'm done with the global reset etc.. If you have the v.2.12 firmware make sure you have the v2.11 Editor installed before you do your backups. If you have not done an upgrade before make sure you back up (twice) a bundle, all the user setlists, and I would back up the presets individually as well. In your case backing up the presets individually is particularly important as your Helix is second hand and is misbehaving so the integrity of the bundle and setlist backups may be in question depending on whether or not a global reset was ever run prior to you designing your own presets or the firmware being upgraded properly. All the presets in a setlist can be backed up individually by highlighting them all in the editor at one time and hitting the 'Export' link. Make sure to back up your IRs as well and take a screen shot of their placement in the IR screen so you can restore them to the same slots afterwards. The global reset will clear all presets and IRs on the Helix and replace them with the latest Factory and Template presets while also deleting all presets from the User lists. Good backups are paramount. After you do the global reset and restore your backups make sure to reboot the Helix in case any presets need to go through the rebuild process. They may not as you are already on the latest firmware revision. Last but not least. If after you do the global reset and restore you are still having issues I would reflash the firmware and do the global reset and restore process just to make sure you are starting off with a healthy install. Good luck! Quote Link to comment Share on other sites More sharing options...
Ziweh Posted March 8, 2017 Author Share Posted March 8, 2017 Thank you "HonestOpinion" for your support. I just realised something: i got the 2.12 V but i'm working n Windows 7, and checked the site which says 2.12 is supposed to work on Windows 10... What do you think? could it be the beginning of an answer? + when i do a bundle export, what am i saving in fact? Quote Link to comment Share on other sites More sharing options...
FlyingsCool Posted March 8, 2017 Share Posted March 8, 2017 Windows 7 is just fine. It's all I use. A bundle is all the setlists. A setlist is, well, a setlist, such as Factory Setlst 1 I wouldn't bother backing up the bundle, as the Factory Setlists change with each release. I backup the setlists individually, and, as HonestOpinion suggested, individual presets I care about. That way I have control over what I restore. The nice thing about backing up presets is they are in text format, and you can read them. So you could do some debugging by saving the preset you are having a problem with at different times, and see what the differences are. Make sure you are saving your presets. If you make a change to a preset, switch to another without saving first, the setlist you just left will revert back to its last saved state. Quote Link to comment Share on other sites More sharing options...
HonestOpinion Posted March 9, 2017 Share Posted March 9, 2017 Thank you "HonestOpinion" for your support. I just realised something: i got the 2.12 V but i'm working n Windows 7, and checked the site which says 2.12 is supposed to work on Windows 10... What do you think? could it be the beginning of an answer? + when i do a bundle export, what am i saving in fact? A bundle exports all your presets on the Helix including the Factory and Templates presets. That is why many people don't use a bundle to restore as it overwrites any new Factory/Templates presets that might have come with the new firmware version with the ones from your saved bundle. Of course, if you modify your presets "in place" in the Factory lists you may want to use a bundle restore. My strategy and many others here has always been to create my presets in the User setlists and copy any over from the Factory lists to the User lists that I may want to modify. When it comes time for a firmware upgrade I restore my User setlists instead of a bundle. I always save a bundle just to be thorough as a last line of defense for restores in case all else fails but I never use them for restores. There are a couple of advantages to saving not only setlists but the individual presets as well - if your setlist backup has an issue you have an alternative method for restoring your presets, additionally if one or more of the presets in a setlist has issues you can analyze the contents of your presets and potentially fix them because as FlyingCool pointed out they are in text format. I am on Windows 10 but it looks like FlyingCool answered the question in the affirmative regarding whether the 2.12 firmware works (with the Editor) on Windows 7. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.