[02:07] <brownie17> jrib, i'm here
[02:07] <jrib> hi
[02:07] <brownie17> jhi
[02:07] <brownie17> sorry for making you wait. needed bathroom
[02:07] <jrib> ok, first thing to understand is the basic syntax of convert
[02:07] <brownie17> k
[02:07] <darkchr0n0s> what are we learning today ?
[02:08] <brownie17> darkchr0n0s, batch image conversion with imagemagick
[02:08] <jrib> so, according to http://www.imagemagick.org/script/convert.php, it's  convert IN_FILE OUT_FILE
[02:08] <jrib> convert doesn't change the image you give it, it saves the change as OUT_FILE and leaves IN_FILE alone
[02:08] <brownie17> jrib, yes. i aslo tried the 'mogrify' option instead of convert, which i think just modifies the original files
[02:08] <jrib> right
[02:08] <jrib> which one do you want to use?
[02:08] <jrib> mogrify will leave you with no backups
[02:08] <brownie17> jrib, i'd prefer mogrify
[02:09] <brownie17> jrib, i already made backups
[02:09] <jrib> k
[02:09] <jrib> so my command should work if you change "convert" to "mogrify"
[02:09] <jrib> find /some/directory -iname '*.jpg' -exec convert -interlace none '{}' \;
[02:09] <jrib> find /some/directory -iname '*.jpg' -exec mogrify -interlace none '{}' \;
[02:10] <brownie17> okay ahh, i leave the  '{}' \;    exactly as it is?
[02:10] <jrib> you can omit "/some/directory" if you are in the directory already that you want to start it
[02:10] <jrib> s/it/in
[02:10] <jrib> brownie17: yes, '{}' gets changed to the filename that find finds, and "\;" is just an escaped ";" to specify the end of the command that you want find to execute
[02:11] <brownie17> jrib, k it's working
[02:12] <jrib> great
[02:12] <brownie17> wait
[02:12] <brownie17> sorry i mean
[02:12] <brownie17> it is currently doing the task, i don't know if it's functioning correctly
[02:13] <brownie17> jrib, there's around 80 meg of 50-100 kb images each. so i expect it to take a considerable amount of time
[02:13] <darkchr0n0s> brownie17 :  try on single image first?
[02:14] <brownie17> darkchr0n0s, i made backups, so that's no worry. but i'd rather not CTRL+C out of this in case it ruins some of the images.
[02:14] <brownie17> darkchr0n0s, in other words, too late! ;D
[02:15] <brownie17> one or two of the jpgs have been reported as corrupt, but that's to be expected i think. i haven't verified all of these are already working fine
[02:17] <brownie17> jrib, okay it's finished the process now, checking the files they all appear intact, how can i quickly check a single file to see if it is baseline or progressive?
[02:17] <jrib> no idea
[02:17] <brownie17> jrib, k thanks so much for your help