[BUG]: AudioGraph with FileInputNode/FrameInputNode -> FrameOutputNode completes quantums as fast as possible.

Question

[BUG]: AudioGraph with FileInputNode/FrameInputNode -> FrameOutputNode completes quantums as fast as possible.

Tom Huntington 216

It just dumps the FileInputNode on my FrameOutputNode, instead feeding it in at the correct rate. The quantum length is less than 1ms when we would expect 10ms to get the correct sample rate. To get the quantums to happen every 10ms we can add a AudioFrameOutputNode as follows:

   fileInputNode.AddOutgoingConnection(frameOutputNode);  
   fileInputNode.AddOutgoingConnection(deviceOutputNode);  
   deviceOutputNode.Stop();

However, if I do this I run into another bug https://learn.microsoft.com/answers/questions/658616/bug-audiographcreatedeviceoutputnodeasync-fails-if.html.

[The following appears to have been fixed] I have also ran into another bug, but this was hardware dependant. This time with deviceInputNode -> frameOutputNode. For a specific render device if the sample rate is 44100 Hz, then the we get a quantum size of 448 every 10ms (a sample rate of 44800 Hz). If the sample rate is anything else then the quantum's are spaced appropriately. Picking a different primary render device can make the problem go away.

Anonymous

2021-12-10T08:28:58.95+00:00

Could you please check the AudioGraph.SamplesPerQuantum Property to see what exactly value it is of the quantum size after the AudioGraph object is created?
Tom Huntington 216 Reputation points

2021-12-10T18:17:59.49+00:00

Sorry, I communicated poorly. The quantums are the expected size, the just happen instantanely.

The quantum size is always the sample rate divided by 100. The correct quantum size for quantums of 10ms. But the quantums are occurring significantly faster that this.

Edit: Actually this is not the case for the device I was getting the second (deviceInputNode -> frameOutputNode) bug on, its actually 448.
Anonymous

2021-12-13T09:46:08.177+00:00

Do you mean when checking AudioGraph.SamplesPerQuantum Property, it is the correct value like 10ms, but you think it actually is faster than the value you got?
Tom Huntington 216 Reputation points

2021-12-14T03:59:18.897+00:00

AudioGraph.SamplesPerQuantum Property gives the number of samples per quantum lets say 441. The quantum's can occur with different periods but usually they are 10ms apart (1000/10 quantum's per second). samples_per_quantum * quantums_per_second gives you the samples per second 44100. Lets say the audio file has 60*44100 samples. Then you would get the 441 samples each 10ms for a minute. But what happens without an deviceOutputNode, is the quantum's occur as fast as possible, and you get the whole file in 441 sample chucks in under a second.

Maybe this is the desired behaviour.
Anonymous

2021-12-14T07:17:56.557+00:00

I understand it, so you think that the whole process of collecting sample data goes faster than it should be? For example, It should take 60 x10 ms to get all the data but now it only takes 60 x1 ms, right? Could you please tell me how do you check this so I can try to reproduce it on my side to confirm the behavior you mentioned.
Tom Huntington 216 Reputation points

2021-12-16T22:38:17.05+00:00

Here's a example demonstrating the behaviour.

https://github.com/tom-huntington/AudioGraphBug2.git

Maybe this behaviour is okay from a AudioFileInputNode. Maybe I haven't been using the AudioFrameInputNode api correctly, I don't know if this is really an issue anymore.
Anonymous

2021-12-20T09:19:35.97+00:00

@Tom Huntington Thanks for sharing, I noticed that you are using a console app. Have you tested this in UWP projects and will it give the same behavior? If this only happens on consols apps, then this issue might be related to the console app itself.