Jump to content

andrewilley

Administrators
  • Posts

    21,154
  • 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 andrewilley

  1. First, Poweramp processes all audio in stereo PCM (32/64 bit). It does not pass any formats through natively, they need to be converted to PCM first. So no native DSD I'm afraid.

    And as for above 768kHz? That would make a great app for annoying bats I guess, but I'm not sure how much mainstream traction such a feature would attract. As far as I know, 384kHz is the highest you'll get.

    Andre

  2. 2 hours ago, military vehicles said:

    I've tried email but they just keep giving me the same copy paste email response 👍 

    Has it occurred to you that if you keep asking the same question, you'll most likely get the same answer?

    Android apps are meant to identify in their code whether they want their audio output to be able to be managed by external apps, and if they don't then the content is not meant to be processed. Using the DUMP permission (which is something of a hack) expands on that number, but there will still be apps which don't even identify themselves as playing audio at all, which the PS-EQ won't touch.If an app can be equalized though, just select it from the Known Players list and it should work fine.

    Andre 

  3. That's already a feature. When you use Save/Assign to store an EQ Preset, there are a number of tickboxes that you can select to so it can be automatically applied in specific situations - for example for specific folders, albums, genres, even individual songs, or particular Output devices.

    To save for the current Bluetooth device, tick only the name of the device in the list. Don't also tick the overall Bluetooth option, as that will apply it to all BT devices.

    image.png

    Andre

  4. 35 minutes ago, André Inácio said:

    I currently use OpenSL because the other outputs have a huge delay (600ms or more)

    That's perhaps more of an issue of higher resolutions and larger buffer sizes to be honest. Not that latency really matters much for pure audio playback.

    image.png

    After an Android update, it might be worth setting the Outputs menu back to defaults and seeing if that helps, but sometimes it's just changes in the ROM that cause the issues.

    Andre

  5. If you can get someone else to do the porting work, that would make sense to me. Not sure whether its design ethos fits too well with the Apple way of doing things though.

    But otherwise, I would say only once the Frequently Requested Features list has been addressed would it be time to think of new platforms. :) 

    Andre

  6. POPM is a bizarre tag anyway. It consists of a text string to identify the user (meant to be an email address, but it often isn't) then a null-byte separator, then a one-byte number to indicate the chosen rating on a scale of 1 to 255. Generally apps convert this byte to a more user-recognisable 1-5 figure - so a byte value of 64 often represents '2' in the 1-5 scale, or 196 would be a rating of '4'.

    The reason for the string is because ratings are meant to be personal to you, and you wouldn't want to see someone else's rating. Thus there can actually be more than one POPM tag in a file for different people's ratings. Mostly this is not filled with a username/email though, and often you'll find the writing application's details are in there instead - e.g. Windows tends to use "Windows Media Player 9 Series". 

    Oh, and just to confuse things further, after the rating byte there is an optional play count figure for the song - which would also be user-specific of course. Rarely used. 

    And all of the above assumes that all apps follow the spec rather than inventing their own variants.

    Andre

  7. 35 minutes ago, André Inácio said:

    I'm glad he's okay, I'm looking forward to new updates, unfortunately in the last update, my smartphone stopped working hi-res. sad

    Last update of Android, or Poweramp? What device? Rather than using the experimental High-Res Output mode, try something like AAudio or AudioTrack which on recent Android versions support high-res settings.

    Andre

  8. @Loweaul Ah, OK, in which case yes I agree that the remaining selection list can become centred rather than being tethered closer to the bottom of the screen. Might be something to do with the keyboard popping up previously? Has no functional implication that I can see though, as the background elements are not accessible either way.

    For some reason it doesn't seem to happen all the time though - I can't get it to occur now for example. And some popup menus present themselves mid-screen anyway. e.g. the long-press popup shown on the Player Screen is text-oriented and in the middle of the screen, whereas the popup triggered by long-pressing in a list is a smaller icon-based format at the bottom (to allow you to still access and scroll the background list). If the background is not going to still be accessible, I think I prefer a centred approach, as tall as necessary/possible to avoid needless scrolling.

    Andre

  9. @Loweaul Not quite sure why this is a bug? When you cancel the '+' function for creating/naming a new playlist, it just takes you back to the original screen for choosing existing playlist(s) instead. You can just close that screen if you want to cancel and leave the 'Add To Playlist' function completely.

    Andre

  10. Some Bluetooth devices send their own resume commands upon establishing a connection, which can cause playback to commence just because a connection has been established. Most people do not want this behaviour, so there is an option for PA to ignore such instances for up to 10 seconds after connection, see Settings=>Headset/Bluetooth=>Ignore Bluetooth Commands. Set it to zero if you do want the headunit to assume control.

    Poweramp also has its own controls for restarting playback on connection, see Settings=>Headset/Bluetooth=>Resume On Bluetooth.

    Personally I would suggest ignoring whatever the headunit may (or may not) be sending, and use PA's own resume setting instead - which in theory should give you more consistent behaviour. If your vehicle supports it, Android Auto generally provides a better experience than just Bluetooth.

    Andre

  11. [I've moved this discussion out from the Build 981 Release thread, as it has nothing to do with issues with that particular build]

    From the 'Year' Category you drilled down into '2020', which would show you any albums that are notionally treated as being from 2020. Remember that in cases where songs from one album which have different Year tags (e.g. Collections or Best-Of albums) Poweramp has to make a best assumption as to which year it should choose to refer to the whole album.

    When you then drill down to view a single Album - in this case, due to the limited tagging, you selected 'Unknown Album' - you would see all of the songs in that album, regardless of the various Genre, Year, Artist, etc tags. The Album level view would no longer be filtered to show 2020 songs only, it would show the whole album.

    If you want to only see songs which have a specific tag of 2020, once you have opened the Year in question ignore the album titles and tap on 'All Year Songs' at the top instead. Every song in the resulting list should be from 2020.
     

    Personally, I have almost no songs with blank Album or Album Artist tags by the way. I give them a fake name for sorting purposes, to avoid ending up with albums in the list with just one song inside. I have several generic album names I use - such as "(Singles)" for most rock/pop stuff, "(Film Music)", "(TV Themes)", "(Musicals)", etc. I enclose the names in brackets by the way, so they get sorted at the start of Album lists rather than being stuck somewhere randomly in the middle of a long list of album names.  

    Andre

×
×
  • Create New...