Jump to content


Approved Members
  • Content Count

  • Joined

  • Last visited

 Content Type 





Knowledge Base

База знаний


Everything posted by Quade13

  1. He most obviously knows the issues. I wouldn't look up the reviews or rating on Play Store simply because the amount of inadequate people who tend to leave such testimonials, and having a poor knack of expressing their concerns. Every now and then you'll stumble upon dozens of meaningless reviews, barring the app in question actually performs well and frequently updated. It's just silly people. Not to mention the majority of this crowd has no idea that the release date of next PA build is postponed indefinitely, and there are incurring discussions taking place all around.
  2. Well, Max hasn't surfaced on the 4pda forums for ages (coincidentally, here too), and has not been proactive lately in general, so is more like nagging him for more insider details, privately. This is pissing everyone off, but you can't ask for more.
  3. Totally agree there should be a music player that can comprehend such formats. I myself had issue trying to playback some UnrealEngine proprietary files and XA rips of old PS1 games. In fact, there is unfamiliar charm with the latter, 37.8kHz music tracks sound dubbed in highs resulting in soft and acoustic flavor. The principal reason why that will not happen with Poweramp is the formats you mentioned are indeed proprietary, and the existing decoders are made as for under "as-is" freeware use, while PA is a shareware app. That would require extra licensing and tedious talks and consulting to concede on implementing these codecs. I personally wish it was in there.
  4. @clever_man did. To recap what is known so far: the development is in progress, the UI works are underway.
  5. Dolby libraries and plethora of mods are out there at your disposal for enhancing (is so bad) the sound with 3D effect, or anything that closely resembles it. However, multi-channel emulation/convertion of stereo audio is a terrible idea, regardless. You've got to have DTS ready files or DVD-A rips with the multi-channel support to make use of it, otherwise you would fall for a marketing gimmick. Although, Poweramp will not produce 5.1 or 7.1 surround due to the simple reason - it does output sound to the primary thread submix, and would merge all channels down to stereo.
  6. My apologies for interrupting this message, but bloody hell, you've got to be some kind of a fetish person to audibly endure the 64kbps bitstream for longer than 10 seconds...
  7. We would rather have Poweramp as an open source project, so anyone could contribute and make the development faster. Max can still get most of the revenue, while sharing a small portion in royalties with the top contributors (as the Phonograph dev does).
  8. Well, because he has a greater audience there and de facto he is russian. It's just more convenient to communicate in russian for him rather to do a lenghty explanation on this forum, which appears to be a ticking bomb, judging by this thread alone. There is a glimpse of hope if you look closely at the screenshot. One could notice "Track is decoupled from audioplayer and moved to PowerampAPI". The mentioned API is no less than a layer code, in other words is a framework (allegedly as I guess), to elude conventional audio implementation as seen in the Google's guidelines. Hence, that means audio routing will most likely be independent, at sole discretion of the software (the notorious hi res output, yay). It has already been done by the Neutron's author, in a very clumsy way; but given there is no viable workaround (thanks to the pile of junk, Android that is), it works just as fine as you would expect a contemporary music player on Android to do. I'm not cherry-picking strings of git commits from a sketchy picture and not looking to put up theories. Android Oreo had brought to us even more inconvenience (rather a greater amount of pain to software developers), there is a whole lot of things for Max to do at this point of time, including reworking deprecated notification system (to some extent, Android fumbled with it again) and introducing the MMAP output (as a part of the AAudio architecture, hell no more of that crap). And guess what? It takes time.
  9. No, it is being supported on a very limited number of devices on Nougat, and yours is not among them.
  10. How does this relate to the project transfer to another developer as previously discussed?
  11. Here's an analogy: let's take away your very own smartphone and hand it over to someone else, who allegedly knows the way it works, BETTER than you do. Why would you assume anybody is keen to acquire the software for further development? Why would they want a piece of unfinished code rubbish that requires a lot of preceding research before it is doable to commit changes and resume the development process (oh, and it subsequently prolonges the wait that is already frustrating)? There is always a way around, in fact plenty of: look up for alternatives on the Market. You don't like the software, you don't use it; now that is simple.
  12. You are getting some abnormal readings. It has never drained more than 2%/hr charge on my fairly new battery unit. Check out your power consumption of MediaServer system service, it used to be the principal culprit of severe drains on earlier Android versions. By the way, if you are so inclined, you can upsample primary audio outputs systemwide by modifying policy configurations. Although Android's Speex resampler is a piece of junk.
  13. There is no advantage to have flac files and transmit them over APTX HD, this format is capped at 576kbps (some heavy compression assured). It is still lossy, just as MQA tends to be. Try Neutron as a testbed for hi res support on your phone. There is some sketchy implementation.
  14. There are folks out there who appreciate quality before usability. I would have been listening to a vinyl player (dang, a tangible phonograph, what a coincidence!) if I owned one. No fiddling with analogue converters. The same philosophy applies to Android music playback: I want the sound to travel from point A to point B, unhindered, without layers upon layers of digital audio enhancers. Ever since I've had my first mobile device it's been a pain in the buttocks to achieve for the acme of perfection in that regard. Unfortunately, neither of the mainstream players on Android granted me such an option, except for a few not related to the craze for "the best player on Play Market". So Phonograph did it right on point for me. Should Poweramp deliver the same advantage of unattainable (subjectively) sound quality, I will swap back.
  15. Max had to take this direction simply because he did the survey way before the hi res support rant grew mainstream throughout Android community. It has been a major concern lately, nobody flipped a duck back then when the redesign works commenced. I'd rather recommend you to ditch any kind of equalizers and make use of different headphones and/or IIR filters, if present.
  16. Sigh. Well, it does utilize the DSP offloading (by default!), and just in case your ROM implements code hooking for dedicated DACs (don't mistake it for codecs, such as qcom's) when the output is being processed and created, then you are on the sweet spot. Otherwise, there's a chance it erroneously limits the playback to 16 bit (system-wise related issues). Example: That is what we anticipate to see in Poweramp. Hope Andre doesn't mind we converse on competitors in this thread.
  17. Hold on, it's not over yet. Have you tackled with build.prop values, by any chance? Specifically, the triggers for Samsung and Meizu driver implementations (the Lenovo one is atrocious, skip on it). A dumpsys log will sort it out. Of course, requires a rooted device, or some dodgy trials to get it working with a computer through dev debugger. You might have been tricked to believe it is functioning properly. Here is my readout on rerouting output threads. Notice the direct thread still outputs 48khz on a 96khz file. It has nothing to do with the system, but Poweramp itself. P. S. In fact, you should look up logcat for DAC triggers.
  18. One could do. We've got to consider he did not care to post a word for the sake of brevity. For ages now. All the uproar has been caused with the ignorance.
  19. It means you have to wait. It's not like there is overly sketchy implementation for each and every phone (hence I question the need of the DAC policy dumps topic on the forum), more like a driver callback. As evidently seen, we've been waiting for over a year and there's a glimpse of hope that the upcoming PA build will have the hi res feature restored to its former Android 6 form, or function at all. So, wait.
  20. You are out of luck, like hundreds of users on this forum. Fallback to your former OS version, or grab another player.
  21. Now, do make an AudioFlinger log dump. I am more than certain you'll find PA playing into the primary thread, while being submixed at 16/48.
  • Create New...