qtractor-devel Mailing List for Qtractor (Page 4)
An Audio/MIDI multi-track sequencer
Brought to you by:
rncbc
Menu
▾
▴
qtractor-devel — Qtractor development discussion
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
(3) |
Jun
(1) |
Jul
(2) |
Aug
(4) |
Sep
(6) |
Oct
(2) |
Nov
(2) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
|
May
(4) |
Jun
(3) |
Jul
(1) |
Aug
(7) |
Sep
(3) |
Oct
(1) |
Nov
|
Dec
(2) |
| 2009 |
Jan
(4) |
Feb
|
Mar
(4) |
Apr
(2) |
May
|
Jun
(1) |
Jul
|
Aug
(7) |
Sep
(11) |
Oct
(62) |
Nov
(108) |
Dec
(44) |
| 2010 |
Jan
(164) |
Feb
(43) |
Mar
(21) |
Apr
(11) |
May
(18) |
Jun
(7) |
Jul
(17) |
Aug
|
Sep
(11) |
Oct
(4) |
Nov
(25) |
Dec
(18) |
| 2011 |
Jan
(50) |
Feb
(35) |
Mar
(13) |
Apr
(27) |
May
(15) |
Jun
|
Jul
(21) |
Aug
(13) |
Sep
(1) |
Oct
(11) |
Nov
(15) |
Dec
(37) |
| 2012 |
Jan
(59) |
Feb
(39) |
Mar
(1) |
Apr
(3) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(12) |
Oct
(1) |
Nov
(4) |
Dec
(31) |
| 2013 |
Jan
(2) |
Feb
(3) |
Mar
(1) |
Apr
(3) |
May
(1) |
Jun
(1) |
Jul
(8) |
Aug
(8) |
Sep
|
Oct
|
Nov
(1) |
Dec
(5) |
| 2014 |
Jan
(4) |
Feb
|
Mar
(7) |
Apr
(12) |
May
(6) |
Jun
|
Jul
(1) |
Aug
(34) |
Sep
(12) |
Oct
|
Nov
(1) |
Dec
|
| 2015 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
(14) |
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(9) |
Nov
|
Dec
(24) |
| 2016 |
Jan
(7) |
Feb
(3) |
Mar
(2) |
Apr
(14) |
May
(14) |
Jun
(15) |
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
(19) |
Dec
(15) |
| 2017 |
Jan
(7) |
Feb
(2) |
Mar
|
Apr
|
May
(2) |
Jun
(4) |
Jul
|
Aug
(4) |
Sep
(1) |
Oct
|
Nov
|
Dec
(2) |
| 2018 |
Jan
(4) |
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(12) |
Nov
|
Dec
(1) |
| 2019 |
Jan
|
Feb
(21) |
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2020 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
(5) |
Oct
(1) |
Nov
|
Dec
(1) |
| 2021 |
Jan
(1) |
Feb
(1) |
Mar
(8) |
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2022 |
Jan
(3) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
(1) |
| 2023 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
(2) |
| 2024 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
|
Aug
(3) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(2) |
| 2025 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Rui N. C. <rn...@rn...> - 2019-02-14 17:24:39
|
On 2/14/19 5:03 PM, Will Riley wrote: > Trying to rename midi clips from inside Qtractor. Can't seem to find > where to do that... > Thanks! kind of tricky but it's possible: on the midi clip editor menu: File > Properties... usual 'caveat emptor' disclaimer applies ;) cheers -- rncbc aka. Rui Nuno Capela rn...@rn... |
|
From: Will R. <vir...@gm...> - 2019-02-14 17:04:19
|
Trying to rename midi clips from inside Qtractor. Can't seem to find where to do that... Thanks! |
|
From: Rui N. C. <rn...@rn...> - 2019-02-14 14:32:14
|
Hello again, Qtractor 0.9.5 (valentines'19 hotfix) is out! Changes for this hot-fix release are as follows: - HiDPI display screen support (Qt >= 5.6; patch by Hubert Figuiere, thanks). - Fixed for DSSI plug-ins (eg. fluidsynth-dssi) loss of configuration state: clear internal config/state keys on release virtual method. (REGRESSION) - Fixed for NSM (and JACK) sessions not saving the correct file references/symlinks of clips that are recorded or created during the initial and scratch session. Description: Qtractor [1] is an audio/MIDI multi-track sequencer application written in C++ with the Qt framework [2]. Target platform is Linux, where the Jack Audio Connection Kit (JACK [3]) for audio and the Advanced Linux Sound Architecture (ALSA [4]) for MIDI are the main infrastructures to evolve as a fairly-featured Linux desktop audio workstation GUI, specially dedicated to the personal home-studio. Website: http://qtractor.org http://qtractor.sourceforge.net https://qtractor.sourceforge.io Project page: http://sourceforge.net/projects/qtractor Downloads: http://sourceforge.net/projects/qtractor/files - source tarball: http://download.sf.net/qtractor/qtractor-0.9.5.tar.gz - source package (openSUSE Tubleweed): http://download.sf.net/qtractor/qtractor-0.9.5-40.rncbc.suse.src.rpm - binary package (openSUSE Tubleweed): http://download.sf.net/qtractor/qtractor-0.9.5-40.rncbc.suse.x86_64.rpm - AppImage [7] packages: http://download.sf.net/qtractor/qtractor-0.9.5-10.x86_64.AppImage Git repos: https://git.code.sf.net/p/qtractor/code https://github.com/rncbc/qtractor.git https://gitlab.com/rncbc/qtractor.git https://bitbucket.org/rncbc/qtractor.git Wiki (help wanted!): http://sourceforge.net/p/qtractor/wiki/ - static rendering: http://qtractor.org/doc http://qtractor.sourceforge.net/doc https://qtractor.sourceforge.io/doc - user manual & how-to's: http://download.sf.net/qtractor/qtractor-manual-and-howtos.epub http://download.sf.net/qtractor/qtractor-manual-and-howtos.pdf License: Qtractor [1] is free, open-source Linux Audio [5] software, distributed under the terms of the GNU General Public License (GPL [6]) version 2 or later. References: [1] Qtractor - An audio/MIDI multi-track sequencer http://qtractor.org http://qtractor.sourceforge.net https://qtractor.sourceforge.io [2] Qt framework, C++ class library and tools for cross-platform application and UI development http://qt.io/ [3] JACK Audio Connection Kit http://jackaudio.org [4] ALSA, Advanced Linux Sound Architecture http://www.alsa-project.org/ [5] Linux Audio consortium of libre software for audio-related work http://linuxaudio.org [6] GPL - GNU General Public License http://www.gnu.org/copyleft/gpl.html [7] AppImage, Linux apps that run anywhere http://appimage.org/ See also: https://www.rncbc.org/drupal/node/1983 Enjoy && Keep having fun. -- rncbc aka Rui Nuno Capela rn...@rn... |
|
From: Rui N. C. <rn...@rn...> - 2019-02-13 11:02:15
|
On 2/13/19 9:26 AM, Ralf Mardorf wrote: > On Wed, 13 Feb 2019 08:42:06 +0000, Rui Nuno Capela wrote: >> if you want to have different instruments to play you'll need to split >> into separate MIDI tracks *and* different MIDI channels of each own. >> >> so, everything is working as designed ;) > > I criticised this years ago. It doesn't comply with the MIDI standard. as said, it is a *convention*, not a standard. byee -- rncbc aka. Rui Nuno Capela |
|
From: Ralf M. <ral...@al...> - 2019-02-13 09:27:02
|
On Wed, 13 Feb 2019 08:42:06 +0000, Rui Nuno Capela wrote: >if you want to have different instruments to play you'll need to split >into separate MIDI tracks *and* different MIDI channels of each own. > >so, everything is working as designed ;) I criticised this years ago. It doesn't comply with the MIDI standard. If a musician wants to live record and play back the MIDI recording, splitting a track not necessarily does the trick. Some sounds require to do the program change at a well-defined position in the time line. For example, the DX7 factory preset ST.HELENS requires a program change to the factory preset EXPLOSION. A split track, one for ST.HELENS and another for EXPLOSITION won't work, since you need to play one note and do the program change. Let alone program changes to immediately stop e.g. a vintage delay, for example of a SPX 90 II. |
|
From: Rui N. C. <rn...@rn...> - 2019-02-13 08:42:18
|
On 2/13/19 1:24 AM, Will Riley wrote: > I'm able to successfully record program changes, but they don't seem to > want to play back reliably. If I set the program number to "none" in > Track Properties, recorded dynamic PC's are sent on playback. At some > point the track PC property changes from "none" (on its own), to a > value, making it static, no longer sending dynamic PCs on playback > (though they're in the playing track). > Something is wacky, perhaps. Seems like this should be easy - record > live, changing patches on the fly (of course! live performance), play > back, all the P changes play back... > yes you can record MIDI channel bank-select and program-changes (PC) but due to qtractor's MIDI tracking model and convention it won't be rendered on playback as precisely recorded. what you're seeing is exactly what is expected according to this. qtractor model, which follows the old GM/GS/XG convention for that matter, is such that a MIDI track can only convey one and only MIDI channel and one and only instrument assignment: that's why bank and program are track properties. you can have a SMF (Standard MIDI File) with interleaved PC's on the same channel but when imported into qtractor as MIDI tracks, *only the first PC* in the channel sequence is read as the effective MIDI tracks's (bank and) program number. on playback, the MIDI tracks's (bank and) program properties are always honored and overrule any bank-select and program-change that might be interleaved on a MIDI clip sequence. if you want to have different instruments to play you'll need to split into separate MIDI tracks *and* different MIDI channels of each own. so, everything is working as designed ;) hth. cheers -- rncbc aka. Rui Nuno Capela rn...@rn... |
|
From: Will R. <wi...@vi...> - 2019-02-13 01:24:50
|
I'm able to successfully record program changes, but they don't seem to want to play back reliably. If I set the program number to "none" in Track Properties, recorded dynamic PC's are sent on playback. At some point the track PC property changes from "none" (on its own), to a value, making it static, no longer sending dynamic PCs on playback (though they're in the playing track). Something is wacky, perhaps. Seems like this should be easy - record live, changing patches on the fly (of course! live performance), play back, all the P changes play back... Thanks! |
|
From: Will R. <wi...@vi...> - 2019-02-08 16:37:14
|
That was it - Auto-monitor. At first it seemed like you could only monitor the selected track, but turning off auto-monitor and activating individual tracks state/monitor switch did the trick! Many thanks On Thu, Feb 7, 2019 at 11:00 PM Rui Nuno Capela <rn...@rn...> wrote: > On 2/8/19 3:57 AM, Will Riley wrote: > > Is it possible to record and monitor multiple midi tracks simultaneously? > > I have multiple controllers and outboard midi modules which I would like > > to record simultaneously, live performance style. One instrument per > > track. Many tracks. Many controllers. > > > > Yes it can. > > You have to: > > a. set different MIDI channel for each input outboard controller or > module and assign that into each recording MIDI track; > > b. where the above is not possible or desirable, create and set a > different MIDI input bus for each controller or module and assign that > to each recording MIDI track--this is very similar to what to have to do > for recording different audio sources simultaneously; > > c. better turn off Track > Auto-monitor if doing any multi-track > simultaneous recording, as it will confuse things on the current > highlighted track (eg. automatic MIDI channel filtering); > > hth. > cheers > -- > rncbc aka. Rui Nuno Capela > rn...@rn... > > _______________________________________________ > Qtractor-devel mailing list > Qtr...@li... > https://lists.sourceforge.net/lists/listinfo/qtractor-devel > -- Will Riley Re-Recording Mixer/Supervising Sound Editor 424Post, Inc. Cell:323-440-3551 http://www.imdb.com/name/nm0727194/ |
|
From: Rui N. C. <rn...@rn...> - 2019-02-08 07:00:15
|
On 2/8/19 3:57 AM, Will Riley wrote: > Is it possible to record and monitor multiple midi tracks simultaneously? > I have multiple controllers and outboard midi modules which I would like > to record simultaneously, live performance style. One instrument per > track. Many tracks. Many controllers. > Yes it can. You have to: a. set different MIDI channel for each input outboard controller or module and assign that into each recording MIDI track; b. where the above is not possible or desirable, create and set a different MIDI input bus for each controller or module and assign that to each recording MIDI track--this is very similar to what to have to do for recording different audio sources simultaneously; c. better turn off Track > Auto-monitor if doing any multi-track simultaneous recording, as it will confuse things on the current highlighted track (eg. automatic MIDI channel filtering); hth. cheers -- rncbc aka. Rui Nuno Capela rn...@rn... |
|
From: Ralf M. <ral...@al...> - 2019-02-08 06:41:19
|
On Thu, 7 Feb 2019 19:57:43 -0800, Will Riley wrote: >Is it possible to record and monitor multiple midi tracks >simultaneously? I have multiple controllers and outboard midi modules >which I would like to record simultaneously, live performance style. >One instrument per track. Many tracks. Many controllers. Hi, I dropped Linux MIDI in favour of proprietary MIDI software. I don't remember, if Qtractor is able to do it, but I guess it could. Have you already tried to arm several MIDI tracks? If so, is there a problem? If there should be issues, what are those issues? I could imagine a few possible pitfalls, that might be solvable by using qmidiroute. It might be helpful to mention what version of Qtractor you are using. Regards, Ralf |
|
From: Will R. <wi...@vi...> - 2019-02-08 03:57:56
|
Is it possible to record and monitor multiple midi tracks simultaneously? I have multiple controllers and outboard midi modules which I would like to record simultaneously, live performance style. One instrument per track. Many tracks. Many controllers. Thanks! |
|
From: Rui N. C. <rn...@rn...> - 2019-02-07 16:58:40
|
Dear all, Qtractor 0.9.4 (winter'19 beta) is released! Changes for this season are as follows: - Drag-moving and copy-pasting existing clips, while over the main track-view, now shows the respective (audio wave-shapes and MIDI piano-rolls) graphical representations, as much as possible. - For good and bad, session name changes now trickle down to respective audio/MIDI file names as well. - Audio output monitoring meters may now be shown on MIDI tracks and buses as a default user preference option (View/ Options.../Plugins/Instruments/Show audio output monitoring meters) and also in plugin list context sub-menu (Audio/Meters). - Custom color (palette) themes can be exported to and imported from external files. - LV2 plug-in UI GTK2 and X11 in Qt5 host native support are now enabled on configure by default. - Fixed minimum input value as 10% (was 1%) for audio clip time-stretching in the Clip / Edit... dialog. Description: Qtractor [1] is an audio/MIDI multi-track sequencer application written in C++ with the Qt framework [2]. Target platform is Linux, where the Jack Audio Connection Kit (JACK [3]) for audio and the Advanced Linux Sound Architecture (ALSA [4]) for MIDI are the main infrastructures to evolve as a fairly-featured Linux desktop audio workstation GUI, specially dedicated to the personal home-studio. Website: http://qtractor.org http://qtractor.sourceforge.net https://qtractor.sourceforge.io Project page: http://sourceforge.net/projects/qtractor Downloads: http://sourceforge.net/projects/qtractor/files - source tarball: http://download.sf.net/qtractor/qtractor-0.9.4.tar.gz - source package (openSUSE Tubleweed): http://download.sf.net/qtractor/qtractor-0.9.4-39.rncbc.suse.src.rpm - binary package (openSUSE Tubleweed): http://download.sf.net/qtractor/qtractor-0.9.4-39.rncbc.suse.x86_64.rpm - AppImage [7] packages: http://download.sf.net/qtractor/qtractor-0.9.4-9.x86_64.AppImage Git repos: https://git.code.sf.net/p/qtractor/code https://github.com/rncbc/qtractor.git https://gitlab.com/rncbc/qtractor.git https://bitbucket.org/rncbc/qtractor.git Wiki (help wanted!): http://sourceforge.net/p/qtractor/wiki/ - static rendering: http://qtractor.org/doc http://qtractor.sourceforge.net/doc https://qtractor.sourceforge.io/doc - user manual & how-to's: http://download.sf.net/qtractor/qtractor-manual-and-howtos.epub http://download.sf.net/qtractor/qtractor-manual-and-howtos.pdf License: Qtractor [1] is free, open-source Linux Audio [5] software, distributed under the terms of the GNU General Public License (GPL [6]) version 2 or later. References: [1] Qtractor - An audio/MIDI multi-track sequencer http://qtractor.org http://qtractor.sourceforge.net https://qtractor.sourceforge.io [2] Qt framework, C++ class library and tools for cross-platform application and UI development http://qt.io/ [3] JACK Audio Connection Kit http://jackaudio.org [4] ALSA, Advanced Linux Sound Architecture http://www.alsa-project.org/ [5] Linux Audio consortium of libre software for audio-related work http://linuxaudio.org [6] GPL - GNU General Public License http://www.gnu.org/copyleft/gpl.html [7] AppImage, Linux apps that run anywhere http://appimage.org/ See also: https://www.rncbc.org/drupal/node/1980 Enjoy && Keep the fun. -- rncbc aka Rui Nuno Capela |
|
From: Rui N. C. <rn...@rn...> - 2018-12-07 15:53:16
|
Finally! Qtractor 0.9.3 (end-of-autumn'18 beta) is out! All the changes that were simply 'decrastinated' for this season are as follows: - Auto-backward now skips the end-of-session location. - Audio clip time-stretching and pitch-shifting limits are now 10-fold in either direction. - Custom color (palette) theme editor introduced; color (palette) theme changes are now effective immediately, except on default. - Old deprecated Qt4 build support is no more. - Recover audio and MIDI dedicated port connections when changing any of the Metronome, Player and/or Control option settings. - Fix MIDI track (and bus) bank/program reset to none. - Anti-glitch micro-fade-in is disabled on audio clips with zero offset. - Audio and MIDI file players also stopped on Transport / Panic command. - LV2 plug-in UI GTK2 and X11 in Qt5 host native support are now disabled on default configure. - Get rid of symlink duplicates on the default plugin search paths. - According to Debian policy and guidelines, the out-of process plugin scanner (qtractor_plugin_scan) is now installed to $LIBDIR/qtractor. Description: Qtractor [1] is an audio/MIDI multi-track sequencer application written in C++ with the Qt framework [2]. Target platform is Linux, where the Jack Audio Connection Kit (JACK [3]) for audio and the Advanced Linux Sound Architecture (ALSA [4]) for MIDI are the main infrastructures to evolve as a fairly-featured Linux desktop audio workstation GUI, specially dedicated to the personal home-studio. Website: http://qtractor.org http://qtractor.sourceforge.net https://qtractor.sourceforge.io Project page: http://sourceforge.net/projects/qtractor Downloads: http://sourceforge.net/projects/qtractor/files - source tarball: http://download.sf.net/qtractor/qtractor-0.9.3.tar.gz - source package (openSUSE Tubleweed): http://download.sf.net/qtractor/qtractor-0.9.3-38.rncbc.suse.src.rpm - binary package (openSUSE Tubleweed): http://download.sf.net/qtractor/qtractor-0.9.3-38.rncbc.suse.x86_64.rpm - AppImage [7] packages: http://download.sf.net/qtractor/qtractor-0.9.3-8.x86_64.AppImage Git repos: https://git.code.sf.net/p/qtractor/code https://github.com/rncbc/qtractor.git https://gitlab.com/rncbc/qtractor.git https://bitbucket.org/rncbc/qtractor.git Wiki (help wanted!): http://sourceforge.net/p/qtractor/wiki/ - static rendering: http://qtractor.org/doc http://qtractor.sourceforge.net/doc https://qtractor.sourceforge.io/doc - user manual & how-to's: http://download.sf.net/qtractor/qtractor-manual-and-howtos.epub http://download.sf.net/qtractor/qtractor-manual-and-howtos.pdf License: Qtractor [1] is free, open-source Linux Audio [5] software, distributed under the terms of the GNU General Public License (GPL [6]) version 2 or later. References: [1] Qtractor - An audio/MIDI multi-track sequencer http://qtractor.org http://qtractor.sourceforge.net https://qtractor.sourceforge.io [2] Qt framework, C++ class library and tools for cross-platform application and UI development http://qt.io/ [3] JACK Audio Connection Kit http://jackaudio.org [4] ALSA, Advanced Linux Sound Architecture http://www.alsa-project.org/ [5] Linux Audio consortium of libre software for audio-related work http://linuxaudio.org [6] GPL - GNU General Public License http://www.gnu.org/copyleft/gpl.html [7] AppImage, Linux apps that run anywhere http://appimage.org/ See also: http://www.rncbc.org/drupal/node/1958 Enjoy && Keep thefun. -- rncbc aka Rui Nuno Capela |
|
From: Frank N. <bea...@we...> - 2018-10-25 17:10:55
|
Hi Rui and all, ... > > Also, I don't need to connect any JACK audio ports of drumkv1_jack to my soundcard > > to provoke the crash. It's enough to connect MIDI, play MIDI events into drumkv1_jack > > via a keyboard while I am quickly switching the sound bank for a little while > > (Cursor-Up/Down in the "Recently used" dropdown box helps to reproduce this quickly). > > > > drumkv1 0.9.2.36git.1e208a might do better in this regard, you tell me... > > > > Anything else how I can help in digging deeper? Do you need my test data (tiny drum pattern track)? > > I'd love to see this one squashed, https://sonoj.org is just around the corner ;-). > > > > don't switch presets like mad!? you're asking for non pleasant sounds > and nasty things to happen if you insist doing that :) Well, of course the goal is not simply to switch presets quickly because it sounds nasty :-), but rather stabilize the "normal preset switching", and I provoke that with quick switching. Nobody likes to see a sequencer app dying in front of your eyes because of a harmless preset switch while you were just in a "creative moment" :-). Anyway, I tried the new revision, and it's getting more difficult/takes more time to create crashes :-), but I still see one occasionally, though it looks a little different now. The console output shows me: ... drumkv1widget::clearSampleFile() drumkv1widget::activateElement(36) drumkv1widget::updateSchedNotify(0, 0x0000) drumkv1widget::loadPreset("/home/franky/work/audio/CR78/My_Roland_CR78_Kit.drumkv1") pure virtual method called terminate called without an active exception Aborted (core dumped) and inspecting the core dump with gdb shows this: > gdb /usr/local/bin/drumkv1_jack /tmp/core GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/local/bin/drumkv1_jack...done. [New LWP 6265] [New LWP 6261] [New LWP 6259] [New LWP 6260] [New LWP 6263] [New LWP 6262] [New LWP 6264] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `drumkv1_jack'. Program terminated with signal SIGABRT, Aborted. #0 0x00007f6d19286428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 54 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. [Current thread is 1 (Thread 0x7f6cff8b7700 (LWP 6265))] (gdb) bt #0 0x00007f6d19286428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #1 0x00007f6d1928802a in __GI_abort () at abort.c:89 #2 0x00007f6d198c084d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #3 0x00007f6d198be6b6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #4 0x00007f6d198be701 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #5 0x00007f6d198bf23f in __cxa_pure_virtual () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #6 0x00007f6d1ac1a425 in drumkv1_ramp::process (this=0x2abf198, nframes=128) at drumkv1_ramp.h:74 #7 0x00007f6d1ac182c3 in drumkv1_impl::process (this=0x18e3190, ins=0x7f6cff8b6850, outs=0x7f6cff8b6830, nframes=128) at drumkv1.cpp:2232 #8 0x00007f6d1ac18b5a in drumkv1::process (this=0x18dd050, ins=0x7f6cff8b6850, outs=0x7f6cff8b6830, nframes=128) at drumkv1.cpp:2502 #9 0x000000000040a9ad in drumkv1_jack::process (this=0x18dd050, nframes=128) at drumkv1_jack.cpp:276 #10 0x000000000040a06a in drumkv1_jack_process (nframes=128, arg=0x18dd050) at drumkv1_jack.cpp:112 #11 0x00007f6d1b36bc1e in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #12 0x00007f6d1b36b058 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #13 0x00007f6d1b383680 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #14 0x00007f6d19bba6ba in start_thread (arg=0x7f6cff8b7700) at pthread_create.c:333 #15 0x00007f6d1935841d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 As usual - if I shall provide more debug info, let me know. Greetings, Frank |
|
From: Rui N. C. <rn...@rn...> - 2018-10-19 08:13:20
|
On 10/18/18 7:52 PM, Frank Neumann wrote: > > I have run some more tests today, and can still get qtractor/drumkv1 to crash pretty > quickly; the point where it's crashing is not constant, though. > > Now I realized I do not have to run the drumkv1 LV2 plugin in Qtractor; I can also > make the stand-alone "drumkv1_jack" app to crash in a similar way, and I guess > this might make debugging easier. > Also, I don't need to connect any JACK audio ports of drumkv1_jack to my soundcard > to provoke the crash. It's enough to connect MIDI, play MIDI events into drumkv1_jack > via a keyboard while I am quickly switching the sound bank for a little while > (Cursor-Up/Down in the "Recently used" dropdown box helps to reproduce this quickly). > drumkv1 0.9.2.36git.1e208a might do better in this regard, you tell me... > Anything else how I can help in digging deeper? Do you need my test data (tiny drum pattern track)? > I'd love to see this one squashed, https://sonoj.org is just around the corner ;-). > don't switch presets like mad!? you're asking for non pleasant sounds and nasty things to happen if you insist doing that :) cheers && thanks -- rncbc aka. Rui Nuno Capela rn...@rn... |
|
From: Frank N. <bea...@we...> - 2018-10-18 18:53:01
|
Hi again,
a few days ago I wrote:
> > as of drumkv1-0.9.2.34git.56c7f4 today those issues might have been
> > fixed for you to bother again :)
>
> Great, thanks..I gave it a quick try yesterday and was still able to provoke
> a crash after some time of fiddling around, but I have no core dump, so will
> need to go after this again this weekend.
I have run some more tests today, and can still get qtractor/drumkv1 to crash pretty
quickly; the point where it's crashing is not constant, though.
Now I realized I do not have to run the drumkv1 LV2 plugin in Qtractor; I can also
make the stand-alone "drumkv1_jack" app to crash in a similar way, and I guess
this might make debugging easier.
Also, I don't need to connect any JACK audio ports of drumkv1_jack to my soundcard
to provoke the crash. It's enough to connect MIDI, play MIDI events into drumkv1_jack
via a keyboard while I am quickly switching the sound bank for a little while
(Cursor-Up/Down in the "Recently used" dropdown box helps to reproduce this quickly).
Here are some excerpts from inspecting the core dump of a crashed drumkv1_jack instance:
Core was generated by `drumkv1_jack'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f8b57f46924 in drumkv1_sample::ratio (this=0x0) at drumkv1_sample.h:113
113 { return m_ratio; }
[Current thread is 1 (Thread 0x7f8b3cbea700 (LWP 8061))]
(gdb) bt
#0 0x00007f8b57f46924 in drumkv1_sample::ratio (this=0x0) at drumkv1_sample.h:113
#1 0x00007f8b57f46a4a in drumkv1_generator::next (this=0x18eb5d8, freq=65.4063873) at drumkv1_sample.h:193
#2 0x00007f8b57f44167 in drumkv1_impl::process (this=0x18b8cc0, ins=0x7f8b3cbe9850, outs=0x7f8b3cbe9830, nframes=128) at drumkv1.cpp:2078
#3 0x00007f8b57f45a7a in drumkv1::process (this=0x18b18d0, ins=0x7f8b3cbe9850, outs=0x7f8b3cbe9830, nframes=128) at drumkv1.cpp:2502
#4 0x000000000040a8bd in drumkv1_jack::process (this=0x18b18d0, nframes=128) at drumkv1_jack.cpp:276
#5 0x0000000000409f7a in drumkv1_jack_process (nframes=128, arg=0x18b18d0) at drumkv1_jack.cpp:112
#6 0x00007f8b58693c1e in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0
#7 0x00007f8b58693058 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0
#8 0x00007f8b586ab680 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0
#9 0x00007f8b56ef06ba in start_thread (arg=0x7f8b3cbea700) at pthread_create.c:333
#10 0x00007f8b5668e41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
Core was generated by `drumkv1_jack'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f3c6a223961 in drumkv1_sample::isOver (this=0x0, index=0) at drumkv1_sample.h:128
128 { return !m_pframes || (index >= m_offset_end2); }
[Current thread is 1 (Thread 0x7f3c4eebf700 (LWP 8196))]
(gdb) bt
#0 0x00007f3c6a223961 in drumkv1_sample::isOver (this=0x0, index=0) at drumkv1_sample.h:128
#1 0x00007f3c6a223c6c in drumkv1_generator::isOver (this=0x98f8d8) at drumkv1_sample.h:224
#2 0x00007f3c6a223aee in drumkv1_generator::value (this=0x98f8d8, k=0) at drumkv1_sample.h:203
#3 0x00007f3c6a22119f in drumkv1_impl::process (this=0x962c70, ins=0x7f3c4eebe850, outs=0x7f3c4eebe830, nframes=128) at drumkv1.cpp:2081
#4 0x00007f3c6a222a7a in drumkv1::process (this=0x95dc10, ins=0x7f3c4eebe850, outs=0x7f3c4eebe830, nframes=128) at drumkv1.cpp:2502
#5 0x000000000040a8bd in drumkv1_jack::process (this=0x95dc10, nframes=128) at drumkv1_jack.cpp:276
#6 0x0000000000409f7a in drumkv1_jack_process (nframes=128, arg=0x95dc10) at drumkv1_jack.cpp:112
#7 0x00007f3c6a970c1e in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0
#8 0x00007f3c6a970058 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0
#9 0x00007f3c6a988680 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0
#10 0x00007f3c691cd6ba in start_thread (arg=0x7f3c4eebf700) at pthread_create.c:333
#11 0x00007f3c6896b41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
Core was generated by `drumkv1_jack'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fee4cb9bb2c in drumkv1_generator::value (this=0x27bee98, k=0) at drumkv1_sample.h:208
208 const float x0 = frames[m_index];
[Current thread is 1 (Thread 0x7fee31834700 (LWP 8249))]
(gdb) bt
#0 0x00007fee4cb9bb2c in drumkv1_generator::value (this=0x27bee98, k=0) at drumkv1_sample.h:208
#1 0x00007fee4cb9919f in drumkv1_impl::process (this=0x278dc40, ins=0x7fee31833850, outs=0x7fee31833830, nframes=128) at drumkv1.cpp:2081
#2 0x00007fee4cb9aa7a in drumkv1::process (this=0x2788d00, ins=0x7fee31833850, outs=0x7fee31833830, nframes=128) at drumkv1.cpp:2502
#3 0x000000000040a8bd in drumkv1_jack::process (this=0x2788d00, nframes=128) at drumkv1_jack.cpp:276
#4 0x0000000000409f7a in drumkv1_jack_process (nframes=128, arg=0x2788d00) at drumkv1_jack.cpp:112
#5 0x00007fee4d2e8c1e in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0
#6 0x00007fee4d2e8058 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0
#7 0x00007fee4d300680 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0
#8 0x00007fee4bb456ba in start_thread (arg=0x7fee31834700) at pthread_create.c:333
#9 0x00007fee4b2e341d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
Anything else how I can help in digging deeper? Do you need my test data (tiny drum pattern track)?
I'd love to see this one squashed, https://sonoj.org is just around the corner ;-).
Thanks,
Frank
|
|
From: Rui N. C. <rn...@rn...> - 2018-10-13 14:12:10
|
Hi Frank, >> > ... >> I was trying to modify some of the per-sample parameters while playback was rolling, >> and while e.g. filter settings are reacting nicely, the "Width", "Panning", "Effects" >> and "Volume" dials in the "Out" section (bottom right) don't seem to have any effect. >> I was using a mono sample for that, so it should be able to react to Panning at the >> very least. > ... fixed! today's drumkv1-0.9.2.35git.fc8553 ... fyi. this "OUTage bug" was there since (and including) v0.9.2 summer'18 release. thanks -- rncbc aka. Rui Nuno Capela rn...@rn... |
|
From: Rui N. C. <rn...@rn...> - 2018-10-13 11:37:14
|
Frank, On 10/13/18 10:33 AM, Frank Neumann wrote: >> >> as of drumkv1-0.9.2.34git.56c7f4 today those issues might have been >> fixed for you to bother again :) > > Great, thanks..I gave it a quick try yesterday and was still able to provoke > a crash after some time of fiddling around, but I have no core dump, so will > need to go after this again this weekend. > > However, on a sidenote - and maybe the reason for my crash came from that - I > was trying to modify some of the per-sample parameters while playback was rolling, > and while e.g. filter settings are reacting nicely, the "Width", "Panning", "Effects" > and "Volume" dials in the "Out" section (bottom right) don't seem to have any effect. > I was using a mono sample for that, so it should be able to react to Panning at the > very least. > My thought was that your recent "For safety reasons.." changes could be responsible > for this, but even with commit 2c5cbd2 which was before that change, I cannot seem > to modify panning or volume at all via these dials. Am I missing something? > confirmed. and it seems to affect the LV2 plugin only, the stand-alone doesn't seem to suffer from this OUT'age :S gotta figure why... > On still another sidenote :-) - there is an additional pair of "Panning" and "Volume" > dials just above the "Out" section which do have some kind of effect when turned - can > you explain what these are good for? Do we need two pairs of buttons for Panning? > those are of the LFO section thus are modulation amount parameters; the OUTput section refers to fixed, non-modulated amount parameters. > Thanks, and I hope "Leslie" will not strike you too hard :-\ - buckle up!, > Frank > i have no outdoor activities planned for the evening, so probably I'll be safe at home, fixing the LV2 OUTage bug :) cheers -- rncbc aka. Rui Nuno Capela rn...@rn... |
|
From: Frank N. <bea...@we...> - 2018-10-13 09:34:09
|
Hi Rui and all, > >> On a sidenote..I was trying the last few days to change the loaded preset file > >> in drumkv1 while it is actively playing back a short (looped) MIDI pattern > >> (this is for e.g. auditing different drumkits while the underlying pattern > >> is playing and unchanged). > >> > >> This works fine *most* of the time, but every now and then I can make it to > >> crash. I was wondering - should drumkv1 be basically robust to this, or can > >> it happen it attempts to e.g. play back a sample that was free()d just a ms > >> before? > >> > >> I rebuilt drumkv1 with --enable-debug and could produce a core dump and gdb > >> backtrace. It looks like the following; is that enough to start debugging? > >> > > > > don't bother with that > > > > loading samples let alone a set of samples while it's playing some is > > not a safe operation. please refrain and avoid doing that unless you > > enjoy the fun of fireworks burning in your face :) > > > > as of drumkv1-0.9.2.34git.56c7f4 today those issues might have been > fixed for you to bother again :) Great, thanks..I gave it a quick try yesterday and was still able to provoke a crash after some time of fiddling around, but I have no core dump, so will need to go after this again this weekend. However, on a sidenote - and maybe the reason for my crash came from that - I was trying to modify some of the per-sample parameters while playback was rolling, and while e.g. filter settings are reacting nicely, the "Width", "Panning", "Effects" and "Volume" dials in the "Out" section (bottom right) don't seem to have any effect. I was using a mono sample for that, so it should be able to react to Panning at the very least. My thought was that your recent "For safety reasons.." changes could be responsible for this, but even with commit 2c5cbd2 which was before that change, I cannot seem to modify panning or volume at all via these dials. Am I missing something? On still another sidenote :-) - there is an additional pair of "Panning" and "Volume" dials just above the "Out" section which do have some kind of effect when turned - can you explain what these are good for? Do we need two pairs of buttons for Panning? Thanks, and I hope "Leslie" will not strike you too hard :-\ - buckle up!, Frank |
|
From: Rui N. C. <rn...@rn...> - 2018-10-12 07:14:04
|
hi Frank, On 10/7/18 9:08 PM, Rui Nuno Capela wrote: > On 10/7/18 8:14 PM, Frank Neumann wrote: >> >> On a sidenote..I was trying the last few days to change the loaded preset file >> in drumkv1 while it is actively playing back a short (looped) MIDI pattern >> (this is for e.g. auditing different drumkits while the underlying pattern >> is playing and unchanged). >> >> This works fine *most* of the time, but every now and then I can make it to >> crash. I was wondering - should drumkv1 be basically robust to this, or can >> it happen it attempts to e.g. play back a sample that was free()d just a ms >> before? >> >> I rebuilt drumkv1 with --enable-debug and could produce a core dump and gdb >> backtrace. It looks like the following; is that enough to start debugging? >> > > don't bother with that > > loading samples let alone a set of samples while it's playing some is > not a safe operation. please refrain and avoid doing that unless you > enjoy the fun of fireworks burning in your face :) > as of drumkv1-0.9.2.34git.56c7f4 today those issues might have been fixed for you to bother again :) cheers -- rncbc aka. Rui Nuno Capela rn...@rn... |
|
From: Rui N. C. <rn...@rn...> - 2018-10-07 20:08:43
|
On 10/7/18 8:14 PM, Frank Neumann wrote: > > Hi Rui and all, > >>>> $ git log --oneline >>>> 7778e0d - Yet some more offset sync state fixing. <-- gives the reported issue above >>>> a2114b6 Yet another round to offset sync fixing. >>>> a25be50 - Fix LV2 UI initialization (again). <-- this version still works fine >>>> ... >>>> >>>> Any idea what is going on here? >>>> My qtractor version is 0.9.3, commit ID af83cd. >>>> >>> >>> hi Frank, >>> >>> confirmed: current git head (7778e0d) is bonkers :) >>> >>> will try to fix it asap. >>> >> >> maybe fixed now, hopefully! :) >> >> drumkv1.git $ git log --oneline >> 2c5cbd2 (HEAD) - Again some more reverse and offset sync state fixing. >> 7778e0d - Yet some more offset sync state fixing. >> a2114b6 Yet another round to offset sync fixing. > > > Yep, looking good - great reaction time again :-). Thanks a lot! > > > On a sidenote..I was trying the last few days to change the loaded preset file > in drumkv1 while it is actively playing back a short (looped) MIDI pattern > (this is for e.g. auditing different drumkits while the underlying pattern > is playing and unchanged). > > This works fine *most* of the time, but every now and then I can make it to > crash. I was wondering - should drumkv1 be basically robust to this, or can > it happen it attempts to e.g. play back a sample that was free()d just a ms > before? > > I rebuilt drumkv1 with --enable-debug and could produce a core dump and gdb > backtrace. It looks like the following; is that enough to start debugging? > don't bother with that loading samples let alone a set of samples while it's playing some is not a safe operation. please refrain and avoid doing that unless you enjoy the fun of fireworks burning in your face :) cheers -- rncbc aka. Rui Nuno Capela rn...@rn... |
|
From: Frank N. <bea...@we...> - 2018-10-07 19:14:44
|
Hi Rui and all, > >> $ git log --oneline > >> 7778e0d - Yet some more offset sync state fixing. <-- gives the reported issue above > >> a2114b6 Yet another round to offset sync fixing. > >> a25be50 - Fix LV2 UI initialization (again). <-- this version still works fine > >> ... > >> > >> Any idea what is going on here? > >> My qtractor version is 0.9.3, commit ID af83cd. > >> > > > > hi Frank, > > > > confirmed: current git head (7778e0d) is bonkers :) > > > > will try to fix it asap. > > > > maybe fixed now, hopefully! :) > > drumkv1.git $ git log --oneline > 2c5cbd2 (HEAD) - Again some more reverse and offset sync state fixing. > 7778e0d - Yet some more offset sync state fixing. > a2114b6 Yet another round to offset sync fixing. Yep, looking good - great reaction time again :-). Thanks a lot! On a sidenote..I was trying the last few days to change the loaded preset file in drumkv1 while it is actively playing back a short (looped) MIDI pattern (this is for e.g. auditing different drumkits while the underlying pattern is playing and unchanged). This works fine *most* of the time, but every now and then I can make it to crash. I was wondering - should drumkv1 be basically robust to this, or can it happen it attempts to e.g. play back a sample that was free()d just a ms before? I rebuilt drumkv1 with --enable-debug and could produce a core dump and gdb backtrace. It looks like the following; is that enough to start debugging? franky@silence:/tmp> gdb /usr/local/bin/qtractor core GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/local/bin/qtractor...(no debugging symbols found)...done. [New LWP 13606] [New LWP 13602] [New LWP 13601] [New LWP 13603] [New LWP 13604] [New LWP 13608] [New LWP 13609] [New LWP 13605] [New LWP 13615] [New LWP 13607] [New LWP 13600] [New LWP 13614] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `qtractor'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f5399753836 in drumkv1_sample::ratio (this=0x0) at drumkv1_sample.h:113 113 { return m_ratio; } [Current thread is 1 (Thread 0x7f53afbf4700 (LWP 13606))] (gdb) thread apply all bt Thread 12 (Thread 0x7f539a38f700 (LWP 13614)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007f53cd97da5b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x00000000004d6c21 in ?? () #3 0x00007f53cd97c7be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x00007f53cd6c16ba in start_thread (arg=0x7f539a38f700) at pthread_create.c:333 #5 0x00007f53ccb5641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7f53d17049c0 (LWP 13600)): #0 0x00007f53cda0b400 in QString::resize(int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x00007f53cda0b4ad in QString::expand(int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x00007f53cda0bad1 in QString::insert(int, QChar) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x00007f5398acbb0f in QString::prepend (this=0x7fff01c98950, c=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:429 #4 0x00007f5398acbd55 in operator+ (c=91 '[', s=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1272 #5 0x00007f5398acb34a in drumkv1widget_sample::updateToolTip (this=0x256dd60) at drumkv1widget_sample.cpp:691 #6 0x00007f5398ac82c9 in drumkv1widget_sample::setSampleName (this=0x256dd60, sName=...) at drumkv1widget_sample.cpp:160 #7 0x00007f5398ab108c in drumkv1widget::updateSample (this=0x254c090, pSample=0x0, bDirty=false) at drumkv1widget.cpp:1071 #8 0x00007f5398ab0e57 in drumkv1widget::clearSampleFile (this=0x254c090) at drumkv1widget.cpp:1037 #9 0x00007f5398ab0698 in drumkv1widget::loadPreset (this=0x254c090, sFilename=...) at drumkv1widget.cpp:957 #10 0x00007f5398af12ba in drumkv1widget::qt_static_metacall (_o=0x254c090, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fff01c98d00) at .moc_ui/moc_drumkv1widget.cpp:165 #11 0x00007f53cdb8bd2a in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x00007f5398af3d9c in drumkv1widget_preset::loadPresetFile (this=0x254ca40, _t1=...) at .moc_ui/moc_drumkv1widget_preset.cpp:200 #13 0x00007f5398ad32d6 in drumkv1widget_preset::loadPreset (this=0x254ca40, sPreset=...) at drumkv1widget_preset.cpp:197 #14 0x00007f5398ad3264 in drumkv1widget_preset::activatePreset (this=0x254ca40, sPreset=...) at drumkv1widget_preset.cpp:186 #15 0x00007f5398af3ac6 in drumkv1widget_preset::qt_static_metacall (_o=0x254ca40, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0x7fff01c98ef0) at .moc_ui/moc_drumkv1widget_preset.cpp:118 #16 0x00007f53cdb8bd2a in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x00007f53ce5622a5 in QComboBox::activated(QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x00007f53ce5646c6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x00007f53ce566f49 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x00007f53ce56c5dd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x00007f53cdb8bd2a in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x00007f53ce7eb132 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x00007f53ce562c38 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x00007f53cdb5d172 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x00007f53ce45003c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x00007f53ce455c19 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x00007f53cdb5d38b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x00007f53ce454b32 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x00007f53ce4ad91d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x00007f53ce4afb7b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x00007f53ce45005c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #32 0x00007f53ce455516 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #33 0x00007f53cdb5d38b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x00007f53cde9f4e1 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #35 0x00007f53cdea11a5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #36 0x00007f53cde84f08 in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #37 0x00007f53d1650200 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #38 0x00007f53c9e4b197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #39 0x00007f53c9e4b3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #40 0x00007f53c9e4b49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #41 0x00007f53cdbb37cf in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #42 0x00007f53cdb5ab4a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #43 0x00007f53cdb62bec in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ---Type <return> to continue, or q <return> to quit--- #44 0x0000000000453812 in ?? () #45 0x00007f53cca6f830 in __libc_start_main (main=0x4535c0, argc=1, argv=0x7fff01c9b1c8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff01c9b1b8) at ../csu/libc-start.c:291 #46 0x00000000004562a9 in ?? () Thread 10 (Thread 0x7f53ae05e700 (LWP 13607)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007f53cd97da5b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x00000000005376c2 in ?? () #3 0x00007f53cd97c7be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x00007f53cd6c16ba in start_thread (arg=0x7f53ae05e700) at pthread_create.c:333 #5 0x00007f53ccb5641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7f5399728700 (LWP 13615)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007f53cd97da5b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x00007f5399768290 in drumkv1_sched_thread::run (this=0x23a50a0) at drumkv1_sched.cpp:155 #3 0x00007f53cd97c7be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x00007f53cd6c16ba in start_thread (arg=0x7f5399728700) at pthread_create.c:333 #5 0x00007f53ccb5641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f53af55e700 (LWP 13605)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007f53cd97da5b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x000000000045ae32 in ?? () #3 0x00007f53cd97c7be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x00007f53cd6c16ba in start_thread (arg=0x7f53af55e700) at pthread_create.c:333 #5 0x00007f53ccb5641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f53ad05c700 (LWP 13609)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007f53cd97da5b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x0000000000521b32 in ?? () #3 0x00007f53cd97c7be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x00007f53cd6c16ba in start_thread (arg=0x7f53ad05c700) at pthread_create.c:333 #5 0x00007f53ccb5641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f53ad85d700 (LWP 13608)): #0 0x00007f53ccb4a74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x0000000000523c45 in ?? () #2 0x00007f53cd97c7be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x00007f53cd6c16ba in start_thread (arg=0x7f53ad85d700) at pthread_create.c:333 #4 0x00007f53ccb5641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f53afc97700 (LWP 13604)): #0 0x00007f53ccb4627d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007f53c5cc2073 in ?? () from /usr/lib/nvidia-384/tls/libnvidia-tls.so.384.130 #2 0x00007f53d135c065 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #3 0x00007f53d135ed9b in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #4 0x00007f53d135a680 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #5 0x00007f53cd6c16ba in start_thread (arg=0x7f53afc97700) at pthread_create.c:333 #6 0x00007f53ccb5641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f53afd18700 (LWP 13603)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007f53d135b6ac in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #2 0x00007f53d1352a48 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #3 0x00007f53d135a680 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 ---Type <return> to continue, or q <return> to quit--- #4 0x00007f53cd6c16ba in start_thread (arg=0x7f53afd18700) at pthread_create.c:333 #5 0x00007f53ccb5641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f53bedbb700 (LWP 13601)): #0 0x00007f53ccb4a74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007f53c7288c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x00007f53c728a8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x00007f53d161e889 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x00007f53cd97c7be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007f53cd6c16ba in start_thread (arg=0x7f53bedbb700) at pthread_create.c:333 #6 0x00007f53ccb5641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f53b4ccc700 (LWP 13602)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007f53cd97da5b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x00007f53ce68382a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #3 0x00007f53cd97c7be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x00007f53cd6c16ba in start_thread (arg=0x7f53b4ccc700) at pthread_create.c:333 #5 0x00007f53ccb5641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f53afbf4700 (LWP 13606)): #0 0x00007f5399753836 in drumkv1_sample::ratio (this=0x0) at drumkv1_sample.h:113 #1 0x00007f539975395c in drumkv1_generator::next (this=0x2510918, freq=73.4161987) at drumkv1_sample.h:193 #2 0x00007f539975114c in drumkv1_impl::process (this=0x26a91d0, ins=0x7f53afbf38c0, outs=0x7f53afbf38a0, nframes=128) at drumkv1.cpp:2069 #3 0x00007f53997529b6 in drumkv1::process (this=0x2337eb0, ins=0x7f53afbf38c0, outs=0x7f53afbf38a0, nframes=128) at drumkv1.cpp:2480 #4 0x00007f53999895e5 in drumkv1_lv2::run (this=0x2337eb0, nframes=128) at drumkv1_lv2.cpp:409 #5 0x00007f539998a5a5 in drumkv1_lv2_run (instance=0x2337eb0, nframes=128) at drumkv1_lv2.cpp:737 #6 0x00000000004d6614 in ?? () #7 0x000000000055f621 in ?? () #8 0x0000000000538a9f in ?? () #9 0x0000000000467391 in ?? () #10 0x00007f53d1342c1e in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #11 0x00007f53d1342058 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #12 0x00007f53d135a680 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 #13 0x00007f53cd6c16ba in start_thread (arg=0x7f53afbf4700) at pthread_create.c:333 #14 0x00007f53ccb5641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 (gdb) Greetings, Frank |
|
From: Rui N. C. <rn...@rn...> - 2018-10-07 11:31:49
|
On 10/7/18 11:44 AM, Rui Nuno Capela wrote: > On 10/7/18 8:40 AM, Frank Neumann wrote: >> >> Hi Rui and all, (first off: This is a problem report for drumkv1, not for qtractor) >> >> I noticed that with the current drumkv1 Git state there is a regression: Instantiating >> a drumkv1 LV2 plugin causes one CPU core to got to 100% load; the GUI becomes >> unresponsive, and the whol qtractor session is essentially unusable (though there >> is no crash). >> >> I compared this to recent versions of e.g. padthv1 since they are often in sync, >> but padthv1 behaves fine. >> >> Looking closer, I see there were two recent commits on (only) drumkv1 that broke it for me: >> >> $ git log --oneline >> 7778e0d - Yet some more offset sync state fixing. <-- gives the reported issue above >> a2114b6 Yet another round to offset sync fixing. >> a25be50 - Fix LV2 UI initialization (again). <-- this version still works fine >> ... >> >> Any idea what is going on here? >> My qtractor version is 0.9.3, commit ID af83cd. >> > > hi Frank, > > confirmed: current git head (7778e0d) is bonkers :) > > will try to fix it asap. > maybe fixed now, hopefully! :) drumkv1.git $ git log --oneline 2c5cbd2 (HEAD) - Again some more reverse and offset sync state fixing. 7778e0d - Yet some more offset sync state fixing. a2114b6 Yet another round to offset sync fixing. cheers -- rncbc aka. Rui Nuno Capela rn...@rn... |
|
From: Rui N. C. <rn...@rn...> - 2018-10-07 10:44:20
|
On 10/7/18 8:40 AM, Frank Neumann wrote: > > Hi Rui and all, (first off: This is a problem report for drumkv1, not for qtractor) > > I noticed that with the current drumkv1 Git state there is a regression: Instantiating > a drumkv1 LV2 plugin causes one CPU core to got to 100% load; the GUI becomes > unresponsive, and the whol qtractor session is essentially unusable (though there > is no crash). > > I compared this to recent versions of e.g. padthv1 since they are often in sync, > but padthv1 behaves fine. > > Looking closer, I see there were two recent commits on (only) drumkv1 that broke it for me: > > $ git log --oneline > 7778e0d - Yet some more offset sync state fixing. <-- gives the reported issue above > a2114b6 Yet another round to offset sync fixing. > a25be50 - Fix LV2 UI initialization (again). <-- this version still works fine > ... > > Any idea what is going on here? > My qtractor version is 0.9.3, commit ID af83cd. > hi Frank, confirmed: current git head (7778e0d) is bonkers :) will try to fix it asap. thanks -- rncbc aka. Rui Nuno Capela rn...@rn... |
|
From: Frank N. <bea...@we...> - 2018-10-07 07:41:06
|
Hi Rui and all, (first off: This is a problem report for drumkv1, not for qtractor) I noticed that with the current drumkv1 Git state there is a regression: Instantiating a drumkv1 LV2 plugin causes one CPU core to got to 100% load; the GUI becomes unresponsive, and the whol qtractor session is essentially unusable (though there is no crash). I compared this to recent versions of e.g. padthv1 since they are often in sync, but padthv1 behaves fine. Looking closer, I see there were two recent commits on (only) drumkv1 that broke it for me: $ git log --oneline 7778e0d - Yet some more offset sync state fixing. <-- gives the reported issue above a2114b6 Yet another round to offset sync fixing. a25be50 - Fix LV2 UI initialization (again). <-- this version still works fine ... Any idea what is going on here? My qtractor version is 0.9.3, commit ID af83cd. Thanks, Frank |
12 messages has been excluded from this view by a project administrator.
