File I/O error in PI Blink Process

[Ryderscope]

This is a repost of a post made to the PI forum.

Something odd is happening in the Blink process since I upgraded to Windows 10. I am receiving a file i/o error when attempting to move an image file to a 'Reject' folder. Something that I have done many times before but I now find that I am receiving a file i/o error that says that the source file does not exist. This is of course not correct as I successfully opened the file in the blink process. This is most puzzling and any assistance would be much appreciated. See attached image with a screen shot of the error that I am receiving.

Thanks in advance,
Rodney

[cfranks]

I though of a possible cause so I tried it and get the same error on Win 7. Nothing to do with my 'possible cause'.

Charles

[RickS]

I've never tried to use Blink to move files before but I just did and got the same error. My guess is that the Blink process isn't closing the files before attempting to move them.

Hopefully you'll get a response on the PI Forum from Juan or NKV (the original Blink author.)

Cheers,
Rick.

[Ryderscope]

Interesting, thanks for the follow up test Rick. Must be a recent thing as I have been using this technique for some time. I find it convenient when doing a quick first assessment of subs to use the Blink process to identify the obvious bad ones and to throw them into the bit bucket.

[RickS]

If it's something that got broken recently it shouldn't be too hard to fix, Rodney :)

I use Blink and SubframeSelector to pick poor quality subs to reject but I scribble notes on a piece of paper instead of trying to automate the process. I probably should be using the tools to their full potential...

Cheers,
Rick.

[Ryderscope]

I have just tested this on a PC at work and confirmed that this fault has come in with the recent update to the Blink module. I had not used PI on this machine for a couple of months and the Blink process worked fine. I then downloaded the latest update release, which included changes to the Blink process and - no go. The fault now exists. I believe that this problem has started with the update with the package title "Blink module version 1.2.2.218 (update)".

[Ryderscope]

Update: PI have confirmed a fault with the Blink process and have released an new version. I have just tested it and it works fine. A very quick turn around I am pleased to say.

[RickS]

Glad to hear you got a prompt fix, Rodney!