From Ingo.Wolf at gmx.de  Tue Aug 13 13:48:34 2019
From: Ingo.Wolf at gmx.de (Ingo.Wolf at gmx.de)
Date: Tue, 13 Aug 2019 15:48:34 +0200
Subject: sdr# version rtlsdr
Message-ID: <trinity-6172169e-f764-4f84-91c8-3182fee21863-1565704114411@msvc-mesg-gmx022>

An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/osmocom-sdr/attachments/20190813/f600cc24/attachment.htm>

From laforge at gnumonks.org  Tue Aug 13 20:15:49 2019
From: laforge at gnumonks.org (Harald Welte)
Date: Tue, 13 Aug 2019 22:15:49 +0200
Subject: sdr# version rtlsdr
In-Reply-To: <trinity-6172169e-f764-4f84-91c8-3182fee21863-1565704114411@msvc-mesg-gmx022>
References: <trinity-6172169e-f764-4f84-91c8-3182fee21863-1565704114411@msvc-mesg-gmx022>
Message-ID: <20190813201549.GJ9715@nataraja>

Hi Ingo,

On Tue, Aug 13, 2019 at 03:48:34PM +0200, Ingo.Wolf at gmx.de wrote:
> http://osmocom.org/attachments/download/2242/RelWithDebInfo.zip
>  
> is this the last version with rtlsdr.dll?

no, the latest windows binary builds are the weekly automatic builds 
available from http://ftp.osmocom.org/binaries/windows/rtl-sdr/

Pleaes note that in Osmocom almost nobody is working with/on Windows, so we
have no actual idea whtether the builds above work or not.
-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)


From Ingo.Wolf at gmx.de  Tue Aug 13 20:22:38 2019
From: Ingo.Wolf at gmx.de (Ingo.Wolf at gmx.de)
Date: Tue, 13 Aug 2019 22:22:38 +0200
Subject: AW: Re: sdr# version rtlsdr
Message-ID: <trinity-5b686b83-a42f-4738-9ec0-bd9c303c8462-1565727758720@msvc-mesg-gmx122>

An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/osmocom-sdr/attachments/20190813/44e5c3a1/attachment.htm>

From mueller at kit.edu  Wed Aug 14 05:51:53 2019
From: mueller at kit.edu (=?utf-8?B?TcO8bGxlciwgTWFyY3VzIChDRUwp?=)
Date: Wed, 14 Aug 2019 05:51:53 +0000
Subject: AW: Re: sdr# version rtlsdr
In-Reply-To: <trinity-5b686b83-a42f-4738-9ec0-bd9c303c8462-1565727758720@msvc-mesg-gmx122>
References: <trinity-5b686b83-a42f-4738-9ec0-bd9c303c8462-1565727758720@msvc-mesg-gmx122>
Message-ID: <70d7683045e884a396108a6bcf3da8f1cd3d5247.camel@kit.edu>

Hi Ingo, 

that's almost certainly a question for the SDR# developers, not the
osmocom mailing list: they very likely compiled that lib themselves. 

Also, that's just naming. You can name library files however you like.

Also, even if it had the same name, it wouldn't guarantee any
compatibility: When linking against a shared library (a DLL in windows
parlance), you need a compatible ABI, and you only achieve that by
using

* the same version of source code
* a compatible compiler
* the same compilation/linking settings

So, I'm almost certain that no matter what you're trying to achieve,
you're auf dem Holzweg with this one.

Best regards,
Marcus

On Tue, 2019-08-13 at 22:22 +0200, Ingo.Wolf at gmx.de wrote:
> In the actual rtl-sdr windows builds there is an librtlsdr.dll,
> while sdr# seems to need an rtlsdr.dll like in the quoted link.
>  
> When was rtlsdr.dll changed to librtlsdr.dll ?
>  
> -----Urspr?ngliche Nachricht-----
> Von: "Harald Welte" <laforge at gnumonks.org>
> Gesendet: Dienstag, 13. August 2019 22:15
> An: Ingo.Wolf at gmx.de
> Cc: osmocom-sdr at lists.osmocom.org
> Betreff: Re: sdr# version rtlsdr
> Hi Ingo,
> 
> On Tue, Aug 13, 2019 at 03:48:34PM +0200, Ingo.Wolf at gmx.de wrote:
> > http://osmocom.org/attachments/download/2242/RelWithDebInfo.zip
> > 
> > is this the last version with rtlsdr.dll?
> 
> no, the latest windows binary builds are the weekly automatic builds 
> available from http://ftp.osmocom.org/binaries/windows/rtl-sdr/
> 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6582 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/osmocom-sdr/attachments/20190814/dae675a4/attachment.bin>

From ingo.wolf at gmx.de  Wed Aug 14 18:28:19 2019
From: ingo.wolf at gmx.de (Ingo Wolf)
Date: Wed, 14 Aug 2019 20:28:19 +0200
Subject: sdr# version rtlsdr
In-Reply-To: <70d7683045e884a396108a6bcf3da8f1cd3d5247.camel@kit.edu>
References: <trinity-5b686b83-a42f-4738-9ec0-bd9c303c8462-1565727758720@msvc-mesg-gmx122>
 <70d7683045e884a396108a6bcf3da8f1cd3d5247.camel@kit.edu>
Message-ID: <54fa79fc-9b76-a974-0872-fc2eb7686076@gmx.de>

sdr# package doesn't contain rtlsdr.dll,

but some script to download it from:

http://osmocom.org/attachments/download/2242/RelWithDebInfo.zip

from your site, may be some licensing issue, not for getting some
current one.

Am 14.08.2019 um 07:51 schrieb M?ller, Marcus (CEL):
> Hi Ingo,
>
> that's almost certainly a question for the SDR# developers, not the
> osmocom mailing list: they very likely compiled that lib themselves.
>
> Also, that's just naming. You can name library files however you like.
>
> Also, even if it had the same name, it wouldn't guarantee any
> compatibility: When linking against a shared library (a DLL in windows
> parlance), you need a compatible ABI, and you only achieve that by
> using
>
> * the same version of source code
> * a compatible compiler
> * the same compilation/linking settings
>
> So, I'm almost certain that no matter what you're trying to achieve,
> you're auf dem Holzweg with this one.
>
> Best regards,
> Marcus
>
> On Tue, 2019-08-13 at 22:22 +0200, Ingo.Wolf at gmx.de wrote:
>> In the actual rtl-sdr windows builds there is an librtlsdr.dll,
>> while sdr# seems to need an rtlsdr.dll like in the quoted link.
>>
>> When was rtlsdr.dll changed to librtlsdr.dll ?
>>
>> -----Urspr?ngliche Nachricht-----
>> Von: "Harald Welte" <laforge at gnumonks.org>
>> Gesendet: Dienstag, 13. August 2019 22:15
>> An: Ingo.Wolf at gmx.de
>> Cc: osmocom-sdr at lists.osmocom.org
>> Betreff: Re: sdr# version rtlsdr
>> Hi Ingo,
>>
>> On Tue, Aug 13, 2019 at 03:48:34PM +0200, Ingo.Wolf at gmx.de wrote:
>>> http://osmocom.org/attachments/download/2242/RelWithDebInfo.zip
>>>
>>> is this the last version with rtlsdr.dll?
>> no, the latest windows binary builds are the weekly automatic builds
>> available from http://ftp.osmocom.org/binaries/windows/rtl-sdr/
>>
>>


From laforge at gnumonks.org  Thu Aug 15 08:42:10 2019
From: laforge at gnumonks.org (Harald Welte)
Date: Thu, 15 Aug 2019 10:42:10 +0200
Subject: sdr# version rtlsdr
In-Reply-To: <54fa79fc-9b76-a974-0872-fc2eb7686076@gmx.de>
References: <trinity-5b686b83-a42f-4738-9ec0-bd9c303c8462-1565727758720@msvc-mesg-gmx122>
 <70d7683045e884a396108a6bcf3da8f1cd3d5247.camel@kit.edu>
 <54fa79fc-9b76-a974-0872-fc2eb7686076@gmx.de>
Message-ID: <20190815084210.GI3979@nataraja>

Hi Ingo,

On Wed, Aug 14, 2019 at 08:28:19PM +0200, Ingo Wolf wrote:
> sdr# package doesn't contain rtlsdr.dll,
> 
> but some script to download it from:
> 
> http://osmocom.org/attachments/download/2242/RelWithDebInfo.zip
> 
> from your site, may be some licensing issue, not for getting some
> current one.

Then SDR# is insisting to use a snapshot from 2014 rather than something
that's remotely current.  As indicated, there are automatic current builds
made available.  I suggest you suggest to the SDR# developers to port their
software / scripts / whatever to use recent versions rather than 5 year old
ones.

There's little we can do about it.  We just develop and publish the library,
primarily in source code form, but also as binary packages for a variety of
systems.  Which versions people decide to use is entirely up to them.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)


From hudspero at oregonstate.edu  Thu Aug 15 15:50:38 2019
From: hudspero at oregonstate.edu (Hudspeth, Robert Lee)
Date: Thu, 15 Aug 2019 08:50:38 -0700
Subject: Coding Support
Message-ID: <CANjkrr=Jpc3232_gMF1e-F_0Ujr6YN1UvvZd2nsFsVLD8WSLTg@mail.gmail.com>

Hello! I am an undergraduate student at Oregon State University working
with RTL-SDR dongles for an academic project under supervision from
Benjamin Brewster, and I had a dev question.

I'm trying to run utilities that capture 978
<https://github.com/mutability/dump978> & 1090Mhz
<https://github.com/mutability/dump1090> traffic simultaneously, but I
can't seem to stop rtl_sdr from allocating too many zero-copy buffers and
preventing both programs from running simultaneously (I'd like to cut down
from 15). I've been through librtlsdr.c and rtl_adsb.c with the hope of
manually changing some variable that will let me accomplish this to no
avail.

Is there some line I might have overlooked, or some additional parameter(s)
I might need to enter?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/osmocom-sdr/attachments/20190815/5fece905/attachment.htm>

From Ingo.Wolf at gmx.de  Thu Aug 15 17:51:20 2019
From: Ingo.Wolf at gmx.de (Ingo Wolf)
Date: Thu, 15 Aug 2019 19:51:20 +0200
Subject: Aw: Coding Support
Message-ID: <trinity-20a1d64a-e30d-4e0e-9587-0a49cd6e8c32-1565891480268@msvc-mesg-gmx021>

An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/osmocom-sdr/attachments/20190815/8c40d1c0/attachment.htm>

From hudspero at oregonstate.edu  Thu Aug 15 17:59:32 2019
From: hudspero at oregonstate.edu (Hudspeth, Robert Lee)
Date: Thu, 15 Aug 2019 10:59:32 -0700
Subject: Coding Support
In-Reply-To: <CALL-=e56BuYEumcbZBZRXUjRvc5s+hjYnNv4FqFwEBZ0U3T9Ug@mail.gmail.com>
References: <CANjkrr=Jpc3232_gMF1e-F_0Ujr6YN1UvvZd2nsFsVLD8WSLTg@mail.gmail.com>
 <CALL-=e56BuYEumcbZBZRXUjRvc5s+hjYnNv4FqFwEBZ0U3T9Ug@mail.gmail.com>
Message-ID: <CANjkrr=Sj8zWwAvVxEF6+2qzR+ggRiVYxHS84P-HO-jjA9Qw2A@mail.gmail.com>

Thank you for your email, and I appreciate the communication. I did have
one last question: If I were to make a change to the code and need to
recompile it, are the steps the same ones listed on the wiki under
"building the software", or is there a different make process?

On Thu, Aug 15, 2019, 10:51 AM Karl <gmkarl at gmail.com> wrote:

> Hi Robert,
>
> It sounds like you're looking for the `buf_num` argument to
> rtlsdr_read_async.  This is in rtl-sdr.h:
> https://git.osmocom.org/rtl-sdr/tree/include/rtl-sdr.h#n362 .
>
> I run into problems like that all the time, myself.  Due to my issues,
> I've found it hard to collaborate on this project myself.  See mailing
> list archive of contributions that were minimally addressed.  I try to
> focus around communication that's more reliable than radio now, like
> memo.cash .
>
> But I'm still passionate about helping rtl-sdr grow.
>
> Karl
>
> On 8/15/19, Hudspeth, Robert Lee <hudspero at oregonstate.edu> wrote:
> > Hello! I am an undergraduate student at Oregon State University working
> > with RTL-SDR dongles for an academic project under supervision from
> > Benjamin Brewster, and I had a dev question.
> >
> > I'm trying to run utilities that capture 978
> > <https://github.com/mutability/dump978> & 1090Mhz
> > <https://github.com/mutability/dump1090> traffic simultaneously, but I
> > can't seem to stop rtl_sdr from allocating too many zero-copy buffers and
> > preventing both programs from running simultaneously (I'd like to cut
> down
> > from 15). I've been through librtlsdr.c and rtl_adsb.c with the hope of
> > manually changing some variable that will let me accomplish this to no
> > avail.
> >
> > Is there some line I might have overlooked, or some additional
> parameter(s)
> > I might need to enter?
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/osmocom-sdr/attachments/20190815/738e3034/attachment.htm>

From steve at steve-m.de  Thu Aug 15 20:08:30 2019
From: steve at steve-m.de (Steve Markgraf)
Date: Thu, 15 Aug 2019 22:08:30 +0200
Subject: Coding Support
In-Reply-To: <CANjkrr=Jpc3232_gMF1e-F_0Ujr6YN1UvvZd2nsFsVLD8WSLTg@mail.gmail.com>
References: <CANjkrr=Jpc3232_gMF1e-F_0Ujr6YN1UvvZd2nsFsVLD8WSLTg@mail.gmail.com>
Message-ID: <542475ea-6ba2-087d-47b0-627db3841724@steve-m.de>

Hi Robert,

On 15.08.19 17:50, Hudspeth, Robert Lee wrote:
> I'm trying to run utilities that capture?978
> <https://github.com/mutability/dump978>?&?1090Mhz
> <https://github.com/mutability/dump1090>?traffic simultaneously, but I
> can't seem to stop rtl_sdr from allocating too many zero-copy buffers
> and preventing both programs from running simultaneously (I'd like to
> cut down from 15). I've been through librtlsdr.c and rtl_adsb.c with the
> hope of manually changing some variable that will let me accomplish this
> to no avail.?

Just increase the usbfs memory limit, the default is only 16MB.
Either write the new size, or completely disable the limit with:

echo 0 > /sys/module/usbcore/parameters/usbfs_memory_mb

Regards,
Steve


From hudspero at oregonstate.edu  Fri Aug 16 16:17:45 2019
From: hudspero at oregonstate.edu (Hudspeth, Robert Lee)
Date: Fri, 16 Aug 2019 09:17:45 -0700
Subject: Coding Support
In-Reply-To: <542475ea-6ba2-087d-47b0-627db3841724@steve-m.de>
References: <CANjkrr=Jpc3232_gMF1e-F_0Ujr6YN1UvvZd2nsFsVLD8WSLTg@mail.gmail.com>
 <542475ea-6ba2-087d-47b0-627db3841724@steve-m.de>
Message-ID: <CANjkrrnsmsVoLXVrBKhAdGukDs-B_XMTDWA+VgYuj47FKiC4-g@mail.gmail.com>

Hello, Steve. I tried the fix you suggested the other day, but I still end
up with the same error as before.

I thought it'd help if I show what exactly I'm seeing in my console output
when I try to run both dump978 & dump1090 at the same time.

*Robert L. Hudspeth*


On Thu, Aug 15, 2019 at 1:15 PM Steve Markgraf <steve at steve-m.de> wrote:

> Hi Robert,
>
> On 15.08.19 17:50, Hudspeth, Robert Lee wrote:
> > I'm trying to run utilities that capture 978
> > <https://github.com/mutability/dump978> & 1090Mhz
> > <https://github.com/mutability/dump1090> traffic simultaneously, but I
> > can't seem to stop rtl_sdr from allocating too many zero-copy buffers
> > and preventing both programs from running simultaneously (I'd like to
> > cut down from 15). I've been through librtlsdr.c and rtl_adsb.c with the
> > hope of manually changing some variable that will let me accomplish this
> > to no avail.
>
> Just increase the usbfs memory limit, the default is only 16MB.
> Either write the new size, or completely disable the limit with:
>
> echo 0 > /sys/module/usbcore/parameters/usbfs_memory_mb
>
> Regards,
> Steve
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/osmocom-sdr/attachments/20190816/fa32cb47/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2019-08-16-091344_1600x900_scrot.png
Type: image/png
Size: 163002 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/osmocom-sdr/attachments/20190816/fa32cb47/attachment.png>

From oliver.jowett at gmail.com  Fri Aug 16 17:45:47 2019
From: oliver.jowett at gmail.com (Oliver Jowett)
Date: Sat, 17 Aug 2019 01:45:47 +0800
Subject: Coding Support
In-Reply-To: <CANjkrrnsmsVoLXVrBKhAdGukDs-B_XMTDWA+VgYuj47FKiC4-g@mail.gmail.com>
References: <CANjkrr=Jpc3232_gMF1e-F_0Ujr6YN1UvvZd2nsFsVLD8WSLTg@mail.gmail.com>
 <542475ea-6ba2-087d-47b0-627db3841724@steve-m.de>
 <CANjkrrnsmsVoLXVrBKhAdGukDs-B_XMTDWA+VgYuj47FKiC4-g@mail.gmail.com>
Message-ID: <CAAjXfu96x1P-_UoZQsbrdtmmNDb7Zt-OFhVC+cbiHyzrScvi2g@mail.gmail.com>

dump1090 is not expecting samples on stdin, it uses librtlsdr directly; now
you have two things competing for the same dongle. It's got nothing to do
with the zero-copy stuff.

Oliver


On Sat, 17 Aug 2019 at 00:19, Hudspeth, Robert Lee <hudspero at oregonstate.edu>
wrote:

> Hello, Steve. I tried the fix you suggested the other day, but I still end
> up with the same error as before.
>
> I thought it'd help if I show what exactly I'm seeing in my console output
> when I try to run both dump978 & dump1090 at the same time.
>
> *Robert L. Hudspeth*
>
>
> On Thu, Aug 15, 2019 at 1:15 PM Steve Markgraf <steve at steve-m.de> wrote:
>
>> Hi Robert,
>>
>> On 15.08.19 17:50, Hudspeth, Robert Lee wrote:
>> > I'm trying to run utilities that capture 978
>> > <https://github.com/mutability/dump978> & 1090Mhz
>> > <https://github.com/mutability/dump1090> traffic simultaneously, but I
>> > can't seem to stop rtl_sdr from allocating too many zero-copy buffers
>> > and preventing both programs from running simultaneously (I'd like to
>> > cut down from 15). I've been through librtlsdr.c and rtl_adsb.c with the
>> > hope of manually changing some variable that will let me accomplish this
>> > to no avail.
>>
>> Just increase the usbfs memory limit, the default is only 16MB.
>> Either write the new size, or completely disable the limit with:
>>
>> echo 0 > /sys/module/usbcore/parameters/usbfs_memory_mb
>>
>> Regards,
>> Steve
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/osmocom-sdr/attachments/20190817/95528555/attachment.htm>

From Ingo.Wolf at gmx.de  Sat Aug 24 10:14:09 2019
From: Ingo.Wolf at gmx.de (Ingo.Wolf at gmx.de)
Date: Sat, 24 Aug 2019 12:14:09 +0200
Subject: DVB-T2
Message-ID: <trinity-73900d0a-876e-4bab-af04-fad36fdd80f6-1566641649847@msvc-mesg-gmx024>

An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/osmocom-sdr/attachments/20190824/8aa946af/attachment.htm>

From steve at steve-m.de  Sat Aug 24 16:19:30 2019
From: steve at steve-m.de (Steve Markgraf)
Date: Sat, 24 Aug 2019 18:19:30 +0200
Subject: DVB-T2
In-Reply-To: <trinity-73900d0a-876e-4bab-af04-fad36fdd80f6-1566641649847@msvc-mesg-gmx024>
References: <trinity-73900d0a-876e-4bab-af04-fad36fdd80f6-1566641649847@msvc-mesg-gmx024>
Message-ID: <03167e57-4887-caa3-6fe8-5733bd385da3@steve-m.de>

Hi,

On 24.08.19 12:14, Ingo.Wolf at gmx.de wrote:
> can somebody confirm RTL-chip is not DVB-T2 capable not having 10MHz
> bandwidth needed?

The RTL2832U does not support DVB-T2 as it lacks the required
demodulater hardware. On the RTL2832P, an external demodulator can be
attached via a parallel MPEG TS interface. This is used by dongles
manufactured by Astrometa, which attach a Panasonic MN88472 DVB-T2
demodulator, see [1].

Regards,
Steve

[1] https://steve-m.de/pictures/rtl-sdr/rtl2832p_dvbt2/



From Ingo.Wolf at gmx.de  Sun Aug 25 03:02:57 2019
From: Ingo.Wolf at gmx.de (Ingo.Wolf at gmx.de)
Date: Sun, 25 Aug 2019 05:02:57 +0200
Subject: AW: Re: DVB-T2
Message-ID: <trinity-f9169f10-3b29-4119-89b1-594e7bd825ad-1566702177351@msvc-mesg-gmx122>

An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/osmocom-sdr/attachments/20190825/9060578a/attachment.htm>

From Ingo.Wolf at gmx.de  Sun Aug 25 03:21:34 2019
From: Ingo.Wolf at gmx.de (Ingo.Wolf at gmx.de)
Date: Sun, 25 Aug 2019 05:21:34 +0200
Subject: DVB-T2 RTL2832U SDR
Message-ID: <trinity-ce74d090-eedb-4bcf-b9d3-6cecf8b3af77-1566703294512@msvc-mesg-gmx121>

An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/osmocom-sdr/attachments/20190825/29681407/attachment.htm>

From mueller at kit.edu  Mon Aug 26 12:11:46 2019
From: mueller at kit.edu (=?utf-8?B?TcO8bGxlciwgTWFyY3VzIChDRUwp?=)
Date: Mon, 26 Aug 2019 12:11:46 +0000
Subject: AW: Re: DVB-T2
In-Reply-To: <trinity-f9169f10-3b29-4119-89b1-594e7bd825ad-1566702177351@msvc-mesg-gmx122>
References: <trinity-f9169f10-3b29-4119-89b1-594e7bd825ad-1566702177351@msvc-mesg-gmx122>
Message-ID: <ed816649df498402c4016abfd4eba026f38f0e96.camel@kit.edu>

No.

The fact that you can use your RTL dongle as SDR device is because one
can *bypass* most of the digital logic (demodulator, decoder, stream
extractor?) and just get a raw IQ stream.
Decoding DVB-T in software is a really CPU-intense problem, due to
high-rate (in both senses of the word) channel coding, complex
synchronization, and high-order constellations used.

Best regards,
Marcus

On Sun, 2019-08-25 at 05:02 +0200, Ingo.Wolf at gmx.de wrote:
> But isn't SDR demodulation in software?
>  
> -----Urspr?ngliche Nachricht-----
> Von: "Steve Markgraf" <steve at steve-m.de>
> Gesendet: Samstag, 24. August 2019 18:19
> An: osmocom-sdr at lists.osmocom.org; Ingo.Wolf at gmx.de
> Betreff: Re: DVB-T2
> Hi,
> 
> On 24.08.19 12:14, Ingo.Wolf at gmx.de wrote:
> > can somebody confirm RTL-chip is not DVB-T2 capable not having 10MHz
> > bandwidth needed?
> 
> The RTL2832U does not support DVB-T2 as it lacks the required
> demodulater hardware. On the RTL2832P, an external demodulator can be
> attached via a parallel MPEG TS interface. This is used by dongles
> manufactured by Astrometa, which attach a Panasonic MN88472 DVB-T2
> demodulator, see [1].
> 
> Regards,
> Steve
> 
> [1] https://steve-m.de/pictures/rtl-sdr/rtl2832p_dvbt2/
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6582 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/osmocom-sdr/attachments/20190826/9ddd9381/attachment.bin>

From Ingo.Wolf at gmx.de  Mon Aug 26 12:35:21 2019
From: Ingo.Wolf at gmx.de (Ingo.Wolf at gmx.de)
Date: Mon, 26 Aug 2019 14:35:21 +0200
Subject: AW: Re: AW: Re: DVB-T2
Message-ID: <trinity-7025ca64-3db8-40eb-b8b7-07d56c03b6c9-1566822921012@msvc-mesg-gmx122>

An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/osmocom-sdr/attachments/20190826/1ce7b14e/attachment.htm>

From mueller at kit.edu  Mon Aug 26 13:05:28 2019
From: mueller at kit.edu (=?utf-8?B?TcO8bGxlciwgTWFyY3VzIChDRUwp?=)
Date: Mon, 26 Aug 2019 13:05:28 +0000
Subject: AW: Re: AW: Re: DVB-T2
In-Reply-To: <trinity-7025ca64-3db8-40eb-b8b7-07d56c03b6c9-1566822921012@msvc-mesg-gmx122>
References: <trinity-7025ca64-3db8-40eb-b8b7-07d56c03b6c9-1566822921012@msvc-mesg-gmx122>
Message-ID: <17aa2d442387822a4f68b90fcc1b672c9299530f.camel@kit.edu>

Hi Ingo,
On Mon, 2019-08-26 at 14:35 +0200, Ingo.Wolf at gmx.de wrote:
> But if you bypass demodulator, don't you have to demodulate in software then?

Indeed. That's why you don't bypass the DVB-T demodulator if you want
to use your TV dongle as TV dongle.

> How can you just say "NO" isn't that nonsense?

Because it's not nonsense.

> Can the RTL2832U capture the 10MHz Bandwidth?

No.

> Wasn't it something like 3MB/s max on the RTL, does that mean 3MHz with 8 Bit Samples?

That's what it can transport in raw IQ sample across USB.
That has nothing to do with what the integrated DVB receiver /
demodulator can deal with. The contained MPEG data stream is much less
in bits per second than the raw samples.

>  
> Wether CPU can handle is another topic, but GHz Multicore + GPU don't look like completely impossible.

It's not completely impossible, just very hard. I'm not aware of any
DVB-T2 software decoder that would work on laptop-grade hardware. You
seem to be fond of stating a few unfounded assumptions here:

I'd recommend looking into gr-dtv, which is software decoders for DVB-
** standards, and look how far in rate you can push them with purely
recorded or simulated signals. I think you don't realize how complex
the problem of concatenated LDPC and BCH decoders is. The LDPC block
for DVB-T2 is 64800 bits long, and that means that channel decoding
means you have to find solutions x to

xH=y

where H is a 64800?(64800/2, /3, /4, /8) matrix, and y is the received
softbits vector of length 64800, multiple hundred times a second. Good
luck doing that in software without spending a lot of time optimizing
the architecture of your solver (that solver is called a LDPC decoder).
Suddenly, your fast CPU isn't fast enough for real-time decoding ? by
orders of magnitude, not by a factor of 2 or 5 or so.

Best regards,
Marcus

>  
> -----Urspr?ngliche Nachricht-----
> Von: "M?ller, Marcus (CEL)" <mueller at kit.edu>
> Gesendet: Montag, 26. August 2019 14:11
> An: "Ingo.Wolf at gmx.de" <ingo.wolf at gmx.de>
> Cc: "osmocom-sdr at lists.osmocom.org" <osmocom-sdr at lists.osmocom.org>
> Betreff: Re: AW: Re: DVB-T2
> </osmocom-sdr at lists.osmocom.org></ingo.wolf at gmx.de>
> No.
> 
> The fact that you can use your RTL dongle as SDR device is because one
> can *bypass* most of the digital logic (demodulator, decoder, stream
> extractor?) and just get a raw IQ stream.
> Decoding DVB-T in software is a really CPU-intense problem, due to
> high-rate (in both senses of the word) channel coding, complex
> synchronization, and high-order constellations used.
> 
> Best regards,
> Marcus
> 
> On Sun, 2019-08-25 at 05:02 +0200, Ingo.Wolf at gmx.de wrote:
> > But isn't SDR demodulation in software?
> > 
> > -----Urspr?ngliche Nachricht-----
> > Von: "Steve Markgraf" <steve at steve-m.de>
> > Gesendet: Samstag, 24. August 2019 18:19
> > An: osmocom-sdr at lists.osmocom.org; Ingo.Wolf at gmx.de
> > Betreff: Re: DVB-T2
> > Hi,
> > 
> > On 24.08.19 12:14, Ingo.Wolf at gmx.de wrote:
> > > can somebody confirm RTL-chip is not DVB-T2 capable not having 10MHz
> > > bandwidth needed?
> > 
> > The RTL2832U does not support DVB-T2 as it lacks the required
> > demodulater hardware. On the RTL2832P, an external demodulator can be
> > attached via a parallel MPEG TS interface. This is used by dongles
> > manufactured by Astrometa, which attach a Panasonic MN88472 DVB-T2
> > demodulator, see [1].
> > 
> > Regards,
> > Steve
> > 
> > [1] https://steve-m.de/pictures/rtl-sdr/rtl2832p_dvbt2/
> >
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6582 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/osmocom-sdr/attachments/20190826/2e0624e7/attachment.bin>

From ingo.wolf at gmx.de  Mon Aug 26 13:44:45 2019
From: ingo.wolf at gmx.de (Ingo Wolf)
Date: Mon, 26 Aug 2019 15:44:45 +0200
Subject: DVB-T2
In-Reply-To: <17aa2d442387822a4f68b90fcc1b672c9299530f.camel@kit.edu>
References: <trinity-7025ca64-3db8-40eb-b8b7-07d56c03b6c9-1566822921012@msvc-mesg-gmx122>
 <17aa2d442387822a4f68b90fcc1b672c9299530f.camel@kit.edu>
Message-ID: <ce4158a6-77ec-ca79-1de5-4cd68c84bb94@gmx.de>

I still think "NO" is a wrong answer to isn't SDR demodulation in software.

Will have a look at the other details.



From mueller at kit.edu  Tue Aug 27 13:33:11 2019
From: mueller at kit.edu (=?utf-8?B?TcO8bGxlciwgTWFyY3VzIChDRUwp?=)
Date: Tue, 27 Aug 2019 13:33:11 +0000
Subject: DVB-T2
In-Reply-To: <ce4158a6-77ec-ca79-1de5-4cd68c84bb94@gmx.de>
References: <trinity-7025ca64-3db8-40eb-b8b7-07d56c03b6c9-1566822921012@msvc-mesg-gmx122>
 <17aa2d442387822a4f68b90fcc1b672c9299530f.camel@kit.edu>
 <ce4158a6-77ec-ca79-1de5-4cd68c84bb94@gmx.de>
Message-ID: <b20c07784d0d3ac02f01a3399136507a5aecc1c2.camel@kit.edu>

Again: SDR demodulation is, as the name implies, done in software.
But that wasn't the question here, as far as I thought: DVB-T reception
with these DVB-T dongles is done in dedicated hardware on the dongle
itself, and is not an SDR implementation.

Best regards,
Marcus

On Mon, 2019-08-26 at 15:44 +0200, Ingo Wolf wrote:
> I still think "NO" is a wrong answer to isn't SDR demodulation in software.
> 
> Will have a look at the other details.
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6582 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/osmocom-sdr/attachments/20190827/147ebca5/attachment.bin>