Howdy,
I have Trunking Recorder configured to record via Universal Trunker (and via DSD+ for ProVoice). It's an awesome setup; however, Trunking Recorder is not recording all of the radio calls UniTrunker follows with the VCOs. It's getting to the point of being quite unreliable.
The calls that the recorder skips are all picked up and broadcast by UniTrunker. The call info shows up on the proper VCO/Scope, it's listed in the UniTrunker Call History, and there is audio output to the virtual cables. However, the Trunking Recorder window does not show the call, it does not record (no audio file), and it does not show up on the web server. If I were to output the Unitrunker audio to my speakers, I would hear all the calls; likewise, Trunking Recorder fails to record some calls while also recording other calls (so it's not like a complete freeze or disconnect).
I especially notice the problem with calls made on the same talkgroup by the same Source ID in succession (such as police conversations or tac channel conversations -- it may catch 4/10 of ~3 second calls made within a minute); however, it also skips unrelated calls (calls spaced out over time and talkgroup) and calls on infrequently used talkgroups. It occurs during both slow radio traffic (there is only one call and Trunker Recorder misses it) and when the system is busy (i.e. Trunking Recorder will record 2-3 of the conversations while missing the other one or two -- in these cases a VCO is assigned and broadcasting audio for all calls). It occurs with both digital and analog calls. Basically, I can't identify a pattern, which makes it difficult to troubleshoot.
About my setup:
I am following an EDACS system with analog and Provoice traffic. There are 5 voice channels on the system. I have one R820T2 and one R820T SDR dongles monitoring the system with three voice VCOs each (this covers the entire bandwidth of the channels and enough VCOs to cover traffic on all voice channels simultaneously). The R820T2 also follows the control channel. I am routing through two instances of DSD+ on two of the VCOs for Provoice decoding (one on each SDR) -- most of the traffic is analog. All of my virtual audio cables transmit audio to Trunking Recorder properly, and all of the VCOs have provided complete recordings on Trunking Recorder. I have Trunking Recorder 1.8.1531.5820 and Universal Trunker 1.0.32.7. I am using both Virtual Audio Cable (paid) and VB Cable. My reception of the EDACS control signal is good, with the health hovering at or near 100 most of the time. I'm running Windows 8.1, Intel i7, 32 GB RAM, and a solid state drive, so I don't think it is hardware bottleneck (Unitrunker uses 1-2% CPU, 17mb ram & Trunking Recorder < 1% CPU, ~50mb).
I am happy to upload any logs that may be of use. Of note, I noticed a receiver DecodeA log around 70 mb. (Edit: deleted some of my ignorance regarding the log files)
Also notable, sometimes Trunking Recorder freezes when I click save after changing settings. When I restart the program, the settings are set the way I changed them. (This doesn't bother me -- just trying to provide a comprehensive history)
If anyone can shed some light on this, I should be very thankful. Information regarding the communication between UniTrunker and Trunking Recorder would be helpful. What logs or files does Trunking Recorder read? How does it know when to stop and end recording, as well as which VCO to follow? Etc. A general commentary of Trunking Recorder should be very useful; I couldn't find much about the nuts and bolts of it on the forums.
In summary, my problem is that the Trunking Recorder call list does not show all of the calls in the UniTrunker Call History... many of the calls are not recorded. I appreciate any insight.
Cordially,
Justin
I have Trunking Recorder configured to record via Universal Trunker (and via DSD+ for ProVoice). It's an awesome setup; however, Trunking Recorder is not recording all of the radio calls UniTrunker follows with the VCOs. It's getting to the point of being quite unreliable.
The calls that the recorder skips are all picked up and broadcast by UniTrunker. The call info shows up on the proper VCO/Scope, it's listed in the UniTrunker Call History, and there is audio output to the virtual cables. However, the Trunking Recorder window does not show the call, it does not record (no audio file), and it does not show up on the web server. If I were to output the Unitrunker audio to my speakers, I would hear all the calls; likewise, Trunking Recorder fails to record some calls while also recording other calls (so it's not like a complete freeze or disconnect).
I especially notice the problem with calls made on the same talkgroup by the same Source ID in succession (such as police conversations or tac channel conversations -- it may catch 4/10 of ~3 second calls made within a minute); however, it also skips unrelated calls (calls spaced out over time and talkgroup) and calls on infrequently used talkgroups. It occurs during both slow radio traffic (there is only one call and Trunker Recorder misses it) and when the system is busy (i.e. Trunking Recorder will record 2-3 of the conversations while missing the other one or two -- in these cases a VCO is assigned and broadcasting audio for all calls). It occurs with both digital and analog calls. Basically, I can't identify a pattern, which makes it difficult to troubleshoot.
About my setup:
I am following an EDACS system with analog and Provoice traffic. There are 5 voice channels on the system. I have one R820T2 and one R820T SDR dongles monitoring the system with three voice VCOs each (this covers the entire bandwidth of the channels and enough VCOs to cover traffic on all voice channels simultaneously). The R820T2 also follows the control channel. I am routing through two instances of DSD+ on two of the VCOs for Provoice decoding (one on each SDR) -- most of the traffic is analog. All of my virtual audio cables transmit audio to Trunking Recorder properly, and all of the VCOs have provided complete recordings on Trunking Recorder. I have Trunking Recorder 1.8.1531.5820 and Universal Trunker 1.0.32.7. I am using both Virtual Audio Cable (paid) and VB Cable. My reception of the EDACS control signal is good, with the health hovering at or near 100 most of the time. I'm running Windows 8.1, Intel i7, 32 GB RAM, and a solid state drive, so I don't think it is hardware bottleneck (Unitrunker uses 1-2% CPU, 17mb ram & Trunking Recorder < 1% CPU, ~50mb).
I am happy to upload any logs that may be of use. Of note, I noticed a receiver DecodeA log around 70 mb. (Edit: deleted some of my ignorance regarding the log files)
Also notable, sometimes Trunking Recorder freezes when I click save after changing settings. When I restart the program, the settings are set the way I changed them. (This doesn't bother me -- just trying to provide a comprehensive history)
If anyone can shed some light on this, I should be very thankful. Information regarding the communication between UniTrunker and Trunking Recorder would be helpful. What logs or files does Trunking Recorder read? How does it know when to stop and end recording, as well as which VCO to follow? Etc. A general commentary of Trunking Recorder should be very useful; I couldn't find much about the nuts and bolts of it on the forums.
In summary, my problem is that the Trunking Recorder call list does not show all of the calls in the UniTrunker Call History... many of the calls are not recorded. I appreciate any insight.
Cordially,
Justin
Attachments
Last edited: