<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
> > It doesn't mean the synth will not sound good, there are just some <br>> > things that it<br>> > will not be able to do.<br>> ><br>> > Regards, nick.<br>> <br>> Indeed a B3 emulated by an Oberheim Matrix-1000 might be no good choice, <br>> OTOH because of the automation, you won't have any synth with a good B3 <br>> emulation to change 20 parameters during a song, while for any <br>> "synthetic" sound e.g. from an Oberheim Matrix-1000 you might wish to <br>> change a lot of parameters during a song and changing filter parameters <br>> for "synthetic" sounds 128 steps are enough.<br>> <br><br>The Matrix 1000 users also complained of the quantisation of the mod matrix<br>for this beast, admittedly only when being used for very wide/wild modulation<br>where again the steps could be heard (*). Perhaps this is getting off the point: if<br>work is going to be done on a CV proposal (which is admittedly debatable) then<br>quantising to some level at which people have been known to complain of in the<br>past is not a good starting point.<br><br>The nice thing about the tuxfamily proposal is that CV is completely 'analoguous'<br>by which I mean analogous to the native sampling parameters. That is badly<br>phrased, I am likely to get hit on for saying it but it does not suffer from any worse <br>quantisation than the underlying audio signal. The analogue monsters took a lot <br>of flac when they started quantising their parameters and the tux design would <br>avoid such issues.<br><br>Another reason this is getting off the point is that defining a separate CV port in<br>Jack would obfuscate the issue, probably. The people discussing ambient control<br>would want CV at the native rate and that can be delivered now anyway over<br>audio ports - the only question is how the application uses the data on those ports.<br>If a new port type is defined then it will carry some quantised representation of this<br>data and then if any app talked about supporting CV you would not know which<br>type was being supported. I don't think the overhead in jack would be that high <br>for distributing native/audio CV and if people wanted to quantise down to fractions<br>of the sample rate or resolution because that is how their apps work then this could <br>still be applied as an interface into the native data. The reverse is naturally not true.<br><br>Nick.<br>* The Matrix-1000 (and related 6 and 12) are amongst the best synths ever, don't<br>misunderstand my critisism. When they were first released several of the hardware<br>magazines refered to them as the most over the top analogue synths imaginable.<br>If anything, a new implementation of CV should take into account the small number<br>of complaints that were made against it and parameter quantisation is one of them.<br>I still want to build an emulator for one of these however I need to finish the EMS<br>Synthi first as the Oberheim mod matrix was loosely based on its patch pin panel.<br> <br /><hr />Hotmail: Free, trusted and rich email service. <a href='https://signup.live.com/signup.aspx?id=60969' target='_new'>Get it now.</a></body>
</html>