Jump to content

Kundun

Approved Members
  • Posts

    51
  • Joined

  • Last visited

 Content Type 

Profiles

Forums

Downloads

Poweramp Knowledge Base

База знаний Poweramp

Poweramp知识库

Poweramp Equalizer Knowledge Base

База знаний Poweramp Equalizer

Everything posted by Kundun

  1. I don't see the distinction here, do you mean that if I add some tracks of an album on the n day and then after that I add other tracks of the same album on the n+x day then the album will still be sorted as added on the n day? Isn't it how it should behave?
  2. From the Library home you can go in the Albums category and there from the 3-dots-menu you can select List Options -> Sort: by date added to Library
  3. +1, I always thought to have a toggle switch to disable rounded corner in the default skin as a good idea
  4. +1 on this, it's less intrusive as a solution
  5. 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?
  6. 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 accordingly to user input). From a desktop playing point of view I am an MPD (Linux) and Foobar200 (Windows) user, and both of them do recognize the TYER+TDAT combo properly. Those are just three examples of three popular apps (I mean, in their own niches) that do support the TYER+TDAT combo, so considering to use that as the preferable method (since it's id3 compliant too) is to me pretty logical, and having some sort of priority list like the one above (and by that covering more use cases) sounds like the right choice to me.
  7. How do you achieve that collage album art for genre? I checked the Album Art settings but nothing related to that is in there.
  8. In MIUI 12 it is displayed grayed out as your one, but if you long press it it will open the app.
  9. 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.
  10. 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/
  11. 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 let him create some sort of priority list (basically a fallback list) like: TDOR TORY TYER+TDAT TYER I'm still of the idea that TYER in the form of YYYY-MM-DD and TYER+TDAT should be implemented as a default behavior, but this TDOR/TORY can be a nice addition too. Just as an example mpd, an incredibly popular application (at least in the Free and Open Source world), supports TYER+TDAT by default.
  12. 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.
  13. 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' frame contains a timestamp describing when the audio was recorded. [...] The timestamp fields are based on a subset of ISO 8601. When being as precise as possible the format of a time string is yyyy-MM-ddTHH:mm:ss (year, "-", month, "-", day, "T", hour (out of 24), ":", minutes, ":", seconds), but the precision may be reduced by removing as many time indicators as wanted. Hence valid timestamps are yyyy, yyyy-MM, yyyy-MM-dd, yyyy-MM-ddTHH, yyyy-MM-ddTHH:mm and yyyy-MM-ddTHH:mm:ss. All time stamps are UTC. The TDAT tag was changed to the TDRC one in id3v2.4, but I suggest to support both of them (probably most of the time only one of those will be present, not both), since most of other players/taggers support only TDAT (probably due to parsing criticalities related to the variable timestamp length of TDRC). I myself use the TDAT tag only, it's just way more straightforward and more supported. If those fields are not present then a timestamp like "YYYY-01-01" can be inserted in the internal DB, as many others do in this case. I know that it will need a full rescan of the user music library to function properly, but by settings "YYYY-01-01" as the default timestamp this won't affect or break anything, since the fallback sorting will always be the alphanumerical order (as it is right now). Thank you for your job and have a happy new year! Related request: Choose Metadata Field for Year Сортировка альбомов
  14. I basically agree on everything you said, on the bullet separator too, so thank you for your contribution Andre
  15. 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 (already highlighted by Andre), but without taking that in account this is also wrong since the album would be listed under Eno (insted of Brian Eno), creating a second inconsistency. So to just parse a single string is a suboptimal solution, and that's why I think that the combo solution with Album Artist/Artist tags is the way to go (of course I'm not reinventing the wheel, this is how a lot of players/platforms handles multiple artists), so for the sake of this example the artist tag of each track should be "Cluster; Brian Eno" and the Album Artist one "Cluster & Eno". It has already been said how the Album Artist tag can be considered an additional grouping condition, so this one to me seems the most-straightforward way to implement this use case. Plus, this can be quite useful for genres that are very featurings-prone, even though I can see some edge cases so maybe to use other specific ID3 tags is a better idea. On a small side note, can we avoid to use semicolons in the UI in general? They're just incredibly ugly, I'm not talking about the tagging-side, just the visualization, spaced forward slashes are way more organic on the eye. Just look at: Miles Davis; Sonny Rollins; Red Garland; Paul Chambers; Philly Joe Jones Miles Davis / Sonny Rollins / Red Garland / Paul Chambers / Philly Joe Jones That may seems a futile detail but since we're here to talk, just my two cents. Hope this will be implemented soon!
  16. 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.
  17. Just remember that when you're buying a product you're buying the product as it is (especially if it is a one-time payment), the fact that Max tries to satisfy PA community requests is just a bonus. Seconding on the multiple artists tho, right now it's the feature that I'm missing the most, and I think that in order to reach a good implementation of it some community-dev interactions about the topic are needed here on the forum.
  18. The volume knob bug seems to be solved in 890, thank you Max!
  19. After updating to 889 I'm experiencing some issues with the volume knob. When adjusting the volume, the black window that usually contains the knob appears without showing anything but a tiny version of the colorful contour that was recently added (and some times without that too). I'm using a Xiaomi Mi9T with Android 10.
  20. Because ID3 tags are a way to store all types of album related-data, not necessarily only the ones needed to have a good-looking library, and since for me what a music player should do is to create an abstraction layer from what humans perceive as important in their music library and what's contained in their files, I don't see this request as that unreasonable (if I just want a raw display of my ID3 tags I can use a File Manager, right?). Plus: this is how Picard and MusicBrainz in general works with classical recordings (the first artist in the list is the most relevant one), and in a way it's more or less an open standard that everybody can agree with (Do you really want a list entry for every single combination of composer, singer, symphony, chorus, etc?)
  21. What about the idea to add the option to parse only the first artist in the list? I've seen this implemented in others players/scrobblers. This may seems unusual but if you listen to a lot of classical music you probably want a record to be under (e.g.) Ludwig von Beethoven , and not six duplicates of it under Margarete Bäumer, Heinz Sauerbaum, Manfred Hübner, Symphony Orchestra of the Mitteldeutsche Rundfunk, Chorus of the Mitteldeutsche Rundfunk, Gerhard Pflüger. This may be implemented on single album-level, but a general option in the settings would be appreciated too.
  22. I highly recommend MusicBrainz Picard , it basically automate all the tagging procedure + it will standardize your music naming using commonly-agreed conventions so you don't have to decide for yourself.
  23. Not here to self-promote my requests but we talked extensively about the implementation of something like that here (with a brief summary by Andre here), so if you're interested in it check it out
×
×
  • Create New...