discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] how to implement synchronous source block correct


From: Marcus Müller
Subject: Re: [Discuss-gnuradio] how to implement synchronous source block correctly ?
Date: Thu, 05 Dec 2013 11:17:15 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Btw, this restriction frustrating. Someone would like to make
> useful
graph
> containing both audio source and sink in single chain, but it's
impossible
> due to current GNU Radio design.
As I told you before: That's plainly not true.
There are a lot of flowgraphs that have both hardware sources and sinks.
Why your's not working is a mystery to me, because, seriously, audio
sample rates should pose no problem for a moderately capable PC,
unless you do something complicated.

> I think it would be better to implement such scheduler which do 
> synchronization itself (using software generator or some external
> source provided by user).

The scheduler is a *scheduler*, it schedules the calling of the work
functions. I don't think you realize the implications of designing a
per-sample real-time signal processing framework. It basically
eradicates the possibility of having variable computational costs in
each block.
And, by the way, I think you over-estimate the real-time abilities of
modern operating systems on modern PC hardware. If you want to have a
guaranteed "sample clock" in GNU Radio, you would need HUGE amounts of
spare computational power. That'd be a waste.
GNU Radio works on *blocks* of samples. This implies latency, and
makes it impractical to say "ok, that single sample always comes every
x µs", but it gives you the advantage of a buffer, so that you can
have actual hardware interaction with your SDR.

Having a hardware defined sample rate basically does exactly what you
want.
And: If you're looking for an innovative GNU Radio scheduler, look
into GRAS (GNU Radio advanced scheduler), it has a different model of
block interaction, but of course /can't/ take the route of
time-synchronous per-sample processing. That's just anti-SDR, to be
honest.

Greetings,
Marcus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSoFKrAAoJEAFxB7BbsDrL0KgH/RDZztwlNgpbwgk5ggrH+ZJB
7ROXUtAxr7mMoiIXwDe6cMPXJ9uN7ykZImCFYBQguadFzPbRaa5aPg1ALbF7eRoi
6odFqi4t3bUTpD0a1KO2KTfCEF7HeLnsQ9CkspxLw1BakOf0Pnw+1+HtIpu2PRpw
OKloxGJcH5RUcQpDp99QCYFX1OYpJ8gTE4EOmY+lWFXK2MQxwtce4CiDcV7Ue1YQ
eHycxGjwayYN9hWZWrSN169EbJ2QcBQT4VsR32xmADHBqvYK6eb0u/Zheh5HPmNj
HOZSmbWGgkNNTjgMR9+TDYnJgqAXG2w1ar4rHp6PHgb5n1kyhW5WKyylMV4psKg=
=XpsW
-----END PGP SIGNATURE-----



reply via email to

[Prev in Thread] Current Thread [Next in Thread]