Hi Eric,
Thanks for your reply.
OK, first issue, namely .edl files. There seems to be some extreme miscommunication here!
I'm using Channels DVR server 2026.10.28.2140 on macOS 27.2 on Apple Silicon. I don't know if things are perhaps different for Windows or Linux, but on my system (lets just assume a movie)
-
the recordings live in
ChannelsDVR[an externalSSD]/DVR/Movies/movieName.mpg
This folder, Movies, has never had anything in it except *.mpg files, and that hasn't changed recently
-
in the past there was a directory called
ChannelsDVR[an externalSSD]/DVR/Logs/comskip that had multiple directories in it, each directory a number corresponding to the recording number of the file (recordings start at 1 and just keep incrementing).
Such a directory, let's assume it's 1234, used to have a few files in it useful for commercial editing, including a soft link to the target .mpg, a video.edl file, a video.ffsplit file, and a bunch of preview stills as small .jpgs
The latest version of such a directory, let's assume it's 12345, now has ONLY the preview-###.jpg files, no .edl, no soft link, no .ffsplit.
A system wide search for .edl files shows them only in these Logs/comskip/ directories, and only in the older directories.
Secondly thread/multicore uiltization.
Look at the screen shots below.
I have an M2 Pro with 6+4 cores. I have the system set up to use 9 threads (the max it will allow me).
I have (second screen shot) one manual commercial detection queued up (I'm trying to see if forcing a manual commercial detection will generate a .edl somewhere and an entire library's worth of old content waiting for new-style processing and characterization.
There's no shortage of work to be done. And yet channelsDVR is running at a pathetic ~10..20% or so, just recording the two active recordings, but making no attempt whatsoever to work through the queued up recordings. And this never seems to change! I can maybe force it to start working through the work queue for a few minutes or so by manually hitting the "Reprocess" buttob below Media Fingerprints, but that results in only something between 0 seconds and maybe 180 seconds of hard work before we revert to this situation of lots of queued up work and nothing being done!
Both these problems are very recent, I don't know exactly but maybe three or four weeks ago?