Does INIT.DATA work?
Same thing, the value of M resets but the metronome keeps ticking at the old rate.
the bug was also in
INIT.DATA, fixed those as well.
Ah, I missed that. Thanks
posted new files - no change, just to update the commit version number.
My Teletype just blanked itself too. It was running fine last night and when I powered up this morning everything was gone. Guess I should get better at backing up.
I’m running 3.0 and the TT has an I2C backpack and is connected to a TXo and JF.
sorry to hear that, hopefully you didn’t lose too much…
everybody still running 3.0 firmware - i would strongly advise to do a backup and then update to the beta 3.+ version posted in this thread: Teletype 3.+ feature requests and discussion as it has additional protections against this bug.
I needed a fresh start, anyway – ha ha! But seriously, I’ll definitely be updating to the new beta tonight. Thanks!
Hey folks, the dreaded scene wipe got me yesterday / today as well. I had backed up recently, so not that big of a deal.
Just to provide some data about what I was doing:
- I’d really only been working on a single scene.
- Last night, I transitioned to a new scene.
- I didn’t actually add anything to the new scene, but I’d run some commands from the Live view.
- I powered down without saving the new scene.
That’s all I can think of as far as actual actions taken, sadly. Today I powered up and there were no scenes on the device.
I’ve already updated to the latest beta, so hopefully all save now.
thanks for the info, and sorry you lost your scenes, glad you had a recent backup.
do you remember the scene numbers by any chance?
The one that I had been operating on & the one that I switched to? It was 9 & 10, respectively.
(If that’s what you mean )
yep, that was my question, thanks!
Either PN.RND is funny or I’m missing something.
Pattern 3: 0, 2, 3, 5, 10 (rightmost column in tracker)
PN.RND 3 returns 0 95% of the time, occationally some of the other values of the pattern…
PN.RND will randomly select values within the
PN.END range. check what your start and end are set to.
That’s it thanks alot, end was 63!
Sorry for the noise…
2 posts were merged into an existing topic: Teletype 3.+ feature requests and discussion
I finally have a little time to get back into TT programming. And I have some idea Last time I looked the ‘everything is gone’ bug was still worrying. So I didn’t update… Is this fixed in the latest beta?
I think so? There’s now an added warning printed to the screen requiring user confirmation (via button press) before memory is wiped. Of course, you have to back up your scenes before installing the update.
i wasn’t able to reproduce the bug or pinpoint the exact reason for what might cause it, so i can’t guarantee that the bug is no longer there. we did put additional checks around the code that overwrites the scenes, so hopefully this did fix the issue. as far as i’m aware, there were no reports of people running into the issue among those using the latest 3.+ beta.
as an additional guard we also added a warning during the module startup - if it decides to overwrite scenes in flash memory, it will warn you first and give you a chance to not proceed, with the hope that you can try and restart the module and see if the message goes away - this can give you a chance to recover your scenes. since we haven’t had a case where this warning came up during normal operation (again, as far as i’m aware) we don’t know whether this will actually help, but it should hopefully provide additional confidence.
regardless, it’s a really good idea to do a USB backup of your scenes often, especially after making major changes.
20 characters of many thanks. I’ll get started again.