Open Skyking-Bravo opened 1 week ago
What setting are you using for patch group streaming?
Go to the User Preferences dialog, Audio >> Call Management tab.
You can select the behavior for patch group streaming to either stream the call audio using the patch group, or to stream the call as the individual patched groups.
What setting are you using for patch group streaming?
Go to the User Preferences dialog, Audio >> Call Management tab.
You can select the behavior for patch group streaming to either stream the call audio using the patch group, or to stream the call as the individual patched groups.
Yes, I am familiar with those options. Selecting "Individual Talkgroups" does not help. In fact it seems to make things worse in that I appear to be missing some traffic entirely, when compared to selecting "Patch Group".
Maybe these screenshots might be helpful. In the first, user preference for streaming is set to individual talkgroups and in the second it is set to patch group. In the first screen shot, Fire Dispatch 1801 is patched with 65133 according to my SDS100 and with 65130 in the second screenshot. But it doesn't look like sdrtrunk is seeing 1801 in either scenario.
sdrtrunk Version Nightly Version (Downloaded on 8/30/24)
Describe the bug I am using sdrtrunk to stream to Rdio-Scanner and on the Harris-built Miami P25 system https://www.radioreference.com/db/sid/10812 many transmission only show up on the patch 65XXX talkgroups and not also the source talkgroups such as Fire Dispatch (TG 1801) and EMS Dispatch (1803). It seems like it should be possible in sdrtrunk to generate the audio files in such a way that Rdio-Scanner would play the traffic on the Fire or EMS Dispatch channels. When the 65XXX talkgroups are active the traffic is also heard on the source talkgroups when using my SDS100.
To Reproduce Not Applicable
Expected behavior When a 65XXX series patch talkgroup is in use, I expect sdrtrunk to produce a streaming file that contains the necessary metadata to allow rdio-scanner to play the audio via the Fire-Dispatch or EMS Dispatch channel.
Screenshots Not Applicable
Application Log
Desktop (optional - complete the following information):
Additional context Examples of filenames of audio recordings: '20240908_004337Miami_P25_Miami_T-ControlTO_P65144[83904098390411]_FROM_7030220.wav' '20240908_004348Miami_P25_Miami_T-ControlTO_P65144[83904098390411]_FROM_7030901.wav' '20240908_004355Miami_P25_Miami_T-ControlTO_P65144[83904098390411]_FROM_7030275.wav' '20240908_004401Miami_P25_Miami_T-ControlTO_P65144[83904098390411]_FROM_7030901.wav' '20240908_004432Miami_P25_Miami_T-ControlTO_P65144[83904098390411]_FROM_7030273.wav' '20240908_004448Miami_P25_Miami_T-ControlTO_P65144[83904098390411]_FROM_7030901.wav' 20240908_004505Miami_P25_Miami_T-Control__TO_65144_FROM_7030198.wav
Details of the first file: File Name : 20240908_004337Miami_P25_Miami_T-Control__TO_P65144[8390409__8390411]_FROM_7030220.wav Directory : . File Size : 47 kB File Modification Date/Time : 2024:09:08 00:43:37-04:00 File Access Date/Time : 2024:09:08 00:44:31-04:00 File Inode Change Date/Time : 2024:09:08 00:43:37-04:00 File Permissions : -rw-rw-r-- File Type : WAV File Type Extension : wav MIME Type : audio/x-wav Encoding : Microsoft PCM Num Channels : 1 Sample Rate : 8000 Avg Bytes Per Sec : 16000 Bits Per Sample : 16 Product : T-Control Subject : Miami P25 Warning : Bad CMT� chunk ID3 Size : 393 Comment : Date:2024-09-08 00:43:37.946;System:Miami P25;Site:Miami;Name:T-Control;Decoder:P25 Phase 1;Channel:0-756;Frequency:860462500; Album : T-Control Composer : sdrtrunk nightly - 2024-08-31T12:34:00.580+0000 Genre : Scanner Audio Date : 2024-09-08 00:43:37.946 Grouping : Miami P25 Title : P:65144 [8390409, 8390411]"Patch Channels" Artist : 7030220 Year : 2024 Date/Time Original : 2024 Duration : 2.93 s