[hpsdr] process priority

[n3evl]

I think any audio popping glitches are due to the combined processing load 
of the dsp and video -- I certainly noticed a difference with PowerSDR in 
combination with HPSDR ozy/Janus at 192KHz vs 96KHz.  From what I 
understand, the typical CPU today can easily handle the dsp part of the 
task: its the combination of dsp and video, especially at the higher 
bandwidths that can put a strain on the overall system.  My next computer 
upgrade will certainly take this into account when I choose components.

73, Pete, N3EVL

----- Original Message ----- 
From: "Alberto I2PHD" <i2phd at weaksignals.com>
To: <hpsdr at hpsdr.org>
Sent: Thursday, July 19, 2007 4:49 PM
Subject: Re: [hpsdr] process priority


> ***** High Performance Software Defined Radio Discussion List *****
>
>>
>> Another thing to try adjusting -- the process
>> priority.  At 192khz
>> you may need to run PowerSDR real time to keep it
>> glitch free.
>
> Well 192 kHz are not that much. While experimenting with the new Perseus 
> direct sampling receiver, Winrad was fed with a
> 500 kHz I/Q stream, 24-bit samples, via the USB 2.0 port, and it did its 
> downsampling, filtering and demodulating job
> with a CPU load of about 50% on an Athlon clocked at 2.2 GHz. Absolutely 
> no audio glitches. The priorities of the
> various threads of Winrad, and the process priority of the main task were 
> the Windows default. The hardware,
> reprogramming the FPGA, can go even at 1 Ms/sec, and that will probably be 
> the next experiment.
>
> 73  Alberto  I2PHD
>
> _______________________________________________
> HPSDR Discussion List
> To post msg: hpsdr at hpsdr.org
> Subscription help: http://lists.hpsdr.org/listinfo.cgi/hpsdr-hpsdr.org
> HPSDR web page: http://hpsdr.org
> Archives: http://lists.hpsdr.org/pipermail/hpsdr-hpsdr.org/ 


 1184879853.0