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:
Wim Taymans 2022-02-11 12:22:02 +01:00
parent 2c71282f16
commit d3f879e4ed

View file

@ -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;