Re: [AH] wanted: acid machine

From David VicunĖƒa
Sent Thu, Jan 8th 2015, 22:39

--001a113de7dafdc30c050c2ae037
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I am not an expert in any way, but from what i know, one of the things that
can affect midi timing is the jitter... when you have jitter problems in a
midi signal, the devices can loss their original "analog swing"... there
are some analog devices that definitely have their own micro pulsating
rhythm that makes you dance - 606, 808, 909, 303, 101, the mpc with that
60% set... the XBase09 has also a groove which is pleasant to me.

But if you provide those "groovy" devices a jitter-free midi signal, they
keep their original groove even when it is midi. If it is not jitter free,
like a bad USB midi signal from Ableton.

Another thing is that midi messages need to be "read" by software, and that
can delay the response, specially when you have several devices chained...
affecting the global groove.

Last, CV/gate attacks tends to be sharper in many synths; there are also
midi only synths that make for great attacks like Nords though.

All those characteristics added make it easier to get sharp grooves if you
use only CVgate/dinsync connections, but you can also achieve great results
with a dependable midi clock source like a syncgen, a mpc or a hw
sequencer, and avoiding midi daisy chains.




2015-01-08 21:24 GMT+01:00 David Bulog <d2ba@xtra.co.nz>:

> One thing to my ears is the TT-303  as a midi slave its not quite there
> (latest OS never solved it)
> It seems a bit off compare to other midi sequencers as a slave =E2=80=94a=
nyone
> else think this about theres?
>
> On 9/01/2015, at 8:46 am, Nicholas Keller <niroke@tampabay.rr.com> wrote:
>
> > I thought you were saying that the original machines had a unique
> sloppiness to their clocks which is often not replicated successfully in
> clones, and that upgrading to a QS CPU would eliminate this slop and that
> the slop is actually preferable.  I can testify that the 707 I used to ha=
ve
> was terrible as a master clock.  Now I have a TB and a 606, sometimes run
> by themselves and sometimes synced to a midi master with either a Doepfer
> MSY-2 or MCV24 (and soon, a TR-9090).
> >
> > And I love a good curry.  I got spoiled living in the UK for a few
> years, now I'm back in FL and it's hard to find a dish that satisfies me.
> >
> >
> > Nick
> >
> >
> >> On Jan 8, 2015, at 2:22 PM, Kenny Balys <kenny@beatkamp.com> wrote:
> >>
> >>
> >> As soon as you are running things via midi, all bets are off for timin=
g.
> >>
> >> The best Midi you will ever get will be from an MPC or something
> similar but its nowhere near analogue.
> >>
> >> Timing in the analogue domain is where everything can be rigidly
> synchronous. Triggers, pulses, clocks all together work well because they
> are just a precession or cascade of events happening at the slew rate of
> the component parts. ie) Nanoseconds
> >>
> >> If you are not using the internal sequencer on the 303 I don't imagine
> a difference as far as the timing goes. I don't have a quick silver'd
> machine so take that with a grain of salt.
> >>
> >> ps: saying nanoseconds always makes me want a stiff curry with some
> nanobread
> >>
> >>> On 08-01-2015 7:01 PM, Nicholas Keller wrote:
> >>> This sequencer stiffness you mention... If you ran the TB from a
> >>> MIDI->Sync converter, wouldn't you also lose some of the TB's
> >>> fl-acid-ity?  I was thinking about getting the Quicksilver upgrade at
> >>> some point, so I wonder what difference it will make if I rarely use
> the
> >>> TB with its own internal clock.
> >>>
> >>> Nick
> >>
>
>

--001a113de7dafdc30c050c2ae037
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I am not an expert in any way, but from what i know, one o=
f the things that can affect midi timing is the jitter... when you have jit=
ter problems in a midi signal, the devices can loss their original &quot;an=
alog swing&quot;... there are some analog devices that definitely have thei=
r own micro pulsating rhythm that makes you dance - 606, 808, 909, 303, 101=
, the mpc with that 60% set... the XBase09 has also a groove which is pleas=
ant to me.<br><br>But if you provide those &quot;groovy&quot; devices a jit=
ter-free midi signal, they keep their original groove even when it is midi.=
 If it is not jitter free, like a bad USB midi signal from Ableton.<div><br=
></div><div>Another thing is that midi messages need to be &quot;read&quot;=
 by software, and that can delay the response, specially when you have seve=
ral devices chained... affecting the global groove.<br><div><br></div><div>=
Last, CV/gate attacks tends to be sharper in many synths; there are also mi=
di only synths that make for great attacks like Nords though.=C2=A0<br><br>=
All those characteristics added make it easier to get sharp grooves if you =
use only CVgate/dinsync connections, but you can also achieve great results=
 with a dependable midi clock source like a syncgen, a mpc or a hw sequence=
r, and avoiding midi daisy chains.=C2=A0</div><div><br></div><div><div><div=
><div><div><br></div><div><br></div></div></div></div></div></div></div><di=
v class=3D"gmail_extra"><br><div class=3D"gmail_quote">2015-01-08 21:24 GMT=
+01:00 David Bulog <span dir=3D"ltr">&lt;<a href=3D"mailto:d2ba@xtra.co.nz"=
 target=3D"_blank">d2ba@xtra.co.nz</a>&gt;</span>:<br><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">One thing to my ears is the TT-303=C2=A0 as a midi slave its not =
quite there (latest OS never solved it)<br>
It seems a bit off compare to other midi sequencers as a slave =E2=80=94any=
one else think this about theres?<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On 9/01/2015, at 8:46 am, Nicholas Keller &lt;<a href=3D"mailto:niroke@tamp=
abay.rr.com">niroke@tampabay.rr.com</a>&gt; wrote:<br>
<br>
&gt; I thought you were saying that the original machines had a unique slop=
piness to their clocks which is often not replicated successfully in clones=
, and that upgrading to a QS CPU would eliminate this slop and that the slo=
p is actually preferable.=C2=A0 I can testify that the 707 I used to have w=
as terrible as a master clock.=C2=A0 Now I have a TB and a 606, sometimes r=
un by themselves and sometimes synced to a midi master with either a Doepfe=
r MSY-2 or MCV24 (and soon, a TR-9090).<br>
&gt;<br>
&gt; And I love a good curry.=C2=A0 I got spoiled living in the UK for a fe=
w years, now I&#39;m back in FL and it&#39;s hard to find a dish that satis=
fies me.<br>
&gt;<br>
&gt;<br>
&gt; Nick<br>
&gt;<br>
&gt;<br>
&gt;&gt; On Jan 8, 2015, at 2:22 PM, Kenny Balys &lt;<a href=3D"mailto:kenn=
y@beatkamp.com">kenny@beatkamp.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; As soon as you are running things via midi, all bets are off for t=
iming.<br>
&gt;&gt;<br>
&gt;&gt; The best Midi you will ever get will be from an MPC or something s=
imilar but its nowhere near analogue.<br>
&gt;&gt;<br>
&gt;&gt; Timing in the analogue domain is where everything can be rigidly s=
ynchronous. Triggers, pulses, clocks all together work well because they ar=
e just a precession or cascade of events happening at the slew rate of the =
component parts. ie) Nanoseconds<br>
&gt;&gt;<br>
&gt;&gt; If you are not using the internal sequencer on the 303 I don&#39;t=
 imagine a difference as far as the timing goes. I don&#39;t have a quick s=
ilver&#39;d machine so take that with a grain of salt.<br>
&gt;&gt;<br>
&gt;&gt; ps: saying nanoseconds always makes me want a stiff curry with som=
e nanobread<br>
&gt;&gt;<br>
&gt;&gt;&gt; On 08-01-2015 7:01 PM, Nicholas Keller wrote:<br>
&gt;&gt;&gt; This sequencer stiffness you mention... If you ran the TB from=
 a<br>
&gt;&gt;&gt; MIDI-&gt;Sync converter, wouldn&#39;t you also lose some of th=
e TB&#39;s<br>
&gt;&gt;&gt; fl-acid-ity?=C2=A0 I was thinking about getting the Quicksilve=
r upgrade at<br>
&gt;&gt;&gt; some point, so I wonder what difference it will make if I rare=
ly use the<br>
&gt;&gt;&gt; TB with its own internal clock.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Nick<br>
&gt;&gt;<br>
<br>
</div></div></blockquote></div><br></div>

--001a113de7dafdc30c050c2ae037--