Re: [Discuss-gnuradio] sync_interpolator

2013-08-30 Thread Miklos Maroti
Thanks. This confirms what I was saying. Miklos On Aug 28, 2013 7:07 AM, "Martin Braun (CEL)" wrote: > Let's cover some signal processing basics: > > Say our block's input signal is x[k] and the output signal is y[k]. > Let's assume there's one input to keep things simple. > > If a block has a hi

Re: [Discuss-gnuradio] sync_interpolator

2013-08-28 Thread Martin Braun (CEL)
Let's cover some signal processing basics: Say our block's input signal is x[k] and the output signal is y[k]. Let's assume there's one input to keep things simple. If a block has a history of N, the output depends on N samples of the input, or y[k] = f(x[k], x[k-1], ..., x[k-N-1]). If the block

Re: [Discuss-gnuradio] sync_interpolator

2013-08-27 Thread Miklos Maroti
Hi Martin, On Tue, Aug 27, 2013 at 3:07 AM, Martin Braun (CEL) wrote: > On Tue, Aug 27, 2013 at 02:43:32AM -0500, Miklos Maroti wrote: >> Hi Martin, >> >> I have checked the tutorials, but they do not give precise details. > > http://gnuradio.org/redmine/projects/gnuradio/wiki/OutOfTreeModules >

Re: [Discuss-gnuradio] sync_interpolator

2013-08-27 Thread Martin Braun (CEL)
On Tue, Aug 27, 2013 at 02:43:32AM -0500, Miklos Maroti wrote: > Hi Martin, > > I have checked the tutorials, but they do not give precise details. http://gnuradio.org/redmine/projects/gnuradio/wiki/OutOfTreeModules discusses the whole concept several times. > Here is what I have discovered with

Re: [Discuss-gnuradio] sync_interpolator

2013-08-27 Thread Miklos Maroti
Hi Martin, I have checked the tutorials, but they do not give precise details. Here is what I have discovered with a general block: 1) set_history(1+m) will simply fill your input buffer with m many zero items at startup, then your input data will follow. 2) If you actually want to see more samp

Re: [Discuss-gnuradio] sync_interpolator

2013-08-27 Thread Martin Braun (CEL)
On Tue, Aug 27, 2013 at 12:11:48AM -0500, Miklos Maroti wrote: > Hi Guys, > > I do not understand how set_history and fixed rate blocks are > interacting. Supposedly, the scheduler can figure out a static > schedule for sync blocks. However, the sync_interpolator is forcasting > this > > int sync

[Discuss-gnuradio] sync_interpolator

2013-08-26 Thread Miklos Maroti
Hi Guys, I do not understand how set_history and fixed rate blocks are interacting. Supposedly, the scheduler can figure out a static schedule for sync blocks. However, the sync_interpolator is forcasting this int sync_interpolator::fixed_rate_noutput_to_ninput(int noutput_items) { return nou