PipeWire: Tutorial - Part 3: Forcing A Roundtrip

PipeWire 1.2.7

Loading...
Searching...
No Matches
Tutorial - Part 3: Forcing A Roundtrip

Tutorial - Part 2: Enumerating Objects | Index | Tutorial - Part 4: Playing A Tone

In this tutorial we show how to force a roundtrip to the server to make sure an action completed.

We'll change our example from Tutorial 2 slightly and add the extra code to implement the roundtrip.

Let's take the following small method first:

struct roundtrip_data {
int pending;
struct pw_main_loop *loop;
};
static void on_core_done(void *data, uint32_t id, int seq)
{
struct roundtrip_data *d = data;
if (id == PW_ID_CORE && seq == d->pending)
pw_main_loop_quit(d->loop);
}
static void roundtrip(struct pw_core *core, struct pw_main_loop *loop)
{
static const struct pw_core_events core_events = {
PW_VERSION_CORE_EVENTS,
.done = on_core_done,
};
struct roundtrip_data d = { .loop = loop };
struct spa_hook core_listener;
int err;
pw_core_add_listener(core, &core_listener, &core_events, &d);
d.pending = pw_core_sync(core, PW_ID_CORE, 0);
if ((err = pw_main_loop_run(loop)) < 0)
printf("main_loop_run error:%d!\n", err);
spa_hook_remove(&core_listener);
}

Let's take a look at what this method does.

struct spa_hook core_listener;
pw_core_add_listener(core, &core_listener, &core_events, &d);
pw_core_add_listener
#define pw_core_add_listener(c,...)
Definition core.h:384
spa_hook
A hook, contains the structure with functions and the data passed to the functions.
Definition hook.h:350

First of all we add a listener for the events of the core object. We are only interested in the `done` event in this tutorial. This is the event handler:

static void on_core_done(void *data, uint32_t id, int seq)
{
struct roundtrip_data *d = data;
if (id == PW_ID_CORE && seq == d->pending)
pw_main_loop_quit(d->loop);
}
PW_ID_CORE
#define PW_ID_CORE
default ID for the core object after connect
Definition core.h:62
pw_main_loop_quit
int pw_main_loop_quit(struct pw_main_loop *loop)
Quit a main loop.
Definition main-loop.c:108

When the done event is received for an object with id `PW_ID_CORE` and a certain sequence number `seq`, this function will call `pw_main_loop_quit()`.

Next we do:

d.pending = pw_core_sync(core, PW_ID_CORE, 0);
pw_core_sync
#define pw_core_sync(c,...)
Do server roundtrip.
Definition core.h:390

This triggers the `sync` method on the core object with id `PW_ID_CORE` and sequence number 0.

Because this is a method on a proxy object, it will be executed asynchronously and the return value will reflect this. PipeWire uses the return values of the underlying SPA (Simple Plugin API) helper objects (See also SPA Design ).

Because all messages on the PipeWire server are handled sequentially, the sync method will be executed after all previous methods are completed. The PipeWire server will emit a `done` event with the same ID and the return value of the original `pw_core_sync()` method in the sequence number.

We then run the mainloop to send the messages to the server and receive the events:

pw_main_loop_run(loop);
pw_main_loop_run
int pw_main_loop_run(struct pw_main_loop *loop)
Run a main loop.
Definition main-loop.c:122

When we get the done event, we can compare it to the sync method and then we know that we did a complete roundtrip and there are no more pending methods on the server. We can quit the mainloop and remove the listener:

spa_hook_remove(&core_listener);
spa_hook_remove
static void spa_hook_remove(struct spa_hook *hook)
Remove a hook.
Definition hook.h:391

If we add this roundtrip method to our code and call it instead of the `pw_main_loop_run()` we will exit the program after all previous methods are finished. This means that the `pw_core_get_registry()` call completed and thus that we also received all events for the globals on the server.

#include <pipewire/pipewire.h>
/* [roundtrip] */
struct roundtrip_data {
int pending;
struct pw_main_loop *loop;
};
static void on_core_done(void *data, uint32_t id, int seq)
{
struct roundtrip_data *d = data;
if (id == PW_ID_CORE && seq == d->pending)
pw_main_loop_quit(d->loop);
}
static void roundtrip(struct pw_core *core, struct pw_main_loop *loop)
{
static const struct pw_core_events core_events = {
PW_VERSION_CORE_EVENTS,
.done = on_core_done,
};
struct roundtrip_data d = { .loop = loop };
struct spa_hook core_listener;
int err;
pw_core_add_listener(core, &core_listener, &core_events, &d);
d.pending = pw_core_sync(core, PW_ID_CORE, 0);
if ((err = pw_main_loop_run(loop)) < 0)
printf("main_loop_run error:%d!\n", err);
spa_hook_remove(&core_listener);
}
/* [roundtrip] */
static void registry_event_global(void *data, uint32_t id,
uint32_t permissions, const char *type, uint32_t version,
const struct spa_dict *props)
{
printf("object: id:%u type:%s/%d\n", id, type, version);
}
static const struct pw_registry_events registry_events = {
PW_VERSION_REGISTRY_EVENTS,
.global = registry_event_global,
};
int main(int argc, char *argv[])
{
struct pw_main_loop *loop;
struct pw_context *context;
struct pw_core *core;
struct pw_registry *registry;
struct spa_hook registry_listener;
pw_init(&argc, &argv);
loop = pw_main_loop_new(NULL /* properties */);
context = pw_context_new(pw_main_loop_get_loop(loop),
NULL /* properties */,
0 /* user_data size */);
core = pw_context_connect(context,
NULL /* properties */,
0 /* user_data size */);
registry = pw_core_get_registry(core, PW_VERSION_REGISTRY,
0 /* user_data size */);
pw_registry_add_listener(registry, &registry_listener,
&registry_events, NULL);
roundtrip(core, loop);
pw_proxy_destroy((struct pw_proxy*)registry);
pw_core_disconnect(core);
pw_context_destroy(context);
pw_main_loop_destroy(loop);
return 0;
}

To compile the simple test application, copy it into a tutorial3.c file and use:

        gcc -Wall tutorial3.c -o tutorial3 $(pkg-config --cflags --libs libpipewire-0.3)

Now that our program completes, we can take a look at how we can destroy the objects we created. Let's destroy each of them in reverse order that we created them:

pw_proxy_destroy((struct pw_proxy*)registry);
pw_proxy_destroy
void pw_proxy_destroy(struct pw_proxy *proxy)
destroy a proxy
Definition proxy.c:209
pw_proxy

The registry is a proxy and can be destroyed with the generic proxy destroy method. After destroying the object, you should not use it anymore. It is an error to destroy an object more than once.

We can disconnect from the server with:

pw_core_disconnect(core);
pw_core_disconnect
int pw_core_disconnect(struct pw_core *core)
disconnect and destroy a core
Definition core.c:481

This will also destroy the core proxy object and will remove the proxies that might have been created on this connection.

We can finally destroy our context and mainloop to conclude this tutorial:

pw_context_destroy(context);
pw_main_loop_destroy(loop);
pw_context_destroy
void pw_context_destroy(struct pw_context *context)
destroy a context object, all resources except the main_loop will be destroyed
Definition context.c:529
pw_main_loop_destroy
void pw_main_loop_destroy(struct pw_main_loop *loop)
Destroy a loop.
Definition main-loop.c:73

Tutorial - Part 2: Enumerating Objects | Index | Tutorial - Part 4: Playing A Tone