On 13/03/2021 13:11, The Natural Philosopher wrote:
For people who just want to listen and not go through the faff of 3rdAny chance of a copy without the word wrapping?
party programs or hardware
this is stripped from my updated media server code but you can work out
what's up....
Here ya go...[]
(A quick reformat using a utility of mine... (:-))
On 14/03/2021 19:35, Axel Berger wrote:
Cursitor Doom wrote:I sympathise.
Hard to believe anyone with an internet radio would still want to
listen to the shite the BBC has to offer,
Come to Germany and you'll see how enormously grateful I am for the BBC.
Whatever do you have in mind, that could be even comparable to them?
In continental Europe on FM the only classical music radio was
re-broadcasts for Radio 3 concerts and nothing in Germany
I used to listen on longwave after the demise of the British forces'Indeed
BFBS. You can't think what a great change podcasts and streeams have
made to my listening.
In article <s2lor1$5qt$1@dont-email.me>, The Natural Philosopher <tnp@invalid.invalid> scribeth thus
On 14/03/2021 19:35, Axel Berger wrote:
Cursitor Doom wrote:I sympathise.
Hard to believe anyone with an internet radio would still want to
listen to the shite the BBC has to offer,
Come to Germany and you'll see how enormously grateful I am for the BBC. >>> Whatever do you have in mind, that could be even comparable to them?
In continental Europe on FM the only classical music radio was
re-broadcasts for Radio 3 concerts and nothing in Germany
I used to listen on longwave after the demise of the British forces'Indeed
BFBS. You can't think what a great change podcasts and streeams have
made to my listening.
Don't quite understand what your getting at here are you saying theres
no classic stations in Germany or ones worth listening to?
Still got Bayern Klassik?..
Https://www.br-klassik.de/programm/livestream/livestream-158.html
Let alone the excellent Czech D-Dur service from Prague:)
https://www.mujrozhlas.cz/zive/d-dur?autopla
Don't quite understand what your getting at here are you saying theres
no classic stations in Germany or ones worth listening to?
tony sayer wrote:
Don't quite understand what your getting at here are you saying theres
no classic stations in Germany or ones worth listening to?
Not sure who "you" is in your answer. In this thread I'm exclusively
speaking about radio, i.e. the spoken word, while several others are
going on about music.
Music, specifically classic music is by definition old
anywhere like a deceased relative's record collection. Radio is valuable
for its currently relevant content and must be received now. That's
where differences in quality come in. Anyone can put on records.
Axel Berger <Spam@berger-odenthal.de> wrote:
Not sure who "you" is in your answer. In this thread I'm exclusively
speaking about radio, i.e. the spoken word, while several others are
going on about music.
I don't know about usage in Germany, but in (IME) in
the UK, Australia, and NZ "radio" might mean any kind
of radio broadcast of audio, whether of speech, music,
weird experimental sound sculptures, etc; or combinations
thereof.
#Paul
On 23-03-2021 10:04, The Natural Philosopher wrote:
On 22/03/2021 20:15, #Paul wrote:
Axel Berger <Spam@berger-odenthal.de> wrote:
Not sure who "you" is in your answer. In this thread I'm exclusively
speaking about radio, i.e. the spoken word, while several others are
going on about music.
I don't know about usage in Germany, but in (IME) in
the UK, Australia, and NZ "radio" might mean any kind
of radio broadcast of audio, whether of speech, music,
weird experimental sound sculptures, etc; or combinations
thereof.
Radio (or wireless!)Â in the UK effectively means 'sound transmission
by radio waves'
In German, too. Radio or Hörfunk is both music and talk radio. Maybe
it's different for him locally, or maybe he invented his own meaning.
Also, it is known to happen that German people, too, get their music
from sources other than dead relatives.
On 22/03/2021 20:15, #Paul wrote:
Axel Berger <Spam@berger-odenthal.de> wrote:
Not sure who "you" is in your answer. In this thread I'm exclusively
speaking about radio, i.e. the spoken word, while several others are
going on about music.
I don't know about usage in Germany, but in (IME) in
the UK, Australia, and NZ "radio" might mean any kind
of radio broadcast of audio, whether of speech, music,
weird experimental sound sculptures, etc; or combinations
thereof.
Radio (or wireless!)Â in the UK effectively means 'sound transmission by radio waves'
Axel Berger <Spam@berger-odenthal.de> wrote:
Not sure who "you" is in your answer. In this thread I'm exclusively
speaking about radio, i.e. the spoken word, while several others are
going on about music.
I don't know about usage in Germany, but in (IME) in the UK, Australia,
and NZ "radio" might mean any kind of radio broadcast of audio, whether
of speech, music, weird experimental sound sculptures, etc; or
combinations thereof.
On 22/03/2021 20:15, #Paul wrote:
Axel Berger <Spam@berger-odenthal.de> wrote:Radio (or wireless!) in the UK effectively means 'sound transmission by radio waves'
Not sure who "you" is in your answer. In this thread I'm exclusively
speaking about radio, i.e. the spoken word, while several others are
going on about music.
I don't know about usage in Germany, but in (IME) in the UK, Australia,
and NZ "radio" might mean any kind of radio broadcast of audio, whether
of speech, music, weird experimental sound sculptures, etc; or
combinations thereof.
#Paul
If it's speech, it's colloquially known as 'talk radio'. Sometimes.
On Tue, 23 Mar 2021 09:04:16 +0000, The Natural Philosopher wrote:
On 22/03/2021 20:15, #Paul wrote:
Axel Berger <Spam@berger-odenthal.de> wrote:Radio (or wireless!) in the UK effectively means 'sound transmission by
Not sure who "you" is in your answer. In this thread I'm exclusively
speaking about radio, i.e. the spoken word, while several others are
going on about music.
I don't know about usage in Germany, but in (IME) in the UK, Australia,
and NZ "radio" might mean any kind of radio broadcast of audio, whether
of speech, music, weird experimental sound sculptures, etc; or
combinations thereof.
#Paul
radio waves'
If it's speech, it's colloquially known as 'talk radio'. Sometimes.
We need a better description than 'talk radio': there is far too much
crap and assorted political raving around to lump it all together under
that the same heading as Radio 4 or WOR.
At least when one of the political ravers is called a 'shock jock' you
know what to expect.
But it did wake me up to the steel guitar, which although I never learnt
to play one, I still love to hear played well...
https://www.youtube.com/watch?v=4naoG2z4Zcc
On Tue, 23 Mar 2021 09:58:12 +0000, The Natural Philosopher wrote:
But it did wake me up to the steel guitar, which although I never learntThe best steel guitar player I've seen live is B J Cole, whi has been
to play one, I still love to hear played well...
https://www.youtube.com/watch?v=4naoG2z4Zcc
known to tour with Hank Wangford & the Lost Cowboys. I don't normally
listen to C&W, but I'll go to one of their gigs any time.
On 23/03/2021 12:30, Martin Gregorie wrote:
On Tue, 23 Mar 2021 09:58:12 +0000, The Natural Philosopher wrote:Ah - Hank Wangford, yes, great boys and girls!
But it did wake me up to the steel guitar, which although I neverThe best steel guitar player I've seen live is B J Cole, whi has been
learnt to play one, I still love to hear played well...
https://www.youtube.com/watch?v=4naoG2z4Zcc
known to tour with Hank Wangford & the Lost Cowboys. I don't normally
listen to C&W, but I'll go to one of their gigs any time.
Ah they gigging this year?
but in (IME) in
the UK, Australia, and NZ "radio" might mean any kind
of radio broadcast of audio, whether of speech, music,
weird experimental sound sculptures, etc; or combinations
thereof.
specifically classic music is by definition old
When I listen to a Philip Glass piano piece, I'm listening to classical
music IMHO.
#Paul wrote:
but in (IME) in
the UK, Australia, and NZ "radio" might mean any kind
of radio broadcast of audio, whether of speech, music,
weird experimental sound sculptures, etc; or combinations
thereof.
Same here of course. But this thread began with the topic of quality at
the top. Of course most stations and all the local ones offer little
more than a sound background fpr the advertisements. But BBC, especially Radio 4 and to a far lesser degree some German programs are different.
On Tue, 23 Mar 2021 15:12:59 +0000, Stephen Pelc wrote:
When I listen to a Philip Glass piano piece, I'm listening to classical
music IMHO.
One of the best orchestral concerts I've been to was at Cambridge Corn Exchange in 2000, when the Britten Sinfonia played a concert of pieces by John Adams and Frank Zappa.
Definitely a good fit in the Contemporary Classical category.
On 21/03/2021 14:02, tony sayer wrote:
The Natural Philosopher <tnp@invalid.invalid> scribeth thusNo, I am saying that I found none on FM radio while driving from
On 14/03/2021 19:35, Axel Berger wrote:
Cursitor Doom wrote:I sympathise. In continental Europe on FM the only classical
Hard to believe anyone with an internet radio would still
want to listen to the shite the BBC has to offer,
Come to Germany and you'll see how enormously grateful I am for
the BBC. Whatever do you have in mind, that could be even
comparable to them?
music radio was re-broadcasts for Radio 3 concerts and nothing in
Germany
Don't quite understand what your getting at here are you saying
theres no classic stations in Germany or ones worth listening to?
Dunquerque to Koblenz..after Aachen.
In article <s2kgai$nef$1@dont-email.me>,
Brian Gaff (Sofa) says...
Its going to be a pain
till all the aggregators catch up particularly with the bbc ones.
Airable has done so.
https://www.airablenow.com/airable/radio/
The 320k BBC stream now identifies as BBC Radio 3 HD
This on my Yamaha AVR which uses Airable after a change from VTuner with
a firmware update a couple of years ago
Internet radio lags behind FM by a few seconds. Switching from FM on the
last Pip of the time signal I catch the last couple of pips from the
net.
Internet radio lags behind FM by a few seconds. Switching from FM on the
last Pip of the time signal I catch the last couple of pips from the
net.
"Rink" <rink.hof.haalditmaarweg@planet.nl> wrote in message news:sd73u5$q4t$1@dont-email.me...
Internet radio lags behind FM by a few seconds. Switching from FM on
the last Pip of the time signal I catch the last couple of pips from
the net.
I wonder whether anyone has considered running studios a couple of seconds early (so when they play the pips at 12:00:00 it's actually 11:59:58) and delaying FM by the same amount that DAB is inherently delayed, to keep them in sync ;-)
For a station that only plays recorded music and doesn't have any second-accurate timechecks, they don't even need to run the studio early.
Or do different radios have different amounts of buffering of the received data before playing it as an analogue feed to the speaker?
delaying FM by the same amount that DAB is inherently delayed,Sadly, that is not a constant and depends largely on te recieving
I wonder whether anyone has considered running studios a couple of seconds early (so when they play the pips at 12:00:00 it's actually 11:59:58) and delaying FM by the same amount that DAB is inherently delayed, to keep them in sync;-)
On 20/07/2021 19:51, NY wrote:
I wonder whether anyone has considered running studios a couple of
seconds
early (so when they play the pips at 12:00:00 it's actually 11:59:58) and
delaying FM by the same amount that DAB is inherently delayed, to keep
them
in sync;-)
What is the point when both VHF FM and DAB have the time transmitted all
the time and displayed on the radio. I would think both of these are
quite accurate enough for most people most of the time.
Anyone needing precision time is going to be using something else.
Or do different radios have different amounts of buffering of the received data before playing it as an analogue feed to the speaker?
I don't have any radio that can display the time, even if it is transmitted >as part of RDS. My car radio is the only one that can handle RDS, and that >doesn't set the car's clock - you always have to set it manually , and there >isn't even a "0 or +1 hour" GMT/BST setting to keep the minutes and seconds >the same and only change the hour. I *think* my wife's Honda (dating from >2015) also needs to have the time and daylight savings set manually and it >doesn't set/correct it from the FM RDS or the DAB radio.
The only radios I have are a tuner from a stereo system I bought in 1986,
and my wife's all-in-one music centre that is probably from the 1990s. I use
It might be feasible to do something like rate-adaptive buffering - for example start the stream at a low resolution while you're buffering in the background, and then upgrade the resolution when there's enough buffered. I don't know if anyone does that already.
If one needs accurate time on an R-Pi, either a network connection to
NTP servers, a battery-backed RTC module (though those do tend to lose a
bit of time and need to be resynced to another time source at periods), or
a GPS time source.
"Dennis Lee Bieber" <wlfraed@ix.netcom.com> wrote in message news:mn8gfg9ivl3ca3d12llf2bs4ehv4iulh4f@4ax.com...
If one needs accurate time on an R-Pi, either a network connection to
NTP servers, a battery-backed RTC module (though those do tend to lose
a bit of time and need to be resynced to another time source at
periods), or a GPS time source.
My Pi's are connected to my LAN, so they get the benefit of NTP resyncs
every so often. The problem comes when a Pi reboots and then can't see
the LAN for a while - eg because everything has come back after a power
cut and the router is taking ages to connect to the internet. In that
case, the Pi can be running for a significant period of time with a slightly-wrong time.
My Pi's are connected to my LAN, so they get the benefit of NTP resyncs
every so often. The problem comes when a Pi reboots and then can't see the >LAN for a while - eg because everything has come back after a power cut and >the router is taking ages to connect to the internet. In that case, the Pi >can be running for a significant period of time with a slightly-wrong time.
I notice this on the Pi which logs data from my weather station: I've seen >occasions when the graphs of temperature, wind speed etc have a section
which goes back in time and then suddenly jumps forwards in time again once >NTP can reset the clock to the correct time. Usually the temporary error is >only 30 minutes or so - enough to create an "interesting" blip (*) but not >enough to go back to before the beginning of the graph (I plot the last 48 >hours' data).
What is the accuracy of the clock on the Pi if it initially syncs with an
NTP source but then loses network contact while remaining booted up? What is >the default resync period for Raspberry PiOS - is it every 24 hours or is it >more/less frequent that that? My old (Windows 7) laptop had a very poor RTC >which lost a lot of time - several minutes over the default resync time of >Windows - so I found the registry keys to make it resync more frequently - >probably once per day. My new Windows 10 laptop never seems to be out by
more than a few seconds, so either its RTC is more accurate or it resyncs >more often.
What is the accuracy of the clock on the Pi if it initially syncs with an
NTP source but then loses network contact while remaining booted up? What is the default resync period for Raspberry PiOS - is it every 24 hours or is it more/less frequent that that? My old (Windows 7) laptop had a very poor RTC which lost a lot of time - several minutes over the default resync time of Windows - so I found the registry keys to make it resync more frequently - probably once per day. My new Windows 10 laptop never seems to be out by
more than a few seconds, so either its RTC is more accurate or it resyncs more often.
On 21/07/2021 19:53, NY wrote:
What is the accuracy of the clock on the Pi if it initially syncs with
an NTP source but then loses network contact while remaining booted up?
What is the default resync period for Raspberry PiOS - is it every 24
hours or is it more/less frequent that that? My old (Windows 7) laptop
had a very poor RTC which lost a lot of time - several minutes over the
default resync time of Windows - so I found the registry keys to make
it resync more frequently -
probably once per day. My new Windows 10 laptop never seems to be out
by more than a few seconds, so either its RTC is more accurate or it
resyncs more often.
I would recommend installing NTP which appears to be missing from the
recent RPi OS releases.
On 21/07/2021 19:53, NY wrote:
What is the accuracy of the clock on the Pi if it initially syncs with an
NTP source but then loses network contact while remaining booted up? What is >> the default resync period for Raspberry PiOS - is it every 24 hours or is it >> more/less frequent that that? My old (Windows 7) laptop had a very poor RTC >> which lost a lot of time - several minutes over the default resync time of >> Windows - so I found the registry keys to make it resync more frequently - >> probably once per day. My new Windows 10 laptop never seems to be out by
more than a few seconds, so either its RTC is more accurate or it resyncs
more often.
I would recommend installing NTP which appears to be missing from the recent RPi OS releases.
I would recommend installing NTP which appears to be missing from the
recent RPi OS releases.
On 20/07/2021 19:51, NY wrote:
I wonder whether anyone has considered running studios a couple of seconds early (so when they play the pips at 12:00:00 it's actually 11:59:58) and delaying FM by the same amount that DAB is inherently delayed, to keep them in sync;-)
What is the point when both VHF FM and DAB have the time transmitted all
the time and displayed on the radio. I would think both of these are
quite accurate enough for most people most of the time.
Anyone needing precision time is going to be using something else.
On Thu, 22 Jul 2021 07:00:40 +0100, David Taylor wrote:
On 21/07/2021 19:53, NY wrote:
What is the accuracy of the clock on the Pi if it initially syncs with
an NTP source but then loses network contact while remaining booted up?
What is the default resync period for Raspberry PiOS - is it every 24
hours or is it more/less frequent that that? My old (Windows 7) laptop
had a very poor RTC which lost a lot of time - several minutes over the
default resync time of Windows - so I found the registry keys to make
it resync more frequently -
probably once per day. My new Windows 10 laptop never seems to be out
by more than a few seconds, so either its RTC is more accurate or it
resyncs more often.
I would recommend installing NTP which appears to be missing from the
recent RPi OS releases.
The whole point is that OP is doing that, but on boot, sync to get a
valid time is overtaken by other stuff starting (and getting the wrong
time).
On 22/07/2021 07:00 am, David Taylor wrote:
I would recommend installing NTP which appears to be missing from the
recent RPi OS releases.
Check timedatectl (a systemd service)
On Thu, 22 Jul 2021 11:34:22 +0100, Chris Elvidge wrote:
On 22/07/2021 07:00 am, David Taylor wrote:
I would recommend installing NTP which appears to be missing from the
recent RPi OS releases.
Check timedatectl (a systemd service)
It may not be installed if you've had your RPI for some time and have
done in-situ upgrades as successive Raspbian versions have been released.
I have an early Pi 2B (the 512MB version) successively upgraded from
Wheezy to Buster. It does not have the timedatectl service installed.
The whole point is that OP is doing that, but on boot, sync to get a
valid time is overtaken by other stuff starting (and getting the wrong
time).
That's because of the switch to systemd. An ntp (-like?) service is still installed. Its interface is "timedatectl" which gives a status overview.
See man timedatectl.
It seems to sync often enough by itself that my Pi4 (without an rtc) which
is always on and which I don't monitor is accurate to within about a second compared manually to this iOS device from which I just logged in. So, I
don't think it's a good idea to install the ntp service on top of that; not without first disabling this new stuff.
On 22/07/2021 09:48, Bob Eager wrote:
The whole point is that OP is doing that, but on boot, sync to get a
valid time is overtaken by other stuff starting (and getting the wrong
time).
Thanks, Bob. Perhaps simply delay the other stuff by 30 seconds or so
might be a simple solution?
That's the thing. I haven't had any of the gloom and doom that a lot
of people predicted for the shift to systemd*except* that it can be extremely confusing for me to figure out how to configure the small
number of things that I want to customize.
Trying to change the time in the morning that cron.daily (weekly,
monthly) runs was an absolute pig, and I found the documentation about
where to put the customization file tricky to follow.
Trying to change the time in the morning that cron.daily (weekly,
monthly) runs was an absolute pig, and I found the documentation about
where to put the customization file tricky to follow.
Indeed. I thought systemd was supposed to solve all that (hollow laugh,
glad I don't have to use it).
On 22/07/2021 09:32, A. Dumas wrote:
That's because of the switch to systemd. An ntp (-like?) service is still
installed. Its interface is "timedatectl" which gives a status overview.
See man timedatectl.
It seems to sync often enough by itself that my Pi4 (without an rtc) which >> is always on and which I don't monitor is accurate to within about a second >> compared manually to this iOS device from which I just logged in. So, I
don't think it's a good idea to install the ntp service on top of that; not >> without first disabling this new stuff.
A "sudo apt-get install ntp" fixes the lack of NTP on all my RPi cards. No problems at all even with the latest OS. Personally I prefer to trust the reference NTP version rather than some other version, and it has the advantage
that I can manage it in the same way as NTP on Windows and other Linux systems.
Here I see accuracies well under a millisecond even when syncing over Wi-Fi - e.g. a Raspberry Pi 400:
https://www.satsignal.eu/mrtg/raspi24_ntp-b.html
and when you activate the GPS/PPS option, well under 10 microseconds even with
a Raspberry Pi 1B:
https://www.satsignal.eu/mrtg/raspi1_ntp.html
Here's a Raspberry Pi 4 with the Uputronics GPS/PPS/RTC HAT:
https://www.satsignal.eu/mrtg/raspi25_ntp.html
The antenna is a mag mount puck, indoors, on top of some mains trunking. Something like that can be your stratum-1 source so many local clients.
I'm comparing file timestamps with another system in the Netherlands and having
sub-second accuracy makes the comparison much more certain. I appreciate that
your requirements may be less stringent, but you can have a lot of fun with NTP
and GPS!
On 22/07/2021 15:17, Adam Funk wrote:
That's the thing. I haven't had any of the gloom and doom that a lot
of people predicted for the shift to systemd*except* that it can be
extremely confusing for me to figure out how to configure the small
number of things that I want to customize.
Trying to change the time in the morning that cron.daily (weekly,
monthly) runs was an absolute pig, and I found the documentation about
where to put the customization file tricky to follow.
There seem to be a number of people who are strongly against it, but it's not been an issue here.
For scheduled stuff I simply use "crontab -e" (IIRC) and it seems to work, but
that's for boot-time and daily tasks. No customisation file required - as far
as I know.
That's the thing. I haven't had any of the gloom and doom that a lot
of people predicted for the shift to systemd*except* that it can be extremely confusing for me to figure out how to configure the small
number of things that I want to customize.
Trying to change the time in the morning that cron.daily (weekly,
monthly) runs was an absolute pig, and I found the documentation about
where to put the customization file tricky to follow.
On 22/07/2021 03:51 pm, David Taylor wrote:
Trying to change the time in the morning that cron.daily (weekly,
monthly) runs was an absolute pig, and I found the documentation about
where to put the customization file tricky to follow.
How is changing the time in /etc/crontab difficult?
On 22/07/2021 09:32, A. Dumas wrote:
That's because of the switch to systemd. An ntp (-like?) service is still
installed. Its interface is "timedatectl" which gives a status overview.
See man timedatectl.
It seems to sync often enough by itself that my Pi4 (without an rtc) which >> is always on and which I don't monitor is accurate to within about a second >> compared manually to this iOS device from which I just logged in. So, I
don't think it's a good idea to install the ntp service on top of that; not >> without first disabling this new stuff.
A "sudo apt-get install ntp" fixes the lack of NTP on all my RPi cards. No problems at all even with the latest OS. Personally I prefer to trust the reference NTP version rather than some other version, and it has the advantage
that I can manage it in the same way as NTP on Windows and other Linux systems.
Here I see accuracies well under a millisecond even when syncing over Wi-Fi - e.g. a Raspberry Pi 400:
https://www.satsignal.eu/mrtg/raspi24_ntp-b.html
and when you activate the GPS/PPS option, well under 10 microseconds even with
a Raspberry Pi 1B:
https://www.satsignal.eu/mrtg/raspi1_ntp.html
Here's a Raspberry Pi 4 with the Uputronics GPS/PPS/RTC HAT:
https://www.satsignal.eu/mrtg/raspi25_ntp.html
The antenna is a mag mount puck, indoors, on top of some mains trunking. Something like that can be your stratum-1 source so many local clients.
I'm comparing file timestamps with another system in the Netherlands and having
sub-second accuracy makes the comparison much more certain. I appreciate that
your requirements may be less stringent, but you can have a lot of fun with NTP
and GPS!
On 22/07/2021 09:32, A. Dumas wrote:
That's because of the switch to systemd. An ntp (-like?) service is still
installed. Its interface is "timedatectl" which gives a status overview.
See man timedatectl.
It seems to sync often enough by itself that my Pi4 (without an rtc) which >> is always on and which I don't monitor is accurate to within about a second >> compared manually to this iOS device from which I just logged in. So, I
don't think it's a good idea to install the ntp service on top of that; not >> without first disabling this new stuff.
A "sudo apt-get install ntp" fixes the lack of NTP on all my RPi cards. No problems at all even with the latest OS. Personally I prefer to trust the reference NTP version rather than some other version, and it has the advantage
that I can manage it in the same way as NTP on Windows and other Linux systems.
Here I see accuracies well under a millisecond even when syncing over Wi-Fi - e.g. a Raspberry Pi 400:
https://www.satsignal.eu/mrtg/raspi24_ntp-b.html
and when you activate the GPS/PPS option, well under 10 microseconds even with
a Raspberry Pi 1B:
https://www.satsignal.eu/mrtg/raspi1_ntp.html
Here's a Raspberry Pi 4 with the Uputronics GPS/PPS/RTC HAT:
https://www.satsignal.eu/mrtg/raspi25_ntp.html
The antenna is a mag mount puck, indoors, on top of some mains trunking. Something like that can be your stratum-1 source so many local clients.
I'm comparing file timestamps with another system in the Netherlands and having
sub-second accuracy makes the comparison much more certain. I appreciate that
your requirements may be less stringent, but you can have a lot of fun with NTP
and GPS!
On 22/07/2021 01:56 pm, Martin Gregorie wrote:
On Thu, 22 Jul 2021 11:34:22 +0100, Chris Elvidge wrote:systemd-timesyncd.service and/or systemd-timedated.service?
On 22/07/2021 07:00 am, David Taylor wrote:
I would recommend installing NTP which appears to be missing from the
recent RPi OS releases.
Check timedatectl (a systemd service)
It may not be installed if you've had your RPI for some time and have
done in-situ upgrades as successive Raspbian versions have been
released.
I have an early Pi 2B (the 512MB version) successively upgraded from
Wheezy to Buster. It does not have the timedatectl service installed.
On Thu, 22 Jul 2021 14:38:12 +0100, Chris Elvidge wrote:
systemd-timesyncd.service and/or systemd-timedated.service?
Both present: systemd-timesyncd.service enabled but dead
systemd-timedated.service enabled but dead
I remember installing ntpd when I first got the RPi - its still there,
still running and within a second or so of the T440 I'm writing this on.
On Thu, 22 Jul 2021 20:53:36 +0000, A. Dumas wrote:
They may have been disabled when you installed ntpd, or never enabled
when ntpd was detected? That seems sane/logical, anyway. No need to have
two time sync daemons running simultaneously.
Unlikely: ntpd was on the RPi and running long before systemd arrived on
it. Its far more likely that those services crawled onto the machine when systemd first slung in through the door and, because I never needed to
use them they've just sat there
Martin Gregorie <martin@mydomain.invalid> wrote:
On Thu, 22 Jul 2021 14:38:12 +0100, Chris Elvidge wrote:
systemd-timesyncd.service and/or systemd-timedated.service?
Both present: systemd-timesyncd.service enabled but dead
systemd-timedated.service enabled but dead
I remember installing ntpd when I first got the RPi - its still there,
still running and within a second or so of the T440 I'm writing this
on.
They may have been disabled when you installed ntpd, or never enabled
when ntpd was detected? That seems sane/logical, anyway. No need to have
two time sync daemons running simultaneously.
Er, my "about a second" was from me simply glancing at two devices. I'm
sure the actual accuracy is the same as for reference ntp, because it runs this:https://wiki.archlinux.org/title/systemd-timesyncd
"Rink" <rink.hof.haalditmaarweg@planet.nl> wrote in message news:sd73u5$q4t$1@dont-email.me...
Internet radio lags behind FM by a few seconds. Switching from FM on the >>> last Pip of the time signal I catch the last couple of pips from the
net.
I wonder whether anyone has considered running studios a couple of
seconds early (so when they play the pips at 12:00:00 it's actually
11:59:58) and delaying FM by the same amount that DAB is inherently
delayed, to keep them in sync ;-)
For a station that only plays recorded music and doesn't have any second-accurate timechecks, they don't even need to run the studio early.
Or do different radios have different amounts of buffering of the
received data before playing it as an analogue feed to the speaker?
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 418 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 23:01:26 |
| Calls: | 8,804 |
| Calls today: | 2 |
| Files: | 13,304 |
| Messages: | 5,970,093 |