Closed Drazgor closed 10 years ago
Nothing is wrong with FFdecsawrapper, you don't need to change anything in it. But you have to recompile your kernel with CONFIG_DVB_MAX_ADAPTERS=24 One way of doing it is described here:
https://github.com/bas-t/tbs-intree/wiki/HOW-TO--%28Debian-Wheezy,-backports-kernel%29
You can omit adding the TBS drivers to the build system
Oh, forgot to mention: "make -C debian/build/build_amd64_none_amd64 menuconfig " is ment to change the amount of adapters.
If you use v4l (based) drivers, make sure you compile them with CONFIG_DVB_MAX_ADAPTERS=24 too.
I'm sure that FFdecsawrapper will run fine after this.
I did a quick check. Probably solved your issue in commit e298840fed5f417bb51f67fe1ab34ef07543fa66
Hm, still not done. I'll investigate when I have more time.
I did find the initial DVBLB_MAX_ADAPTERS setting, maybe you could use that in the rest of you code as well to make scaling to more adapters possible as well. I can confirm that the commits did resolve the issue, thanks for the quick reply.
I've set it to the max (32 adapters) 64, as you suggested is, wrong. Using 32 loopback devices means you use 32 real adapters as well. Together they add up to the maximum of 64.
As documented it is not possible to use more than 8 adapter without modifying your drivers. I did this since I want to use 12 cards. I set the maximum of cards in the driver to 64 cards. All cards are detected so that part works. The problem is now that I would like to use a loopback on every card, hower the default maximum for the loopback is set at 8. Changing this in the module will allow for more loopbacks to be present. The total number of adapter recognized by the kernel is now indeed 24.
The problem is that when ffdecsawrapper is started using multiple joins between card and loopback the process will stop with the error "Could not connect to loopback device 20"
Using less than 9 joins will run fine and will also descramble the streams so it looks like somewhere there is some check somewhere for the max number of adapter.
Could you tell me what might be wrong?
Kind regards,
Simon Wamelink
Logging info: