• 23.98
• 24
• 25
• 29.98
• 30
• 48
• 50
• 59.94
• 60

Starting the audio player instantly is not possible due to environmental limitations. Starting the audio can take up to 100 milliseconds. At this time, "Starting..." text is seen on the screen. It means that the application tries to start to play audio and get the current time.

1. When the start button is pressed and the sound starts playing (Current time - Prerun >= 0).
2. When the Prerun is added and the countdown comes to zero and the sound starts playing (Current time - Prerun < 0).
3. When the time is changed using the search bar while the sound is playing. (Current time >= 0).

It cannot be eliminated completely. This delay comes from the lower layers such as OS and physical. Starting audio may take up to 100 milliseconds. This period changes depending on the used hardware of the device.

In this application, we benefit from Google’s Exoplayer library functions within our audio process functions. It has Apache 2.0 License. You can inspect the license by clicking here

No, it will not.

1) Distance: If the audio source is further away from the camera causing poor or no sound at all in the recording. 2) No microphone: The lack of a built-in microphone or no microphone is available. E.g. with the use of drones that cannot record sound/audio. 3) Background noise: E.g. the loudness of drones whose rotor noise drowns out the audio/sound. An environment with strong background noise. It is then sufficient for the musician/artists to carry the smartphone with the app and listen/synchronize with the music. This eradicates the set-up and use of large equipment. 4) Song part Repetitions: when a short piece of the music/audio is recorded, the automatic synchronization does not manage to find the right place in the song. For example, if the first and second chorus sounds the same."