maxmp

Some support will be eventually added as the idea here is voted, but it's not even of first page of requests - please vote (https://forum.powerampapp.com/ideas/idea/40-bit-perfectno-resample-mode-for-usb-dacsdaps/ ). I would add that this kind of usb "driver" solution (it's not a driver) is not a silver bullet. It won't work for all USB devices + Android phones. I would say that native Android DAC support works with larger number of devices vs any of the players utilizing libusb, just because Android uses narrower subset of DAC features. For example some Pixel devices may just disallow direct DAC access completely. Or particular DAC won't work on Samsung OneUI 5.x, not matter what, etc.

@Dryst the option is: Headset/Bluetooth -> Resume On Bluetooth. If it's still started, then either bluetooth headset looks like generic headset (then Resume on Wired Headset option may help) or the vehicle headunit explicitly sends Play commands and Poweramp complies. I would suggest first disable such auto resuming option on the other side, but there is also new option Ignore Bluetooth Commands (beta builds). Thanks!

This will be fixed when skin is updated, and that will happen when the stable Poweramp build is released. I would suggest disabling this feature temporarily in the skin. Thanks!

@Mark89 1. Until idea feature is planned to be implemented 2. they will move up when higher voted ideas get implemented 3. the deadlines are not possible 4. if it's possible technically - yes. The voting helps prioritize one features over other. No addon app is planned.

@kamaleon what post?

Poweramp-v3-build-last-uni.apk is usually updated to last stable build. The link stays, while the linked file can be changed. This is a specific support link which can be changed/removed/replaced in future without warning. I would suggest discussing the support related issues with support via email to avoid any further confusion (if there is any). Thanks!

@6b6561 for what purpose? Currently backup is able to collect all the images into one big zip.

@Shafeer Painkal #5 - why exactly it can't start? What do you see in the Last Processed Commands right after the call? The most probably cause of this - app is being killed while paused due to not all the necessary background "permissions" granted (https://dontkillmyapp.com/xiaomi)

@Indra Markam thanks for the request, but Poweramp UI architecture follows some logic, which this kind of transition will break. The songs shown on player screen (with transport buttons << > >> and big cover) are "physically" the same objects which are in the target played list (folder, playlist, etc.). This is clearly visible when you transition from that screen to a list and back. So, transitioning from mini player will be illogical as we never transitioned to the miniplayer at first place. It's possible to change UI transitions to do that, but there should be a good cause for this as it's a lot of effort to gain what, exactly?

@cquinn If no other error messages appear (such as no enough space) - I yet to see root cause of this issue other than in the article linked above.

@Joey R thanks for the detailed review of your quest with the builds;-) First, support can't spend much time investigating possible users issue, as users like to sparsely disclose issue details and there is no point in investigation for issue in "last" user build, which is usually one-two year old one, so the support guy will as to install the stable build (it's 976 - Poweramp-v3-build-last-uni.apk, but it will be updated to whatever next stable build will be). The beta build is currently 980 as Andrew indicated above.

@heula sending Log from within Poweramp -> Settings -> Support may help with investigating what is wrong, but root cause is the same - no files are available to Poweramp. As for any folders and storages, on recent Androids nothing will be scanned and added automatically to Poweramp, adding those folders via Settings / Library -> Music Folders (or lists header menu -> Select Folders) is required and if it's a new/different sd card, stick (or reformatted), it requires that kind of selection. File Managers have no problem immediately showing that as they have appropriate permission, which is not available to music players on Play, though it's available for the Poweramp website (-uni-) build - Settings -> Library -> File Access Legacy Mode option.

@NickIst thanks for the report and feel free to send the affected files for tests to gpmaxmpz@gmail.com

Btw I can't reproduce issues with ratings in lyrics UI. I can set ratings there and ratings are updated everywhere and vice versa.

@w3wilkes I guess it may be improved when (optional) scanning for replay gain, bpm, genre, AI song tags and lyrics guessing, etc. will be added, but it will tax phone CPU and battery a lot, so it won't be enabled by default, but still nice to have e.g. for DAPs, car headunits, and very high end phones 😉

@andrewz thanks, fixed.

@andrewilley there are plans to make tracks "hidden" (+ mass options for hidden tracks such as deletion or unhide), but making them hidden will require selecting them and using action, that is comparable with queue/playlist. Alternative is to use rating system, so negatively rated songs are hidden (like Visualization presets may be hidden on dislike).

@Athlon it requires specific UI built for AAOS, and may be like 25% of Poweramp features are possible there. If this becomes a frequently requested feature, it's possible, but this is not somewhat that easily can be done, basically it should be a separate product.

@yuno thanks for the request. If possible, please share number of such lrcs (gpmaxmpz@gmail.com) as obviously it’s only possible to guess the approach to that based on such files (unless you have some kind of documentation or reference).

@James007 thanks for the report. As for cover size, Poweramp by default won’t even try to load image larger than needed to display it.

Build 980: bug fixes and stability improvements Hi-Res Output for MTK@Android 13 updated translations

@Wyzlow it quite hard to follow you as your disclose your settings with each post one by one;-) There are dozen in Apple Music and hundreds in Poweramp Equalizer, so this topic may get too long. This is why I specifically ask for steps to reproduce and the changed options in both Apple Music and Poweramp Equalizer.If some specific option breaks equalization, you can either disable the option to return equalization, or prefer that specific option over equalization. I'll also edit topic subject as it's not related to the actual problem. I can't reproduce the issue with the sole Spatial Audio option enabled as well. The issue is reproducible with Spatial Audio + Dobly Atmos marked tracks only. EDIT: the investigation shown that Apple either doesn't want their "spatial" (Dolby Atmos marked tracks) audio to be equalized or there is a bug as they don't report audio session. In both cases Advanced Player Tracking helps with this, though listening that "Atmos" content in headphones is like listening with head in a steel pot. The Spatial Audio options also "sticks" and can be only disabled by Force closing Apple music (from (i) menu -> Force Close).

@Liza V thanks for the report.

@Nexaz You can try it by yourself as it's not always possible keep even similar phones in perfect sync to test (small firmware differences across device regional model and country, etc. plus Samsung/Google like to do A-B testing with some features/flags enabled/disabled). Generally for One UI5.x DVC works up to 192khz and for One UI6.0 it works for 384khz too. The bit width is fixed in Samsungs firmwares to 24bit for 192khz and 32bit for 384khz. As for real difference, there is no as the signal-to-noise ratio is defined by the DAC + analog schematics and for the best mobile DACs will be probably around 20 bits, no matter how many bits over that you're pushing into it (and S series even has no 3.5 output anyway, so it's defined by whatever equipment you connect via USB or BT).

@Wyzlow I can't find this song (with Dolby Atmos label) - you can share a link if it doesn't work specifically with it. I tested with lossless and Hi-Res settings as well and it worked fine for songs from this playlist: https://music.apple.com/ru/playlist/dolby-atmos-best-of/pl.3651b01cb53c4f38aa9b50c0489f94aa?l=en-GB&ls), but I would not recommend using Hi-Res option this with Equalizer as 1. on Androids sample rate may not be properly reported to the equalizer, so you get incorrect equalization in such cases, 2. you're removing hi-res/lossless property by equalizing this way. Stick to standard definition Lossless. Anyway processing Hi-Res and to some extent lossless audio with equalizers and dsps contradicts point of these high accuracy audio formats, wastes battery charge, and increases CO2 in the atmosphere;-)