Get the Most Out of VORA

 Recommended External Microphones

Tested and ranked by the VORA team for meeting-room use. All prices are approximate USD retail (February 2026).

 Placement & Room Tips

• Distance: Keep the mic 15–30 cm from your mouth. Too far = noise floor dominates; too close = plosives distort.
• Angle: Point a cardioid microphone directly at your mouth, not at the ceiling or screen.
• Room acoustics: Soft surfaces (curtains, carpets, bookshelves) absorb echo. A bare concrete room will produce noticeable reverb that confuses STT engines.
• Background noise: Close windows, mute fans if possible. Even a laptop cooling fan at 45 dB can drop accuracy by 5–15%.
• Bluetooth latency: Bluetooth mics add 100–200 ms of latency. VORA handles this gracefully, but wired USB is always preferable for accuracy.

 In-App Audio Settings

Open Settings → Audio Processing in VORA:

• Noise Suppression (ON by default): Reduces background hum. Disable only if it causes artefacts on your mic.
• Echo Cancellation (ON by default): Essential if your speakers are near the mic. Disable only for headphone-only setups where there's no echo risk.

 Gemini API Key (Primary AI)

Gemini handles AI question detection, meeting summaries, and text correction.

 Groq API Key (Fast Correction)

Groq runs Llama 3.3 70B on dedicated LPU hardware — blazing fast and completely free.

 OpenRouter API Key (Labs Only)

Used in the OpenRouter Parallel Lab to call three free LLMs simultaneously.

Why Context Matters

The AI corrector receives your speech transcript as raw text. Without context it must guess whether "프로포폴" is a drug name or a mishearing of "프로포절" (proposal). With the right context it gets it right every time.

VORA injects your context into every correction and summary prompt, behaving exactly like telling a human note-taker "this is a pharmaceutical regulatory meeting — watch for these terms."

 Meeting Topic / Project Name

Found in Settings → Meeting Context → Topic / Project Name.

Write 1–3 sentences describing:

• What industry or domain the meeting is about
• The specific project or product being discussed
• Any key participants or roles

 Priority Terms

Found in Settings → Meeting Context → Priority Terms.

Enter a comma-separated list of proper nouns, acronyms, product names, or technical terms that the AI should recognise and preserve exactly:

• Up to 30–40 terms work best. Too many dilute the signal.
• Mix Korean and English freely — the model handles both.
• Include common mis-transcriptions the system makes (e.g. "안드로이드" → "Android").

 Meeting Category

Select the closest category in Settings → Meeting Category. This applies a pre-tuned persona to the AI:

• General — balanced correction, no domain bias
• IT / Software — tech terms, English-Korean code-switching
• Medical / Pharma — clinical terminology, drug names
• Legal — formal Korean / legal clauses
• Finance — financial jargon, numerical precision
• Marketing — brand names, campaign language

Gemini API — Free vs Paid

Groq API — Free Tier Limits

For a typical 60-minute meeting with corrections every 3–5 seconds, VORA generates ~600–800 Groq requests — well within the 14,400/day limit.

OpenRouter — Free Model Limits

Free models on OpenRouter are subject to:

• 20 requests / minute per model
• 200 requests / day per model (with ≥$10 credits on your account)
• 50 requests / day per model (no credits / new account)

The OpenRouter Lab is intended for experimentation, not continuous 60-minute meetings. Use Groq for production correction and OpenRouter for side-by-side model comparison.

 Estimated Monthly Cost Examples

🎙️ Speech not being recognised?

• Check that your browser has microphone permission (click the lock icon in the URL bar).
• Open your OS audio settings and confirm the correct mic is set as default input.
• Try Chrome or Edge — the Web Speech API has the best support in Chromium browsers. Firefox and Safari have limited support.
• Reload the page and grant mic permission again if the indicator stays red.

🤖 AI correction not working?

• Open Settings and check the API status indicator — it should be green.
• If it shows "API key not set", re-enter your key and save.
• If it shows a 429 error, you've hit the rate limit. Wait 60 seconds or switch to Groq fast mode.
• Free tier Gemini keys from newly created Google accounts may be geo-restricted. Try creating the key on a desktop browser rather than mobile.

📝 Correction quality is poor?

• Fill in the Meeting Context and Priority Terms fields. This is the single biggest improvement lever.
• Select the correct Meeting Category (e.g., "Medical" for clinical meetings).
• Use the Language Selector to set the primary recognition language. Mixed Korean/English meetings should use ko-KR as the primary language.
• Reduce the Correction Interval to 2–3 seconds for fast-paced conversations; increase to 8–10 seconds for slower, deliberate speech to save API calls.

📊 Summary is missing or empty?

• Summaries require at least 50 words of transcript. Short meetings may not generate a summary automatically.
• Click Export Minutes manually to force a summary generation at any time.
• Ensure your Gemini key has remaining quota — Groq cannot generate summaries (correction only).

⌨️ Keyboard Shortcuts