Qtractor crash recovery

most probably it's a rogue VST plugin...

you can run from the console under gdb:

open the offending .qtr file and when it stops here eventually on segfault:

an immediate stacktrace is dumped and check where and what's the offending crash point (should point to which plugin, library or code that is segfaulting.

once you find the culprit, try to edit the .qtr file and remove the suspect sections, assuming it's one or more plugins that is causing trouble.

hth.
cheers

Hi Rui, I have a strange problem with 1.5.8 (yes, I realize its old), where it corrupts the .mid files. I checked prior that the file had midi data using Rosegarden. Yet Qtractor showed no data in the clip box. Opening the properties F4 for the clip data selecting the another midi file and exiting Qtractor causes the new selected file to be corrupted (no midi data but comments like Verse1, Chorus1 still shows in the file via Rosegarden. Its like the file type is not 0 or 1 ? Also the midi file size still shows it has has some bytes 200+ bytes. I have lost a few midi files from this bug. Have you struck this issue pre 1.6.1

yes, v1.5.8 is a year old already...

have you tried with a more recent say v1.6.1 ? what is stopping you?

anyway, does it happened with every midi file you thrown into qtractor or just some? care to attach the original file and the corrupted one, if you still can?

EDIT: (scrap that, just noticed this now)

Opening the properties F4 for the clip data selecting the another midi file and exiting Qtractor...

wait a minute! what? are you doing this regularly? that is probably the root cause of your troubles: when changing the file name what your telling is that the new MIDI file will be the one where the current clip data will be stored.

and that is quite IMPORTANT for you to know: you're not importing its contents into the clip whatsoever--you're in fact telling that the new file will get overridden with the current clip data if it gets saved eventually!

please confirm that's been the case (applies to ALL versions, old and new, sorry)

maybe that's the corruption you're talking about: in fact you're using the MIDI clip editor's Properties (F4) dialog all wrong, sorry to tell.

EDIT2: coming v1.6.2 will warn you about this, so keep calm and larry on ;)

hth.
seeya

Hi hth, I found the original problem, the Brass-x.mid file had 4 data events at the same tick in time and the same notes, two events were zero duration and the other two were quarter notes. This caused Qtractor to lockup (100% core use). I am guessing, that I may have merged two clips (in sequence) together in the past ?
I have updated my Ubuntu to 26.04, it now comes with 1.5.11 :-( I will build your 1.6.1 on a rainy day.
Is there a Wiki/Manual explaining the naming convention used in Qtractor, has it seems to have changed over the releases.
Thanks DaveM (NZ).

Hi, qjackctl and qsynth are working fine. Qtractor has a runtime error. I am running xubuntu 2604, but is has QT6 runtime loaded. See attached text file. Any suggestions would be helpful. Thanks for the link, Dave M.

Try the solution in https://linuxmusicians.com/viewtopic.php?p=185039&hilit=qt6ct#p185039

Just for future reference. I wasted an hour looking for the fix for the QT/GTK runtime error. The correct way to fix the Qtractor runtime QT/GTK error is... Install qt6ct "apt install qt6ct". Run the "QT6 Settings" gut tool in Settings. This will show an configuration error "QT_QPA_PLATFORMTHEME=gtk2". Edit with sudo gedit /etc/X11/Xsession.d/56xubuntu-session file. Change the line QT_QPA_PLATFORMTHEME=gtk2 to qt6ct. Save. Reboot as this is a system wide config. Note do not waste time with editing /etc/environment or .profile or .bashrc as the 56xubuntu-session file supersedes your local setup. Thanks for your help. Dave M NZ.

did you also tried the AppImage ?

No.

or instead run qtractor -style Fusion and change the View/Options...

Qtractor did not run at all.

ps. this kind of trouble only happens on Gtk based DEs.

Yes, thats Ubuntu standard release as its either Gnome GTK3 or GTK4 based.

I only offered the above as a reference only, should some non KDE DE user strike this problem.
This is not a battle of "C++/QT6" verses "C/GTK4".
I prefer the light desktop of XFCE as its quick an easy to get around.

Thanks for your support. Qtractor 1.6.2 is working great :-)
Dave M.

Hi, Just a small import bug. Attached is two Kick drum files that won't import into Qtractor 1.6.2.1. These files were created in previous versions of Qtractor. Rosegarden and Muse read the files. DaveM.

hi,

both of these files do not render well since v1.5.12 and most probably they were saved before of this release change in particular:

• Filter out zero-duration note events when importing MIDI files. (qtractor v1.5.12)

fwiw. you may find the hand-corrected files in attachment where each note-off event is displaced by +1 tick and never at the same exact tick as its preceding note-on event (as they were originally).

hth.
byee