Mem,store ,load

[gentleclockdivider]

Can someone explain the difference
In the first example , the load is read directly from the mem module , the second example reads it from store

[colin@loomer]

It shouldn't make a difference: red "reference" connections just serve to connect memory modules in whatever way is most convenient. All [store]/[load] modules that are connected together, in any way, will share the same [memory]. Whether you chain them (as in the second image) or connect all to the [memory] (as in the first) should really come down to personal preference and whatever is clearest in the patch flow.

[gentleclockdivider]

This is a counter that's using the mem modules (not perfect ) , but it doesn't reset when I send the constant zero to the store mod.
Why is that ?

[gentleclockdivider]

Oh dear , once again it was the order of placement , load should be alligned or higher placed with then constant 1

[timmysitc]

It shouldn't make a difference: red "reference" connections just serve to connect memory modules in whatever way is most convenient. All [store]/[load] modules that are connected together, in any way, will share the same [memory]. Whether you chain them (as in the second image) or connect all to the [memory] (as in the first) should really come down to personal preference and whatever is clearest in the patch flow.

Hi Colin,
This is an unrelated question regarding your old thread on converting aupreset to xfl. I'm looking to convert some old nexus 2 presets so I can use them on a Windows setup. If you have any spare time is this something you would consider looking back into? Cheers mate

[colin@loomer]

Of course. I am rather often asked about this, and just haven't found the time to update the python script. Just to keep the forum thread clean, could you PM me with what you need, perhaps a link to a few of the presets, and I'll have a stab at getting the converter up to scratch.

[timmysitc]

Cheers Colin, dropped you a PM.

Cheers mate!