[digitalradio] Re: Revisiting Winwarbler and familiy

[Dave Bernstein]

Thanks, Andy.

WinWarbler was first released in July 2000, with monthly (or better) 
updates since then.

Many PSK ops find WinWarbler's most useful capability to be 
its "Station's Heard" window, which displays a list of all callsigns 
decoded on the current band and the callsign of the station with whom 
each is in QSO. For an example, see

http://www.dxlabsuite.com/winwarbler/Heard.jpg

Double-clicking an entry in the "Station's Heard" window sets up 
WinWarbler for a QSO with that entry's station, displaying all text 
already decoded on the QSO frequency. You can optionally configure 
WinWarbler to create a local entry in SpotCollector when it discovers 
a PSK station, making it easy to quickly identify needed new ones.

73,

  Dave, AA6YQ


--- In digitalradio@yahoogroups.com, "Andrew O'Brien" 
<[EMAIL PROTECTED]> wrote:
>
> I'm not sure how long Winwarbler has been around, but it has to be
> quite a few years since it was first released.  I have not used it
> frequently since I have tended to use  Zakanaka, MixW,  or Multispk
> user over the years.
> 
> Because Multipsk works very well with the DX Lab Suit,  I have
> recently been using DX LAB applications more and more.  I have
> vacillated between Logger32 and DX Keeper as my default logging
> software.
> 
> As much as I like Logger32, I have found some aspects of DX Lab 
Suite
> more suitable to my needs and now use DX Keeper, Spotcollector, and
> Multipsk most of the time.  The DX Lab Launcher makes updating the
> suite of applications so easy that I recently clicked on "upgrade" 
and
> updated Winwarbler.
> 
> This weekend, I wanted to try and mop up a few needed states  via 
the
> NAQP CW contest. I decided to use my DX Keeper log to track needed
> stations and use the very useful feature in Spotcollector and
> Pathfinder  that identify  stations known to use LOTW.  Since
> Winwarbler just looks "cool",   I decided to use the nice layout for
> some CW macros in the contest.  I can report that Winwarbler
> interfaces very easily with my Microkeyer and the on-board Winkey
> chip.  Nice sent CW,  and no lags or missed characters.  I found the
> quick QSL interface with QRZ.com very useful, it allowed me 
to "cheat"
> in NAQP, a tad , since I had a head start on what the person's name
> and state was likely to be.
> 
> So with CW transmit working well, I thought I would give Winwarbler 
a
> whirl on PSK31 and RTTY this morning.  It has been years since I 
used
> it.  I know the authors of software like us to actually read the 
help
> files but I like to poke around and see what can be done before
> actually having to read the file.  Winwarbler is fairly easy to 
figure
> out.  A few quick mouse clicks and I had changed the apparent 
default
> waterfall display from monochrome to colour (choose "synthetic" 
under
> WATERFALL DISPLAY in the PSK Config area) and the method that
> identifies where you are  on the  waterfall to "markers" rather than
> the default "trace" method .  At first I thought that the PSK did 
not
> receive as well as Multipsk but I think it was just poor conditions.
> Below  is the decode of a weak 20M signal.
> 
> Winwarbler
> NAME îCARLOS,  CARLOS
> . QTH  IS  PONT
>   CELGADA
> . AZORµ - HM77DR
> . BTU,
> I1S I1FRS DE CU2AO CU2AO
> K
> 
> 
> Multipsk:
> NAME IS CAR,  CARLOS
> . QTH  IS  PONTA DELGADA
> . AZORES - HM77DR
> . BTU,
> I1FRS I1FRS DE CU2AO CU2AO
> K
> 
> The squelch settings on Winwarbler were "slider 31" and in Multipsk
> the squelch was a '1'.  They appear to decode weak signals about the
> same.
> 
> For RTTY, set up was just as easy and performance as good as one 
would
> expect.  I used the default settings
> 
> In Multipsk with a squelch setting of 3,  the decode of a weak 
signal was
> 
> CQ CQ CQ DE RZ3AFK RZ3AFK RZ3AFK PSE K
> CC CQ CQ DA RZ3AFKIMZ3AFK RZ3AFK PSE K
>   CQ CQ DE RZ3AFK RZ3AFK RZ3AFK NSE K
> 
> In Winwarbler
> 
> CQ CQ DE RZ3AFKRZ3AFK RZ3AFK PSE K
> CQ DAFK RZ3AFK PSE K
> CQ DE RZ3AFK RZ3AFK RZ3AFK PK J
> 
> Again, not a whole lot of difference and squelch settings not set 
for
> exact matching.
> 
> 
> On this Yahoogroup, we often get people that are totally new to
> digital modes and are looking for something easy to start with,
> usually just PSK31.  I usually suggest Digipan because it is so easy
> to set-up and the newcomer can be up and running in no time.  I 
think
> I will now add Winwarbler to that list of software recommended for 
the
> newcomer   It is very easy to set-up,  GREAT on the eyes,  
interfaces
> very well with your electronic keyer, When used with it's siblings 
(DX
> Keeper, Spotcollector, DXView, Pathfinder and Propview ) you have 
some
> very powerful applications that I suggest the "expert" digital
> operators should give a try.
> 
> Winwarbler supports decoding of BPSK31 BPSK61 QPSK31 QPSK63,
> RTTY,MTTY (23 Hz RTTY), and various filtered adjustments for RTTY
> affected by multipath and "fluttered" signals"
> 
> 
> Andy K3UK
> Skype Me :  callto://an

[digitalradio] Re: Burkina Faso

[Andrew O'Brien]

Got him...


K3UK 599 599 K3U BK

K3UK TU XT2C UP

0204 UTC  40M.

Not an l new one but new for the band and mode.  Thank you
Spotcollector and DX Joe !

Andy K3UK

On 1/14/07, Andrew O'Brien <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
>
> Hmmm, I have not heard them with my ears but came in the shack and
> found my RTTY software (Multipsk had decoded them on 40M .
>
> QSL SP1DTG TU XT2C UP
>
> Too bad I did not have a robot set-up to work them while I was having dinner
>
> --
> Andy K3UK
> Skype Me : callto://andyobrien73
> www.obriensweb.com
> 



-- 
Andy K3UK
Skype Me :  callto://andyobrien73
www.obriensweb.com

[digitalradio] Burkina Faso

[Andrew O'Brien]

Hmmm, I have not heard them with my ears but came in the shack and
found my RTTY software (Multipsk had decoded them on 40M .

QSL SP1DTG TU XT2C UP

Too bad I did not have a robot set-up to work them while I was having dinner

-- 
Andy K3UK
Skype Me :  callto://andyobrien73
www.obriensweb.com

[digitalradio] Re: Implementing Contestia/RTTYM, could use some advice

[Vojtech Bubnik]

Joe, I have derived both Contestia and RTTYM from Pawel's code. You
may look at the sources at http://pocketdigi.sourceforge.net

Try to revert the bits before they are fed to the baudot decoder.

73, Vojtech OK1IAK

--- In digitalradio@yahoogroups.com, "Patrick Lindecker" <[EMAIL PROTECTED]>
wrote:
>
> Hello Joe,
> 
> What is sure is that there is no other differences that the ones I
gave in the "RX/TX modes selection and their descriptions" chapter, so
modifications on:
> * Block size (symbols)
> * Scrambling pseudo-random sequence
> * Scrambling shift (in number of bits of sequence right rotation)
> * Characters set 
> 
> Try first to change from Olivia to Contestia. It is the simplest, as
RTTYM adds a switch management, contrary to RTTYM.
> 
> Then try in reception generating Contestia, without noise. You must
decode it. Then adjust the different parameters of your code to decode
low S/N Contestia signals.
> 
> 73
> Patrick
> 
> 
> 
> 
> 
> 
> 
> 
>   - Original Message - 
>   From: Joe Veldhuis 
>   To: digitalradio@yahoogroups.com 
>   Sent: Wednesday, September 27, 2006 6:38 PM
>   Subject: Re: [digitalradio] Re: Implementing Contestia/RTTYM,
could use some advice
> 
> 
>   Patrick only gave an outline of the differences between Olivia and the
>   derivative modes. What I am looking for is some pointers on the actual
>   task of modifying the templates to implement those differences.
> 
>   I tried implementing RTTYM by changing the "BitsPerCharacter" and
>   scrambling code/shift parameters in Pawel Jalocha's reference code
(and
>   then passing the output through a Baudot>ASCII routine), but that was
>   apparantly not enough, since I don't get any output from the
demodulator.
> 
>   -Joe, KD8ATU
> 
>   jhaynesatalumni wrote:
>   > I haven't looked yet, but you might look in the MultiPSK
documentation,
>   > since Patrick recently implemented those modes in his program
and may
>   > have written them up.
> 
> 
>
> 
> [Non-text portions of this message have been removed]
>

[digitalradio] RAFT satellite to use PSK-31 mode Jan 16

[Andrew O'Brien]

Next week, we will enable the PSK-31 transponder on RAFT.

This transponder is 28.120 USB MHz PSK-31 SSB uplink and 2 meters FM down.

Both RAFT and ANDE (and PCSAT-1 this week) are working fine on orbit
for those with a big enough OSCAR satellite array to hear the weak 2
meter downlink. PCSAT-1 is much stronger and has passes that are
almost 15 minutes in length and can be worked horizon to horizon with
a good beam. ANDE and RAFT are only usable above about 10 to 15 deg
with a good beam for only a central 3 minutes or less.

RAFT packet-to-voice mode has been enabled for the first 3 weeks and
several stations have made contact... See web page:
http://www.ew.usna.edu/~bruninga/ande-raft-ops.html

Next week starting Tuesday 16 Jan, we will enable the RAFTPSK-31
transponder for similar experiments. Here is what it takes once the
PSK-31 mode has been enabled:
1) Read the user-service-agreement on the above web page
2) Someone in the footprint must do a packet CONNECT RAFT
3) That will bring up the 10m RX and 145.825 TX for 1 minute
4) Anyone sending PSK-31 or CW on 28.120 MHz USB should be heard

The transponder will time out after 1 minute (maybe later we can
extend that time depending on usage).

Remember that the footprint of RAFT is an order of magnitude smaller
than PCSAT-1 and so it is hard to hear except when a high pass and the
duration is only a few minutes.

With PCSAT-1 fully alive this week and next, we are seeing over 80
different stations (the maximum depth of the live capture page
http://pcsat.aprs.org )in under 8 hours.

Just today another satellite was launched onto 145.825 so now there
are 5 satellites there!
PCSAT-1, ANDE, RAFT, UO-11 and now Pehunesat. All but UO-11 use
standard 1200 baud AX.25 packets.

Bob Bruninga
USNA Small Satellite Lab



-- 
Andy K3UK
Skype Me :  callto://andyobrien73
www.obriensweb.com

[digitalradio] ANNOUNCE: PocketDigi-1.0.7

[Andrew O'Brien]

-- Forwarded message --
From: Vojtech Bubnik <[EMAIL PROTECTED]>
Date: Jan 14, 2007 12:34 PM




Hi gang.

I have added Olivia modes to PocketDigi. PocketDigi is a multimode
terminal software for Pocket PCs. It is freely downloadable from
http://pocketdigi.sourceforge.net

The software is discussed on hampocket group at yahoogroups. My
posting to this group follows.

73, Vojtech OK1IAK


This is a new version of PocketDigi. There are two new modems
implemented - Throb/ThrobX and Olivia/Contestia/RTTYM. Both of them
have not been optimized for best S/N yet, but seem to work well.

The Olivia modem has been adopted from the code by Pawel Jalocha, but
simplified. I have removed the receive input processor, which does
kind of channel equalization. I actually do not think that Olivia
decodes better than MFSK16, but Olivia is much more easier to tune. I
wonder whether anyone will ever use the Throb/ThrobX modems.

If the microphone input is overloaded, the waterfall line will be
marked by magenta stripes now. I did not know myself that my device
gets overloaded by the Warbler TRX until I added this feature. The
overload must have added considerable distortion to the signal. If you
experience it, add an external resistor divider to the microphone cable.

Please report the bugs, annoyances, whishes etc. If I do not know
about the bugs, I would not fix them. Thanks.

Excerpt from ChangeLog:

- Added OLIVIA/CONTESTIA/RTTYM modes. Initial implementation without
channel equalization.
- The three new modes tested for compatibility against MULTIPSK 4.1.2
- Known issue of THROB: AFC does not work correctly
- Overload indication. Magenta stripes are drawn over the waterfall if
mic input is overdriven.
- Fixed  bug in RTTY
- Fixed CW TX speed setting problem.
- Fixed problem of hanging CW TX at slow speeds.
- RTTY filters changed from IIR to FIR, which are faster on a fixed
point CPU
- Added THROB/THROBX modes
- Enabled reverse for MFSK16
- Premliminary port of Feld Hell. Only TX enabled, paper tabe control
is still missing for RX.
- Added setting of TX prefetch sound card buffers. If experiencing
rattling sound during TX, increasing number of prefetch buffers may help
- Adding error message boxes to report problems with sound card. It
shall clarify, whether some of the OEMs are lazy to support duplex
sound input/output

73, Vojtech OK1IAK

Re: [digitalradio] Re: next ea psk31 contest 2007

[EA4ZB]

I hope to see you in the contest too Andrew.

Good luck



2007/1/14, Andrew O'Brien <[EMAIL PROTECTED]>:


  -Thank you Joaquin, I hope to see you in the contest.

Andy K3UK

-- In digitalradio@yahoogroups.com , EA4ZB
<[EMAIL PROTECTED]> wrote:
>
> Hey all:
>
> It is a great pleasure for me to invite to participate to them next EA
> PSK31 CONTEST 2007
>
> *EA PSK31 CONTEST 2007 *
>
>







--
73 de Joaquin, EA4ZB

[digitalradio] Re: next ea psk31 contest 2007

[Andrew O'Brien]

-Thank you Joaquin, I hope to see you in the contest.

Andy K3UK

-- In digitalradio@yahoogroups.com, EA4ZB <[EMAIL PROTECTED]> wrote:
>
> Hey all:
> 
>  It is a great pleasure for me to invite to participate to them  next EA
> PSK31 CONTEST 2007
> 
> *EA PSK31 CONTEST 2007 *
> 
> 

[digitalradio] next ea psk31 contest 2007

[EA4ZB]

Hey all:

It is a great pleasure for me to invite to participate to them  next EA
PSK31 CONTEST 2007

*EA PSK31 CONTEST 2007 *



Sponsored by Unión de Radioaficionados Españoles (URE). The manager of the
contest is

EA4ZB.

*Participants: *Any licensed amateur station.

*Date: *From 16:00 UTC March 10th to 16:00 UTC March 11th, 2007.

*Mode: *BPSK31.

*Bands: *10, 15, 20, 40 and 80 meters, according to IARU Region 1 band plan.


*Classes*:

1) Single operator all band EA.

2) Single operator single band EA. (One band is only allowed during the
contest).

3) Single operator all band non-EA.

4) Single operator single band non-EA. (One band is only allowed during the
contest).

5) Multioperator EA, only all bands.

6) Multioperator non EA, only all bands.

More info, see down:

in spanish language: http://www.ure.es/hf/concursos/eapsk31/baseseapsk31.pdf
in english: http://www.ure.es/hf/concursos/eapsk31/baseseapsk31ingles.pdf


--
73 de Joaquin, EA4ZB
Contest Manager

[digitalradio] Revisiting Winwarbler and familiy

[Andrew O'Brien]

I'm not sure how long Winwarbler has been around, but it has to be
quite a few years since it was first released.  I have not used it
frequently since I have tended to use  Zakanaka, MixW,  or Multispk
user over the years.

Because Multipsk works very well with the DX Lab Suit,  I have
recently been using DX LAB applications more and more.  I have
vacillated between Logger32 and DX Keeper as my default logging
software.

As much as I like Logger32, I have found some aspects of DX Lab Suite
more suitable to my needs and now use DX Keeper, Spotcollector, and
Multipsk most of the time.  The DX Lab Launcher makes updating the
suite of applications so easy that I recently clicked on "upgrade" and
updated Winwarbler.

This weekend, I wanted to try and mop up a few needed states  via the
NAQP CW contest. I decided to use my DX Keeper log to track needed
stations and use the very useful feature in Spotcollector and
Pathfinder  that identify  stations known to use LOTW.  Since
Winwarbler just looks "cool",   I decided to use the nice layout for
some CW macros in the contest.  I can report that Winwarbler
interfaces very easily with my Microkeyer and the on-board Winkey
chip.  Nice sent CW,  and no lags or missed characters.  I found the
quick QSL interface with QRZ.com very useful, it allowed me to "cheat"
in NAQP, a tad , since I had a head start on what the person's name
and state was likely to be.

So with CW transmit working well, I thought I would give Winwarbler a
whirl on PSK31 and RTTY this morning.  It has been years since I used
it.  I know the authors of software like us to actually read the help
files but I like to poke around and see what can be done before
actually having to read the file.  Winwarbler is fairly easy to figure
out.  A few quick mouse clicks and I had changed the apparent default
waterfall display from monochrome to colour (choose "synthetic" under
WATERFALL DISPLAY in the PSK Config area) and the method that
identifies where you are  on the  waterfall to "markers" rather than
the default "trace" method .  At first I thought that the PSK did not
receive as well as Multipsk but I think it was just poor conditions.
Below  is the decode of a weak 20M signal.

Winwarbler
NAME îCARLOS,  CARLOS
. QTH  IS  PONT
  CELGADA
. AZORµ - HM77DR
. BTU,
I1S I1FRS DE CU2AO CU2AO
K


Multipsk:
NAME IS CAR,  CARLOS
. QTH  IS  PONTA DELGADA
. AZORES - HM77DR
. BTU,
I1FRS I1FRS DE CU2AO CU2AO
K

The squelch settings on Winwarbler were "slider 31" and in Multipsk
the squelch was a '1'.  They appear to decode weak signals about the
same.

For RTTY, set up was just as easy and performance as good as one would
expect.  I used the default settings

In Multipsk with a squelch setting of 3,  the decode of a weak signal was

CQ CQ CQ DE RZ3AFK RZ3AFK RZ3AFK PSE K
CC CQ CQ DA RZ3AFKIMZ3AFK RZ3AFK PSE K
  CQ CQ DE RZ3AFK RZ3AFK RZ3AFK NSE K

In Winwarbler

CQ CQ DE RZ3AFKRZ3AFK RZ3AFK PSE K
CQ DAFK RZ3AFK PSE K
CQ DE RZ3AFK RZ3AFK RZ3AFK PK J

Again, not a whole lot of difference and squelch settings not set for
exact matching.


On this Yahoogroup, we often get people that are totally new to
digital modes and are looking for something easy to start with,
usually just PSK31.  I usually suggest Digipan because it is so easy
to set-up and the newcomer can be up and running in no time.  I think
I will now add Winwarbler to that list of software recommended for the
newcomer   It is very easy to set-up,  GREAT on the eyes,  interfaces
very well with your electronic keyer, When used with it's siblings (DX
Keeper, Spotcollector, DXView, Pathfinder and Propview ) you have some
very powerful applications that I suggest the "expert" digital
operators should give a try.

Winwarbler supports decoding of BPSK31 BPSK61 QPSK31 QPSK63,
RTTY,MTTY (23 Hz RTTY), and various filtered adjustments for RTTY
affected by multipath and "fluttered" signals"


Andy K3UK
Skype Me :  callto://andyobrien73
www.obriensweb.com

Re: [digitalradio] Re: Movement toward open digital software?

[Bill Aycock]

It is apparent that you understand that ownership of a copyright 
allows you to control its use, even if that control is to allow free 
use, but your statement has a major semantic flaw--

The words "precise" and "legal" are incompatible and should never be 
used in the same sentence.

That's why we have so many lawyers, to debate (for fees) the 
differences among "shall be", "will be" ,"to be" and "is".

Bill-W4BSG

At 01:36 AM 1/14/2007, you wrote:
>--- In digitalradio@yahoogroups.com, "Simon Brown" <[EMAIL PROTECTED]>
>wrote:
>
> > I am *not* making it open source, only the decoding DLL's. The UI
>will never
> > be open source as it uses copyrighted code.
>
>Copyright and Open Source are not opposites. Copyright ownership is
>the precise legal foundation of, for example, the General Public
>License (GPL).
>
>There is a simple, concise discussion of the issues involved at
>.
>
>73
>Frank
>AB2KT
>
>
>
>
>
>Announce your digital  presence via our DX Cluster 
>telnet://cluster.dynalias.org
>
>Our other groups:
>
>http://groups.yahoo.com/group/dxlist/
>http://groups.yahoo.com/group/themixwgroup
>http://groups.yahoo.com/group/contesting
>http://groups.yahoo.com/group/wnyar
>http://groups.yahoo.com/group/Omnibus97
>
>
>Yahoo! Groups Links
>
>
>

Re: [digitalradio] Re: Movement toward open digital software?

[Robert McGwier]

Exactly.  My personal experience, which I believe is nearly identical to 
Frank's,  is found in our doing the software defined radio code (which 
is used now by thousands of radio amateurs and others) finds Simon's 
fear is misplaced.   However,  it is a personal (if incorrect ;-) )  
decision and his to make.

That does not keep us from voting with out fingers and feet and going 
elsewhere.  If Simon's game is the only one in town,  then we are left 
with no choice.   DttSP, Flex Radio, GnuRadio,  HPSDR, uwSDR, AEA 
DSP1232/2232  all run code that Frank and/or  I have written (along with 
many others).  My experience with open source in these projects is that 
it has been utterly glorious and the few Neaderthal's that come dragging 
their knuckles out of their caves are a minor annoyance.  We have been 
aided greatly and have learned a tremendous amount from doing business 
this way.

Soapbox shoved firmly back in to the closet,
Bob
N4HY




Frank Brickle wrote:
> --- In digitalradio@yahoogroups.com, "Simon Brown" <[EMAIL PROTECTED]>
> wrote:
>
>   
>> Spot on. I use a commercial library from Codejock - www.codejock.com
>> 
> - this 
>   
>> cannot be distributed. I also use other commercial libraries with
>> 
> similar 
>   
>> restrictions. I can only ship the runtime libraries or link the code
>> 
> into my 
>   
>> executable.
>> 
>
> You don't have to distribute their libraries to open your source,
> unless their API is covered by an NDA.
>
> As far as questions about myriad versions go, "Let us all know when
> you find out!" is as good an answer as any.
>
> 73
> Frank
> AB2KT
>
>
>
>
> Announce your digital  presence via our DX Cluster 
> telnet://cluster.dynalias.org
>
> Our other groups:
>
> http://groups.yahoo.com/group/dxlist/
> http://groups.yahoo.com/group/themixwgroup
> http://groups.yahoo.com/group/contesting
> http://groups.yahoo.com/group/wnyar
> http://groups.yahoo.com/group/Omnibus97 
>
>  
> Yahoo! Groups Links
>
>
>
>
>   


-- 
AMSAT Director and VP Engineering. Member: ARRL, AMSAT-DL,
TAPR, Packrats, NJQRP, QRP ARCI, QCWA, FRC. ARRL SDR WG Chair
"If you board the wrong train, it is no use running along the
corridor in the other direction. " - Dietrich Bonhoeffer

Re: [digitalradio] Re: Movement toward open digital software?

[Alex Flinsch]

On Jan 13, 2007, at 6:29 PM, Leigh L Klotz, Jr. wrote:

> - Separating the UI from the modems and rig control and using a  
> protocol
> between them would make it easier to write platform-specific
> best-of-breed UIs.  PSKCore.DLL is OK for this approach for  
> Windows, but
> as it uses the Microsoft component implementation framework, it  
> doesn't
> help cross-platform, just cross-application.


If developers used hamlib for the rig control part of the  
application, that part of the would be solved.

--
Alex / AB2RC
Running a Linux/Mac installation, where the only windows  are in the  
walls where they belong

[digitalradio] Re: Movement toward open digital software?

[Frank Brickle]

--- In digitalradio@yahoogroups.com, "Simon Brown" <[EMAIL PROTECTED]>
wrote:

> No matter, the terms under which I use this code specifically disallow 
> redistribution.

In other words, the *suppliers* of your support libraries have control
over the distribution rights of *your own* code?

Man, I'd never give up that kind of control over my own code. The kind
of damage users can do is trivial by comparison.

;-)

73
Frank
AB2KT

Re: [digitalradio] Re: Movement toward open digital software?

[Simon Brown]

- Original Message - 
From: "Frank Brickle" <[EMAIL PROTECTED]>
>
> Copyright and Open Source are not opposites. Copyright ownership is
> the precise legal foundation of, for example, the General Public
> License (GPL).
>

No matter, the terms under which I use this code specifically disallow 
redistribution.

Simon Brown, HB9DRV 

[digitalradio] Re: Movement toward open digital software?

[Frank Brickle]

--- In digitalradio@yahoogroups.com, "Simon Brown" <[EMAIL PROTECTED]>
wrote:

> Spot on. I use a commercial library from Codejock - www.codejock.com
- this 
> cannot be distributed. I also use other commercial libraries with
similar 
> restrictions. I can only ship the runtime libraries or link the code
into my 
> executable.

You don't have to distribute their libraries to open your source,
unless their API is covered by an NDA.

As far as questions about myriad versions go, "Let us all know when
you find out!" is as good an answer as any.

73
Frank
AB2KT

Re: [digitalradio] Re: Movement toward open digital software?

[Simon Brown]

- Original Message - 
From: "Dave Bernstein" <[EMAIL PROTECTED]>


>I suspect what Simon means is that the UI portion of his application
> contains code whose copyright is held by individuals other than him,
> thereby precluding release to open source without the holder's
> approval.

Spot on. I use a commercial library from Codejock - www.codejock.com - this 
cannot be distributed. I also use other commercial libraries with similar 
restrictions. I can only ship the runtime libraries or link the code into my 
executable.

Another reason for not making the UI code OpenSource is that we end up with 
a myriad of product variants, also I then get bombarded with questions about 
porting to Linux / MacOS, how do I compile etc.

Simon Brown
---
www.sysgem.com

[digitalradio] Re: Movement toward open digital software?

[Dave Bernstein]

I suspect what Simon means is that the UI portion of his application 
contains code whose copyright is held by individuals other than him, 
thereby precluding release to open source without the holder's 
approval.

Releasing an application to open source is easiest if one only 
include components or snippets whose licenses are compatible with the 
license one has chosen for the application. Otherwise, its necessary 
to track down the license holders and obtain their approval.

   73,

  Dave, AA6YQ


--- In digitalradio@yahoogroups.com, "Frank Brickle" <[EMAIL PROTECTED]> 
wrote:
>
> --- In digitalradio@yahoogroups.com, "Simon Brown" 
> wrote:
> 
> > I am *not* making it open source, only the decoding DLL's. The UI
> will never 
> > be open source as it uses copyrighted code.
> 
> Copyright and Open Source are not opposites. Copyright ownership is
> the precise legal foundation of, for example, the General Public
> License (GPL).
> 
> There is a simple, concise discussion of the issues involved at
> .
> 
> 73
> Frank
> AB2KT
>