Jump to content
Poweramp

Mehrshad Shafaghi

Approved Members
  • Content Count

    31
  • Joined

  • Last visited

Everything 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. 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. @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. 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?
  6. Thanks for the update. The "OpenSL Hi-res Output" is missing for me I've got only 3 outputs including AudioTrack, normal OpenSL ES and Direct hardware hi-res(which isn't hires either. For some reason it's being downsampled) I'm running an 8.1 oreo rom
  7. @Ajendra25 Which device are you using and which custom rom? Are you using a kenzo running an oreo rom? (If you are, go and check the audiophile discussion thread on xda. The only working combo I can think of is NOS O+latest alpha build of PA)
  8. 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
  9. Will uploading those system files help you in debugging on different devices? If it does, I'll upload mine.
  10. In terminal: Type: su (then grant root) dumpsys media.audio_flinger Via adb: Adb shell dumpsys media.audio_flinger
  11. 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...?
  12. 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.
  13. 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?
  14. 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 ?
  15. 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.
  16. 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 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?
  17. I uninstalled the alpha build and I'm trying the beta one. I'm still getting battery consumption warnings.
  18. This is the first time I'm seeing such error on the Android ecosystem. This build is backward-developing overtime lol. Donno if this is going to help or anything since the beta build looks like to be all different ??‍♂️
  19. Lol, Material Design V2 is here. I guess we have to wait several years more so Max can redesign the user interface
  20. Max, bro, Just wanted to remind that there's no need to release the beta build exactly on 31 May. You can release it sooner if you want
×
×
  • Create New...