We're not yet saving the hex colors as that will break in older patches.
But we do print out warning messages in this interim period and will
save the hex colors at a later date. Once that change is made, all the
interim versions will be able to read the new format

Vanilla commit 94d59de44ea23aa084596d1ba2050d3883511ec3

vanilla commit 853967de05253eaba8bf153450d573e8b6067576

Vanilla commit ab4750bd39964efd5c9a32fdaf9fb300d0d2f5d7

If a user added a device on the commandline, it's likely that they want
this device to be the default.

This allows Purr Data to work nicely inside a Flatpak sandbox, as we
can use `-alsaadd pulse` to enable audio output to PulseAudio by
default, with direct hardware access still an option.

This could lead to an assert failure inside ALSA if the output device
wasn't open and we tried to configure it anyway.

As the comment above the alsa_checkiosync() function suggests, there's
no sync to be done if we only have an input or an output.

The (input) and (output) markers were missing in some cases, and
incorrect in others.