Jump to content

maxmp

Moderators
  • Posts

    5,324
  • Joined

  • Last visited

Community Answers

  1. maxmp's post in Poweramp build 976 doesn't show correct tags on some FLAC files was marked as the answer   
    @twask thanks for the files. I've checked those and they don't have valid FLAC metainformation. FLAC format demands first block to be a METAINFO block (https://xiph.org/flac/format.html#metadata_block_streaminfo). As this is not true for these files (the image block is the first block instead), Poweramp consider those not to contain a valid metadata and skips parsing those tags quickly.
  2. maxmp's post in selected_aa filenames clarification was marked as the answer   
    The filename part of the path depends on category type.
    For the non-stream tracks it would be this function: https://gist.github.com/maxmpz/6e83a36e16c3fd4fd7cfe1d5cd440f29
    Where relevant PathUtils methods are here: https://gist.github.com/maxmpz/dab88451c0f54c6851074e7146cd5b8d
     
  3. maxmp's post in Poweramp ignore replaygain 2.0 tag was marked as the answer   
    @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!
  4. maxmp's post in Avoiding redundant sound processing when using bluetooth was marked as the answer   
    @jemenfous Hello and welcome to the forum
    the option is called "No DVC Headroom Gain" and it basically applies negative preamp to allow equalization in No DVC mode. Negative preamp is generally required for applying sound processing on normalized digital signal, where signal peaks already reach maximum digital value, so any direct amplification over that value is not possible (it will cause audible overloads and/or force Limiter to act, which causes rapid volume drops around loud parts of the signal). This is applied in non-DVC mode only DVC allows for more headroom (meaning we can amplify frequencies without negative preamp or overloading/limiting) float32 may work or may not work on the specific device/firmware/patch level. It's not possible to know that in advance, but you can try to enable it. It usually works on Pixel and Samsung devices, but often broken on the Chinese devices/firmwares Thanks!
  5. maxmp's post in New release of Poweramp app in Mi app store but not on official website. was marked as the answer   
    The last build on forum/Play (976) is up-to-date. 3rd party stores may have higher build numbers, but these include specific changes for that stores only which can't go into Play build anyway (Play doesn't generally allow 3rd party payment systems/app stores libraries). And we can't keep the same build number as on Play as otherwise users will never get these (often important for that store) updates from those stores.
    For example, Huawei AppGallery build has specific AppGallery related code. You don't really want this code in your general build (it talks back to Chinese Huawei servers), but it's probably ok for Huawei users.
  6. maxmp's post in Add Furigana support was marked as the answer   
    @Feuerswut thanks for the request, but if you means lyrics rendering, Poweramp displays text as is, it doesn't process text itself. If text is unicode, it should be properly displayed for all the symbols included into the font.
  7. maxmp's post in Android 14 was marked as the answer   
    @kamaleon this is a planned feature. Thanks for the request.
  8. maxmp's post in System status bar without background was marked as the answer   
    @Luucas Android doesn't "enforce" contrast for status bar as it does for navigation bar, so light/white-ish album art will make status bar non-readable, and also there is not-that-great-looking overlap of status bar icons with lists if no background is used. This is why it's not implemented in the built-in skins, but still it's implemented in many 3rd party skins.
    Also you can remove status bar in Poweramp completely via "Hide Status Bar" option.
    Thakns!
  9. maxmp's post in Poweramp for Android 5.1 was marked as the answer   
    @JueWe there are no changes in regard of Android versions - Poweramp runs on Androids 5.0 to 14 (beta).
    As for slow downs, if you just initialized the device and added music, it’s probably system scan scanning a lot of music and taxing the (quite slow) cpu and io subsystems. 
  10. maxmp's post in Pairing .lrc lyrics was marked as the answer   
    @SAT-Oxford if LRC file is in different folder, it won't be matched by the track file name (this is to avoid matching Track 01.mp3-like named tracks). It will be matched based on track and lrc tags - title, album/artist, and duration +/-2sec.
  11. maxmp's post in On Nothing Phone (2), any audio seems to resample to a fixed rate, then resamples again. was marked as the answer   
    @1meter thanks for the details.
    I tested various outputs on this device, and apart from USB DAC running on 384khz, any other output device (including LDAC) are forced to 48khz. Quick investigation revelead "Dirac" sound effect hanging around globally and forcing audio being 48khz on all times, causing those weird 44.1->48->44.1 or 96->48->96 resamplings. The Dirac effect switch in Settings does nothing (effect is still there, enabled).
    The effect can be disabled by "adb shell pm disable-user --user 0 com.dirac.acs" (+ reboot) and reenabled by "adb shell pm enable com.dirac.acs".
    Then you can get Hi-Res output working properly on this device:

     
  12. maxmp's post in Google assistant driving mode was marked as the answer   
    @odlaw added better support for this mode. This is actually new Google maps launcher/media browser which is now supported from build 976. These results are cached it seems - I haven't found a way to reset the cache. I hope Google will fix this soon as for now it just caches top categories (or, top playlists e.g. for Spotify) forever.
  13. maxmp's post in Poweramp overrides bluetooth device controls when another app is in use was marked as the answer   
    @elucid8 the issue is not reproducible on the recent Poweramp builds (97x). Please upgrade if not yet.
  14. maxmp's post in Separate artist names was marked as the answer   
    @andrewilley I added that to dev builds. Btw separator chars (with the whitespace option) are not trimmed, so the new logic may separate artists differently as now these spaces are included into the patterns.
  15. maxmp's post in Setting resets after each update / Max volume after changing options was marked as the answer   
    I limited cases when Volume levels will be reset on update. This option is very limited on current (12+) Androids, and also it can interfere with Android Auto, and generally Google wants to forget this option existed due to the Sonos case and they break it all the time. But it works for some firmwares, so that's why it's there.
  16. maxmp's post in 972 Hitches in Playback was marked as the answer   
    @w3wilkes almost no difference, though AudioTrack is capable of Hi-Res for BT and USB on the recent Androids (12+). Also, on some Motorolas AudioTrack may be set to default or vice versa (there is a batch of Motorolas with AudioTrack implementation bug, and another batch of Motorolas with OpenSL implementation bug and Poweramp tries to avoid that by changing default output settings).
  17. maxmp's post in Poweramp Equalizer Pre-Set Always on When Launching was marked as the answer   
    @MikeFrank I would add that this issue reproduces only for graphic equ when # of equ bands is modified/custom equ bands used.
  18. maxmp's post in LSC and HSC Audio Filter was marked as the answer   
    @Blaze Emerson Thanks for the report. Yes, Poweramp supports non-standard AutoEq LS/HS filters, but looks like they recently updated that (https://github.com/jaakkopasanen/AutoEq/issues/586). This will be implemented in the next Poweramp build.
  19. maxmp's post in Improve synchronization of lyrics on Bluetooth devices was marked as the answer   
    Thanks for the request. Actually, we already have this kind of synchronization for Visualizations. Probably this latency can be also applied to the sync. lyrics UI. Though, BT latencies are rarely more than few hundreds ms, and lyrics UI already have resolution of 250ms, but anyway this will help a bit.
    (The visualization delay already can be configured per device, so this definitely can be useful for lyrics display as well).
  20. maxmp's post in Spinorama EQ was marked as the answer   
    The format seems to be very close to auto eq txt format, but it can’t be imported due to some minor incompatibility it seems.
    I’ll try to add support for importing those (txts can be opened in Poweramp or Equalizer vis file managers or imported from within preset list).
  21. maxmp's post in Poweramp Waze support was marked as the answer   
    @beno52 they specifically whitelist players (https://support.google.com/waze/answer/9171270?hl=en), so this is something that should be requested from the Waze devs, not from Poweramp. Thanks!
  22. maxmp's post in Poweramp not running at 120hz on Nothing Phone 2 was marked as the answer   
    @Rashid Alawadi btw I got my hands on Nothing phone 2 and it seems the OPPO/OnePlus (non-standard) API is used to force-enable higher frame rate. There is also some sort of app whitelisting, but at least that OnePlus API works, so I'm adding support for that (via now exposed Misc / Apply OP High Framerate option).
    Thanks!
     
  23. maxmp's post in Optimizing for Large Libraries? was marked as the answer   
    I would add that for the initial scan (right after Poweramp is installed, or if Full Rescan is initiated), try to keep Poweramp playing something/on the background, as scanning large library on slower storage (sd-card) may take some time and Android will kill Poweramp if it's not playing something. Poweramp will attempt to scan further on the next run still, but you may not get all your library available until it finishes the scan.
    There are plans to improve this - by showing "Scan in progress" notification.
  24. maxmp's post in Glitches and distortions when Sample Rate is 192khz. was marked as the answer   
    @Loweaul actually, MTKs have a long history of supporting Hi-Res without any issues. DVC works fine when it's supported. But while almost all SOCs out there do support hi-res, OEMs choose not to support it across the range of their devices (i.e. phones).
    So if OEM claims it's supported for that phone mode, it most probably will work, but if OEM doesn't have such claim, it may work, or may work unreliable, may work on some firmware and fail with updates, etc.
    Unfortunately, must having Hi-Res capable SOC in the device does not mean your phone can produce hi-res output - at least on 3.5 output, as USB and Bluetooth audio implementations are software and not dependent on the SOC.
  25. maxmp's post in App Crash When Adjusting the Volume was marked as the answer   
    @Loweaul Thanks for the log. Yes, the log shows the crash in android native audio track API during setVolume. This is some kind of firmware customization/issue, which is very hard to track/fix in the app (as it's very OEM/firmware specific), but hopefully I will occasionally get similar ROM on my Motorolas, or may be firmware update fixes this first.

    In the meantime I would recommend trying other outputs, such as AAudio which (on the recent Androids) is on-par with Hi-Res output in
    terms of hi-res support.
     
×
×
  • Create New...