<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Good points.<br>
<br>
regarding 2) I still have all the analyzer data saved for later
inspection.<br>
I went for small zoomable graphics in favor of a nice looking
layout. That's probably the non academic approach.<br>
<br>
In the end I was too lazy to export all the measurements as CSV and
replot them in something like gnuplot as vector images.<br>
For printing I think a dark background isn't too good either.<br>
<br>
regarding 3) I try to find out the best way to generate some
statistical descriptions from the data I have. Never done this
before.<br>
I basically just thought writing something like a paper is probably
more useful than just uploading a huge dump of logic analyzer data.<br>
<br>
But it's always good to learn something and get some feedback. Much
appreciated!<br>
I never wrote a paper before besides my diploma thesis years ago and
it was fun to dust off my LaTeX skills again.<br>
<br>
I already implemented most of my findings in the replacement CPU I'm
developing. The lag of the gate signal is already switchable, but
not the interplay of the clocks which is the more interesting part
imho. So maybe I can make some A/B testing in a few days when
realtime switching to a pin change interrupt for the tempo clock is
implemented.. Turning off the 1ms on and the 2.4ms off lag makes no
big difference to my untrained ears.<br>
<br>
Julian<br>
<br>
<br>
<div class="moz-cite-prefix">Am 15.03.2017 um 17:13 schrieb Bruno
Afonso:<br>
</div>
<blockquote
cite="mid:CA+z2k4u76eDpP7Xi6T7DHWC5PML20N66Bshf0d8zbV1U34Fjww@mail.gmail.com"
type="cite">
<div dir="ltr">Thanks for this work Julian, very interesting. A
couple of notes:
<div><br>
</div>
<div>1) For things like ISR and DAC, just write them out the
first time they appear ,i.e.: "interrupt service routine (ISR)
" and then just use ISR subsequently. This way for someone
reading linearly from the beginning everything is obvious.</div>
<div>2) some figures small and thus hard to see without zooming,
maybe crop the pics to the part that matter or that is
critical to the point you're making. Think about someone
printing it, can they still see what you'd like them to? If
you can't crop to show the point you are trying to make, maybe
it's superfluous.</div>
<div>3) you mention jitter several times but there is no
statistical description of the phenomena (mean, std dev, etc)
or even a graphic depiction such as an histogram. Without this
it's hard for the reader to see how relevant it may or not
be. </div>
<div><br>
</div>
<div>The article hinges on how interesting the 303 is due to the
interplay of clocks. You do not mention where you'd like to go
next or what would be useful to further explore. This is
normally included in order to share things that in your mind
are important and left to uncover. A younger brave soul may
just try to pursue this, what a nice side effect! Personally,
I feel it would be cool to simulate the clock interplay to
reproduce obseved experimental data and then explore the space
in order to get it more tight or more loose. Would it have a
big impact on sound and experience? Would people care or
notice if they used a much tighter 303 clock wise?</div>
<div><br>
</div>
<div>cheers</div>
<div>b</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Wed, Mar 15, 2017 at 11:14 AM Julian Schmidt
<<a moz-do-not-send="true" href="mailto:elfenjunge@gmx.net">elfenjunge@gmx.net</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">I'm
currently working on a TB-303 replacement CPU for the RE-303
project.<br class="gmail_msg">
www.<a moz-do-not-send="true"
href="http://sonic-potions.com/re303" rel="noreferrer"
class="gmail_msg" target="_blank">http://sonic-potions.com/re303</a><br
class="gmail_msg">
<br class="gmail_msg">
Since there is not too much information available, and a lot
of<br class="gmail_msg">
speculations are running wild on the net, I tried to clear
things up a bit.<br class="gmail_msg">
<br class="gmail_msg">
Someone from the RE-303 forums loaned me an original CPU and I
hooked it<br class="gmail_msg">
up to a logic analyzer and did some extensive testing and
measurement<br class="gmail_msg">
sessions.<br class="gmail_msg">
<br class="gmail_msg">
I summed up my findings in a short paper available here:<br
class="gmail_msg">
<a moz-do-not-send="true"
href="http://sonic-potions.com/Documentation/Analysis_of_the_D650C-133_CPU_timing.pdf"
rel="noreferrer" class="gmail_msg" target="_blank">http://sonic-potions.com/Documentation/Analysis_of_the_D650C-133_CPU_timing.pdf</a><br
class="gmail_msg">
<br class="gmail_msg">
I have to admit, a lot of it is definitely from the "hear the
fleas<br class="gmail_msg">
cough" category, as we say in Germany, but at least we now
have data<br class="gmail_msg">
coming from a real CPU.<br class="gmail_msg">
<br class="gmail_msg">
Comments are welcome. I'm a bit rusty in writing proper papers
;)<br class="gmail_msg">
<br class="gmail_msg">
Best,<br class="gmail_msg">
Julian<br class="gmail_msg">
_______________________________________________<br
class="gmail_msg">
Synth-diy mailing list<br class="gmail_msg">
<a moz-do-not-send="true"
href="mailto:Synth-diy@synth-diy.org" class="gmail_msg"
target="_blank">Synth-diy@synth-diy.org</a><br
class="gmail_msg">
<a moz-do-not-send="true"
href="http://synth-diy.org/mailman/listinfo/synth-diy"
rel="noreferrer" class="gmail_msg" target="_blank">http://synth-diy.org/mailman/listinfo/synth-diy</a><br
class="gmail_msg">
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>