Re: [Development] Exception to source compatibility: adding AA_CompressHighFrequencyEvents flag

2016-04-27 Thread Boudewijn Rempt
On Wed, 27 Apr 2016, Lisandro Damián Nicanor Pérez Meyer wrote: On Wednesday 27 April 2016 08:50:48 Boudewijn Rempt wrote: [snip] As a Debian developer, you might also consider that you should never ever package Krita 3 for Debian with a Qt 5.6 without this fix. You'd have to carry the patch

Re: [Development] QMovie no longer supports .mng

2016-04-27 Thread Thiago Macieira
On quarta-feira, 27 de abril de 2016 02:10:09 PDT Jake Petroules wrote: > If we can simply update libmng and recompile against the new version then we > should do so immediately! I still vote for carrying fewer dependencies, especially those that try to read external files and may be used on

Re: [Development] Exception to source compatibility: adding AA_CompressHighFrequencyEvents flag

2016-04-27 Thread Lisandro Damián Nicanor Pérez Meyer
On Wednesday 27 April 2016 08:50:48 Boudewijn Rempt wrote: [snip] > As a Debian developer, you might also consider that you should never > ever package Krita 3 for Debian with a Qt 5.6 without this fix. You'd have > to carry the patch for Qt 5.6 or forego packaging Krita (and later on, >

Re: [Development] QtMultimedia && QML - hard performance regressions on Windows

2016-04-27 Thread Massimo Callegari via Development
Da: Mitch Curtis A: Massimo Callegari ; "development@qt-project.org" Inviato: Mercoledì 27 Aprile 2016 14:56 Oggetto: RE: [Development] QtMultimedia && QML - hard performance

Re: [Development] QtMultimedia && QML - hard performance regressions on Windows

2016-04-27 Thread Mitch Curtis
> -Original Message- > From: Development [mailto:development-bounces+mitch.curtis=qt.io@qt- > project.org] On Behalf Of Massimo Callegari via Development > Sent: Wednesday, 27 April 2016 12:28 PM > To: Denis Shienkov ; development@qt-project.org > Subject: Re:

Re: [Development] QtMultimedia && QML - hard performance regressions on Windows

2016-04-27 Thread Denis Shienkov
> I've seen something similar and solved it by changing codecs (installed k-lite codec pack) I have the K-Lite codec pack already installed (I'm sorry, if I haven't mentioned it). BR, Denis 2016-04-27 14:10 GMT+03:00 Sergio Martins : > On Wednesday, 27 April 2016

Re: [Development] QtMultimedia && QML - hard performance regressions on Windows

2016-04-27 Thread Sergio Martins
On Wednesday, 27 April 2016 12:37:26 WEST Denis Shienkov wrote: > Hi developers. > > I faced with a big problem with the video playback performance, when I try > to open the mp4 video file from any of QML video examples. I have a high > CPU loading (~40%) and the video is freezing and jerks. But

Re: [Development] QtMultimedia && QML - hard performance regressions on Windows

2016-04-27 Thread Massimo Callegari via Development
Hey Denis, welcome to the "QtMultimedia lovers" club :) Good luck with your remarks, most likely nobody will care. It seems that the primary role of QtMultimedia is to capture input video. All the rest doesn't matter. I've opened a number of tickets and none of them have been solved:

[Development] QtMultimedia && QML - hard performance regressions on Windows

2016-04-27 Thread Denis Shienkov
Hi developers. I faced with a big problem with the video playback performance, when I try to open the mp4 video file from any of QML video examples. I have a high CPU loading (~40%) and the video is freezing and jerks. But the C++ media player works satisfactory, more or less tolerably (on point

[Development] Heads up - 5.7 soft string freeze

2016-04-27 Thread Jani Heikkinen
Hi all, Qt 5.7 beta is out & work towards final release continues. One step on the way is String Freeze which is planned to happen 7th May 2016, see https://wiki.qt.io/Qt-5.7-release. So it is time to start keeping the translatable strings as it is and fix remaining important issues. Br,

Re: [Development] Exception to source compatibility: adding AA_CompressHighFrequencyEvents flag

2016-04-27 Thread Boudewijn Rempt
On Tue, 26 Apr 2016, Lisandro Damián Nicanor Pérez Meyer wrote: Please correct me if I'm wrong: the feature which will break API was added in 5.6.0, and we can say that most of the people out there are not using it. Ideally API/ABI should not be broken without a SONAME change. If I had some