advanced index counter for samplers

[KG_is_back]

This is an advanced index counter for samplers, with a sampler as an example.
The Clock Core has 3 internal clocks, that can calculate 3separate sections of indexes. First clock counts the most recent section and rest two calculate previous sections during crossfades.

The clock core receives several parameters that define a clock:
Section start point (32bit integer - converters are inside the schematic)
Section end point (also 32bit int)
+both also receive a fractional part, so you can define a section with subsample precision
crossfade length
direction (forward or backward playback)
and "play" boolean which suppose to be a pulse, that initiates the clock.

When you initialize new clock, old clock 0 is moved to clock above (the clock 1) and continues to calculate until the crossfade is finished (this can by stacked twice, allowing 2crossfades ad the same time for example when "release" is hit during loop crossfade). Clocks 1 and 2 have also gain output (for crossfade calculations) which is a falling ramp and stop calculating after zero is reached.
The clocks continue to calculate even if the index leave start/end boundaries. You get notified about such event in clock 0 by the "finished" boolean output which becomes true when index will step outside the section boundaries (you get notified one sample in advance, so when connected in feedback your loop/ADSR section calculator can react in next sample).

I think my description above is not very clear, but I will write complete clear manual once I finish several features and optimizations. Until then, here is an example schematic. You can load a wave file, define 3 sections in the file and define crossfade lengths. First section (named attack) is played when you hit the note, once it finishes, it crossfades to the middle section (named looped sustain). The middle section is looped while holding the note (also with definable crossfade). When you release the note, sound crossfades to the last "release" section (note that this also works during attack and when crossfade is already happening). The schematic also indicates the index positions for the 3 clocks by lines (notice that you see two lines during crossfades or even 3 lines when you need to crossfade during crossfade).

[tester]

Few months more, and we will have first DAW made in Flowstone.

[KG_is_back]

Few months more, and we will have first DAW made in Flowstone.

We would have made DAW a long time ago, if VST hosting was possible...

Also mouse wheel support is a big drawback in this matter and prevents us form making efficient sound/midi/sequence editors (scrolling and zooming via mouse wheel saves so much time... using mouse dragging for such thing feels like driving a car from back seat using a stick to push pedals).

[tester]

On the other hand - "Yet another DAW? Really?"

Reaper is relatively cheap and pretty well equipped, not to mention they don't limit it after trial is expired.

But with FS apps there is one issue worth to mention. Glitches. When making exe apps, you don't even need to bother with protections, because you will experience glitches very often. Unpredictable, sometimes after each selector switch, and sometimes it may take quite some time before app becomes stable again (or after starting the app as well). This is what prevents me from thinking on even making a dedicated "player" of something. It will work great for testing, it will work great as a vst, and it will work great as standalone for other applications. But for clean sound presentations? Ehm... I think it's not that level of guts inside.

[KG_is_back]

On the other hand - "Yet another DAW? Really?"

Reaper is relatively cheap and pretty well equipped, not to mention they don't limit it after trial is expired.

But with FS apps there is one issue worth to mention. Glitches. When making exe apps, you don't even need to bother with protections, because you will experience glitches very often. Unpredictable, sometimes after each selector switch, and sometimes it may take quite some time before app becomes stable again (or after starting the app as well). This is what prevents me from thinking on even making a dedicated "player" of something. It will work great for testing, it will work great as a vst, and it will work great as standalone for other applications. But for clean sound presentations? Ehm... I think it's not that level of guts inside.

I completely agree.

Anyway, what you think about the sampler clock I've made? any suggestions?

[tester]

With samplers you would have to ask someone else. I basically do extensive job on large audio sections, thus using mono4 and not midi/poly related stuff. Then, there are heavy hours of intense listening and target specific testing.

With clock - if it can work for simple start/end crossfading, then I will need to spend some time on it to digest it. I don't feel an expert.