canon raw

[Mickey Adair]

How can I get rid of the .HTM files that accompany each .CRW file, all at once?

 

[Bart_van_der_Wolf]

How can I get rid of the .HTM files that accompany each .CRW file, all at once?

Hi Mickey,

The Canon software doesn't add .HTM files, nor does e.g. Photoshop, so it might be a by-product of your image-editor, or Raw converter.

Bart

 

[John Sheehy]

How can I get rid of the .HTM files that accompany each .CRW file, all at once?

Instead of deleting them you might consider moving them to another folder, as they are very fast to browse through.

To perform any action on all of them, go to the top folder (if you use Windows) and hit the F3 key, and Search will come up. Then, type *.thm (not .htm, as you mis-typed), and search, and it will give you a list of all of them. Then, press CTR-A to select them all, and then drag them to another folder, or right-click one and select delete. If you're not sure if you're doing this right, scroll through the list first to make sure you only have .thm files. If you leave them where they are, the Canon converters will use them for thumbnails instead of creating them, IIRC.

 

[Mickey Adair]

re: .THM

I'm a Mac user and haven't been able to figure out how to isolate these .THM files for deletion. I don't want to save or use them.
Thanks for your reply.

 

[Dawid Loubser]

Hi Mickey,

I have no idea what your comfort level is around your computer, but if you know how to open and type commands in the terminal (Terminal.app) you could get rid of those .thm files with a single command:

1. Change to the directory below which your pictures are stored, e.g. cd ~/Pictures/
2. Zap all .thm files with rm `find . -name *.thm` (note, those are not normal single quotes, they are reversed, next to your 'z' key)

 

[Bart_van_der_Wolf]

I'm a Mac user and haven't been able to figure out how to isolate these .THM files for deletion. I don't want to save or use them.
Thanks for your reply.

One small word of caution. If I remember correctly, there are older Canon Raw (.CRW) files that were accompanied by .THM files where the .THMs contained a thumbnail, but also EXIF data. By deleting such .THMs will therefore also make one lose the EXIF shooting details.

If your version of .THM files is different, then you can delete them without losing potentially useful info. Modern file viewers and Raw converters can make new thumbnails quite fast.

Bart

 

[Sean DeMerchant]

Zap all .thm files with rm `find . -name *.thm` (note, those are not normal single quotes, they are reversed, next to your 'z' key)

You will find left single quotes (backticks) below the Esc with the tilde (~) key on most US keyboards. Keyboards tend to vary with native language, so keys are not always in the same place.

Also, does Finder not support searching internally? Searching for *.thm and deleting them might work. I would personally just use bash shell for it (Terminal as already noted).

some thoughts,

Sean

 

[Emil Martinec]

Hi Mickey,

I have no idea what your comfort level is around your computer, but if you know how to open and type commands in the terminal (Terminal.app) you could get rid of those .thm files with a single command:

1. Change to the directory below which your pictures are stored, e.g. cd ~/Pictures/
2. Zap all .thm files with rm `find . -name *.thm` (note, those are not normal single quotes, they are reversed, next to your 'z' key)

What does this do that rm *.thm will not accomplish in step 2?

 

[Cem_Usakligil]

What does this do that rm *.thm will not accomplish in step 2?

Hi Emil,

If you use "rm *.thm", you will only remove the thm files in directory /pictures but will not do anything for the subdirectories.

rm `find . -name *thm` also searches and removes the thm files in the subdirectories of /pictures.
That is the difference.

HTH

Cheers,

 

[Emil Martinec]

Hi Emil,

If you use "rm *.thm", you will only remove the thm files in directory /pictures but will not do anything for the subdirectories.

rm `find . -name *thm` also searches and removes the thm files in the subdirectories of /pictures.
That is the difference.

HTH

Cheers,

If I wanted to remove such files in subdirectories as well as the current directory, I would have used "rm -R *.thm". Is the syntax "... find . -name ..." different, or just another route to the same goal?

 

[Cem_Usakligil]

If I wanted to remove such files in subdirectories as well as the current directory, I would have used "rm -R *.thm". Is the syntax "... find . -name ..." different, or just another route to the same goal?

Yes, I think so.

 

[Sean DeMerchant]

Fine Details and Pedagogy

If I wanted to remove such files in subdirectories as well as the current directory, I would have used "rm -R *.thm". Is the syntax "... find . -name ..." different, or just another route to the same goal?

Emil,

IIRC, your method will also remove directories. Hence if a directory name ended in .thm it would remove that directory and all its subdirectories. The find command is more discriminatory and limits the command.

So they are not isomorphic routes to the same end. rm -R is a much more potent command and one I would shy away from pedagogically.

Using find by itself will also display the list of files to be manipulated. Using rm -R one must replace rm by ls to view the affected set of files and directories. Hence, I think the find command presents the information manipulated better for a neophyte and further it introduces the shell scripting concept of piping output effortlessly to the user helping them understand the concept of piping more easily in the future.

some thoughts,

Sean

 

[Emil Martinec]

OK, thanks!