dvbcut-devel — DVBCUT development discussions

[DVBCUT-devel] Status of the project in 2015 ?

[Zdeněk T. <zd...@gm...>]

Hi all,

something new with development DVBCut ? Mainly with support HD streams ? I
know, that develop was officially stopped in 2012 but I found new activity
in 2013.

I think, that this great software has no alternative (for example: cut with
"Show difference to current picture")

I would like to support DVCut with some money.

Is there any coordinator of project or someone who has skills to revive
DVBCut ?

Z.

Re: [DVBCUT-devel] Qt4 port and further directions

[Olaf D. <ola...@ol...>]

Wolfgang Baron <Wol...@gm...> writes:

> Am 18.02.2014 14:40, schrieb Olaf Dietsche:
>> Reinhard Tartler <sir...@gm...> writes:
>>
>>> Hi Wolfgang.
>>>
>>> I wonder how is it going with dvbcut? Are you still working on it?
>>>
>>> In debian, we are currently trying to move to libav10, and dvbcut
>>> fails to compile against it:
>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739220
>>>
>>> Before spending too much time on dvbcut, I wonder if it made sense to
>>> keep dvbcut in Debian? We currently carry quite a number of patches:
>>> http://patch-tracker.debian.org/package/dvbcut/0.5.4+svn178-4 that
>>> really should go upstream.
>> There is a Qt4 port at https://github.com/nextghost/dvbcut-qt4, though I
>> don't know how mature this is.
>>
>> I just uploaded a quick hack to make dvbcut build with the current
>> ffmpeg 2.1.3, see https://github.com/olafdietsche/dvbcut/tree/ffmpeg-2.1.3.
>>
>> I don't know how far away libav10 is from ffmpeg. Maybe, this helps with
>> your effort to go to libav10.
> Maybe you can tell me, whether ffmpeg and libav10 are still the way to
> go for ultimate performance, or whether I have a better alternative for Qt?

I don't know, if ffmpeg or libav is superior regarding performance. For
me it doesn't really matter, because for removing commercials from a
video, either should be fast enough. I stick with ffmpeg, because I had
some problems with libav in the past, which were resolved by using the
then current ffmpeg version.

For the widget set, if you want to keep dvbcut cross-platform, you're
limited to just a few toolkits, Qt, Gtk, wxWidgets. The two big ones, Qt
and Gtk, are both valid choices, I think. So, in the end, it is largely
a matter of taste and which one you're most comfortable with.

>> Past attempts to reach Sven in order to take over dvbcut at Sourceforge,
>> haven't been successful, AFAIK. So, I would say, you must either
>> maintain your own repository or abandon dvbcut in Debian.
> I am suffering from the same fate. I have tried to contact him in every
> possible way on every possible channel, but he is just ignoring every
> communication attempt. Like I said earlier, my current idea is to create
> a new, similar project on bitbucket or sourceforge.

Well, that's the point of open source after all. You can maintain or
extend a project, even if the original author isn't around anymore. And
even if the author is still active, you can fork a project, as can be
seen with ffmpeg/libav.

So, since Sven isn't responding, you're free to move on. At least,
that's what I have done with my github repository.

Regards, Olaf

Re: [DVBCUT-devel] Qt4 port and further directions

[Reinhard T. <sir...@gm...>]

On Tue, Feb 18, 2014 at 8:08 PM, Wolfgang Baron <Wol...@gm...> wrote:

> Hi Reinhard,
>
> I have DVBCut running under Qt4 and Qt5, but like Olaf Dietsche points
> out, Sven Over, who is the only one, who can transfer the Sourceforge
> project to anyone else, does not react at all to any kind of
> communication attempt. I guess I will have to relaunch the whole program
> with a new name.
>
> At the moment, I am slowly making the code more Qt-ish and giving it a
> more usual GUI and the capability to mix several input files.

That's great to hear!

> I spent a lot of time thinking about what to do with the ffmpeg related
> code. The performance is nice, but the API has a playground stability.
> So I will probably copy some arbitrary version into my own project and
> update it from time to time, so that I will only have to keep code for
> one version of the ffmpeg API.

Well, if you believe that helps you making progress on this progress,
that's great. However, having source code copies is not really
acceptable for inclusion into a Linux distribution for obvious
reasons.

> I did not see much point in making fast progress, as most Linux
> distributions still ship Qt4 with the Qt3 compatibility module. Are you
> saying it cannot ship with debian anymore at all? If that is so, I will
> concentrate on producing a release (and hope for some help of a packager
> to make my project packager-friendly).

At the moment, I'm undecided what to with dvbcut. ATM, there are only
three open bugs in the package, and non of them are release-critical,
yet.

https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=dvbcut

>From these three, #739220: FTBFS with libav10, is problematic because
of two reasons: First, it is going to become RC as soon as the
transition starts, but OTOH, the amount of packages that break with
the new libav block starting the transition. I'm currently trying to
remove this number so that we can start the transition rather sooner
than later.

Ideally, I would like to update the package to a new release that
works with qt4/qt5 and a modern libavcodec. If that's not possible
anytime soon, then it may be better to remove dvbcut from debian for
now, and possibly reintroduce it or its successor at a later time.

As said, I'm currently rather undecided how to proceed from here, and
appreciate any input on this.



-- 
regards,
    Reinhard

Re: [DVBCUT-devel] Qt4 port and further directions

[James C. <qu...@la...>]

On Wed, Feb 19, 2014 at 02:08:22AM +0100, Wolfgang Baron wrote:
> I have DVBCut running under Qt4 and Qt5, but like Olaf Dietsche
> points out, Sven Over, who is the only one, who can transfer the
> Sourceforge project to anyone else, does not react at all to any
> kind of communication attempt.
> I guess I will have to relaunch the whole program with a new name.

Yes, that seems appropriate.

http://sourceforge.net/p/forge/documentation/Abandoned%20Projects/
provides only forking as a method to resolve an uncontactable project
administrator.

(It is pointless to speculate why a project owner has become
uncontactable; there can be many reasons; but I don't have any
evidence that communication is being ignored, only that there is no
response.)

-- 
James Cameron
http://quozl.linux.org.au/

Re: [DVBCUT-devel] Qt4 port and further directions

[Wolfgang B. <Wol...@gm...>]

Am 18.02.2014 14:40, schrieb Olaf Dietsche:
> Reinhard Tartler <sir...@gm...> writes:
>
>> On Sun, Apr 21, 2013 at 5:51 PM, Wolfgang Baron <Wol...@gm...> wrote:
>>> On 04/20/2013 08:04 AM, Reinhard Tartler wrote:
>>>> On Fri, Apr 19, 2013 at 1:59 AM, Wolfgang Baron <Wol...@gm...> wrote:
>>>>> Hi all,
>>>>>
>>>>> I started porting dvbcut from Qt3 to Qt4 on 2013-03-29, based on the
>>>>> most current svn sources late at night in my free time using mercurial
>>>>> for storing the history. My first aim was to port dvbcut to Qt4 and add
>>>>> multiple source videos.
>>>> Please let me in the role of one of the Debian/Ubuntu package
>>>> maintainers of the dvbcut package say you a big, big thank you for
>>>> working on that. Qt3 is really a showstopper for distribution
>>>> use-cases.
>>> Now I know what you must be going through. This was my first Qt3->Qt4
>>> port and I hope it will be my last :)
>>>> I also wanted to point you out to the patches that we apply in Debian
>>>> to the dvbcut package:
>>>>
>>>> http://patch-tracker.debian.org/package/dvbcut/0.5.4+svn178-3
>>>>
>>>> Maybe you find one or the other patch useful, espc. the gcc 4.7 and
>>>> Libav 9 patches.
>>>>
>>>> Please do not hesitate to write me an email if you have any questions.
>>>>
>>> Thank you for your helpful information. That was exactly what I was
>>> looking for. I will try to make this project as easy to package as
>>> possible and I will appreciate any help with accomplishing that. First
>>> of all, I will have to get the project up and running, and then I will
>>> definately contact you.
>>>
>>> Cheers,
>> Hi Wolfgang.
>>
>> I wonder how is it going with dvbcut? Are you still working on it?
>>
>> In debian, we are currently trying to move to libav10, and dvbcut
>> fails to compile against it:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739220
>>
>> Before spending too much time on dvbcut, I wonder if it made sense to
>> keep dvbcut in Debian? We currently carry quite a number of patches:
>> http://patch-tracker.debian.org/package/dvbcut/0.5.4+svn178-4 that
>> really should go upstream.
> There is a Qt4 port at https://github.com/nextghost/dvbcut-qt4, though I
> don't know how mature this is.
>
> I just uploaded a quick hack to make dvbcut build with the current
> ffmpeg 2.1.3, see https://github.com/olafdietsche/dvbcut/tree/ffmpeg-2.1.3.
>
> I don't know how far away libav10 is from ffmpeg. Maybe, this helps with
> your effort to go to libav10.
Maybe you can tell me, whether ffmpeg and libav10 are still the way to
go for ultimate performance, or whether I have a better alternative for Qt?
> Past attempts to reach Sven in order to take over dvbcut at Sourceforge,
> haven't been successful, AFAIK. So, I would say, you must either
> maintain your own repository or abandon dvbcut in Debian.
I am suffering from the same fate. I have tried to contact him in every
possible way on every possible channel, but he is just ignoring every
communication attempt. Like I said earlier, my current idea is to create
a new, similar project on bitbucket or sourceforge.

Cheers,

Wolfgang Baron

Re: [DVBCUT-devel] Qt4 port and further directions

[Wolfgang B. <Wol...@gm...>]

Am 16.02.2014 21:54, schrieb Reinhard Tartler:
> On Sun, Apr 21, 2013 at 5:51 PM, Wolfgang Baron <Wol...@gm...> wrote:
>> On 04/20/2013 08:04 AM, Reinhard Tartler wrote:
>>> On Fri, Apr 19, 2013 at 1:59 AM, Wolfgang Baron <Wol...@gm...> wrote:
>>>> Hi all,
>>>>
>>>> I started porting dvbcut from Qt3 to Qt4 on 2013-03-29, based on the
>>>> most current svn sources late at night in my free time using mercurial
>>>> for storing the history. My first aim was to port dvbcut to Qt4 and add
>>>> multiple source videos.
>>> Please let me in the role of one of the Debian/Ubuntu package
>>> maintainers of the dvbcut package say you a big, big thank you for
>>> working on that. Qt3 is really a showstopper for distribution
>>> use-cases.
>> Now I know what you must be going through. This was my first Qt3->Qt4
>> port and I hope it will be my last :)
>>> I also wanted to point you out to the patches that we apply in Debian
>>> to the dvbcut package:
>>>
>>> http://patch-tracker.debian.org/package/dvbcut/0.5.4+svn178-3
>>>
>>> Maybe you find one or the other patch useful, espc. the gcc 4.7 and
>>> Libav 9 patches.
>>>
>>> Please do not hesitate to write me an email if you have any questions.
>>>
>> Thank you for your helpful information. That was exactly what I was
>> looking for. I will try to make this project as easy to package as
>> possible and I will appreciate any help with accomplishing that. First
>> of all, I will have to get the project up and running, and then I will
>> definately contact you.
>>
>> Cheers,
> Hi Wolfgang.
>
> I wonder how is it going with dvbcut? Are you still working on it?
>
> In debian, we are currently trying to move to libav10, and dvbcut
> fails to compile against it:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739220
>
> Before spending too much time on dvbcut, I wonder if it made sense to
> keep dvbcut in Debian? We currently carry quite a number of patches:
> http://patch-tracker.debian.org/package/dvbcut/0.5.4+svn178-4 that
> really should go upstream.
>
> Thanks for any input,
> Reinhard
Hi Reinhard,

I have DVBCut running under Qt4 and Qt5, but like Olaf Dietsche points
out, Sven Over, who is the only one, who can transfer the Sourceforge
project to anyone else, does not react at all to any kind of
communication attempt. I guess I will have to relaunch the whole program
with a new name.

At the moment, I am slowly making the code more Qt-ish and giving it a
more usual GUI and the capability to mix several input files.

I spent a lot of time thinking about what to do with the ffmpeg related
code. The performance is nice, but the API has a playground stability.
So I will probably copy some arbitrary version into my own project and
update it from time to time, so that I will only have to keep code for
one version of the ffmpeg API.

I did not see much point in making fast progress, as most Linux
distributions still ship Qt4 with the Qt3 compatibility module. Are you
saying it cannot ship with debian anymore at all? If that is so, I will
concentrate on producing a release (and hope for some help of a packager
to make my project packager-friendly).

Kind regards,

Wolfgang Baron

Re: [DVBCUT-devel] Qt4 port and further directions

[Olaf D. <ola...@ol...>]

Reinhard Tartler <sir...@gm...> writes:

> On Sun, Apr 21, 2013 at 5:51 PM, Wolfgang Baron <Wol...@gm...> wrote:
>> On 04/20/2013 08:04 AM, Reinhard Tartler wrote:
>>> On Fri, Apr 19, 2013 at 1:59 AM, Wolfgang Baron <Wol...@gm...> wrote:
>>>> Hi all,
>>>>
>>>> I started porting dvbcut from Qt3 to Qt4 on 2013-03-29, based on the
>>>> most current svn sources late at night in my free time using mercurial
>>>> for storing the history. My first aim was to port dvbcut to Qt4 and add
>>>> multiple source videos.
>>> Please let me in the role of one of the Debian/Ubuntu package
>>> maintainers of the dvbcut package say you a big, big thank you for
>>> working on that. Qt3 is really a showstopper for distribution
>>> use-cases.
>> Now I know what you must be going through. This was my first Qt3->Qt4
>> port and I hope it will be my last :)
>>> I also wanted to point you out to the patches that we apply in Debian
>>> to the dvbcut package:
>>>
>>> http://patch-tracker.debian.org/package/dvbcut/0.5.4+svn178-3
>>>
>>> Maybe you find one or the other patch useful, espc. the gcc 4.7 and
>>> Libav 9 patches.
>>>
>>> Please do not hesitate to write me an email if you have any questions.
>>>
>> Thank you for your helpful information. That was exactly what I was
>> looking for. I will try to make this project as easy to package as
>> possible and I will appreciate any help with accomplishing that. First
>> of all, I will have to get the project up and running, and then I will
>> definately contact you.
>>
>> Cheers,
>
> Hi Wolfgang.
>
> I wonder how is it going with dvbcut? Are you still working on it?
>
> In debian, we are currently trying to move to libav10, and dvbcut
> fails to compile against it:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739220
>
> Before spending too much time on dvbcut, I wonder if it made sense to
> keep dvbcut in Debian? We currently carry quite a number of patches:
> http://patch-tracker.debian.org/package/dvbcut/0.5.4+svn178-4 that
> really should go upstream.

There is a Qt4 port at https://github.com/nextghost/dvbcut-qt4, though I
don't know how mature this is.

I just uploaded a quick hack to make dvbcut build with the current
ffmpeg 2.1.3, see https://github.com/olafdietsche/dvbcut/tree/ffmpeg-2.1.3.

I don't know how far away libav10 is from ffmpeg. Maybe, this helps with
your effort to go to libav10.

Past attempts to reach Sven in order to take over dvbcut at Sourceforge,
haven't been successful, AFAIK. So, I would say, you must either
maintain your own repository or abandon dvbcut in Debian.

Regards, Olaf

Re: [DVBCUT-devel] Qt4 port and further directions

[Reinhard T. <sir...@gm...>]

On Sun, Apr 21, 2013 at 5:51 PM, Wolfgang Baron <Wol...@gm...> wrote:
> On 04/20/2013 08:04 AM, Reinhard Tartler wrote:
>> On Fri, Apr 19, 2013 at 1:59 AM, Wolfgang Baron <Wol...@gm...> wrote:
>>> Hi all,
>>>
>>> I started porting dvbcut from Qt3 to Qt4 on 2013-03-29, based on the
>>> most current svn sources late at night in my free time using mercurial
>>> for storing the history. My first aim was to port dvbcut to Qt4 and add
>>> multiple source videos.
>> Please let me in the role of one of the Debian/Ubuntu package
>> maintainers of the dvbcut package say you a big, big thank you for
>> working on that. Qt3 is really a showstopper for distribution
>> use-cases.
> Now I know what you must be going through. This was my first Qt3->Qt4
> port and I hope it will be my last :)
>> I also wanted to point you out to the patches that we apply in Debian
>> to the dvbcut package:
>>
>> http://patch-tracker.debian.org/package/dvbcut/0.5.4+svn178-3
>>
>> Maybe you find one or the other patch useful, espc. the gcc 4.7 and
>> Libav 9 patches.
>>
>> Please do not hesitate to write me an email if you have any questions.
>>
> Thank you for your helpful information. That was exactly what I was
> looking for. I will try to make this project as easy to package as
> possible and I will appreciate any help with accomplishing that. First
> of all, I will have to get the project up and running, and then I will
> definately contact you.
>
> Cheers,

Hi Wolfgang.

I wonder how is it going with dvbcut? Are you still working on it?

In debian, we are currently trying to move to libav10, and dvbcut
fails to compile against it:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739220

Before spending too much time on dvbcut, I wonder if it made sense to
keep dvbcut in Debian? We currently carry quite a number of patches:
http://patch-tracker.debian.org/package/dvbcut/0.5.4+svn178-4 that
really should go upstream.

Thanks for any input,
Reinhard



-- 
regards,
    Reinhard

Re: [DVBCUT-devel] Qt4 port and further directions

[Wolfgang B. <Wol...@gm...>]

On 04/20/2013 08:04 AM, Reinhard Tartler wrote:
> On Fri, Apr 19, 2013 at 1:59 AM, Wolfgang Baron <Wol...@gm...> wrote:
>> Hi all,
>>
>> I started porting dvbcut from Qt3 to Qt4 on 2013-03-29, based on the
>> most current svn sources late at night in my free time using mercurial
>> for storing the history. My first aim was to port dvbcut to Qt4 and add
>> multiple source videos.
> Please let me in the role of one of the Debian/Ubuntu package
> maintainers of the dvbcut package say you a big, big thank you for
> working on that. Qt3 is really a showstopper for distribution
> use-cases.
Now I know what you must be going through. This was my first Qt3->Qt4
port and I hope it will be my last :)
> I also wanted to point you out to the patches that we apply in Debian
> to the dvbcut package:
>
> http://patch-tracker.debian.org/package/dvbcut/0.5.4+svn178-3
>
> Maybe you find one or the other patch useful, espc. the gcc 4.7 and
> Libav 9 patches.
>
> Please do not hesitate to write me an email if you have any questions.
>
Thank you for your helpful information. That was exactly what I was
looking for. I will try to make this project as easy to package as
possible and I will appreciate any help with accomplishing that. First
of all, I will have to get the project up and running, and then I will
definately contact you.

Cheers,

Wolfgang

Re: [DVBCUT-devel] Qt4 port and further directions

[Wolfgang B. <Wol...@gm...>]

On 04/20/2013 11:50 AM, Francesco Fumanti wrote:
> Hi,
>
> ...
>
> If you could team up and create a software that could also handle HD with an interface and cutting procedure similar to that would really be awesome. Otherwise, it would be great to have at least dvbcut work on current distributions.
>
> In any case, thanks to everybody that worked and is working on dvbcut or a similar new solution for the linux desktop.
Stay tuned :)

Cheers,

Wolfgang

Re: [DVBCUT-devel] Qt4 port and further directions

[Wolfgang B. <Wol...@gm...>]

On 04/20/2013 03:12 AM, Michael Riepe wrote:
>
> On 04/20/13 01:17, Wolfgang Baron wrote:
>
>>>> I started porting dvbcut from Qt3 to Qt4 on 2013-03-29, based on the
>>>> most current svn sources late at night in my free time using mercurial
>>>> for storing the history. My first aim was to port dvbcut to Qt4 and add
>>>> multiple source videos.
>>> Nice to hear that some people still have free time. Not so nice to hear
>>> that you're wasting it. Well, in my opinion, anyway.
>> Please explain. Of the zillion programs I used for editing DVB
>> recordings, DVBCut is by far the most productive, because I do not have
>> to demultiplex and remultiplex the material, editing is extremely fast
>> and producing the output is a breze.
> Sure. I use dvbcut myself, you know. ;)
>
> But I'm also aware of the program's limitations. H.264 support, for
> example, requires that you rewrite virtually everything. The same goes
> for any other video format. So there is no HDTV, and probably never will be.
I already assessed, that in the long run, I may have to change virtually
everything, but hey, that's why software projects are so much fun, no?
The program does very well, what it does now and I am not afraid to move
my fingers to get in new features.
>> Why should I not give something
>> back, now that the functionality has become limited (Settings are not
>> saved (because Qt4 with q3compat does not do the job), the file dialogs
>> are stone aged and Qt3 and the versions of the used libraries will not
>> be here for much longer)? If there is some even better project I could
>> invest my time into, please tell me.
> I'm working on something, but I'm afraid my free time is more limited
> than yours. Gotta pay the bloody bills...
Well, I've got my own bills to pay :(, but I've spent too many years
just programming for money, so now I really want to start giving
something back, so I am open to where this project may lead in the end.
>
> [...]
>>>> The autoconf stuff and directories containing library code are not used.
>>>> I have
>>>> not yet created a new KDevelop4 project, because I do not have any
>>>> experience
>>>> with KDevelop. If anyone needs this, I will of course look into it. I would
>>>> also look into new autoconf support, if anyone can give a good reason for
>>>> doing so.
>>> Unlike others, an autoconf-based build environment will work on any
>>> system that has `make' and a decent shell. Is that reason good enough?
>> No. If you can compile a Qt program, you have qmake. The system
>> dependencies are handled by the Qt libraries. What does autoconf leave
>> me with except a bunch of overcomplicated #ifdefs?
> More freedom, and the option to check for system characteristics Qt
> doesn't really care about, for example. But let's not waste our precious
> time with that discussion.
Exactly. If anyone really needs it, I will definately support it.
>>>> I sent a mail to Sven Over some time ago, but he has not answered yet.
>>>> If you like to see, what I have done in the dvbcut project, can please
>>>> anybody reply to my and tell me how to proceed?
>>> Maybe the best course of action would be to take over maintenance of the
>>> package, if you're really willing and able to spend so much time on it.
>>> Unfortunately, I can't give you write access to the repository, since
>>> I'm not its owner. Only Sven can do that, and he's abandoned the project
>>> years ago.
>> I would be willing to do that. However, I have no experience with
>> Sourceforge administration etc. So if you are willing to boot me into
>> that business just a little bit, I would make this a useful and modern
>> project again.
> I'm not really a subversion expert either. I can check out, create a
> diff, check in, and that's about it. I'm using CVS a lot, but that's
> different.
>
> As far as sourceforge is concerned, I'm probably the last one you should
> ask for help. I don't use it for anything else.
No problem, we work as a team here and I have already been given helpful
hints.
>
> [second mail]
>> Oh yes, I forgot to ask. @Michael Riepe: Have you produced any code,
>> that might be integrated already?
> Nope. I've written about 800 KByte (~32000 lines) of code, but that's a
> separate project, not based on the dvbcut code. It will eventually serve
> the same purpose, but it does things in quite a different way, starting
> with the fact that the audio/video handling is completely independent
> from the GUI. In fact, there is no GUI at the moment. And before I start
> writing one, there are more important things to do, like getting the
> cutting logic right for video formats other than MPEG-2.
Well, that's great. If we cooperate a little, we will get our stuff
together in the long run. I know it's a lot of work, but as I said, I am
not afraid of that.

First, I will try to contact Sven using the help from Olaf Dietsche and
if Sven proves to be absolutely unreachable, I'll take over or fork.

Cheers,

Wolfgang

Re: [DVBCUT-devel] Qt4 port and further directions

[Wolfgang B. <Wol...@gm...>]

On 04/20/2013 01:48 PM, Olaf Dietsche wrote:
> There's the Abandoned Project Takeover (APT) page
> http://sourceforge.net/apps/trac/sourceforge/wiki/Abandoned%20Project%20Takeovers
> Creating a new project at sourceforge is pretty easy. On the homepage,
> there is a link to http://sourceforge.net/create/, where you can
> create and configure a new project. Although, you can also use github,
> gitourious, code.google.com or any other project hosting site. Take
> whatever you're comfortable with, and let us know of course ;-) 
>> ... 
> If he doesn't respond, you might have no other choice.
>
> If you're willing to spend the time, you can compare the pictures at 
>
> - http://sourceforge.net/users/svenor
> - https://twitter.com/spacedentist
> - https://github.com/spacedentist
>
> and see, if he is reachable through one of these channels.
Thank you very much for your helpful links. And of course I will let you
know!

Cheers,

Wolfgang

Re: [DVBCUT-devel] Qt4 port and further directions

[Olaf D. <ola...@ol...>]

Wolfgang Baron <Wol...@gm...> writes:

> On 04/19/2013 07:31 PM, Michael Riepe wrote:
>>
>> On 04/19/13 01:59, Wolfgang Baron wrote:
>>> I sent a mail to Sven Over some time ago, but he has not answered yet.
>>> If you like to see, what I have done in the dvbcut project, can please
>>> anybody reply to my and tell me how to proceed?
>> Maybe the best course of action would be to take over maintenance of the
>> package, if you're really willing and able to spend so much time on it.
>> Unfortunately, I can't give you write access to the repository, since
>> I'm not its owner. Only Sven can do that, and he's abandoned the project
>> years ago.
> I would be willing to do that. However, I have no experience with
> Sourceforge administration etc. So if you are willing to boot me into
> that business just a little bit, I would make this a useful and modern
> project again.

There's the Abandoned Project Takeover (APT) page 
http://sourceforge.net/apps/trac/sourceforge/wiki/Abandoned%20Project%20Takeovers

Creating a new project at sourceforge is pretty easy. On the homepage,
there is a link to http://sourceforge.net/create/, where you can create
and configure a new project.

Although, you can also use github, gitourious, code.google.com or any other project
hosting site. Take whatever you're comfortable with, and let us know of
course ;-)

>> On the other hand, you don't have to use the repository on sourceforge.
>> You don't have to use subversion either. You could set up a new git or
>> mercurial repository and work with that.
> Are you talking about a completely new, forked project with a new name
> etc. in case Sven will not answer at all? No problem. However, I would
> prefer to talk to Sven about that before doing so. Does anyone know how
> to reach him? The Address of the contact link on the
> dvbcut.sourceforge.net homepage does not seem be helpful.

If he doesn't respond, you might have no other choice.

If you're willing to spend the time, you can compare the pictures at 

- http://sourceforge.net/users/svenor
- https://twitter.com/spacedentist
- https://github.com/spacedentist

and see, if he is reachable through one of these channels.

Regards, Olaf

Re: [DVBCUT-devel] Qt4 port and further directions

[Francesco F. <fra...@gm...>]

Hi,

On 2013-04-20 03:12, Michael Riepe wrote:
>>>> I started porting dvbcut from Qt3 to Qt4 on 2013-03-29, based on the
>>>> most current svn sources late at night in my free time using mercurial
>>>> for storing the history. My first aim was to port dvbcut to Qt4 and add
>>>> multiple source videos.
>>> Nice to hear that some people still have free time. Not so nice to hear
>>> that you're wasting it. Well, in my opinion, anyway.
>> Please explain. Of the zillion programs I used for editing DVB
>> recordings, DVBCut is by far the most productive, because I do not have
>> to demultiplex and remultiplex the material, editing is extremely fast
>> and producing the output is a breze.

+1

> Sure. I use dvbcut myself, you know. ;)

I am still using it, too.

> But I'm also aware of the program's limitations. H.264 support, for
> example, requires that you rewrite virtually everything. The same goes
> for any other video format. So there is no HDTV, and probably never will be.
>
>> Why should I not give something
>> back, now that the functionality has become limited (Settings are not
>> saved (because Qt4 with q3compat does not do the job), the file dialogs
>> are stone aged and Qt3 and the versions of the used libraries will not
>> be here for much longer)? If there is some even better project I could
>> invest my time into, please tell me.
>
> I'm working on something, but I'm afraid my free time is more limited
> than yours. Gotta pay the bloody bills...
>
> [...]
>>>> The autoconf stuff and directories containing library code are not used.
>>>> I have
>>>> not yet created a new KDevelop4 project, because I do not have any
>>>> experience
>>>> with KDevelop. If anyone needs this, I will of course look into it. I would
>>>> also look into new autoconf support, if anyone can give a good reason for
>>>> doing so.
>>> Unlike others, an autoconf-based build environment will work on any
>>> system that has `make' and a decent shell. Is that reason good enough?
>> No. If you can compile a Qt program, you have qmake. The system
>> dependencies are handled by the Qt libraries. What does autoconf leave
>> me with except a bunch of overcomplicated #ifdefs?
>
> More freedom, and the option to check for system characteristics Qt
> doesn't really care about, for example. But let's not waste our precious
> time with that discussion.
>
>>>> I sent a mail to Sven Over some time ago, but he has not answered yet.
>>>> If you like to see, what I have done in the dvbcut project, can please
>>>> anybody reply to my and tell me how to proceed?
>>> Maybe the best course of action would be to take over maintenance of the
>>> package, if you're really willing and able to spend so much time on it.
>>> Unfortunately, I can't give you write access to the repository, since
>>> I'm not its owner. Only Sven can do that, and he's abandoned the project
>>> years ago.
>> I would be willing to do that. However, I have no experience with
>> Sourceforge administration etc. So if you are willing to boot me into
>> that business just a little bit, I would make this a useful and modern
>> project again.
>
> I'm not really a subversion expert either. I can check out, create a
> diff, check in, and that's about it. I'm using CVS a lot, but that's
> different.
>
> As far as sourceforge is concerned, I'm probably the last one you should
> ask for help. I don't use it for anything else.
>
> [second mail]
>> Oh yes, I forgot to ask. @Michael Riepe: Have you produced any code,
>> that might be integrated already?
>
> Nope. I've written about 800 KByte (~32000 lines) of code, but that's a
> separate project, not based on the dvbcut code. It will eventually serve
> the same purpose, but it does things in quite a different way, starting
> with the fact that the audio/video handling is completely independent
> from the GUI. In fact, there is no GUI at the moment. And before I start
> writing one, there are more important things to do, like getting the
> cutting logic right for video formats other than MPEG-2.

If you could team up and create a software that could also handle HD with an interface and cutting procedure similar to that would really be awesome. Otherwise, it would be great to have at least dvbcut work on current distributions.

In any case, thanks to everybody that worked and is working on dvbcut or a similar new solution for the linux desktop.

Cheers,

Francesco

Re: [DVBCUT-devel] Qt4 port and further directions

[Francesco F. <fra...@gm...>]

Hi,

I have not produced any code. I only repackaged some update versions in my PPA on Ubuntu to make it easily available to the public.

If I remember correctly, at some point I stopped with it because of missing dependencies.

Cheers,

Francesco

On 2013-04-20 01:32, Wolfgang Baron wrote:
> On 04/19/2013 04:53 PM, Francesco Fumanti wrote:
>> You might perhaps try to contact Michael Riepe. He has been the last
>> to maintain dvbcut and as far as I know, he has the intention to
>> create a new dvbcut version, that is also able to cut HD material.
>> Cheers, Francesco
> Oh yes, I forgot to ask. @Michael Riepe: Have you produced any code,
> that might be integrated already?
>
> Cheers,
>
> Wolfgang
>
>

Re: [DVBCUT-devel] Qt4 port and further directions

[Reinhard T. <sir...@gm...>]

On Fri, Apr 19, 2013 at 1:59 AM, Wolfgang Baron <Wol...@gm...> wrote:
> Hi all,
>
> I started porting dvbcut from Qt3 to Qt4 on 2013-03-29, based on the
> most current svn sources late at night in my free time using mercurial
> for storing the history. My first aim was to port dvbcut to Qt4 and add
> multiple source videos.

Please let me in the role of one of the Debian/Ubuntu package
maintainers of the dvbcut package say you a big, big thank you for
working on that. Qt3 is really a showstopper for distribution
use-cases.

I also wanted to point you out to the patches that we apply in Debian
to the dvbcut package:

http://patch-tracker.debian.org/package/dvbcut/0.5.4+svn178-3

Maybe you find one or the other patch useful, espc. the gcc 4.7 and
Libav 9 patches.

Please do not hesitate to write me an email if you have any questions.

Cheers,
Reinhard

-- 
regards,
    Reinhard

Re: [DVBCUT-devel] Qt4 port and further directions

[Michael R. <mi...@mr...>]

On 04/20/13 01:17, Wolfgang Baron wrote:

>>> I started porting dvbcut from Qt3 to Qt4 on 2013-03-29, based on the
>>> most current svn sources late at night in my free time using mercurial
>>> for storing the history. My first aim was to port dvbcut to Qt4 and add
>>> multiple source videos.
>> Nice to hear that some people still have free time. Not so nice to hear
>> that you're wasting it. Well, in my opinion, anyway.
> Please explain. Of the zillion programs I used for editing DVB
> recordings, DVBCut is by far the most productive, because I do not have
> to demultiplex and remultiplex the material, editing is extremely fast
> and producing the output is a breze.

Sure. I use dvbcut myself, you know. ;)

But I'm also aware of the program's limitations. H.264 support, for
example, requires that you rewrite virtually everything. The same goes
for any other video format. So there is no HDTV, and probably never will be.

> Why should I not give something
> back, now that the functionality has become limited (Settings are not
> saved (because Qt4 with q3compat does not do the job), the file dialogs
> are stone aged and Qt3 and the versions of the used libraries will not
> be here for much longer)? If there is some even better project I could
> invest my time into, please tell me.

I'm working on something, but I'm afraid my free time is more limited
than yours. Gotta pay the bloody bills...

[...]
>>> The autoconf stuff and directories containing library code are not used.
>>> I have
>>> not yet created a new KDevelop4 project, because I do not have any
>>> experience
>>> with KDevelop. If anyone needs this, I will of course look into it. I would
>>> also look into new autoconf support, if anyone can give a good reason for
>>> doing so.
>> Unlike others, an autoconf-based build environment will work on any
>> system that has `make' and a decent shell. Is that reason good enough?
> No. If you can compile a Qt program, you have qmake. The system
> dependencies are handled by the Qt libraries. What does autoconf leave
> me with except a bunch of overcomplicated #ifdefs?

More freedom, and the option to check for system characteristics Qt
doesn't really care about, for example. But let's not waste our precious
time with that discussion.

>>> I sent a mail to Sven Over some time ago, but he has not answered yet.
>>> If you like to see, what I have done in the dvbcut project, can please
>>> anybody reply to my and tell me how to proceed?
>> Maybe the best course of action would be to take over maintenance of the
>> package, if you're really willing and able to spend so much time on it.
>> Unfortunately, I can't give you write access to the repository, since
>> I'm not its owner. Only Sven can do that, and he's abandoned the project
>> years ago.
> I would be willing to do that. However, I have no experience with
> Sourceforge administration etc. So if you are willing to boot me into
> that business just a little bit, I would make this a useful and modern
> project again.

I'm not really a subversion expert either. I can check out, create a
diff, check in, and that's about it. I'm using CVS a lot, but that's
different.

As far as sourceforge is concerned, I'm probably the last one you should
ask for help. I don't use it for anything else.

[second mail]
> Oh yes, I forgot to ask. @Michael Riepe: Have you produced any code,
> that might be integrated already?

Nope. I've written about 800 KByte (~32000 lines) of code, but that's a
separate project, not based on the dvbcut code. It will eventually serve
the same purpose, but it does things in quite a different way, starting
with the fact that the audio/video handling is completely independent
from the GUI. In fact, there is no GUI at the moment. And before I start
writing one, there are more important things to do, like getting the
cutting logic right for video formats other than MPEG-2.

-- 
Michael "Tired" Riepe <mi...@mr...>
X-Tired: Each morning I get up I die a little

Re: [DVBCUT-devel] Qt4 port and further directions

[Wolfgang B. <Wol...@gm...>]

On 04/19/2013 04:53 PM, Francesco Fumanti wrote:
> You might perhaps try to contact Michael Riepe. He has been the last
> to maintain dvbcut and as far as I know, he has the intention to
> create a new dvbcut version, that is also able to cut HD material.
> Cheers, Francesco 
Oh yes, I forgot to ask. @Michael Riepe: Have you produced any code,
that might be integrated already?

Cheers,

Wolfgang

Re: [DVBCUT-devel] Qt4 port and further directions

[Wolfgang B. <Wol...@gm...>]

On 04/19/2013 07:31 PM, Michael Riepe wrote:
>
> On 04/19/13 01:59, Wolfgang Baron wrote:
>> Hi all,
>>
>> I started porting dvbcut from Qt3 to Qt4 on 2013-03-29, based on the
>> most current svn sources late at night in my free time using mercurial
>> for storing the history. My first aim was to port dvbcut to Qt4 and add
>> multiple source videos.
> Nice to hear that some people still have free time. Not so nice to hear
> that you're wasting it. Well, in my opinion, anyway.
Please explain. Of the zillion programs I used for editing DVB
recordings, DVBCut is by far the most productive, because I do not have
to demultiplex and remultiplex the material, editing is extremely fast
and producing the output is a breze. Why should I not give something
back, now that the functionality has become limited (Settings are not
saved (because Qt4 with q3compat does not do the job), the file dialogs
are stone aged and Qt3 and the versions of the used libraries will not
be here for much longer)? If there is some even better project I could
invest my time into, please tell me.

>> This is an overview of what I already did:
>> - apply qt3to4
>> - convert forms with uic3 -convert
>> - port issues not covered by qt3to4
>> - use current libavcodec, libavformat and libswscale from system packages
>> - remove the dependency of the q3support module
>>
>> Issues not covered by qt3to4 were:
>> - QImage::scale() -> QImage::scaled()
>> - implicit cast from std::string to QString
>> - implicit cast from QString to bool
>> - lots of changes in method names
>>
>> Things to consider using QtCreator:
>> - run setversion.sh to create version information
>>
>> The autoconf stuff and directories containing library code are not used.
>> I have
>> not yet created a new KDevelop4 project, because I do not have any
>> experience
>> with KDevelop. If anyone needs this, I will of course look into it. I would
>> also look into new autoconf support, if anyone can give a good reason for
>> doing so.
> Unlike others, an autoconf-based build environment will work on any
> system that has `make' and a decent shell. Is that reason good enough?
No. If you can compile a Qt program, you have qmake. The system
dependencies are handled by the Qt libraries. What does autoconf leave
me with except a bunch of overcomplicated #ifdefs? But don't get me
wrong. If anyone really needs it, I would maintain it, I just need a
real use case.
> You won't believe how much trouble I've already had with packages that
> use scons, cmake, or other evil^H^H^H^Hfancy stuff.
Oh, I know exactly what you mean. That's why I would reduce the number
of supported build systems as far as possible.
>> These will be my next steps:
>> - make sure it still runs on windows
>> - remove all deprecations and compiler warnings
>> - use models in all convenient places
>> - use QListViews instead of QListWidgets
>> - enable multiple input files
>> - provide translations
>> - find similar frames assistant
>> - etc.
>>
>> I sent a mail to Sven Over some time ago, but he has not answered yet.
>> If you like to see, what I have done in the dvbcut project, can please
>> anybody reply to my and tell me how to proceed?
> Maybe the best course of action would be to take over maintenance of the
> package, if you're really willing and able to spend so much time on it.
> Unfortunately, I can't give you write access to the repository, since
> I'm not its owner. Only Sven can do that, and he's abandoned the project
> years ago.
I would be willing to do that. However, I have no experience with
Sourceforge administration etc. So if you are willing to boot me into
that business just a little bit, I would make this a useful and modern
project again.
> On the other hand, you don't have to use the repository on sourceforge.
> You don't have to use subversion either. You could set up a new git or
> mercurial repository and work with that.
Are you talking about a completely new, forked project with a new name
etc. in case Sven will not answer at all? No problem. However, I would
prefer to talk to Sven about that before doing so. Does anyone know how
to reach him? The Address of the contact link on the
dvbcut.sourceforge.net homepage does not seem be helpful.

Cheers,

Wolfgang

Re: [DVBCUT-devel] Qt4 port and further directions

[Michael R. <mi...@mr...>]

On 04/19/13 01:59, Wolfgang Baron wrote:
> Hi all,
> 
> I started porting dvbcut from Qt3 to Qt4 on 2013-03-29, based on the
> most current svn sources late at night in my free time using mercurial
> for storing the history. My first aim was to port dvbcut to Qt4 and add
> multiple source videos.

Nice to hear that some people still have free time. Not so nice to hear
that you're wasting it. Well, in my opinion, anyway.

> This is an overview of what I already did:
> - apply qt3to4
> - convert forms with uic3 -convert
> - port issues not covered by qt3to4
> - use current libavcodec, libavformat and libswscale from system packages
> - remove the dependency of the q3support module
> 
> Issues not covered by qt3to4 were:
> - QImage::scale() -> QImage::scaled()
> - implicit cast from std::string to QString
> - implicit cast from QString to bool
> - lots of changes in method names
> 
> Things to consider using QtCreator:
> - run setversion.sh to create version information
> 
> The autoconf stuff and directories containing library code are not used.
> I have
> not yet created a new KDevelop4 project, because I do not have any
> experience
> with KDevelop. If anyone needs this, I will of course look into it. I would
> also look into new autoconf support, if anyone can give a good reason for
> doing so.

Unlike others, an autoconf-based build environment will work on any
system that has `make' and a decent shell. Is that reason good enough?

You won't believe how much trouble I've already had with packages that
use scons, cmake, or other evil^H^H^H^Hfancy stuff.

> These will be my next steps:
> - make sure it still runs on windows
> - remove all deprecations and compiler warnings
> - use models in all convenient places
> - use QListViews instead of QListWidgets
> - enable multiple input files
> - provide translations
> - find similar frames assistant
> - etc.
> 
> I sent a mail to Sven Over some time ago, but he has not answered yet.
> If you like to see, what I have done in the dvbcut project, can please
> anybody reply to my and tell me how to proceed?

Maybe the best course of action would be to take over maintenance of the
package, if you're really willing and able to spend so much time on it.
Unfortunately, I can't give you write access to the repository, since
I'm not its owner. Only Sven can do that, and he's abandoned the project
years ago.

On the other hand, you don't have to use the repository on sourceforge.
You don't have to use subversion either. You could set up a new git or
mercurial repository and work with that.

-- 
Michael "Tired" Riepe <mi...@mr...>
X-Tired: Each morning I get up I die a little

Re: [DVBCUT-devel] Qt4 port and further directions

[Francesco F. <fra...@gm...>]

On 2013-04-19 01:59, Wolfgang Baron wrote:
> Hi all,
>
> I started porting dvbcut from Qt3 to Qt4 on 2013-03-29, based on the
> most current svn sources late at night in my free time using mercurial
> for storing the history. My first aim was to port dvbcut to Qt4 and add
> multiple source videos.
>
> This is an overview of what I already did:
> - apply qt3to4
> - convert forms with uic3 -convert
> - port issues not covered by qt3to4
> - use current libavcodec, libavformat and libswscale from system packages
> - remove the dependency of the q3support module
>
> Issues not covered by qt3to4 were:
> - QImage::scale() -> QImage::scaled()
> - implicit cast from std::string to QString
> - implicit cast from QString to bool
> - lots of changes in method names
>
> Things to consider using QtCreator:
> - run setversion.sh to create version information
>
> The autoconf stuff and directories containing library code are not used.
> I have
> not yet created a new KDevelop4 project, because I do not have any
> experience
> with KDevelop. If anyone needs this, I will of course look into it. I would
> also look into new autoconf support, if anyone can give a good reason for
> doing so.
>
> These will be my next steps:
> - make sure it still runs on windows
> - remove all deprecations and compiler warnings
> - use models in all convenient places
> - use QListViews instead of QListWidgets
> - enable multiple input files
> - provide translations
> - find similar frames assistant
> - etc.
>
> I sent a mail to Sven Over some time ago, but he has not answered yet.

You might perhaps try to contact Michael Riepe. He has been the last to maintain dvbcut and as far as I know, he has the intention to create a new dvbcut version, that is also able to cut HD material.

Cheers,

Francesco

> If you like to see, what I have done in the dvbcut project, can please
> anybody reply to my and tell me how to proceed?
>
> Cheers,
>
> Wolfgang
>
>
> ------------------------------------------------------------------------------
> Precog is a next-generation analytics platform capable of advanced
> analytics on semi-structured data. The platform includes APIs for building
> apps and a phenomenal toolset for data science. Developers can use
> our toolset for easy data analysis & visualization. Get a free account!
> http://www2.precog.com/precogplatform/slashdotnewsletter
> _______________________________________________
> DVBCUT-devel mailing list
> DVB...@li...
> https://lists.sourceforge.net/lists/listinfo/dvbcut-devel
>

[DVBCUT-devel] Qt4 port and further directions

[Wolfgang B. <Wol...@gm...>]

Hi all,

I started porting dvbcut from Qt3 to Qt4 on 2013-03-29, based on the
most current svn sources late at night in my free time using mercurial
for storing the history. My first aim was to port dvbcut to Qt4 and add
multiple source videos.

This is an overview of what I already did:
- apply qt3to4
- convert forms with uic3 -convert
- port issues not covered by qt3to4
- use current libavcodec, libavformat and libswscale from system packages
- remove the dependency of the q3support module

Issues not covered by qt3to4 were:
- QImage::scale() -> QImage::scaled()
- implicit cast from std::string to QString
- implicit cast from QString to bool
- lots of changes in method names

Things to consider using QtCreator:
- run setversion.sh to create version information

The autoconf stuff and directories containing library code are not used.
I have
not yet created a new KDevelop4 project, because I do not have any
experience
with KDevelop. If anyone needs this, I will of course look into it. I would
also look into new autoconf support, if anyone can give a good reason for
doing so.

These will be my next steps:
- make sure it still runs on windows
- remove all deprecations and compiler warnings
- use models in all convenient places
- use QListViews instead of QListWidgets
- enable multiple input files
- provide translations
- find similar frames assistant
- etc.

I sent a mail to Sven Over some time ago, but he has not answered yet.
If you like to see, what I have done in the dvbcut project, can please
anybody reply to my and tell me how to proceed?

Cheers,

Wolfgang

Re: [DVBCUT-devel] Status on the project?

[Michael R. <mi...@mr...>]

On 11/07/12 22:36, Francesco Fumanti wrote:

> Could you please tell us whether you are still working on dvbcut 2, that was intended to support hd?

I intend to, but right now my free time is rather limited.

-- 
Michael "Tired" Riepe <mi...@mr...>
X-Tired: Each morning I get up I die a little

Re: [DVBCUT-devel] Status on the project?

[Olaf D. <ola...@ol...>]

Reinhard Tartler <sir...@gm...> writes:

> On Thu, Nov 8, 2012 at 12:17 AM, Olaf Dietsche
> <ola...@ol...> wrote:
>> Michael Riepe <mi...@mr...> writes:
>>
>>> Hi *,
>>>
>>> On 11/07/12 17:26, Reinhard Tartler wrote:
>>>
>>>> Regarding libav, I've tried to compile dvbcut against libav 9, but the
>>>> list of compilation issues is long.
>>>
>>> I can imagine. I once tried it with libav 7 (I think). Thank you, not again.
>>
>> Just curious, what are (libav 9) or were (libav 7) the problems? I have
>> it running here (Ubuntu 12.04) with libavcodec53, which claims to be
>> version 4:0.8.3-0ubuntu0 and I'm very comfortable with it.
>>
>
> Have a look at the build log [1] and look for "is deprecated". These
> are heads-up to upstream developers that this function/type/attribute
> is going away in a newer version. This has now happened with libav 9.
>
> [1] https://launchpadlibrarian.net/103823575/buildlog_ubuntu-quantal-amd64.dvbcut_0.5.4%2Bsvn178-2_BUILDING.txt.gz

All in all, there are just a dozen different warnings. If there aren't
more problems, it seems to be a tedious but feasible task.

Regards, Olaf

Re: [DVBCUT-devel] Status on the project?

[Reinhard T. <sir...@gm...>]

On Thu, Nov 8, 2012 at 12:17 AM, Olaf Dietsche
<ola...@ol...> wrote:
> Michael Riepe <mi...@mr...> writes:
>
>> Hi *,
>>
>> On 11/07/12 17:26, Reinhard Tartler wrote:
>>
>>> Since this list seems pretty quiet over the last months, I wanted to
>>> check on the status of the dvbcut project. As maintainer of the dvbcut
>>> package in Debian and Ubuntu, I am actually quite worried about
>>> weather it makes sense to keep the package. I see currently two big
>>> issues: Dependency on Qt3 and necessary updates for libavcodec.
>>
>> That's the big problem with dvbcut. You can't port it to another gui or
>> another codec library - not even a newer version - without an
>> unreasonable amount of work.
>>
>>> Qt3 is somewhat mitigated by a patch, which AFAIUI has still not been
>>> merged upstream. What's the status on that?
>>
>> The problem with the Qt4 patch is that it needs to work on Windows, too.
>> I haven't been able to check that yet, due to lack of time and a
>> suitable system (my notebook, which also ran Windows, went kaput long ago).
>>
>>> Regarding libav, I've tried to compile dvbcut against libav 9, but the
>>> list of compilation issues is long.
>>
>> I can imagine. I once tried it with libav 7 (I think). Thank you, not again.
>
> Just curious, what are (libav 9) or were (libav 7) the problems? I have
> it running here (Ubuntu 12.04) with libavcodec53, which claims to be
> version 4:0.8.3-0ubuntu0 and I'm very comfortable with it.
>

Have a look at the build log [1] and look for "is deprecated". These
are heads-up to upstream developers that this function/type/attribute
is going away in a newer version. This has now happened with libav 9.

[1] https://launchpadlibrarian.net/103823575/buildlog_ubuntu-quantal-amd64.dvbcut_0.5.4%2Bsvn178-2_BUILDING.txt.gz

-- 
regards,
    Reinhard