Date: Thu, 28 Feb 2002 17:09:10 -0800 From: Karl Cunningham <karlc@..........> Subject: Re: New WinSDR
Yes it is. I renamed the record file at around 16:05, but I expected it to
draw the GIF files starting at the beginning of today's record file (around
02:25utc). It didn't draw the gif files starting with the first data in
the record file, but it picked up from about the time I renamed yesterday's
record file (16:09UTC).
Karl
--On Thursday, February 28, 2002 1:31 PM -0800 Larry Cochrane
<cochrane@..............> wrote:
> Hi Karl,
>
> It seems to be working OK now....
>
> -Larry
>
> ----- Original Message -----
> From: "Karl Cunningham" <karlc@..........>
> To: <winsdr@..............>
> Sent: Thursday, February 28, 2002 8:15 AM
> Subject: Re: New WinSDR
>
>
>> Hi Larry --
>>
>> I tried renaming yesterday's record file and now the gif shows no traces
> at
>> all. There is no time shown in the left margin and the start date at the
>> bottom shows 01/01/70. Same for all channels. I'm sure it will be
>> resolved tonight when yesterday's record file isn't being accessed
> anymore.
>>
>> Karl
>>
>>
>> --On Thursday, February 28, 2002 12:52 AM -0800 Larry Cochrane
>> <cochrane@..............> wrote:
>>
>> > Hi Karl,
>> >
>> > I found the problem. It turns out I only added the code that checks for
> a
>> > different record file format to the real-time historical display code
> and
>> > not the GIF images code. The next release will fix this problem. In the
>> > mean time, if you change the sample rate or number of channels to
>> > record you will need to exit WinSDR and then delete or move the daily
>> > record files to another directory so when you restart WinSDR it
>> > doesn't have access to the old files.
>> >
>> > -Larry
>> >
>> > ----- Original Message -----
>> > From: "Karl Cunningham" <karlc@..........>
>> > To: <winsdr@..............>
>> > Sent: Wednesday, February 27, 2002 11:15 PM
>> > Subject: Re: New WinSDR
>> >
>> >
>> >> Hi Larry --
>> >>
>> >> I still see this problem on v2.0.1. I changed the number of channels
>> >> from 3 to 4 and now the gif files are almost all black. I made the
>> >> change at 02:21 UTC this evening, and the gif files are supposed to
> show
>> >> 24hrs, so it's going back quite a ways into yesterday's record file
>> >> (which only contains 3-channel data).
>> >>
>> >> Karl
>> >>
>> >>
>> >> --On Tuesday, February 26, 2002 15:26 -0800 Larry Cochrane
>> >> <cochrane@..............> wrote:
>> >> > I fixed a problem with changing the number of channels to record or
> the
>> >> > sample rate and gif file generation. When you change the number of
>> >> > channels to record or the sample rate the daily record file format
>> >> > changes. The code that draws the gif images did not check to see if
> the
>> >> > number of channels or sample rate has changed in the record file. As
>> > with
>> >> > the replay window, the gif file creating process can only use the
>> > current
>> >> > number of channels to record and sample rate record files. Now the
> gif
>> >> > file generation process will skip any record files not created using
>> >> > the current record channels and sample rate.
>> >>
>> >>
>> >>
>> >> __________________________________________________________
>> >>
>> >> Public Seismic Network Mailing List WinSDR
>> >>
>> >> To leave this list email WINSDR-REQUEST@.............. with
>> >> the body of the message (first line only): unsubscribe
>> >>
>> >
>> >
>> > __________________________________________________________
>> >
>> > Public Seismic Network Mailing List WinSDR
>> >
>> > To leave this list email WINSDR-REQUEST@.............. with
>> > the body of the message (first line only): unsubscribe
>>
>>
>> __________________________________________________________
>>
>> Public Seismic Network Mailing List WinSDR
>>
>> To leave this list email WINSDR-REQUEST@.............. with
>> the body of the message (first line only): unsubscribe
>>
>
>
> __________________________________________________________
>
> Public Seismic Network Mailing List WinSDR
>
> To leave this list email WINSDR-REQUEST@.............. with
> the body of the message (first line only): unsubscribe
.