Package Details: ffdecsawrapper-git 4.xx-1

Package Base: ffdecsawrapper-git
Description: FFdecsa empowered softcam
Upstream URL: https://github.com/bas-t/ffdecsawrapper.git
Category: multimedia
Licenses: GPLv3
Conflicts: ffdecsawrapper, sasc-ng
Provides: ffdecsawrapper
Submitter: p-we
Maintainer: None
Last Packager: p-we
Votes: 3
First Submitted: 2013-09-01 14:01
Last Updated: 2015-05-14 12:22

Dependencies (5)

Sources

Latest Comments

Comment by p-we

2015-05-27 01:01

Hi Everyone,
Since I moved a year ago to New Zealand I have much less time to keep my AUR packages maintained and keep my system tweaked. Arch Linux is just too bleeding edge to make a comfortable low maintenance multimedia server platform and I now need a server which will continue to run for years in a very boring reliable way without much input from me. Also the frequent surprises that happen when Arch updates to something new are not as fun as they should be. I recently made the switch to CentOS7 on my main server which is running FFdecsawrapper and will stay on a 3.10 kernel probably for the next 8 years.

This is the time for me to bow out as I can not longer test this package. So this package needs a new owner. I will miss the learning fun that ArchLinux has given me. But I'll keep a little fun as my remote frontends will still run Arch.

Comment by p-we

2015-05-15 12:02

For linux-lts users, ffdecsawrapper-git-lts is being brought back because there are subtle differences in the script with 4.xx kernels and 3.xx which linux-lts uses for now.

https://aur.archlinux.org/packages/ffdecsawrapper-git-lts/

Comment by p-we

2015-05-14 12:27

Thanks for the warning. Updated
I use the TBS version of FFdecsawrapper so although I do try to anticipate, I don't detect package problems.

Comment by p-we

2015-03-31 08:46

Didn't catch the last comments until now.
Package updated

Comment by bas-t

2015-03-13 17:55

I've got several complaints about the use of exported usercopy.
This may or may not be related to Ubuntu, all of the complaining people are running Ubuntu/Mythbuntu.
Bottomline: they could not get it to work properly.

So yesterday I decided that the importance of using the exported usercopy does not superseed the importance of quite a large group of FFdecsawrapper users getting a working setup.

Bottomline: I reverted changes related to exported usercopy, you don't have to copy the Module.symvers file manualy, FFdecsawrapper will automagically pick the right one. As it always did. In your case: just use the right './configure --dvb_dir=/path' parameter.

Comment by John-K

2015-03-13 17:04

thanks, I've downloaded the drivers from the manufacturers website, only need that one. Modified their dvbdev.c (/usr/src/dddvb-0.9.16/dvb_core/dvbdev.c) in a manner similar to the normal patch, the dvb_usercopy is already exported in the driver's dvbdev.c version.

I compile (as an external module) and install. (It loads the drivers and gives me 4 adapters) A Module.symvers is created in /usr/src/dddvb-0.9.16/. It contains the exported dvb_usercopy. I tried to modify and use your configure script to use the new directories, ffdecsawrapper and dvbloopback compile fine, but a modprobe dvbloopback gives me the famous "Unknown symbol dvb_usercopy"

I had to upgrade to kernel >3.17 (3.19) to make the driver compile properly.
However I don't think thats the problem, I have the feeling I'm not completely understanding your configure script. From where to where should this new Module.symvers be copied, and how do I make sure the patched dvbdev.c is used. I am using an Ubuntu "out-of-the-box kernel, without linux media drivers...

Comment by bas-t

2015-03-11 19:27

@John-K
it's not just media_experimental, upstream v4l media_tree has massive changes to the dvb-core, resulting in kernel crashes (soft lockups) when loading dvbloopback module. These changes are not yet in linux-4.0-RC series, nor in linux-next.
So you can still compile a kernel that works with current dvbloopback module.
You'll have to patch such a kernel to include the drivers you need if they are not in there yet. And that is, imo, not so hard to do.

So the dvbloopback module needs some (or a lot of) work.
Obviously I'm not the one that's going to do that, but I guess that eventually somone else will take over.

Please don't call Ziggo:-)

Comment by John-K

2015-03-11 18:45

Thanks for your efforts Bas! It's been a pleasure to work with ffdecsawrapper since you took over sasc-ng. I'm about to call Ziggo and ask them to reconsider their decision to transmit plain channels :-) since I'm stuck with CanalD.
Was just building a new system using kernel 3.16.0-23, but using the latest media-experimental (for Dig. Devices) drivers in combination with the latest ffdecsa my loopback device throws dvblb_fake_ioctl errors (when I try to use it) and can't be used. I'm not patching anymore, it seems the dvbdev.c already has the patch.

Thanks anyway for your work, and I hope someone has a good heart and will give this orphan a home.

Comment by p-we

2015-03-05 09:27

PKGBUILD is changed as per bas-t's comments below. Also tsbuffer is 32 standard nowadays so no need to declare it in configure. The package builds and should be OK. However since I use TBS DVB tuners, I cannot test this to be sure.

Comment by bas-t

2015-03-03 22:52

@p-we:
Since the new dvb-core patch exports the dvb-usercopy symbol, it makes no sense to keep the duped usercopy code in FFdecsawrapper. In 'master' branch I removed it (conditionaly, depending on linux version beeing < 3.13). I've been testing this change enough to merge it into 'stable' branch.

However, there is a minor complication involved. You'll have to see to it that the Module.symvers file that is generated by patching dvb-core.ko is copied to the dvbloopback/module directory in FFdecsawrapper before the dvbloopback module gets compiled. So not the Module.symvers file that the configure script would normaly copy into the dvbloopback/module dir. I've done that for Debian/Ubuntu, but I'm not comfortable enough with arch to do it for you guys as well.

Mind you, you don't have to change anything in you packages that are building out-of-kernel drivers, those would import a changed Module.symvers file anyway.

This is just a heads up, I know you are quite busy. So I'll wait a couple of weeks before merging into stable.

If I can do anything (like changing the code) to make this easy for you, let me know.

All comments