my release doesn't have that. Should I make a new release? I have already submitted disc ids to this one
2026-04-17 10740, 2026
shisma[m]
the barcode is the same
2026-04-17 10756, 2026
crism1 has left the channel
2026-04-17 10759, 2026
crism1 joined the channel
2026-04-17 10715, 2026
crism1 has quit
2026-04-17 10735, 2026
crism joined the channel
2026-04-17 10740, 2026
crism has left the channel
2026-04-17 10743, 2026
crism joined the channel
2026-04-17 10759, 2026
MeatPupp3t217362 has quit
2026-04-17 10705, 2026
crism
shisma[m]: new cover art means a new release, so yes, IMO.
2026-04-17 10716, 2026
shisma[m]
can two releases share the same tracklist entity?
2026-04-17 10700, 2026
reosarevok[m]
Not the tracklist itself but the recordings yes
2026-04-17 10721, 2026
Island joined the channel
2026-04-17 10731, 2026
lioncat6[m] has quit
2026-04-17 10757, 2026
kepstin
when creating a new release, you can copy the tracklist from an existing release, but it is a copy - modifying one later will not update the other one.
2026-04-17 10757, 2026
rgggn has quit
2026-04-17 10744, 2026
rgggn joined the channel
2026-04-17 10724, 2026
rgggn has quit
2026-04-17 10703, 2026
rgggn joined the channel
2026-04-17 10738, 2026
RandomMushroom12 joined the channel
2026-04-17 10738, 2026
RandomMushroom12
is search down? "Sorry, but your query could not be performed, because it appears you’ve been rate-limited. Either the server is overloaded or you’re making a lot of requests all at once."
2026-04-17 10750, 2026
RandomMushroom12
i'm not making a lot of requests all at once
2026-04-17 10722, 2026
zas[m] joined the channel
2026-04-17 10723, 2026
zas[m]
Yes, search down
2026-04-17 10716, 2026
RandomMushroom12
👍
2026-04-17 10733, 2026
hibiscuskazeneko joined the channel
2026-04-17 10733, 2026
hibiscuskazeneko
Did the bots break it?
2026-04-17 10703, 2026
elomatreb[m] joined the channel
2026-04-17 10703, 2026
elomatreb[m]
I know what it means but "the cluster is unstable" sounds like movie technobabble lol
2026-04-17 10739, 2026
thelittleoutside joined the channel
2026-04-17 10739, 2026
thelittleoutside uploaded an image: (422KiB) < https://matrix.chatbrainz.org/irc/v1/media/download/AdCH0N4Hzw20acXJF5c_l0h6DEKUqD0UUsHYOVJ2hrf5G6BR3XJhMivIIk8eNNKoKB54EbDrHHL7zyttAnh5VqJCedwDxVDAAGNoYXRicmFpbnoub3JnL3lxSEVlZkNTZXVscFdkSm1QTUZQYm1CdQ >
2026-04-17 10739, 2026
thelittleoutside
damn
2026-04-17 10756, 2026
thelittleoutside
ok it let me edit on the second time
2026-04-17 10727, 2026
jeffbyrnes has quit
2026-04-17 10718, 2026
Sharpie has quit
2026-04-17 10725, 2026
Sharpie joined the channel
2026-04-17 10740, 2026
shisma[m]
i assume the disc ids will also not be shared
2026-04-17 10732, 2026
elomatreb[m]
if the disc is the exact same you can add the disc ID to multiple releases
2026-04-17 10737, 2026
zas[m]
<hibiscuskazeneko> "Did the bots break it?" <- We don't know the cause, but it happened in the past
2026-04-17 10720, 2026
shisma[m]
I assume yes, but I should probably revert these edits since i cannot be sure. one submission changed track lengths by one second
2026-04-17 10732, 2026
ansg191 has quit
2026-04-17 10744, 2026
ansg191 joined the channel
2026-04-17 10720, 2026
elomatreb[m]
that doesn't sound unreasonable to keep then, a a single second can be a rounding difference if the release did not have millisecond-accurate track times before
2026-04-17 10748, 2026
elomatreb[m]
(you can't enter millisecond track lengths from the UI, but if the track length is submitted by a seeder or calculated from the disc ID it has millisecond precision)
