VibeVoice ASR Streaming 7B vs Hy3
At a Glance
| Compare | VibeVoice ASR Streaming 7BMicrosoft | Hy3Tencent |
|---|---|---|
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | Not reported | $0.0825Openrouter ↗ · Sep 22, 2026 |
| Output priceFrom · USD / 1M tokens | Not reported | $0.33Openrouter ↗ · Sep 22, 2026 |
| Context windowMaximum documented tokens | Not reported | 262K |
| Model facts checked | Sep 2, 2026View model evidence → | Aug 28, 2026View model evidence → |
Token prices are the lowest available sourced USD rates; input and output may use different providers. Cost ranking estimates output spend on LiveBench, not a full request bill. Ranking methodology →
Available Benchmarks
Side-by-Side Facts
| Field | VibeVoice-ASR-Streaming-7B | Hy3 |
|---|---|---|
| Developer | Microsoft | Tencent |
| Family | Vibevoice ASR Streaming | Hy3 |
| Model | VibeVoice-ASR-Streaming-7B | Hy3 |
| Version | VibeVoice-ASR-Streaming-7B | Hy3 |
| Lifecycle | active | active |
| Released | 2026-09-03 | Unknown |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Audio | Text |
| Output modalities | Text | Text |
| Context window | Unknown | 262K |
| Total parameters | 8.7B | 298.8B |
| Active parameters | Unknown | 21B |
| License | mit | apache-2.0 |
| Open weights | Yes | Yes |
| API available | No | Yes |
| Self-hostable | Yes | Yes |
| Provider access | Unknown | Deepinfra (Standard), Hugging Face (Standard), Openrouter (Standard) |
| Capabilities | diarization, hotwords, multilingual, streaming, transcription | chat, generation, tools |
| Streaming chunk | 22 frames | Unknown |
| Streaming lookahead | 4 frames | Unknown |
| Supported languages | Chinese, English, French, German, Italian, Japanese, Korean, Portuguese, Russian, Spanish | Unknown |
| Target sample rate | 24000 Hz | Unknown |
VibeVoice ASR Streaming 7B Capabilities
Hy3 Capabilities
Primary Evidence
Sources and Freshness
Questions
VibeVoice ASR Streaming 7B vs Hy3 FAQs
Is VibeVoice ASR Streaming 7B or Hy3 better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both VibeVoice ASR Streaming 7B and Hy3, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, VibeVoice ASR Streaming 7B or Hy3?+
Only Hy3 has a directly sourced input price: $0.0825 per million tokens. Only Hy3 has a directly sourced output price: $0.33 per million tokens.
Which has a larger context window, VibeVoice ASR Streaming 7B or Hy3?+
Neither model has a larger sourced context window in this comparison. VibeVoice ASR Streaming 7B is — and Hy3 is 262K.
Which performs better in benchmarks, VibeVoice ASR Streaming 7B or Hy3?+
There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.
Can VibeVoice ASR Streaming 7B or Hy3 be self-hosted?+
Both models have the same recorded self-hosting status: supported. VibeVoice ASR Streaming 7B is open weight; Hy3 is open weight.
Can VibeVoice ASR Streaming 7B and Hy3 understand images?+
VibeVoice ASR Streaming 7B is not documented with image input; Hy3 is not documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, VibeVoice ASR Streaming 7B or Hy3?+
Neither has a larger sourced maximum output. VibeVoice ASR Streaming 7B is — and Hy3 is —.
Do VibeVoice ASR Streaming 7B and Hy3 support reasoning and tool use?+
VibeVoice ASR Streaming 7B: none of these features are definitively sourced. Hy3: tool calling. Feature support does not establish relative quality.
Which is available from more inference providers, VibeVoice ASR Streaming 7B or Hy3?+
VibeVoice ASR Streaming 7B has 0 sourced provider routes; Hy3 has 3, so Hy3 has broader tracked availability.
Which offers better value, VibeVoice ASR Streaming 7B or Hy3?+
There is no universal value winner. Compare the input and output prices above with the matched benchmark result for your workload: cheaper tokens can be offset by different quality, token usage, latency, or provider availability.