Discussion:
ffmpeg vs ffmpeg2
Ottavio Caruso
2014-08-12 12:40:11 UTC
Permalink
Let's it move to ffmpeg1 and drop release date from PKGVERSION :)
Ok, in the end I liked this solution best. I've renamed ffmpeg and
ffplay to ffmpeg1 and ffplay1 respectively. I've compile-tested the
programs, but some didn't compile before, and I didn't check closely
if something might have just lost ffmpeg support. Let me know if you
find breakage.
Thomas
Incidentally (and sorry if this seems a thread hijacking)
gst-plugins1-libav compiled against ffmpeg2 seg faults:
http://mail-index.netbsd.org/pkgsrc-users/2014/08/11/msg020209.html

Is this one of these case where gst plugins should/could be rebuilt
against a different version?
Thomas Klausner
2014-08-12 16:40:10 UTC
Permalink
Post by Ottavio Caruso
Incidentally (and sorry if this seems a thread hijacking)
http://mail-index.netbsd.org/pkgsrc-users/2014/08/11/msg020209.html
Is this one of these case where gst plugins should/could be rebuilt
against a different version?
Do you have both ffmpeg and ffmpeg2 installed?
Thomas
Ottavio Caruso
2014-08-13 11:19:38 UTC
Permalink
Post by Thomas Klausner
Post by Ottavio Caruso
Incidentally (and sorry if this seems a thread hijacking)
http://mail-index.netbsd.org/pkgsrc-users/2014/08/11/msg020209.html
Is this one of these case where gst plugins should/could be rebuilt
against a different version?
Do you have both ffmpeg and ffmpeg2 installed?
I did have ffmpeg2 and ffmpeg010. I have now removed both but I
haven't tried rebuilding. Would it be worth it?
Thomas Klausner
2014-08-13 13:13:42 UTC
Permalink
Post by Ottavio Caruso
Post by Thomas Klausner
Post by Ottavio Caruso
Incidentally (and sorry if this seems a thread hijacking)
http://mail-index.netbsd.org/pkgsrc-users/2014/08/11/msg020209.html
Is this one of these case where gst plugins should/could be rebuilt
against a different version?
Do you have both ffmpeg and ffmpeg2 installed?
I did have ffmpeg2 and ffmpeg010. I have now removed both but I
haven't tried rebuilding. Would it be worth it?
No, it was only between ffmpeg1 and the others that I saw bad
interaction. I'm not sure why you see segfaults.

What exactly are you doing? Perhaps someone can replicate it.
Thomas
Ottavio Caruso
2014-08-13 13:23:16 UTC
Permalink
Post by Thomas Klausner
Post by Ottavio Caruso
Post by Thomas Klausner
Post by Ottavio Caruso
Incidentally (and sorry if this seems a thread hijacking)
http://mail-index.netbsd.org/pkgsrc-users/2014/08/11/msg020209.html
Is this one of these case where gst plugins should/could be rebuilt
against a different version?
Do you have both ffmpeg and ffmpeg2 installed?
I did have ffmpeg2 and ffmpeg010. I have now removed both but I
haven't tried rebuilding. Would it be worth it?
No, it was only between ffmpeg1 and the others that I saw bad
interaction. I'm not sure why you see segfaults.
What exactly are you doing? Perhaps someone can replicate it.
I saw that gstreamer1 and correspondent plugins had been updated, so I
did a 'make update' on all the affected packages. After doing that,
anytime the gst-plugins1-libav was activated, Firefox crashed and an
error was output as in this message:
http://mail-index.netbsd.org/pkgsrc-users/2014/08/11/msg020209.html

But at this point I think it had nothing to do with ffmpeg, although a
similar thread on the ffmpeg-devel mailing lists suggested otherwise:
https://www.mail-archive.com/ffmpeg-***@ffmpeg.org/msg00520.html

Would you like me to fill a BR for that occurrence?
Thomas Klausner
2014-08-13 15:58:35 UTC
Permalink
Post by Ottavio Caruso
I saw that gstreamer1 and correspondent plugins had been updated, so I
did a 'make update' on all the affected packages. After doing that,
anytime the gst-plugins1-libav was activated, Firefox crashed and an
http://mail-index.netbsd.org/pkgsrc-users/2014/08/11/msg020209.html
Which webpage triggers this, for example?

You could additionally rebuild gst-plugin1-libav with symbols and post
the backtrace.
Thomas
Ottavio Caruso
2014-08-14 08:20:30 UTC
Permalink
Post by Thomas Klausner
Post by Ottavio Caruso
I saw that gstreamer1 and correspondent plugins had been updated, so I
did a 'make update' on all the affected packages. After doing that,
anytime the gst-plugins1-libav was activated, Firefox crashed and an
http://mail-index.netbsd.org/pkgsrc-users/2014/08/11/msg020209.html
Which webpage triggers this, for example?
This one:
http://www.quirksmode.org/html5/tests/video.html
Post by Thomas Klausner
You could additionally rebuild gst-plugin1-libav with symbols and post
the backtrace.
Thanks. Are you referring to :
PKG_DEBUG_LEVEL=yes
or
PKG_OPTIONS.gst-plugin1-libav = devel ?

The backtrace I did earlier was:

#0 0x0000000000000001 in ?? ()
#1 0x00007f7ffffffe40 in ?? ()
#2 0x0000000000000000 in ?? ()

I see from the changelog that there's been a bit of bug fixing on
ffmpeg2 so I'll give it a go.
Alistair Crooks
2014-08-19 19:10:07 UTC
Permalink
Post by Ottavio Caruso
PKG_DEBUG_LEVEL=yes
You should probably be aware that PKG_DEBUG_LEVEL takes a numeric value:

0: (default) no debugging information
1: echo commands to be executed
2: echo everything

Regards,
Alistair

Ottavio Caruso
2014-08-14 14:56:28 UTC
Permalink
Post by Thomas Klausner
Post by Ottavio Caruso
I saw that gstreamer1 and correspondent plugins had been updated, so I
did a 'make update' on all the affected packages. After doing that,
anytime the gst-plugins1-libav was activated, Firefox crashed and an
http://mail-index.netbsd.org/pkgsrc-users/2014/08/11/msg020209.html
Which webpage triggers this, for example?
You could additionally rebuild gst-plugin1-libav with symbols and post
the backtrace.
Thomas
I've updated pkgsrc from head and rebuilt ffmpeg2 and no I have no seg
fault for gst-plugin1-libav.
Loading...