• Announcements

    • andrewilley

      Poweramp v3 Project Update   04/24/2017

      As you may be aware, the Poweramp developer has been working hard on an updated material design user interface for Poweramp v3 which required a full ground-up rebuild of the code and is taking some time to get to a beta-test stage. See the forum thread for more details and to discuss.    

Quade13

Approved Members
  • Content count

    22
  • Joined

  • Last visited

About Quade13

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Interests
    Audiophile

Recent Profile Visitors

150 profile views
  1. The only problem in this never-ending, ever-lasting mess is the lack of communication and reluctance of posting any paper updates. There would have been less public uproar, should the dev (any dev, for sure) kept the customers informed on the process of whatever they are doing. In this very case, we have unilateral feedback - from us, not the author, - hence the issues. Make a milestone build of the app, do explain if you have difficulties and/or need more time, and we are all set and keep our mouth zipped. P. S. No flaming.
  2. Looks wonky, but I hold my appraisal for now. Hopes there will be the famed black theme which fits well to Amoled screens.
  3. That doesn't really matter to me what engine is being used as long as it fits my listening preferences. I find the stock OpenSL with audio output of music playback rerouted to direct thread to be accommodating. Plays high res content as intended, sound is great. Whereas the utmost concerning issue tends to be the hardware side of the flipping coin - you can hardly wish for vendors to deliberately implement drivers and sound backend in their own firmwares, whereby enabling users to enjoy music in whatever way they want to. Sadly, many disregard this part and the whole system crumbles down: dedicated DACs either don't work or are not hooked up during the sound thread call execution; half of the music players just ignore the fact there is sophisticated hardware pre-installed due to lack of related driver callbacks, the other half is specifically programmed to identify such or emulate the behavior. To summarize: the hardware backend matters©. Personally, I enjoy Phonograph as a viable alternative that WORKS for my needs, despite a ton of code hooking headache I had to do.
  4. That is upsetting. I do hear a difference by comparing a downsampled 320 mp3 file and a ripped flac. Most of the time this manifests in distinctive loss of detail or hiss on treble-induced instruments. Speed metal and/or similar genres turn out to be hell to listen to. I'm looking forward to grab a pair of Ety iems soon, that should mitigate my keenness of listening to lossy formats, ever again lol Back on the topic: this is the principal reason to avoid PA as it does not match up to the correct frequency output of a file, and either of the formats are imparing due to resample to android's default. So, even a lossy format would be upscaled to 48khz with a sampler lib (not sure which one PA utilizes), not even at a 2:1 ratio.
  5. Wat. Elaborate this utterly sketchy statement.
  6. This is the one I use daily now (paid), thanks to offloading as the default output. Actually I messed around with the audio policy and managed to reroute Phonograph's playback onto the direct output, which, hey PA, works as intended. I haven't had any problem with that, since I don't need filters and eqs to enjoy music; Neutron (due to poor sound quality) and PA (which is lagging behind and abandoned), both are long gone for me as music players.
  7. It will happen, eventually, but too late to care about.
  8. Okay, if that thing is not going to be released in the next 12 hours, I formally cease to even consider using any of the software related to Poweramp by the author and the app itself. The ignorance is enough, not even a drop-by to enlighten the customers with plans and heads up on the development.
  9. https://m.androidcentral.com/google-play-updates-2018 Just one more year, boys, Big G will wipe it.
  10. That wouldn't help. The player will utilize the mixer instead of dsp offloading or direct output. Meaning there is no difference, however you will see a fancy chunk of text saying everything works just fine. Not to mention Axon's implementation of dedicated DAC should kick in (code dependant), otherwise you will be fooled and encounter placebo effect by listening to wcd codec. Prove your approach, do an AudioFlinger dump or measure frequency response on your PC with RMAA.
  11. A lot of players have already exceeded it. At least those are kept up to date.
  12. Depends on your device. In the current iteration of PA there's only constant 48khz 16 bit. The player utilizes primary output, i.e. proceeds through the audio mixer. The notorious "hires" option is inclusive to that behavior.