mirror of
https://gitlab.freedesktop.org/pipewire/pipewire.git
synced 2025-10-29 05:40:27 -04:00
jack: only set force-latency property
There is no point in setting a node.latency property when we also set a force-quantum.
This commit is contained in:
parent
2c71282f16
commit
d3f879e4ed
1 changed files with 1 additions and 4 deletions
|
|
@ -4000,15 +4000,12 @@ SPA_EXPORT
|
|||
int jack_set_buffer_size (jack_client_t *client, jack_nframes_t nframes)
|
||||
{
|
||||
struct client *c = (struct client *) client;
|
||||
char latency[128];
|
||||
|
||||
spa_return_val_if_fail(c != NULL, -EINVAL);
|
||||
|
||||
snprintf(latency, sizeof(latency), "%d/%d", nframes, jack_get_sample_rate(client));
|
||||
pw_log_info("%p: buffer-size %s", client, latency);
|
||||
pw_log_info("%p: buffer-size %u", client, nframes);
|
||||
|
||||
pw_thread_loop_lock(c->context.loop);
|
||||
pw_properties_set(c->props, PW_KEY_NODE_LATENCY, latency);
|
||||
pw_properties_setf(c->props, PW_KEY_NODE_FORCE_QUANTUM, "%u", nframes);
|
||||
|
||||
c->info.change_mask |= SPA_NODE_CHANGE_MASK_PROPS;
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue