Is there something I'm missing on my custom builds for film scanning?

ajn0071

Prominent
May 8, 2017
6
0
510
I have a weird problem and I'm hoping someone can help me.

I work for a small archive and we purchase motion picture film scanning equipment from a local builder. I build my own computers, nothing too fancy, just something with a lot of storage, mainly, to handle the digitization files and enough speed and RAM to do basic editing (running Windows 7 Pro). I also make sure these computers exceed the specs required for the scanners. The problem I've had, though, is with some new scanners we bought. Just some background on the scanners, they are very simple. Basically a camera is connected via USB to the computer. The scanner's hardware triggers the camera to take pictures and feed those into a file that is built by the scanning software.

The scanner has two speed settings: fast and slow. Everything works fine when scanning at the slow speed, but if I put it on the fast speed, after capturing about 100 feet of film it starts dropping frames like crazy. It is almost like the computer can't handle the data coming through from the camera. When I mentioned this to the scanner builder, he said that there's something weird about custom built computers and that they tend to have this problem. If I use a Dell or the like, the problem doesn't happen. I happened to have a Dell laptop in the office and, sure enough, on the fast speed the scanning software has no problem and doesn't drop a single frame.

My question is, am I doing something wrong on my custom builds to cause this problem? It makes no sense to me. All the drivers are up to date. This problem even happens when connected to a USB 3.0 port, which should have more than enough bandwidth to handle the incoming data. I can't help but think there must be a setting, or maybe even a jumper on the motherboard, that I'm not getting right that is causing these problems.

If anyone has any kinds of ideas to this weird issue, I'd greatly appreciate it.
 


There are no solid state disks involved, though one laptop (not a Dell) that I tested the scanner while troubleshooting did have the same problem even though it has SSDs installed. All the drives being used on the computers are 6 GB/s drives plugged into 6 GB/s ports. I even tried RAID 0, same result.

I should also point out that the specs on the Dell computer we purchased for the scanner we were having problems with has almost identical specs to the computers I build, no SSDs and no RAID, yet the scanner works fine on both speed settings.

P.S.: The only reason speed is an issue is because it takes twice as long to digitize a reel on the slow speed as on the fast speed and we are an archive that has a high volume of film to be digitized. It already takes forever, need to avoid anything that slows us down further.
 
My custom build:
Windows 7 Pro SP1
CPU Intel Core i5-4460
MB: MSI Z97 PC Mate ATX
Memory: 8GB GSkill
C Drive: 1GB WD1003FZEX (not used for scanning)
D & E Drives: WD2003FZEX

Dell Laptop it worked on for troubleshooting (scanner is currently running on a Dell Precision 3620):
Vostro 3750
Windows 7 Pro SP1
CPU: Intel Core i5-2450M
Memory: 8 GB
HDD: ST9500325AS

 
I think the problem is the size of the ram sticks in the custom build, each one is only 2GBs, so it's possible... the scanner software isn't using all the ram very well, and it overloads after reaching a certain amount of data gets stored in memory.

It'd be a pretty quick and simple test, with either an 2x4gb set or a single 8gb stick being the only one in the system.

Because the laptop is technically weaker than your desktop, by quite a big amount, so it'd have to be something like the way the computer is handling data.
 


That is an excellent idea. I'll try this. Thanks!
 


I doubt the RAM is the problem, but anything is possible. I am much more thinking it is a USB issue. I can't find a block diagram for that motherboard to see if all the USB ports originate on the motherboard chipset or if they added non-intel USB ports.
 
Honestly, with this hardware and software combo, "anything is possible" is the right attitude to have. It isn't exactly "polished" let's say. I wouldn't be surprised if the software is not handling memory properly.
 
Since you mentioned the camera is taking pictures, the camera itself could be a bottleneck right there. From phone cameras to studio-grade cameras. They still have hardware to encode those pictures. Now, it could be the camera, but lets not take it there.
Another limitation, when it comes to USB 2.0 / 3.0 is the bandwidth.
Although you are inputting data through a USB 3.0 Slot, are you sure the scanner is able to supply data at that bandwidth ?
In that case, it would be like putting a USB 2.0 Disk into a USB 3.0 Slot, USB 2.0 Speeds.

EDIT: You could try with special FPS cameras like the SlowMoBros. They use cameras that record real-time, but are strong enough to slow down videos to an extent where you can see the output video without any blur.
That should be enough to capture fast-moving reel. I doubt these are cheap by any standard, but it could help.