Does the data in test.musicbrainz ever get reset? Or I can create tests against it?
2024-12-23 35818, 2024
LupinIII has quit
2024-12-23 35857, 2024
LupinIII joined the channel
2024-12-23 35844, 2024
sentriz has quit
2024-12-23 35828, 2024
sentriz joined the channel
2024-12-23 35826, 2024
Island_ has quit
2024-12-23 35844, 2024
reosarevok[m]
It does sometimes
2024-12-23 35831, 2024
reosarevok[m]
I wouldn't expect things to be unchanged. What are you trying to test?
2024-12-23 35833, 2024
vardhan_ has quit
2024-12-23 35852, 2024
vardhan_ joined the channel
2024-12-23 35827, 2024
Jigen joined the channel
2024-12-23 35809, 2024
LupinIII has quit
2024-12-23 35801, 2024
lazybookwyrm[m] joined the channel
2024-12-23 35801, 2024
lazybookwyrm[m]
Added a release with two vinyl mediums with automatic sequencing (<https://musicbrainz.org/release/7f95f3b9-c195-4b6d-bb91-a2f05a0db7d1>), one with Side 1 & 4 and the other with Side 2 & 3. Hadn't run into that before, wondered if it'd be valid to add a pseudo-release with manual sequencing?
2024-12-23 35818, 2024
ahvalmissaamine
📌
2024-12-23 35806, 2024
rustynova[m]
> I wouldn't expect things to be unchanged. What are you trying to test?
2024-12-23 35806, 2024
rustynova[m]
It was to create unit tests for detecting recordings with styel issues. But I probably won't change it after coding it once so it doesn't matter much
2024-12-23 35839, 2024
LupinIII joined the channel
2024-12-23 35848, 2024
Jigen has quit
2024-12-23 35816, 2024
MeatPupp3t21 has quit
2024-12-23 35834, 2024
___nick___ joined the channel
2024-12-23 35812, 2024
___nick___ has quit
2024-12-23 35832, 2024
___nick___ joined the channel
2024-12-23 35828, 2024
LupinIII has quit
2024-12-23 35846, 2024
MonkeyPython joined the channel
2024-12-23 35825, 2024
MikeM1 joined the channel
2024-12-23 35819, 2024
bwbuhse has quit
2024-12-23 35819, 2024
bwbuhse__ has quit
2024-12-23 35843, 2024
minimal joined the channel
2024-12-23 35847, 2024
reosarevok[m]
I mean
2024-12-23 35803, 2024
reosarevok[m]
There's nothing really forbidding you from creating new recordings to test with each time tbh
2024-12-23 35803, 2024
p9 joined the channel
2024-12-23 35854, 2024
kellnerd[m] joined the channel
2024-12-23 35855, 2024
kellnerd[m]
As part of another change, I am considering to change the wording of a phrase in Harmony and would appreciate a second opinion:
2024-12-23 35855, 2024
kellnerd[m]
"Submit ISRCs from $source to MusicBrainz" or "Import ISRCs from $source into MusicBrainz"?
2024-12-23 35802, 2024
kellnerd[m]
For the edit notes, I have the same phrase but with plain text release links, where I think that the same prepositions to/into won't work...
2024-12-23 35802, 2024
kellnerd[m]
"Submit ISRCs from $source_release_url to $musicbrainz_release_url" or "Import ISRCs from $source_release_url into $musicbrainz_release_url"
2024-12-23 35821, 2024
kellnerd[m]
Would you use "for $musicbrainz_release_url" in that case?
2024-12-23 35818, 2024
p9 has quit
2024-12-23 35800, 2024
sentriz has quit
2024-12-23 35856, 2024
mll joined the channel
2024-12-23 35844, 2024
p9 joined the channel
2024-12-23 35853, 2024
technonerd
is there a way to create a cue sheet from a musicbrainz entry? original is 1 single file per CD
kellnerd: I think "Submit ISRCs" makes sense as the text for the action; that also matches what people see when they authenticate to MusicBrainz for isrc submission tools.
2024-12-23 35826, 2024
kepstinbrainz
but I'd suggest using the "Import ISRCs…" version in the edit note
2024-12-23 35854, 2024
kepstinbrainz
I think that provides better context for people who look through the edit history later
2024-12-23 35829, 2024
kepstinbrainz
technonerd (IRC): hmm. that tool uses the musicbrainz tracklist as input, not the disc id, so it might end up being a bit off.
2024-12-23 35845, 2024
kepstinbrainz
if you know a specific disc id that matches your disc, you could make a more accurate cue sheet.
2024-12-23 35846, 2024
kepstinbrainz
(note that musicbrainz only stores the positions of the "INDEX 01" entries, not any of the other indexes, so the cue sheet will be incomplete for albums which use the more advanced/weirder cd features)
2024-12-23 35831, 2024
lusciouslover joined the channel
2024-12-23 35810, 2024
lusciouslover has quit
2024-12-23 35832, 2024
lusciouslover joined the channel
2024-12-23 35818, 2024
___nick___ has quit
2024-12-23 35824, 2024
joessexmpp joined the channel
2024-12-23 35835, 2024
joessexmpp has quit
2024-12-23 35840, 2024
MikeM1 has quit
2024-12-23 35810, 2024
petitminion joined the channel
2024-12-23 35837, 2024
Island_ joined the channel
2024-12-23 35822, 2024
soundandvision[m has quit
2024-12-23 35834, 2024
technonerd
theres disc id to match
2024-12-23 35838, 2024
technonerd
its a single file
2024-12-23 35842, 2024
kellnerd[m]
Thank you for your opinions bitmap and kepstin!
2024-12-23 35825, 2024
kellnerd[m]
So I will keep using "Submit from/to" for the release action, I have probably chosen it in the first place because of the MB permission.
2024-12-23 35850, 2024
kellnerd[m]
Good point about the different context of the edit note, I hadn't thought about having two different wordings.
2024-12-23 35819, 2024
kellnerd[m]
It makes sense to use "import" for these as this was the place where "submit" started to feel odd for me.
technonerd (IRC): cueshit might not be the best fit for multi-disc releases, it ignores the disc boundary as all supported formats (except MB) do not support mutliple discs/files.
2024-12-23 35845, 2024
kellnerd[m]
It generates one long cuesheet for a file which covers both discs.
2024-12-23 35822, 2024
kellnerd[m]
Track lengths are also only accurate to the second, you only get millisecond/frame precision if you submit a TOC / DiscID to MusicBrainz.
