• Announcements

    • andrewilley

      Poweramp v3 Project Update   04/24/2017

      As you may be aware, the Poweramp developer has been working hard on an updated material design user interface for Poweramp v3 which required a full ground-up rebuild of the code and is taking some time to get to a beta-test stage. See the forum thread for more details and to discuss.    

maxmp

Moderators
  • Content count

    965
  • Joined

  • Last visited

Everything posted by maxmp

  1. Poweramp alpha3 build-703 Poweramp alpha3 build-704 (N preview 3 quick fix, not recommended for any other Android versions, as it wasn't tested outside N preview 3) Known issues: - on some device @ N preview 3, OpenGL surface can fail to be restored, causing no visualization in Poweramp Google Play testing Opt-in URL: https://play.google.com/apps/testing/com.maxmpz.audioplayer (Use this URL again for Opt-out if needed.) This is alpha version of upcoming major Poweramp release. Please make backup of your existing Poweramp app/settings/db before installation as you won't be able to rollback to Poweramp v2 without alpha uninstallation, causing settings to be lost. You can install it over your existing v2 or any alpha version (your purchase and settings will be carried over). At this time, only ARM processors are supported. We'll add Intel support for later beta builds. Min. supported Android: 4.1. Skins are disabled in alpha as UI is partially changed and there is no point in (re-)building skins now. Alpha-3: - 704: few fixes for N preview 3 - added DVC support for Hi-Res Snapdragon 24-bit PCM variant (e.g. LG Gx/v10, HTC A9, etc.)- Hi-Res support for Sony Z3, Meizu 5 Pro, Lenovo Vibe X3- Look and Feel / Status Bar/Notification / Notification Colors option to override non-standard ROM notification colors- mp3 vbr seeking improvements- 2 Hi-Res API variants (Sony Hi Res and Snapdragon 24-bit offload) for Sony Z5/P- option to always process/send album art (useful for smartwatches)- bt pause/resume polishing- scrobbling fixes, removed obsolete ScrobbleDroid support- album art downloading update- language selection fix- better current output device detection (wired headset vs bt)- other few small fixes
  2. Planned features for Poweramp - UI improvements (we'll keep 3rd party skins compatible) - support for album grabbing apps via system library album art support - google music song info - system library playlists support - settings export/import (to/from sd card, including equ/tone presets) - advanced tag editing - rating sync'ing from/to tags - optional (enabled by default) support for standard android .nomedia files - special treatment for user created playlists/queue, which keeps songs in playlist even if songs are deleted/temporarily unaccessible to Poweramp Bunch of 3rd party and in-house plugins, which optionally enhance Poweramp in some direction for users, who need it. We don't put everything in "monster" Poweramp package, instead, these are separately downloadable plugins: - cloud services via 3rd party plugins - smart playlist via 3rd party plugin - online radios via 3rd party plugins - automatic tag matching via 3rd party plugin - lyrics via 3rd party plugins - audio effects via 3rd party plugins - Sony Smart* accessories support via plugin - "Social" Poweramp plugin for FB, VK.com, Twitter
  3. Applies to Internal DAC only (Wired Headset/AUX in Poweramp output settings). Please post your device (with optional ROM/Android version) if Poweramp alpha Hi-Res audio works for it. If it doesn't work, check this thread:
  4. Your device supports Hi-Res audio _output_* (at least 24bit, at least 96khz sampling rate), but Poweramp v3.0 alpha doesn't support it? Request the support here! Please provide (requests without these items will be deleted): Device model ROM version (Android version, stock/OTA/Custom ROM) Why do you think your device supports Hi-Res (link to device features, etc.)? A copy of your device's /etc/audio_policy.conf file may be helpful. * Please note, this is for Hi-Res output requests, just playback (with resampling) of hi-res audio is already implemented by Poweramp v2.0 for all devices/ROMs.
  5. What should be the next build priorities?
  6. Hello, few updates on development status: - development never stopped, but the chunk is hard to chew for 1 person, for sure - the light can be seen at the end of the tunnel - posting my recent git log here: And thank you guys for all your moral support here!
  7. Two news. The bad one: an additional round of device specific optimizing and polishing is required for Poweramp v3.0, this delays release. As indicated before, v3 will run on Androids 5.0+ (O included). Poweramp v2 stays for 2.3-4.4. Good one: everything works and I'm on finishing steps. Just stuff like Samsung Mali driver bug in phones up to S8+ causing inability to render some simple stuff in 60fps need to be taken care of (if interested, some Samsung Mali based devices - the ones with Exynos - have an issue in OpenGL HWUI renderer - they lag at render like 40 nine-patch images probably due to HWUI caching issues on those devices). Keep tuned.
  8. Sorry for the delay) I think I'm quite good at programming, but unfortunately, I'm bad on managing other developers, so basically I do everything by myself. That of course is not speeding things up. Also, I try to polish each feature until it works 100%. It's not possible to predict how long exactly that or this feature will take time to complete. Especially on Android, when you may need to write whole functionality from scratch as platform-provided one is buggy, is not reliable, or plain doesn't work on some devices/ROMs. Currently, planned v3 beta release month is set to May. This will be full featured v3 (it's basically alpha3 + new UI + fixes for recent ROMs, but not more). Thanks!
  9. Poweramp alpha2 build-702 Google Play testing Opt-in URL: https://play.google.com/apps/testing/com.maxmpz.audioplayer This is alpha version of upcoming major Poweramp release. Please make backup of your existing Poweramp app/settings/db before installation as you won't be able to rollback to Poweramp v2 without alpha uninstallation, causing settings to be lost. This version is focused on Hi-Res output and Album Artist support. You can install it over your existing v2 or v3-alpha1 installation (your purchase and settings will be carried over). At this time, only ARM processors are supported. We'll add Intel support for later beta builds. Min. supported Android: 4.1. Skins are disabled in alpha as UI is partially changed and there is no point in (re-)building skins now. This build fixes issues reported for 701: - some non-english tags are better handled for mp3 - non-rectangular embed art is handled properly in notification - fixed album art when playing Playlists and Queue - dsf files should be played without extra click between them - resume after bt call is adjusted a bit - issue with MusicFX button should be resolved now - typos fixed - eq preset assignment for usb/other outputs Alpha-2: - experimental Hi-Res output for 24bit 96/192khz phone internal DAC and USB DACs where supported by device - external USB DAC support for 24bit 96khz (Android 5.0) and 24bit 96/192khz (Android 6.0) via AudioTrack output - output plugins are assignable per specific output (headset, speaker, USB DAC, etc.) - output settings, such as sample rate, sample format and few other advanced options are available per various output/device combinations - detailed audio system information available via right drawer top (i) icon - actual output bit width/sample rate, output device is shown under frequency response view in right drawer and equalizer screen - greatly improved spectrum visualization synchronization to audio - visualization delay option is per output now as well - visualization preset advance/shuffle by time - USB OTG storage access @ Android 6.0 via Storage Access Framework - audiofocus volume duck option - experimental support for wired headset button long press (Android 5.0+) - headset button beep is played ASAP - 30/50/100 volume levels (Settings/Audio/Advanced Tweaks) - custom volume panel (Settings/Audio/Advanced Tweaks) - Album Artist tag support. Albums are grouped based on Album Artist tag, where available. Album Artists category added as well (hidden by default). - Settings / Folders/Library / Lists / Join Albums option Known Issues: - scrobbling can fail sometimes for some scrobbling apps
  10. Prerequisites: Install Android SDK (you may need to install various required components, see System requirements here – http://developer.and.../sdk/index.html). Current Poweramp skin build script is ADT 23.0.5 compatible.Ensure you have BOTH Android SDK Build-tools 21.1.1 and 20 installedDownload/extract skin projects, import into Eclipse (get latest poweramp_api sources: https://github.com/maxmpz/powerampapi).Now you're ready to review, make modifications in Eclipse and compile/build skins in console. Note that you can build skin only from console with Ant, thus, ensure “ant” command is in path and Ant generally works. You can't build/”run” skin from within Eclipse, it will probably find non-existent errors (just “delete” errors in Eclipse Problems then, as they are not relevant anyway).How Poweramp themes work in short: Poweramp uses standard Android layouts/styles/themes and resources (http://developer.and...-resources.html)Poweramp contains “default” skin, other skins inherit from this one, thus it's not necessary to define each and every image, style, layout, etc. to build your skin – you just redefine parts you want to redefine.Poweramp demo skin sources include Ant build skin, which can be used both for developing/debugging your skin via jar packaging (“ant jarpush”, which immediately uploads skin jar to the connected device/emulator), or for APK building.Poweramp detects installed skins (either built as APK or as jar files in appropriate folder on sd card) and shows them in Settings => Look and Feel => ThemePoweramp detects skin change on Activity.onDestroy, i.e. when some Poweramp screen closed/navigated away with back button. Poweramp skin is: An Android project with specific ant build scriptskin_lib library project, which is referenced by your skin project. skin_lib contains necessary AndroidManifest.xml definitions, some java/xml code for InfoActivity (the default activity which is started when skin icon is pressed in launcher) Skin APK which contains skin resources and also some Activity (sample skins contain Activity which has just small hint/about text and button, which opens Poweramp theme selection dialog via intent).Skin APK manifest should contain <meta-data android:name="com.maxmpz.PowerampSkins" android:value="true"/>. This is used by Poweramp to find skin “app”, installed on the device.Each theme in skin APK/jar is listed in values/skins.xml. There are 3 arrays (1 integer array and 2 string-arrays). First one contains (<integer-array name="poweramp_skins">) list of skin themes, second list contain skin names (<string-array name="poweramp_skin_names">), and third – skin author names (<string-array name="poweramp_skin_authors">). Basically, you can start with modifying these strings as needed in sample skin sources.Selected skin theme/style applied to the whole application (either on user theme user selection in theme dialog or when Poweramp starts for the first time). Android styles and various other resources support some sort of “inheritance” - meaning app theme can be derived from some other global theme, which only few styles/images/dimensions/etc. redefined where needed. Poweramp exploits this in its theme implementation, this simplifies skin development a lot, as skin author can start with “default” skin and modify elements he/she wishes gradually until desired result achieved. For example, one skin author can redefine just Poweramp backgrounds, buttons, but leave icons as is. While another author can change all fonts, icons, some layouts, but leave “as is” backgrounds and buttons from default theme. Generally, only limited number of styles could be modified to get absolutely different look from skin, but anyway, almost each style/resource in Poweramp can be overridden, though it's not strictly required or needed. How to start building your own skin: copy some provided skin source/template (e.g. skin_template) and name it as desiredensure the skin_lib project is available to Eclipse and ant build tools (skin_lib project is near your skin project folder) rename skin_lib/local.properties.EDITME to skin_lib/local.properties and edit it: point sdk.dir to your android-sdk root directory edit <your project>/AndroidManifest.xml – change <manifest> package attribute to some developer/skin unique name edit <your project>/res/values/strings.xml app_name string – this is app/skin name, visible in Google Play/device Apps tab, etc. rename <your project>/local.properties.EDITME to <your project>/local.properties and edit it: point sdk.dir to your android-sdk root directory point key.store and and set key.alias to your android developer keystore/alias. Only needed for release version of APK for publishing on Google Play <optionally> edit import project name in .project file (<name> tag) and “Import...” project into Eclipse project. Any text editor can be actually used for skin creation, Eclipse or other IDE is not required. Skin build process: ant – (default task) - Simple build skin as jar: while in skin directory Build should end with something like: BUILD SUCCESSFUL Total time: 1 secondant jarpush - build (debug) skin as .jar and upload to the device New skin is immediately available in Poweramp themes selection dialog. This is preferred way of debugging skins, as Poweramp can also detect jar changes immediately – you just need to close/return from Poweramp screen and start it again.ant apkpush – build (debug) skin as .apk and upload/install to the device.ant dist – build release skin as .apk and put it named as ${ant.project.name} into /dist directory. These builds are numbered appropriately with version.num, but AndroidManifest.xml is not modified automatically, i.e. you should manually increment version numbers there for updates on Google Play.Namespaces: It's important to understand how namespaces work in skin xml files and how to properly use them to override some Poweramp style, image, layout, etc. Various styles, images, strings, ids, almost anything in Android xml resources and resources themselves are identified by simple name within some namespace. By default (when namespace part is not specified), Android resource compiler uses project package name. Poweramp package name is “com.maxmpz.audioplayer”, thus all resource references for Poweramp should be prefixed with “com.maxmpz.audioplayer:” (with semicolon) to be visible to Poweramp. Simple example: <item name=”Text1”>...</item> - this defines some Text1 attribute, which is not visible to Poweramp, nor overrides anything for custom Poweramp skin. <item name="com.maxmpz.audioplayer:Text1">@style/Classic_Text1</item> This overrides Poweramp Text1 attribute and forces Poweramp to use skin Classic_Text1 style everywhere, where Text1 attribute is referenced in Poweramp. com.maxmpz.audioplayer namespaceprefix should be used also for in-layout ids (as Poweramp should be able to find widgets by known-by-Poweramp ids), strings, dimen(sions) and other resources. This prefix shouldn't be used for the skin customized styles or other possible resources which skins adds to Poweramp – including new drawables, icons, custom layouts, colors, etc. You can see clear examples of namespace prefix usage in skin_classic sources. Sample projects and resources: skin_lib skin_lib project is not a sample project, but a library project, which should be referenced by your skin project. All skin SDK sample projects reference skin_lib, so if you copy/paste some sample project into the same directory where skin_lib project is located, reference is already valid. Otherwise you should edit <your project>/project.properties file and point android.library.reference.1 property to your skin_lib project location. To setup this project, please rename skin_lib/local.properties.EDITME to skin_lib/local.properties and edit it: point sdk.dir to your android-sdk root directory NOTE: please try not to customize/edit skin_lib project, except local.properties file. Instead, you can override everything in your skin project. The skin_lib library provides: basic AndroidManifest.xml definitions, required for Poweramp Skin APK (meta) basic resources, required for skin - /res/public.xml, full InfoActivity implementation, which is capable of: selecting skin (multiple skins in one APK are supported) supporting Poweramp themed icon hiding skin icon from launcher few basic string labels in strings.xml ant build script rules for both library project and for the skin projects reference Poweramp APK which is required in skin build process skin_template This is empty skin, which can be built out of box (please see section How to start building your own skin). “Empty” means there are no overrides to default Poweramp skin at all. two_skins This is almost empty skin (just song title color override), which shows how to implement 2 or more skins in one APK. skin_classic This is full source of Poweramp Classic Skins, which include many skin overrides, graphics, layouts, etc. skin_custom_info_activity This sample skin project shows how to override skin_lib InfoActivity and add some extra buttons into it. This project tries to reuse as much as possible from skin_lib, derives activity class from skin_lib InfoActivity, but fully overrides AndroidManifest.xml. reference_resources These are Poweramp resources (animations, colors, drawables, layouts, dimensions, etc.) resources given for reference. As Poweramp skins are derived from default skin, please use reference_resources/values/default_styles.xml as primary source for available "skinnable" styles. default_style.psd Default theme "source" photoshop file. This is the file, from which all Poweramp graphic resources were generated for default theme. Note that the file is heavily organized into: Layer Comps. Please enable Layer Comps in Photoshop (Window=>Layer Comps) to quickly show/hide appropriate Poweramp layouts/elements. Grouped Layers. There are various groups, which visibilities are controlled by Layer Comps Layer Names. These can be directly used as resulting image name. Various additional words after space should be ignored in the name (such as "copy", "xdpi", "mdpi", etc.). Default skin also adds "matte_" to each image name (as Poweramp has also few other themes, with graphics prefixed by theme name). Prefixing is not necessary for custom theme, but advised. Also, this is the only way to have two or more skins in one APK. Layers. All Poweramp generated graphics placed into separate Smart Object layers. Those layers, which are not Smart Objects, are not used in Poweramp, but just there for visual help (i.e. android wallpaper, android statusbar, some backgrounds, etc.). Each Smart Object can be separately opened, edited and saved. Such separate Smart Object documents have specifically assigned dimension (width x height) to match icon and layout sizes. Some Smart Objects are duplicated right in PSD file for xhdpi/mdpi resolutions, some are not (where not needed). 9p files. Note that some layers have .9 suffix. This means, they have 9-patch "meta" black lines added (via "9p" named layer) and should be saved as "layername.9p.png" Smart Object Layer Comp. Some images have few states, for example, buttons have normal, pressed, and focused states. These are all there, implemented via Layer Comps for such Smart Objects. When such Smart Object double clicked in Layers tab, Smart Object document Layer Comps tab will show available states. Normal state image is saved with Layer name, without suffixes (button.png), other state - with lowercase state name after underscore "_" (button_pressed.png, button_focused.png). This is true for Poweramp skins, you can follow any other naming scheme as long as you properly put your drawables/images names into appropriate XML files. Lollipop (Android 5.0) compatible skins You may need to rebuild your skin with latest poweramp_skin_sdk revision. Please check poweramp_skin_sdk changelog.txt for detais. Update android:targetSdkVersion to 21 in AndroidManifest.xml of your skin and in project.properties Android 5.0 doesn't support skin defined attrs.xml (style attributes) anymore. Those won't be resolved and skin will fail to load. Please remove such attributes from your skin xml code and use one of the following workarounds: just use some styles/values directly, instead of using custom skin attributes use some Poweramp defined attribute which can be safely used for skin (e.g. com.maxmpz.audioplayer:background can be used freely as skin attribute, as Poweramp uses it internally for sub styles) use skin_ref1..skin_ref10, skin_bg1..skin_bg10, skin_color1..skin_color10, skin_dimen1..skin_dimen10 attributes (see reference resources values/attrs.xml for details). This is provided by Poweramp build-565+
  11. Download Poweramp alpha-build-700 (or use the new 'Downloads' tab at the top of the page) This is alpha version of upcoming major Poweramp release. Please make backup of your existing Poweramp app/settings/db before installation as you won't be able to rollback to Poweramp v2 without alpha uninstallation, causing settings to be lost. You can install it over your existing v2 installation (your purchase and settings will be carried over). At this time, only ARM processors are supported. We'll add Intel support for later beta builds. Min. supported Android: 4.1. Skins are disabled in alpha as UI is partially changed and there is no point in (re-)building skins now. This Alpha is focused on Audio Engine and Visualizations. This is why Visualizations are enabled by default. It can be disabled via right drawer menu, and we'll add option to disable it completely later. Changelog: - new audio engine - Poweramp now uses 32-bit float sample representation - Poweramp core DSP now uses 64-bit float internal math, helps a lot for accurate high amplification of basses - Reverb with presets, improved StereoX effects - Tempo control - mp3, aac, ogg vorbis, opus and other lossy formats now decoded directly to 32-bit float representaion (no intermediate conversions) - opus, tak, mka, dsf, dff formats support - Poweramp now always properly fades in/out and ramps volume changes to avoid clicks and pops during any transitions (resume/pause/seek/etc.) - Poweramp now applies gapless smoothing between gapless tracks - Poweramp now always uses own resampler - optional SoX very high quality resampler - output Dithering options - OpenSL optimized output - support for 3rd party plugins (DSP/Decoder/Output) - visualizations - full support for milkdrop presets - v1 and v2 (with shaders) presets supported. Support for v2 presets is best on OpenGL ES 3.0 enabled devices - milkdrop presets can be loaded from sdcard and downloaded as APKs from Play - support for 3rd party preset APKs - spectrum visualizations - main player right drawer for fast Equ/DSP/Visualizations access - many other changes, more changes are planned Planned features for next betas: - improved Album Art area navigation - new spectrum-like seekbar - improved tablet UI - improved lists - various plugin APIs published with sample apps - improved info/tag editing - some cloud support - DNLA
  12. Download Poweramp build-588 (or use the new 'Downloads' tab at the top of the page) Download Poweramp HD Skins build-8 NOTE: 860xxx build under Spoiler below is for Intel based devices - it brings 2x-6x reduced CPU usage and better battery life for such devices. You can install the intel optimized version on devices with Intel inside logo. It won't work on ARM based devices. If you install this one you won't be able to install 'usual' version without full reinstall and settings loss! Recent Changelog: 589: fixed issue with Android 6.0 @ Intel based devices (build exists for Intel devices only) 588: album art downloading update 587: rebuilt with previous Android Build Tools version to fix UI language selection (Android 4.4- 586: fixed embed covers @ Samsung S7/E 586: added link to v3.0 test build (Settings, Android4.1+/ARM-only) 585: fixed album art downloading 584: fixed couple of minor issues @ Android 6.0 583: fixed tag editing on SD card @ Android 6.0 583: fixed issue which prevented some skins from loading on Sony devices @ Android 5.0+ 582: fixed issue with seekbar @ Android 6.0 If for any reason you have problems when you install the latest build, you can re-download older versions of the Regular (ARM) Builds or the Intel Chipset Versions. Caution should always be advised when rolling back any software, just in case new settings or features may have been added which may no longer be compatible with older versions. You'll probably be fine of course, but install at your own risk.
  13. Poweramp build-589 INTEL ONLY VERSION 589: fixed issue with Android 6.0 @ Intel based devices
  14. Version

    95,601 downloads

    Poweramp v2 for INTEL-based Android devices. For more information, see What's New in Version INTEL Build 589 - 589: fixed issue with Android 6.0 @ Intel based devices
  15. Small update on UI progress: Tthe UI redesign development is finishing, but a chunk is too big to swallow, thus the delays. Basically, the animations, transitions, lists, grids, seekbar, etc. were built from zero, as Android platform just doesn't give what's needed.
  16. The fix is ready and will be published after small in-house testing in a day or so. Thanks!
  17. Quick fix (build-704) is available here (same link as 703, it will suggest 704 for you): Please note, that this build hasn't been tested on non N devices. Also, N preview 3 (on some devices, like Nexus 5X) introduced issues with OpenGL driver, causing Poweramp visualization become black sometimes. As UI (and album art/visualization area, specifically) is changed in development UI builds anyway, so no point to fix that for Poweramp Alpha + N preview 3.
  18. Can you please send (PM) your /etc/audio_policy.conf file and build.props file? I'll check if adding Hi-Res is possible for this device. Thanks!
  19. Please also see small alpha FAQ here: Check also (growing) list of supported Hi-Res output Android devices: Request Hi-Res support if your device supports it, but Poweramp doesn't:
  20. Version 703/704

    25,847 downloads

    Poweramp v3 (ALPHA-3 test builds 703 / 704) for standard (ARM-based) Android devices. Released: 16 April 2016 This is alpha version of upcoming major Poweramp release. Please make backup of your existing Poweramp app/settings/db before installation as you won't be able to rollback to Poweramp v2 without alpha uninstallation, causing settings to be lost. You can install it over your existing v2 installation (your purchase and settings will be carried over). At this time, only ARM processors are supported. We'll add Intel support for later beta builds. Min. supported Android: 4.1. Skins are disabled in alpha as UI is partially changed and there is no point in (re-)building skins now. Alpha-3: - added DVC support for Hi-Res Snapdragon 24-bit PCM variant (e.g. LG Gx/v10, HTC A9, etc.) - Hi-Res support for Sony Z3, Meizu 5 Pro, Lenovo Vibe X3 - Look and Feel / Status Bar/Notification / Notification Colors option to override non-standard ROM notification colors - mp3 vbr seeking improvements - 2 Hi-Res API variants (Sony Hi Res and Snapdragon 24-bit offload) for Sony Z5/P - option to always process/send album art (useful for smartwatches) - bt pause/resume polishing - scrobbling fixes, removed obsolete ScrobbleDroid support - album art downloading update - language selection fix - better current output device detection (wired headset vs bt) - other few small fixes
  21. Build-702 didn't support DVC on Gx series (Snapdragon Offload PCM 24 bit variant). Support for DVC for this Hi-Res variant was added in build 703, which will be released today-tomorrow.
  22. Poweramp doesn't have driver level access to USB DACs, so anything beyond android facilities is not possible here.
  23. .jpg, .jpeg, .png are checked for album art (during scan). Though, due to quite complicated priority system for album art (as there are multiple possible sources of covers for tracks), some other image can be selected. The only exception if <album_name>.jpg - for given album, Poweramp probes it name with just .jpg extension.
  24. One menu with ~40 buttons you mean (the number of various buttons in left/right drawer and action bar) ?