quad cortex 2.0.3 changes to reverb “mix” and “delay” don’t hold after save and switching back to preset. Preset existed before firmware upgrade. The FIX was to delete the Reverb effect and reenter it. Then it works fine and changes hold after the save. This happens and many ( if not all) presets that were set up before 2.0.3. But after only deleting the reverb effect block (not the entire preset) and reentering it fixes it.
Does your preset have multiple scenes? If so, try enabling the misbehaving parameters as scene assignable and see if the settings will save.
1 Like
No scenes, just the preset.
Check the setting for ‘Scene Bypass State Behavior’ under ‘Settings’. Perhaps this is impacting how the QC is saving your preset changes. Even if you aren’t switching scenes afterwards.
1 Like
Scene Bypass State in first/top setting.
See attached Video to see what is happening. Not all patches do this, but several do. After the reverbs are deleted and reentered the issue goes away. It seems, some of these that were created on a particular firmware version then after a firmware upgrade this issue surfaces.
I was not even going to notify you about the issue since it can be resolved by the above procedure. But though you may wanted to know about it.
(Attachment MyVideo_1685634599910.mp4 is missing)
Hmmm, odd. I just updated to 2.03 a few days ago but haven’t tried modifying any presets yet. I’ll give it a try and report back.
Scene Bypass State in first/top setting.
I tried to send a Video to show what is happening, but your site rejected it as “unauthorized”. Basically the video displayed me adjusting the “decay” and “mix” on the “Modulated” reverb. Then saving the preset, changing to another preset and after returning to the edited preset; showing the reverb went back to its original settings. Not all patches do this, but several do. After the reverbs are deleted and reentered the issue goes away. It seems, some of these that were created on a particular firmware version then after a firmware upgrade this issue surfaces.
I was not even going to notify you about the issue since it can be resolved by the above procedure. But though you may wanted to know about it.
I wonder if doing a full backup, and then restoring it to your current 2.0.3 firmware might fix this issue.
No, just tried a backup → restore did not change the issue.
1 Like
I just changed and saved the reverb level on two different presets and they both retained the new settings. V2.03 seems to be working fine on my QC. That’s a strange glitch you’re experiencing. Out of curiosity, does the preset name italicize when you make changes?
Yes it does, after you save it and go back into the reverbs the new settings are there, but go back to what they were if you go to another preset then back to it again. I could send you one of the presets that are doing this and see the same issue surfaces on another machine.
Do you happen to know which version of CoreOS the problem presets were created on? Just wondering if someone would have to use presets from that version to recreate this problem. Also are presets created with any/every prior version displaying this behavior on your QC?
Have a little more info: In my notes the original preset came from the Cloud from WorshipGuitarGuy preset = See A Victory
So I just downloaded that preset and it also has the same issue. I did use that preset to make several presets (from his cloud shared preset) and it appears that the issue is related to those presets I made from that download. I am assuming if you download that same preset from WorshipGuitarGuy the same issue would surface on your device. So it appears that a preset created on an earlier version of the CoreOS could exhibit the issue. I don’t know if the presets have imbedded information concerning what CoreOS they were created under, I know that they at least have the original author’s user name.
After changing the reverb mix, I went to another preset then back to the altered preset and confirmed that the parameters were retained.
I’d be happy to try your preset but won’t be able to do it until we return home, mid-month. I’ll keep checking in to see if this issue is still unresolved.
Thanks so much for all the great responses. I don’t know if you are aware that HO also has been involved regarding this issue. But just incase I will pasted my last correspondence to HO to you below. I think it nails down this issue in area of having old presets loaded into new CoreOS firmware.
Sincerely
Have a little more info: In my notes the original preset came from the Cloud from WorshipGuitarGuy preset = See A Victory
So I just downloaded that preset and it also has the same issue. I did use that preset to make several presets (from his cloud shared preset) and it appears that the issue is related to those presets I made from that download. I am assuming if you download that same preset from WorshipGuitarGuy the same issue would surface on your device. So it appears that a preset created on an earlier version of the CoreOS could exhibit the issue. I don’t know if the presets have imbedded information concerning what CoreOS they were created under, I know that they at least have the original author’s user name.
Interesting. All of my presets were created on v2.0 but tweaked many times along the way. I haven’t noticed this irritating phenomenon. You’d think it would have become a common complaint by now. Who knows? Maybe I’ve been tweaking away for the last two months, not noticing that I have the exact same presets I started with. 
Sounds like this issue may all stem from a corrupted preset or corrupted download of the preset “See A Victory”, mentioned by @rschieder . Version may not turn out to be relevant.
I think you are right, probably no reason to pursue this issue further. My question is why wouldn’t the Quad Cortex produce a checksum or crc error on a corrupt preset file. Anyway, since we know this can happen with no indication other than certain settings or features failing to be saved on changes. Therefore when this happens one must delete the effect box and then reinsert for it to function correctly.
Thanks both of you for being so diligence in tackling this issue, it is much appreciated.
Take care and God Bless!
1 Like