| |
VK7AX > SSTV 31.12.07 00:12l 194 Lines 6062 Bytes #999 (0) @ VKNET
BID : VK7AX-1012EU
Read: GUEST I3CRIS
Subj: [MM-SSTV] Digest Number 1707
Path: IZ3LSV<IW2OAZ<F4BWT<I0TVL<N9ZZK<VE2PKT<ZL2BAU<VK7NW
Sent: 071210/0009Z @:VK7NW.#ULV.TAS.AUS.OC #:31895 [NWTARIG] FBB7.00g $:VK7AX-1
From: VK7AX@VK7NW.#ULV.TAS.AUS.OC
To : SSTV@VKNET
There are 4 messages in this issue.
Topics in this digest:
1a. Re: MMSSTV Programming Interface
From: Simon Brown
1b. Re: MMSSTV Programming Interface
From: w6ids
1c. Re: MMSSTV Programming Interface
From: jdow
1d. Re: MMSSTV Programming Interface
From: Simon Brown
Messages
________________________________________________________________________
1a. Re: MMSSTV Programming Interface
Posted by: "Simon Brown" simon.brown@kns.ch simonbrown42
Date: Sat Dec 8, 2007 4:25 pm ((PST))
I'll make a request: please add API support for all user-selectable values
(in MMSSTV this is the Option menu, Setup MMSSTV(0)). Also it's often
necessary to use a difference device ID for TX and RX.
If this can be done I will add the MMSSTV engine to a small program of mine
(DM780).
Simon Brown, HB9DRV
----- Original Message -----
From: "Simon Brown" <simon.brown@kns.ch>
> >
> > Looking at ESSTVENG.txt I don't see any way for a 3rd-party program to
> > specify the soundcard or sample rates. Have I missed something or will
> > this be added in the future?
> >
Messages in this topic (5)
________________________________________________________________________
1b. Re: MMSSTV Programming Interface
Posted by: "w6ids" w6ids@verizon.net w6ids2003
Date: Sat Dec 8, 2007 9:26 pm ((PST))
----- Original Message -----
From: "Simon Brown" <simon.brown@kns.ch>
To: <MM-SSTV@yahoogroups.com>
Sent: Saturday, December 08, 2007 9:25 AM
Subject: Re: [MM-SSTV] MMSSTV Programming Interface
> > I'll make a request: please add API support for all user-selectable values
> > (in MMSSTV this is the Option menu, Setup MMSSTV(0)). Also it's often
> > necessary to use a difference device ID for TX and RX.
> >
> > If this can be done I will add the MMSSTV engine to a small program of
> > mine
> > (DM780).
> >
> > Simon Brown, HB9DRV
> >
GASP! There really is an all supreme entity after all. This is indeed
a Kodak moment if I ever saw one. It isn't even Christmas yet and
my birthday isn't until June....maybe it's someone else's birthday?
Howard W6IDS
Richmond, IN
Messages in this topic (5)
________________________________________________________________________
1c. Re: MMSSTV Programming Interface
Posted by: "jdow" jdow@earthlink.net ferdyfubar
Date: Sun Dec 9, 2007 5:20 am ((PST))
Howdy, Simon.
I played with this so long ago I had to dig to find my notes.
You have to bring up its option window. That's probably because there
are so many options available.
===8<---
LONG mmsOption(void)
~~~~~~~~~~~~~~~~~~~~
[Return value]
TRUE if the OK button is depressed
FALSE if the CANCEL button is depressed.
[Remarks]
This function opens the dialog box, with which the user can control the
parameters of the engine.
void mmsSetOptionTitle(LPCSTR pTitle)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[Parameter]
pTitle : Pointer to the title string
[Remarks]
This function specifies the title of the dialog box invoked by mmsOption.
If NULL or NULL string is passed as the parameter, the default text appears
in the dialog box title.
===8<---
The second function allows you to set your own title for the options
window.
There are so many options it gets tough to set them individually. It
would be nice to be able to specify the sound card. You CAN cheat my
editing the MMSSTV engine's ini file, there are only 117 options to
handle. If you close the engine, modify the file, and reopen the engine
the file gets read again.
Of late I've abandoned the huge monolithic project I had at one time with
WinPSK, remote control, and MMSSTV in it. Now I use separate programs that
are doctored to use a modified version of the TCP based remote sound and
com port communications. I modified them both to allow multiple connections
with the com port shared between programs. It's easier than a rat's nest
of USB<->RS232 dongles. (The audio port sharing is automatic in Windows.)
{^_^} Joanne, W6MKU
----- Original Message -----
From: "Simon Brown" <simon.brown@kns.ch>
Sent: Saturday, 2007, December 08 03:34
> > Hi,
> >
> > I have been asked to add SSTV to a digital mode program I am writing, part
> > of this would should ensure that the UI is consistent, so I would want to
> > be able to define all MMSSTV options via the API.
> >
> > Looking at ESSTVENG.txt I don't see any way for a 3rd-party program to
> > specify the soundcard or sample rates. Have I missed something or will
> > this be added in the future?
> >
> > Simon Brown, HB9DRV
Messages in this topic (5)
________________________________________________________________________
1d. Re: MMSSTV Programming Interface
Posted by: "Simon Brown" simon.brown@kns.ch simonbrown42
Date: Sun Dec 9, 2007 6:30 am ((PST))
Hi Joanne,
Having been watching MMSSTV decoding pictures of a young Miss Claus (thanks
to I8LPR and EB5DZC) I am actually quite bitten by the SSTV bug. To be
honest I think that I should write my own SSTV engine(s), there's so much
that I would want to do that it becomes unfair to ask JE3HHT to add the
support.
Today I have been adding picture support using MFSK16, this works very well
in receive, I must get the transmit side working. I expect that a protocol
such as MFSK16 will outperform analogue SSTV. I haven't looked to see what
protocol is used for digital SSTV.
At the moment I seem to be able to automatically decode Scottie, other modes
are not displayed properly. I am using the defaults for MMSSTV and have not
read any user guides. I'm using my Elecraft K3 as RX.
Simon Brown, HB9DRV
----- Original Message -----
From: "jdow" <jdow@earthlink.net>
> >
> > I played with this so long ago I had to dig to find my notes.
> >
> > You have to bring up its option window. That's probably because there
> > are so many options available.
> >
Messages in this topic (5)
________________________________________________________________________
________________________________________________________________________
Read previous mail | Read next mail
| |
