Nick
Nick
Couldn't we just start a new call if the recorder detects a change in PL/DPL? Over in https://github.com/robotastic/trunk-recorder/pull/630, I'm trying to imagine a future where conventional channels can be organized...
Plotting the two in audacity, it does look like this is just sox doing its usual "fast but not very good" normalization pass. Sox is adjusting the volume of the...
> Do you know where the normalization occurs in the code? I might look into adding some kind of audio threshold check that skips normalization on silent calls. https://github.com/robotastic/trunk-recorder/blob/36dbf43c1b41e3f2a9c15e4a267841ed27417c12/trunk-recorder/call_concluder/call_concluder.cc#L35 `sox...
Changes in the recent [no-overlap](https://github.com/robotastic/trunk-recorder/tree/no-overlap) branch have allowed plugins to see errors and spikes. Commits to this branch should already provide rdio-scanner with correctly-formatted json files if using upload scripts....
> 1. If my control channel and the speech channel are in the sample rate range that my dongle supports, does that mean that one dongle is enough for me?...
Just tested this on both a fresh master.zip and a git pull; comment out the below lines in `git_watcher.cmake`: https://github.com/robotastic/trunk-recorder/blob/a30ee308518d478c4fdcd39fab2314717898bd65/git_watcher.cmake#L137-L140 and it will build. T-R will fall back on the...
> What version of git are you using? > […](#) I tested the above with `git version 2.37.1` on MacOS/homebrew. As noted previously, building from a [source zip](https://github.com/robotastic/trunk-recorder/archive/refs/heads/master.zip) will fail...
Instead of using the frequency as a TG ID, wouldn't it be helpful to just have something like: ```json "channels": [ 472000000, 472100000, 472200000, 472300000, 472400000, 472500000, 472600000, 472700000, 472800000,...
Currently playing around with a solution using `talkgroupsFile` as a lookup table for conventional talkgroup numbers and alpha tags (groups, etc..). For example: ``` "systems": [{ "type": "conventionalP25", "channels": [451650000,...
> @taclane - that is interesting. I think something like that could work. The CSV parsing code is already pretty brittle, but this could be a good excuse to work...