Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Stelios Bounanos <lhams@enotty.net>
To: Stephane Fillod <f8cfe@free.fr>, Linux HAMs <Linux-hams@vger.kernel.org>
Cc: Tomi Manninen <oh2bns@sral.fi>
Subject: Re: Amateur Radio -> MacOS?
Date: Fri, 01 Feb 2008 00:10:16 +0000	[thread overview]
Message-ID: <8763x9zgd3.wl@obsidian.enotty.net> (raw)
In-Reply-To: <20080131221001.GD5891@charybde.local>

>>>>> On Thu, 31 Jan 2008 23:10:01 +0100, Stephane Fillod
>>>>> <f8cfe@free.fr> was rumoured to have said:

> Tomi Manninen skribis:
>> Frank Brickle wrote:
>> 
>>> Applications that use JACK move smoothly between Linux and OSX. They can 
>>> also take good advantage of FireWire sound systems like the Edirol FA-66.  
>>> Please see http://dttsp.org/wiki for an example of an SDR application that 
>>> runs on Linux and OSX without pain.
>> 
>> Yes, but IIRC, Jack is also callback based *) and that is the key in my
>> argument. Doable but non-trivial changes are needed. That requires
>> someone with the motivation and hardware to do it.
>> 
>> This is not meant to be an excuse why ham radio software is lacking
>> from OSX (and I don't even know if it really is), just a possible
>> explanation why at least some soundcard based Linux ham radio programs
>> are not trivial to port to OSX.

> What about Libjackasyn[1] and jacklaunch?
> Does PortAudio[2], which is also callback based, have a similar library?

IMO, PortAudio would be a much better option.

PortAudio is callback-based but, in v19, also has a blocking API.
Fldigi uses it and is able to access OSS, ALSA, and JACK. I understand
that PortAudio also supports the OSX sound system (CoreAudio?).

JACK support is a big bonus because it makes fldigi usable with DttSP[0]
and, to a lesser extent, because it makes it easy to run multiple
instances (to decode more than one signal at the same time and test /
experiment).

The move from OSS to blocking PortAudio was fairly straightforward in
fldigi and I would expect this to be the case for gMFSK also.

There are a couple of things to look out for. First, some sound system
features have been placed in PortAudio's "Host API extensions" in such a
way that they are actually unusable with dynamic linking. This has not
been a problem for fldigi, as there was no need to use those extensions
(though setting the JACK client name would be nice).

Second, the OSS style of opening/closing the device for capture/playback
works fine but has an undesirable side effect with Portaudio/JACK
streams -- the port bindings are reset.


[0] http://dttsp.org/wiki/index.php?title=Main_Page


73,
Stelios M0GLD.

-- 

Stelios Bounanos
perl -e 'print+reverse"t\nney.ttno\@esb"=~/(..)/sg'     #key: 0xE88A7F61

      reply	other threads:[~2008-02-01  0:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 16:49 Amateur Radio -> MacOS? IT2 Stuart Blake Tener, USNR
2008-01-31 17:42 ` Curt, WE7U
2008-01-31 18:25   ` IT2 Stuart Blake Tener, USNR
2008-01-31 18:41     ` Curt, WE7U
2008-01-31 19:06       ` Curt, WE7U
2008-01-31 19:21         ` Curt, WE7U
2008-01-31 18:41 ` Matti Aarnio
2008-01-31 20:35   ` Tomi Manninen
     [not found]     ` <fc22d18f0801311255q570b490ay4f0e50b0a602c288@mail.gmail.com>
2008-01-31 21:53       ` Tomi Manninen
2008-01-31 22:10         ` Stephane Fillod
2008-02-01  0:10           ` Stelios Bounanos [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8763x9zgd3.wl@obsidian.enotty.net \
    --to=lhams@enotty.net \
    --cc=Linux-hams@vger.kernel.org \
    --cc=f8cfe@free.fr \
    --cc=oh2bns@sral.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox