Peter Cave wrote:You do need to use leading zeros to get the sort order correct.
No need to do this under Win10 in file explorer. W10 sort naturally as S1, S3, S10 not S1, S10, S3. No need to add 0 like S01, S03, S10... What about is you get later S100 file ? Do you have to add one more 0 before...
Getting around is an answer but do not solve the real problem....
You can’t use win file explorer in Resolve, and it doesn’t solve the same problem in gazillion other places that don’t do smarts for sorting.
This is solved by anticipating the number of digits for your token and padding it appropriately. If you anticipate going to hundreds you do 001 and so on. It works the same with a lot of things, version numbers, shot codes, frame numbers and so on for example. And as a hint, for nonsequentially produced codes (as opposed to versions and frame numbers), use bigger step size, 10 for example, to anticipate stick-ins. Then you can do 010-015-020 instead of some abomination like 010-010a-011