Why whenever I schedule a DVB-T recording does TSReader report that it couldn't lock the signal?
You're probably receiving your signals through a relay station. Most of the relays don't correctly update the network table (NIT) to reflect the frequencies they're actually transmitting on, but rather use a thing called a frequency list descriptor - if you click on an NIT entry you'll see these listed in the TSReader text window. So, TSReader is scheduling recordings based on the NIT frequency and has no way that we currently know of to find which relay frequency to actually tune to.
To work around this, create a file called DVBT.INI in the folder where TSReader is installed. The format of this file is simply the full frequency from the NIT and an equal sign along with the relay frequency for the same multiplex along with a [DVBT] tag at the start of the file. Here's a sample for the UK for a DVB-T relay that covers a town near London:
[DVBT]
481.833=746.000
505.833=690.167
529.833=777.833
537.833=826.000
561.833=786.167
578.167=802.000