Re: [Svxlink-devel] Block Size of MsgHandler AudioPacer
Brought to you by:
sm0svx
From: <st...@ar...> - 2008-11-08 20:43:47
|
I found a solution, that seems to work, although you might not be happy about it. The problem is that the TX has no additional FIFO after the Pacer, so it can easily run full or empty. When it runs full, the sinkWriteSamples call in the Pacer's timer functions returns zero, disabling further timer action. When the TX has free stream spaces, it calls the resumeOutput function, that restarts the timer again. But when the timer event is fired, it is already too late and the TX ran empty. To avoid this, not only the timer needs to be restarted in the resume function, but also the block output timer function has to be called immediately. vy 73s de Steve, DH1DM ----- Original Nachricht ---- Von: st...@ar... An: svx...@li... Datum: 08.11.2008 18:28 Betreff: Re: [Svxlink-devel] Block Size of MsgHandler AudioPacer > > Hi Tobias, > > while debugging the AudioPacer problem I found one issue in line 284 of > AsyncAudioPacer.cpp: > The current code in svn rev 1503 at this line is > buf_pos -= samples_written; > but I think it should be > buf_pos -= tot_samples_written; > Whin this modification the audio does not completely hang any more, when > using a 512 entry buffer, > but the Pacer still inserts gaps. > > vy 73s de Steve, DH1DM > > ----- Original Nachricht ---- > Von: Tobias Blomberg <sm...@us...> > An: Discussions about development issues > <svx...@li...> > Datum: 03.11.2008 09:01 > Betreff: Re: [Svxlink-devel] Block Size of MsgHandler AudioPacer > > > Strange. Let me know what you find out. I guess it's safe to use 256 byte > > > blocks for both 8 and 16k for now then. > > > > 73's de SM0SVX / Tobias > > > > > > On Sunday 02 November 2008 22:09:47 st...@ar... wrote: > > > Hi Tobias, > > > > > > allthough it is a good idea to put an AudioPacer after the MsgHandler, > I > > > have bad news. Msg audio does not work when a block size of 512 is > used, > > > which is the default case at 16 kHz. Setting it to 256 (8 Khz default > > > value) works fine at 16 kHz, but 512 does not work at both 8 and 16 > kHz. > > > Further investigations in process... > > > > > > vy 73s de Steve, DH1DM > > > > > > > > > > ------------------------------------------------------------------------- > > > This SF.Net email is sponsored by the Moblin Your Move Developer's > > > challenge Build the coolest Linux based applications with Moblin SDK & > > win > > > great prizes Grand prize is a trip for two to an Open Source event > > anywhere > > > in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > > _______________________________________________ > > > Svxlink-devel mailing list > > > Svx...@li... > > > https://lists.sourceforge.net/lists/listinfo/svxlink-devel > > > > > > > > ------------------------------------------------------------------------- > > This SF.Net email is sponsored by the Moblin Your Move Developer's > > challenge > > Build the coolest Linux based applications with Moblin SDK & win great > > prizes > > Grand prize is a trip for two to an Open Source event anywhere in the > world > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > _______________________________________________ > > Svxlink-devel mailing list > > Svx...@li... > > https://lists.sourceforge.net/lists/listinfo/svxlink-devel > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Svxlink-devel mailing list > Svx...@li... > https://lists.sourceforge.net/lists/listinfo/svxlink-devel > |