Re: [Discuss-gnuradio] Solved! Repeat Block/New Repeat Block

2015-08-03 Thread Marcus Müller
Hi Kevin, I'm really happy about this! Hope you like the brave new C++ world ;) Now, curious as I am, (and a little ashamed for not replying earlier,) could you share your code with us? Best regards, Marcus On 02.08.2015 16:46, Kevin McQuiggin wrote: > Hi All: > > My previous report of lock-up

Re: [Discuss-gnuradio] Solved! Repeat Block/New Repeat Block

2015-08-02 Thread Francisco Albani
:) (Are you sure you meant to thank me? Hahaha... I only mentioned the underlined parameters! :P ) Sometimes I still find myself looking for the cause of a stopped flowgraph, to finally find I connected two streams with different sample rates to the same GUI sink. 2015-08-02 14:25 GMT-03:00 Tom

Re: [Discuss-gnuradio] Solved! Repeat Block/New Repeat Block

2015-08-02 Thread Kevin McQuiggin
> Kevin, > > Yes, the qtgui sinks can only accept streams coming in at the same sample > rate, and the repeat block would change that. Glad you figured it out. I > really thought that I had added that warning to the manual page, but I don't > see it in the published manual. I need to check on

Re: [Discuss-gnuradio] Solved! Repeat Block/New Repeat Block

2015-08-02 Thread Tom Rondeau
On Sun, Aug 2, 2015 at 10:46 AM, Kevin McQuiggin wrote: > Hi All: > > My previous report of lock-up issues with both the standard Repeat block, > and a new OOT block that I wrote to allow variable interpolation can be > ignored. > > The issue that generated my report was my use of a dual-input ti

[Discuss-gnuradio] Solved! Repeat Block/New Repeat Block

2015-08-02 Thread Kevin McQuiggin
Hi All: My previous report of lock-up issues with both the standard Repeat block, and a new OOT block that I wrote to allow variable interpolation can be ignored. The issue that generated my report was my use of a dual-input time sink. I was feeding a base [0,1] signal into one input, and the