Problems renaming images sequentially

[lacm1993]

I have a rule that renames images sequentially, with the name of the folder followed by a number and finally the extension like this:

(Assuming the folder is called "Image")

Image 1.jpg
Image 2.jpg
image 3.jpg
etc.

The problem is when I have more than one type of image type, then the rule does this:

image 1.jpg
image 1.png
image 1.tiff
image 2.jpg
image 2. png
image 2.tiff
image 3.jpg
image 4.jpg
etc.

It seems like the number count increments for files with the same extension but for files with a different extension is doing a separate count.

Is really annoying because is not immediately obvious what I'm doing wrong.

I can't figure out right now how to upload a local screen capture of my rule but is really simple:

If:
Kind is image
Do:
Rename with pattern source folder # extension

[Mr_Noodle]

That's how it works. It renumbers files that match the same initial name. As of yet, there's no way to do it how you are describing.

[lacm1993]

That's how it works. It renumbers files that match the same initial name. As of yet, there's no way to do it how you are describing.

Thanks, so there's no way of renaming the contents of a folder ignoring the type of the files?

I have folder with PNG, JPG, TIFF (sorted by name) and I want to rename them sequentially based on the name of the source folder and a number that increases regardless of the type.

From this:

Bicycle.jpg
Car.png
Motorcycle.HEIC
Plane.tiff

To this: (assuming the name of the folder is "Vehicles")

Vehicles 1.jpg
Vehicles 2.png
Vehicles 3.HEIC
Vehicles 4.tiff

Right now I'm getting:

Vehicles 1.jpg
Vehicles 1.png
Vehicles 1.HEIC
Vehicles 1.tiff

[Mr_Noodle]

Actually, which option do you have on the counter, "always increment" or use the "lowest available"? If the latter, this is the expected behavior so you may want to consider "always increment".

[lacm1993]

Actually, which option do you have on the counter, "always increment" or use the "lowest available"? If the latter, this is the expected behavior so you may want to consider "always increment".

That worked, thanks, I used lowest available thinking that If I ever delete an image and later add a new image I would want the new image to take the place of the old image to avoid having holes in the sequence. But I guess that’s not how it works, I’m going to read the documentation more carefully.