orklev2-coreaudio

Explain Orkid's CoreAudio backend and AudioUnit I/O callback behavior on macOS.

35|16|Updated Feb 10, 2013
One-click install
npx skills add https://github.com/tweakoz/orkid --skill orklev2-coreaudio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orklev2-coreaudio
Source: https://github.com/tweakoz/orkid/tree/main/.claude/skills/orklev2-coreaudio
Command: npx skills add https://github.com/tweakoz/orkid --skill orklev2-coreaudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a focused reference for understanding and troubleshooting Orkid's CoreAudio backend on macOS so developers can trace how audio is captured, processed, and played back through the AudioUnit graph and related systems.

Core Features & Use Cases

  • Detailed mapping of core components such as CoreAudioDevice, AuContext, AudioUnit graph, and I/O callbacks to their source files for quick navigation.
  • Explanation of data flow between HAL input/output, LayerFragment/StereoFragment pools and queues, and the Singularity synth compute path for accurate debugging and performance tuning.
  • Use cases include diagnosing audio glitches, configuring sample rate and buffer sizes, and integrating or testing the Singularity synth with macOS audio devices.

Quick Start

Ask for an explanation of how Orkid's CoreAudioDevice constructs the AudioUnit graph and how the Singularity synth buffers are delivered to the HAL output.

Frequently Asked Questions about orklev2-coreaudio

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does the Orkid CoreAudio backend handle AudioUnit I/O callbacks on macOS?

The Orkid CoreAudio backend uses an AudioUnit graph to route audio through HAL input/output and I/O callbacks. It maps CoreAudioDevice and AuContext setup directly to source files for tracing how audio is captured and played back on macOS.

How do I diagnose audio glitches in the Singularity synth integration with CoreAudio?

To diagnose audio glitches in the Singularity synth, trace the synth compute path and LayerFragment/StereoFragment pool queues. Checking buffer sizing and sample rate configuration helps identify data flow bottlenecks between the synth and HAL output.

What is the best way to configure sample rates and buffer sizes for an AudioUnit graph on macOS?

Configuring sample rates and buffer sizes for an AudioUnit graph involves examining the AuContext setup and HAL output parameters. The Orkid audio codebase provides specific mappings to these components for accurate performance tuning and audio processing.

Can I trace the HAL input/output data flow through the Singularity synth compute path in Orkid?

Yes, you can trace HAL input/output data flow through the Singularity synth compute path. The backend details how LayerFragment and StereoFragment pools and queues deliver audio buffers from the synth to the HAL output for playback.

Why do I need to understand AuContext setup when working with the Orkid audio codebase?

Understanding AuContext setup is necessary because it manages the AudioUnit graph construction and I/O callback behavior. Mapping this architecture to source files allows developers to navigate the CoreAudio backend and troubleshoot audio device integration effectively.

Are there limitations when debugging CoreAudio AudioUnit graphs with the Orkid backend?

Debugging CoreAudio AudioUnit graphs with the Orkid backend is focused on macOS environments. It specifically addresses Singularity synth integration, HAL input/output, and fragment pool queues, but does not cover cross-platform audio systems outside this scope.