Poweramp builds 978-988

[Ash Roarshock]

On 1/16/2024 at 6:05 AM, andrewilley said:

@AiM__FreakZ: the functionality may be skin-dependent. It doesn't work for me using the current release of YAPS for example.

Andre

Yeah doesn't work for me either using yaps

[Pav0]

This version + Android 14 is broken af

trying to view any album/adding songs to queue screws up the UI badly and the Hi-Res output its still not available but i guess that's more on Android 14

[andrewilley]

@Pav0 That's not the default skin, please try using the standard skin(s). If that seems OK, please raise this issue with the developer of the skin you are using. If it happens with the default skins too, please could you elaborate on exactly how you reproduce this issue.

You are right that some Android 14 ROMs don't support the Experimental Hi-Res feature (my own Samsung Galaxy A54 is an example, even after a few monthly maintenance updates). Please try using AAudio instead.

Andre

[Pav0]

@andrewilley Ok, i just recreated the issue with the default skin, take a look at the video i just recorded about it
The Hi-Res issue is not that big of a deal since my dac kinda takes care of it so i can leave that aside for now.
https://photos.app.goo.gl/hJpV4hNSpyMs9wr57

[andrewilley]

@Pav0 I can't seem to duplicate this at all on my system with as close as I can get to what seem to be your settings. Is the step of selecting a song and tapping 'Play Next' required to create the problem for you, as on your video I didn't see the normal toast popup saying the song had been added into the Queue. And then after that you seem to tap the Albums link at the top of the page several times but nothing happens at first? It seem to works fine with all of those steps for me anyway (tested on a Galaxy A54, Android 14) so we'll probably need @maxmp's input.

But to stop the Hi-Res error message, just use AAudio instead and select your higher resolution mode within that method.

Andre

[Pav0]

@andrewilley weird.. Im using a Galaxy A73 5G (essentially the same phone) yet it behaves quirky like that 

[andrewz]

Even after resetting my Xperia 10 IV on Android 14, I continue to have these issues with the latest beta build:

- playback does not start after I connect my wired headphones, even though setting is correct

- memory card keeps disconnecting

- I'm getting crashes (sorry, no crash log)

[Ash Roarshock]

I saw the headphones not playing also.

Xperia 5 II

[andrewz]

On 2/29/2024 at 12:09 PM, andrewz said:

Even after resetting my Xperia 10 IV on Android 14, I continue to have these issues with the latest beta build:

- playback does not start after I connect my wired headphones, even though setting is correct

- memory card keeps disconnecting

- I'm getting crashes (sorry, no crash log)

It turned out that part of syncing my Android device to Google account is not power management settings. After the reset, I set power saving features again to not interrupt with Poweramp. Some of the issues may be caused with that. I will report my findings later.

P.S.: How about some kind of warning when first launching Poweramp? "For uninterrupted playback, turning off power saving features on your phone may be required. Do you want to check it out right now?"

[andrewilley]

@andrewz No, power management settings probably would not get synced to a new phone, it'd be up to you to enable them as and when wanted. Not all devices are so aggressive about it, but if you are getting playback issues (especially when the screen goes to sleep) it's a good one to check.

Andre

[andrewz]

On 3/2/2024 at 11:58 AM, andrewz said:

It turned out that part of syncing my Android device to Google account is not power management settings. After the reset, I set power saving features again to not interrupt with Poweramp. Some of the issues may be caused with that. I will report my findings later.

P.S.: How about some kind of warning when first launching Poweramp? "For uninterrupted playback, turning off power saving features on your phone may be required. Do you want to check it out right now?"

Sorry for blaming Poweramp for my issues. There's clearly something wrong with my microSD card that keeps disconnecting. When playing content from the card that gets disconnected, it leads to Poweramp crash.

[andrewilley]

@andrewz If storage unmounts, or a filesystem error is encountered during playback, PA should first try to skip the problem song and then after a few consecutive skipped songs it should give up and stop playback. It should not crash though.

Andre

[andrewz]

24 minutes ago, andrewilley said:

@andrewz If storage unmounts, or a filesystem error is encountered during playback, PA should first try to skip the problem song and then after a few consecutive skipped songs it should give up and stop playback. It should not crash though.

Andre

Although faulty microSD card or reader should be primarily blamed in my case, Poweramp build 981 really crashed when I play something from my (occasionally faulty) card and physically remove its tray while playing.

[andrewilley]

@andrewz I'd never suggesting hot-swapping SD Cards anyway without unmounting first, quick way to kill them. I turn my phone off before messing with the SIM/SD Card slot.

Andre

[MotleyG]

3 hours ago, andrewz said:

Although faulty microSD card or reader should be primarily blamed in my case, Poweramp build 981 really crashed when I play something from my (occasionally faulty) card and physically remove its tray while playing.

This is a quick way to cause file errors at a minimum, or brick a card if it is writing index updates when it gets removed without unmounting it while the device is on. Eject the card using the settings, or power the device down first.

[andrewz]

3 hours ago, MotleyG said:

This is a quick way to cause file errors at a minimum, or brick a card if it is writing index updates when it gets removed without unmounting it while the device is on. Eject the card using the settings, or power the device down first.

It started to disconnect by its own many weeks ago. I wouldn't experiment with it if it wasn't already dying. Instead of a crash, I would like to see a warning like "Memory card disconnected. Do not remove the card without unmounting it first. If you did not disconnected it yourself, it might be a sign of the card failing. " in Poweramp. Thanks for your hint though.

[andrewilley]

@andrewz As I said, PA should not crash just because storage has become unmounted or a file is missing. It should try the next file, and then after a few more tries fail gracefully and stop with a message saying "too many failed files". If it is crashing, it's due to something about the storage crashing rather than unmounting.

You could try reformatting the SD Card and copy everything back to it, but it could be the card is faulty or the phone is not contacting to it properly.

Andre

[MotleyG]

6 hours ago, andrewz said:

Instead of a crash, I would like to see a warning like "Memory card disconnected. Do not remove the card without unmounting it first. If you did not disconnected it yourself, it might be a sign of the card failing. " in Poweramp.

I think this may be more of an OS level issue though. If storage is removed while in use, Android may be having the meltdown. And since Poweramp was the app in use at the time, it could be that the OS kills it simultaneously. 

[Loweaul]

So I was about to reply someone's question in other forum, it's a question of turning the Lyrics Background off, well I tried, but it seemed like it didn't work the way I wanted, here's the picture of 3 situations.

Apparently if I want to turn the Lyrics Background off, I have to turn both of the Lyrics Background and the List Background off, which is strange, I believe that the person who asked for this must met the same issue like this. Indeed it is a subtle issue.

PA Version 981

[frankmaxon]

Some tracker modules (like this) have subsongs which aren't playable currently. I can suggest listing them separately from the main file like how FLACs can have different cue points in a single track.

Also, internal texts in Lyrics look messy without monospace font. Would be nice to be able to change it like in the widget.

PA Version 981

[andrewilley]

@frankmaxon I think the fact that it plays at all is pretty astounding.  I'd never of this as an audio format until I Googled it. I rather doubt that there's likely to be much support for submodules or wide-screen monospaced comment text though.

On the plus side, you probably get the award for most obscure file-format question of the year so far. 👍

Andre

[Loweaul]

Just accidentally found an issue, I was about to add a new song to my playlist, but then I tapped the wrong button, and it went like this (video down here).

 

To reproduce it,

1: you select a random song, and hit the button "Add to Playlist" ,

3: long press a playlist,

4: hit the button at the top right of the bar "Add New Playlist", and then you cancel it. 

Boom, the selection bar is floating in the middle of the screen. So the action 3 is crucial, the issue won't come out if you don't do it in the first place.

[andrewilley]

@Loweaul Not quite sure why this is a bug? When you cancel the '+' function for creating/naming a new playlist, it just takes you back to the original screen for choosing existing playlist(s) instead. You can just close that screen if you want to cancel and leave the 'Add To Playlist' function completely.

Andre

[Loweaul]

@andrewilley Oh, so what I meant a bug is that these movements I listed up there caused an issue of animation, in the normal situation, the "Playlist" area should fall down to the bottom of the screen after I cancel the "Add to Playlist" function, right? But as you can see in the video, it just floated in the middle of the screen, there was something wrong with the animation, yeah, in my opinion.

[andrewilley]

@Loweaul Ah, OK, in which case yes I agree that the remaining selection list can become centred rather than being tethered closer to the bottom of the screen. Might be something to do with the keyboard popping up previously? Has no functional implication that I can see though, as the background elements are not accessible either way.

For some reason it doesn't seem to happen all the time though - I can't get it to occur now for example. And some popup menus present themselves mid-screen anyway. e.g. the long-press popup shown on the Player Screen is text-oriented and in the middle of the screen, whereas the popup triggered by long-pressing in a list is a smaller icon-based format at the bottom (to allow you to still access and scroll the background list). If the background is not going to still be accessible, I think I prefer a centred approach, as tall as necessary/possible to avoid needless scrolling.

Andre