Skip to content
AskCc
Menu
Getting Started
Quick StartSystem RequirementsAudio & Permissions
Before the Interview
Interview ProfileAdd a Resume, JD, and Project MaterialPersonal Knowledge BaseOfficial Question BanksSkill Profiles
During the Interview
Live Interview AssistanceLive OverlayScreen Questions and Exam Assistance
Account & Policies
SettingsPlans & BillingPrivacy & Data
Help & Reference
Keyboard ShortcutsFAQHelp & SupportChangelog

Audio & Permissions

Select microphone and system output devices, test both channels, and fix preflight permission failures.

Why must both audio paths work before an interview?

Section titled “Why must both audio paths work before an interview?”

AskCc uses system audio for the interviewer’s voice and the microphone for your voice. On both macOS and Windows, the microphone, screen-capture capability, and system-audio path must pass preflight. A failure in any required path prevents the interview from starting.

How do I select and test audio devices?

Section titled “How do I select and test audio devices?”

Open Settings → Audio & Permissions:

  1. Under Microphone, select the input device you will use.
  2. Under System Audio, select the output used by the meeting app, or keep Follow system output.
  3. Start each test separately.
  4. Speak into the microphone and play sound through the meeting app or system.
  5. Confirm that both meters respond, then stop the tests before starting an interview.

You do not need BlackHole, Soundflower, VB-CABLE, or another virtual-audio driver. Prefer the system devices and AskCc’s built-in tests.

How are macOS and Windows permissions different?

Section titled “How are macOS and Windows permissions different?”

The first-run guide requests microphone, screen recording, and system audio permissions. You may skip the guide, but you must grant the permissions before an interview can start.

If access is missing:

  1. Open System Settings → Privacy & Security.
  2. Allow AskCc under Microphone.
  3. Allow AskCc under the screen and system-audio recording settings.
  4. Quit AskCc completely, reopen it, and test again.

AskCc tries to open the relevant system page. If macOS does not navigate there, find it manually.

Why is there no activity in a test?

Section titled “Why is there no activity in a test?”
  • No microphone meter: check mute state, input selection, system permission, and apps that may hold the microphone exclusively.
  • No system-audio meter: make sure the meeting app is playing through the output selected in AskCc.
  • No activity after switching devices: stop the test, select again, and restart AskCc if needed.
  • Noise or echo: use headphones, lower speaker volume, and avoid multiple active microphones.
  • Tests pass but preflight fails: reopen Audio & Permissions, verify permission state, and retry. If it continues, record the OS version and device names for support.

How can I get more stable transcripts?

Section titled “How can I get more stable transcripts?”
  • Use headphones or a wired headset to reduce speaker feedback.
  • Keep the meeting app and AskCc on the same system-output route.
  • Use a quiet room and a stable microphone distance.
  • Run a mock session with the same meeting app before the real interview.
  • Retest after switching Bluetooth devices because the system may change input or output automatically.