Jump to content

maxmp

Moderators
  • Posts

    5,327
  • 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. @1meter in this case of Bluetooth connection, the allowed sample rates are defined by the codec, firmware bt stack settings, phone + bt device negotiation, and if multiple sample rates/bit formats are possible, developer options can be taken into account.

    7 hours ago, 1meter said:

    I don't know if I'm doing something wrong while using LDAC, but I've found that no matter what the distance or settings, I can't get Poweramp to not resample the track to 16-bit 48 khz. It just does the same thing as the picture above. Am I doing something wrong?

    Poweramp will resample to whatever the sample rate you set. This will be resampled again to the codec sample rate as needed. 

    If you want to get 96khz from LDAC, and your firmware is playing safe (as 96khz is not reliable for many devices on distance > 20cms)  and not allowing that by default, try to set (in Developer options) LDAC bitrate to 990kb and LDAC sample rate to 96khz.

    If Poweramp output sample rate is set to auto, it will use 96khz automatically. Also try AudioTrack output, not the Hi-Res output.

  2. @1meter Equalizer app shows sample frequency as reported to it (via visualization component). If this is incorrectly reported, there may be some errors in the visualizations, but not in the DSP part as internally Android should know the frequency it's operating on (or there is a major bug in a firmware, immediately obvious).

    As for multiple resamplings, bluetooth codec will force sample rate and it's not possible to change it. The codec and codec parameters are negotiated by the Android BT stack and the BT device (some hints from Developer options may be taken into account as well). In this case I would suggest selecting the Poweramp output sample rate to avoid extra reamplings as much as possible.

    For LDAC over BTR, please note that 96kHz is there only when BTR is within 20-30cm from the phone, it transparently jumps to 48khz if distance is any larger. It's transparent to human ear as humans do not hear frequencies above 20khz (but the sample rate can be measured in base of BTR easily due to the 3.5 output easily connectible to the analyzing device).

  3. @eng3 if Poweramp is last used music player, Android will resume it next time "resume" button is pressed. (The resume "button", or command, may be just a single press on buds, or double press, etc. - depending on the headset/device/firmware). Some Android 13 firmwares have bug when Poweramp "Beep" option always makes Poweramp as last active player for some reason. Workaround for that was added to Poweramp build-975 (or you can temporarily disable Beep option). Thanks!

  4. I don't think Poweramp (player) has any Deezer related functionality. Do you mean Poweramp Equalizer app and its Known Apps info message regarding players? This is added by me and this means there is a Deezer known issue, not the Poweramp Equalizer issue. This should be reported to the Deezer devs, as previously they supported 3rd partry equalization on Android, then broke it.

  5. @Meshman thanks for the detailed report. The symptoms like you're describing are the indication of connection failure FROM chromecast TO the phone. For example, chromecast is in the different subnet with one way routing allowed (so you can find and control chromecast from the phone), or firewall/network setup allows some types of connections and disallows others (Isolate clients router/access point option), or you have firewall on the phone denying incoming connections for your network. More details here: 

     

  6. Keep service obviously won't help as headunits like to shutdown completely and kill apps (almost) without the notice.

    There is a standard "shutdown" Android broadcast message android.intent.action.ACTION_SHUTDOWN which alows apps to store the state before device is switched off.

    On the earlier days of Android headuinits, some OEM modified that for some reason to something like OEM_NAME.intent.action.ACTION_SHUTDOWN and the next OEM which used the same firmware/source, modified it further to OEM_NAME2.intent.action.ACTION_POWER_OFF, etc., etc. and now each headunit OEM has own SHUTDOWN intent variant - just due to that original headunit firmware developer who modified the system intent name and the every next OEM2-3-4 using global find/replace for "OEM" to "OEM2-3-4" in sources.

    If you don't know the shutdown intent for your headunit, try to write "android.intent.action.SCREEN_OFF" (no quotes) in Settings / Misc / Shutdown Intent. Provided that headunit switches off screen when it's powered off, that may help.

  7. @TONY CORISH that requires sending video which will destroy phone battery, increase latency, bring more chances for stutter, and reduce audio quality due to the recompression. Given all that it's not appropriate for a music player focused on audio quality.

    There is an alternative way to render visualizations on Chromecast device/TV itself, but it's not a small project and it requires large % of user base requesting this. Thanks!

  8. @Si64 it should work out of box - Poweramp sends album art which is shown (I hope it's shown for you) in Android notification and Android lockscreen. BT uses the same image. May be your BT stack is dependent on Now Playling list - ensure "Now Playing List For Connected Devices/Apps" option is enabled in Poweramp. May be there is another issue with the BT stack, for example it doesn't like too large images, or image format. Try to toggle options Settings / Album Art / "Send High Resolution Album Art" and "API Compatibility". Thanks!

  9. This functionality is implemented (or not) by the firmware and player has "no say" in how BT protocol works, unfortunately. There are some options in Poweramp which will disable Album art or may otherwise break this functionality, but if it's supported by firmware/phone/end-device, it will work out of box on default Poweramp settings.

  10. @AlbertWest Poweramp doesn't trigger "foreground" scanning process (when there is a notification with some scan progress and scanning happens in the "foreground" background). Instead, Poweramp tries to scan as much as possible while it's in the foreground (while UI is on top or when playing). Recent Androids kill background app in about 30 to 60 seconds (and some Chinese firmwares will do that sometimes even for the foreground app) - so scan may not complete fully for a larger library. Poweramp will attempt to scan rest of the library next time unless scan is disabled in Settings / Library / Scanner.

    The "foreground" scanning with the notification and progress was there, but was removed by user requests.

  11. @soundpimp for Poweramp and flac, the bit rate estimation during tag scan differs from the playback estimation. The first one excludes tag size, but the playback estimation (as implemented in ffmpeg) uses whole file size for the estimation, including metadata. This is usually OK for the moderate image sizes, but if you push very large image for some reason, indeed it offsets displayed bitrate while playing.

    Thanks!

×
×
  • Create New...