Custom Naming and Encoding Flexibility Proposal #37
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey Lessica (彩華 from Cytus?), I freaking love this project. It's the best audio recorder I've seen so far, and I've been thinking about enabling power users to tinker with the recording settings.
I'm talking about more flexible options for naming recordings and tweaking encoding parameters directly using ffmpeg.
For the naming feature, I think it would be incredibly useful to incorporate regex or a similar pattern-matching system, so users could define their own naming conventions based on variables (date, time, caller ID, location, etc.). It would make organizing, categorizing, archiving, and locating recordings much easier down the line.
For the encoding part, it would be killer to have the ability to do custom encoder parameters. Here's an example of how I usually set up my voice recordings (this is for single channel only):
./ffmpeg (audio device) -ar 16000 -acodec libopus -ac 1 -frame_duration 60 -vbr on -b:a 24k -application voip -compression_level 6 "(target path)\audio_record_${currentDate}_${currentTime}_${Caller}.ogg"
, and these settings are VERY efficient while retaining great quality and are low on processing demands.I'm totally willing to contribute and implement it in TrollRecorder, though I gotta admit, I'm a bit unfamiliar with the codebase. If you could help me figure this out with some boilerplates, similar to a merge I completed on Uptime Kuma.
What do you think?