7890
7890
It's really up to you :)) - there are no code guidelines (...). It should be consistent in some way for new files, for existing files the strategy is to...
@chris-kuhr I've checked out your branch and indeed there is no single tab left in any of the avt/* .h or .c files, very well. I'm _nitpicking_ on more formal...
For reference: https://lac.linuxaudio.org/2019/doc/kuhr.pdf @chris-kuhr do you know if there is the video of your presentation archived somewhere? I missed it and it would be interesting to see.
It's good to test-drive this. These things are important information for anybody else to try.
@ahellquist thank you for the first test. I take from this that AVB is somewhat tricky and that a few other units must be in place to successfully use this...
I'm tempted to try this out. @chris-kuhr what are the minimal hardware requirements? From what I read it's -a compatible NIC such as the i210 -a media clock talker on...
Thanks, that helped. It's like a word clock coming in via network interface ~ Jack client running in AVB enabled jack instances distributed on the network could then for instance...
Naively asked, could jack be a media clock talker? Let's say it would provide the clock from the attached audio hardware interface to the network. To have multiple jack instances...
@DeviLaxmii thanks for the patch. Can you outline a scenario in which jackd can benefit from the patch? IIUC it's allowing for a better handling of jackd behavior when it...
Thanks for the explanation @DeviLaxmii Sounds reasonable to inform jackd when alsa thread terminated unexpectedly.