headers
Leif Asbrink | 14 Feb 14:13

Linrad-02.23 and watzo

Hi All,

The known bugs in 02-22 are corrected and the remaining
planned network formats are included in 02-23.

There is also a program watzo (Waterfall Zoom) that
can be used to receive FFT2 transforms from Linrad.

73

Leif

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <linrad@...>.
To unsubscribe, E-mail to: <linrad-off@...>
To switch to the DIGEST mode, E-mail to <linrad-digest@...>
To switch to the INDEX mode, E-mail to <linrad-index@...>
Send administrative queries to  <linrad-request@...>
Permalink | Reply | 0 comments |
headers
Leif Asbrink | 15 Feb 16:55

Re: Sampling speed.

Hello Alberto,

Long ago you sent the mail about resampling in Windows.
I have not tested until today for various reasons.

The result is somewhat unexpected. I can see no difference
whatsoever when running a Delta 44 at nominal 100 kHz.
Neither performance nor cpu load is affected at all.

The choice is available for Delta 44 multi on one
of my Windows 2000 installations but not on the
other. Presumably the drive routines from M-Audio 
differ.

The two figures here
http://www.sm5bsz.com/linuxdsp/install/uiparm.htm
do truly represent the Windows performance and one
should avoid non-integer resampling (silently)
done by the Windows operating system. 

Another thing, Linrad now has a network by which one
can split processing between several computers and
also add various post-processors like MAP65 (hopefully)

I have been able to do this for Linux only - using 
some prototype code for multicasting supplied by 
ON4IY and some code for a connected socket that I 
got from W3SZ. I think it would be nice to add 
network capabilities in the Windows version as well
but I do not know how to proceed. Do you know where
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alberto di Bene | 16 Feb 17:07
Picon

Re: Sampling speed.

Hi Leif,

   I saw your message just today, so I am answering with a bit of delay, sorry.
What you observed is in accord with my observations... it looks like either Windows does not care very much
about how 
the user has set that slider, or it passes the resampling task to the sound card driver. And the fact that it
appears in 
just one of your installations seems to confirm this latter hypothesis.

As said in my previous post, I don't use the resampling done by Windows, as being not reliable, especially
considering 
that I need to do a fractional resampling that is absolutely not even offered by Windows. Also for output, if
the user 
has just one sound card. I upsample from the internal 8000 or 11025 Hz processing rate to a sampling rate
equal to that 
used for input, so to be able to use the same card both for input and for output. I offer the user the choice to
let 
Windows do this upsampling, or to have Winrad doing it.

About network multi-casting, that is a problem I will have to face with in a not too distant future. I have
added to 
Winrad the possibility to be interfaced to a user DLL, which, among other tasks, can receive the raw data
just 
digitized. I would like at some point in the future experiment with the possibility to send those raw data
through the 
Internet to another copy of Winrad for processing, by just using this DLL. I think I will have to take
advantage of the 
time I will spend reading some of the examples that are found here :
http://www.codeproject.com/internet/
I have also seen that the compiler I use, Borland Developers Studio, offers natively some pre-built
(Continue reading)

Permalink | Reply | 8 comments |
headers
Leif Asbrink | 25 Feb 21:14

Bugs?

Hi All,

The list has been silent for quite some time and
in particular I have not received any bug reports
on the latest Linrad versions. I do not know if
it is good or bad - i.e. whether it works well or
whether nobody tried to use 02-22 or 02-23.

At the "Linrad Homepage" Linrad-02.21 is still the 
latest version and I would like to know that 
the later ones have not caused problems before 
I upload 02-24 and make it the latest version at 
"Linrad Homepage".

Earlier versions do not work with a SDR-14 under 
Microsoft Windows if the only soundcard is a Delta44.
02-24 also has some changes in the noise blanker,
but I can see no influence on the final result except
for a small decrease in cpu load.

The reason for making changes to the blanker is 
that I tried to make the calibration automatic. 
Linrad can extract the average pulse shape from 
pulses present in the normal receive input. 
As it turned out I was not able to extract reliable 
enough information to come anywhere near the 
accuracy the old calibration method gives.

There has not been a single comment on watzo. 
Does it mean that it works or does it not?
(Continue reading)

Permalink | Reply | 0 comments |
headers
Pierre Vanhoucke | 25 Feb 22:01
Picon

Re: Bugs?

Hi Leif,

On Sunday 25 February 2007 21:14, Leif Asbrink wrote:

> The list has been silent for quite some time and
> in particular I have not received any bug reports
> on the latest Linrad versions. I do not know if
> it is good or bad - i.e. whether it works well or
> whether nobody tried to use 02-22 or 02-23.

To me it is very good :-) 
Linrad 02.23 and watzo are running fine on my Suse10.0 system  under X11.

> There has not been a single comment on watzo.
> Does it mean that it works or does it not?

It works very well but I am still trying to find out how I can increase the  
vertical size of the waterfall.
(Only 15% of the available screen space is used)
Hitting F1 gives help information but it is hard to read because the text is 
interlaced with other information on the screen.

73

Pierre/ON5GN

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <linrad@...>.
To unsubscribe, E-mail to: <linrad-off@...>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Leif Asbrink | 25 Feb 22:13

Re: Bugs?

Hi Pierre,

> > There has not been a single comment on watzo.
> > Does it mean that it works or does it not?
> 
> It works very well but I am still trying to find out how I can increase the  
> vertical size of the waterfall.
> (Only 15% of the available screen space is used)
> Hitting F1 gives help information but it is hard to read because the text is 
> interlaced with other information on the screen.
Oooh! Not intentional. The screen should be cleared 
so you see only the help text. It was cleared in the 
waterfall area but I have now changed it to clear 
the whole window allocated for watzo.

Watzo is primitive is some ways. In case you set it up for
15% waterfall area, the only way to change that is to
erase or edit the par_ui file. "Screen height" and "Max lines"
affect the vertical size of the waterfall.

73

Leif

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <linrad@...>.
To unsubscribe, E-mail to: <linrad-off@...>
To switch to the DIGEST mode, E-mail to <linrad-digest@...>
To switch to the INDEX mode, E-mail to <linrad-index@...>
(Continue reading)

Permalink | Reply | 0 comments |
headers
John Harrison, NI1B | 26 Feb 03:24

Re: Bugs?


Hi,

   I haven't tested it extensively. But I did download, compile and run it
on knoppix 3.6. The X windows version worked almost without any hitches :) 
Nice.

   The only bug I noticed was when I shrink the fft3 bandwidth to a very
small value, I sometimes get a seg. fault? This is an old bug, so I doubt
that it is anything new to worry about.

   Very nice package.

   Glad to see it getting better and better :).

   warm regards to all,
   john

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <linrad@...>.
To unsubscribe, E-mail to: <linrad-off@...>
To switch to the DIGEST mode, E-mail to <linrad-digest@...>
To switch to the INDEX mode, E-mail to <linrad-index@...>
Send administrative queries to  <linrad-request@...>
Permalink | Reply | 0 comments |
headers
Pierre Vanhoucke | 26 Feb 17:15
Picon

watzo-00.00

Hi Leif,

Here is my second comment on watzo
When I change the frequency in the WSE box of the sender , the frequency scale 
and the box 'X0=......' in watzo are not updated immediately.
I have to hit the left or right arrow keys to get updated frequency 
information.

73

Pierre/ON5GN

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <linrad@...>.
To unsubscribe, E-mail to: <linrad-off@...>
To switch to the DIGEST mode, E-mail to <linrad-digest@...>
To switch to the INDEX mode, E-mail to <linrad-index@...>
Send administrative queries to  <linrad-request@...>
Permalink | Reply | 0 comments |
headers
Leif Asbrink | 26 Feb 22:04

Re: watzo-00.00

Hi Pierre,

> Here is my second comment on watzo
> When I change the frequency in the WSE box of the sender , the frequency scale 
> and the box 'X0=......' in watzo are not updated immediately.
> I have to hit the left or right arrow keys to get updated frequency 
> information.
OK. Fixed (hopefully)

I will await some more comments before uploading the
next version.

73

Leif  /  SM5BSZ

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <linrad@...>.
To unsubscribe, E-mail to: <linrad-off@...>
To switch to the DIGEST mode, E-mail to <linrad-digest@...>
To switch to the INDEX mode, E-mail to <linrad-index@...>
Send administrative queries to  <linrad-request@...>
Permalink | Reply | 0 comments |
headers
Leif Asbrink | 26 Feb 22:08

Re: Bugs?

Hello John,

>    The only bug I noticed was when I shrink the fft3 bandwidth to a very
> small value, I sometimes get a seg. fault? This is an old bug, so I doubt
> that it is anything new to worry about.

Oooh! I was unaware of this one. Can you reproduce it?
Seg faults can sometimes be trapped with e.g. valgrind.
Things run really slow under valgrind, but sometimes 
it gives information on what causes a segfault.

In any case, some details on how to trigger this bug
would be welcome.

73

Leif / SM5BSZ

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <linrad@...>.
To unsubscribe, E-mail to: <linrad-off@...>
To switch to the DIGEST mode, E-mail to <linrad-digest@...>
To switch to the INDEX mode, E-mail to <linrad-index@...>
Send administrative queries to  <linrad-request@...>
Permalink | Reply | 3 comments |

Gmane