Include edition information such as catalogue number and record label in transcode directory name

[Asparghus]

Be able to differentiate torrents by their catalogue number and have the option to add that to the folder name.

E.g. 4317932 and 4317935. Both torrents are from the same group, single and format.

That causes issues when trying to upload it. The two I've identified are:

• The second transcode overwrites the first when moved to the content folder as it uses the same folder name
• If the torrent files is still present, it thinks that it had been already transcoded and tries to upload the same file which results on the following error: ERRO ! Failed to upload torrent / ERRO ! A 400 error occurred / ERRO ! r*.sh/torrents.php?torrentid=******* The exact same torrent file already exists on the site!

[RogueOneEcho]

I was aware that collisions were possible but hadn't personally come across any so didn't see the necessity to include catalogue numbers.

If more collisions are reported I'll definitely investigate this further, but usually there's a distinction in the edition title (or remaster_title in API terms) that is included in the naming scheme:

caesura/src/naming/source_name.rs

Lines 21 to 24 in 5615b8d

	format!(
	"{} - {} ({}) [{}]",
	metadata.artist, metadata.album, metadata.remaster_title, metadata.year
	)

With your examples I believe that 4317935 needs to be edited to correctly include The Urban Remixes as its edition title. Once this is done you won't see the collision. If you're Elite or above you can do this yourself, if not you can report it and select "Request an edit".

Do let me know if you see other occurrences of this

[RogueOneEcho]

We can determine if a collision may occur by filtering the torrents returned by the API's torrentgroup action for matching remasterTitle, format and encoding.

If there's more than one result then add the remasterRecordLabel or remasterCatalogueNumber for uniqueness.

[Asparghus]

That sound like a good solution to me. As it will avoid the need of a user input.

BTW, I edited those I've reported as conflicting, I will give it a shot now to see how it goes. Hopefully it won't be an issue anymore.

[Asparghus]

Yep, just fixing the edition titles fixed it.

[RogueOneEcho]

I've come across a good example of this:

OPS: 3596503 and 3576571

3576571is a source that contains 1 track.

3596503 is a source released and uploaded 2 weeks later that contains 3 tracks.

Both are in torrentgroup 1584533, have catalogue number set but no edition title.

caesura therefore transcodes them both to the same directory.

3576571 was transcoded first so that was transcoded and uploaded successfully.

3596503 was then transcoded.

caesura finds the .ops.torrent for 3576571 and incorrectly assumes it's a match and so assumes it is already transcoded.

caesura then uploads that .torrent which is rejected by the API:

2026-04-24 10:22:02.077 DBUG * Found existing FLAC transcode
2026-04-24 10:22:02.987 ERRO ! caesura::UploadAction::Upload

  × Failed to upload torrent
  ├─▶ Failed to unexpected response
  ├─▶ The exact same torrent file already exists on the site! <a href="artist.php?id=833073" dir="ltr">ARTIST</a> – <a href="torrents.php?id=1584533&amp;torrentid=3597183#torrent3597183"
  │   dir="ltr">TITLE</a> [2026 Single]
  ╰─▶ The exact same torrent file already exists on the site! <a href="artist.php?id=833073" dir="ltr">ARTIST</a> – <a href="torrents.php?id=1584533&amp;torrentid=3597183#torrent3597183"
      dir="ltr">TITLE</a> [2026 Single]

Including the category number in the directory name is the correct solution for this.

[ResponsiveIntrovert]

The edition catalogue data of the input (to be transcoded), as listed on the website, should be added to the output folder name even when there are no collisions, for the following reasons :

Benefits:

• Prevents mixing music files from different editions' torrents with identical folder name.
• (Big!) Preserves edition, catalogue details for future reference if the website becomes unavailable.

Sample Output Folder Format (Needs Improvement) :

Artist - Album (AlbumYear) [SourceMedia OutputFormat BitDepth-SampleRate] {RecordLabel, CatalogueNumber, EditionName, EditionYear}

Example:

• Input Vinyl 24bit/192kHz album details on the website:
  John Doe - Sample Album of Songs 1950

• Input's Edition on the website:
  2010 - XYZ Music Label / ABC Records / 012345 / 0567890 / 60th Anniversary Edition / Vinyl

• Output Folder (16/48 Transcode):
  John Doe - Sample Album of Songs (1950) [Vinyl FLAC 16-48] {XYZ Music Label, ABC Records, 012345, 0567890, 60th Anniversary Edition, 2010}

[RogueOneEcho]

I agree with the sentiment that in an ideal world all that info would be included however there are some significant limitations that need to be taken into account.

Don't take the following as criticism of the idea, it's mostly for my benefit when I revisit the idea in the future:

1. 180 character length constraint.

I know it's just an example but it's not an unrealistic one. The example transcode directory name is 138 characters and the rules limit the total length of any path in a torrent to 180 characters. So by adopting such a long format it would significantly limit the path length of tracks. For example this is fairly basic path is 181 characters and would therefore be rejected.

John Doe - Sample Album of Songs (1950) [Vinyl FLAC 16-48] {XYZ Music Label, ABC Records, 012345, 0567890, 60th Anniversary Edition, 2010}/Disk 1/01. Song titles are often long.flac

Hence it's preferable to keep the output directory name as minimal as possible while providing as much info as required.

2. Edition info is already included

For your example caesura would use the following:

John Doe - Sample Album of Songs (60th Anniversary Edition) (2010) [Vinyl FLAC]

• The edition title (remaster_title: 60th Anniversary Edition) is already included in brackets after the album name.
  

  caesura/src/naming/source_name.rs

  Lines 21 to 24 in 5615b8d

  	format!(
  	"{} - {} ({}) [{}]",
  	metadata.artist, metadata.album, metadata.remaster_title, metadata.year
  	)

• The edition year (remaster_year: 2010) is already used in place of the original album year:
  

  caesura/src/source/metadata.rs

  Lines 54 to 60 in 5615b8d

  	fn get_year(group: &Group, torrent: &Torrent) -> u16 {
  	if torrent.remaster_year.is_none() || torrent.remaster_year == Some(0) {
  	group.year
  	} else {
  	torrent.remaster_year.expect("Remaster year should be set")
  	}
  	}

3. sample rate: 48

I believe that transcodes may be a mixture of 48 khz and 41 khz tracks therefore it may simply be incorrect to include the sample rate in the name.

Even if a transcode contained just one sample rate is it of value to know that? Do people really prefer one over the other for 16 bit FLACs. I agree for 24 bit FLACs it's worth including this information because multiple sample rates can co-exist.

4. 16 bit

The standard is that unless it's explicitly stated that a FLAC is 24 bit then it can be assumed to be 16 bit. I'm not aware of any uploaders who deviate from this therefore I would say it's redundant information that increases the likelihood of hitting the 180 character limit.

For example caesura also doesn't explicitly mention MP3 in the name, it's just assumed that 320 means MP3 320 and V0 mean MP3 V0.

5. Record label and Catalogue number

There is some value in including the record label and catalogue number however that has to be balanced against the 180 character limit. (see the previous comments in this discussion).

The times where they are worth including is when collisions may occur. However caesura is only as powerful as the information it's provided so it would have to assume the number and label name are correct which isn't always the case. On the website you can edit incorrect details but once it's encoded in the torrent name and uploaded that's fixed and would result in the upload being trumped if incorrect.

Therefore I'd prefer to only include these details if they are essential which is rarely the case.

I'm also unsure of the context in which a user would be downloading multiple transcoded copies of the same edition such that a collision might occur. If you really wanted to compare the same edition you'd presumably download the source for its higher quality rather than a transcode.

[RogueOneEcho]

I neglected your point:

Preserves edition, catalogue details for future reference if the website becomes unavailable.

That's a valid consideration but due to the reasons above I think including it in the directory name isn't possible.
Instead I'd recommend either including the edition, catalogue number etc:

• in the track metadata, this is often already the case for well tagged media and the advantage here is it can also be read by media players.

The VORBIS standard has fields for this:

ORGANIZATION
Name of the organization producing the track (i.e. the 'record label')

ISRC
ISRC number for the track; see the ISRC intro page for more information on ISRC numbers.

https://xiph.org/vorbis/doc/v-comment.html

• in an edition.txt file alongside the transcoded file.

[RogueOneEcho]

Possible solution in #155 option 3