Jump to content

John Titor

Approved Members
  • Posts

    318
  • 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 John Titor

  1. Ah, this version is bit buggy. On AAudio output, if just play a song, then seek, play/pause, audio randomly stops, but on Poweramp the track isn't paused. It looks like it's still being played, but I can't hear it. It doesn't happen on Hi-res output. I checked. I sent a full system bug report to Poweramp.maxmpz at gmail.com.
  2. It works on android 9 now, according to the Changelog in app. You might want to update the changelog on this thread. And BTW, is there a way to get play distribution versions? Uni is big. I prefer the play variant but Google Play probably hasn't accepted the update yet. So I didn't see an update there.
  3. Yes, Poweramp currently supports AAudio output on any devices running on Android 10 and up. As for Hi-res on AAudio on OnePluses, I am not sure. You can try setting the sample rate to 192kHz and sample format to Float32. Support for more devices may be added in future, but that's a question for Max.
  4. Most phones don't really process to that 32 bit depth. It's pretty much useless on phones. More information: https://forum.powerampapp.com/topic/20261-direct-hd-vs-direct-hd-10/?do=findComment&comment=91754
  5. AAudio output is currently Hi-res capable only on Samsungs and MTK based phones. On other devices, it is similar to OpenSL ES/AudioTrack output (no Hi-res), though Hi-res might work with Bluetooth devices.
  6. Max, were you able to clear the licensing issue? Or is there something else blocking the implementation?
  7. There are three modes. Default, power saving, and low latency. I read on an article that it's possible to reach as low as 20 ms latency but it would use small buffer size and more resources, consuming more power in the process. Power saving mode trades off latency for more power by using big buffers and etc. As Max said, low latency isn't necessarily needed for media players, they are for high performance apps (sound interactive apps, games, etc). I am not entirely sure which mode it is using, probably the power saving mode. But I would rather save power than latency 🙂. Though, AAudio output in Poweramp is still in beta stage and I am expecting some improvements. AAudio API is supported since Android O but on Poweramp it is supported for Android Q+ devices. It should be possible to enable this on Android 8 devices I think. ~~And would be nice to be able set specific modes~~
  8. I am not sure what you mean by "better". OpenSL ES is an audio API added way back in android 2.3 but it was significantly improved in android 4.3. While AAudio is a pure native API designed for high performance applications (that require low latency). It was added in Android 8. It's great for high performance applications but for media players, it is almost the same as AudioTrack (as Max said). The latter API allows Float32 output format and high sample rate (Hi-res) which OpenSL ES lacks in Poweramp.
  9. I support that, but I think it would be a good idea to let users add artist names to the whitelist themselves, rather than hardcoding them in PA. Hmm, Luminous Black seems to be made by the same dev as Aurora. Is this something that skin devs control or it's a Poweramp bug? I would wait for some intel from @maxmp.
  10. Rounded bars visualisation on EQ works fine for me on both light and dark skin (built-in ones).
  11. It works fine with some skins (i.e Liv Dark) and on some skins it doesn't (i.e Aurora).
  12. AAudio is an audio API for android 8+ devices (on Poweramp it is available for android 10+ devices at the moment, tho). It was implemented as per this discussion. https://forum.powerampapp.com/topic/20113-output-feature-request-use-oboe-output-in-Poweramp/ And Hi-res, yay!
  13. I would support this tidying up suggested by Andre. https://forum.powerampapp.com/topic/20813-organisation-of-items-in-output-menu/ Just another feature request, would be nice to change the default output method for unassigned devices. Disabling high-res output toggle just makes Poweramp fallback to normal OpenSL ES, I would like it to be AAudio or something else for my convenience. 😁
  14. Thanks for the update Max. 😄 Could you change AudioTrack sample format toggle to an option selector like the one for AAudio to make them more consistent? to
  15. Well yeah, a choose default album art setting could be an workaround for the copyright issue. I mean like, it would let us pick an image file from our storage and use that as the default album art. Since the custom album art wouldn't come preloaded with the skin, it wouldn't violate any copyright. I think using copyrighted images for personal use is grey. 🤔
  16. Speaking of stereo effect, I think the only current way to increase/decrease it is by manipulating the gain of specific frequencies. Poweramp already has a Stereo expand knob, would it be possible to implement it on PEQ?
  17. Actually it happened a few times with me. Usually restarting my device fixed it, can't test it properly because it happens randomly. I am guessing YouTube (Vanced) just ends audio session randomly (during pause/play/fast forwarding), while PEQ couldn't refresh the session id for some reason/or just it couldn't detect the new session id. So PEQ keeps equalizing the dead session id while showing that YouTube (Vanced) is active. It could be fixed if we just clear all tracked/cached session id info from PEQ and query again. (Effectively refreshing the session info) Would it be possible to implement something like that? Note: I am not an audio engineer/android dev, that above information could be faulty, it's just a guess anyway.
  18. Show your love for the dev during valentine's week 🙂😂 Good idea. I am also into the idea of implementing a home page like Spotify/YouTube Music/Deezer where suggestions/most played songs are listed on. Kind of like how this open source retro player implements. https://github.com/h4h13/RetroMusicPlayer what do you think? Would it be possible to implement something like this? Currently even custom Poweramp skins can't add this feature.
  19. I am assuming you guys are talking about adding something like this one Spotify has? I would be all for that!
  20. Hmm, looks like android still doesn't have a full native support of midi yet. But I think Amidi API could be helpful 🤔? And I remember the first music I played on my parent's phone were actually .mid files, in the 2000's 😄. So my support is based on kinda "nostalgic" feeling. Mid files are very rare these days. Frankly, even I, myself, don't use the format mid regularly. So if adding support for mid files would be a pain, I totally understand.
  21. Well @maxmpsaid that ^, there is not a reason to not implement this, right? Midi files are rare these days but some people do use it. There are some already working alternative apps on Play Store, but I don't see a need to actually maintain to music player on my device. I support this feature request too!
  22. I just use the MusixMatch app lol haha ,I don't use the overlay. Song/music detection feature is pretty good tho
  23. Which specific API? Because https://developer.musixmatch.com/documentation still exists and I think lyrics can still be queried from there.
  24. Yes, give it notification listener and ADB dump perm as instructed, then enable advanced player tracking.
  25. There is a toggle named "Disable permission monitoring" at the very end of Developer options page. The toggle is disabled by default you need to enable the toggle to "disable permission monitoring". If it still doesn't work, please ask on XDA preferably with a screenshot of the developers option page.
×
×
  • Create New...