Thanks man!Bruce B wrote:Spaces are very easy to work around in the script. The characters I would have to test would be things like ' and a couple others. I'll post a modification for spaces when Sylvander reports back.
That patch didn't seem to work, but I'll play with it some more (or just wait for the next version)To add space support one does like this:
from ${fn}.mpg to "${fn}.mpg"
Another thing that is hard to pass on the CLI in this case * , that's why it is in the script and not to be entered on the CLI
Incidentally, I tried my old script, and the new one. Briefly, the output sizes:Primarily I'm interested in seeing if Sylvander will get the file quality he wants, later I'll dress up the script, after I get complaints.
Original .flv = 13MB
My older conversion parameters:
ffmpeg -i "$1" -y -f avi -vtag divx -vcodec mpeg4 -b 800k -g 300 -bf 2 -acodec libmp3lame -ab 128k "$1".avi
results in a 22MB file (and I think the quality is comparable, or perhaps slightly better than below)
And the version "fmpeg -target vcd -y" = 33 MB
Of course, once a script works, it's easy enough to change this around.
Years ago I had written a widget to do that, but support for spaces has greatly improved since then, so I prefer to just leave them (in my code, I actually removed all of the troublesome characters).As for spaces in filenames, some years ago I donated spacereplace
to Puppy. (I didn't write it, I borrowed it) Is it still included in new releases?