Generating Fingerprint

[tycrum]

Can someone explain what is going in when I'm logging generating fingerprint for file xxxxxx in the log? I keep hearing my DVR (windows10) pc's fans spinning up when nobody is using it. When I look in the log i see the following in my log. Under activity I see video processing and the video name. In task manager channels is using substatial CPU and bandwidth. I guess I changed something because I don't remember those entries in the log before. Thanks

2025/12/22 09:57:18.623220 [DVR] Generating fingerprint for file-11390: The Blacklist S10E12 Dr Michael Abani 2023-05-14-2159.mpg
2025/12/22 09:59:18.333654 [DVR] Generated fingerprint for file-11390 in 2m0s
2025/12/22 09:59:18.371758 [DVR] Generating fingerprint for file-11394: Rio Bravo (1959) 2023-05-16-1959.mpg
2025/12/22 10:05:39.612720 [DVR] Generated fingerprint for file-11394 in 6m21s

[babsonnexus]

@tycrum

I guess I changed something because I don't remember those entries in the log before.

Not you, Channels changed. However, this is in relation to the in-development Commercial Skip/Edits sharing feature:

Another Call For Help: Does anyone manually edit the commercials on a lot of their recordings?

Thanks for catching this. We were reporting this activity even though no commercial edits were being shared (due to the setting not being enabled). The latest pre-release resolves this issue. I've made some improvements to fingerprinting where it was being more aggressive than it should have been. Thanks for reporting these issues. Can you try the latest pre-release and see if it lowers the load on your system?

You should probably get to the latest prerelease from last night because it specifically addresses the performance issues you are seeing.

DVR Pre-Release Notes

v2025.12.22.0514 • IMPROVED: make sure fingerprinting happens at low priority in more places

[tycrum]

Thanks. I had loaded a pre-release yesterday, but there was another one. I remember the request for commercial edits but I didn't enable that because I really don't edit commercials unless it is extremely bad. Loaded the new pre-release. Notice that the usage is lower but still there even with the submit disabled. But at least my fans aren't all running right now.

[eric]

Fingerprinting has been enabled for all users to support current and future features (such as Intro/Credits detection). It is intended to run in the background (when no other activity is happening on your DVR) to not impact other playback.

[latenitetech]

Is there a way to opt-out of this new aggressive fingerprint generation? I would have thought the checkbox "Deep Video Processing" under Settings/General would control this behavior, but unchecked I'm still seeing the constant fingerprint generation. And while I agree it only runs as a background task, it still causes the PC to use a lot more power than it used to. I'm specifically using a power-efficient old Windows laptop (ThinkPad T410s) that idles under 10 watts, and now I'm seeing it consuming ~33 watts continuously due to all this new activity.

It appears to be walking my entire local content library of ~16TB (15,766 Recordings) generating a new fingerprint for each file. Per the log it appears to have started on 12/20 with an update I apparently took that day, and so far has processed 5,630 files. So that would mean I have about 2 more weeks of this heavy load before it hopefully settles down. But my fear is you'll change the fingerprint algorithm and it'll want to start all over again.

I'm all for continuous development and new features, but this seems like a really high price to pay for functionality I will likely never use, especially across my entire local library. Can you offer up some way to control this behavior, or perhaps selectively apply it?

Thx!

[Kryptonyte]

@eric

Fingerprinting has been enabled for all users to support current and future features

How do I disable this feature?

[eric]

@latenitetech

I would have thought the checkbox "Deep Video Processing" under Settings/General would control this behavior, but unchecked I'm still seeing the constant fingerprint generation.

This is fixed in the latest pre-release — previously already enqueued recordings would be processed if the setting was enabled at the time it was enqueued.

@fancybot

v2025.12.27.0118

• FIXED: “Deep Video Processing” setting did not impact already-enqueued recordings

[latenitetech]

Yep, the latest update worked as expected. Thx for the quick response!