Jump to content

Crericper

Approved Members
  • Content Count

    64
  • Joined

  • Last visited

 Content Type 

Profiles

Forums

Gallery

Downloads

Knowledge Base

База знаний

知识库

Posts posted by Crericper


  1. 3 hours ago, andrewilley said:

    I was suggesting the idea of adding more criteria beyond simple text strings into the existing category search feature

    Yes, that is what I meant. I didn't fully understand what "List Options" exactly do. However, it looks very similar to the idea of filtering and matching criterias. 

    In fact, the concept design image is made based on the screenshot of "List Options". 

    1595502110325.jpg

    Hope this will bring some inspiration. 


  2. 19 minutes ago, andrewilley said:

    make more sense to put any extra options into the already-existing Search feature at the top of each list

    That's right. I think the current "List Option" is quite confusing and unusable. I think changing it to "Filter" will be more intuitive for most people. 

    And I also think it is more powerful. 


  3. I will be amazed if I see this to be implemented. :)

    Concept design for "Advanced Search Filter" 

    concept-search.fw(UpRGB)(scale)(width 2160).jpg

    Note: 

    1. New filter button beside the start playing button. 

    2. Rules that will filter the current search result based on them. 

    3. This design should be implemented in all folder-like structures (e.g. Folders, Playlists) for the most consistent searching experience.  

     


  4. @andrewilley 

    There are also cases where I'd like to filter tracks inside a folder or a playlist. That said, the filter tool should also exist inside Playlists or any folder-like structures. 

    The tool should only show any filtered result instead of modifying anything. Hence, we can use features such as "Select All" to easily select them. 

    BTW, the search tool should also be added inside any folder-like structures for further filtering.

    (All talks are based on the concept of having hundreds of items needed to be selected.)


  5. 2 hours ago, andrewilley said:

    Each library category in Poweramp has its own independently set sorting method. which control how the contents should be viewed and played  For example, in Folders mode you could have the songs sorted by Rating (in either forward or reverse order) by tapping the three-dots menu icon and selecting List Options. You can't filter to see ONLY see one particular rating though, it would just change which ones you see/hear first.

    If you want to apply this logic to your entire music collection, use the All Songs category and do the same thing there.

    Playlists are slightly different in that they are a created list of song titles that already have their own pre-defined playback order. You can re-sort that order for a specific playlist though, by using the same three-dots menu inside the playlist and choosing Re-sort.

    Andre

    Adding filter will make life easier on arranging tracks. 

    e.g. Selecting and adding all 5 starred tracks from a folder with 2000 of them to a dedicated playlist. 

    It doesn't have to modify the list. It's all about filtering and selecting, which can make my life easier on managing, for example, rated songs and unheard songs. 


  6. On 7/21/2020 at 3:40 AM, andrewilley said:

    Do you actually mean inside Playlists here? As in the Library category called Playlists where you see previously created ordered lists of songs?

    Andre

    No. I meant a filter inside any Playlist or Folder. 


  7. 28 minutes ago, andrewilley said:

    that's more the job of an EQ.

    Oh, I thought compressor is a feature is to shift frequency from e.g. 20Hz to 60Hz, which, you know, is somehow similar to the HDR filter in photography, to compress audio dynamic range. And I'm also not sure if there is anything existing like that. 😂


  8. @andrewilley However, it's different on my situation. As I said before, 

    On 2/28/2020 at 2:37 AM, Crericper said:

    In my case it's the JBL filp 3 speaker that does not respond to frequency lower than 60Hz, which some songs sound strange without sub 60Hz frequency. 

    Compressor is greatly helpful on fixing that. And also, 

    On 2/28/2020 at 2:37 AM, Crericper said:

    If possible, please also add a button to disable pitch normalization during tempo adjustment. That will be extremely useful for some Nightcore songs! :)

     


  9. In my case it's the JBL filp 3 speaker that does not respond to frequency lower than 60Hz, which some songs sound strange with that issue. 

    I need this feature as well as the people in this thread. It should be much easier to code than the reverb, right? 

    p.s. If possible, please also add a button to disable pitch normalization during tempo adjustment. That is extremely useful for Nightcore songs! :)


  10. @RBEmerson, it was a thread that checks play service, but went into infinity loop, and I think, it is most likely caused by play service not responding. 

    Quotes here: 

    On 11/7/2019 at 5:05 PM, Crericper said:

    After some extra digging, found this: 

    Seems like it is waiting for a thread to stop: 

    
    "awakenReason":1,"stack":["java.lang.Thread.join(Thread.java:1268)","com.maxmpz.audioplayer.player.PlayerService.onDestroy","android.app.ActivityThread.handleStopService"...

    As: 

    On 11/7/2019 at 9:24 PM, dinfinity said:

    Nice work! com.maxmpz.audioplayer.player.PlayerService.onDestroy would be the significant bit here. The application generating the log seems to be a MIUI monitor app, but it still gives valuable information about PA.

    Looking at "beginTime":3210750," and endTime":3214770",  it seems that the MIUI monitor gives off a warning because the onDestroy method is taking more than 4 seconds. This is probably because something in that onDestroy method is stuck in an infinite loop as hypothesized before.

     

    On 11/8/2019 at 8:11 AM, dinfinity said:

    @maxmp: Sent you the bug report. I suspect this is the culprit:

    
    "player service thread" prio=5 tid=9 Suspended
      | group="main" sCount=1 dsCount=0 obj=0x12c07340 self=0x7f78b8fc00
      | sysTid=21390 nice=0 cgrp=bg_non_interactive sched=0/0 handle=0x7f7618d3a0
      | state=S schedstat=( 0 0 0 ) utm=3765 stm=66 core=5 HZ=100
      | stack=0x7f7608b000-0x7f7608d000 stackSize=1036KB
      | held mutexes=
      at ׅ.tg$D.D(":702)
      at ׅ.tg$D.ׅ(":696)
      at ׅ.tg$L.ׅ(":759)
      at ׅ.tg.ׅ(":645)
      at ׅ.px.release(":5034)
      at com.maxmpz.audioplayer.player.PlayerService.llll(":3093)
      - locked <0x014f9035> (a java.lang.Object)
      at com.maxmpz.audioplayer.player.PlayerService$v0.ׅ(":1145)
      at ׅ.pz.handleMessage(":29)
      at android.os.Handler.dispatchMessage(Handler.java:102)
      at android.os.Looper.loop(Looper.java:148)
      at android.os.HandlerThread.run(HandlerThread.java:61)

    (utm is high and this seems to be the only thread that is not waiting/native waiting)

     


  11. 1. Switch to PA, with a playlist loaded
    2. Go to next song using the main interface, not the notification interface (note: actually playing a song is not required)
    3. Switch to OS monitor or SystemPanel (or any other app)
    4. Notice that Poweramp CPU usage increases and stays high, specifically that it maxes out a single CPU core

    @maxmp, have you got the bug successfully reproduced on your end? Or is that the case where the bug only applies to only me and @dinfinity


  12. Ah, forgot to post my device & info. In case if you need @maxmp

    Model: Xiaomi MI 6
    Android: 8.0.0
    ROM: MIUI 10 9.3.21 Beta
    Security patch level: 2019-04-05
    Kernel: 4.4.78-perf-ge57b3e5
    
    CPU: Snapdragon 835 8-Core @ 2.45GHz
    RAM: 6.00GB
    Avaliable Storage: 9.37GB
    Poweramp version: v3-build-852-arm64-play
    SHA-1: 3dfe11e642d0cdc8cb2941198f732ca2007e93e3
    Unlocker version: 3-build-301
    SHA-1: e9e324843197257366074a3027eda6ed3adf5f25

    @dinfinity, I believe that's the case as well! That instance have also appeared in the first log I've posted. (Notice there's the orange chunk below.)

    Here quotes: 

    On 11/1/2019 at 10:12 PM, Crericper said:

    I've reproduced the bug twice and logged it with LogcatX. Inside this screenshot, the selected 3 lines seems suspicious

    image.thumb.png.58dbf75bb58bf21c24d376caedd975a7.png

    Log_2019-11-01_22-09-24.zip 33.89 kB · 1 download

     


  13. After some extra digging, found this: 

    Quote

    W(25788) {"eventType":3,"eventTypeName":"ConditionWait","seq":36,"pid":25788,"uid":10382,"processName":"com.maxmpz.audioplayer","packageName":"com.maxmpz.audioplayer","threadId":25788,"threadName":"main","beginTime":3210750,"endTime":3214770,"policy":0,"priority":-10,"schedGroup":0,"runningTime":0,"runnableTime":0,"sleepingTime":0,"endRealTime":0,"eventFlags":1,"monitorId":502570013224,"awakenReason":1,"stack":["java.lang.Thread.join(Thread.java:1268)","com.maxmpz.audioplayer.player.PlayerService.onDestroy","android.app.ActivityThread.handleStopService","-.-wrap26","android.app.ActivityThread$H.handleMessage","android.os.Handler.dispatchMessage","android.os.Looper.loop","android.app.ActivityThread.main","java.lang.reflect.Method.invoke","com.android.internal.os.Zygote$MethodAndArgsCaller.run","com.android.internal.os.ZygoteInit.main"]}  (MIUI-BLOCK-MONITOR)

    Seems like it is waiting for a thread to stop: 

    "awakenReason":1,"stack":["java.lang.Thread.join(Thread.java:1268)","com.maxmpz.audioplayer.player.PlayerService.onDestroy","android.app.ActivityThread.handleStopService"...

    As: 

    Quote

    java.lang.Thread.join()

    Joining Threads in Java. java.lang.Thread class provides the join() method which allows one thread to wait until another thread completes its execution. If t is a Thread object whose thread is currently executing, then t.join() will make sure that t is terminated before the next instruction is executed by the program.


  14. @maxmp, sorry that the developer logging wasn't functional on my phone. But you may still find this useful. Information below will be based on the log made by rs.pedjaapps.alogcatroot. 

    I've reproduced the issue 3 times for logging, each time I ensure CPU goes up before continuing. 

    1. Start Poweramp
    2. Swipe for next song
    3. Switch to SystemPanel and wait
    4. Switch back to Poweramp
    5. Repeat step 2-4 two more times

    Then I've filtered the log with keyword "maxmp", which should only return Poweramp related instances. 

    Here's a screenshot of the filtered & formatted log. I circled everything related to the suspecious "dsp_thread". I have also included a text-based log. 

    Screenshot_2019-11-07-14-23-23-795_rs.pedjaapps.alogcatroot.highlight_gzip.thumb.png.1bbef64a3da2bdca85fd8a0e93d792a0.png

    Hope you find this useful, thanks! 

    alogcat.2019-11-07-14-24-07+1100.txt

×
×
  • Create New...