DSP Robotics Support

Here is what I need.

I need a random number generator, but... In the schematic - there are multiple units, so each unit should have:

a) different initial value (differences between units)
b) different initial value on each start (differences betwen loads)

Now the problem is following. This should be in blue/code. There is no big deal with live usage, but problem begins when randomization will be used for audio export on DAW. Right now, the closest thing I can get is - to have (b) - just by seeding with green RND on timeseed, but can't get (a) to work.

Why blue/code? Sample accurate syncing is the answer. Plus - can't do the design on green timers, because they don't work on audio export in DAW.

My guess is to make
a) one global green RND with timeseed...
b) ...that creates some rigid (non-time-based) sequence of different numbers, each sent to individual unit as a seed (and another green RND activator, that sends the actual seed to blue gen?); but maybe I'm wrong.

Any ideas how to make it?

Plus - second part of this task - would be to initialize blue RND outputs - only, when input blue trigger is received. So the output is not a continuous noise, but a sequence of blue readouts, activated via blue trigger. No green ticks nor timers.

This one will probably produce different seeds. On each load values are different, plus - different values between each other.

Technical question. Is the "pink noise" an equivalent of "regular spread of hits throughout octaves"? Like:

the same average of hits in 1x-2x range,
the same average of hits in 2x-4x range,
the same average of hits in 4x-8x range

?

Compact version of seed generator, useful if there are many receivers.
Just copy/paste wireless modules, and each one will generate different out.

Added slow ticker. If you ask what for - well... There is a small thing related to code/asm boxes. When they reset during operational period (and they tend to reset if you change user values inside your app) - they use initial seed, and thus - they use the same pattern if seed is not changing over time.

How to use it with random number generation in blue -you will find here:
http://synthmaker.co.uk/forum/viewtopic ... =15#p90965

tester wrote:When they reset during operational period (and they tend to reset if you change user values inside your app)

The resets (jump to stage(0)) will occur whenever anything happens that changes the routing of streams - so usually selectors and multiplexers are the culprits.
If you can identify the particular controls causing the resets, you could maybe have them send a "new seed" trigger just before the switching happens, to prevent the same number sequence from recurring.

There are a lot of selectors and multiplexers

I think the "ping" on/off trigger will be better here. New random pattern will be generated after on/off switch, while old pattern will remain if you don't reset it. Two functions at once.

*

Funny thing - restoring green values from blue streams instead of doing everything on green, and then sending to blue. But sometimes is the only way to have proper syncing on what you hear..