(02-07-2019, 09:37 PM)XORadmin Wrote:(02-07-2019, 09:31 PM)skybox Wrote:(02-07-2019, 09:29 PM)XORadmin Wrote:(02-07-2019, 09:27 PM)skybox Wrote: So interestingly enough, I wasn't able to get a save file to reset to 1 BPM after I changed it back to the correct BPM and saved. I did still have all my untouched saves which all showed 1 BPM. Ok, so I thought maybe the RC2 update would reset all my BPMs back to 1. So I updated my NerdSeq again with RC2 and... it fixed ALL of my BPMs. Even the ones I didn't touch that had 1 BPM are now reset to their original BPMs. I will keep looking in case it resets again but, still a very weird anomaly.
Are they all internal clock projects? ( Sorry, didn't read your edit...so i expect internal clock)
Yes. Also, I just reboot NerdSeq and all my saves are 1 BPM again!
UPDATE: Rebooted again and the BPMs are normal again. Seems like a coin flip.
Super double update: It looks like it happens when I load a new save while the current project is playing!
Oh please, attach or pm a coin flip file.
I'm including the save and a video of it happening. It actually happens before I'm able to get to load the final file:
https://photos.app.goo.gl/Nzem7urpARYrWQ3s6
I should have slowed down. at :27 you can see all the launches get screwy--they aren't even on the patterns!
Actually, I think I figured out what is happening:
When you have a live song playing and switch to a new save, it remembers the location of all the last patterns played. So it tries to play on patterns that are filled in one song but empty on the current, and it breaks the file somehow.
(Sorry for all the crazy updates, I do QA testing for a living so I get really worked up/excited about testing/troubleshooting!!)