+- Moode Forum (https://moodeaudio.org/forum)
+-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: Upcoming moOde 7 series (/showthread.php?tid=2856)
RE: Upcoming moOde 7 series - Tim Curtis - 09-15-2020
How common is the usage scenario?
1. Tracks contain MUSICBRAINZ_ALBUMID
2. Some portion of the collection consists of multiple copies of a given album each with different ALBUMID's
If this is going to be rare in the field then I could just go with the comment tag but if you think not so rare then it will likely have to be a configurable Library option.
RE: Upcoming moOde 7 series - TheOldPresbyope - 09-15-2020
Like I said, "Given the screwed-up metadata situation we face, there's probably no better solution."
MPD doesn't do anything with the MB fields. They got added because some user argued for them, there was a traceable definition for them, and Max deemed the addition to be benign. In the same way I was successful in getting "work" added to the MPD list so a multi-track work like a symphony, opera, etc., could be identified.
Picard's a nice tool but it has been problematic for me with classical music. Like its competitors', the MusicBrainz database is no better than the users' contributions to it.
Regards,
Kent
RE: Upcoming moOde 7 series - challenge - 09-15-2020
@Tim Curtis can't answer that question with real data.
I think it's in the very rare, but not sure. It's already rare to use full MBID tags, plus not many have multiple releases of the same album, on top of that using moode. I'd say very rare but what do I know.
For the light usage I do, I would be more than happy with the MBID grouping+ some way to quickly see comment from library view.
I think it's enough for me, but I'm just a random guy.
If someone has the need, then it's up to him reopen the issue.
@TheOldPresbyope, agree, luckily I'm not into classical music so I'm fine with it.
RE: Upcoming moOde 7 series - Tim Curtis - 09-15-2020
Ya, I think kinda rare scenario so what I think I'll do is display the comment tag and if in the future there is demand for having it be an option to display either the comment tag or the albumid part then deal with it at that point.
RE: Upcoming moOde 7 series - Tim Curtis - 09-15-2020
Here is with comment displayed.
[attachment=1640]
RE: Upcoming moOde 7 series - challenge - 09-15-2020
does it show only when you click on the artist (showing all albums of an artist in the bottom frame) like the screenshot or does it also show when you click straight to the album in the right frame (showing the album's tracks in the bottom frame)?
That's good but I have the feeling I'd like it to show also when I click on an album on the right column.
Does it makes sense?
e.g. I choose stevie ray vaughan, I see on the right two "In step" albums, I click on one and it should show the comment in the bottom frame on top of the track lists of that single album.
If you can make it do that too, then for my usage it would be perfect.
Maybe group it all as "show comment metatag in library view" option under Appearence, so everyone's happy, then I'd call it done.
RE: Upcoming moOde 7 series - Tim Curtis - 09-15-2020
That makes sense. It should take just a bit of added logic.
RE: Upcoming moOde 7 series - bitlab - 09-16-2020
(09-15-2020, 01:29 PM)Tim Curtis Wrote: Ya, I think kinda rare scenario so what I think I'll do is display the comment tag and if in the future there is demand for having it be an option to display either the comment tag or the albumid part then deal with it at that point.
Some posts agog @TheOldPresbyope states: This assumes that a user isn't already using the comment field for a different purpose.
And here we have that user ;-)
I'm afraid my comment value varies from empty to very multi line comments.
In advanceof the albumid/comment information final implementation, I did give the current git impl a try:
After adding the comment field to the library cache the load library json increased more then 25% in my case. Even with a toggle to show or not to show, the loading and memory use will be there. And knowning what is inside my comments I really don't like to see it.
There is and prob will never be a satisfactory solution to handle all cases out of the box. I would prefer that the user could supply only one field (default none) that should be extracted and shown here. If empty no penality for others.
And if the user then really would like to see something usefull here; with Picard or Foobar scripting you can then makeup a new field based one (parts of) multiple other fields.
For example if I would I could go for a combination of the media source, published label and country.
Regards,
Marcel
RE: Upcoming moOde 7 series - Tim Curtis - 09-16-2020
I was also wondering what the impact would be for always carrying the comment field in libcache.json.
I'll add a Library option as you suggested but prolly keep it simple like
Include comment tag [No ]
(i) This tag is currently used in the Library to display some identifying text to differentiate albums that have the same name but different MUSICBRAINZ_ALBUMID values. NOTE: Including the comment tag can impact the performance of the Library.
RE: Upcoming moOde 7 series - yannig - 09-21-2020
(08-02-2020, 01:33 PM)Tim Curtis Wrote: Hi,
Here's a preview of some the features the crew is working on for upcoming moOde 7 series :-)
Thanks to a wonderful contribution from @bitlab, audio enthusiasts that want more control over resampling are going to enjoy access to Custom SoX recipes and Selective resampling. Custom SoX recipes allows a set of low level SoX options to be configured. Selective resampling automatically upsamples or resamples based on the source rate and selective resampling mode.
Selective resampling:
Custom SoX recipes:
Does it mean it will be possible to manage lossless interpolation ?
(it seems not, but I ask anyway, but if so, I would love to have a choice of different filters)...