PC 오디오 입출력 경로를 체계적으로 설계하고 부팅 시 자동 적용되는 스크립트를 생성합니다.
You are now my long‑term Audio Routing Automation Engineer for this exact project.
I want you to design, build, and maintain a complete, production‑ready audio‑routing system that matches my original goal.
Do the following:
Review & Refine
Re‑read the original goal and all previous instructions and suggestions.
Clarify any missing details (OS, hardware, streaming apps, latency tolerance, headless vs GUI).
Return a bullet‑list summary of what you understand the final system should do.
Design the Architecture
Draw a simple node‑routing diagram in text (inputs → intermediate nodes → outputs).
For each node: name the exact tool (e.g., PipeWire virtual sink, JACK bus, OBS audio capture, Stereo Mix, Voicemeeter, etc.).
Explain why this architecture is optimal (latency, stability, automation, resource usage).
Build Automation Scripts
Generate real, runnable scripts (bash, PowerShell, Python, or WirePlumber/Lua, depending on my OS) that:
Create the required virtual devices.
Apply the routing rules automatically on boot/login.
Optionally restart or re‑apply the routing if I tell you a device changed.
Structure each script so it can be saved as a file (e.g., ~/bin/audio-routing-init.sh) and run with a single command.
Add Error‑Handling & Idempotency
Ensure the scripts:
Check if dependencies are installed and install them if possible.
Avoid creating duplicate nodes (idempotent setup).
Log errors into a file or the terminal so I can debug.
If you cannot install packages directly, list the exact apt, brew, winget, or GUI‑install steps.
Document a Maintenance Workflow
Provide a small maintenance checklist for me:
How to stop the routing.
How to restart it.
How to regenerate configs if I change audio devices.
How to test that everything is still working.
Output Format
Use Markdown clearly:
## Architecture → node diagram and tool list.
## Installation → step‑by‑step commands.
## Scripts → each script in its own code block with a filename and a short comment.
## Maintenance → concise bullet list.
Do not summarize the whole conversation; focus only on actionable, copy‑paste‑ready content.
Now, based on my original goal and our history, show me the full architecture, scripts, and maintenance plan.당신은 이제 이 프로젝트를 위한 저의 장기적인 오디오 라우팅 자동화 엔지니어입니다. 원래 목표에 부합하는 완전하고 즉시 도입 가능한 수준의 오디오 라우팅 시스템을 설계, 구축 및 유지 관리해 주기를 바랍니다. 다음 작업을 수행하세요: 1. 검토 및 다듬기 - 원래 목표와 모든 이전 지시사항 및 제안을 다시 읽으세요. - 누락된 세부 정보(OS, 하드웨어, 스트리밍 앱, 지연 시간 허용 범위, 헤드리스 vs GUI)를 명확히 하세요. - 최종 시스템이 수행해야 한다고 이해한 내용을 요약하여 불릿 리스트로 반환하세요. 2. 아키텍처 설계 - 텍스트로 간단한 노드 라우팅 다이어그램을 그리세요 (입력 → 중간 노드 → 출력). - 각 노드에 대해 정확한 도구 이름(예: PipeWire virtual sink, JACK bus, OBS audio capture, Stereo Mix, Voicemeeter 등)을 명시하세요. - 이 아키텍처가 최적인 이유(레이턴시, 안정성, 자동화, 리소스 사용량)를 설명하세요. 3. 자동화 스크립트 작성 - 내 OS에 맞춰 실행 가능한 실제 스크립트(bash, PowerShell, Python 또는 WirePlumber/Lua)를 생성하세요: - 필요한 가상 장치를 생성합니다. - 부팅/로그인 시 라우팅 규칙을 자동으로 적용합니다. - 장치가 변경되었음을 알릴 경우 선택적으로 라우팅을 다시 시작하거나 재적용합니다. - 각 스크립트를 파일(예: ~/bin/audio-routing-init.sh)로 저장하고 단일 명령어로 실행할 수 있도록 구조화하세요. 4. 오류 처리 및 멱등성 추가 - 스크립트가 다음을 보장하도록 하세요: - 의존성이 설치되어 있는지 확인하고 가능한 경우 설치합니다. - 중복 노드 생성을 방지합니다 (멱등성 보장). - 디버깅할 수 있도록 파일이나 터미널에 오류를 기록합니다. - 패키지를 직접 설치할 수 없는 경우 정확한 apt, brew, winget 또는 GUI 설치 단계를 나열하세요. 5. 유지 관리 워크플로우 문서화 - 나를 위한 소규모 유지 관리 체크리스트를 제공하세요: - 라우팅을 중지하는 방법. - 다시 시작하는 방법. - 오디오 장치를 변경할 때 구성을 재생성하는 방법. - 모든 것이 여전히 작동하는지 테스트하는 방법. 6. 출력 형식 마크다운을 명확하게 사용하세요: - ## Architecture → 노드 다이어그램 및 도구 목록. - ## Installation → 단계별 명령어. - ## Scripts → 파일 이름과 짧은 주석이 있는 각 스크립트 코드 블록. - ## Maintenance → 간결한 불릿 리스트. 대화 전체를 요약하지 말고 바로 복사해서 붙여넣을 수 있는 실용적인 콘텐츠에만 집중하세요. 이제 나의 목표를 바탕으로 전체 아키텍처, 스크립트 및 유지 관리 계획을 보여주세요.
출처 · prompts.chat · Audio Routing Automation Engineer — 원문은 출처에 게시된 그대로이며, 권리는 원작자에게 있습니다.
Gemini로 실행한 결과입니다. 입력 항목에는 국내 환경의 예시값을 적용했습니다(AI 생성 — 사실 확인 필요).
You are now my long‑term Audio Routing Automation Engineer for this exact project.
I want you to design, build, and maintain a complete, production‑ready audio‑routing system that matches my original goal.
Do the following:
Review & Refine
Re‑read the original goal and all previous instructions and suggestions.
Clarify any missing details (OS, hardware, streaming apps, latency tolerance, headless vs GUI).
Return a bullet‑list summary of what you understand the final system should do.
Design the Architecture
Draw a simple node‑routing diagram in text (inputs → intermediate nodes → outputs).
For each node: name the exact tool (e.g., PipeWire virtual sink, JACK bus, OBS audio capture, Stereo Mix, Voicemeeter, etc.).
Explain why this architecture is optimal (latency, stability, automation, resource usage).
Build Automation Scripts
Generate real, runnable scripts (bash, PowerShell, Python, or WirePlumber/Lua, depending on my OS) that:
Create the required virtual devices.
Apply the routing rules automatically on boot/login.
Optionally restart or re‑apply the routing if I tell you a device changed.
Structure each script so it can be saved as a file (e.g., ~/bin/audio-routing-init.sh) and run with a single command.
Add Error‑Handling & Idempotency
Ensure the scripts:
Check if dependencies are installed and install them if possible.
Avoid creating duplicate nodes (idempotent setup).
Log errors into a file or the terminal so I can debug.
If you cannot install packages directly, list the exact apt, brew, winget, or GUI‑install steps.
Document a Maintenance Workflow
Provide a small maintenance checklist for me:
How to stop the routing.
How to restart it.
How to regenerate configs if I change audio devices.
How to test that everything is still working.
Output Format
Use Markdown clearly:
## Architecture → node diagram and tool list.
## Installation → step‑by‑step commands.
## Scripts → each script in its own code block with a filename and a short comment.
## Maintenance → concise bullet list.
Do not summarize the whole conversation; focus only on actionable, copy‑paste‑ready content.
Now, based on my original goal and our history, show me the full architecture, scripts, and maintenance plan.Architecture
[마이크/게임/디스코드] → [PipeWire Virtual Sinks] → [OBS / 헤드폰 모니터링]
Installation
sudo apt update && sudo apt install -y pipewire pipewire-pulse wireplumber pipewire-audio-client-libraries
Scripts
~/bin/audio-routing-init.sh
#!/bin/bash
# PipeWire 가상 오디오 노드 자동 생성 및 멱등성 보장 스크립트
LOG_FILE="$HOME/audio-routing.log"
exec 2>> "$LOG_FILE"
# 1. PipeWire 서비스 확인
if ! systemctl --user is-active --quiet pipewire; then
echo "$(date): PipeWire 실행 중 아님" >> "$LOG_FILE"
exit 1
fi
# 2. Game_Sink 생성 (중복 생성 방지)
if ! pactl list sinks short | grep -q "Game_Sink"; then
pactl load-module module-null-sink sink_name=Game_Sink sink_properties=device.description="Game_Audio_Sink"
echo "$(date): Game_Sink 생성 완료" >> "$LOG_FILE"
fi
# 3. Voice_Sink 생성
if ! pactl list sinks short | grep -q "Voice_Sink"; then
pactl load-module module-null-sink sink_name=Voice_Sink sink_properties=device.description="Voice_Audio_Sink"
echo "$(date): Voice_Sink 생성 완료" >> "$LOG_FILE"
fiMaintenance
chmod +x ~/bin/audio-routing-init.sh && ~/bin/audio-routing-init.shsystemctl --user restart pipewire && ~/bin/audio-routing-init.shpactl list sinks shortcat ~/audio-routing.logmopick 개선안
원문을 그대로 넣으면 AI 가 매번 다르게 답하거나 중요한 부분을 빠뜨릴 수 있습니다. 개선안은 원문의 뜻과 언어는 그대로 두고 역할 · 바꿔 넣을 입력 칸 · 결과 형식 · 지킬 조건을 보완해 다시 쓴 버전입니다. 원문과 같은 곳(ChatGPT · Claude 등)에 그대로 붙여 넣어 쓰면 됩니다.
AI 평가 점수 — 명확성 · 구체성 · 결과 형식 · 재사용성 기준(100점)
작업 순서레슨 07 배우기 ›
원문 · 없음작업 순서가 정해져 있지 않아 AI 가 순서를 스스로 정해야 했습니다.
개선 · 4단계
이 개선안에 쓰인 기법 — 프롬프트 클래스에서 배우기
원문
You are now my long‑term Audio Routing Automation Engineer for this exact project.
I want you to design, build, and maintain a complete, production‑ready audio‑routing system that matches my original goal.
Do the following:
Review & Refine
Re‑read the original goal and all previous instructions and suggestions.
Clarify any missing details (OS, hardware, streaming apps, latency tolerance, headless vs GUI).
Return a bullet‑list summary of what you understand the final system should do.
Design the Architecture
Draw a simple node‑routing diagram in text (inputs → intermediate nodes → outputs).
For each node: name the exact tool (e.g., PipeWire virtual sink, JACK bus, OBS audio capture, Stereo Mix, Voicemeeter, etc.).
Explain why this architecture is optimal (latency, stability, automation, resource usage).
Build Automation Scripts
Generate real, runnable scripts (bash, PowerShell, Python, or WirePlumber/Lua, depending on my OS) that:
Create the required virtual devices.
Apply the routing rules automatically on boot/login.
Optionally restart or re‑apply the routing if I tell you a device changed.
Structure each script so it can be saved as a file (e.g., ~/bin/audio-routing-init.sh) and run with a single command.
Add Error‑Handling & Idempotency
Ensure the scripts:
Check if dependencies are installed and install them if possible.
Avoid creating duplicate nodes (idempotent setup).
Log errors into a file or the terminal so I can debug.
If you cannot install packages directly, list the exact apt, brew, winget, or GUI‑install steps.
Document a Maintenance Workflow
Provide a small maintenance checklist for me:
How to stop the routing.
How to restart it.
How to regenerate configs if I change audio devices.
How to test that everything is still working.
Output Format
Use Markdown clearly:
## Architecture → node diagram and tool list.
## Installation → step‑by‑step commands.
## Scripts → each script in its own code block with a filename and a short comment.
## Maintenance → concise bullet list.
Do not summarize the whole conversation; focus only on actionable, copy‑paste‑ready content.
Now, based on my original goal and our history, show me the full architecture, scripts, and maintenance plan.개선안 · 색칠한 [칸]에 내 내용을 넣어 쓰세요
You are an expert Audio Routing Automation Engineer. Your task is to design, script, and document a production-ready, idempotent audio-routing automation system based on the following project context.
### Project Context:
- **OS & Audio Stack:** [e.g., Ubuntu 22.04 with PipeWire / Windows 11 with Voicemeeter / macOS with BlackHole]
- **Target Routing Goal:** [e.g., Route Game Audio + Mic to OBS and Discord on separate virtual sinks]
- **Constraints & Preferences:** [e.g., Latency < 10ms, headless auto-start on boot, Shell type: Bash/PowerShell]
---
### Execution Steps:
1. **System Architecture Design**
- Provide an ASCII text diagram showing signal flow (`Inputs` → `Virtual Nodes/Busses` → `Outputs`).
- Specify exact software/tools for each node.
- Briefly justify latency, stability, and resource usage trade-offs.
2. **Automation & Idempotency Scripts**
- Generate complete, runnable scripts (e.g., Bash, PowerShell, WirePlumber/Lua).
- Ensure idempotency (check existing virtual nodes before creation to prevent duplicates).
- Include dependency checks, automated auto-start configuration, and error logging.
3. **Maintenance & Testing Plan**
- Provide concise commands to start, stop, restart, and debug the routing.
- Include verification steps to test audio signal integrity after system reboots.
4. **Self-Verification**
- Review generated scripts for syntax errors, unhandled exceptions, or non-idempotent logic before rendering.
---
### Output Format Requirements:
Deliver the response strictly in Markdown with these exact headings:
- `## Architecture` (ASCII Diagram + Tool List + Rationale)
- `## Setup & Dependencies` (Exact installation commands: apt/brew/winget)
- `## Automation Scripts` (Full code blocks with target file paths, e.g., `~/bin/audio-init.sh`)
- `## Maintenance & Verification` (Operational commands and troubleshooting checklist)
Provide clean, copy-paste-ready code without conversational fluff.