---
description: Make sure your notes start and end in the right moment
---

# Finetuning synchronization

## In this lesson you will learn how to

* determine the correct start positions and duration of notes,
* use auxiliary note playback,
* resize notes - make them start or end one beat earlier or later.

## Before you start

After the previous lesson you should already have a folder with the song's audio & txt file. Your txt file should contain 2 lines, the first line should already have correct lyrics in place.

You can also download the files required for this lesson here:

{% file src="https://2464591649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWYWuwgmUrVIBcYKbiiso%2Fuploads%2FItzoUMbSwJAbRPwuh2Zz%2FDavid%20Amber%20-%20Second%20Time%20Around%20%5Bfinetune-synchro%5D.zip?alt=media&token=e95a7445-6f05-4d60-8fc5-d3d4ce8da6fa" %}

## Finetuning synchronization

Timing in Ultrastar is very important. If you specify start or end beats of the notes incorrectly, players will be confused because what they see will not match what they hear. The more effort you put into this step, the more grateful you will be to yourself while singing.

### Determining the note's start beat

#### Theory

In the previous lesson we already roughly placed the notes according to what we heard - we verified that during playback the ticks representing note beginnings  matched the audio. That's why finetuning start beats should not change much - maybe move some note's start beat by 1.

{% hint style="info" %}
In theory note should begin in the first beat in which the note's lyrics (or more precisely - the syllable's vowel) become audible.
{% endhint %}

But how to find such beat?

Let's look at the first note with lyrics _"can"_:

<figure><img src="https://2464591649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWYWuwgmUrVIBcYKbiiso%2Fuploads%2FV3lFxfJCdjkNdKMWgQPI%2Fimage.png?alt=media&#x26;token=1348b2e3-4831-4e81-ac32-e7a1ea6107c9" alt=""><figcaption></figcaption></figure>

It currently begins in the beat 0 (beats are visible on the lower X axis of the [grid](../../user-interface/middle-components/main-editor/beats-and-pitches-grid)).

To determine if the position is correct we need to verify two things, basically that:

* the vowel is audible in beat 0,
* the vowel is not audible before beat 0.

As you may remember, we used `space` key shorcut to hear the whole note. It is not particularly useful when finetuting. For finetuning we need something more fine-grained - ideally we would like to be able to listen to one chosen beat. In practice, one beat is too short - it would be hard to recognize any actual sounds.

Karedi has a special playback mode for finetuning called auxiliary note playback mode. In our case it will play the first beat of the note and some time before it just to make the sound clearer.

#### Check that the vowel is audible in note's first beat

If you press `alt + ↑` shortcut, you will hear the first beat of the current note and 2-3 beats before it. You need to determine whether or not you hear the vowel of the note's syllable in that playback.

In case of our note _"can"_ we can hear the start of the vowel. We are dealing with the start of the note so it means that the last beat of the playback and at the same time the first beat of the note contains the vowel sound.

We have just verified the first condition.

{% hint style="info" %}
If you could not hear the vowel it would mean that the note starts too early. In such case, you would need to make it begin one beat later (as explained below) and try again.
{% endhint %}

#### Check that the vowel is not audible in the previous beat

We still need to check that the note is not audible in the previous beat. The easiest way to do it is resize the note to the left - make it start one beat earlier - and re-do the check described above.

To make the note start earlier, use `ctrl + ←` shortcut:

<figure><img src="https://2464591649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWYWuwgmUrVIBcYKbiiso%2Fuploads%2FJAEd0gMlWsdz1H3KszOd%2Fimage.png?alt=media&#x26;token=e0b06832-61aa-4be8-b5d0-c3b9cd3cf0ca" alt=""><figcaption></figcaption></figure>

This time when you use `alt + ↑` shortcut, you can't hear the vowel, you can only hear the start of the _"k"_ sound in _"can"_. It means that the last note of the playback and consequently the first beat of the note does not contain vowel sound - the note begins too soon now.

Let's make the note start later by using `ctrl + →` shortcut:

<figure><img src="https://2464591649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWYWuwgmUrVIBcYKbiiso%2Fuploads%2FrH0d1hCsjTNiwfDqP9Am%2Fimage.png?alt=media&#x26;token=5410fc85-4f34-4032-a291-04cdfdac85a4" alt=""><figcaption></figcaption></figure>

We have just verified the second condition. Beat 0 is the first beat in which _"can"_ starts. We can now move on to determining where it should end.

### Determining the note's end beat

#### Theory

{% hint style="info" %}
In theory note should end in the last beat in which the note's lyrics (or more precisely - the syllable's vowel) is still clearly audible.
{% endhint %}

The valid end beat is usually more fuzzy than the start beat. Singers often reduce the volume of the syllable at the end. Therefore with increased or decreased volume of the playback, you can get slightly different duration. The best way is not to overhink it, if the vowel is theoretically still audible but barely audible compared to the previous beat just assume it's no longer audible and move on.

Just like before we need to check two things, that:

* vowel is audible in the last beat of the note,
* vowel is not audible in the note after the last beat.

#### Check that the vowel is audible in note's last beat

Just like for the start beat, there is an auxialiary note playback meant for determining the end beat of the note. It will play the last beat of the note and some time after it.

To activate the playback of the end of the note, use `alt + ↓` shortcut.

In case of our _"can"_ note, we can not hear any vowel. We need to shorten the note using `alt + ←` shortcut:

<figure><img src="https://2464591649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWYWuwgmUrVIBcYKbiiso%2Fuploads%2FeREY4gveppgr7m6A0mYT%2Fimage.png?alt=media&#x26;token=a4e8c142-f55c-40f8-b2db-ed2905b83da0" alt=""><figcaption></figcaption></figure>

Press `alt + ↓` shortcut. Still nothing. Shorten the note until you can hear the vowel.

You should end up with:

<figure><img src="https://2464591649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWYWuwgmUrVIBcYKbiiso%2Fuploads%2FYjCkNc2TJYN7CPixsyqc%2Fimage.png?alt=media&#x26;token=f279f7d0-f6f7-46f4-a6e0-d4c6f9494fd7" alt=""><figcaption></figcaption></figure>

Now when you use `alt + ↓` shortcut to hear the end of the note, you can clearly hear _"a"_ sound.

#### Check that the vowel is not audible after the note's last beat

Because we were shortening the note we already checked it. However sometimes your note may be too short instead of being too long so you need to know how to do this. Just for practice let's check it again.

Make the note end one beat later by using `alt + →` shortcut:

<figure><img src="https://2464591649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWYWuwgmUrVIBcYKbiiso%2Fuploads%2F8vfGylEzBtMqKNJYEEZZ%2Fimage.png?alt=media&#x26;token=eeb4abf5-ed8e-4fd1-b1ee-345945dd893e" alt=""><figcaption></figcaption></figure>

Now when you use `alt + ↓` shortcut to hear the end of the note, you can only hear the _"n"_ sound which is not picked up by microphones well - we should cut it and focus on the vowel.

{% hint style="info" %}
You can hold `alt` key and just press the arrow keys one by one. First `↓` (to hear the end), then while still holding the alt key press `→` (to lengthen the note), then `↓` again, then `←` (to shorten the note)_,_ then `↓` again. It will speed up the process.
{% endhint %}

### Finishing the line

In the same way please try to determine the start and end beats for the remaining notes of the first line.

{% hint style="warning" %}
Notes should never touch, always shorten the previous note to have at least 1 beat break.
{% endhint %}

Once you are ready check if it looks like this:

<details>

<summary>Final result</summary>

<img src="https://2464591649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWYWuwgmUrVIBcYKbiiso%2Fuploads%2FH958JA4jL3gt75Z89Wbn%2Fimage.png?alt=media&#x26;token=971e4deb-3edd-475b-bb6b-cbdc0ed3f4c6" alt="" data-size="original">

</details>

As explained above, some of your notes e.g. "_we"_ or "_ver"_ may last 1 beat shorter, it's not a problem as 1 beat difference in duration is sometimes debatable.&#x20;

{% hint style="info" %}
Finetuning may seem like a lot of work at first. Do not worry - once you get the hang of the shortcuts, the process will speed up significantly.
{% endhint %}

## Video

{% embed url="https://youtu.be/dILihEf-bgw" %}

### Shortcuts summary:

Let's summarize the shortcuts that we have learned in this lesson:

* make the note start one beat earlier: `ctrl + ←`
* make the note start one beat later: `ctrl + →`
* make the note end one beat earlier: `alt + ←`
* make the note end one beat later: `alt + →`
* listen to the first beat of the note (with several beats before): `alt + ↑`&#x20;
* listen to the last beat of the note (with several beats after): `alt + ↓`

### What's next

In the next lesson we will finish the first line by setting the pitches.

## To learn more refer to:

{% content-ref url="../../user-interface/playback/auxiliary-note" %}
[auxiliary-note](../../user-interface/playback/auxiliary-note)
{% endcontent-ref %}

{% content-ref url="../../user-interface/middle-components/main-editor/managing-notes/resizing-notes" %}
[resizing-notes](../../user-interface/middle-components/main-editor/managing-notes/resizing-notes)
{% endcontent-ref %}
