Open atomGit opened 4 years ago
Thanks for this issue/recipe! @privatezero I'd be interested to hear your thoughts on this?
Do you know what lossless even means?
@richardpl I don't understand what you are implying by asking that. Are you trying to make a disparaging comment? If so, please log off because being rude and condescending is not welcome here.
I genuinely ask user to give reasoning behind using lossy codecs for lossless trimming.
I would expect anyone looking here would be fairly well informed of the implications of using a lossy codec. As to giving the reason, that would depend on the person and their use of a lossy codec; usually it's to save on size to transfer over the interwebz or stream etc. lossless trimming to my knowledge is trimming audio to the point of a zero crossing without losing any content, so the lossiness in the context of this recipe is not really the point. That's like saying here is a guide to cut white bread with a slicer, and then saying "do you even know what white bread means.."
i think quite a few people, myself included, are looking for a clean and lossless method to trim excess silence from only the beginning and end of an audio file, particularly music files, leaving a set amount of silence
while this is possible with ffmpeg and ffprobe, the process involves decoding the audio, reversing it, and decoding again so it's all quite slow
i found this on stack and modified it a bit to make a (sorta) working example, but i see this solution as a very dirty way to accomplish the task, however it is the only thing i was able to hack together after a LOT of searching and reading over the course of several days
note that
-nostdin
seems to be required else funny things seem to happen happen, like chopping off a portion of the audio that contains detectable audiotrivial considering this request, but the script also causes an error when i open the file in Kwave (similar to Audacity):
related: #367