[sdiy] Generating a large number of CV outputs

[brianw]

This is very strange. The copy of my message that I received from the mailing list has that corruption, but following the link to the Archive shows the message as I sent it. I just confirmed by looking at the raw content of the message that I received from the list, and the !\n corruption is there in the plain ASCII content (i.e. this is not an HTML formatted message).

Somehow, the message is getting corrupted on its way to some list members and not others.

Brian

On Dec 10, 2023, at 10:30 AM, Ben Stuyts <ben at stuyts.nl> wrote:
> Hi Mattias,
> 
> Is this is the message you are quoting? https://synth-diy.org/pipermail/synth-diy/2023-December/132104.html If so, I do not see it in my copy of the message, nor in the Archive. So it could be something in your mail client? Or forwarder? ;-)
> 
> Ben
> 
> On 10 Dec 2023, at 13:03, Mattias Rickardsson <mr at analogue.org> wrote:
>> [snip]
>> PS: on the topic of strangenesses in emails, what's the cause of the inserted  [exclamation point + newline + whitespace]  in long paragraphs? See:
>> 
>> 
>> ... as a message comes in, rather than a DAC that needs a continuous data stream (usually fed from a waveform buffer). DAC chips that operate on a fixed sample rate require a clock signal as part of the serial bus that they use, whereas DAC chips that are flexible about fixed or variable sample!
>>   rate do not need a clock, per se, because they have a "convert" signal to load each new value. There is clearly some overlap in the design here, but the point is that you want to think about what the CPU is required to do to feed the DAC. In general, a DAC that is capable of variable...
>> 
>> ... CODEC without each signal interfering with the other. But that's an example of way too many bits in each word and way too many data transfers per conversion to be an effici!
>>  ent model. Your CPU will run out of power an order of magnitude faster with this approach.