proper resync plus offset?

[tester]

I'm not sure how to handle this one, so that resync starts the ramp from initial offset (and then goes full range).

[Tepeix]

Here's how i would do.
(Not sure, but i think that the tick/timer part could sometime not work.
in my machine i could click on it with no effect, i increased the time value but now it stay on a little time..)

[tester]

Thanks.

You are right, at short times, sometimes clicker doesn't work.

Which raises an interesting question, because blue components theoretically are 'hardwired', i.e. (at least to what I understand) they shouldn't miss any green value (comparing sample rate to green tick). Anyone any idea why this is happening?

On the other hand - is there other way to address the resync function, to make it 1:1 compatible with resync node on stock oscillators? From what I see, they react to streambool 0 to 1 change.

[tester]

I think I fixed problem with resync and missing triggers, it can now be formatted to other needs.

Quick question. Can this be simplified in terms of performance?

[Tepeix]

Good solution !
I think that the way to make it perform faster is to make it in asm.
But will it be so much fast ? For short code i'm not sure..

I was also working on something for the tick to blue in one sample.
(needed also one) Not sure which solution is faster..
(I need to read and write 2 time and to subtract 2 time when there's no ticks
but i plan a hopped version)

I will post it in example.

I was also surprise that the tick could not fire.
Normally 1 ms is supposed to stay 44 sample.
But the windows timer distort time.
(this also means that it could make more calculation when it have the time)
So 1 ms could be less than one sample or 1200 sample. I suppose it's machine dependent.

[tester]

ASM is outside my boundaries, I'm better in wiring green relationships.

Basically this ramp module will drive a mixer/rotator, and everything x24 or so.

Since these are very analog setups, I'm using hard resync, to reset phase relationships between all oscillators, because this changes sound very much.

For this module, to make it compatible with stock oscillators (in terms of resync), instead abs, min/max function should be used, to make it react only to bool-to-true. I will post it tomorrow... or next week. Global resync can be handled so, that a green-whatever-thing (solution from here) is converted to blue output, and this output is then redistributed as sample-accurate reset for all else.

btw, I'm a bit surprised, that this graph I use inside - captures all blue impulses. I will re-extract the routine for further testing, because this raises interesting question about syncing between green and blue data.

[Spogg]

I’ve had a look through this topic and schematics and I wanted to ask why do you want to sync an oscillator from the green world?

Green is low priority for the CPU and uses the Windows timer which is notoriously inaccurate. Also any critical green timing can behave somewhat unpredictably as schematics increase in complexity. Finally, a VST’s green processing will usually behave differently and faster than a schematic in the FS editor which has more overheads to deal with. I’ve actually had many situations where green processing doesn’t work properly in a schematic but does in a VST. Admittedly, this is more likely when there’s a lot of re-drawing going on.

[tester]

You probably missunderstood something.

Live preview and parameter modification --> green resync button --> single bule resync sender --> multiple blue receivers.

Resyncing that way allows to hear what you will get on VST export.
This solution works as expected, I always get what I hear.
As you can see in the "diagram" above, the green part is irrelevant here, as syncing goes from blue part to blue all else.

As for module that is analyzed in this topic - it's not really an oscillator, but a sort of driver/timer.

[tester]

Take this example.

In order to control pitches, vibes, phases and timings, you need a way to reset this thing after changing parameters.

[Spogg]

You probably missunderstood something.

Yes I think I did misunderstand!

I was just curious about the application.