Skip to content

Update potentially confusing sample_duration explanation #3559

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.

Sign up for GitHub

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

Open
ethancrawford wants to merge 1 commit into
base: dev
Choose a base branch
from
+6 −4
Open

Update potentially confusing sample_duration explanation #3559

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions etc/doc/tutorial/03.4-Enveloped-Samples.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,16 +47,18 @@ up to more than the duration of the sample, the sustain is simply set to

## Fade Outs

To explore this, let's consider our Amen break in more detail. If we ask
Sonic Pi how long the sample is:
To explore this, let's consider our Amen break in more detail. Let's say
Sonic Pi's tempo is set to the default 60 BPM. If we ask Sonic Pi how
long the sample is:

```
print sample_duration :loop_amen
```

It will print out `1.753310657596372` which is the length of the sample
in seconds. Let's just round that to `1.75` for convenience here. Now,
if we set the release to `0.75`, something surprising will happen:
in beats - and at 60 BPM, that is the same as 1.753310657596372 seconds.
Let's just round that to `1.75` for convenience here. Now, if we set the
release to `0.75`, something surprising will happen:

```
sample :loop_amen, release: 0.75
Expand Down
Loading