amiaopensource / amiaopensource/ffmprovisr

avoid doubling file extensions in example for recursively batch processing with `find`?

Abierto
#465 2 comentarios 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
HTML
Estrellas
581
Forks
74
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

In the "Batch Processing (Mac/Linux)" [section](https://amiaopensource.github.io/ffmprovisr/index.html#batch_processing_bash), there's an example variation provided for recursively processing files contained in sub-directories using `find`, rather than the standard `for` loop for processing within the same directory - this was super helpful to me for a completely different/non-AV batch processing task, but as @kieranjol [noted](https://github.com/amiaopensource/ffmprovisr/pull/220#issue-250261372) when originally suggesting the current one-liner, the limitation with sending `find` output directly into the ffmpeg command with `-exec` is that you wind up doubling up on file extensions in the output file name, e.g. `filename.mxf.mov`

I'm a bit torn here - on the one hand, the current version is definitely simpler/quicker to understand, on the other hand, it's a bit confusing if you're not expecting that output, and trying to batch rename from Bash after-the-fact is a can of regex worms.

It would require a bit more text to explain the loop, but what about:
`find input_directory -iname "*.mxf" -print0 | while read -d $'\0' file; do ffmpeg -i "$file" -map 0 -c copy "${file%.mxf}.mov"; done`?

(see e.g. https://askubuntu.com/a/648990)

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.