regression (node-driver): using a PTP clock as clock doesn't work anymore
As part of #3217 I'm in the process of adding a way to specify a PTP clock by providing the network interface name. After rebasing those changes on master the config I had working with 0.3.79 broke. The timestamps are not correct anymore and it seems like the clock isn't used at all.
My clock config:
context.objects = [
{ factory = spa-node-factory
args = {
factory.name = support.node.driver
node.name = PTP0-Driver
node.group = pipewire.ptp0
priority.driver = 40000
clock.name = "clock.system.ptp0"
clock.device = "/dev/ptp1"
clock.min-quantum = 64
object.export = true
}
}
]
Bisection led to commit 8249fa3c which broke it.
Are there now any additional parameters I need to configure to 'allow' the clock to jump after initial sync?