Re: status of mp4, mov, mkv ?

Hi Ken,


> I noticed that xine-{lib,ui} default to -O3 -g, so I've changed my builds to use -O3,

xine-ui does not (yet).

Also, it is a bad idea to turn off -g when there are issues.


>   and then I looked at things like -D_FORTIFY_SOURCE=2,

xine does not use that macro now, and I dont really know what it should do.


> -fstack-protector=strong and so forth.

> On my first runs I'd seen xine (ui) crash when I tried to play some mp4 file and thought "don't do that,
> then".
>
> With some builds, and some files, I see crashes.

Not very helpful. Were these real crashes or guard exits?

Did they also happen without "hardening"?

Generally, bug reports against current rev would be much easier to handle.


> Sometimes movement in the file causes the picture to jump backwards and "vibrate". One
> of the affected files, which I could share except for its size, is a
> file from my own camera - it started as a 77MB .mov in 2011, and in
> late 2011 I used the then-current ffmpeg to convert it to mp4 (14 MB).
>
> I think this is caused by out-of-order timestamps in the original
> .mov file (tried ripping it using recent ffmpeg and x265, which is
> smaller, but with similar "sometimes xine crashes" results).
A sample file would be great. Dont send the file itself to xine-devel,
it has very rigid size limits.


Torsten