lör 2023-12-30 klockan 12:44 +1100 skrev glen english LIST:
> It's an interesting idea. For real time work, taking it to the
> extreme,
> putting a bit of latency in there-
>
> the encoder and decoder pair, could over time , generate shortcut
> tokens
> / lookup for whole words
>
> IE encoder
I'm wondering how much of a data size difference there is between this
proposed sound encoding, the International Phonetic Alphabet, and
ASCII of spelled words?
Brian
On Friday, December 29, 2023 at 08:46:43 PM EST, glen english LIST
wrote:
It's an interesting idea. For real time
It's an interesting idea. For real time work, taking it to the extreme,
putting a bit of latency in there-
the encoder and decoder pair, could over time , generate shortcut tokens
/ lookup for whole words
IE encoder continuously stores the encoded words. (it doesnt know the
word, only the
I personally very much doubt that. You can get a higher symbol rate by tapping
a CW key.
On 29 December 2023 12:54:02 UTC, "Tomas Härdin" wrote:
>
>I think Dave posted on his blog a while back that the effective data
>rate of human speech is on the order of 1-10 bit/s or so
fre 2023-12-29 klockan 10:44 +1100 skrev glen english LIST:
> Hi Tomas
> "codec2 + zip makes for even smaller files"
>
> implying that there is still redundancy to remove in the codec2
> encoded voice files
> That sounds like low hanging fruit to pick.
That is not surprising. In speech you
Hi Glen,
you're right, there is still some redundant information in time domain between
frames. This is on purpose, as Codec2 is meant to be a real-time speech codec
for wireless transmissions, which generelly speaking has to be considered to
have bad channels... The main idea is that you can
Hi Tomas
"codec2 + zip makes for even smaller files"
implying that there is still redundancy to remove in the codec2 encoded voice
files
That sounds like low hanging fruit to pick.
I guess though that is across a large number of frames (an audio book), where
there may be redundancy /
tor 2023-12-28 klockan 07:20 +1030 skrev david:
> Hi Tomas,
>
> Thanks for that work. 1.2 was clean up of the Git repo, so nothing
> much has changed in terms of functionality. We have no plans for a
> fixed point version. The .c2 file format is a corner use-case (we
> focus mainly on the HF
I would think, that a floating pt implementation on a soft FPGA
processor core with floating point would take less area that a purely
FPGA fixed point HDL implementation. The reason is that the amount of
work required to do (in terms of computations per cycle) does not really
take advantage
Hi Tomas,
Thanks for that work. 1.2 was clean up of the Git repo, so nothing
much has changed in terms of functionality. We have no plans for a
fixed point version. The .c2 file format is a corner use-case (we
focus mainly on the HF radio use case), but we have no plans to change
it.
A road
Hi Tomas,
Someone did a FPGA implementation a while back for a university project.
That's the closest we've gotten to a fixed-point implementation. Right now,
there are no plans to port it officially but this may be revisited later.
Thanks,
-Mooneer K6AQ
On Wed, Dec 27, 2023 at 10:11 AM Tomas
Hi
I see codec2 has now reached version 1.2.0. I'm working on updating the
libcodec2 binding in libavformat in FFmpeg accordingly.
So far I've been conservative, only allowing major version 0 and
requiring version to be >= 0.8. So in effect versions 0.8 to 0.255. Now
that 1.X is out I'm updating
12 matches
Mail list logo
