Re: [Discuss-gnuradio] Feature #394

2012-03-09 Thread Tom Rondeau
On Thu, Mar 8, 2012 at 6:05 PM, Andrew Davis wrote: > Ok, sounds good, also I've only been updating cmake files, is there a > date when the switch from autotools will become official? > > ~Andrew No, no official date. We're still have a few things in mind to try out and work with, so it comes do

Re: [Discuss-gnuradio] Feature #394

2012-03-08 Thread Andrew Davis
Ok, sounds good, also I've only been updating cmake files, is there a date when the switch from autotools will become official? ~Andrew On Thu, Mar 8, 2012 at 5:56 PM, Tom Rondeau wrote: > On Thu, Mar 8, 2012 at 5:40 PM, Andrew Davis > wrote: >> >> >As for the complex bandpass, we really do nee

Re: [Discuss-gnuradio] Feature #394

2012-03-08 Thread Tom Rondeau
On Thu, Mar 8, 2012 at 5:40 PM, Andrew Davis wrote: > >As for the complex bandpass, we really do need that. I know I've used it > in GNU Radio-based projects before, and I'd bet >others have/are, too. > Creating it as an LPF and the frequency shifting it is a perfectly valid > way of creating this

Re: [Discuss-gnuradio] Feature #394

2012-03-08 Thread Andrew Davis
>As for the complex bandpass, we really do need that. I know I've used it in >GNU Radio-based projects before, and I'd bet >others have/are, too. Creating >it as an LPF and the frequency shifting it is a perfectly valid way of >creating this kind of a >filter, and it enforces symmetrical transit

Re: [Discuss-gnuradio] Feature #394

2012-03-08 Thread Tom Rondeau
On Thu, Mar 8, 2012 at 1:07 PM, Andrew Davis wrote: > Thanks, > > All the 'fix' comments are there as I was debugging on a remote > machine using github as an intermediate for all my little changes. > I'll get those merged into real comments before the real merge. Same > for the AM demods, my gith

Re: [Discuss-gnuradio] Feature #394

2012-03-08 Thread Andrew Davis
Thanks, All the 'fix' comments are there as I was debugging on a remote machine using github as an intermediate for all my little changes. I'll get those merged into real comments before the real merge. Same for the AM demods, my github optfir branch is for my local testing and will only include o

Re: [Discuss-gnuradio] Feature #394

2012-02-27 Thread Tom Rondeau
On Fri, Feb 24, 2012 at 9:48 PM, Andrew Davis wrote: > Ok, I've got a branch on github: > https://github.com/glneo/gnuradio-davisaf/tree/optfir with optfir > ported and working in C++, it's part of gr ( gr.optfir ) like firdes. > This keeps the filter design tools together and allows the old optfi

Re: [Discuss-gnuradio] Feature #394

2012-02-24 Thread Andrew Davis
Ok, I've got a branch on github: https://github.com/glneo/gnuradio-davisaf/tree/optfir with optfir ported and working in C++, it's part of gr ( gr.optfir ) like firdes. This keeps the filter design tools together and allows the old optfir to still be imported and used until I can get all the exampl

Re: [Discuss-gnuradio] Feature #394

2012-02-08 Thread Andrew Davis
Thanks, I think i'll work on QA too while i'm at it then. On Wed, Feb 8, 2012 at 10:32 PM, Tom Rondeau wrote: > On Tue, Feb 7, 2012 at 9:52 PM, Andrew Davis wrote: > >> Hello all, >> >> I would like to help expand the C++ API, so I'm attempting to work on >> Feature #394 or "Re-implement hierarc

Re: [Discuss-gnuradio] Feature #394

2012-02-08 Thread Tom Rondeau
On Tue, Feb 7, 2012 at 9:52 PM, Andrew Davis wrote: > Hello all, > > I would like to help expand the C++ API, so I'm attempting to work on > Feature #394 or "Re-implement hierarchical blocks currently living in > blks2 in C++ and put into gnuradio-core/src/lib/hier." I've started on > am_demod.py

[Discuss-gnuradio] Feature #394

2012-02-07 Thread Andrew Davis
Hello all, I would like to help expand the C++ API, so I'm attempting to work on Feature #394 or "Re-implement hierarchical blocks currently living in blks2 in C++ and put into gnuradio-core/src/lib/hier." I've started on am_demod.py but this requires optfir, which is also in python, I think this