How can we
help?

Open the tool page again and confirm that you are using an updated version of your browser. Reload the page once. If you changed tabs, blocked a permission, or left another application using the microphone, the reading may stop. Close video calls, recorders, meeting applications, and games with voice chat before testing.

Run a simple test on the same device. Speak for 3 seconds near the microphone or record a short note in another application. If no application can capture your voice, the problem may be with the device's permission or hardware, not the Cantivy page. On Android, check the browser's permissions in Settings. On iPhone, find the browser under Settings, Privacy & Security, Microphone.

If the problem is with the online tuner, play one string at a time and bring the instrument closer to the device's microphone without touching the instrument to the phone. On a six-string guitar, start with the open sixth string, the note E2, at an approximate frequency of 82.41 Hz. Play a clean note for 2 to 4 seconds and move your hand away from the other strings.

On an electric guitar, confirm that the cable is connected to the audio interface if you are not using the phone's microphone. If the interface has more than one input, select the input receiving the instrument. Lower the speaker volume to prevent feedback. Do not play the guitar in front of a powered speaker while trying to measure the note.

To record an idea while you investigate, you can use the audio recorder. Record 10 seconds of the problem, including the sound that should have been recognized. Say whether the file was captured by the internal microphone, a USB interface, or another device. This recording helps compare the behavior on another device without relying only on your memory of the test.

If your question concerns a feature, also consult all tools and confirm that you opened the correct page. For now, write down in a note: the page address, device, browser, action taken, and result. This list already provides the basis for a support message.

Run this test with your instrument ready. First, see whether a notice appears asking for microphone access. Choose Allow. If you denied access earlier, open the browser's permissions and allow the microphone for the site. Then reload the page. On a phone, also check that the browser has microphone access in the system settings. On a computer, check the browser permission and the selected input in the sound settings.

Second, test the correct input. If headphones with a microphone, a USB interface, or a connected Bluetooth speaker are present, the device may have selected that source. Disconnect the accessory and try again. Speak near the microphone for 3 seconds to confirm that it captures sound. Then play a sustained note, such as the guitar's A string, at an approximate frequency of 110 Hz, without hitting it hard.

Third, reduce noise for 30 seconds. Turn off the fan, television, and metronome. Move the phone away from a speaker to prevent feedback. In a room with other people, ask for silence during a single note. If you are in a very echoey room, move the device closer to the instrument, but keep at least 15 centimeters of distance so you do not overload the microphone.

If the tuner displays an unstable frequency, the cause may be the environment, the microphone, or your playing. The result depends on the device's microphone and does not replace the ear of an experienced musician. A note played with a very hard pick attack can produce harmonics and make the initial reading difficult. Try again with medium intensity and a note sustained for 2 seconds.

If it still does not work, write down which device you used, which browser you opened, whether the permission appeared, and which audio input was connected. Also say whether the problem occurs with every note or only one. A description such as “I played 82.41 Hz on the open sixth string and the screen did not react” is more useful than “it does not work.”

Run this procedure now: 1) close audio applications; 2) allow microphone access; 3) reload the page; 4) play one string for 3 seconds; 5) repeat with another string; 6) write down the result of each attempt. If the first string fails and the second works, report that difference.

Start with the page address and your objective. For example: “I am using the tuner to check the guitar's sixth string before practicing a country song, but the indicator does not move.” Then provide the device, system, and browser. “Samsung Galaxy A54 phone, Android 14, Chrome 122, and internal microphone” gives a clear starting point. If you do not know the version, write only the model and browser name.

Include the steps you followed in order. Say whether you authorized the microphone, reloaded the page, tested another note, and repeated the procedure in another browser. For a rhythm problem, report the tempo, such as 60, 72, or 96 BPM, the device used, and what happened after 4 or 8 measures. For a content question, copy the page title, the exact passage, and explain why it seems incorrect.

Report the result without excessive interpretation. “The screen displayed E2 for 1 second and then stopped” is more helpful than “the tuner got confused.” If the error occurs only under one condition, describe it: B string, USB input, Firefox browser, portrait orientation, or a device with Bluetooth headphones connected.

A screenshot can help, as long as it does not show your phone number, email, full name, or other personal data. If the error involves audio, send a short file and identify when the failure occurs, such as “the sound begins at 00:02 and the reading disappears at 00:07.” Do not send passwords, documents, banking information, or third-party information. Consult the privacy policy before attaching anything.

If your message concerns a site rule, read the terms of use. For questions about the team, editorial approach, or project goals, the about Cantivy page explains the context. These links keep you from repeating a question that has already been answered.

Before sending, check this list of 6 items: page address, device, system, browser, steps taken, and observed result. If one item is missing, add a line. A message containing this information usually allows for more direct triage.

Support messages receive a reply within 2 business days. This timeframe applies to questions about tools, browser permissions, and usage problems submitted with the basic information. If you write on a Saturday, Sunday, or holiday, the count begins on the next business day. A message sent on Friday after business hours may begin counting on the following Monday.

Reports that require reproducing the error may take up to 5 business days. This happens when it is necessary to test different combinations of device, browser, microphone, system, and connection. An error that appears only in one specific version should not be handled with a guess. I prefer to confirm the behavior before advising you.

Editorial correction requests receive an initial reply within 5 business days. The review may take longer when it involves a historical source, music theory, copyright, or comparison between versions of a recording. You will receive confirmation that the message was received when it includes the page, passage, and justification.

Press, partnership, and educational-use requests also receive an initial reply within 5 business days when they arrive complete. The reply may be a confirmation, an additional question, or an indication that the format is not a fit for the site. This timeframe does not mean automatic approval of the proposal.

If you do not receive a reply after the deadline, resend the message in the same subject line and include the date of the first contact. Avoid sending five identical messages in a row. This separates the history and may delay review. If there is a privacy risk or publication of personal data, indicate that in the first line.

To track the deadline today, write down the date and time you sent the message. For a support request, set a reminder for 2 business days later. For a correction, press inquiry, partnership, or school request, set the reminder for 5 business days later.

You may request a correction to musical, technical, or historical information. Send the page link, the passage that needs review, and a verifiable source. A book with its author and edition, an academic article with a citation, a manufacturer's manual, an identified interview, or an official recording helps more than a general comment. Also explain what wording you suggest and why it is more appropriate.

Use a source that another person can consult. For an instrument, provide the brand, model, and manual page. For historical information, provide the author, title, publisher, and year. For a recording, provide the artist, track, album, and release year. These 4 details reduce the chance of confusing versions, reissues, or different arrangements.

Do not request a change to an analysis simply because it presents a different reading. A I–V–vi–IV progression, for example, may appear in country, worship music, pop, and blues with different functions depending on the key, arrangement, and melody. In that case, describe the disagreement. A factual correction is different from an aesthetic preference.

When the subject involves a person, band, church, school, or company, send the request with identification and supporting grounds. If you directly contest a published statement, the responsible party may present a response proportional to the passage in question. This space is not for publishing complete lyrics, full chord charts, or copyrighted material. You may send an analysis, reference, harmonic progression, or the minimum excerpt needed to locate the problem.

After review, Cantivy may correct the text, add an editorial note, or explain why it kept the wording. Not every request results in a change, but every well-supported request receives an evaluation. To learn who writes here and understand the editorial responsibility, consult the authorship page.

To submit a request today, copy the article address, paste the paragraph in question, add the source, and write your suggested wording in up to 5 lines. Separate verifiable facts from opinions about style, tone, or interpretation.

For press inquiries, send the outlet name, story topic, deadline, and participation format. Say whether you need an interview about music production, instrument practice, browser-based tools, or music education. Include any questions that have already been defined. Tell us whether the interview will be by text, audio, video, or call, and indicate the expected duration, such as 20 or 40 minutes.

For partnerships, provide the project, audience, expected period, and what you expect from Cantivy. Describe the deliverable with concrete numbers: one article, one 60-minute workshop, one test with 20 students, or one mention in a newsletter. Include the decision deadline and the channels involved. Do not send a proposal without explaining its connection to music, study, or production.

If the proposal includes sponsored content, product promotion, or brand use, describe that relationship in the first message. Include the format, number of deliverables, publication period, and who approves the material. Cantivy needs to assess the editorial fit before confirming any participation.

Schools, teachers, and community projects may write about educational use. Tell us the age range, approximate number of participants, available devices, instrument type, and whether the activity requires continuous internet access. Since the tools work in the browser with the page open, test them beforehand in a room with the same type of connection and microphone.

For a 45 to 60-minute class, state how many students will share each device and whether headphones, speakers, or external microphones will be available. A class of 20 students with 5 phones requires a different activity structure from a class with 20 individual devices. These details help evaluate the proposed use without assuming the school's setup.

Press, partnership, and educational-use requests receive a reply within 5 business days when they arrive complete. The response may be a confirmation, an additional question, or an indication that the format is not a fit for the site. For institutional information, combine your proposal with the guidance on the about Cantivy page.

Today, prepare the proposal in 7 lines: who is writing, what the project is, who will participate, what deliverable you expect, when it would happen, which resources already exist, and what response you need. This format makes the evaluation faster.

• Reload the page and allow microphone access before requesting support.
• Close calls, recorders, meetings, and other applications that use audio.
• Provide the device, system, browser, tool, steps taken, and observed result.
• For the tuner, test one string at a time for 2 to 4 seconds and record the displayed note or frequency.
• Send only necessary screenshots and audio, without unnecessary personal data.
• Allow up to 2 business days for support and up to 5 business days for complex errors or editorial corrections.
• For a correction, include the exact passage, a verifiable source, and your suggested wording.
• For a right of reply, identify the contested statement and send a response proportional to the passage.
• For press, partnership, or school requests, provide the topic, audience, deadline, format, and available resources.
• Write down the sending date and resend in the same subject line only if the stated deadline passes.