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

Unknown stream type: alsa (in AUR package) #692

Closed
cpegel opened this issue Sep 17, 2020 · 4 comments
Closed

Unknown stream type: alsa (in AUR package) #692

cpegel opened this issue Sep 17, 2020 · 4 comments
Labels
next release fixed in develop branch and will be part of the next release

Comments

@cpegel
Copy link

cpegel commented Sep 17, 2020

I just built snapcast 0.21.0 for an x86_64 ArchLinux using the AUR package.

However, having a source = alsa://… entry in my config, the snapserver won't start anymore:

2020-09-17 11-04-47.969 [Notice] (Server) Server::start: Unknown stream type: alsa
2020-09-17 11-04-47.969 [Error] (main) Exception: Unknown stream type: alsa

The output of snapserver -v starts with snapserver v0.21.0, so it is indeed the new version.

Maybe some configuration went wrong during the build, but I'd need help to figure that out.

@badaix
Copy link
Owner

badaix commented Sep 17, 2020

The AUR package is built using make, since I'm mainly using cmake, I forgot to add a flag in the makefile. It's now in, so the 0.21.1 or 0.22.0 AUR package should have support for alsa stream sources

@badaix badaix changed the title Unknown stream type: alsa Unknown stream type: alsa (in AUR package) Sep 17, 2020
@badaix badaix added the next release fixed in develop branch and will be part of the next release label Sep 17, 2020
@cpegel
Copy link
Author

cpegel commented Sep 17, 2020

Thanks, I've patched the makefile and rebuilt the package. ALSA sources are working now!

@badaix badaix closed this as completed Oct 15, 2020
@mogwa1
Copy link
Contributor

mogwa1 commented Oct 16, 2020

Hi, I'm the maintainer of the AUR package.
Just for my information: should I change the implementation to use cmake? If so, could the documentation be updated as well, because currently it's only mentioning make as the build mechanism.
Thanks in advance!

@badaix
Copy link
Owner

badaix commented Oct 17, 2020

Hi @mogwa1 ,
yes, cmake is the preferred way. I use it during development and recently changed the debian packaging to use cmake. Some things still need to be migrated to cmake, e.g. Android, the documentation and clang sanitizer builds.
I will update the documentation soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
next release fixed in develop branch and will be part of the next release
Projects
None yet
Development

No branches or pull requests

3 participants