Jump to content

6b6561

Approved Members
  • Content Count

    69
  • Joined

  • Last visited

 Content Type 

Profiles

Forums

Gallery

Downloads

Knowledge Base

База знаний

知识库

Everything posted by 6b6561

  1. And I assume that if you copy the file back to internal from external then it works just fine?
  2. The problem isn't with the files, as full rescans will read them correctly. Problem is most likely that the first scan of the file is done while the file is still being copied and therefore the metadata isn't in place at the time of the scan.
  3. Turning off auto-scan doesn't fix tracks already on the device, it's only good for new tracks copied to the device. My new "workflow" is that I copy any new stuff to the device, once the files are there, then I run an manual rescan, Have you tried to rename the files on your phone? That caused the files to be fully scanned on my phone.
  4. Thanks, this did the trick, this saves me from the full re-scans.
  5. Look's like the same problem is being discussed in
  6. @maxmp thanks for the proposal to disable automatic scan, I believe that will solve my problem for now and I can then just do manual scans after upload has completed. I assume you are using something like inotify for getting notifications to PA about new files in the library and this triggers a scan of the new object? If this is correct, wouldn't it be possible to put in a simple check in the scan to see if the file is open by another process and if so delay the scan? How about changing the "rescan" behavior launched in a folder in such a way that it does a full rescan of the objects in the directory?
  7. It's not a tagging issue or problem with the file. The issue is with files copied to a SD card not being properly picked up at the time of copy, the way to fix it is to either run a full rescan or rename the directory on the SD card. If the same file is copied to the internal storage, then it's properly picked up. My guess is that PA scans the file before it's completely copied to the card, and during this first scan the meta data isn't in place
  8. I have a similar issue where correctly taged MP3 songs ends up as unknown in PA when initially copied to the phone. I have found two ways to resolve the problem: Rename the directory on the phone that holds the problematic tracks, this causes PA to re-scan the tracks. Do a FULL rescan of the library. I would recommend you to try a FULL rescan of your library, go to settings and at the bottom of Library settings page there you have the full rescan.
  9. PA see's the new files, plays them happily but without tags. A simple rename of the file or directory on the device makes PA re-scan the files and then the tags are picked up and I can rename back the directory to the initial name. It doesn't matter how the file is created on the SD-card, always the same result. New files/directories synchronized to device with "FolderSync pro". Files copied from NAS -> phone with "ES File Manager" Files copied from "SD card folder "-> "another SD card folder" with "ES File Manager" or the built in file manager. A normal re-scan will not read the tags, and a full re-scan feels a bit excessive.
  10. @maxmp is there anything that you could do about this problem?
  11. Or just display the generic PA icon for the playlists, I really hate the "random" first track of the list approach. Please either make it selectable or default to a generic icon.
  12. @djdarko My 828 has a white NavBar, just like your 829 screen shot.
  13. Try to login with email address instead of login name or vice versa, that worked for me.
  14. Please confirm that you are doing a "full rescan" and not just a rescan. The full rescan is triggered from the bottom of the library settings page. Kim
  15. I know, it's just exiting the user interface, but there is something in the logic of PA that causes me to back out of it way to often, and then I have to either dig it out from recently used apps or move to the home screen where I have the widget to get into the UI again... I don't know why I keep on doing it, but it's killing me. I must admit that I haven't earlier noted that back is not back, as I'm used to hit the mini player to get back to the main player screen. It's probably better for people like me (musik organized in a Artist/Album hierarchy and basically always using Folder Hierarchy mode) that back acts as up instead of back. Workflow for switching to another album: Tap album cover to get to folder list Back once or twice, depending on if I want to just switch album or artist Enter new folder to be played Tap the first track which starts the track and takes me back to the main screen With this workflow it would be very irritating that back would be back as then I would just be switching between player screen and current category and would have to start using up button in the library. We had a discussion a while ago about having "play" in the pop up context menus, in my workflow it's more intitutive to long press the folder and hit play, instead of entering it and then click on the first item to play it, now I'm used to entering the folder but I do still miss the play button. This made me aware of the fact that people use tools in different ways, depending on how you select what to listen to, size of library, library organization etc. Kim
  16. This is also number one on my wish list, I really hate "being thrown" out of the app by hitting back one time to much! I'm standing on my knees beging for the option to disable the exit... it would really be an early Christmas gift for me to get this implemented... I wonder what it would take to bribe Max to add this? Kim
  17. @maxmp is there any chance that we could bribe you to add a possibility to disable the "exit" button within Poweramp? Default behaviour for back button would be to take you back one screen at the time and once on the start screen another back would close the app, just as it's today. Alternate would be to take you back one screen at the time until the start screen, once there it would just do nothing or ask if you want to exit the app. Please... Kim
  18. @maxmp not sure if the MusixMatch support is new for this version or not, but anyway a BIG thank you for adding this, it's something that I have really been missing since abandoing the 2.0. Kim
  19. I have a MiMax3 running 9 PKQ1.181007 recently upgraded from Android 8 which runs PA without any issues. Have you tried to uninstall and re-install PA after upgrading your phone? There is a per app "background limitations" under battery optimization in phone setting that might down prioritize PA if those settings are active. Kim
  20. Same result, I did just a sdcard to sdcard copy of a couple of tracks into a test folder with music running. Tracks shows up in PA with blank tags, renaming the folder from the filemanager causes the tags to be properly read.
  21. Hi, Device: Xiaomi MiMax3, stock Android 9 Poweramp: Build 828 Workflow: I have all my music stored on a NAS device in a artist/album hierarchy. The entire hierarchy is replicated to the phone using FolderSync pro. Issue: When new tracks are added then: PA doesn't read the tags on tracks copied to the SD card. Files copied to internal memory are properly read. I don't have this issue on my Samsung xcover3. It's not an SD card issue as the files copied from SD card -> internal memory are fine. When did it start?: I know for sure that the workflow has been working and unfortunately I'm not sure when it broke. I have had quite a lot of changes done in my setup recently. Laptop used to copy CD's to MP3 has been replaced, NAS device has been upgraded from ARM based to Intel based Debian and with this the mp3 tools used has been upgraded. Phone OS upgraded from Android 8 to 9... Workaround: Full rescan will pick up tags, but I don't want to rescan 7000 tracks everytime files are added. Rescan in the folder doesn't work. (Proposal rescan launched in a folder should do a full rescan of the folder where it's launched) Tags are picked up by PA if the directory is re-named and named back in the filemeanager after the file has been copied to the device. Replicatable: Yes, it happens every time when new tracks are copied to the SD card. Same thing happens if a directory is copied on the device, if a copy is made of a music dir, then PA will see the files and play them, tags are not picked up unless I do rename the folder. Assumption: PA scans the file before it has been completly copied and therefore the meta data isn't available when the file is scanned? Kim
  22. I had a stab at the (https://www.sendspace.com/file/evvj3n) and the verdict is that there is something broken in the meta data of the file. Conclusion after quite some messing around with the file is that: eyeD3 reads only the title, year, track and disc tags, basically the same info that PA is able to read from the file. id3v2 reads all the tags in the file. mid3v2 reads all tags but the UFID tag. What's interesting is that after adding and removing a TPE3 header to the file with id3v2 all the tags becomes readable in all tools including PA, so there is something garbled in the id3 header which is fixed by modifying a tag in the file. mid3v2 is also able to read the UFID tag after this operation.
×
×
  • Create New...