Jump to content

andrewilley

Administrators
  • Posts

    21,151
  • Joined

  • Last visited

 Content Type 

Profiles

Forums

Blogs

Gallery

Downloads

Poweramp Knowledge Base

База знаний Poweramp

Poweramp知识库

Poweramp Equalizer Knowledge Base

База знаний Poweramp Equalizer

Store

Events

Ideas

Everything posted by andrewilley

  1. @maxmp Could you take a look at this? The files don't play in PA (although the file tags are read fine) but I don't know enough about Vorbis audio within OGG containers to see why. If I remux it into an MKA container, it plays fine. Andre
  2. If it doesn't happen with the EQ button toggled off, what about with the button on but all sliders/knobs set to flat? Andre
  3. That was what I originally thought this post was about, but having seen the screenshots I think it's more about Visualizations. Those extra YAPS spectrum options obscure the main app control icons and other interface elements though, so I don't personally tend to use them. Andre
  4. Does it happen with all music player apps, or just this one? What happens if you disable the EQ processing in the controls screen? I assume you don't have any other audio processing apps running at the same time? Andre
  5. Ah, that sort of source. Does make it a bit harder to work out what got broken of course. However for me, even the second sample file that you uploaded is also fixed just as easily by simply opening it in MP3Tag and immediately saving it again, no need to make any changes, and then the full ID3v2.3 tags are picked up. Make sure you rescan after copying it over to your phone so the old file info is not still being used. 01 MyTVandYou - MP3Tag resave.mp3 Andre
  6. I was referring to the YAPS skin settings, not Poweramp's settings. However what you seem to be referring to here is a Visualization, and the one that you have chosen just happens to be a blue spectrum analyser display. There are literally hundreds of these supplied in Poweramp, or you can download and install new ones from the internet (they are referred to as "milkdrop presets"). They vary from simple bar displays to some really weird psychedelic patterns! If that's the case, you can turn them on and off, or go fullscreen, using the Visualization icon (left-hand side, under the artist name). Then you can choose which style you want to see by tapping on the selection bar at the top of the screen while the visualization is being displayed and pick from the list. Andre
  7. The mini spectrum-analyser display on the main screen (which is what I assume you are referring to?) is controlled in YAPS Settings=>Waveseek/Spectrum=>Spectrum for Main UI. There are various pattern styles and colours available. Personally I usually just turn it off for the Player Screen as I feel it clutters the main display, but there are about 20 options to choose from. Andre
  8. I can't answer everything there, but Audio Accessory Mode simply means that the USB-C port (and the device plugged into it) is able to process analogue audio via pins on the USB-C connector, so the dongle or headset does not need to contain its own DAC. Basically it's like having a 3.5mm socket for audio generated by the phone, but the analogue L & R audio is routed via the USB-C connector instead. Not many devices support this as far as I know. Andre
  9. Technically TSOA (and TSOP, which was in the earlier B.T.A. file) are not defined in the ID3v2.3 spec as they were only added for ID3v2.4, but the same goes for some other tags which are applied somewhat loosely by apps. I was also puzzled by "ID3_TSP" and "ID3_TSC" entries, which I'm not familiar with. However since Poweramp doesn't parse any of these anyway, I can't see why their slightly-unexpected presence should cause the whole ID3v2 block to be ignored. And after simply re-saving the problem files with MP3Tag, those tags are all still present but the rest of the ID3v2.3 data is all read correctly. This is going to need Max to take a look as I'm sure it will turn out to be something slightly out of spec that is breaking the parser. @RetroGameReaper What was the original source of these files, and have they been re-edited since their original download? One file for example shows both iTunes and MusicBrainz tags. Andre
  10. Normally ID3v2 tags should override any v1 tags that are in the same file, which are only there for backward compatibility. But it does seem that again in the second example file (VAST,) only the v1 tags are being utilised. But again it is completely fixed by simply opening and re-saving it in MP3Tag, and then all of the v2.3 tags show up as expected (including genre, cover art and lyrics). Andre
  11. @frankmaxon I think the fact that it plays at all is pretty astounding. I'd never of this as an audio format until I Googled it. I rather doubt that there's likely to be much support for submodules or wide-screen monospaced comment text though. On the plus side, you probably get the award for most obscure file-format question of the year so far. 👍 Andre
  12. Definitely something slightly skew in the tagging data. If you open the file in MP3Tag and simply re-save it without making any content changes, it then reads everything fine in Poweramp. I'm guessing that either the ordering of the data might be a bit unusual, or one of the tags contains some information which is breaking Poweramp's parsing process. Foobar2000 on my PC reads the 'missing' items fine, but VLC does not see track#, artwork, etc. @maxmp ought to be able to tell us more anyway, and if there are more of this type of file in the wild then perhaps he might be able to create a work-around for them? [Edit] In fact, I wonder if Poweramp is only able to see the legacy ID3v1 data, at the end of the file. I say this as the Genre byte in the ID3v1 tags is '12', which decodes to "Other", Also only the content available in the v1 tags is visible in PA's Info/Tags screen. Andre
  13. As I said earlier, that is Poweramp's normal default mode. With 'Restore Per-Track Progress' turned OFF, older saved playback positions will not be restored when you play a track again. However the current song position (i.e. the song shown in the Player Screen) should always be remembered between sessions,and if you try that on a regular phone or tablet you will see that is the case. The problem here is most likely with your headunit not sending a standard Shutdown Intent, or not allowing the app enough time to cleanly save its status, when you turn the ignition off. You could try pressing Pause manually, and exiting the app, before you cut the power, that might allow the state to be saved. Max's reply in this thread provides a bit more background, but the playing song's position is only saved when PA is sent a shutdown command from Android; if the power gets cut before that occurs, then the position obviously cannot be saved: Andre
  14. @6b6561 While that can be an issue (and a Full Rescan often fixes it) in this case some tag data (Title, Artist, Album) is getting read, but not cover artwork or Album Artist. Looks more like a file issue to me. Andre
  15. The position within the current song in the Player Screen (e.g. listening 30 minutes into a one-hour track) should always be retained when you pause Poweramp and then restart it again later. That position should even survive a device reboot, but that does depend on your device's ability to correctly save its state during a shutdown. Sometimes you may find that Android car headunits (some of the no-brand Chinese versions in particular) can simply cut off power with the ignition without giving running apps the chance to shutdown gracefully and save their status. Is your Poweramp installation on an Android-based car headunit, or on a regular phone that is connected to the car via Bluetooth? The 'Restore Per-Track Progress' options are only for when you have gone on to play other music before returning to your long session. If you don't want to remember the last-played position when coming back to a song again later, turn those features off. Andre
  16. @Donnie1490 Your headunit is sending Repeat and Shuffle commands during the BT connection process: Poweramp is responding correctly to those commands and adjusting the modes as instructed. We don't know why Android 14 is passing these commands on when previous versions did not, but the latest release of Poweramp (e.g. build 981) include an option to attempt to ignore these command when they are not wanted. See Settings=>Headset/Bluetooth=>Ignore Repeat/Shuffle. This workaround will be improved further in future releases, as some instances of these commands still seem to be getting through. Andre
  17. If you long-press on one of the songs which has this issue, what does 'Info/Tags' show you? That should display the data stored within the audio file's embedded tags. Compare the results for that song with the same screen for a different song. I assume you are looking at a Folder view there by the way, as the problem file most likely won't appear in Artist or Albums views due to the missing data. In the case of the first song in your screenshot, it would appear nothing was found when the file was initially found during the library scanning process (filename shown instead of a Title, and no Artist/Album info either). Also, the subsequent entries all show filenames instead of Titles too, even though they do have Artist/Album details. Do you perhaps have Settings=>Library=>Lists=>Filename As Title enabled, or is the Title tag missing from their Info/Tags display? If the Info/Tags data seems correct, try doing Settings=>Library=>Full Rescan and see if the information is picked up by a new scan. Andre
  18. Looks like those files are not saved quite as PA is expecting them as per the spec. Could you temporarily upload the B.T.A. one somewhere for testing, as that is not indicating the presence of tags for Track#, Album Artist or a cover image. Please upload directly from your phone's storage, not from a separate master copy held elsewhere on a computer. Andre
  19. Poweramp actually keeps underlying log data of the last playback position of every file it has played. If you wish to resume at that position again whenever you next play the same song, go into Settings=>Library and enable 'Store/Restore Per Track Progress'. There is a threshold slider which controls how long a track needs to be for this resume function to work; normally this would be fairly long so it only resumes for tracks like podcasts, full-length concerts, audiobooks, etc, but if you set it to zero then every song will be resumed rather than starting from the beginning. This is a Global setting, which will always occur when a song is started - including by clicking on a new song, auto-advancing, or using the Next/Prev buttons. There is also a separate option for individual Folders and Playlists only, which you can get to via (menu)=>List Options from each Playlist or Folder view. Enable 'Per Track Progress' to resume playing at the saved playback position. You can also enable 'List Position' which means that when you use the 'Play' icon in the header of that folder or playlist, playback will resume with the last song you listened to - handy for continuing where you left off in a playlist containing a lot of songs, or large folder. These two settings are local to just the specific folders or playlists in which you enable the feature, so if you play from the Album Category for example then only the earlier (Global) Library setting will take effect. You can't set either of these features of only trigger when you manually start a new song from scratch though, they will happen any time a new song begins playing. Andre
  20. Has your version of Android (or the Google Assistant/Android Auto) been updated recently? I'm guessing it probably has as the shuffle/repeat mode change with BT connections only happened in very recent Android 14 builds. PA 981 does have a new option to try to help alleviate this issue in Settings=>Headset/Bluetooth=>Ignore Repeat/Shuffle, but the underlying cause is Android forwarding commands that it did not do before (usually from car headunits). To check if this is the case, see Settings=>Headset/Bluetooth=>Last Processed Commands and see what commands are being sent to Poweramp during the connection. Andre
  21. No, there's no specific limit other than the more files you have the longer scans/etc will take to complete. I would suggest not having too many files directly within any given subfolder as that could potentially slow system access down too. Andre
  22. Try long-pressing on one of the problem songs and select Info/Tags to see what the actual tag contents contain. Andre
  23. I'm not sure why foobar2000 (usually my benchmark for file handling) is creating a valid R128_TRACK_GAIN tag but is setting its value to zero. But that's definitely what it is doing - MP3Tag, TagScanner and even a raw dump of the bytes contained in the file clearly show that: It is also creating a header OutputGain value (which is an overall gain value to be applied to a track, regardless of whether ReplyGain processing is being applied) which Poweramp correctly detects and applies to the whole track. Remember that in addition to any quoted RG value inside tags (in this case, zero) PA also applies a user-configurable offset whenever an RG tag is present - which by default is +5dB - to counter the unexpectedly low volume that the RG spec otherwise defines. If you set that offset value to zero, then only the OutputGain value in the header will get applied, as RG will become nothing (zero plus zero). But yes, using a different format, or a different container for the same audio data, may well solve the problem. Andre
  24. You can't I'm afraid. When you use the 'Shuffle' icon (either in a list header or on the Player Screen) the current playback sequence is randomised so that each new track is a random surprise. What you can do if you want to see and/or adjust a randomised Playlist is to use the 'Re-sort' option in that playlist's three-dots menu, and choose 'Shuffle'. That will permanently re-order the songs in the list into a new random sequence. This has the advantage that you can return to the list at any time and see and move songs around, or you can resume playing a long shuffled list exactly where you left off last time, etc. On the downside though, the change is made to the layout of the original playlist, so you cannot recover the original song order if that was important to you. There is a popular Feature Request for a 'Now Playing' view like the one you mentioned though, which would allow you to see a flattened list of the currently planned song order - regardless of whether that order is based on Categories or Shuffled. You can vote for that feature here, although it's currently already the most requested item: Andre
×
×
  • Create New...