The stream count wont be related to his problem. As far as I can tell it's calling dtvTune.exe when it needs to. I'm wondering if it's something to do with those ip addresses or similar.
So looking at the logs I see the problem. The .102 ip actually belongs to my fourth tuner not my second. Dtvtune is never called with the .101 or .103 ips which belong to my second and third tuners. Somehow it is not calling the right blaster for those two tuners.
The blaster settings need to be set correctly when you create the channels. It stores a copy in each channel (since you might want different channel using difference settings - like if you've got two if you have one device with two set top boxes connected to different inputs and with different blasters)
A common error is for people to try editing their blaster settings after they've created their channels.
They were set right before the channels. That's why it works fine with the previous version of NShared when I put it back in place without changing anything else.
So I was just looking at the channel_mapping table and you are correct that it only has references to 100 and 102. Was that possibly not being used with older versions of NShared? Also would the right fix now be to simply remove the channels for those tuners and re-add them?
Yeah, that's probably the best fix. (backup your database first though)
I've been meaning to update the screen to show what blaster info is associated with each channel, to make it more clear to people. If you want to post a copy of your db3 file, I use it as a test case.