Jump to content

maxmp

Moderators
  • Posts

    5,327
  • 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 maxmp

  1. @TaKe91 thanks for the report. Yes, there seems to be a problem with named USB devices preset assignment. I'll try to fix it for the next builds. Meantime you can uncheck the named assignment and use just generic USB assignment.
  2. @Wyzlow Just tried Apple Music 4.5.0 with Equalizer build 980 on Pixel 6@Android 14 and S22@One UI6.0 and it works fine (all default settings in both apps). If it works then stops (and you can notice it reloads when you open Equalizer from launcher), it may indicate the app is killed in the background - enable Equalizer to work in background and enable its notification. Also, modifying Known Player options from the default settings may break equalization - ensure Restore defaults is used in Equalizer -> Settings -> Equalizer -> Known Players -> Apple Music.
  3. @ericg if you have File selection dialog disabled and can't enable it ( ), you may try to open the backup file in file manager with Open in... Poweramp, though this can be also broken, then there is no way (as Open file dialog is disabled).
  4. @Nexaz Better from what point of view? Prefer lowest possible sample rate and bit width to reduce load on battery and better stability and/or higher range of DSP/Tone/Equalizer adjustments with the DVC. Especially if there is no noticeable quality difference between higher and lower sample rates - as you just waste processing power on it. Thanks!
  5. @Blaze Emerson can you please elaborate more - what exactly do you expect to see from this project in Poweramp Equalizer?
  6. @Ibrahimbo101 Thanks for the request. 1. hex entry is possible, though for the theme/material u colors it won't make sense as these are dynamic. 2. tab to apply color for what elements exactly? We currently have background, text, and buttons/icon colors and there are no other elements to apply color to. 3. if all buttons/actions enabled, there may be not enough space, but if some are disabled, we can definitely have more or configurable padding there.
  7. @Amirhamdy45 I guess there are comments / notes and/or further questions and discussion regarding these features on the forum? You can participate in the appropriate topics and move feature to a voted feature - that will bring it closer to implementation (https://forum.powerampapp.com/ideas/?mode=popular). I would say most of the items you indicated are already in the voting process.
  8. Build 980: fixed known player settings page
  9. @Vizir44 newer Androids may not support very old apps that well. The new Androids are perfectly supported in the new Poweramp builds, so I would suggest upgrading. Thanks!
  10. @Amirhamdy45 what unanswered requests do you mean? Can you please provide links to those? The target is 4 stable builds per year and much more often releases on beta channel/forum. If some feature takes xx months to implement, there may be appropriate obvious pause for xx months in the release schedule. Reading further into your post - have you confused this forum (Poweramp/Poweramp Equalizer) with some other project/app forum?
  11. The title of the topic is incorrect as Poweramp sorts items based on unicode value and all languages included to your Android firmware unicode+sqlite are supported. Sorting is placing items in order, it’s not related to thе AZ scrolling bar. You can change AZ bar to normal scroller via Settings -> Library -> Lists -> AZ scroll. As for supporting romanization to intermix Chinese/Japanese items with the latin items - this was already requested previously and this can be supported via additional “sort” fields (which are partially already used for e.g. article insensitive sorting). I think this can be added to the voting. Thanks!
  12. @Abduallah Khalf Hi-Res output is not guaranteed to work on all devices. If it doesn't work for you, you can try other outputs. On the recent Androids AAudio output should be more stable, but anyway, there are devices with broken AAudio output as well. For the default settings, AudioTrack output (as well as OpenSL output) should match in volume to other players. If it doesn't match for you (on default settings, as you can always adjust preamp, and various Poweramp gains to change that), please see here: https://forum.powerampapp.com/kb/en_us/faq/volume-issues-r7/
  13. https://play.google.com/apps/testing/com.maxmpz.equalizer Builds 979-983: AutoEq presets/devices database update support for the predictive back animation on Android 14 improvements for Samsung One UI 6 workaround for Samsung Dual Messenger option This option starts 2 copies of Equalizer, breaking equalization settings search history new Settings Shortcuts in Main Menu option Target SDK updated to 34 translations updates bug fixes and stability improvements
  14. 4,904 downloads

    Builds 979-983: AutoEq presets/devices database update support for the predictive back animation on Android 14 improvements for Samsung One UI 6 workaround for Samsung Dual Messenger option This option starts 2 copies of Equalizer, breaking equalization settings search history new Settings Shortcuts in Main Menu option Target SDK updated to 34 translations updates bug fixes and stability improvements
  15. @dez93_2000 thanks for the file, just played it fully (4:00) in builds 979 and 976.
  16. @Fatalxe unfortunately, I can't reproduce this on same OneUI. If it doesn't open web variants, it means no default browser (which handles http(s) intents) is registered in the system or something is actively blocking this. You can try to make Poweramp Settings -> Support -> Send log (and PM me your email so I can find the log) or a device Developer settings -> Full Log -> gpmaxmpz@gmail.com and I'll try to investigate, but issue is not with Poweramp itself. Thanks!
  17. @Phantom52347 I tried that and it doesn't work that well as we want to consider last velocity of the finger and it's too easy to miss the wanted "screen" then.
  18. @Rachidulric thanks for log, but no double press there. Double press is 2 presses within 600ms, while from your log these are two presses within 1.8 sec.
  19. @andrewilley thanks. At this point I can confirm some parts of app not being translated, but starting app from launcher again fixes that. Looking into the issue. This is some sort of non-standard caching in OneUI 6.0 which may be only fixable by the firmware fix. Some extra delay seems to work around this, included into the next build.
  20. @stoicmindsxia thanks for the report. What happens if you return back to launcher with back action and then return to player?
  21. @sxpad8010 Thanks for the report. Poweramp doesn't call this code, tested and works on Android 14 (Pixel and Samsung variants) and stack trace shows some Google Play logic which is not directly used by Poweramp. What is the scenario/reproduce steps for this crash?
  22. @andrewilley this is already changed/fixed in the current dev builds. Thanks for the investigation.
  23. @shuephei the (next) build 979 includes parsing of replaygain_* for the opus tracks not containing R128_* tags. Previously Poweramp hasn't read it as this is non standard and specifically mentioned not to be read in the format specs. It's not possible to guess in advance what are the actual tags used "in the wild" - before such tracks are committed for the investigation and for the ad-hoc solution. Thanks!
  24. @SachinSachi Android decoder does not pass gain info to the calling code (Poweramp). I guess something can be added to support that, but I need a sample tracks (feel share with gpmaxmpz@gmail.com). Thanks!
  25. @LPW00 that's not possible on Play due to Repetitive Content Policy.
×
×
  • Create New...