Basic flow
Horizon · Japanese-English
Convert conversations that naturally move between Japanese and English into structuredtext for meetings, interviews, customer conversations, podcasts, media, voiceapplications, search, analytics, and AI workflows. Use Shunya Horizon Universalfor Japanese and English speech, and evaluate Horizon Code-Switch forconversations where both languages naturally appear inside the same interaction.
この meeting は tomorrow に変更できますか?
Japanese + English inside one real conversationJapanese-English speech to text
Business and technology conversations do not always stay in one language. Shunya’s broader Horizon platform supportsboth Japanese and English speech recognition, while Horizon Code-Switch is designed for conversationsthat naturally change languages within the same sentence or interaction.
この meeting は tomorrow に変更できますか?
Payment status を確認してください。
新しい API integration について説明します。
Basic flow
Why mixed-language recognition matters
An English-only recognition path needs to handle the Japanese speech surrounding those words. HorizonCode-Switch is instead designed for speech that changes languages inside the same interaction.
次の meeting は Friday に変更します。
Important support note
However, it does not explicitly name Japanese + English as a dedicated production Code-Switch pair.Confirm supported pairs in the deployment you plan to use.
Horizon supports
Safe positioning
Try it yourself
Try examples such as:
Meeting は tomorrow の 10 AM です。
Payment confirmation がまだ届いていません。
この account の status を確認してください。
API integration は next week に開始します。
Order number 48217 を check してください。
Why mixed-language recognition matters
Horizon Code-Switch is instead designed for speech that changes languages inside the same interaction.
Traditional multilingual processing may try
Horizon Code-Switch
English technical vocabulary
Production evaluation should include the actual vocabulary used by the business.
Example
Japanese writing system
Written Japanese commonly combines Kanji, Hiragana, and Katakana inside the samelanguage. Japanese-English conversations may therefore combine Kanji, Hiragana, Katakana, and Latin-script English terminology.
Japanese writing system
This makes script handling an important part of mixed-language transcription quality.
Example
Horizon Code-Switch
Horizon Code-Switch is designed for conversations that naturally switch betweenlanguages inside the same sentence or interaction.Verify the current configuration before making a pair-specific deployment.
Important
Code-Switch handles mixed speech.
Important
It does not specifically name Japanese + English as a supported production pair.
Mixed speech
Real-time Japanese-English transcription
Horizon supports real-time speech recognition through WebSocket streaming.For mixed Japanese-English speech, validate the correct model routing beforedeployment.
Live audio
Streaming audio
Horizon supports live audio representations including int16 PCM, float32, μ-law, and A-law.This supports both general real-time audio and telephony-oriented workflows.
Live audio
Batch transcription
For recorded speech, Horizon returns a complete transcript, then optional intelligence.
Audio
Streaming vs batch
Exact Japanese-English mixed-language routing should be verified against the active Code-Switch configuration.
| Requirement | Streaming | Batch |
|---|---|---|
| Live Japanese-English | ||
| Recorded Japanese-English | ||
| Partial Transcript | ||
| Complete Transcript | ||
| Voice Applications | ||
| Live Meetings | ||
| Post-call Intelligence | ||
| WebSocket | ||
| HTTP API |
Customer support
The STT layer provides speech understanding. The business system remains responsible for actual account and customer actions.
Customer audio
Voice applications
Horizon provides machine-readable input for search, LLMs, agents, CRM, analytics,and automation. For dedicated Japanese-English Code-Switch behavior, validate deployed pair support.
User speaks
Horizon
Transcript
LLM / Agent
Application response
Where the mix shows up
Global meetings
The meeting-transcription source positions Horizon Universal for global meetings and Horizon Code-Switch for mixed-language meetings.
Meeting → Appropriate Horizon model → Transcript → Speakers → Timestamps → Search / Notes / AI
Interviews
Possible use cases
Interview → Horizon → Transcript → Speaker labels → Timestamps → Search / Analysis
Podcasts
Horizon Universal includes Japanese for global-language podcasts. For mixed-language podcasts, it separately recommends Horizon Code-Switch. Japanese is explicitly listed under global podcast coverage. Mixed-language routing should follow the current supported configuration.
Japanese-English podcast → Horizon Universal / Code-Switch as appropriate → Transcript → Speakers → Timestamps → Summary → Publishing / Search / AI
Speaker diarization
Horizon supports speaker diarization across its broader platform.
次の meeting は Friday です。
Okay, I will update the schedule.
ありがとうございます。
Japanese-English meeting workflow
This follows the architecture supported in the meeting transcription workflow.
Speaker identification
Registered voice profiles can be combined with diarization to identify known speakers. Unknown speakers canremain anonymous labels. Speaker identification should not be treated as legal identity verification.
Before
I'll update the schedule.
After
I'll update the schedule.
Word-level timestamps
Verbose transcription output can include start time, end time, and confidence for individual words.
| Field | Verbose output |
|---|---|
| Start time | |
| End time | |
| Confidence |
Search
Confidence scores
Mixed Japanese-English conversations may contain names, acronyms, product names, technical terminology, addresses,and numbers. Confidence scores can support review. They should not be treated as guarantees of correctness.
They should not be treated as guarantees of correctness.
Numbers and references
Production evaluation should include the actual vocabulary used by the business.
Order number 48217 を check してください。
Audio input
Horizon batch transcription supports WAV, MP3, M4A, OGG, FLAC, and WebM.
Video transcription
The language and conversation determine the model - not the MP4, MOV, or other container. For multilingual video,use the appropriate multilingual/Code-Switch workflow. Horizon supports multilingual and mixed-language video transcription. Visual information requires separate visual analysis when needed.
Japanese-English video workflow
Multilingual meeting intelligence
The meeting workflow supports optional speaker identification, emotion, intent,sentiment, summary, keyterms, and redaction.
Meeting
Intent detection
Understand what a speaker wants. Intent is part of Shunya's optional intelligence layer.
Transcript → Intent → Workflow
Sentiment analysis
Add post-call context. Shunya supports sentiment analysis among optional transcription intelligence features. Sentiment should supplement the transcript rather than replace it.
Emotion analysis
Add another conversation signal. Emotion detection is part of the broader Horizon intelligence stack. Emotion should be treated as inferred metadata.
Summarisation
Reduce long bilingual conversations. Summarisation is part of Shunya's supported optional intelligence layer.
Audio → Transcript → Summary → Search / CRM / Knowledge Base
Keyterms
Preserve important domain terminology. Keyterm handling is available in Shunya's batch intelligence workflows.
Raw transcript → Keyterm processing → Consistent downstream terminology
Redaction
Mask configured sensitive terms. Shunya supports custom redaction within supported transcription workflows.
Sensitive information → Configured redaction → Masked transcript
Developers
The broader Horizon API supports recorded audio through HTTP transcription and liveaudio through WebSocket transcription. POST /v1/audio/transcriptions is supportedacross the meeting and video workflows. Use the current supported Code-Switchrouting only after confirming pair availability.
RECORDED AUDIO
HTTP transcription
BATCH ENDPOINT
POST /v1/audio/transcriptionsChoose the right model
Shunya supports this model-family approach across Voice to Text workflows.
Japanese-first
Use the appropriate Horizon Universal configuration for Japanese.
English-first
Use Horizon Universal.
Mixed Japanese + English
Horizon Code-Switch where the active configuration supports the pair. Use the current supported mixed-language/Code-Switch route only after verifying pair support.
Clinical speech
Japanese and English on one STT platform
This means a product can support Japanese and English without maintaining entirely separate speech platforms.Shunya positions Horizon Universal for broad multilingual transcription across global languages.For mixed-language speech, the Code-Switch family should be evaluated where supported.
Global speech
Japanese-English is not translation
A transcription workflow should first preserve that utterance as speech-to-text output. It should not automaticallyturn the whole sentence into only Japanese or only English unless a translation step is intentionally added.
Payment status を確認してください。
Separate functions.
STT
Translation
Evaluate before production
Customer calls, meetings, phone audio, product vocabulary, and background noise shoulddrive your evaluation.
Test real audio
Pair-support caution
Horizon Code-Switch handles speech that changes language within the same conversation.Confirm that your deployed configuration supports Japanese-English before you go live.
Safe production process
Built for production
Requirement | Horizon
| Requirement | Support |
|---|---|
| Japanese Speech Recognition | |
| English Speech Recognition | |
| Horizon Universal | |
| Code-Switch Platform | |
| Dedicated Japanese-English Pair | Verify active configuration |
| Streaming Transcription | |
| Batch Transcription | |
| Speaker Diarization | |
| Speaker Identification | |
| Word-level Timestamps | |
| Confidence Scores | |
| Multilingual Meetings | |
| Global Podcasts | |
| Multilingual Video | |
| Intent Detection | |
| Sentiment Analysis | |
| Emotion Analysis | |
| Summarisation | |
| Keyterms | |
| Redaction | |
| API Integration | |
| Self-hosted Deployment |
Questions
It converts conversations containing Japanese and English speech into structured written text.
Yes. Japanese is explicitly included in the broader Horizon multilingual/global language network.
Yes. English is supported by Horizon Universal.
Yes. Horizon Code-Switch is designed for speech that naturally changes languages inside the same sentence or interaction.
Confirm Japanese + English as a supported production pair in your deployment.
Yes. The current Code-Switch configuration should be checked before making a dedicated Japanese-English routing.
Use the appropriate Horizon Universal configuration for Japanese.
Use Horizon Universal.
Use the current supported mixed-language/Code-Switch route only after verifying pair support.
Horizon supports real-time WebSocket transcription. Exact mixed-pair routing should be validated.
Horizon supports batch transcription for recorded audio. Mixed-language configuration should be confirmed.
The platform supports global and multilingual meetings, while Code-Switch is used for mixed-language meetings.
Japanese is explicitly part of Horizon Universal's global podcast workflow, while mixed-language podcasts can use Code-Switch where supported.
Yes. Shunya supports video transcription by extracting the audio track from supported containers.
Yes. Speaker diarization can label transcript segments by speaker.
Yes. Registered voice profiles can be combined with speaker identification.
Yes. Verbose output can include start time, end time, and confidence.
Yes. Intent is part of the optional intelligence layer.
Yes. Sentiment analysis is supported.
Yes. Emotion detection is supported.
Yes. Summarisation is supported in applicable batch workflows.
Yes. Keyterm handling is available in batch transcription workflows.
Yes. Custom redaction is supported.
Shunya does not publish a dedicated Japanese-English word error rate. Test it on your own audio.
No. It should not be re-labelled as Japanese-English Code-Switch performance.
No. STT converts speech into text. Translation changes the language and is a separate workflow.
Get started
Global teams do not always stay in one language. A meeting may begin in Japanese. A product term may be English. Atechnical discussion may move between both. Use Horizon Universal for Japanese and English speech, and evaluatethe Code-Switch route for mixed Japanese-English conversations. Test real meetings, interviews, podcasts, customerconversations, product terminology, names, acronyms, multiple speakers, and real production audio.