Re: [LMMS-devel] CLang scan build

2015-05-14 Thread Yann Collette
If you are interested, I can do this scan-build before every release ... Just send an email on the mailing list. Le 14/05/2015 15:08, Tres Finocchiaro a écrit : Thanks Yann. The vast majority of those (about 307 of them, or 90%) are introduced with some older 3rd party LADSPA plugins, namel:

Re: [LMMS-devel] MIDI import bug

2015-05-14 Thread midi-pascal
On 15-05-14 03:45 AM, Raine M. Ekman wrote: > Quoting midi-pascal : > >> The idea of naming the imported tracks and CC is a very nice feature too! >> However the tracks name import does not work as expected: >> The tracks are named Track 1, Track2... Track n, even if they have a >> name in the or

Re: [LMMS-devel] CLang scan build

2015-05-14 Thread Tres Finocchiaro
Thanks Yann. The vast majority of those (about 307 of them, or 90%) are introduced with some older 3rd party LADSPA plugins, namel: - 67% - SWH LADSPA Plugin - 12% - Tap LADSPA Plugin - 7% Calf LADSPA Plugin - 4% Zyn Instrument Plugin - 10% LMMS source If someone is familiar wit

[LMMS-devel] CLang scan build

2015-05-14 Thread Yann Collette
Hello, I build LMMS from git repo using clang scan build on fedora 21 64 bits with clang-3.5. The log of the scan build is available on http://ycollette.free.fr/LMMS/scan-build-2015-05-14-134424-1529-1.tar.gz This report can be opened using firefox on the file scan-build-2015-05-14-134424-1529-

Re: [LMMS-devel] MIDI import bug

2015-05-14 Thread Raine M. Ekman
Quoting midi-pascal : > The idea of naming the imported tracks and CC is a very nice feature too! > However the tracks name import does not work as expected: > The tracks are named Track 1, Track2... Track n, even if they have a > name in the original MIDI file. It did work back when I first made