Shutting down PlanePlotter and its ancillary applications certainly helped, and running it on my laptop out in the field proved fruitful too.
Raw from the laptop (while moving):
http://www46.zippyshare.com/v/26685312/file.html
Processed from the laptop, same time & conditions of course:
Zippyshare.com - DSDPlus.2014-01-03@1425.wav
Raw from the PC just now (and naturally nobody's talking, so no processed audio):
Zippyshare.com - DSDPlus-Raw-Input_2014-01-03@152454.wav
SDR#, when minimized or covered by another window, is taking 18 to 22 percent CPU while running (bringing in audio from the SDR stick). When I bring up the display with the graph and/or waterfall, that goes up to 30 percent. Even completely idle, i.e. before I hit "play", SDR# is using up 3 percent CPU. I'm considering doing a wipe & fresh install of the software to see if that helps.
I also see it's decoding as an Icom IDAS trunk system (NXIDAS voice) - I've never come across one of those before. Anyone know what the MB in the NXIDAS MB VOICE stands for?
The control channel is NXDN96. Another local system resulted in "NXDN96 VOICE" (and there probably was a two-letter code but I don't recall) so I was surprised that the valid, good decode this afternoon indeed showed NXIDAS MB VOICE. With the control channel running, I see NXDN96 TB CCDATA.
Looking at the NXDN documentation (particularly the CAI document), I'm wondering if MB could mean multi-site broadcast group call... because the audio above is definitely multi-site (Midnapore and Westbrook Mall are on opposite ends of the city, and I'm listening to a tower 30 miles away from either of them). But that doesn't explain TB. Neither abbreviation shows up in the NXDN documentation explicitly - It could even be a term cooked up by the author of DSD+.