search

bas-t / ffdecsawrapper

FFdecsa empowered softcam for MythTV
GNU General Public License v3.0
17 stars 9 forks source link

ffdecsawrapper starts thread on wrong frontend HVR-4000 #43

Closed ricjo97 closed 8 years ago

ricjo97 commented 8 years ago

I have a Hauppauge HVR-4000 dvb card and it has a DVB-T and a DVB-S receiver. it shows up as /dev/dvb/adaptor0/ with two frontends 0 and 1. My problem is that ffdecsawrapper shows in the end of the log file that it start threads at frontend1 and this is the DVB-T receiver, I would like it to be joined with frontend0 instead. Is it possible to choose what frontend ffdecsawrapper is joining with? Or is it something that I have overlooked?

bas-t commented 8 years ago

Hi, FFdecsawrapper always has a thread at frontend1. This is the userspace part of the dvbloopback driver. So when you have only one adapter, it shows as /dev/dvb/adapter0 Now, when you load the dvbloopback driver correct, you'll end up with an extra adapter: /dev/dvb/adapter1, that has 2 frontends, frontend0 (kernel space part of the dvbloopback driver) and frontend1 (userspace counterpart of the dvbloopback driver). And of course audio0/1 demux0/1 and so on. So in your case the FFdecsawrapper log should have something like:

Aug 3 14:19:52.934 frontend: Starting thread on /dev/dvb/adapter1/frontend1

Note that it does NOT start a thread on /dev/dvb/adapter0/frontend1

From what I understand, your goal is to use only DVB-S. Most straightforward way to go (imo) is to just disable the DVB-T part of the driver permanently. Well, that's what I would do. But maybe there are other ways to force your card in either DVB-S or DVB-T mode. I'm not familiar with your card, so I don't know.

This is of course a DVB driver issue, not FFdecsawrapper/dvbloopback related in any way.

Cheers, Tycho.

Op 03-08-15 om 07:56 schreef ricjo97:

I have a Hauppauge HVR-4000 dvb card and it has a DVB-T and a DVB-S receiver. it shows up as /dev/dvb/adaptor0/ with two frontends 0 and

  1. My problem is that ffdecsawrapper shows in the end of the log file that it start threads at frontend1 and this is the DVB-T receiver, I would like it to be joined with frontend0 instead. Is it possible to choose what frontend ffdecsawrapper is joining with?

No. it is always frontend1 but it should be frontend1 from the dvbloopback driver. Not frontend1 of the original driver.

Or is it something that I have overlooked?

— Reply to this email directly or view it on GitHub https://github.com/bas-t/ffdecsawrapper/issues/43.

bas-t commented 8 years ago

BTW: If you feel that I totally misunderstood your ticket, feel free to post a reply, or open a new ticket.

ricjo97 commented 8 years ago

The HVR-4000 card that I have is adapter0 and when I start ffdecsawrapper I get an new adapter with the name adapter1, as you mentioned. The configuration file for ffdecsawrapper is only on the adapter level and not on the frontend level. Here is the list information from adapter0 (my real adapter): mythtv@server:/dev/dvb/adapter0$ ls -l totalt 0 crw-rw---- 1 root video 212, 1 aug 3 07:11 demux0 crw-rw---- 1 root video 212, 5 aug 3 07:11 demux1 crw-rw---- 1 root video 212, 2 aug 3 07:11 dvr0 crw-rw---- 1 root video 212, 6 aug 3 07:11 dvr1 crw-rw---- 1 root video 212, 0 aug 3 07:11 frontend0 crw-rw---- 1 root video 212, 4 aug 3 07:11 frontend1 crw-rw---- 1 root video 212, 3 aug 3 07:11 net0 crw-rw---- 1 root video 212, 7 aug 3 07:11 net1 The listings from the dvbloopback adapter1 is the same with some extra (audio, osd, video). To join the real and virtual adapter I use "join 0:1" but the virtual adapter grabs frontend1 (DVB-T) in stead of frontend0 (DVB-S). Is there some way to tell ffdecsawrapper which frontend to grab? I hope this made the problem more clear.

bas-t commented 8 years ago

Op 03-08-15 om 20:55 schreef ricjo97:

The HVR-4000 card that I have is adapter0 and when I start ffdecsawrapper I get an new adapter with the name adapter1, as you mentioned. The configuration file for ffdecsawrapper is only on the adapter level and not on the frontend level. Here is the list information from adapter0 (my real adapter): mythtv@server:/dev/dvb/adapter0$ ls -l totalt 0 crw-rw---- 1 root video 212, 1 aug 3 07:11 demux0 crw-rw---- 1 root video 212, 5 aug 3 07:11 demux1 crw-rw---- 1 root video 212, 2 aug 3 07:11 dvr0 crw-rw---- 1 root video 212, 6 aug 3 07:11 dvr1 crw-rw---- 1 root video 212, 0 aug 3 07:11 frontend0 crw-rw---- 1 root video 212, 4 aug 3 07:11 frontend1 crw-rw---- 1 root video 212, 3 aug 3 07:11 net0 crw-rw---- 1 root video 212, 7 aug 3 07:11 net1 The listings from the dvbloopback adapter1 is the same with some extra (audio, osd, video). To join the real and virtual adapter I use "join 0:1" but the virtual adapter grabs frontend1 (DVB-T) in stead of frontend0 (DVB-S). Is there some way to tell ffdecsawrapper which frontend to grab?

AFAIK: no. So that leaves you with the option to disable the DVB-T frontend.(should not be difficult)

I hope this made the problem more clear.

Yes, it does.

— Reply to this email directly or view it on GitHub https://github.com/bas-t/ffdecsawrapper/issues/43#issuecomment-127369732.

ricjo97 commented 8 years ago

Thank you, for your answer. I'll try to disable DVB-T frontend. Best regards Rickard