I spent several hours yesterday trying to get this going.
However there are so many patches around that whilst I was able to get it to compile and run I was unable to get it into the state I wanted with plugins etc. I think Goga77 has posted something somewhere but I couldn't find it and in any case things seem to be a bit out of control with patches flying all over the place.
Sorry I can't help but at least you know you're not the only one.
Mike
Hi
I couldn't run properly vdr 171 + s2api + extension patch + s2api patch + h.264patch that's why I keep vdr 170 + s2api patch + h.264patch
Goga
I spent several hours yesterday trying to get this going.
However there are so many patches around that whilst I was able to get it to compile and run I was unable to get it into the state I wanted with plugins etc. I think Goga77 has posted something somewhere but I couldn't find it and in any case things seem to be a bit out of control with patches flying all over the place.
Sorry I can't help but at least you know you're not the only one.
Goga777 goga777@bk.ru writes:
Hi
I couldn't run properly vdr 171 + s2api + extension patch + s2api patch + h.264patch that's why I keep vdr 170 + s2api patch + h.264patch
There's a git repository for vdr at http://git.gekrumbel.de/?p=vdr.git Wouldn't it be appropriate to use it to maintain a working vdr+s2+h264 source tree ?
what do you reckon ?
Hello
Am Donnerstag, 20. November 2008 schrieb syrius.ml@no-log.org:
Goga777 goga777@bk.ru writes:
Hi
I couldn't run properly vdr 171 + s2api + extension patch + s2api patch + h.264patch that's why I keep vdr 170 + s2api patch + h.264patch
There's a git repository for vdr at http://git.gekrumbel.de/?p=vdr.git Wouldn't it be appropriate to use it to maintain a working vdr+s2+h264 source tree ?
I'm maintaining that aforementioned git repository. I didn't want to host different versions of VDR in this git repository (except the 'original sources' git).
This repository is intended to be used as a source for cloning own git repositories and pulling upcoming development changes provided by Klaus Schmidinger. If you clone it to a public git hoster (or publish it on some own server) and add the various patches (s2api, h.264 etc.), it will be easy for others to retrieve already patched versions of VDR to their local computers.
If I get informed of such a repository I will be happy to add a link on my VDR git hosting site, to inform others about the patched VDR git existence.
Look at git homepage http://git.or.cz/ for a list of public git hosting providers.
Kind regards Dieter
Dieter Hametner dh+vdr@gekrumbel.de writes:
Hi,
I couldn't run properly vdr 171 + s2api + extension patch + s2api patch + h.264patch that's why I keep vdr 170 + s2api patch + h.264patch
There's a git repository for vdr at http://git.gekrumbel.de/?p=vdr.git Wouldn't it be appropriate to use it to maintain a working vdr+s2+h264 source tree ?
I'm maintaining that aforementioned git repository. I didn't want to host different versions of VDR in this git repository (except the 'original sources' git).
Ok, sorry I should have asked you first. BTW is it used by a lot of people ?
This repository is intended to be used as a source for cloning own git repositories and pulling upcoming development changes provided by Klaus Schmidinger. If you clone it to a public git hoster (or publish it on some own server) and add the various patches (s2api, h.264 etc.), it will be easy for others to retrieve already patched versions of VDR to their local computers.
If I get informed of such a repository I will be happy to add a link on my VDR git hosting site, to inform others about the patched VDR git existence.
Look at git homepage http://git.or.cz/ for a list of public git hosting providers.
ok. I'm not a h264 or s2api user yet, it would be very nice if some people could maintain such a repository. It's seem messy to get these patches working and questions about them are very recurrent.
If anyone does offer a prepatched tree, PLEASE DON'T use that enormous "ext" patch! I'd rather if someone just kept a patch archive with an explanation of what each patch does. However, hopefully we won't need to use patches for s2api and h264 for much longer.
Hello
Am Freitag, 21. November 2008 schrieb syrius.ml@no-log.org:
There's a git repository for vdr at http://git.gekrumbel.de/?p=vdr.git Wouldn't it be appropriate to use it to maintain a working vdr+s2+h264 source tree ?
I'm maintaining that aforementioned git repository. I didn't want to host different versions of VDR in this git repository (except the 'original sources' git).
Ok, sorry I should have asked you first.
I did setup this git as a kind of seed. It contains the development history (in terms of the official releases) of VDR since its beginning. I have the hope that the community picks it up and creates something usefull out of it.
BTW is it used by a lot of people ?
Unfortunately I don't think so. Nobody ever informed me about that he cloned it, added some patches and published them somewhere else. I know only of some experiments Tobias Grimm did with it.
Look at git homepage http://git.or.cz/ for a list of public git hosting providers.
ok. I'm not a h264 or s2api user yet, it would be very nice if some people could maintain such a repository. It's seem messy to get these patches working and questions about them are very recurrent.
I'm no h264 and s2api user either. But helping to reduce this kind of mess was one of my motivations to setup the VDR git.
Regards Dieter
-
Dieter Hametner -
Goga777 -
Mike Booth -
syrius.ml＠no-log.org -
VDR User