Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question on S&H vs. T&H #25

Open
firolightfog opened this issue Dec 10, 2021 · 1 comment
Open

Question on S&H vs. T&H #25

firolightfog opened this issue Dec 10, 2021 · 1 comment

Comments

@firolightfog
Copy link

Isn't the S&H switch actually more of a T&H on MG, MG8, MG16?

@sumpygump
Copy link
Contributor

sumpygump commented Feb 6, 2025

I think it is correctly characterized as a sample-and-hold function. When triggered, the module will generate either a random LFO or a sample-and-hold value. Presumably the source of the 'sample' is its own source of random noise.

With track-and-hold it is more like a gate is applied for a limited period and then you have the original sample pass through for another period. Almost like track-and-hold will use a gate: when it is high, the sample is held at a single voltage from the time of the onset of the gate and when it is low, the original sample passes through.

With the MG* modules, when it selects to return a sample-and-hold value, It just stays at that value. There is no time when the original sample passes through (the random noise).

I am basing my understanding of the differences from sample-and-hold and track-and-hold from this example: https://www.youtube.com/watch?v=KvjiKzBaTAs and this diagram: (a: S&H, b: T&H):

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants