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

Use pcmrecord instead of pcmcat #971

Merged
merged 3 commits into from
Jan 1, 2025

Conversation

argilo
Copy link
Contributor

@argilo argilo commented Dec 31, 2024

As noted in ka9q/ka9q-radio#66 (comment), @ka9q has merged pcmcat's functionality into pcmrecord, and pcmcat may be removed or converted to a shell script. Here I've switched over to using pcmrecord, and this is working well on my test station.

Since the required pcmrecord functionality is only available in recent commits, the wiki will need to be updated to recommend a newer commit. (I've tested with 08142683dbc398087a5b7d384b1a36bb24b1eca3).

Since a new commit is required, there's no reason to keep the workaround for the powers bug (#941) so I've reverted it here.

@argilo
Copy link
Contributor Author

argilo commented Dec 31, 2024

ka9q-radio now depends on libogg-dev, so I added that to the Dockerfile to fix the build.

@darksidelemm darksidelemm merged commit bdf2e90 into projecthorus:testing Jan 1, 2025
6 checks passed
@ka9q
Copy link

ka9q commented Jan 12, 2025

Glad it's working for you. I think I'm pretty much done with pcmrecord.c for a while after my intense work of the past few weeks. I did add the --raw option.

I'd like to encourage users to also try the --exec option, which will obsolete the pcmspawn program. It's very convenient when you want to invoke a separate instance of some consumer program on each SSRC stream in the same multicast group. You don't have to worry about the SSRC; it and other parameters, like the radio frequency, sample rate, channel count and antenna description are available as macros to the command line that executes your program. You just add channels in the radiod config file and everything else happens automagically.

With the --stdout option you either have to specify the SSRC or it will automatically latch onto the first one it sees and ignore any others. That's really only useful if there's only one SSRC in the group, which is often not the case.

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

Successfully merging this pull request may close these issues.

3 participants