Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

channelFile format does not make sense for digital modes #724

Open
ZeroChaos- opened this issue Sep 7, 2022 · 1 comment
Open

channelFile format does not make sense for digital modes #724

ZeroChaos- opened this issue Sep 7, 2022 · 1 comment

Comments

@ZeroChaos-
Copy link

channelFile csv was added to help users configure conventional systems. The design makes a lot of sense, until you look at it with a digital conventional mode.

TG Number | Frequency | Tone | Alpha Tag | Description | Tag | Group | Enable (optional)

But wait, why are we setting an arbitrary talk group when talk group is coming in via the metadata on the transmission? Turns out we aren't setting the metadata for conventional digital modes and probably should be, but once that happens, this csv format makes no sense as the first field will be ignored.

@robotastic
Copy link
Owner

Good points - I am going to have to dive into the code though to see what is possible. The Conventional P25 was sort of done as a hack - it copied the approach taken with Analog. The new stuff with the Transmissions might make it possible to pull this data from the transmission.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants