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.

Sign up for GitHub

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

Jump to bottom

Snapcast client not starting with error "missing argument for --latency" #211

Closed
tmigone opened this issue Jun 8, 2020 · 1 comment
Closed

Snapcast client not starting with error "missing argument for --latency" #211

tmigone opened this issue Jun 8, 2020 · 1 comment
Labels
bug Something isn't working multi room Everything about the multi room

Comments

@tmigone
Copy link
Contributor

tmigone commented Jun 8, 2020

Describe the problem

Snapcast client not starting after deploying with no customization. Error below:

08.06.20 10:04:04 (-0300)  snapcast-client  Target snapcast server: 192.168.90.207
08.06.20 10:04:04 (-0300)  snapcast-client  Exception: missing argument for --latency
08.06.20 10:04:04 (-0300)  snapcast-client  
08.06.20 10:04:04 (-0300)  snapcast-client  Allowed options:
08.06.20 10:04:04 (-0300)  snapcast-client    --help                          produce help message
08.06.20 10:04:04 (-0300)  snapcast-client    -v, --version                   show version number
08.06.20 10:04:04 (-0300)  snapcast-client    -l, --list                      list PCM devices
08.06.20 10:04:04 (-0300)  snapcast-client    -s, --soundcard arg (=default)  index or name of the pcm device
08.06.20 10:04:04 (-0300)  snapcast-client    -e, --mstderr                   send metadata to stderr
08.06.20 10:04:04 (-0300)  snapcast-client    -h, --host arg                  server hostname or ip address
08.06.20 10:04:04 (-0300)  snapcast-client    -p, --port arg (=1704)          server port
08.06.20 10:04:04 (-0300)  snapcast-client    -d, --daemon [=arg(=-3)]        daemonize, optional process priority [-20..19]
08.06.20 10:04:04 (-0300)  snapcast-client    --user arg                      the user[:group] to run snapclient as when daemonized
08.06.20 10:04:04 (-0300)  snapcast-client    --latency arg (=0)              latency of the PCM device
08.06.20 10:04:04 (-0300)  snapcast-client    -i, --instance arg (=1)         instance id
08.06.20 10:04:04 (-0300)  snapcast-client    --hostID arg                    unique host id
08.06.20 10:04:04 (-0300)  snapcast-client    --player arg                    audio backend
08.06.20 10:04:04 (-0300)  snapcast-client    --sampleformat arg              resample audio stream to <rate>:<bits>:<channels>

To Reproduce
Steps to reproduce the behavior:

  1. Deploy latest balenaSound

Expected behavior
Snapcast client should start.
@tmigone tmigone added bug Something isn't working multi room Everything about the multi room labels Jun 8, 2020
tmigone added a commit that referenced this issue Jun 8, 2020
@tmigone
snapcast-client: Fix bug where snapcast client is not starting
43d58e3 
Connects-to: #211
Change-type: patch
Signed-off-by: Tomás Migone <tomas@balena.io>
@tmigone tmigone mentioned this issue Jun 8, 2020
Merged
@tmigone tmigone closed this as completed Jun 8, 2020
@jellyfish-bot
Copy link

[tmigone] This issue has attached support thread https://jel.ly.fish/be1f09bb-6328-4cb2-91ef-65f2423e487c

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working multi room Everything about the multi room
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tmigone @jellyfish-bot