Jump to content

MadMaxster

Approved Members
  • Posts

    7
  • Joined

  • Last visited

 Content Type 

Profiles

Forums

Blogs

Gallery

Downloads

Poweramp Knowledge Base

База знаний Poweramp

Poweramp知识库

Poweramp Equalizer Knowledge Base

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

Store

Events

Ideas

Everything posted by MadMaxster

  1. Just want to say a big 'THANK YOU!' to the developers and the forum as the latest version has this feature now and it's working just great as far as I can see. Very happy user here! 😁
  2. I tend to agree with you that this is unlikely to happen unless there's a major overhaul scheduled. Nevertheless I've been able to say my piece and stated my view on how it should be improved, so I'm thankful for this forum. It's my number #1 gripe with Poweramp but still it's not big enough to make me switch to something else right now. Still love it! Thanks for the constructive discussion!
  3. Agreed - this would need to be applied to all fields to work properly, not just AlbumArtist. But if you could insert the flatten routine to create the multiple pointers all of which have a single item per tag then the engine should just work as normal. e.g. A;B gets interpreted as both A & B pointing to the same file. Care would have to be taken for duplicate files in queues though.
  4. No changes are required to tags, it's how Poweramp interprets them here is the question. Just because it is the way it is now, doesn't mean it can't be better. What I see today is if I have a library : A;B A;C B A;D I see A/B, A/C, A/D, B as separate entries. I should be able to go select A and see all files except B I should be able to go select B and see A;B file and B file etc. Are you really saying that seeing : A/B, A/C, A/D, B is better or more correct than just seeing : A, B, C, D I do agree that this is probably a sizable change to the way Poweramp stores the database, but just because it's a large change doesn't make it not worth pursing (or incorrect) and be in line with the way other music programs handle this scenario.
  5. I didn't go through the sorting expected for the example breakdown. So if I sort by : Album I can access this file under : 1 single album - Encore Artist I can access this file under : Eminem only AlbumArtist I can access this file under : Eminem OR Dr. Dre So if I sort by : Album I can access this file under : 1 single album - Encore Artist I can access this file under : Eminem OR Dr. Dre AlbumArtist I can access this file under : Eminem I find it's rarer to have mutliple AlbumArtists on Albums, compared to multiple Artists. For this reason today I pretty much use list by AlbumArtists exclusively in Poweramp to ensure that albums are grouped together. But multiple AlbumArtists are much more common on singles and Poweramp doesn't refactor them under individual artists right now.
  6. Thanks for the conversation and suggestions, but I'm not sure why this is so complicated. For me it's boils down to just parsing for ';' in albumartist tag and adding to multiple artists instead of recognizing it as a unique string. This is just creating multiple pointers to the same object/file and allowing you to find it by different paths. It's up to the user to get the tag itself correct and the tag content determines where the albums show up in the listing. For Andre's genre example : 40 songs :5 pop, 10 rock, 25 'rock;pop', I expect 35 in Rock and 30 in pop exactly like you say. If I want to play Rock I do expect to get 35 files, if I want to play Pop I do expect to get 30 files, and the player should be smart enough that if you select all genre's to only add the file once (by default) (multiple pointers resolve to the same file so don't re-add), so I get 40 songs. (I find it useful to think about this with Venn diagrams, each song can only be a single element in the venn diagram, but you can draw different collections around objects to group them) Artist and AlbumArtist are two unique tags and as far as I know completely separate relationship (e.g. I can put Artist:Kate Bush, AlbumArtist:Rage against the Machine if I so wish). So for Absintheque's example : Artist: Eminem, Album Artist: Eminem; Dr. Dre, Album: Encore This should be broken down to simple single elements and handled with pointer to the same file under : Artist: Eminem, Album Artist: Eminem, Album: Encore AND Artist: Eminem, Album Artist: Dr. Dre, Album: Encore and likewise : Artist: Eminem; Dr. Dre, Album Artist: Eminem, Album: Encore should be broken down as : Artist: Dr. Dre, Album Artist: Eminem, Album: Encore AND Artist: Eminem, Album Artist: Eminem, Album: Encore Having stuff show up in multiple places is fine by me. I control the tag content, but I need Poweramp to do the tag breakdown and simplification to multiple pointers. This is what other programs do to handle this scenario. Thx! glad this is getting some chatter at a minimum! Again I love this product.
  7. I came to this forum for this EXACT reason. I'm using mediaMonkey as my music organizer and it also uses semicolon to separate artists on albumartists tag. So if I have artists 'A;B;C' for albumartists tag, I would expect an album to be available under artist 'A' or 'B' or 'C' but instead it just groups under "A/B/C' which relies on me remembering the artist name 'A' to find it again (by scrolling without using search) Also if I have another album with 'X;B;Z' for albumartists tag then I can't get both albums for 'B' to show up together, I have two entries 'A/B/C' & 'X/B/Z' but nothing under 'B' itself. Add mediamonkey to the list (FooBar, Logitech Media Server as previously mentioned) which supports this parsing of albumartists this way also. Poweramp is awesome and I use it every day! Please make this enhancement to make it 'awesome'er' 😊 Thanks!
×
×
  • Create New...