# creating file names from aaa000 through zzz999
**URL:** https://community.mp3tag.de/t/creating-file-names-from-aaa000-through-zzz999/9852
**Category:** Support
**Created:** [February 9, 2010, 1:38am UTC](https://community.mp3tag.de/t/creating-file-names-from-aaa000-through-zzz999/9852 "2010-02-09T01:38:01Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@world.stark](https://community.mp3tag.de/u/world.stark)
#### Post date: [February 9, 2010, 1:38am UTC](https://community.mp3tag.de/t/creating-file-names-from-aaa000-through-zzz999/9852/1 "2010-02-09T01:38:01Z")
I hope someone can help me figure this out.
I'm trying to name my mp3s from aaa000 through zzz999. So once mp3tag reaches aaa999, the next file should be named aa **b** 000. How can I set up mp3tag to do this? I have been trying to figure this out using these 2 sites
[https://docs.mp3tag.de/converters/rename-files](https://docs.mp3tag.de/converters/rename-files)
[https://docs.mp3tag.de/scripting](https://docs.mp3tag.de/scripting)
but I can't figure out the right combination. Help would be really appreciated.
Thanks,
---
### Author:  [@DetlevD](https://community.mp3tag.de/u/DetlevD)
#### Post date: [February 9, 2010, 7:06am UTC](https://community.mp3tag.de/t/creating-file-names-from-aaa000-through-zzz999/9852/2 "2010-02-09T07:06:20Z")
> [@worlds](#):
>
> ... I'm trying to name my mp3s from aaa000 through zzz999. So once mp3tag reaches aaa999, the next file should be named aa **b** 000. ...
You can stop trying ... here comes the solution.
Well, I hope you really did try to solve this for your own ... so hard as you can do ... at least you have did the first step ... counting from "aaa000" to "aaa001"!
So whenever you did this you can ever understand what the following work is worth.
This was somewhat a challenge (using Mp3tag scripting language) ... and now here it is:
a group of actions that does right this what you have described.
Description
The following group of actions will create a running alphanumerical number replacement for the decimal number range of 0 to 17575999, which fits into 6 digit places by using three lowercase alpha digits from the Latin alphabet set [a..z] and three numerical digits from the set [0..9] giving the format "aaannn".
Counting of items begins at zero. When reaching item 1000 plus 1 the numerical part overflows (greater than 999) and the lowest value from the alpha part will be incremented from letter "a" to "b" and the numerical part starts counting again from zero.
If the number reaches "aaz999" (this is item 26000 in decimal), then the next higher value from the alpha part will be incremented, so the following number will be "aba000" and the numerical part starts counting again from zero.
The highest number will be "zzz999". It could not be verified what will happen when incrementing this counter value again by 1. 😉 _No liability for consequential damages._
How to use?
Select the tracks to enumerate.
Run the action against the selection.
When ready the number string can be read from the tag field "TMP\_NUM\_AAANNN" (this tag field name can be renamed by user).
Begin Actionsgroup **20100209.Counter.AAANNN**
Action #1
_Actiontype 5:_ **Format tag field**
_Field:_ **TMP\_CNT\_B10**
_Formatstring:_ **$sub(%\_counter%,1)**
Action #2
_Actiontype 5:_ **Format tag field**
_Field:_ **TMP\_CNT\_B10\_MAX**
_Formatstring:_ **1000**
Action #3
_Actiontype 5:_ **Format tag field**
_Field:_ **TMP\_NUM\_B10**
_Formatstring:_ **$mod(%TMP\_CNT\_B10%,%TMP\_CNT\_B10\_MAX%)**
Action #4
_Actiontype 5:_ **Format tag field**
_Field:_ **TMP\_CNT\_NB**
_Formatstring:_ **$div(%TMP\_CNT\_B10%,%TMP\_CNT\_B10\_MAX%)**
Action #5
_Actiontype 5:_ **Format tag field**
_Field:_ **TMP\_NB**
_Formatstring:_ **26**
Action #6
_Actiontype 5:_ **Format tag field**
_Field:_ **TMP\_DGT\_NB0**
_Formatstring:_ **$mod(%TMP\_CNT\_NB%,%TMP\_NB%)**
Action #7
_Actiontype 5:_ **Format tag field**
_Field:_ **TMP\_DGT\_NB1**
_Formatstring:_ **$mod($div(%TMP\_CNT\_NB%,%TMP\_NB%),%TMP\_NB%)**
Action #8
_Actiontype 5:_ **Format tag field**
_Field:_ **TMP\_DGT\_NB2**
_Formatstring:_ **$mod($div(%TMP\_CNT\_NB%,$mul(%TMP\_NB%,%TMP\_NB%)),$mul(%TMP\_NB%,%TMP\_NB%))**
Action #9
_Actiontype 5:_ **Format tag field**
_Field:_ **TMP\_NUM\_1**
_Formatstring:_ **$add($add($mul($mul(%TMP\_NB%,%TMP\_NB%),%TMP\_DGT\_NB2%),$mul(%TMP\_NB%,%TMP\_DGT\_NB1%)),%TMP\_DGT\_NB0%)**
Action #10
_Actiontype 5:_ **Format tag field**
_Field:_ **TMP\_NUM\_2**
_Formatstring:_ **%TMP\_DGT\_NB2%÷%TMP\_DGT\_NB1%÷%TMP\_DGT\_NB0÷%$num(%TMP\_NUM\_B10%,3)**
Action #11
_Actiontype 5:_ **Format tag field**
_Field:_ **TMP\_NUM\_AAANNN**
_Formatstring:_ **$char($add(97,%TMP\_DGT\_NB2%))$char($add(97,%TMP\_DGT\_NB1%))$char($add(97,%TMP\_DGT\_NB0%))$num(%TMP\_NUM\_B10%,3)**
Action #12
_Actiontype 9:_ **Remove fields**
_Fields to remove (semicolon separated):_ **TMP\_CNT\_B10\_MAX;TMP\_CNT\_B10;TMP\_CNT\_NB;TMP\_NB;TMP\_DGT\_NB0;TMP\_DGT\_NB1;TMP\_DGT\_NB
2;TMP\_NUM\_B10;TMP\_NUM\_1;TMP\_NUM\_2**
_Note: Replace each special ÷ character with one space character._
End Actionsgroup **20100209.Counter.AAANNN** (12 Actions)
DD.20100209.0905.CET
Edit.
Actions #9 and #10 are not necessary, they can be removed in production environment.
DD.20100209.1414.CET
---
### Author:  [@world.stark](https://community.mp3tag.de/u/world.stark)
#### Post date: [February 9, 2010, 12:49pm UTC](https://community.mp3tag.de/t/creating-file-names-from-aaa000-through-zzz999/9852/3 "2010-02-09T12:49:18Z")
Thank you, thank you. I will give your suggestion a try in a few days. Seems like a lot of work.
---
### Author:  [@DetlevD](https://community.mp3tag.de/u/DetlevD)
#### Post date: [February 10, 2010, 5:57am UTC](https://community.mp3tag.de/t/creating-file-names-from-aaa000-through-zzz999/9852/4 "2010-02-10T05:57:52Z")
Still I am wondering where the practical relevance lies for the work with Mp3tag and music files.
DD.20100210.0757.CET
---
### Author:  [@system](https://community.mp3tag.de/u/system)
#### Post date: [February 9, 2026, 12:22pm UTC](https://community.mp3tag.de/t/creating-file-names-from-aaa000-through-zzz999/9852/5 "2026-02-09T12:22:09Z")