Jump to content

Kundun

Approved Members
  • Content Count

    48
  • Joined

  • Last visited

About Kundun

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. +1, I always thought to have a toggle switch to disable rounded corner in the default skin as a good idea
  2. +1 on this, it's less intrusive as a solution
  3. A few days ago I was also thinking that showing the complete YYYY-MM-DD everywhere may result in a bloated UI, so maybe it's a better idea to show that in the Years category only (when a specific year is selected)? Or maybe make it toggleable?
  4. I still suggest to use TYER+TDAT as the preferable method, and TYER in the YYYY-MM-DD format as a fallback method, maybe using a priority list like the following: TYER+TDAT TYER YYYY-MM-DD TYER YYYY-01-01 Just to give a little bit of context on why I suggest to do so: From a metadata tagging point of view I am a Picard user, and what Picard does is to store the TYER (YYYY) and TDAT (DDMM) in a compliant way, even though the input field is just a single "date" field where you can put YYYY or YYYY-MM-DD (Picard will update TYER only or both TYER and TDAT accord
  5. How do you achieve that collage album art for genre? I checked the Album Art settings but nothing related to that is in there.
  6. In MIUI 12 it is displayed grayed out as your one, but if you long press it it will open the app.
  7. The ability to specify a list of characters ('/', ';') or keywords ("ft.", "w/") to use as separators would be a nice addition. This can be useful for non-english users too, so a user can specify mit for German or con for Italian.
  8. If you want to do it automatically give Picard a try: https://picard.musicbrainz.org/ Try first with a single album as showed here: https://picard.musicbrainz.org/quick-start/
  9. I'm a Picard user too (and the idea for my topic came from that) and as far I can tell Picard operates with TYER, TDAT, TORY e TDOR. Even though the date field is displayed as a single field in the UI, when a date in the form of YYYY-MM-DD is inserted then the TYER and TDAT tag are set accordingly (instead of saving the full date in TYER). My suggestion for the implementation in Poweramp is to let the user choose which field to use (with some sort of fallback to TYER when the selected tag is not available) with a specific setting entry (leaving the current behavior as the default one) or to le
  10. Seemingly so simple? Several edge cases have been listed above, I don't see this feature as simple from an implementation point of view as a lot of users defined it to be honest.
  11. Hi there, I'm here to ask to support full date in sorting and grouping. If you have a tons of album from the same year it can be problematic to sort or group albums by year (plus this can be useful in the album view for artists with significant output in a single year, cfr. this). This can be implemented using the id3v2.3 tag TDAT or the id3v2.4 tag TDRC. A short summary (from id3 specification): TDAT:The 'Date' frame is a numeric string in the DDMM format containing the date for the recording. This field is always four characters long. TDRC: The 'Recording time' f
  12. I basically agree on everything you said, on the bullet separator too, so thank you for your contribution Andre
  13. So how can this be implemented effectively? Should we use a semicolon-separated list in the Artist tag and a general representive label in the Album Artist one? Let's take the 1977 album Cluster & Eno, composed by the homonimous musicians. Basically everywhere (RYM / Discogs / MusicBrainz) it is credited as it's titled (Cluster & Eno by Cluster & Eno), of course this isn't ideal, but what's the best solution to handle this case scenario? To just take the content of a single tag and split on ampersands is obviously a bad idea, since a lot of bands use them in their name (alrea
  14. I've read and partecipated in some Multi-arists related threads, but I don't see a general consensus on how it should be implemented, that's why I say that some community-dev interactions are needed.
×
×
  • Create New...