如何使用FFmpeg录制音频而不生成输出文件？

Absolutely! You can skip writing to a file entirely by directing FFmpeg's output to standard output (stdout), which Node.js can capture and forward over WebSocket. Here's a complete solution tailored to your use case:

Step 1: Modify Your FFmpeg Command #

Instead of specifying a file name like output.wav, use - to tell FFmpeg to send output to stdout. You'll also need to explicitly define the output format (since there's no file extension to infer it from):

ffmpeg -f alsa -i hw:0,0 -af "pan=2c|c0=c0" -f wav -

• -f wav: Explicitly sets the output format to WAV (matches your original command)
• -: Tells FFmpeg to stream output to stdout instead of a file

Step 2: Node.js WebSocket Implementation #

Use Node.js's child_process module to spawn the FFmpeg process, capture its stdout, and send the audio chunks over WebSocket. We'll use the popular ws library for WebSocket handling:

First, install the dependency:

npm install ws

Then create your server code:

const { spawn } = require('child_process');
const WebSocket = require('ws');

// Initialize WebSocket server
const wss = new WebSocket.Server({ port: 8080 });

wss.on('connection', (ws) => {
  console.log('New client connected');

  // Spawn FFmpeg process with our modified command
  const ffmpegProcess = spawn('ffmpeg', [
    '-f', 'alsa',
    '-i', 'hw:0,0',
    '-af', 'pan=2c|c0=c0',
    '-f', 'wav',
    '-'
  ]);

  // Forward FFmpeg's stdout chunks to the WebSocket client
  ffmpegProcess.stdout.on('data', (audioChunk) => {
    // Only send if the WebSocket connection is open
    if (ws.readyState === WebSocket.OPEN) {
      ws.send(audioChunk);
    }
  });

  // Handle FFmpeg error output (useful for debugging)
  ffmpegProcess.stderr.on('data', (error) => {
    console.error(`FFmpeg Error: ${error.toString()}`);
  });

  // Clean up FFmpeg process when client disconnects
  ws.on('close', () => {
    console.log('Client disconnected');
    ffmpegProcess.kill();
  });
});

console.log('WebSocket server running at ws://localhost:8080');

Step 3: Optimizations for Streaming (Optional) #

WAV is uncompressed, which works but uses more bandwidth. For better streaming efficiency, consider using a compressed, stream-friendly codec like Opus:

Updated FFmpeg Command for Opus: #

ffmpeg -f alsa -i hw:0,0 -af "pan=2c|c0=c0" -c:a opus -b:a 64k -f opus -

• -c:a opus: Uses the Opus codec
• -b:a 64k: Sets a reasonable bitrate for speech/audio (adjust as needed)
• -f opus: Explicitly sets the output format to Opus

You'll need to adjust your WebSocket client to decode Opus, but it's much more efficient for real-time streaming.

Key Notes #

• Make sure FFmpeg is installed and available in your system's PATH (or use the full path to the FFmpeg executable in the spawn command)
• Verify your audio device ID (hw:0,0) is correct with arecord -l
• Always check the WebSocket connection state before sending data to avoid errors
• Add error handling for cases where FFmpeg fails to start (e.g., invalid device ID)

内容的提问来源于stack exchange，提问作者user9601710