---
title: "Audio Logger"
slug: "dataflow-nodes-audio-logger"
updated: 2026-02-10T04:32:53Z
published: 2026-02-10T04:32:53Z
canonical: "docs.knovvu.com/dataflow-nodes-audio-logger"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.knovvu.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Audio Logger

Audio Logger Node. Stores the inputted audio to object storage in a Wave format.


## Parameters
|  <div style="width:120px">name</div> | description | <div style="width:220px">default</div> |
|---|---|---|
| Channel Count | The channel count of the inputted audio | 1 |
| Encoding | Desired encoding of the stored audio, PCM for quality, ULaw for storage | PCM |
| Postfix | Postfix for identifying the audio files. Can only contain alphanumeric characters or '_' | audio|

:::(Warning) (Channel Count)
Channel Count must be left as 1 unless a [Mono to Stereo Mixer](/v1/docs/dataflow-nodes-mono-to-stereo-audio-mixer) is directly connected as the only streaming audio input to the Audio Logger. You can check the [Project Structure](/v1/docs/dataflow-nodes-audio-logger#project-structure) section for more information.
:::

## Inputs

### Audio
&emsp; Accepts mono or stereo audio from a single channel.


### Events
&emsp;None 

## Outputs

### Audio
&emsp;None

### Events
&emsp;None 


## Remarks

### Requirements
:::(Warning) (Server Configuration)

MinIO Node Audio Logging must be enabled in the server configurations by the system administrator for this node to function properly. 

:::

### Project Structure

This node can be given any audio connection to log a wave file.

An example Audio Logger node that collects and stores modified streaming audio.
<center>

![image.png](https://cdn.document360.io/9bca2910-6a3b-4224-9470-43f91f9a6d57/Images/Documentation/image-RFLB6Q6U.png){height="" width=""}
</center>

The node above will collect audio through the session and log it as a single wave file. 

An example Audio Logger node that collects and stores TTS Outputs is like.
<center>

![image.png](https://cdn.document360.io/9bca2910-6a3b-4224-9470-43f91f9a6d57/Images/Documentation/image-5TSEES0X.png){height="" width=""}
</center>

The node above will collect each TTS output separately and log each output in a different wave file. 

<center>

![image.png](https://cdn.document360.io/9bca2910-6a3b-4224-9470-43f91f9a6d57/Images/Documentation/image-Q6J9VDIO.png){height="" width=""}

</center>

The node above will collect all the audio through the session that comes from Batch To Stream Audio Merger, and log it in a `Stream` wave file, and collect each of the TTS outputs and log them in separate `Batch` wave files. 

<center>
    
![image.png](https://cdn.document360.io/9bca2910-6a3b-4224-9470-43f91f9a6d57/Images/Documentation/image-HPKJOJD0.png){height="" width=""}
    
</center>

:::(Error) (Channel Count)
Channel Count **must** be set to 2 ***if and only if*** a [Mono to Stereo Mixer](/v1/docs/dataflow-nodes-mono-to-stereo-audio-mixer) node is directly connected as the **only** streaming audio input. 
:::

### Supported flow types
Batch, Stream


## Release Notes 

<div style="max-height: 200px; overflow-y: auto; overflow-x: hidden"> 
        <details>
        <summary> <strong> v4.6.0</strong> </summary>
        <ul>
            <li>Removed 'Auto' from encoding options.</li>
            <li>Added restriction in UI so that channel count can only be set to 1 or 2.</li>
            <li>Moved audio upload congestion point to a background worker to prevent a possibly long blocking in the main flow.</li>
        </ul>
    </details>
    <details>
        <summary> <strong> v4.5.0</strong> </summary>
        <ul>
            <li>Introduced node.</li>
        </ul>
    </details>
</div>