64 bit HDRi RAW file renaming

[owl]

Problem: With HDRi RAW files, HDR sets the output filename from the NAME found in the metadata (and ignores the actual filename). If there is no metadata, then HDR has no problem reusing the input filename (since there is nothing else to use, of course).

My planned process flow is
- bulk scan 20k slides in SF 8.8 on computer #1, sending the files to a network drive
- correct the filenames using computer #2. Use the operating system, Windows 7 to change the filenames to agree with the label on the front of each slide
- at this point, all the filenames agree with the slide labels, which are different than the "arbitrary" names assigned in SF 8.
- bulk process the HDRi RAW files using computer #2 with HDR so that the output files are created with the slide labels (new filenames) and NOT the ones originally created in SF 8.8
- for the rare case where I am not happy with the bulk settings, redo the image by hand in HDR
- where the slide was mis-scanned (auto frame did not work properly), go all the way back to SF8.8 and rescan, then re-HDR.

Since HDR will not use the new filenames I have provided, I could of course, manually update the names in the HDR job manager and then run a pass through HDR just to get the right filenames, but that seems like a big waste of time AND would result in having to update all the HUGE raw files, and since these are ARCHIVES, I really do not want to be editting them in any way. I could also drop the files into job manager, save the job, and have a small script I write, hunt down the XML file in SilverFast 8 HDR\Pref\Jobs and patch the correct name for each of the files, but that seems like a complicated way to go as well (and of course, would only help me and not all the other SF users).

I have spoken with Darren in the USA office and he has duplicated the "problem".

Problem Setup
- scan an image in SF 8.8 for output as 64 bit HDRi RAW with the name "sf8source" and as a TIF (resolution and size are unimportant)
- rename the file in the operating system (Windows 7) from "sf8source.tif" to "sf8target.tif"
- open HDR and drop the file "sf8target.tif" in
- the hope is that the "name" will be prefilled with "sf8target", but that is not the case, it is stuck on "sf8source"

To prove my point, you can verify this by hacking the 2 metadata NAME fields in the TIF file (one for the image and one for the infrared), to something else (however, do NOT insert of delete characters, just replace them). For our example, open "sf8target.tif" using HxD. Find both occurences of "sf8source" and replace it with "sf8target". Save the file. Now drop this file into HDR and presto, the name field now has "sf8target". Nice.

Request: Where is the option to tell HDR to use the input filename as the output filename. From a customer perspective, all that is needed is a single checkbox in preferences somewhere, that says, always use the filename and ignore the name in metadata.

I am using SilverFast 8.8, Version 8.8.0r1, Build number 16004
Reflectra MS Scanner and HDR Studio, respectively.

I have read similar posts by others, but the responses have always seemed to imply a fundamental lack of problem understanding.

I hope this post helps clarify the problem so we all benefit from the solution.

[LSI_Ketelhohn]

Dear customer,

It does not use the file name because the Name in the Image Dimensions is not the input but the output name.
So this will have to differ from the input name and has to be stored in the metadata.
I am not entirely sure but maybe the ExifTool can help you renaming the files.
But I have not tested this.
But we will also look into this and check if we can find a solution.

Kind regards,
Arne Ketelhohn.

[PhotoMike]

I'm trying to create RAW files from negative scans with SE 8.8. The only output format I find is TIF. The goal is to batch process and then import the RAW files into Lightroom for editing and management. I'm new to the software and not finding much documentation.

[owl]

Hi,

So I have written a small program that will direct HDR to modify the name in the metadata and rename the filename. It takes as input a CSV file with 2 main columns, the "from name" (which is used by both the filename and the metadata) and the "to name" (the name I wish the file to be called to the operating system) and the metadata to refer. I drop the image files into HDR Job Manager, the program reads the CSV file and proceeds to navigate down the Job Manager list, image by image, replacing the old name with the new one. As the next image is selected, HDR updates the metadata for the prior image. When done, all the images in the Job Manager are removed (new job button does this) and then the program renames the filenames as seen by the operating system. Presto, both the filename and the metadata use the new name.

Now the questions.

1. With multiple images in Job Manager, every time I select an image, HDR updates the prior image's metadata. HDR seems to write every little change, including open windows, crop settings, all settings to the metadata, sometimes nothing at all except the current date and time. Is this observation basically correct? If so, when I save the Job, is all the same information stored in the XML that the job manager writes for the entire job, when compared with what was stored in the metadata of each image? If different, what are the basic differences?

2. Once my program has HDR modify the metadata name and the program renames the filenames, I plan to return the images to a read only state. The reason for the read only state is I really do not want anyone touching the archive images. Furthermore, all the images will be backed up in multiple locations, with CRC signature verification. With HDR messing with the files, the CRCs will never match. I have tried dropping read only files into HDR, and all seems ok. HDR must try to update the metadata but finds it can't, doesn't complain, and moves on. What problems may I encounter in the future as a result of making the images read only?

Any thoughts and advice would be greatly appreciated.

[LSI_Ketelhohn]

Dear customer,

There is no .raw output. scanners directly deliver RGB data. That is why the raw (as in unchanged) data is stored in tiff files.

____________________

Yes the JobManager updates the file as soon as there is a change.

Sorry I can not really say what kind effects that will have. I have not tested this.

Kind regards,
Arne Ketelhohn.

[owl]

Hi,

From above. another attempt, reworded

Metadata is store in at least 2 places in support of SF and HDR
- the XML stored by the HDR job manager when the user saves the entire job
- the metadata stored in each individual image (HDRi RAW)

Is the same information stored in each? Is more information stored in the job manager's XML? Is some information the same and some unique? If you do not know, where can I find more information on this?

Thanks.

[LSI_Ketelhohn]

The JobManager saves settings presets.
The HDRi RAW file stores settings in its metadata.
This can but does not has to be identical information, depending on the settings used.

Kind regards,
Arne Ketelhohn.

[bosveldboer]

Hi,

I have found a better solution to the problem of embedded 64bit HDRi RAW file names.

SF stores the embedded file name in a custom Silverfast tag structure in the RAW file. However, if you disable the option for Silvferfast to store the filter and frame settings in the RAW file, there is no embedded file name. When you rename the RAW file using the operating system, HDR will use the operating system file name and not any embedded filename, because there is no embedded filename.

I am not sure what is the use of saving the filter settings etc in the RAW file, as a RAW file only contains the RAW scan data and all filtering and processing are done afterwards in HDR Studio.

You can disable the option for SF to save the RAW data in the file by clearing the tick for HDR RAW in Preferences / General. (See photo)

Am I missing something?