What alterations would it take for this codebase to be adopted in a
bunch of commercial products in the same way as BSD Unix and Linux?
I believe new research and signal processing coding can only be done
by experts. I also believe more new implementations and ports will be
done by non-experts,
David does code in an older style and that can look odd to newer
programmers, but the newer styles look verbose to older programmers. I tend
to use every const declaration possible, etc., so that the compiler will
show me more coding errors and it has frustrated me that the codec2 code
doesn't do
A lot boils down to the question. I think codec2 is well documented and
list has always been helpful. I also think the last question asked about
the UART was really a question about how to use the UART on the STM32
without breaking Codec2. The answer was use interrupt driven UART (or DMA
UART)
I've been following development for a while too, and think I can answer
some of these questions
In the main, though, the questions can be answered by understanding the
difference between the CODEC (which is used to encode and decode voice into
bits and bytes) and the modem (which is used to
On 11/05/2012 07:03 AM, Thomas Kocourek wrote:
there are questions which can only be answered by folks using the
'product' in the real world.
Yes, many. But maybe not these. :-)
What happens when the sender and receiver equipment drift apart in
frequency?
Most softmodem
Hello Thomas,
1/ The fdmdv modem can sync up with +/- 200 Hz frequency offsets. Once
it's synced it will track changes in frequency offset of several Hz per
second. So tuning and drift are less of a problem than for regular SSB.
2/ I am running the prototype fdmdv2 GUI program on a 4 year old
On 11/05/2012 01:04 PM, David Rowe wrote:
2/ I am running the prototype fdmdv2 GUI program on a 4 year old laptop
(dual core 2.4MHz) at about 30% CPU load.
What load with graphics turned off? I'd hope that's mostly graphics.
One would believe that a fixed-point implementation would run on
