On 01/16/2021 09:00 PM, Glen Langston wrote:
Dear Marcus and all,
Thanks for all your efforts. I really to appreciate all you’ve done.
Best regards,
Glen
We know you do, Glen.
Sometimes when you haven't been "inside the sausage factory" it can be a
bit hard to understand why things are
Dear Marcus and all,
Thanks for all your efforts. I really to appreciate all you’ve done.
Best regards,
Glen
> On Jan 16, 2021, at 8:30 PM, Marcus Müller wrote:
>
> Hi!
>
> On 17.01.21 00:56, KB3CS - Chris wrote:
>
>> why does not in my mind figure just as prominently as GSoC: other
>>
Hi!
On 17.01.21 00:56, KB3CS - Chris wrote:
> why does not in my mind figure just as prominently as GSoC: other
> campaigns like GSoD or GSoGUI ? (does anyone actually need me to fill in
> the definitions for those abbreviations?)
Well, the G in GSoC is "Google", not "GNU Radio": Google
On Fri, 08 Jan 2021 22:16:22 -0500, "Marcus D. Leech" <
patchvonbr...@gmail.com> wrote a great many things, and then this excerpt:
> I "get" the whole "oh, but it's so very close to what I need". But GR
> really is just a specialized programming environment, and GRC
>has the unfortunate (in
On 1/13/21 10:13 AM, Marcus D. Leech wrote:
On 01/12/2021 02:51 PM, Lamar Owen wrote:
I'm trying to debug and patch the UHD stack for USRP1 with DBS-RX
daughterboard; it just quit working, and while I've reported to the
UHD list no action has been taken to fix the regression.
I was able to
On 01/12/2021 02:51 PM, Lamar Owen wrote:
I'm trying to debug and patch the UHD stack for USRP1 with DBS-RX
daughterboard; it just quit working, and while I've reported to the
UHD list no action has been taken to fix the regression.
I was able to reproduce the regression issue with DBS-RX
[Accidentally sent this from the wrong account this is the right
one]
On 1/5/21 10:30 AM, Glen Langston wrote:
Concerning my previous email, sent in extreme frustration. I
understand that we all want to make improvements and progress.
I want to take a moment and thank Glen for posting
Very many thanks, Marcus.
Best wishes. Paul
On 01/08/2021 12:38 AM, p...@dbnut.com wrote:
[Apologies for the lack of paragraph breaks in that last - taken by
surprise after using a crude editor]
Thank you, Marcus, for taking so much trouble to respond so
comprehensively. And with such good grace!
Your detailed section on dependencies
Hi Paul:
FYI, I was in largely the same position re DSP and SDR several years ago, that
is, of a newbie with strong computing science and math background, and fairly
good radio systems knowledge, but with dust on the mathematics side for a
couple of decades.
I found a fantastic introductory
[Apologies for the lack of paragraph breaks in that last - taken by
surprise after using a crude editor]
Thank you, Marcus, for taking so much trouble to respond so
comprehensively. And with such good grace!
Your detailed section on dependencies is very sobering and helps me
understand much
On 01/07/2021 03:32 PM, p...@dbnut.com wrote:
Prompted to write by Glen Langston's post, I'm an old man resurrecting
an old moan, and in a minority that (I believe) is just not catered for:
* Windows user
* Non-programmer (of any great consequence)
It was NEVER a goal of GR to make it easy for
Prompted to write by Glen Langston's post, I'm an old man resurrecting
an old moan, and in a minority that (I believe) is just not catered for:
* Windows user
* Non-programmer (of any great consequence)
A couple of years ago I became hooked on GRC after watching Balint
Seeber's YouTube videos
Hi all,
to jump in from a point of someone who has contributed "improvements"
over the last couple of years.
Many of your points are vaild, I understand your frustation and pain of
continuouly having to adapt to new methodologies.
Believe me when I say we are not these changes are not
On 01/05/2021 09:24 AM, Johannes Demel wrote:
Hi Glen,
I fully understand your frustration to make things work long term and
constant breakage.
There are, however, reasons why breaking changes are unavoidable. Some
examples are:
1. GRC used Cheetah with XML for block definitions BUT:
Dear Johannes and all members of the GNURadio community,
Happy New Year. I hope all are doing well.
Thanks for all your efforts!
Concerning my previous email, sent in extreme frustration. I understand
that we all want to make improvements and progress.
Concerning your points below.
Hi Glen,
I fully understand your frustration to make things work long term and
constant breakage.
There are, however, reasons why breaking changes are unavoidable. Some
examples are:
1. GRC used Cheetah with XML for block definitions BUT:
Cheetah got unmaintained for years. Cheetah is only
On Tue, 22 Dec 2020 20:21:42 -0500
Glen Langston wrote:
[snip]
> I like the SDRPlay device, but it can not be used in gnuradio 3.8. According
> to the web.
> But the web indicates it might be usable in 3.9
> So I installed 3.9 only to find that swig has been replace by pybind. This
> breaks
Glen - which of your modules do you need to port? Maybe one or more of us
can give you a hand, since this is for education and RA.
Backward compatibility is important. The choice the GR devs are trying to
make in some cases is between backward compatibility and software that can
continue to grow
On 12/22/2020 08:21 PM, Glen Langston wrote:
Hello GNuradio Superheros,
I have to say, after 5 years with gnu radio, I’m either tool old or
something has to change.
I’ve been trying to produce some tools for High School teacher to do radio
astronomy.
and for that gnuradio 3.7 was perfectly
Hello GNuradio Superheros,
I have to say, after 5 years with gnu radio, I’m either tool old or
something has to change.
I’ve been trying to produce some tools for High School teacher to do radio
astronomy.
and for that gnuradio 3.7 was perfectly fine. However some people are
continuing
to
21 matches
Mail list logo
