Jump to content
Poweramp

Mehrshad Shafaghi

Approved Members
  • Content Count

    31
  • Joined

  • Last visited

Posts posted by Mehrshad Shafaghi


  1. I have a Redmi K20 Pro running pie based AOSIP custom rom. I experience this on MIUI and Lineage OS as well.

    The Output status is telling me that when I use OpenSL ES output I have 16bit output and a total of 2880 audioframes processed (statistically speaking. I don't care about *numbers. I donno how it even works)

    But a terminal check gives me other results:

    Output thread 0xf3f03640, name AudioOut_D, tid 1536, type 0 (MIXER):
      I/O handle: 13
      Standby: no
      Sample rate: 48000 Hz
      HAL frame count: 192
      HAL format: 0x6 (AUDIO_FORMAT_PCM_24_BIT_PACKED)
      HAL buffer size: 1152 bytes
      Channel count: 2
      Channel mask: 0x00000003 (front-left, front-right)
      Processing format: 0x5 (AUDIO_FORMAT_PCM_FLOAT)
      Processing frame size: 8 bytes
      Pending config events: none
      Output device: 0x4 (AUDIO_DEVICE_OUT_WIRED_HEADSET)
      Input device: 0 (AUDIO_DEVICE_NONE)
      Audio source: 0 (default)
      Normal frame count: 960
      Last write occurred (msecs): 0
      Total writes: 43966
      Delayed writes: 0
      Blocked in write: yes
      Suspend count: 0
      Sink buffer : 0xf40ce000
      Mixer buffer: 0xf49d7000
      Effect buffer: 0xf40c3000
      Fast track availMask=0xea
      Standby delay ns=3000000000
      AudioStreamOut: 0xf49c9e68 flags 0x6 (AUDIO_OUTPUT_FLAG_PRIMARY|AUDIO_OUTPUT_FLAG_FAST)
      Frames written: 42207360
      Suspended frames: 0
      PipeSink frames written: 42207360
      Hal stream dump:
      Thread throttle time (msecs): 0
      AudioMixer tracks:
      Master mono: off

    .

    .

    Is this expected? Or is it a bug? Should I ignore that?


  2. I have bought my redmi k20 pro recently. There's this new "hi-fi audio" switch under the "headphones and audio effects" page in settings which is new to me as I didn't have it in my older Redmi Note 3 pro or Redmi Note 4X. There are some issues when I turn on the switch:

    1. DVC: on results in a lower volume. The DVC volume problem isn't a new thing, right? You can totally get what I mean; the volume drops low even when you turn it all the way up. Makes it useless when playing songs in a car/noisy places.

    2. The Volume Knob isn't in sync with the actual volume level. Don't know how to put this. %100 volume on system equals to %60 volume on Poweramp. 61-100 volume on the knob doesn't make any change. Changes only appear in 0-60.

    These are the stuff I found. There might be some other problems that I don't know. I'll include the output detection log.

    Using MIUI 10.3.16 china stable.

     

    Screenshot_2019-08-21-13-54-59-336_com.android.settings.png

    New file.txt


  3. I wanted to ask for a built-in scrobbler for last.fm, libre.fm and ListenBrainz. Once you have em in your music player, there's no need for extra apps which take recources and consume battery since most of them may keep the device awake...

    Plus I guess it doesn't need much coding since the api for the three above is already available.


  4. On 11/15/2018 at 3:32 AM, Mehrshad Shafaghi said:

    From Android 7 to Android 9. Across all of the roms I had tried. Hi-res outputs always are downsampled to 48khz+16bit. Android 6 and below seem to be working fine. How can I prevent this?

    @maxmp Please help a brother out here. I remember I had talked to a couple of developers before and they claimed that the rom has the needed CAF patches.
    So the hi-res output works on android M and below (OEM rom or custom rom, both sides work) but in the next Android versions they seem to be always downsampling. I'm dying out of curiosity cause during this short time I had to spend with the older OEM rom I've fallen in love with Hi-res output again...


  5. 8 hours ago, majovajo said:

    Hi Max, I am sure that you are under heavy load now but I noticed an issue.
    I have a Oneplus One with latest Ressurection Remix ROM and on build 588 I could utilize the rom's function to control playback with volume buttons with locked screen.
    I haven't updated the rom but I installed the 705 (same on 706, 709) build and the playback control doesn't work for PAMP (for other players it does).
    Also doesn't work with offscreen gestures.

    Could you please check the issue if you have time for this? Maybe it would be helpful so that it doesn't end up in the final version.
    Thank you very much for your support and thanks for Poweramp. (Using since Symbian)

    Symbian? Interesting


  6. On 5/18/2018 at 10:38 AM, adhiNick said:

    this screenshot from old PA build 704 + marsmallow rom.
    it should be 2 images as comparation from marsmallow rom + PA 704 vs on oreo + PA 790, i forgot to add the one from oreo...

    I believe the problem comes from the oreo roms, since people have reported that alpha build 705 has a working hi-res on Nitrogen OS oreo.

    Btw, if you ever found a working combo, please come and report in the "Audiophile Discussion" of XDA


  7. On 5/16/2018 at 3:59 PM, maxmp said:

    Many Huaweis - they are all on Kirin - support hi-res (for example, P20 series, Honor 8 Pro). If it doesn't detect it on your device, it means something differs there. You can try to extract build.props, and any of: /etc/audio_policy.conf, /vendor/etc/audio_policy.conf, /vendor/etc/audio_output_policy.conf and PM me with them - I can take a look and compare it with the Huaweis known to produce Hi-Res on internal DAC. 

    As far as I can tell, (esp. based on pure AOSP) custom ROMs rarely support Hi-Res. Quite specific patches (qualcomm caf in this case) are required - per specific SOC + all the mixer, DSP, DAC configs. 

    build.props, and any of: /etc/audio_policy.conf, /vendor/etc/audio_policy.conf, /vendor/etc/audio_output_policy.conf can make it a bit more clear, but even with these existing and being OK, these said patches should be in the system - as configs just don't work without appropriate code integrated into ROM.

    Andre, what is the exactly device/Hi Res variant?

    Will uploading those system files help you in debugging on different devices? If it does, I'll upload mine.


  8. 8 hours ago, andrewilley said:

    Correct, it can do. Did you try what I suggested and remove artwork from a song file and see if it still happens?

    Andre

    Yep, the problem is solved.

    But tbh, is solution is a bit awkward XD. Is this a thing with MPEG format or other formats have the same problem? I mean, should I encode my songs in AAC from now on or...?


  9. On 5/11/2018 at 3:13 PM, andrewilley said:

    Some files don't seem to have header length information set correctly, which means that for songs with very large cover images, the seekbar counter can get offset. Try removing the cover art from a song which exhibits this problem and see if it then works correctly for you. (I use TagScanner on my PC, but there a lots of ways to edit/delete embedded tags)

    Andre

    Thanks for your response.

    My problem is PA-specific and I don't have such problem on any other media player in any other platform.

    I guess I misunderstood your explanations. The large album art makes the seekbar miscalculate the track duration? (!)

    I usually sync the metadata with MusicBrainz, therefore any probable corrupt tag must have been changed with the standard one.


  10. 2 minutes ago, maxmp said:

     

    Direct Experimental Hi-Res is no less or no more VS OpenSL ES HD. It's just a different way of doing the same thing - providing audio beyond 48khz/16bit. 

    I can't confirm if any custom ROM actually produces Hi-Res output, as for the stock ROMs - I test each build on each Hi-Res capable device in my test lab by capturing audio and analyzing spectrum - and most devices do produce real ultrasound up to 96khz (and above e.g. for Snapdragon 835 with 384khz sampling rate).

    Only few devices are known to advertise Hi-Res, but have no real Hi-Res output from stock or any other player, including Poweramp, on Hi-Res files (Asus I'm looking at you), despite in fact running all the audio/drivers/etc. on 192khz.

    Thanks for your response

    I had asked this question earlier: How do you check the audio output? (The spectrum analysis and stuff)

    I can remember there was a way to check this with some code in the terminal, do you do the same thing?


  11. Xiaomi Redmi Note 3

    Oreo 8.1 custom rom

    I'm missing the OpenSL ES HD output. I was so happy I could finally check to see if the new output actually works on this device or not since I could barely feel any difference.

    I have hires experimental output instead, but not the snapdragon 24-bit pcm one. And again, I can't feel any difference compared to default OpenSL output ?

    Screenshot_Poweramp_20180512-211647.png

    Screenshot_Poweramp_20180512-211653.png


  12. Ok I'll go straight to the point. I'm facing this bug since V2 and it continues to pop-up on V3 beta.

    This barely happens, but the seek bar goes out of sync with the actual playback time. It happens on mp3 files only. Even if you slide the bar, the player may start from the beginning while the seekbar doesn't reset and continues from the moment you chose to play.

    Screenshot_Poweramp_20180511-124826.png


  13. 25 minutes ago, maxmp said:

    Direct (Experimental) Hi-Res output doesn't work on 8.0 (mostly due to the new Android security rules regarding platform library usage). This output will remain to exist in Poweramp for Android 5/6/7.

    Successfully, most Hi-Res Android 8 devices (e.g. - Samsungs S8/S9) support Hi-Res via OpenSL HD output, and it can be validated by capturing and analyzing audio output (I did that for those Samsungs and Sony XZ).

    Current beta-preview OpenSL HD output has no device checks, thus, it's always available even if the device actually does not support Hi Res.

    I know it's possible to check the audio output sample rate N bitrate through some code in terminal but I can't remember it. I own a Xiaomi Redmi Note 3 running on a custom firmware (I'm sure a large number of PA users use custom firmware) and thus, I have no choice but to use the OpenSL HD output. Since I can't hear any difference btw the normal and HD Opensl output and messing with Float32 and DVC doesn't help me either, I'm wondering if you can tell me and other enthusiasts how to analyze the audio output.

    Sorry for long post :P

    Edit: I forgot to ask, will you be giving small updates to fix some obvious bugs or we should wait till May? 

    And one more question XD, Android is warning me of high battery consumption of PA (it was so annoying I disabled Android System Notifications). Is this normal?

×
×
  • Create New...