Hi Jeroen and David, Thanks for recognising I have a problem.
I've had a look at README_data.md and I'm no wiser. I do this, decode an audio file: prompt$ freedv_data_raw_rx 700D ve9qrp_700d.wav test1.700C and, it should be mode 700C data: prompt$ c2dec 700C test1.700C - | aplay -f S16 What do I have to do to "make" test1.700C a listenable mode 700C file? Preferably suitable for retransmission. And, can I get a Codec2 library revision number this works with? Alan VK2ZIW On Tue, 7 Jul 2020 06:20:42 +0930, David Rowe wrote > Hi Jeroen, > > > The easiest would be to fix 700D to use the same pattern as the other modes. > > But maybe we should fix all of them to use the 700D pattern and make the > > rawdatarx/rawdatatx truly independent of any codec2 knowledge. > > @David, do you have a preference? > > Perhaps the latter, however we still might find some of the modes don't > fill an integer number of bytes. > > Option 3 is we could just leave it for now, and let the API caller deal > with it. As explained in: > > https://github.com/drowe67/codec2/blob/master/README_data.md > > .... the idea of the raw data API was to support new HF data > waveforms, that will have much larger packet sizes, an integer > number of bytes, and other features that make them more suitable for > production HF data applications. So I just used the existing voice- > oriented waveforms as a placeholder for now. > > Cheers, > David > > _______________________________________________ > Freetel-codec2 mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 --------------------------------------------------- Alan VK2ZIW OpenWebMail 2.53, nothing in the cloud. _______________________________________________ Freetel-codec2 mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freetel-codec2
