can someone please tell me what syntax to use to search for the release when using "search for similar tracks" with a single/one track? With an album I use successfully mbid, I tried that with one tracks and it doesn't work, I can use rid to search for the recording but I don't want that, I want to search using the specific ID of the release
2023-12-13 34727, 2023
yvanzo
Hi Imbecile9506
2023-12-13 34715, 2023
yvanzo
Where does it take place exactly? When editing the tracklist in the Recordings tab of the release editor?
2023-12-13 34713, 2023
Imbecile9506
Hi, sorry I forgot to say that I'm talking about Picard
2023-12-13 34732, 2023
yvanzo
Imbecile9506: You can use `reid:` instead of `mbid:`
2023-12-13 34755, 2023
yvanzo
(it stands for release id)
2023-12-13 34732, 2023
yvanzo
(whereas `rid` stands for recording id)
2023-12-13 34714, 2023
Imbecile9506
I tried with reid and it didn't work though maybe was because the entries were too recent, I'll try again next time, thank you!
if instead of searching you directly want to load a specific recording as a standalone recording you could also enter "recording:a8ce148c-48a9-4d38-84ed-2f9d22eacbb7" in the search field in the main window and Picard will load this recording directly
2023-12-13 34744, 2023
outsidecontext
sorry, I didn't see you want to search for the release ID. Yes, then reid is correct, e.g. "reid:reid:7e8a850a-ed19-4de5-b2a9-61b87218124b" will work.
2023-12-13 34746, 2023
insane_22 joined the channel
2023-12-13 34720, 2023
minimal joined the channel
2023-12-13 34724, 2023
thuna` has quit
2023-12-13 34741, 2023
thuna` joined the channel
2023-12-13 34747, 2023
thuna` has quit
2023-12-13 34701, 2023
thuna` joined the channel
2023-12-13 34714, 2023
petitminion joined the channel
2023-12-13 34704, 2023
AJ_Z0 has quit
2023-12-13 34728, 2023
Ovalelephant joined the channel
2023-12-13 34734, 2023
Ovalelephant has quit
2023-12-13 34739, 2023
AJ_Z0 joined the channel
2023-12-13 34702, 2023
pranavkonidena has quit
2023-12-13 34700, 2023
petitminion has quit
2023-12-13 34747, 2023
insane_22 has quit
2023-12-13 34726, 2023
pranavkonidena joined the channel
2023-12-13 34744, 2023
insane_22 joined the channel
2023-12-13 34752, 2023
insane_22 has quit
2023-12-13 34707, 2023
pprkut has quit
2023-12-13 34737, 2023
mll has quit
2023-12-13 34727, 2023
mll joined the channel
2023-12-13 34705, 2023
Cheezmo has quit
2023-12-13 34732, 2023
Cheezmo_ joined the channel
2023-12-13 34748, 2023
pprkut joined the channel
2023-12-13 34702, 2023
ttpcodes has quit
2023-12-13 34720, 2023
ttpcodes joined the channel
2023-12-13 34716, 2023
Cheezm___ joined the channel
2023-12-13 34728, 2023
petitminion joined the channel
2023-12-13 34752, 2023
Cheezmo_ has quit
2023-12-13 34753, 2023
petitminion has quit
2023-12-13 34755, 2023
petitminion joined the channel
2023-12-13 34727, 2023
outsidecontext
zas: the picard CI build issues were caused by pyqt6 version mismatch caused by our requirements.txt and the latest release. fixed now (currently test building also a fix for macos)
2023-12-13 34747, 2023
outsidecontext
also with pyqt6.6 / qt6.6 the dark theme flickering is gone on my system
2023-12-13 34730, 2023
ttpcodes has quit
2023-12-13 34743, 2023
ttpcodes joined the channel
2023-12-13 34712, 2023
outsidecontext
I still would like to see that we integrate the PyQtDarkTheme thing you posted. The default dark colors are horrible, at least on my system. It's all just the same very dark color, I can't even see window / dialog borders
2023-12-13 34744, 2023
petitminion has quit
2023-12-13 34752, 2023
outsidecontext
sorry, the above was meant for #metabrainz dev channel (will continue there)
