Jump to content

maxmp

Moderators
  • Posts

    5,324
  • Joined

  • Last visited

 Content Type 

Profiles

Forums

Blogs

Gallery

Downloads

Poweramp Knowledge Base

База знаний Poweramp

Poweramp知识库

Poweramp Equalizer Knowledge Base

База знаний Poweramp Equalizer

Store

Events

Ideas

Posts posted by maxmp

  1. Yes, these files have R128_TRACK_GAIN set to 0. This means default +5dB gain is applied in addition to (decoder) handled implicit gain which is for the track test1 is FD.C0 (hex Q7.8 signed value, == -2.25) and for test2 is FE.D3 (-1.18).

    So basically final gain for opus is: +5dB + header gain + R128_TRACK_GAIN (+ optional gains from Poweramp RG settings/preamp).

    Poweramp doesn't display implicit decoder gain, but it displays replay gain with the +5dB offset applied.

  2. Hi-Res output uses the approach which can be easily broken (forever or until some future update) in the particular OEM firmware. Successfully, Poweramp supports multiple ways to output Hi-Res audio:

    - (basic) AudioTrack now supports hi-res sample rates and formats for Bluetooth (LDAC) and some USB outputs - usually on modern Androids (13+, earlier for some OEMs)
    - on recent firmwares (Android 13/14) AAudio Output supports everything that Hi-Res output supports for the older devices, but in a bit more stable way
    - even super-stable OpenSL is capable for Hi-Res output on some recent Androids (Pixels/some mid and high-end Samsungs)

    3.5 output usually doesn't work with AudioTrack/OpenSL in Hi-Res, but 3.5 output is just missing on modern Android phones anyway.

  3. @MarioC Poweramp plays all the aac files with the "issues" as previously provided by the users. There is no "universal" standard for aac files (which is not a container but a sequence of the raw aac packets, where AAC stands for the codec), so this is implemented "ad-hoc" in players. Poweramp aac support is based on modified FFMpeg and TagLib, with the fixes for the mentioned above user provided/test files.

    From your brief description, longer file may not be fully played due to some non-audio content in the middle (e.g. parts of video stream, meta info such as tags/album art in the middle of song, etc). But that can be only investigated when the failing file is available on hands.

    Thanks!

  4. @1artist there is no such option (and actually adding something like that will require alarm and related permissions, which we would generally avoid), but there are enough automation tools on Android which can do that, for example, Samsung Routines can do a Routine with Open an app or do an app action with Poweramp Play action selection and that can be ran on the specific time or for a specific condition/mode/etc.

  5. @andrewilley it's possible to purchase 2 separate licenses on the same account in a few rare scenarios, such as first payment/processing was delayed for the first one and another attempt for the same account is made. It will work OK for the later license, and we can change the first one to any email as user requests, or refund it.

  6. @waterfall could you describe your setup (phone/ROM/BT end device), as AFAIK Android LDAC implementation:

    - forces upsampling to 96khz
    - actual BT end device DAC jumps 48-96khz dynamically depending on the radio environment, and even that requires Developer Settings - 900kbs LDAC setting (I can see 96khz sampling rate only when distance between phone and BTR3 device used for the tests is less than 20cm, otherwise it's 48khz)
    - that means for the Android phone out of box, even if LDAC is selected, we always have 2 sample rate conversions, but those are transparent and can't be heard or easily detected 

    Poweramp notices Bluetooth Codec Changer (BCC) manipulations and changes DSP sampling rate accordingly to the active codec - just leave Output Sample Rate option on Auto. Making it work vice versa (changing BT output constantly) is a viable idea only if you're sure you codec support that rate, you have that BT changing app working, permissions given, etc. and it introduces audio artifacts and disruption of Poweramp crossfades, fades and accurate track starting/ending. 

    Btw I will test BCC on a wider set of the devices, and may be similar functionality (minus analytics, trackers, and reporting personal stuff to the remote servers) can be added to Poweramp and Equalizer.

    Thanks!

  7. @waterfall On Android, BT codec (and sometimes it's a dynamically changed, e.g. for LDAC the resulting sample rate jumps between 48 and 96 depending on distance between the BT device and phone) defines the sampling rate and if try to send the tracks sample rate, resampling happens inside Android/in codec, sometimes multiple times.

    "Bit perfect" (which is pure marketing term) would be possible for some USB-DACs and some DAPs, and that's planned for Poweramp, but not voted/requested that high vs other features, actually.

  8. Poweramp full rescan requires reading tags from each song you have in the Poweramp library. The tag can be as small as 1 kb, or it can be many MBs, if the file contains huge album art, for example. In any case, tags must be read. The overall speed is defined by the speed of the storage AND the concurrency for the storage access (meaning, system and/or other player(s) may scan same storage at the same time, reducing scanning speed). AFAIK Poweramp scanner is the fastest on Android, but it can't overcome your storage reading performance limits.

×
×
  • Create New...