[WT-support] recording messing up cw sending

[Bob Wilson, N6TV]

It takes quite a bit of CPU power and file I/O to create an MP3 file in real
time, so fast computers may be required if you want to do parallel port CW
and MP3 recording at the same time.

With a 3rd party program like Virtual Audio Cable you can play back a QSO
with Win-Test and route the audio output to another 3rd party program called
Audacity, then save the excerpt as an MP3 file.

Or, the new wtQsoPlayer application may also be capable of splitting a huge
Win-Test MP3 recording into reasonably sized .mp3 files that you can can
further trim with Audacity.

See http://download.win-test.com/utils .

73,
Bob, N6TV

On Thu, Dec 3, 2009 at 4:38 AM, Tõnno Vähk <Tonno.Vahk at gildbankers.com>wrote:

> Yes exactly the same 1-2 sec hang ups then. I hope there is something
> authors can do abt this to make recording function usable.
>
> Another question: How can I cut out one QSO from the recording file to send
> to friends?? I could not invent any way now.
>
> tonno
>
> -----Original Message-----
> From: support-bounces at win-test.com [mailto:support-bounces at win-test.com]
> On Behalf Of Matt IZ3EYZ
> Sent: Monday, November 30, 2009 11:37 PM
> To: support at win-test.com
> Subject: Re: [WT-support] recording messing up cw sending
>
> >Nice while it worked but shortly after starting the program and recording
> >the computer got into problems and started to mess up cw sending.
>
> It happened spotty for abt 15mins on Sat late afternoon and just on one pc.
>
> >In some cases froze for a few seconds completely.
>
> This way it worked the whole contest on all the recording PCs and it
> happened since the 1st hr! It got frozen for 1-2 secs and wouldn't send cw
> for abt 5 or 10secs.
> I found switching to Alt-K and pressing F key or sending thru keyboard mode
> solved the cw sending trouble.
>
> >Checked the Task Manager and having the recording on definitely resulted
> in
> >having 100% processor capacity reached occasionally for some reason and I
> >guess that is where the >problem comes from.
>
> CPU usage was ok here (60% on peaks) . Memory as well. (abt 26mb nearly
> half
> point)
>
> 73
>
> Matt.EYZ
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.f5mzn.org/pipermail/support/attachments/20091203/e3268f7c/attachment-0001.htm