This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://firstname.lastname@example.org/.ikjtel ikj1234i at yahoo.com
Look, the repeater.vocoder block was designed for a real-time, multi-channel, full-duplex environment. File input was never really a design req... Also, you didn't mention that a valid output file was appearing. Finally, not everyone accepts "attachments"... Thx Max ________________________________ From: Matt Mills <mmills at 2bn.net> To: op25-dev at yahoogroups.com Sent: Monday, September 10, 2012 10:32 AM Subject: Re: [op25-dev] Re: repeater.vocoder doesnt run to completion [1 Attachment] [Attachment(s) from Matt Mills included below] Max, Did the attachment not come through? That has the actual python I was using. Either way the vocoder is instantiated as: repeater.vocoder(False, False, 0, "", 0, False) Here are a few lines of input: 3ca 01f fd1 cba 007 5bb 3a4 09a ce8 a43 d38 011 3ff 445 07a 0b0 2e3 a19 5ba 352 00b 77f 6bb 08e 26e df2 0ec 257 002 022 74b 0a0 2ad 36c 579 1bd 686 251 7ee 0ae 2e4 cb6 e2c e68 402 527 6e3 0f0 2da 0ef 37b 11c 00c 21e 7c9 03e 29b 2ed 0b2 583 018 2ed 47f 048 259 a3d c62 b06 01c 268 04b 0fe 19d 0de be8 55f 030 63e 7c6 07e 2af a65 d05 2ee 7d8 599 439 092 I've also attached the entire file. It generates a valid wav file file, it just never terminates and remains running at 100% cpu. Thanks, Matt. On Mon, Sep 10, 2012 at 5:37 AM, ikj1234i <ikj1234i at yahoo.com> wrote: > > >This isn't really enough info, could be many different things. > >First what arg(s) are you passing to repeater.vocoder ? > >Second, the input in decoder mode is actually readable ASCII text. Can you post a few lines of your input file ? > >Max > > >--- In op25-dev at yahoogroups.com, Matt Mills <mmills at ...> wrote: >> >> Hi All, >> >> I'm trying to have repeater.vocoder() run as a small app to read from >> a file sink and write to a wav sink... If I replace the vocoder with a >> char_to_short() block it works as expected, however with the vocoder >> in place it never completes... >> >> Also, it looks as though even though it has run out of samples the >> vocoder thread continuously runs at 100% cpu. >> >> Anyone have any ideas? (associated python is attached. >> >> thanks, >> Matt. >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/op25-dev/attachments/20120910/98ab13ec/attachment.htm>