twask Posted March 11 Share Posted March 11 Hi, I have a purchased version of Poweramp build 976 which doesn't show/use tags on some FLAC files. On some files it doesn't even show the track time, but is able to play these tracks. Mp3Tag shows tags on these files just fine. I uploaded several files to https://1drv.ms/u/s!Ah6fXVV9ivrOiqVBs6dEVS0J6J9YCA?e=P3wQay The password on the link and on the file this link points to is "poweramp123" (no quotes around it). Thanks. Link to comment Share on other sites More sharing options...
andrewilley Posted March 11 Share Posted March 11 There is definitely something non-standard about those files, none of the embedded tags are readable in Poweramp. Also some of my PC music players (e.g. ZoomPlayer) also don't see the tags either, while foobar2000 and VLC do read them. The displayed title is being parsed from the filenames by the way, on the assumption they are in "<track#> - <title>" layout. Long-press on the song and select Info/Tags, and you'll see that no tag data has been accessed. TagScanner can re-save these files, but the tagging remains in the non-standard format. MP3Tag refuses to re-save them at all (just gives an error message) however it can re-save them after TagScanner has first processed them. At that point (after saving in TagScanner, and then re-saving in MP3Tag) they work. I'm sure @maxmp will be able to take a look at them, and perhaps design a workaround. I suspect it might be related to the embedded cover image data, which in these files comes first in the data area before the other tags. Removing the cover images in TagScanner causes the rest of the tags to become readable (without needing to double-save in MP3Tag afterwards). What app or source created the tagging data? Andre Link to comment Share on other sites More sharing options...
twask Posted March 11 Author Share Posted March 11 These tracks are sold by Bleep (Warp label). Link to comment Share on other sites More sharing options...
6b6561 Posted March 11 Share Posted March 11 I had a look at the file saving issue in mp3tag and found https://community.mp3tag.de/t/error-message-cannot-be-opened-for-writing/19020/14 ryerman says that the issue is that the picture sits in METADATA block #0 which should be used by the stream data. And the files uploaded by twask looks like they have the setup with an picture in block 0 METADATA block #0 type: 6 (PICTURE) METADATA block #1 type: 0 (STREAMINFO) METADATA block #2 type: 6 (PICTURE) METADATA block #3 type: 4 (VORBIS_COMMENT) METADATA block #4 type: 1 (PADDING) And for some reason the picture is twice in the file. Link to comment Share on other sites More sharing options...
6b6561 Posted March 11 Share Posted March 11 Looks like the issue is that the image sits in Block 0. I re-muxed the file with ffmpeg and that fixed the file so that the stream info is in block 0, the fixed file shows up correctly in Poweramp. Quote ffmpeg -i "07 - sinistrailAB air.flac" -acodec copy 07-Fixed.flac Link to comment Share on other sites More sharing options...
twask Posted March 11 Author Share Posted March 11 That's just sad. Bleep should've known better. Thanks for the pointers. Link to comment Share on other sites More sharing options...
andrewilley Posted March 12 Share Posted March 12 Yes, the early instances of the cover images seemed the mostly likely cause to me too, as confirmed by @6b6561 . It may be that Max can devise a workaround anyway, as some other programs such as foobar2000 and VLC appear to have done. Editing the tags with regular editors might prove more difficult though. Andre Link to comment Share on other sites More sharing options...
6b6561 Posted March 12 Share Posted March 12 Personally I would "fix" the files. There is a windows batch tool available for ffmpeg. I have no experience with the tool, but it looks like you can add a source directory including sub-directoryies and there is a "Recreate source path" in the output part of the screen shot. https://ffmpeg-batch.sourceforge.io/index.html Link to comment Share on other sites More sharing options...
andrewilley Posted March 12 Share Posted March 12 Also worth contacting the source company that sold the files ("Bleep") to explain they are creating out-of-spec files, which some applications can't process. I agree that fixing the files is the best overall solution (especially if there are only a few offenders) but if there are a lot of these in the wild then it might be worth trying to create a work-around for them in Poweramp too, as some other apps have done. Andre Link to comment Share on other sites More sharing options...
Solution maxmp Posted March 12 Solution Share Posted March 12 @twask thanks for the files. I've checked those and they don't have valid FLAC metainformation. FLAC format demands first block to be a METAINFO block (https://xiph.org/flac/format.html#metadata_block_streaminfo). As this is not true for these files (the image block is the first block instead), Poweramp consider those not to contain a valid metadata and skips parsing those tags quickly. Link to comment Share on other sites More sharing options...
twask Posted March 12 Author Share Posted March 12 Thanks. I'll fix the files and will reach out to the label about it. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now