#6

@Samuel_Tussing are you using SYSTEM > SLEEP to power off your shield every time ? unplugging while awake is equivalent to “dirty shutdown” and not good

#7

Thought i was doing a clean shutdown but maybe unplugged power before pi was finished shutting down? I’ve used system reset a few times as well. I’ll dig into it l8r when I’m home :red_car:

#8

If this is the case, should I be power cycling norns via system>sleep then powering back up instead of a system>reset when installing a new engine to avoid resetting the tape count?

Edit: can I edit system.state in maiden to ask tape to save starting at number____?

#9

that should do it

Edit: can I edit system.state in maiden to ask tape to save starting at number____?

yes you could do that

WOOPS, no actually that won’t work.

opened issue with 2 simple fix ideas

2 Likes
#10

Editing system.state in maiden, saving, sleeping and starting back up does not seem to fix the problem.

system.state seems to save on clean shutdown and revert to the reset tape count (norns.state.tape = 5 in my case) and not the edited tape increment that I saved in maiden.

#11

Was just posting the same issue - I’m not able to edit system.state - something I’ve noticed before. I just tried setting the tape count from 0 to 23, and after a “sleep” and restart, it is back at 0.

I also noticed norns.state.clean_shutdown is set to false, and I would expect it to be true if I am using sleep.

#12

yes i was utterly wrong, duh. system.state will be overwritten on SLEEP - it’s whole purpose is to cache the state at that point.

i don’t know about the clean boot flag, that does seem odd and maybe there is bug in how the flag is managed.

in any case, as regards this particular issue with the tape counters, my inclination is to cut the gordian knot by programatically incrementing the counter based on the current file contents instead of a data field. (proposed solution #2 in the GH issue.)

i gotta sign off for the night. @tehn is visiting and we will be doing some concentrated norns issue triage.

4 Likes
#13

I’m curious why people didn’t like the previous naming convention. It seems like using a system timestamp would basically guarantee the filename would always be unique, and you wouldn’t need all the extra logic to keep track of a counter.

#14

not a fan of #2 since I usually move all my tapes into the same folder on my computer from norns which would mean a lot of 0001 copy, 0001 copy 2, 0001 copy 3 etc

timestamp would do the trick with an added “now I know when I made the thing” !

#17

AH. Brian reminded me the reason for not having time stamps. Norns doesn’t have a reliable clock and the timestamps can be sort of random. So there you go

#18

ahhh - well another idea out of my brain would be saving tape count in its own file somewhere

counting up the tape counter is also nice for accomplishments so not necessarily against it either

2 Likes
#19

Whatever the solution is, I don’t think tape should ever overwrite an existing file? I was quite surprised when it happened to me, but I thought it was fates/upgrade related and I had already backed up my dust, so no biggie.

1 Like
#20

Of course I agree, hence the gh issue. I’m glad you didn’t lose anything in this instance

https://github.com/monome/norns/issues/1026.

It seems like a good time to move the convo there and start implementing something. IMHO any solution is better than losing data

1 Like
#21

A poll would be great I am for sure on team time stamp. And have lost a lot due to the numbering system and getting confused when I’m archiving into my one folder for recordings. What does the default time stamp look like?

#23

I’ve lost quite a few recordings. I don’t have any naming preference as long as recordings are safe!

1 Like
#24

i’m sorry for the confusion. norns has no clock. raspi has no clock. we tried timestamps in the first place (the obvious answer) and they were non-deterministic enough to be a real problem.

3 Likes
#25

Would this just mean e.g. basing the filename on the count of files currently in the tape dir?

#26

Any way to just have a spot where you could add say a 3 digit prefix to the numbering system that is user assignable? Or something like that. I think making naming any way unique could solv a lot of problems. This is a solution in many digital photo cameras. Obviously the 1 issue is the overwriting on Norns itself and the 2nd for me at least is archiving files and later putting them back on the Norns to use a script that I loaded samples into or so on and its impossible to figure out what 0001 file I’m looking for or my current renaming files to there actual number and archiving them all into a folder and not bowing 0007 is now 0348.

2 Likes
#27

Twenty characters of a reset counter?

#28

how about a prompt to save / discard your recording (after hitting stop) along with an auto-generated (adverb+noun) filename and the facility to edit it?

additionally/alternatively a warning if a file is about to be overwritten?