Re: [Discuss-gnuradio] Basic beginner flowgraph with C++ API

Here's an example. https://github.com/csdvb/dvbs2_tx Ron On 01/24/2018 08:16 AM, Álvaro Cebrián Juan wrote: Hello everyone, I have no prior knowledge with GNU Radio. I would like to learn how to implement a very basic flowgraph using the C++ API. I have already checked the GNU Radio C++

Re: [Discuss-gnuradio] Lost samples from RTL2832 dongle

John, I can't speak to VirtualBox, but I use vmware and have never had problems with RTLSDR dropping samples; I've also used LimeSDR at higher bandwidths just fine, with a 4 year old machine. Choppy audio is generally due to default ALSA settings. Check this out:

Re: [Discuss-gnuradio] Basic beginner flowgraph with C++ API

Hello Álvaro, welcome to the GNU Radio community! I think we could probably help you better why you want to do this in C++ - most of us, including (and very much so) the long-time users and core developers use Python to build their flow graphs, because it's easier and has no performance downside.

[Discuss-gnuradio] Basic beginner flowgraph with C++ API

Hello everyone, I have no prior knowledge with GNU Radio. I would like to learn how to implement a very basic flowgraph using the C++ API. I have already checked the GNU Radio C++ guided tutorial from the wiki, but I find

Re: [Discuss-gnuradio] Audio Sink for pi

I had to force reload alsa on a linux box once. You could try that, too. On Jan 24, 2018 8:32 AM, "Müller, Marcus (CEL)" wrote: > Hello David, > > No experience with audio on the pi, but: > I usually just work with "default" on Linux. > You can query the possible strings using

Re: [Discuss-gnuradio] gnuradio-companion -c is documented but not working

Hello Markus, yep, that's a documentation bug. I'll look up how the manpages are generated. Possibly, GRC *used* to have this feature (or it *will* have that feature). What you want to achieve can be achieved with a different command line utility: grcc [-d target_directory,

[Discuss-gnuradio] gnuradio-companion -c is documented but not working

Hello, I noticed that the manpage for gnuradio-companion on my ubuntu 17.10 system contains the following section: -c, --compile Only compile the GRC file without invoking the GUI. Useful for unit testing, running gnuradio-companion from a Makefile and

Re: [Discuss-gnuradio] Audio Sink for pi

Hello David, No experience with audio on the pi, but: I usually just work with "default" on Linux. You can query the possible strings using "aplay -L", if you have aplay (ALSA player) installed; not sure hw:1,0 actually maps to something that can be used for playback. You could check that

Re: [Discuss-gnuradio] Is there a way to know whether more input data will become available?

Thanks, that worked. :) Am 17.01.2018 um 23:20 schrieb Sakthivel Velumani: > Hi Markus, > > A better way is to specify the amount of data you need for the > processing in the forecast function. By doing so, the GNU Radio > scheduler will guarantee the sufficient amount of input data and hence >

Re: [Discuss-gnuradio] Are hierarchical blocks with a variable number of inputs possible?

Thanks for the hint. However I managed to get the block running with the 2nd method of specifying the number of inputs as a parameter to the constructor. I don't need to change the number of inputs after block creation. So it was easier that way. Am 23.01.2018 um 21:57 schrieb Michael Dickens: >