Open sethkush opened 1 year ago
It's a good idea, but patches welcome - I'm trying to get replaygain to work so I can release 1.0. Would be nice to reuse that code to support config files too.
(JSON might be good for this)
I'd suggest a simple text file. I'm working on an example right now. I will post the example text files later. The reason why I think a simple text file is better is because of the familiarity it brings. It's a .txt file, a simple double click and bam, text editor opens and ready to edit. I know that this ripper isn't for the mortals (until there's a GUI). Syntax is not needed, the program just knows how to parse the file and that can be auto-generated with a command.
Sorry for the delay! Two files: the example, followed by the explanations. That made me find some oversight in the features. cyanrip ripping file example.txt cyanrip ripping file explained.txt
The oversights:
If any questions, just let me know here. I'll check here later.
It would be nice if it were easier to edit the metadata prior to ripping.
What if there were an option similar to -I that would export the metadata (or a blank template) to some sort of text file (JSON might be good for this)? Then that file could be opened in $EDITOR, changed as needed, and imported into cyanrip with another command line option.