Jump to content


  • Content Count

  • Joined

  • Last visited

About andrewilley

  • Rank
    Forum Admin
  • Birthday 09/26/1962

Profile Information

  • Gender
  • Location
    Birmingham UK

Recent Profile Visitors

88,752 profile views
  1. Max was saying that even if the internal chip supports high-res, Poweramp also needs the device firmware (i.e. the Android version) to provide a driver interface via which apps can connect to send high-res audio to the 3.5mm socket. It's unlikely a log would help, he would need to have an example of that phone and your specific ROM to test to find out anything more. Maybe a new ROM might help though? Andre
  2. App tweaking settings can be found in PA EQ > (tap the three-lines menu icon) > Settings. As for your audio adjustments, move the various sliders up and down for each frequency band, or just use the coarser Bass and Treble knobs. What values you arrive at are up to you; unless you have an external frequency analyser and appropriate audio samples to test the frequency response curves of your device, your speakers/headset, and even your ears, it's mostly a case to play around until your music sounds how you like it. There are no one-size-fits-all answers - if there were, all audio app
  3. @Someguyonline Those appear to be .mka (Matroska Audio) files, not video files. Andre
  4. @BluefluffyFusky I thought you'd already tried reducing the preamp gain, as I suggested back in https://forum.powerampapp.com/topic/20589-bass-is-terrible-when-headphones/?do=findComment&comment=93611 ? Andre
  5. There are some other legacy options that help with older, less well-tagged, files - but by far the best (and most correct) modern solution is the one you mentioned, which is to ensure that all tracks in any given album have the same Album Artist tag. Otherwise PA has to rely on solely the Album Title tag matching, which would cause problems with (for example) albums entitled "Greatest Hits" but by different artists. Andre
  6. If your device updated itself to Android 11, try going into PA Settings > Audio > Outputs and reset to defaults. That may help. Andre
  7. MP3 is lossy, but that's not the issue being discussed here - and above about 200k bitrate it's pretty close to the original material for most cases. However PA unpacks any format back into an uncompressed bitstream before starting to process it, it doesn't try to process the still-compressed data. Andre
  8. They both stream from the cloud directly to the Chromecast. PA has to send full uncompressed WAV-style audio from your device to the Chromecast. Andre
  9. Yes, if you want to huge up the bass (is that a phrase?) you might expect to also need to reduce the overall processing gain to compensate by allowing a bit more headroom. Andre
  10. You could try using high-res output instead (e.g. 192kHz / 24bit), that might help give you some extra headroom if none of the other suggestions help. Andre
  11. Turning DVC on usually reduces the amount of processing that the device does, allowing a cleaner path from Poweramp to your output device. Settings > Audio > Audio Info will tell you what is actually being used. Andre
  12. I suspect it would be helpful to have a few extra options in the All Songs sort list - such as your requested "Artist>Album>Title". Or to keep the list contents manageable, perhaps some sort of flexible user-defined sorting option using %field% descriptors - e.g. something like "%artist% %year% %album% %disc% %track%", or your "%artist% %title%". Andre
  13. Date encoding gets rather complicated when you get to ID3 v2.3 and 2.4 tagging (and then there's Vorbis, APE, etc too). There was a recent thread discussing extended dates: Basically though, Poweramp follows the overwhelming consensus among most applications in that the original ID3 v2.3 TYER tag should be used (which can be extended beyond its first four digits to allow for more details YYYY-MM-DD encoding). PA does not use any of the other increasingly convoluted tags such as TDAT (date, DDMM), TIME (time), TORY (original release year), TRDA (recording date), TDRC (recording date in fu
  14. I assume you've tried increasing the buffer size, and checked Settings > Audio > Output > Chromecast to keep output down to 44.1 kHz / 16-bit? But if it works on other Chromecast devices it does seem to be more likely your GTV that's the issue. Andre
  15. @maxmp might be able to shed some more light on this, but in the meantime please could you post the info from long-pressing on the metadata line at the bottom of the player screen, while you are trying to Cast - especially the final few lines. If PA keeps resetting its own playback position to the start of the track, a log might help too (Settings > Get Support > Send Log > email to gpmaxmpz @ gmail . com ) Andre
  • Create New...