playout-gateway: consider making Multi-Threading and Multi-Threaded Timeline Resolving default to on about sofie-core HOT 2 OPEN

Yeah, this is a good point. Currently, our Peripheral Device API has no concept of default settings, and I think that's the reason everything is default-off - because it's undefined. I guess the solution would be to come up with a way of having some default settings - the question is, how should they be handled? I suppose one way of doing it would be to allow the peripheral device to expose a defaultConfig object, that would be valid for the configManifest schema, and then later that would be copied over to the settings property if this is the first connection of the device.

I don't think anything more can be done, without the Peripheral Device itself holding some sort of migration logic to migrate the settings object. The best we could do would be to provide some warning if the current settings do not match the new manifest. I also don't think we could do anything if the defaults change. I don't think an infrastructure as complicated as the one we have for ShowStyles or Blueprint configs would be viable here.

from sofie-core.

We are populating default values for playout-gateway subdevices https://github.com/nrkno/sofie-core/blob/release50/packages/playout-gateway/src/tsrHandler.ts#L655-L661
And we do provide a utility to parse the defaults from the json-schema https://github.com/nrkno/sofie-core/blob/release50/packages/shared-lib/src/lib/JSONSchemaUtil.ts#L49.

So it wouldn't be too hard to on the fly do a deep-merge of the db config on top of the defaults. I don't know whether it would be better to do this in core of the gateway itself. Im not sure if we need to worry about saving the defaults into the database, as the ui may already present the defaults as defined in the schema when it encounters an undefined

from sofie-core.