fix(audio,flutter): restore VAD on iOS and fix Android build
- Add iOS to voiceActivityTransmitAvailable — iOS has CoreML Silero VAD pipeline (AppleCoreMlVadWorker) but was excluded by DEC-030 gating that predated the CoreML integration - Inline deleted VadWorkerPolicy in android_voice_unit.rs — PR #37 removed the enum from vad/mod.rs but missed updating Android
This commit is contained in:
@@ -65,13 +65,12 @@ List<ButtonSegment<rust.BridgeTransmitMode>> transmitModeSegmentsFor({
|
||||
/// True when this host advertises VAD transmit per DEC-030.
|
||||
///
|
||||
/// The desktop Silero ONNX + WebRTC fallback ships on Windows and
|
||||
/// Linux; the Android Oboe + WebRTC path covers Android. iOS and
|
||||
/// macOS still rely on the Apple VoiceProcessingIO unit and have no
|
||||
/// Chanora-owned VAD pipeline, so the bridge cannot honour the
|
||||
/// voice-activity transmit mode there.
|
||||
/// Linux; the Android Oboe + WebRTC path covers Android; iOS uses the
|
||||
/// Apple CoreML Silero VAD pipeline via `vad::apple_coreml`. macOS is
|
||||
/// still gated until its VAD pipeline is confirmed.
|
||||
bool get voiceActivityTransmitAvailable {
|
||||
if (kIsWeb) return false;
|
||||
return Platform.isWindows || Platform.isLinux || Platform.isAndroid;
|
||||
return Platform.isWindows || Platform.isLinux || Platform.isAndroid || Platform.isIOS;
|
||||
}
|
||||
|
||||
/// Android hardware/WebRTC selector segments.
|
||||
|
||||
Reference in New Issue
Block a user