Re: Python script with Head block runs too long before exiting

[Jeff Long]

Please keep discussions on the mailing list.

I don't know the exact reason the program runs for 3 seconds after the file is finished. You could try stubbing out various portions of the flowgraph, e.g., put a Null or Noise Source and Throttle (with the limit set to 100ms) before the Resampler to see if the blocks before that are responsible.

On Sun, Feb 25, 2024 at 1:01 PM Elmore Family <wa4ywm@comcast.net> wrote:

Jeff,

 

The wave file does contain the correct number of samples. You mention that the latency is before the Head block. Note that the file fills for 13.14 sec (157680 samples) starting at the marked time and then it is 3 more seconds before exit.

 

Jim

 

From: Jeff Long

Sent: Sunday, February 25, 2024 11:44 AM

To: Elmore Family

Subject: Re: Python script with Head block runs too long before exiting

 

At 12~48kS/s, it is possible that there is 3 sec of latency before the Head block. However, there should only be around 157680 samples in the wav file when the program finishes. Smaller output buffers (set_max_output_buffer()) on the block before Head may help reduce latency.

 

On Sun, Feb 25, 2024 at 11:21 AM Elmore Family <wa4ywm@comcast.net> wrote:

The attached file is run as a thread of a larger project. I run this as a script and not a GUI.

 

The script waits for a real time of 15 or 45 seconds to begin execution of the flowgraph. The Head block is set at 157680 which is 13.14 seconds at 12000 samples/sec. The Head block feeds a Wave file sink.

 

The program works as it should properly storing data in the wave file except for the issue below.

 

The issue is that I expect the script (flowgraph) to cease execution at 13.14 seconds. This is based on my understanding of the operation of a Head block. However, it continues to run(?) for another approximately 3+ secs before exiting. Needless to say this creates huge timing issues for the rest of the program.

 

Any ideas?

 

Jim

Virus-free.www.avg.com