FIXED: Renamer v5.60 b16 bug: Serialize fails with dirs with numbers

iycgtptyarvg · 2012-12-31 15:20

Whoops!

I didn't notice there also was a beta option. I'll do that right now.

Edit:
No, still fails in v5.60+ beta 23

It states in the history.txt:
Beta 21
* Fixed issue with natural sorting algorithm: next immediate character
after a numeric value was skipped (jumped over) in comparison;

Apparently, it's still not fixed.

I also checked non-natural sorting, and it also fails. There is something really totally wonky with sorting on path in Renamer and I'm very surprised no one else has noticed this.

Renamer v5.60+ beta 23 with non-natural sorting does this:

Last edited by iycgtptyarvg (2012-12-31 15:31)

Stefan · 2013-01-01 00:12

It seems to work for me, i don't see the differences to you.
I have also tested with 12 files in each folder.

Only i do not know how you are always able to set "repeat 0"?

1) Delete: Delete from Position 1 until the End (skip extension)
2) Serialize: Serialize Incremental from 1 step 1 repeat 1 (reset index if folder changes) and pad to length 3 as prefix
3) Case: Extension lower case

X:\~\Godstorm #01\00.jpg	001.jpg
X:\~\Godstorm #1\00.jpg	   001.jpg
X:\~\Godstorm #01\01.jpg	002.jpg
X:\~\Godstorm #1\01.jpg	   002.jpg
X:\~\Godstorm #01\02.jpg	003.jpg
X:\~\Godstorm #1\02.jpg	   003.jpg
X:\~\Godstorm #002\00b.jpg	001.jpg
X:\~\Godstorm #02\00b.jpg	001.jpg
X:\~\Godstorm #2\00b.jpg	001.jpg
X:\~\Godstorm #002\00r.jpg	002.jpg
X:\~\Godstorm #02\00r.jpg	002.jpg
X:\~\Godstorm #2\00r.jpg	002.jpg
X:\~\Godstorm #002\02.jpg	003.jpg
X:\~\Godstorm #02\02.jpg	003.jpg
X:\~\Godstorm #2\02.jpg	   003.jpg

iycgtptyarvg · 2013-01-02 10:09

Ok, I resaved the rule, and now repeat is on 1 (was this a settings bug?)
But, it's STILL not right.
As you can also see in your own screenshot, the problem is that the natural sorting should take into consideration that 1 is not exactly equal to 01 and is not exactly equal to 001 etc.

I just don't understand why the sorting keeps changing and is different for us. I'm on the verge of despair here.

den4b · 2013-01-02 11:18

If you want the sorting to differentiate between 001, 01, 1 - then disable natural sorting, like in Stefan's example. However, natural sorting results in 001, 01, 1 to be be evaluated as equal, hence, the order in which these names will be sorted is undefined and unpredictable.

The Serialize rule however uses character by character comparison when checking for a changed folder. So when it first sees #01 and then #1 it will detect it as a changed folder.

There is no bug. I think you may have misunderstood the functionality.

I hope this helps.

iycgtptyarvg · 2013-01-02 12:12

Dear Den4b,

Ok, I turned off natural sorting, but as you can see it's still wrong. The counting continues until picture 11 of the second directory instead starting at the first picture. (F:\~\Godstorm #2\11.jpg is NOT the first picture in the directory).

I assume by now you understand what I want to do. Could you please tell me exactly which settings I need to accomplish this (and of course still have other renames to work)?

den4b · 2013-01-04 10:32

I've tried to reproduce your scenario but everything has worked as expected.

The natural sorting is disabled
Delete: Delete from Position 1 until the End (skip extension)
Serialize: Serialize Incremental from 1 step 1 repeat 1 (reset index if folder changes) and pad to length 3 as prefix
Case: Extension lower case

As you see, the sorting/grouping of files works and the serialization index gets reset correctly.

Try closing ReNamer and removing your ReNamer.ini file from the installation folder, to reset the settings to the default. Then recreate the rules. And try using the latest development version.

iycgtptyarvg · 2013-01-04 10:52

Yeaaaaaaaaaaaahhhhhh!

The new beta made it work. I would suggest making this the default release so new-comers don't get burned and walk away from Renamer.

Thank you, thank you, thank you!

Stefan · 2013-01-04 13:28

iycgtptyarvg wrote:

No, still fails in v5.60+ beta 23
Renamer v5.60+ beta 23 with non-natural sorting does this:

den4b wrote:

Try closing ReNamer and removing your ReNamer.ini file from the installation folder, to reset the settings to the default.
Then recreate the rules. And try using the latest development version.

iycgtptyarvg wrote:

The new beta made it work.

Great that it works for you now.
BTW, the above link was to the archive containing ReNamer 5.60.X Beta 23 from 24.11.2012

.

iycgtptyarvg · 2013-01-06 21:39

Really? Ok, then I guess it was the .ini file. Very strange, but I'm glad it's solved.

Many many thanks for assisting me!

den4b Forum

#11 2012-12-31 15:20

Re: FIXED: Renamer v5.60 b16 bug: Serialize fails with dirs with numbers

#12 2013-01-01 00:12

Re: FIXED: Renamer v5.60 b16 bug: Serialize fails with dirs with numbers

#13 2013-01-02 10:09

Re: FIXED: Renamer v5.60 b16 bug: Serialize fails with dirs with numbers

#14 2013-01-02 11:18

Re: FIXED: Renamer v5.60 b16 bug: Serialize fails with dirs with numbers

#15 2013-01-02 12:12

Re: FIXED: Renamer v5.60 b16 bug: Serialize fails with dirs with numbers

#16 2013-01-04 10:32

Re: FIXED: Renamer v5.60 b16 bug: Serialize fails with dirs with numbers

#17 2013-01-04 10:52

Re: FIXED: Renamer v5.60 b16 bug: Serialize fails with dirs with numbers

#18 2013-01-04 13:28

Re: FIXED: Renamer v5.60 b16 bug: Serialize fails with dirs with numbers

#19 2013-01-06 21:39

Re: FIXED: Renamer v5.60 b16 bug: Serialize fails with dirs with numbers

Board footer