New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhancement: Automatically sort tracks in track manager #128
Comments
This is great!!! Can you also sort by file name? That would be super helpful as well. One other suggestion I would add is to make the column headings static when you scroll down the list so that they are always visible. I find I forget which column is which almost as soon as that line goes off the screen. |
…rapped in parenthesis, Change: Parse out CD Num from filename, Change: Show First Last author everywhere when Last, First is used in folder name, Fix: Re-Scan updates parsed track nums
I added the sort by filename. I agree with the static column header, this will come in a future release. Btw @jarrodCoombes since we were chatting in the unraid forum it will be easier to respond here. I pushed a bunch of fixes for what we talked about included in release v1.5.0. Author name fix (except in the details input field for now), CD number is parsed from the filename, publish year can be wrapped in parenthesis, and the Re-Scan button will update the track number metadata. Will close this one out, if you have issues with any of the above we can start a new issue or discussion. |
Right now the track manager (where you can rearrange the tracks of an audiobook) shows "Track Parsed from Filename" and "Track From Metadata", but you still have to sort the tracks by hand if you want to use one of these arrangements.
Automatically arranging the list by clicking on the preferred table header would save a lot of dragging and dropping (kind of related to #127, because this is where a lot of rearranging is required. Although auto sorting isn't always possible in that case).
Really love this project, hope it doesn't seem rude that I'm opening all these "issues"! :)
The text was updated successfully, but these errors were encountered: