2d • General discussion
Suggestion for M_dot_C
I've noticed several times when "time" becomes an issue. Things get changed and people get confused as to what time a thing is going to happen in their location.
Why don't you switch to 24 hour UTC time? That way everyone knows what time the event will be occurring even if they are traveling. People in fixed locations can simply learn their offset. Or they can simply type in...
"What time is it in [ my city ] at 17:30 UTC 11/15/2026? Most everyone's phone, tablet, computers are tied to UTC and they will get an exact time. Aviation is all tied to UTC/Zulu.
2026-09-28T16:52:00Z
Year-Month-Day(T=Time)Hour(in 24 format):Minute:Seconds(Zulu = tied directly to UTC:00:00)
But again any search engine can convert normal spoken words. So "The show starts at 13:00 ( 1PM ) UCT on October 2nd" works just fine. If you live on east coast USA that's 9AM EDT 10/02. If you live in Madrid it's 15:00 ( 3PM )11/02
When a contest ends "at midnight" it's much more easily understood and can not be improperly calculated if the contest ends at 23:59 UCT 10/01/2026.
It would simply eliminate all confusion even as time zones change through travel or seasonal standard vs daylight savings. Also it seems to me if you had an instructor in different time zone or a mentor call and one party or both need to quickly coordinate a time.
Anyway just a thought. If it saved everyone a couple minutes on all the varied communications, videos, etc., it would seem worth it in the long run.
2
3 comments
Suggestion for M_dot_C
skool.com/mastering
World's largest community to learn mixing and mastering. Built for self-recording artists who want professional quality at home.
Leaderboard (30-day)
1
+64
2
+55
3
+54
4
+44
5
+42
Powered by