(03-25-2021, 02:56 PM)Maus Wrote: I'm sorry to read you lost your images, but you are absolutely right, reading only the introductory comment lines, especially the last two of them, would have helped:
# The post-processing script is responsible for cleaning up
# temporary directory for the burst.
<snip>
Thanks, Maus! Yeah, I'm not much of a script meister so sometimes I take heuristic shortcuts to study behavior rather than studying the code. I've been in computing since before "microcomputers" even existed. FORTRAN, K&R C, and assembler is mostly how I learned a living many years ago.
But at least I finally settled into reviewing the code and I found the bug. I guess it's best to stick to POSIX syntax when using sh and perhaps a new intolerance to legacy code just bit postprocess.sh!
I changed line 69 in postprocess.sh from
Code:
if [ "$CONVERT" == "convert" ]; then
to
Code:
if [ "$CONVERT" = "convert" ]; then
From https://stackoverflow.com/questions/2044...erators-eq
== is a bash-ism, by the way. It's better to use the POSIX =. In bash the two are equivalent, and in plain sh = is the only one guaranteed to work.
Now I need to discover where to file a bug report.