Recorded Session Auto Naming

General Area
1

When I started recording my sessions, it defaulted to “Session-0001”, so I used the suggested name. When I recorded my second set, it automatically adjusted so that the new set was titled “Session-0002”. This is an excellent feature, and I grew to depend on it to sequence the naming of my sets.

Over time, the space taken up by these recordings became excessive, so I put them on another HDD, and I removed all but the most recent session, which was Session-0136. Last night after playing and recording, I went to save the recording, and Engine DJ OS wanted to save the track as Session-0001, when I was expecting it to save it as Session-0137.

I think there is no database or internal increment for this number, and it is evaluated/figured out when you go to save the recording, so I thought that leaving Session-0136 on the drive, the next recording would be Session-0137, but instead it has reset to Session-0001.

Does anybody have any insight as to what actually triggers this automatic increment? I’m tempted to place a Session-0001, and see if having that would be enough to trigger, and see Session-0136, incrementing to Session-0137, but maybe it’ll just try to save as Session-0002. I don’t have the time to play games and guess and figure it out exactly so I thought I’d ask here instead to see if anybody had any understanding of how this feature works.

That being said, I do think that leaving my most recent recording should have been enough to trigger the auto-increment, especially since we don’t get to customize this default-and-auto-incrementing name, it should be easy to find the file that matches “Session-NNNN” with the greatest number, and increment that by one.

1 Like
2

Not a clue sorry, I rename mine and put a date in the title after each session, never use that default value.

3

My tracklist is mostly 32bit 96khz and recording export as 24bit with less sample rates because build in sound card is cheaper. I think if some djs playing multiple synced tracks at the same time the quality can’t be decreased because these all 4 tracks are stored in 48Khz samples. It means all individual parts, sounds, samples sounds worst on the tracks.

4

So, I placed Session-0001.wav, and empty file, in the Sessions directory, hoping that it would trigger discovering the most recent/largest-numbered Session. Unfortunately it did not.

I will just create a bunch of empty Session wav files, 0001-0136, and that should work, but again, I think it’s pretty silly to implement this auto-increment naming, and to not have accounted for the time when people need to start pulling the recordings off of their device. I’d like to see this feature improved and not have this ‘bug’.

NEW_INCREMENT=$(expr 1 + $(find . -regex '\./Session\-[0-9]*\.wav$' -printf '%f\n' | sort -r | head -n 1 | grep -Po '[0-9]*') | xargs printf "%04d")