On Wed, Feb 5, 2014 at 9:35 AM, Tom Rondeau wrote:
> On Wed, Feb 5, 2014 at 2:25 AM, Tom McDermott
> wrote:
>> A flow graph that used to work in Gnuradio 3.7 now fails in 3.7.2.1
>>
>> I've isolated it to the QT GUI Sink component, which causes the flowgraph to
>> immediately
>> aborts with a se
On Wed, Feb 5, 2014 at 2:25 AM, Tom McDermott wrote:
> A flow graph that used to work in Gnuradio 3.7 now fails in 3.7.2.1
>
> I've isolated it to the QT GUI Sink component, which causes the flowgraph to
> immediately
> aborts with a segmentation fault.
>
> Core was generated by `python ./top_bloc
A flow graph that used to work in Gnuradio 3.7 now fails in 3.7.2.1
I've isolated it to the QT GUI Sink component, which causes the flowgraph to
immediately
aborts with a segmentation fault.
Core was generated by `python ./top_block.py'.
Program terminated with signal 11, Segmentation fault.
#0
On 12/04/2013 04:35 PM, Tom Rondeau wrote:
>> 1.) The waterfall display in the QT GUI sink seems to be about twice as
>> fast as the standalone QT GUI Waterfall sink. That's nothing bad but I'd
>> be curious where this come from.
>
> You can change the rate by adjusting the Update Period in the
>
On Wed, Dec 4, 2013 at 6:18 AM, Stefan Gofferje wrote:
> Hi,
>
> so I got gnuradio basically running and started to experiment. 2 things,
> I noticed:
>
> 1.) The waterfall display in the QT GUI sink seems to be about twice as
> fast as the standalone QT GUI Waterfall sink. That's nothing bad but
On 12/04/2013 02:06 PM, Martin Braun (CEL) wrote:
>> 2.) When I choose the Time Domain Display tab in the QT GUI sink, the
>> window just closes. Nothing on the console, like error messages, etc...
>> Just *puff* gone... Is there a know bug with that?
>
> Have you tried calling the .py-file genera
On Wed, Dec 04, 2013 at 01:18:56PM +0200, Stefan Gofferje wrote:
> so I got gnuradio basically running and started to experiment. 2 things,
> I noticed:
>
> 1.) The waterfall display in the QT GUI sink seems to be about twice as
> fast as the standalone QT GUI Waterfall sink. That's nothing bad bu
Hi,
so I got gnuradio basically running and started to experiment. 2 things,
I noticed:
1.) The waterfall display in the QT GUI sink seems to be about twice as
fast as the standalone QT GUI Waterfall sink. That's nothing bad but I'd
be curious where this come from.
2.) When I choose the Time Dom
On Sun, May 19, 2013 at 4:10 PM, Hans Van Ingelgom
wrote:
> Ok, could you add me as a contributor? I just added an account (username:
> hansvi).
Ok, that's done.
When you report it, also add version numbers of the libraries you're
using (Qt and Qwt, specifically). I think that has to have someth
Ok, could you add me as a contributor? I just added an account (username:
hansvi).
On Sun, May 19, 2013 at 11:25 AM, Tom Rondeau wrote:
> On Sun, May 19, 2013 at 12:58 AM, Hans Van Ingelgom
> wrote:
> >
> > If you just make any signal source and a QT GUI Sink, you'll see that the
> > frequency
Hans Van Ingelgom writes:
> If you just make any signal source and a QT GUI Sink, you'll see that the
> frequency scale is wrong: a 32ksps signal will show a frequency range from
> -8kHz to +8kHz (instead of -16...16kHz).
Ah, I encountered this issue on Mac and reported earlier. I didn't know
if
On Sun, May 19, 2013 at 12:58 AM, Hans Van Ingelgom
wrote:
>
> If you just make any signal source and a QT GUI Sink, you'll see that the
> frequency scale is wrong: a 32ksps signal will show a frequency range from
> -8kHz to +8kHz (instead of -16...16kHz).
>
> Also, if you keep the default FFT siz
If you just make any signal source and a QT GUI Sink, you'll see that the
frequency scale is wrong: a 32ksps signal will show a frequency range from
-8kHz to +8kHz (instead of -16...16kHz).
Also, if you keep the default FFT size of 1024, the chooser widget shows
256, but in reality the FFT size is
> From: discuss-gnuradio-bounces+dr=drelectro@gnu.org
> [mailto:discuss-gnuradio-bounces+dr=drelectro@gnu.org] On Behalf Of
> Marcus D. Leech
> Sent: Monday, 4 April 2011 1:57 AM
> To: discuss-gnuradio@gnu.org
> Subject: Re: [Discuss-gnuradio] QT Gui Sink
>
> On 04/02/2011 08:
On 04/04/2011 08:06 AM, Tom Rondeau wrote:
Right, and I believe it even works correctly now... The original API had the
update time information as part of the constructor, but I didn't see that as
the correct thing to do, but I also did not think to export it.
I am working on updating the QtG
On Sun, Apr 3, 2011 at 11:57 AM, Marcus D. Leech wrote:
> On 04/02/2011 08:11 AM, Philip Balister wrote:
>
>> Is there a way to control the update rate on the QT Gui sink? I have it
>> running on the E100, but it would be helpful if I could slow down the update
>> rate.
>>
>> Philip
>>
>> ___
On 04/02/2011 08:11 AM, Philip Balister wrote:
Is there a way to control the update rate on the QT Gui sink? I have
it running on the E100, but it would be helpful if I could slow down
the update rate.
Philip
___
Discuss-gnuradio mailing list
Discus
Is there a way to control the update rate on the QT Gui sink? I have it
running on the E100, but it would be helpful if I could slow down the
update rate.
Philip
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/
18 matches
Mail list logo
