[If you are posting a new bug, please include the following]
Can you share the logs here or with the support team for investigation?
logsForSupport.zip (483.6 KB)
Kyle - I know where the problem resides:
When I rebuilt my computer, Microsoft made my user name as: Roy Stehle
The space between first and last names was never expected or wanted.
I’ve tried to replace/change that directory name to eliminate the space without success.
Topaz seems to be substituting an under-bar (_) in place of the space. It’s failing finding the directory - see the following:
2025-08-20 14-18-49.742 Thread: 30728 Info Trying to open the file “D:/capture/Film-to-TIFF-Super8/Stehle, Roy_1.1920x1080/Stehle,Roy_1.1920x1080%05d.tif” false
2025-08-20 14-18-49.746 Thread: 30728 Info ===— Rotate on open: 3
Input #0, image2, from ‘D:/capture/Film-to-TIFF-Super8/Stehle, Roy_1.1920x1080/Stehle,Roy_1.1920x1080%05d.tif’:
Duration: 00:00:00.08, start: 0.000000, bitrate: N/A
Actually, the quoted structure is correct to accommodate the spaces.
It appears that the “%05d.tif” reference to all of the files is causing the problem.
I don’t know if Topaz is trying to create an asterisk (*). Even at that, I’ve had failures when I’ve specified a limited number of images. That should be accepted by Topaz. I should NEVER have to expect the entire directory to always be loaded. That’s just poor design. This does seem to explain why, when I do select just the first image, it still fails.
03/19/2019 03:54 PM 5,544,062 Stehle,_Roy_1.1920x1080_23904.tif
03/19/2019 03:54 PM 5,533,572 Stehle,_Roy_1.1920x1080_23905.tif
03/19/2019 03:54 PM 5,523,478 Stehle,_Roy_1.1920x1080_23906.tif
03/19/2019 03:54 PM 5,509,428 Stehle,_Roy_1.1920x1080_23907.tif
03/19/2019 03:54 PM 5,517,682 Stehle,_Roy_1.1920x1080_23908.tif
03/19/2019 03:54 PM 5,508,766 Stehle,_Roy_1.1920x1080_23909.tif
03/19/2019 03:54 PM 5,547,598 Stehle,_Roy_1.1920x1080_23910.tif
03/19/2019 03:54 PM 5,587,220 Stehle,_Roy_1.1920x1080_23911.tif
03/19/2019 03:54 PM 5,497,240 Stehle,_Roy_1.1920x1080_23912.tif
Hoping for a resolution on this input problem. I don’t remember it failing in 7.1.0. At that time, I was operating with a user name that didn’t include a space. I’ll remove 7.1.1 and see if the spaces are still a problem. It shouldn’t, but I suspect “%05d” will still be the problem.
I’ll also try a different directory without the comms and spaces.
These were just the names the frame-to-TIFF digitizing company used.
Roy
Version 7.1.1 works fine for a set of images without the spaces or comma.
If I can do a quoted command that contains spaces and commas, I would expect the “%05d” to be the problem. Also: If Topaz can’t find a file, it should alert the user.
Roy
I can honestly say I dont think I have ever seen that issue occur and would not have thought to look at the user name. Good catch on that.
This is something that we have requested from the devs and design team is to have more in depth error messaging. They have been trying to get some of that updated for us.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
