by TheBestPessimist » Mon Dec 15, 2025 12:21 pm
Thank you again.
> 3. Add a way to identify files with user set Start or Stop Time, either in a Files to Edit node with changed Start/Stop Time or a method to create an AutoPlaylist where Start or Stop Time are user set.
I would word this differently, and expand the scope: Allow searching for ANY field, whether it can be edited or it is read-only. As long as the field can be viewed in UI, i should be able to search for it. Yes, some searches do not have indexes so they could be slower. Name the 'search column' with a suffix "(slow search)" and that's it. (SQLite is freaking fast for local use. I'm a dev, i know)
In this way, anyone could search for anything they could ever desire.
Not sure how other people use MM, but i use it exclusively for maintaining and playing my music collection. Ever since i started using MM, i have never used anything else.
So at times, i wanted to search for various weird fields or weird metadata.
Thank you again.
> 3. Add a way to identify files with user set Start or Stop Time, either in a Files to Edit node with changed Start/Stop Time or a method to create an AutoPlaylist where Start or Stop Time are user set.
I would word this differently, and expand the scope: Allow searching for ANY field, whether it can be edited or it is read-only. As long as the field can be viewed in UI, i should be able to search for it. Yes, some searches do not have indexes so they could be slower. Name the 'search column' with a suffix "(slow search)" and that's it. (SQLite is freaking fast for local use. I'm a dev, i know)
In this way, anyone could search for anything they could ever desire.
Not sure how other people use MM, but i use it exclusively for maintaining and playing my music collection. Ever since i started using MM, i have never used anything else.
So at times, i wanted to search for various weird fields or weird metadata.