<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font face="Calibri">You seem to be drifting off topic somewhat.
Perhaps you should start a new thread... "What is a programmer?"
if that's what you want to discuss?</font></p>
<p><font face="Calibri"><br>
</font></p>
<div class="moz-cite-prefix">On 19/03/2024 9:20 pm, René Schmitz
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:8e97f1d9-e3b6-417c-b998-cf8fa7f01bc3@schmitzbits.de">On
18.03.2024 09:42, Roman Sowa wrote:
<br>
<blockquote type="cite">
<br>
<br>
W dniu 2024-03-16 o 10:04, Spiros Makris pisze:
<br>
<blockquote type="cite">On Fri, 15 Mar 2024 at 17:47, Roman Sowa
via Synth-diy <<a class="moz-txt-link-abbreviated" href="mailto:synth-diy@synth-diy.org">synth-diy@synth-diy.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:synth-diy@synth-diy.org"><mailto:synth-diy@synth-diy.org></a>> wrote:
<br>
<br>
<br>
If I may just add - maybe it's just my impression, but I
think that new
<br>
generations of programmers educated today have absolutely
no idea how
<br>
microprocessor works.
<br>
<br>
<br>
That feels true, but we should keep in mind that "programmer"
has been a continuously expanding group of people, and you can
now be a programmer starting from a wild variety of
disciplines, most of which don't start from the bottom, as is
customary in electrical engineering and (sometimes) computer
science degrees. Most programs I know of have computers and
operating systems as a standard class, but microcontrollers
and embedded systems as an elective. That is, you can't become
an embedded programmer "by accident", unlike python, java and
others, which any STEM major will have some knowledge of.
<br>
</blockquote>
<br>
yes, that makes sense. Noone expects the java programmer to know
how computers work, because java is already created by people
who don't know that. And I bet the people commercially making
websites in WordPress are hired as "programmers".
<br>
I was thinking rather about programmers writing operating
systems like Windows
<br>
</blockquote>
<br>
<br>
The whole field has diversified and changed in the 40 odd years
since I wrote my first BASIC program. If you're writing business
or web applications you don't really need to know that much about
the processor in detail. Neither did you for BASIC.
<br>
<br>
You'd better understand the details of the business requirements
and how to get them implemented. (And as an addendum to my earlier
remark, it's these req's that actually eat many of the clock
cycles.)
<br>
<br>
Database applications are usually also far abstracted from machine
words. Speed is often I/O bound with network and drives or memory
being the bottleneck, so gaining a few ns with some processor
tricks doesn't give you much.
<br>
<br>
But untangling the messy monstrous SQL that your predecessor wrote
on a Friday afternoon, and is now yours to deal with, can get you
more speedup.
<br>
<br>
Lots of problem domains are not really close to the metal.
Embedded, device drivers and operating systems are really among
the few domains I can think of, where an intricate knowledge of
hardware is required.
<br>
<br>
IMO programming should be more about algorithms and data
structures than hardware. Architectures come and go....
<br>
<br>
<br>
<blockquote type="cite">
<br>
<blockquote type="cite">I suspect Ableton clocks are fairly
jittery through USB, so I'll give it another go using a more
stable clock and figure out if the ripple is system
instability or Ableton acting up.
<br>
</blockquote>
<br>
The USB alone makes 1ms jitter. I was observing MIDI clock out
on an oscilloscope and no matter what I do, the clock coming out
of MOTU interface is 1ms jittery AF
<br>
<br>
</blockquote>
It's aliasing, sample rate is 1kHz.
<br>
<br>
<br>
<blockquote type="cite">if incoming clock suddenly increases
frequency, you have no chance to output enough number of clock
before next pulse comes. So I had a wild idea to simply add all
thoise missing MIDI clocks right away, back to back, so the
receiving side will not loose any clock.
<br>
</blockquote>
<br>
<br>
Midi clearly lacks a "tempo change" announcement message. The midi
file format has that though.
<br>
<br>
<br>
Best,
<br>
<br>
René
<br>
<br>
<br>
--
<br>
<a class="moz-txt-link-abbreviated" href="mailto:synth@schmitzbits.de">synth@schmitzbits.de</a>
<br>
<a class="moz-txt-link-freetext" href="http://schmitzbits.de">http://schmitzbits.de</a>
<br>
<br>
________________________________________________________
<br>
This is the Synth-diy mailing list
<br>
Submit email to: <a class="moz-txt-link-abbreviated" href="mailto:Synth-diy@synth-diy.org">Synth-diy@synth-diy.org</a>
<br>
View archive at: <a class="moz-txt-link-freetext" href="https://synth-diy.org/pipermail/synth-diy/">https://synth-diy.org/pipermail/synth-diy/</a>
<br>
Check your settings at:
<a class="moz-txt-link-freetext" href="https://synth-diy.org/mailman/listinfo/synth-diy">https://synth-diy.org/mailman/listinfo/synth-diy</a>
<br>
Selling or trading? Use <a class="moz-txt-link-abbreviated" href="mailto:marketplace@synth-diy.org">marketplace@synth-diy.org</a>
<br>
</blockquote>
</body>
</html>