Re: Using radio time signal for syncronization

Thank you Miroslav. I haven’t tried the alsa-oss package yet. Admittedly I much prefer using Chrony over ntpd :)

I will let you know if and when I have a good application. It may take a long while!

Sviatoslav

On Wed, Jan 8, 2025 at 03:21, Miroslav Lichvar <[[email protected]](mailto:On Wed, Jan 8, 2025 at 03:21, Miroslav Lichvar <<a href=)> wrote:

> On Tue, Jan 07, 2025 at 02:49:52PM +0000, Sviatoslav Feshchenko wrote:
>> I might take Miroslav's suggestion and port the ntpd audio code.
>> This would be a hobby project, so I am not looking for the easiest
>> porting solution. I would also want the code to last and be relevant
>> for the longest amount of time possible, so I would probably write
>> directly for ALSA rather than pipewire, to minimize the risk of
>> obsolescence. I wouldn't use the SOCK wrapper ntp-refclock in this
>> case either, and instead write a standalone application (somewhat
>> along the lines of gpsd), which would provide the SOCK connection.
>> What are your thoughts on this approach?
>
> That sounds like a lot of work, but of course it's your time :). I'd
> just submit a patch adding support for alsa to the ntp project.
> Looking at the ./libntp/audio.c file, it shouldn't be that difficult.
>
> alsa provides an alsa-oss package providing some OSS compatibility.
> You could start ntpd/ntp-refclock with the aoss utility. Have you
> tried that?
>
>> If I am ever successful and
>> it works well, would Miroslav be willing to include a blurb about
>> the existence of this application in chrony documentation for
>> chrony.conf SOCK driver, which currently only mentions gpsd as one
>> application that supports the SOCK protocol?
>
> I'd certainly add it to the "Useful links" page on the chrony website.
>
> --
> Miroslav Lichvar
>
> --
> To unsubscribe email [email protected]
> with "unsubscribe" in the subject.
> For help email [email protected]
> with "help" in the subject.
> Trouble? Email [email protected].