Poweramp builds 867-871

[maxmp]

 

https://play.google.com/apps/testing/com.maxmpz.audioplayer

[invaderzim]

Thanks Max for the new update!

[invaderzim]

Hi Max, I have noticed the BITRATE and other info wasn't shown in the Track Info when the track is not played. As far as I remember, this wasn't PA's behavior before. Now, in order to know the bitrate, you will have to tap the track to play first. Can you please allow retaining those info even if the track is unplayed?

[PChwdhry]

Thank you.

[maxmp]

@invaderzim Bitrate and other loaded-only information may NOT be shown when track has no that meta-information in "tags" (depending on format, in tags or other header), as Poweramp doesn't load track into the audio engine when Info/Tags is used to recalculate those. If info exists in the track, it's shown. 

[invaderzim]

26 minutes ago, maxmp said:

@invaderzim Bitrate and other loaded-only information may NOT be shown when track has no that meta-information in "tags" (depending on format, in tags or other header), as Poweramp doesn't load track into the audio engine when Info/Tags is used to recalculate those. If info exists in the track, it's shown. 

Hi Max, all tracks have that meta-info. As you can see in the pictures provided bitrate appears when PLAYED. Unplayed tracks (eventhough they are properly tagged (due to OCD), bitrate does not appear. So I am sure they should show nonetheless.

[ScarletNeko]

22 hours ago, invaderzim said:

Hi Max, I have noticed the BITRATE and other info wasn't shown in the Track Info when the track is not played. As far as I remember, this wasn't PA's behavior before. Now, in order to know the bitrate, you will have to tap the track to play first. Can you please allow retaining those info even if the track is unplayed?

I noticed that too, files that previously were showing things like the bitrate and gapless, they aren't showing now after the update...

Also, I do have a request. Is there a way to show the bitrates of VBR tracks updating when they are playing? Something like, refreshing 2 times a second maybe. It's not something urgently necessary, but I would like if that could happen, and I think some other people might enjoy it as well.

And thanks for the updates ^^

[maxmp]

@invaderzim If you think it doesn't show bitrate for specific file, please share it with me (preferable within Poweramp itself / list / long press / Send / Gmail / gpmaxmpz@gmail.com) for tests.

Mp3s in the wild often do not contain bitrate information (esp. vbr ones) and average bitrate is only available when track is fully loaded into the audio engine.

[invaderzim]

1 hour ago, maxmp said:

@invaderzim If you think it doesn't show bitrate for specific file, please share it with me (preferable within Poweramp itself / list / long press / Send / Gmail / gpmaxmpz@gmail.com) for tests.

Mp3s in the wild often do not contain bitrate information (esp. vbr ones) and average bitrate is only available when track is fully loaded into the audio engine.

Max, that would mean I'd be sending my entire collection as I've said all of them are tagged properly. ScarletNeko even noticed this issue. Again, let me reiterate, the bitrate doesn't show in the Info/Tags when the track is NOT played. Most of my tracks are on FLAC. If you go back to yhe pictures in the previous post, the first screenshot is when the track is PLAYED. The second (bottom one) is an idle track/UNplayed. Hope I made myself clear. 😅

[ScarletNeko]

Yeah that would be a really hard thing to do as this happens with every file now. 98% of what I carry with me on my phone are properly encoded flac files, and a few others. There's some wavpack, alac, tak and ogg files, mostly that I encoded myself. They're all properly tagged, and before they all showed that info. I can rollback to an older version to send some screenshots as well if needed. I might try to send a few files but it would be only a small demo as my upload rate is abysmally slow.

[M Akmal]

Thank you for update

Anyway, why is the OPUS file (or OGG file containingOpus format) marked as stream?

[maxmp]

@M Akmal Can you please share that track (gpmaxmpz at gmail.com). Thanks!

@ScarletNeko The next 868 build has improved bitrate recognition for the Tag/Info dialog, thanks for your report.

[maxmp]

Build 868:

• Settings Export/Import now also exports/imports reverb presets
• track menu slight reorganization
  Added Genre navigation, menu is now 1 line smaller
• new User Agent option
  Used for streaming
• improved gapless for iTunes mp3s
• Poweramp API improvements
• bug fixes and stability improvements
• translations updates

[andrewilley]

4 hours ago, maxmp said:

Build 868:

• track menu slight reorganization
  Added Genre navigation, menu is now 1 line smaller

Thanks Max. Could I suggest it would make more sense to swap the positions of 'Lyrics' and 'Info/Tags'? It just seems to make more sense to have the generally similar 'Album Art' and 'Info/Tags' options shown next to each other on one line. And maybe some sort of subtle divider line to separate the lower four items (Artist/Albums/Folder/Genre) from the other actions as they have similar functionality? Just a thought.

Andre 

[invaderzim]

11 hours ago, maxmp said:

 

@ScarletNeko The next 868 build has improved bitrate recognition for the Tag/Info dialog, thanks for your report.

Thank you, Max for the update! Appreciate it a lot.

[ScarletNeko]

Hmm things still behave a bit weird with the info page, the difference I noted is that now most tracks show stereo at least. But looks like it's some kind of pre loaded info as I tried a 6 channel track and it was showing stereo before I played it. For the things to be showed correctly I need to play the file once and it needs to be on this version as files I've played days ago also has this behavior. The pictures on the left are after I just started the track, and on the right is before I did it. There's various formats as it can be seen on the file name. Also noticed the samplerate also gets messed up on some occasions.

Some info about the files:

1st TAK: Got the album in DVD Audio format. Audio was extracted with DVD Audio Extractor to uncompressed wav. Encoded to TAK with TAK 2.3.0 GUI at p4m settings. Added tags with foobar2000.

2nd ALAC: got it as an uncompressed wav file. Kept it on my PC as wavpack. Changed back to wav with wavunpack and encoded in ALAC with qaac x64 2.68. The encoder optimzed the file and I added the tags with foobar2000.

3rd FLAC: It was a rip made with EAC, I believe 1.0b. I keep the Flac+Cue on my PC. Used foobar2000 to split the image file to the separated tracks. Foobar used reference libflac 1.3.3. The tags were copied in the process. This CD is fully and completely gapless.

4th AAC: Got the file from a friend, he does some editing and messing with audio. It's a version he did with 6 channels of a music track. Don't know for sure how the file was made, but I know he exports files directly from a DAW and I think it used a very old version of qaac.

All those files are located on a 128gb SD card. It's a decent UHC1 Class 10 SanDisk one. LG G7, Stock 9.0.0 ROM, no root.

[invaderzim]

@ScarletNeko  thanks for the update. I just checked and got the same as you. Left image is when the track is playing. Right image, same track but stopped with another track playing in the background.

[maxmp]

@ScarletNeko @invaderzim Unfortunately such difference is inevitable, this is due to difference in bitrate calculation between tag reader and audio engine:

- tag reader is optimized for speed, it doesn't check some format details, may "include" more data into the audio
- audio engine loads file fully and have better (or slightly different for some formats) understanding of the audio data

@ScarletNeko Some additional polishing for formats like tak is possible, but that requires those (pretty large) files for tests.

[invaderzim]

1 minute ago, maxmp said:

@ScarletNeko @invaderzim Unfortunately such difference is inevitable, this is due to difference in bitrate calculation between tag reader and audio engine:

- tag reader is optimized for speed, it doesn't check some format details, may "include" more data into the audio
- audio engine loads file fully and have better (or slightly different for some formats) understanding of the audio data

Then per my understanding, PA should load the correct bitrate value regardless if the track is played or not. Bitrate is not something you manually assign in a tag editor.

[maxmp]

@andrewilley Generally yes, I would prefer Info/Tags + Lyrics on one line, but in some languages, these labels are too long and don't fit. I'll try to request shorter translations for those.

[maxmp]

@invaderzim Some formats support bitrate indication (e.g. cbr mp3), but many tracks in the wild will have no such information at all. Many formats have no such information provided in the header and bitrate should be calculated. Some formats (or tracks, even if format supports that information) have only partial information provided or no information 

E.g. vbr mp3 may contain no any header or relevant tags and whole file should be decoded fully to learn its duration and bitrate with 100% accuracy. Otherwise we can just approximate based on byte size of the file minus various headers. This is why the calculation introduces difference.

[andrewilley]

Perhaps when a calculated VBR bitrate value is displayed (rather than an explicitly provided one) it could be shown with a tilde to indicate the value is approximated? e.g. "~970kbps". But to be honest, does it really matter if that value is 100% accurate anyway, it's only a variation average so a ball-park figure ought to still be useful. 

Andre

[ScarletNeko]

When I go to a place with better connection I'll try to upload some various Tak files for testing. Resolutions, embedded cues and all. But that might take a little while.

About the info screen, what about the file format? One noticeable thing is, the info screen only shows the format after the file was played once. Notice on the right side of my screenshot that files don't have the format, while in the left side they do. The file format shows on the lists but only show on info page after the file has been played.

Also, would it be possible to make like, a switch so we could choose between an accurate and slower tag scan, or a fast and not so accurate tag scan? Or that would be going too far? Me for example, I could trade some speed for more accurate readings, but I can see things getting harder for yet bigger libraries or slower storages...

And about that request from a few messages ago, would that be possible? To show the actual bitrate of VBR files being updated once or twice a second? I really think that would be a very interesting feature.

Thanks for the attention '3'

[invaderzim]

Hey @maxmp, I really appreciate having the bitrate showing in Info/Tags. My reason why this is important is due to some tracks having been on a compilation album other than its own, so they appear in my collection being doubled/tripled. I use the bitrate to compare and most of the time the higher the bitrate sounds better or have been ripped of a higher quality. I noticed when a track is idle, the bitrate is the "correct" one. Correct in the sense that it is constant to my findings hehe. I checked with foobar2000 at the same time thru Windows by clicking the track's properties. Then, when played in PA it adds a few numbers, in my case a FLAC with 826kbps when idle. Playing the track change to 830kbps. I am now satisfied with my findings and hoping worthy to share.

[Red Balooon]

Small problem with one of the two widgets I use.  The 1 X 1 widget allows me to put a playlist on the home screen and to play that playlist, randomized, just by touching the icon.  I love that feature, and have a whole bundle of playlist shortcuts set up to do that.  Since the last update, though, when I touch the icon for any playlist, the only thing that happens is that Poweramp opens to the last music played.  I tried reinstalling different playlist widgets, but it doesn't help.  I also tried turning off any battery savers or other restrictions, and that also did not work. I know this can be fixed because it was working beautifully only a few days ago.  Thanks for any help.