Audio Segment Picker

Accumulates segments, whenever a Flush is received, picks a segment with a length in range of primary interval. If no such segment exists, tries to pick it in range of secondary interval. Otherwise, picks the first segment.
After picking a segment, the node sends it to the listeners.

Parameters:

name	description	default
PrimaryIntervalLowerLimitMsec	Lower Limit of Primary Interval	5000
PrimaryIntervalUpperLimitMsec	Upper Limit of Primary Interval	20000
SecondaryIntervalLowerLimitMsec	Lower Limit of Secondary Interval	3000
SecondaryIntervalUpperLimitMsec	Upper Limit of Secondary Interval	30000

Inputs

Audio:
Accepts audio from a single channel.

Events:

name	description	known nodes that generate this event
Start of Segment	Signals the start of a speech segment.	Audio Segmenter
End of Segment	Signals the end of a speech segment.	Audio Segmenter

Outputs

Audio:
Audio fragments are sent to output

Events:

name	description
Start of Segment	Raised once at the beginning of each audio fragment.
End of Segment	Raised once at the end of each audio fragment.

Remarks :

• This node does performs its calculations when flush is called. So until all the segments are provided and the flush method is called this node does not output anything. Hence it is only suitable for batch usage.

• Similar to AudioSegmenter Node, this node also toasts the audio output write actions for each segment in between start-of-segment and end-of-segment events. As an example for an audio data with 3 audio segments, the flow is as follows (the order is well defined) :

segment-1: send "Start of Segment" event
segment-1: write the audio data of this segment to output
segment-1: send "End of Segment" event
segment-2: send "Start of Segment" event
segment-2: write the audio data of this segment to output
segment-2: send "End of Segment" event
segment-3: send "Start of Segment" event
segment-3: write the audio data of this segment to output
segment-3: send "End of Segment" event

Project Structure
A sample project can be built as such:

The project picks the best segment that the [Language Identifier](/v1/docs/dataflow-nodes-language-identifier){target=`_blank`} works with, and outputs one Language Change event.

Supported flow types: Batch