demlo issueshttps://gitlab.com/ambrevar/demlo/-/issues2018-08-17T00:26:47Zhttps://gitlab.com/ambrevar/demlo/-/issues/10Modularize path.lua into basename.lua and directory.lua2018-08-17T00:26:47ZAmbrevarModularize path.lua into basename.lua and directory.lua*Created by: Ambrevar*
As mentioned [here](https://github.com/fictionic/demloconf/issues/1), it would give more flexibility to the user.
path.lua would remain for backward compatibility and simply enable the other two.*Created by: Ambrevar*
As mentioned [here](https://github.com/fictionic/demloconf/issues/1), it would give more flexibility to the user.
path.lua would remain for backward compatibility and simply enable the other two.https://gitlab.com/ambrevar/demlo/-/issues/9Album-awareness and input ordering2018-08-17T00:26:47ZAmbrevarAlbum-awareness and input ordering*Created by: Ambrevar*
In #4 we mentioned the issue of auto-numbering tracks according to their position in the queue.
There are several ways to proceed. Some do not cope well with parallelization.
Using the queue order in the sc...*Created by: Ambrevar*
In #4 we mentioned the issue of auto-numbering tracks according to their position in the queue.
There are several ways to proceed. Some do not cope well with parallelization.
Using the queue order in the script is not very flexible though: what if the sorting (which depends on the locale) does not suit the user?
Probably better: add a directory listing function. That should not harm the sandboxed nature of Demlo.
By matching the track path with the directory listing, we could auto-number the tracks.
https://gitlab.com/ambrevar/demlo/-/issues/8Export an 'input()' and 'print()' functions to the Lua scripts2018-08-17T00:26:47ZAmbrevarExport an 'input()' and 'print()' functions to the Lua scripts*Created by: Ambrevar*
Mentioned in #4.
Sometimes it could be handy to make Demlo's process more interactive.
A script could ask the user to enter a value with
`func input(prompt string) string`.
Example: when a disc number is...*Created by: Ambrevar*
Mentioned in #4.
Sometimes it could be handy to make Demlo's process more interactive.
A script could ask the user to enter a value with
`func input(prompt string) string`.
Example: when a disc number is found, ask the user if we should ignore it for the current album or not.
Some input functions could be recurring (booleans, number queries). Add `input_bool` and `input_number`?https://gitlab.com/ambrevar/demlo/-/issues/4Emacs mode (GUI)2018-08-17T00:26:47ZAmbrevarEmacs mode (GUI)*Created by: Ambrevar*
Like many semi-interactive programs, Demlo's user-experience feels limited on the commandline.
In particular, it can be frustrating to re-run Demlo over and over with different pre-/post-/scripts until we get the...*Created by: Ambrevar*
Like many semi-interactive programs, Demlo's user-experience feels limited on the commandline.
In particular, it can be frustrating to re-run Demlo over and over with different pre-/post-/scripts until we get the result right.
I've been thinking of writing an Emacs mode to provide for a better experience.
Why Emacs? Mostly because:
- of its textual nature;
- of its keyboard-based, power-user bindings;
- I use it, I know it, I can program it :)
Running Demlo from Emacs would produce a special buffer "à-la-Magit" where each audio file would contain the diff as it is currently displayed in shells.
The entry would be collapsable.
There would be two collapsable subsections:
- A subsection containing the list of scripts which could be turned on and off with a simple binding.
- A subsection containing the pre/post scripts which would be writable (in Lua mode, obviously).
A `C-c C-c` key press on a track section would update the "diff" by running Demlo with the changed made to the scripts in the subsections.
A `C-u C-c C-c` would do the same to all tracks.
Last but not least, the diff "after" fields would be writable. This would effectively allow for a very convenient way of hand-editing tags and other properties.
Finally, `C-x C-s` would process the track at point while `C-x s` would process all tracks.
https://gitlab.com/ambrevar/demlo/-/issues/2Support the full TagLib API2018-08-17T00:26:47ZAmbrevarSupport the full TagLib API*Created by: Ambrevar*
Adding support for the full TagLib API would improve many aspects:
- Faster processing when only re-tagging.
- Less convoluted around the TagLib and FFmpeg calls.
See https://github.com/taglib/taglib/issues...*Created by: Ambrevar*
Adding support for the full TagLib API would improve many aspects:
- Faster processing when only re-tagging.
- Less convoluted around the TagLib and FFmpeg calls.
See https://github.com/taglib/taglib/issues/455.