Transcription Does Not Work. What Should I Do?

Are you having trouble transcribing your trumpet recordings into sheet music? Here are some possible causes and how to fix them.
Written by Dimitri
Updated 1 month ago

On TrumpetConvert, some recordings may not be transcribed correctly due to a few common issues. Below are the main reasons and what you can do to resolve them:

🎺 1) Your file is too large or too long

TrumpetConvert has limits on file size and duration.

✅ Make sure your audio file is under 15MB

✅ YouTube videos must be under 10 minutes

💡 Tip: If your file is larger than 15MB and in .wav or .flac format, convert it to .mp3 before uploading. Use this free tool: https://convertio.co/wav-mp3/

🛑 2) Your audio file contains internal errors

Some files may be corrupted or improperly encoded, which prevents processing.

🔹 Try uploading a different version of your trumpet performance

🔹 If your file is in WAV format, convert it to MP3 for better compatibility

Convert here: https://convertio.co/wav-mp3/

🌐 3) There was a temporary internal error on TrumpetConvert

As a cloud-based tool, TrumpetConvert depends on its server infrastructure. Occasionally, temporary issues may interrupt the transcription process.

🕒 Solution: Wait a few minutes and try again — most issues are resolved quickly.

🔗 4) The format of your YouTube link is not supported

Some YouTube URLs may not be recognized correctly. Try copying the link using one of the following methods:

1️⃣ Copy the link directly from your browser’s address bar

2️⃣ Right-click on a search result and choose “Copy link”

3️⃣ Click the Share button below the video and copy the link from the popup

🎺 Still having trouble?

Try another video or upload an .mp3 file instead — it’s often the fastest and most reliable solution.

5) Your VPN may be interfering with the transcription

Some users have reported that having a VPN enabled on their device caused transcription processes to fail (e.g., stopping at 90%) or prevented file downloads. If you are using a VPN, we recommend turning it off and trying again. This small change has resolved many similar cases.

Did this answer your question?