Bug#739455: FTBFS with libav10

2014-02-18 Thread Erik Massop
On Tue, 18 Feb 2014 22:24:43 +0100
Moritz Muehlenhoff j...@debian.org wrote:

 Migration documentation can be found at
 https://wiki.libav.org/Migration/10

The attached patch makes the last release of xmms2 build for me with
ffmpeg 2.1.3. I don't have libav here, but looking at document mentioned
above it should work. The patch is just the diff of src/plugins/avcodec
between current devel and last release 0.8DrO_o, with the minor change
s/XMMS_XFORM_PLUGIN_DEFINE/XMMS_XFORM_PLUGIN/.

The patches to src/plugins/avcodec since the last release can be found
here:

http://git.xmms2.org/xmms2/xmms2-devel/log/src/plugins/avcodec?id=0.8DrO_o..d066d6775dd9fce5c8cf30a8068fd2eba4045773


Regards,

Erik Massop / nesciens


backport-avcodec
Description: Binary data


Bug#542956: xmms2 list and xmms2 status show different song

2012-06-25 Thread Erik Massop
On Mon, 25 Jun 2012 15:52:51 +0200
Rémi Vanicat vani...@debian.org wrote:

 Michal Suchanek hramr...@centrum.cz writes:
 
  In xmms2 list the arrow points to a different song than the one
  currently played (and shown by xmms2 status).

This bug is not fixed. However, it is also unlikely to be fixed, as
some people like this behaviour. It is a consequence of allowing the
changing of playlists without interrupting the currently playing song.

This is a 'wontfix' for now, if such a resolution is available.


Wth kind regards,

Erik Massop / nesciens



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#542956: xmms2 list and xmms2 status show different song

2012-06-25 Thread Erik Massop
On Mon, 25 Jun 2012 17:30:39 +0200
Rémi Vanicat vani...@debian.org wrote:

 A visual clue that the pointed song is not the currently played one could
 solve the bug without removing the said feature.
 
 By the way, should I report this bug into mantis?

I added at feature request for it in mantis [1]. Does it need changes?


Regards,

Erik Massop / nesciens


[1] http://bugs.xmms2.org/view.php?id=2536



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#559999: Fails to show tags using UTF-8 right way, if encoding is specified

2011-12-13 Thread Erik Massop
Dear Mehturt,

On Tue, December 13, 2011 11:02 am, Mehturt wrote:
 On Tue, Dec 13, 2011 at 10:52 AM, Daniel Svensson dsvens...@gmail.com
 wrote:
 Upload the file somewhere for inspection.

 Here it is:

 http://c3p0.dyndns.org/Svaty%20Vincent%20-%2002%20-%20Rikaji%20o%20mne,%20ze%20jsem%20blazen.mp3


The tag is wrong. Here's a piece of xxd output of the file:
 0c0: 2154 4954 3200  5500  c598 c3ad  !TIT2...U...
The last 4 bytes are the beginning of the title. We see that the byte just
before that is 00. That means that the title should be
ISO-8859-1-encoded[1]. In fact in id3v2.3 it doesn't even seem possible to
have utf-8 encoded strings. Version 2.4 of the spec does support utf-8,
but then that 00 should be 03 [2]. Changing 00 to 03 indeed solves the
problem for me.

According to a forum post [3] easytag can fix this automatically.


Regards,

Erik Massop / nesciens


[1] The Id3v2.3 spec at http://www.id3.org/id3v2.3.0 :
Frames that allow different types of text encoding have a text encoding
description byte directly after the frame size. If ISO-8859-1 is used this
byte should be $00, if Unicode is used it should be $01.

[2] The id3v2.4.0 spec at http://www.id3.org/id3v2.4.0-structure :
Frames that allow different types of text encoding contains a text
   encoding description byte. Possible encodings:

 $00   ISO-8859-1 [ISO-8859-1]. Terminated with $00.
 $01   UTF-16 [UTF-16] encoded Unicode [UNICODE] with BOM. All
   strings in the same frame SHALL have the same byteorder.
   Terminated with $00 00.
 $02   UTF-16BE [UTF-16] encoded Unicode [UNICODE] without BOM.
   Terminated with $00 00.
 $03   UTF-8 [UTF-8] encoded Unicode [UNICODE]. Terminated with $00.

[3] texray at http://www.musicpd.org/forum/index.php?topic=1552.0;wap2 :
Well, as it turned out, it is the fault of the id3v2 tool. It was
supposed to write the tags in UTF-8, but it didn't. Maybe it doesn't
support ID3v2.4 (which is the first version of IDv2 that officially
supports UTF-8, according to Wikipedia). I checked with easytag and it it
can automatically convert older ID3v2 tags to ID3v2.4, which worked in mpd
as expected.




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#641376: /usr/bin/xmms2d: segfault when switching away from apple-lossless-encoded track

2011-09-17 Thread Erik Massop
On Sat, September 17, 2011 7:00 am, Jonathan Rockway wrote:
 I can't reproduce this when I build xmms2 from git myself.  There must
 be something odd about the Debian build itself.

I can imagine that this is caused by our (past) use of g_new0 instead of
avcodec_alloc_context. This can break when xmms2 is run with a different
(minor) version of avcodec than it is compiled with. See commit 9b1229
[1].


Regards,

Erik Massop / nesciens


[1]
http://git.xmms.se/xmms2/xmms2-devel/commit/?id=9b12296581b16183a9658f253ac8c51621405bac




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#588519: Acknowledgement (xmms2-plugin-tta: tta plugin does not work)

2010-07-10 Thread Erik Massop
On Sat, July 10, 2010 2:27 pm, Yang Zhe wrote:
 I see it is because of the below change in libavcodec/util.c,
 -avctx-codec_id = codec-id;
 +if ((avctx-codec_type == CODEC_TYPE_UNKNOWN || avctx-codec_type
 == codec-type) 
 +avctx-codec_id == CODEC_ID_NONE) {
 +avctx-codec_type = codec-type;
 +avctx-codec_id   = codec-id;
 +}
 +if(avctx-codec_id != codec-id || avctx-codec_type != codec-type){
 +av_log(avctx, AV_LOG_ERROR, codec type or id mismatches\n);
 +goto free_and_end;
 +}

 but I can't understand that in xmms2-0.7DrNo/src/plugins/avcodec/avcodec.c

 data-codecctx = g_new0 (AVCodecContext, 1);

 is initialized to zero. In avcodec_open() function it should go into
 the first if clause. why not.

This seems to be bug 2332 ( http://bugs.xmms2.xmms.se/view.php?id=2332 ).
It is fixed in devel (
http://git.xmms.se/?p=xmms2-devel.git;a=commit;h=71666f5ac8465fc40c8220043174f45e7088c3f0
).

Maybe it is neater to use avcodec_alloc_context() as suggested in
avcodec.h at avcodec_open (and at
http://wiki.aasimon.org/doku.php?id=ffmpeg:avcodec_open ) instead of
g_new0 to make sure such a bug will not show up again with a new version
of avcodec.

(Also it doesn't seem data-codecctx is freed anywhere?)


Regards,

Erik Massop / nesciens




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#588519: xmms2-plugin-tta: tta plugin does not work

2010-07-09 Thread Erik Massop
For me  after xmms2 add /tmp/test.tta xmms2d reports:

15:35:20  INFO: ../src/xmms/xform.c:1475: Successfully setup chain for
'file:///tmp/test.tta' (2280) containing file:magic:tta:avcodec:segment

Could you please check if you have the avcodec-plugin? (File, magic and
segment should be default/integrated in the core.)

If you do and it still doesn't work, could you then please post the
relevant verbose output of xmms2d -v?


Regards,

Erik Massop / nesciens




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org