IR Workflow does not work with large Scans from Silverfast 9

[signynt]

IR Workflow does not work with large Scans from Silverfast 9

[molanfogarty]

Hi again
I just thought to try your Example.TIFF and it worked, so I assume the problem is with my scans. Any suggestions?
Michael

[Signynt]

Hi @molanfogarty, if it works with the example file, there's probably an issue with the scan.
Could you please provide me with all the details of your scanning process (software, scan settings, etc.)?
An attached example would also be great, just upload it to Google drive, and attach a link!

[molanfogarty]

Thanks for responding so quickly, and apologies for my lack of knowledge experience. Sanner: Plusteck OpiticFilm 8200*i* Software: Silverfast Version 9.1.2 *Settings:* I use the Workflow Pilot: Source: Negative Task: Archive *ME* = on *Frames & Resolution:* Scan resolution = 7200ppi Film Kodak, VPS, Iso 160 CCR = on *Export Options:* File Format = HDRi RAW *Is that all that's relevant?* Links to files: 1. Scan: https://drive.google.com/file/d/1WtVReNKQSnBaiV9n46s70lbJRvF_oykM/view?usp=sharing 2. (IR) (Silverfast)-inverted: https://drive.google.com/file/d/19HZZHpZ3UTBOFTol45Kqxm1rRcH7iIwS/view?usp=sharing 3. The Shortcut version: https://drive.google.com/file/d/1JpYZS1s_N6k6fhtJ1QRo1Fh7tCad-AwT/view?usp=sharing Apologies for the delay, I'm in Australia and our internet decided to go slow this evening. Appreciate your assistance. Michael

…

On Tue, 11 Jan 2022 at 16:00, Vincenzo Mitchell Barroso < ***@***.***> wrote: Hi @molanfogarty <https://github.com/molanfogarty>, if it works with the example file, there's probably an issue with the scan. Could you please provide me with all the details of your scanning process (software, scan settings, etc.)? An attached example would also be great, just upload it to Google drive, and attach a link! — Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK5B6RCNOL3YVPIIAVOAC3DUVO2PLANCNFSM5LVKELGQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Visit our blog, Our-Wanderlust <http://our-wanderlust.com/>, for travel stories from places that you'd rather be. http://our-wanderlust.com/ Anna & Michael *The world reveals itself to those who travel on foot*. Werner Herzog

[Signynt]

No worries @molanfogarty, we'll figure out what the issue is.
I don't have access to the files you shared, I've requested access, and you'll need to accept it before I can take a look at them.

I see you're using Workflow Pilot to make your scan. I don't currently have access to my scanner, and have never used it before, so I haven't been able to take a look at how it exactly differs from the settings needed by my Workflow.
Can you try scanning without the Workflow Pilot? Try following these instructions I made on scanning, these are the correct settings my Workflow is expecting as an input. (I'm using Silverfast 8 in the video, but it should be identical to Silverfast 9 for this use case)

Cheers,
Signynt

[molanfogarty]

Hi It's morning now here and hopefully, I've approved the sharing requests. Michael

…

On Wed, Jan 12, 2022, 4:17 AM Vincenzo Mitchell Barroso < ***@***.***> wrote: No worries @molanfogarty <https://github.com/molanfogarty>, we'll figure out what the issue is. I don't have access to the files you shared, I've requested access, and you'll need to accept it before I can take a look at them. I see you're using Workflow Pilot to make your scan. I don't have access to that feature, so I haven't been able to take a look at how it exactly differs from the settings needed by my Workflow. Can you try scanning without the Workflow Pilot? Try following these instructions <https://youtu.be/yS_7Wxnh4q0?t=131> I made on scanning, these are the correct settings my Workflow is expecting as an input. (I'm using Silverfast 8 in the video, but it should be identical to Silverfast 9 for this use case) Cheers, Signynt — Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK5B6RAUPVOYCYNLEX2F6JLUVRQ2FANCNFSM5LVKELGQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[Signynt]

Alright, I've taken a look at the files, and the issue seems to be that the scan contains 3 layers, instead of the 2 layers it expects.

The scans from Silverfast 8 should have one layer that contains the "regular scan" and a second one that contains the infra-red scan used for dust removal.
The scan you sent me has one layer that contains the "regular scan", a second layer that contains a smaller version of the "regular scan" and finally a third layer that contains the infra-red scan.

Try what I commented above, and send me the scan you get out of that.

Cheers,
Signynt

[Signynt]

Hey @molanfogarty, good news!

I've figured out a way to support scans with and without a thumbnail in the second layer. I've updated workflow with this change, which means you'll be able to keep on scanning the way you were previously!

To update the workflow: download the new release and find the Signynt's Darkroom Shortcut (IR) (VueScan).workflow file inside the new release.
Double click on it. It will ask you if you want to install it, then if you want to replace the current file. Select "Replace", and your workflow should be updated.

An important note though: the scan you sent me contains part of the scan holder on the top of the image (the little bit of black visible), and a bit on the left as well. This prevents the workflow from being able to detect the dust, so it's very important you make sure this isn't part of the scan. When scanning, make sure you only have the actual image selected.

Here I've cropped the image a bit to remove the scan holder, and inverted it using the updated workflow, then removed the dust.

Let me know if the updated workflow works for you!

Cheers,
Signynt

[molanfogarty]

I've shared an item with you: Test-1-Inverted.tif https://drive.google.com/file/d/1kVtahtgoNbKX4567L3RGxKYE9nAJ7WQY/view?usp=sharing&invite=CL3s88QB&ts=61df9bfa It's not an attachment – it's stored online. To open this item, just click the link above.

[molanfogarty]

I've shared an item with you: Test-1.tif https://drive.google.com/file/d/1GEJRcKnWW7BkyeRpOQCv41XB7JptxjSp/view?usp=sharing&invite=CJarmZAO&ts=61df9c09 It's not an attachment – it's stored online. To open this item, just click the link above.

[molanfogarty]

Hi Thanks so much for working through this for me, having looked at a couple of images I can see that the dust removal could be a big time saver. A couple of notes and questions Notes: A. I was scanning in 48 bit HDR RAW (Not 64 bit HDR*i* RAW). B. Apart from some, I think, minor variations to the settings on your video (see screenshot below), I followed your video instructions. C. This still produced the same result in Affinity (see screenshot below.) D. I've attached a link to the new scan and the inverted version. E. I realise that your updated workflow might make the above irrelevant but I thought I should follow it up in case it had any implications. Questions: 1. Can I crop the existing scans and run them through your inverter, or do I have to rescan? 2. Is it correct that I can (assuming I can crop the frame from the images) that I can use my existing 48 bit HDR RAW scans? 3. Again, assuming that Q1. and 2. are ok, do you think that there will be a significant difference between a 48 and 64 HDR*i* bit scan, i.e. can I save myself the effort of rescanning or is this a false economy? 4. You said to use the Signynt's Darkroom Shortcut (IR) (VueScan).workflow file, however, I've been using the Darkroom Shortcut (IR) (Silverfast).workflow. I just wanted to check that the Vuescan version is the one I should use in the future? Thank you again for your patient assistance. Michael I've shared the access to these files as per D. above: Scan: https://drive.google.com/file/d/1GEJRcKnWW7BkyeRpOQCv41XB7JptxjSp/view?usp=sharing Inverted file: https://drive.google.com/file/d/1kVtahtgoNbKX4567L3RGxKYE9nAJ7WQY/view?usp=sharing [image: Screen Shot 2022-01-13 at 1.21.58 pm.png] [image: Screen Shot 2022-01-13 at 1.30.45 pm.png]

…

On Wed, 12 Jan 2022 at 13:10, Vincenzo Mitchell Barroso < ***@***.***> wrote: Hey @molanfogarty <https://github.com/molanfogarty>, good news! I've figured out a way to support scans with *and* without a thumbnail in the second layer. I've updated workflow with this change, which means you'll be able to keep on scanning the way you were previously! To update the workflow: download the new release <https://github.com/Signynt/signynts-darkroom-shortcut/archive/refs/tags/v1.5.zip> and find the Signynt's Darkroom Shortcut (IR) (VueScan).workflow file inside the new release. Double click on it. It will ask you if you want to install it, then if you want to replace the current file. Select "Replace", and your workflow should be updated. An important note though: the scan you sent me contains part of the scan holder on the top of the image (the little bit of black visible), and a bit on the left as well. This prevents the workflow from being able to detect the dust, so it's very important you make sure this isn't part of the scan. When scanning, make sure you only have the actual image selected. Here <https://drive.google.com/drive/folders/1Db_i0VUX9pBdSwq82FkpsMAT0Dz0CRoY?usp=sharing> I've cropped the image a bit to remove the scan holder, and inverted it using the updated workflow, then removed the dust. Let me know if the updated workflow works for you! Cheers, Signynt — Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK5B6RHD7REH6WUCXDYBLWLUVTPIZANCNFSM5LVKELGQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Visit our blog, Our-Wanderlust <http://our-wanderlust.com/>, for travel stories from places that you'd rather be. http://our-wanderlust.com/ Anna & Michael *The world reveals itself to those who travel on foot*. Werner Herzog

[Signynt]

Hi,

First of all, regarding 4, yup, I made a mistake in my reply, you should continue using Darkroom Shortcut (IR) (Silverfast).workflow, and that's the workflow you need to update.

Another theory I have is that Silverfast creates a thumbnail if the scan is of a certain size. Since your scanner is newer than mine, and can scan at a higher DPI, it is producing a very large image, which makes Silverfast add a thumbnail, which is probably the real cause of the issue.
As far as I understand, you can keep scanning how you have been scanning up to now, as long as my shortcut continues working for you. If it doesn't work, I recommend falling back on to the settings I have shared with you.
Regarding D: yes, the new version should fix this issue entirely (I hope)!

Regarding 1: Yes, in theory you can crop the images you have already scanned, you shouldn't need to rescan. In practice this is a bit tricky, since both Preview and Affinity Photo end up deleting the necessary dust layer when cropping. The only way I've found so far to crop, without losing the necessary TIFF layers is with imagemagick.
You already have this on your mac, so you could use the Terminal to crop these images you have already scanned. I'll follow up with instructions on how to do this.

In the mean time, try out the updated workflow (Darkroom Shortcut (IR) (Silverfast).workflow), and tell me how that works for you!

Cheers,
Signynt

[molanfogarty]

Hi The (Darkroom Shortcut (IR) (Silverfast).workflow), works a treat. I was able to open the file in Affinity without a problem As you say the dust removal didn't work when I opened another uncropped file. Hopefully, I'll be able to crop them with your instruction. Thanks Michael

…

On Thu, 13 Jan 2022 at 14:47, Vincenzo Mitchell Barroso < ***@***.***> wrote: Hi, First of all, regarding 4, yup, I made a mistake in my reply, you should continue using Darkroom Shortcut (IR) (Silverfast).workflow, and that's the workflow you need to update. Another theory I have is that Silverfast creates a thumbnail if the scan is of a certain size. Since your scanner is newer than mine, and can scan at a higher DPI, it is producing a very large image, which makes Silverfast add a thumbnail, which is probably the real cause of the issue. As far as I understand, you can keep scanning how you have been scanning up to now, as long as my shortcut continues working for you. If it doesn't work, I recommend falling back on to the settings I have shared with you. Regarding D: yes, the new version should fix this issue entirely (I hope)! Regarding 1: Yes, in theory you can crop the images you have already scanned, you shouldn't need to rescan. In practice this is a bit tricky, since both Preview and Affinity Photo end up deleting the necessary dust layer when cropping. The only way I've found so far to crop, without losing the necessary TIFF layers is with imagemagick. You already have this on your mac, so you could use the Terminal to crop these images you have already scanned. I'll follow up with instructions on how to do this. In the mean time, try out the updated workflow (Darkroom Shortcut (IR) (Silverfast).workflow), and tell me how that works for you! Cheers, Signynt — Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK5B6REFTH4S2XR5Z54YPE3UVZDOBANCNFSM5LVKELGQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Visit our blog, Our-Wanderlust <http://our-wanderlust.com/>, for travel stories from places that you'd rather be. http://our-wanderlust.com/ Anna & Michael *The world reveals itself to those who travel on foot*. Werner Herzog

[Signynt]

Instructions for Copping

1. Put a copy of the images you want to crop onto your desktop
   • The images will be modified directly, so make sure you have a backup of the originals!
2. Open the Terminal, and type in cd desktop
3. Type in mogrify -gravity North -chop x500 image.tif and hit enter
   • Change which direction (North) you want to chop off of the image from (South, East, West)
   • Change the number (x500) to change how many pixels are being chopped off
   • Replace image.tif with the name of the file you want to crop

It's not the most streamlined way to do it, but it's currently the only way I know how to for these files, and it's better than rescanning everything :P

I'm glad the updated workflow is working for you!
I'll mark this issue as resolved, but if you're having any issues, feel free to let me know.

Best,
Signynt

[molanfogarty]

Hi Just one question on the cropping. Do I select an image to crop (and if so how) or will your instructions crop all the images on the desktop? Cheers Michael

…

On Thu, 13 Jan 2022 at 15:56, Vincenzo Mitchell Barroso < ***@***.***> wrote: Instructions for Copping 1. Put a *copy* of the images you want to crop onto your desktop - The images will be modified directly, so make sure you have a *backup* of the originals! 2. Open the Terminal, and type in cd desktop 3. Type in mogrify -gravity North -chop x500 image.tif and hit enter - Change which direction (North) you want to chop off of the image from (South, East, West) - Change the number (x500) to change how many pixels are being chopped off - Replace image.tif with the name of the file you want to crop It's not the most streamlined way to do it, but it's currently the only way I know how to for these files, and it's better than rescanning everything :P I'm glad the updated workflow is working for you! I'll mark this issue as resolved, but if you're having any issues, feel free to let me know. Best, Signynt — Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK5B6RDF56WOA2SN366X47LUVZLRBANCNFSM5LVKELGQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Visit our blog, Our-Wanderlust <http://our-wanderlust.com/>, for travel stories from places that you'd rather be. http://our-wanderlust.com/ Anna & Michael *The world reveals itself to those who travel on foot*. Werner Herzog

[Signynt]

You select the image to be cropped by replacing image.tif with the name of the file you want to crop. For example you can replace it with Test-1.tif.

Sidenote: you'll get an error if you've got a space in the file name, just remove the spaces from the filename in both the actual file, and the command you're running in the Terminal.

Only the image you specify will be cropped.

[molanfogarty]

Hi Again, thanks so much and a big apology for not reading your instructions re cropping thoroughly. They were obviously clear. Warmest regards Michael

…

On Thu, 13 Jan 2022 at 16:19, Vincenzo Mitchell Barroso < ***@***.***> wrote: You select the image to be cropped by replacing image.tif with the name of the file you want to crop. For example you can replace it with Test-1.tif. Sidenote: you'll get an error if you've got a space in the file name, just remove the spaces from the filename in both the actual file, and the command you're running in the Terminal. Only the image you specify will be cropped. — Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK5B6RBVJOZZLKXPMC3FNQ3UVZOHPANCNFSM5LVKELGQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Visit our blog, Our-Wanderlust <http://our-wanderlust.com/>, for travel stories from places that you'd rather be. http://our-wanderlust.com/ Anna & Michael *The world reveals itself to those who travel on foot*. Werner Herzog