# Gqrx / gnuradio / BladeRF

**URL:** <https://www.ruby-forum.com/t/gqrx-gnuradio-bladerf/236756>\
**Category:** GNU Radio\
**Created:** [October 1, 2013, 9:16am UTC](https://www.ruby-forum.com/t/gqrx-gnuradio-bladerf/236756 "2013-10-01T09:16:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![alcina](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/a587f6/32.png) [@alcina](https://www.ruby-forum.com/u/alcina)\
**Post date:** [October 1, 2013, 9:16am UTC](https://www.ruby-forum.com/t/gqrx-gnuradio-bladerf/236756/1 "2013-10-01T09:16:31Z")

</div>

Hi,

Not exactly the perfect list for it, but as the specialists are all here  
in  
this list, it somehow should fit 🙂

When using gqrx with the BladeRF I observe that tuning takes “ages”.  
Every  
entered or changed frequency digit takes almost one second to be  
accepted,  
and I mean to remember that directly out of gnuradio this is much  
faster,  
although usually I do there no live tuning, but sending the frequency to  
the  
unit just once, out of a block. When using the USRP1 with WBX or a  
RTL2832/E4000 receiver, tuning occurs without noticeable delay.

Bug or feature? 🙂

With best regards

Ralph.

---

<div class="post-metadata">

**Author:** ![Ralph\_ASSchmidS\_dk](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/91b2a8/32.png) [@Ralph\_ASSchmidS\_dk](https://www.ruby-forum.com/u/Ralph_ASSchmidS_dk)\
**Post date:** [October 1, 2013, 4:07pm UTC](https://www.ruby-forum.com/t/gqrx-gnuradio-bladerf/236756/2 "2013-10-01T16:07:22Z")

</div>

Hi Ralph,

I’ve noticed that as well, and we need to fix it. I believe it’s a  
bug. Not sure if it’s in libbladeRF or gr-osmosdr, but we’re on it.

Sorry for the inconvenience.

Brian

On Tue, Oct 1, 2013 at 3:14 AM, Ralph A. Schmid, dk5ras

---

<div class="post-metadata">

**Author:** ![Ralph\_ASSchmidS\_dk](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/91b2a8/32.png) [@Ralph\_ASSchmidS\_dk](https://www.ruby-forum.com/u/Ralph_ASSchmidS_dk)\
**Post date:** [October 1, 2013, 4:43pm UTC](https://www.ruby-forum.com/t/gqrx-gnuradio-bladerf/236756/3 "2013-10-01T16:43:01Z")

</div>

Hi,

> Hi Ralph,
> 
> I’ve noticed that as well, and we need to fix it. I believe it’s a  
> bug. Not sure if it’s in libbladeRF or gr-osmosdr, but we’re on it.

OK, great to hear.

> Sorry for the inconvenience.

Huh?! Early adopters we are, guess this is normal 🙂

Is there are dedicated mailing list for BladeRF? The forum is so  
inconvenient… Or should we keep it here?

> Brian

Ralph.

---

<div class="post-metadata">

**Author:** ![Ralph\_ASSchmidS\_dk](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/91b2a8/32.png) [@Ralph\_ASSchmidS\_dk](https://www.ruby-forum.com/u/Ralph_ASSchmidS_dk)\
**Post date:** [October 1, 2013, 5:08pm UTC](https://www.ruby-forum.com/t/gqrx-gnuradio-bladerf/236756/4 "2013-10-01T17:08:09Z")

</div>

On Tue, Oct 1, 2013 at 10:41 AM, Ralph A. Schmid, dk5ras  
[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> > Sorry for the inconvenience.
> 
> Huh?! Early adopters we are, guess this is normal 🙂
> 
> Is there are dedicated mailing list for BladeRF? The forum is so  
> inconvenient… Or should we keep it here?

There is an IRC channel on freenode, #bladerf, which has decent  
activity. No mailing list yet. I agree the forum is not ideal.

Best bet is through IRC and/or using the issue tracker on github.

Brian