Very strange. I haven’t heard about this as an issue before, and it does sound buggy, but before we declare it a bug let’s put a few more pieces of info on the table and see if someone or maybe I can figure it out. First off, are you on 1.50 or did you do the recent OS upgrade already? Are you only using audio tracks on that pattern or is there another midi controlled device with audio routed into the inputs? Since you said the second project was fine, it sounds like this mismatch of fader controls is imbedded into the current project (almost as if it’s deliberately set) so it was like that when you reloaded the current project? Did you attempt a power cycle (power off for a full 30 seconds and then power back on)? Are you running standalone or is it connected to a computer or overbridge? Did you attempt to change any routing or settings specifically in that project? Anything outside of the default?
Any details that you can remember might be a clue. It really might be a bug, but the way you’re describing it sounds suspiciously like a setting that I just can’t see past my own nose to determine. I’m honestly not aware of an audio routing which allows you to change the meaning of the level fader, but I’m not at all familiar with the latest OS, I assumed it was just a small update with a couple bug fixes from 1.50.