DSheirer
Add CTCSS codes to Conventional
I'll admit not having any idea what is involved, or how complicated that is. But for me, it is the one feature that would make the program perfect. I have seen the idea of "bounties". How much would be appropriate? I'd pitch in 50$ in a heart beat and I can hardly believe I'm alone!
C5o
On Tue, 15 Oct 2024, 12:03 grahampaull, @.***> wrote:
This would be a very welcome addition.
— Reply to this email directly, view it on GitHub https://github.com/DSheirer/sdrtrunk/issues/2008#issuecomment-2413576461, or unsubscribe https://github.com/notifications/unsubscribe-auth/AS3G6GOX2Q4BR6AW5QDHQLLZ3TZBTAVCNFSM6AAAAABPOOBAPCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJTGU3TMNBWGE . You are receiving this because you are subscribed to this thread.Message ID: @.***>
This would be a perfect addition. Also to get rid of the squelch noise at the end of every transmission. Maybe with adding pl tones that would fix that too.
+1 for me as well.
There was discussion from @DSheirer a while ago in #80
https://github.com/DSheirer/sdrtrunk/issues/80#issuecomment-1585558699
This would be the prefect implementation. Being able to add it as an Identifier to an alias would be amazing and would open doors to allow conventional to be submitted to Broadcastify Calls
Bonus points for adding CDCSS as well.
Tossing my hat/vote into the ring too, CTCSS would be great. Is there still a plan to implement it as an alias like in that other thread?
Been toying with Trunk Recorder on Linux just to get this feature but that's a whole other can of worms.
Decoding CTCSS / PL Tones would be helpful especially when you have multiple channels/repeaters sharing the same frequency to tell the different channels apart.
Hope DSheirer finds some time to add support for CTCSS/DCS codes, because that is the only thing this program is missing (leave aside TETRA) to be absolutely perfect :)
Hope DSheirer finds some time to add support for CTCSS/DCS codes, because that is the only thing this program is missing (leave aside TETRA) to be absolutely perfect :)
DCS is already in there, but not CTCSS. I ended up switching to Trunk Recorder as it can do all my systems and includes CTCSS, but definitely a big undertaking to get it working. The P25 decoding in SDRTrunk with JMBE decoder is superior by a bit, but I wanted an all-in-one solution. But may revisit in the future and add SDRTrunk back into the mix if CTCSS gets added (if only it had SmartNet support, then it could be my all in one solution).
Going to +1 this as well. CTCSS/DCS/NAC/Color Code on the channels themselves would be the missing link for my ingest. It's a high profile ingest and hears everything with no way to filter out traffic from other areas. (I know DCS is in the Alias list but I would like it on the channel itself)
