rncbc / qtractor Goto Github PK

Qtractor 0.8.5, helm 0.9

On a MIDI track, loading Helm LV2 in Qtractor works as expected.

Trying to load helm-VST in Qtractor, and the Helm windows is kind of flickering (it does look that Helm's GUI is switching endlessly between the different presets), then Qtractor's CPU usage is rising up quickly above 100%, then Qtractor is staying frozen-ish for around a minute, Helm's GUI look to become stable (CPU is still over 100%), and eventually, it crashes.

Note that strangely, if I relaunch then Qtractor and try to add Helm to a MIDI track, then there is a second "Helm" in the plugin box:

(I've relaunched 4 times)

Note that even more strangely, if I do a re-scan, the extra Helm-VST lines disappear.

Hope that makes more sense for you than it does for me!

Hi,

All the keyboards I use have a volume control. As soon as I do a move on this controller, qtractor displays this in the left part of the statusbar. Other controllers e.g Pitch-Bend don't show the events.

Problems (at least on weak machines):

• When I do a quick slide, the events take 2-3 seconds to be performed. It takes about this time to stop the statusbar 'spamming'.
• It seems that this statusbar display 'eats' a significant part of CPU cycles: I saw 5-10%. Moving other controllers not displayed in statusbar don't show additional processor load.

Is this a bug or a feature? If feature: Can I disable it somewhere?

Hello.
Sorry for giving you a strange request, I'm just not quite sure what I'm asking for.
Here's the story:

As I'm trying out the new version of u-he Repro, Qtractor gives me a grey, blank window intead of the GUI. You can see my report here:
https://www.kvraudio.com/forum/viewtopic.php?f=31&t=424953&p=6968241#p6968241

When reporting this to the u-he developer, they replied the following:
"You could bug report to QTractor that it needs to call effIdle() from the main thread, maybe at 60 fps? :-)"

Not being a developer or too techy, I'm not sure what that means. But at least now I told you.
Is this anything you can help with, or do you perhaps have good reasons for making it how it is?

One of my pain-points with qtractor is working with cross-fading clips that overlap. If I have two clips that overlap (say, from a punch-in), and I want to smoothly crossfade between them, here's what I have to do:

• Slide the later clip's start-point out of the way, so I can work with the first clip
• Adjust the fade-out on the first clip
• Slide the second clip back to overlap with the first, and then set it's fade-in

Repeating this process over and over to find the right crossfade point is frustrating, because the fade-in curve on the second clip gets wiped out every time I slide it out of the way.

Suggestions to improve this:

• An "auto crossfade" feature that will automatically create a crossfade two overlapping clips
• Or, a "one-click" crossfade feature, that will create a crossfade between two selected clips
• Ideally, some kind of tool to adjust the overlap, cut-point, and fade curves of two clips without having to fuss individually with it.

Thanks for your consideration!

Qtractor 0.7.8, stegosaurus from https://github.com/thunderox/stegosaurus

Hi,
Trying to load stegosaurus in Qtractor on a MIDI track, Qtractor crashes. Qtractor launched from a CLI, it tells "segfault", nothing more.
If that can helps, please note that the same stegosaurus works fine with jalv.gtk, jalv.select and Ardour 5.3

Tell me if you'd need more info.

Hope that helps

When using a midi track with synth plug-in (helm lv2 in this case) changing the volume fader does not change to output volume of the track.
Don't know if this is intended behaviour or plug-in specific.

Latest qtractor

dpkg -l | grep qtractor
ii qtractor 2:0.7.3-1kxstudio1 amd64 MIDI/Audio multi-track sequencer application
ii qtractor-dbg 2:0.7.3-1kxstudio1 amd64 Debugging symbols for Qtractor

Audio tracks are fine

Hi Rui, going forward based on your info from #106 I tried mapping //Edit/Track/Navigate/Previous and //Edit/Track/Navigate/Next to two different midi CCs (CC 14 and 15 to be precise).
I noticed that the following two cases don't really work:

• A value of 0 doesn't result in an action.
• A value of 127 only works once, the next time it's sent nothing happens.

Any value in the range 1-126 (including 126) does work.

Is this correct behavior? A value of 0 resulting in no action might be intended, but 127 only working once doesn't seem correct to me.

I found a similar issue to
#71

but this time its for sending an atom sequence to the UI from the plugin, into the port_event callback.

Again I think the behavior is best illustrated with a test plugin:
https://github.com/jmage619/test_atom.lv2

When activated, my test is simulating how my work-in-progress sampler updates the UI for each wav "zone" that is loaded from reading a patch. I send the UI a bunch of meta info, such as start, end time, loop points, wav path, etc, so each zone has an atom sent over to tell the gui to fill a row with the relevant controls.

Note that the test sends 42 atoms (here just strings for simplicity), each is 472 bytes. It looks like my notify port size is 20480 in qtractor, and the total sequence built is 20176, so there should be enough space to hold them all.

However on the receiving end the UI only receives 2 atoms. 472 * 3 is greater than 1024, so I suspect maybe a 1k ring buffer is somewhere in between? If that's the case, wouldn't it make sense to make this large enough to hold the full 20k bytes available in the control port?

I do plan to significantly reduce the 472 atom sizes, I was playing around with just passing a pointer inside an atom long. But in any case it looks like there's an unexpected 1k limit somewhere here preventing the full 20k bytes of control port from being passed to the UI.

Below is a sample output of a run.

UI: ui instantiate called
plugin activated!
PLUGIN: get zones received!!
PLUGIN: notify capacity: 20480
PLUGIN: sent addZone 0; obj size: 472
PLUGIN: sent addZone 1; obj size: 472
PLUGIN: sent addZone 2; obj size: 472
PLUGIN: sent addZone 3; obj size: 472
PLUGIN: sent addZone 4; obj size: 472
PLUGIN: sent addZone 5; obj size: 472
PLUGIN: sent addZone 6; obj size: 472
PLUGIN: sent addZone 7; obj size: 472
PLUGIN: sent addZone 8; obj size: 472
PLUGIN: sent addZone 9; obj size: 472
PLUGIN: sent addZone 10; obj size: 472
PLUGIN: sent addZone 11; obj size: 472
PLUGIN: sent addZone 12; obj size: 472
PLUGIN: sent addZone 13; obj size: 472
PLUGIN: sent addZone 14; obj size: 472
PLUGIN: sent addZone 15; obj size: 472
PLUGIN: sent addZone 16; obj size: 472
PLUGIN: sent addZone 17; obj size: 472
PLUGIN: sent addZone 18; obj size: 472
PLUGIN: sent addZone 19; obj size: 472
PLUGIN: sent addZone 20; obj size: 472
PLUGIN: sent addZone 21; obj size: 472
PLUGIN: sent addZone 22; obj size: 472
PLUGIN: sent addZone 23; obj size: 472
PLUGIN: sent addZone 24; obj size: 472
PLUGIN: sent addZone 25; obj size: 472
PLUGIN: sent addZone 26; obj size: 472
PLUGIN: sent addZone 27; obj size: 472
PLUGIN: sent addZone 28; obj size: 472
PLUGIN: sent addZone 29; obj size: 472
PLUGIN: sent addZone 30; obj size: 472
PLUGIN: sent addZone 31; obj size: 472
PLUGIN: sent addZone 32; obj size: 472
PLUGIN: sent addZone 33; obj size: 472
PLUGIN: sent addZone 34; obj size: 472
PLUGIN: sent addZone 35; obj size: 472
PLUGIN: sent addZone 36; obj size: 472
PLUGIN: sent addZone 37; obj size: 472
PLUGIN: sent addZone 38; obj size: 472
PLUGIN: sent addZone 39; obj size: 472
PLUGIN: sent addZone 40; obj size: 472
PLUGIN: sent addZone 41; obj size: 472
PLUGIN: total seq size: 20176
UI: received add zone!! zone 0
UI: received add zone!! zone 1

Hello,
this issue occurs for me under ubuntu 16.04, after installing qtractor 0.8.6 via "apt-get", and also after compiling from source both versions 0.8.5 and 0.8.6.

this are the steps to take to reproduce the issue:

• open qtractor (via terminal or via launcher)
• change any option (example: maximum number of recent files)
• close qtactor
• reopen qtractor, the options keep no trace of the changes made

If I then open qtractor from terminal as super user and change any option, then the changes are saved and I see them properly changed also opening qtractor without sudo.

The options configuration file is in ~/.config/rncbc.org/Qtractor.conf
Since I thought it could be a permission issue, I changed the file permission to 777 just to try, and nothing changed.
I tried even chowning it to the user running qtractor, but again nothing changed.

Thanks for your help

Hello Rui,

A small display issue to report:

Qtractor git (Version: 0.8.0.69git.e8b1d5).
qt5.8.0
Fluxbox
Arch Linux 64
Guitarix git

A double window pop up when opening the plugin GUI. That seems to happen mostly with GxAmplifier-X. Doesn't happen in Ardour, or apparently in Qtractor 0.7.9.

The issue was reported to Guitarix devs below:
http://guitarix.sourceforge.net/forum/viewtopic.php?f=6&t=4803

BR,

LX

Hi,
Just wondering if anyone have tried this plugin?
I have created .vst folder and added it to Qtractor VST plugin list, but it won't show up, (glibc 2.24). I have tested successfully other vst's.
If there is anything I can do, let me know.
Thank you for this nice sequencer!

when i open the inputs or outputs window from the shortcut editor, the midi connections window is drawn below the current window and cannot be used. switching to the midi connections window isn't possible because focus returns to the shortcuts/midi window.

Dear Rui,

I understand loop based sequencing may not be a high priority (as with other linear DAWs - fair enough), but wouldn't it be possible to improve a bit the looping control to make it more "pattern like"?
I'm thinking here about moving the loop section on the fly while playing with keyboard shortcuts / midi cc.
Something like "Shift current loop section's next start point forward/backward by X beats", and once the play head reach that start, move the loop end marker accordingly and continue looping without disruption. Or one step further: define several loop boundaries and bind them to keyboard shortcuts / midi and jump there on the next loop occurence.

The only implementation examples I am aware of who do that well are trackers: Renoise & Buzz for example. I hope this makes kind of sense, and apologies if the feature was already dismissed - I didn't find it mentioned anywhere.

By renaming your README into README.md you can switch markdown -> formatted HTML on. That looks much nicer. (Currently only the unformatted text is visible in github and gitlab.)

I can reproducibly crash Qtractor from git by loading my SpectMorph plugin and generating lots of UI changes with the mouse (using the 2x2 grid template). I debugged the problem, and the crash is
caused by the function qtractorLv2Worker::schedule, which in the original implementation uses:

::jack_ringbuffer_write(m_pRequests, (const char *) &size, sizeof(size));
::jack_ringbuffer_write(m_pRequests, (const char *) data, size);

to write the request. Now the case that triggers the crash is that the first ringbuffer_write is executed, and then the request is read by the worker thread. Since data isn't yet written, the worker thread executes an incomplete request, which in turn causes a crash in the SpectMorph plugin. I know it sounds like an unlikely thing to happen, but I can trigger it reproducibly in a short amount of time.

My fix is to copy the data into one consecutive chunk of data, and writing that with one single ringbuffer_write. Patch attached.

Cu... Stefan
lv2workerfix.diff.txt

Sorry again me but..:

I do:

• create or import a MIDI drum track
• set a loop of e.g 4 beat
• play the loop (for me this is more fun than playing with an annoying click)
• start jamming on another track with MIDI keyboard (monitor)

With this I see the notes played right before loop-rewind (seems like last bar) are eaten up / kept unheard.

Duplicating an audio track that is armed for recording seems to confuse the R button on the duplicated track.

Steps to reproduce:

1. Create an audio track
2. Arm it for recording
3. Duplicate the track
4. The duplicated track does not appear to be armed for recording, however, if you then begin recording a clip will be recorded on the ducplicated track.
5. If you click the arm button, it appears to light up but now the track is actually disarmed for recording.
6. To "unconfuse" the button you have to disarm again and re-arm.

Seeing this on 0.7.8 on Antergos with GNOME 3.20, though it may have been around before that.

I compile qtractor from master branch on fedora 23 64 bits.
It's not possible to desactivate the VST support.
I added the following flags to configure: --disable-vst --disable-vestige
I have the following sum-up:
X11 Unique/Single instance . . . . . . . . . . . .: no
VeSTige header support . . . . . . . . . . . . . .: no
Gradient eye-candy . . . . . . . . . . . . . . . .: yes
Debugger stack-trace (gdb) . . . . . . . . . . . .: yes

But when I compile qtractor:

d src/ && ( test -e Makefile.qtractor_vst_scan || /usr/lib64/qt5/bin/qmake /home/collette/repositories/qtractor/src/qtractor_vst_scan.pro -o Makefile.qtractor_vst_scan ) && make -f Makefile.qtractor_vst_scan
make[2]: Entering directory '/home/collette/repositories/qtractor/src'
g++ -c -pipe -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic -O2 -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG -DQT_CORE_LIB -I. -isystem /usr/include/qt5 -isystem /usr/include/qt5/QtCore -I. -I/usr/lib64/qt5/mkspecs/linux-g++ -o qtractor_vst_scan.o qtractor_vst_scan.cpp
qtractor_vst_scan.cpp:37:22: erreur fatale: aeffectx.h : Aucun fichier ou dossier de ce type
compilation terminée.

This feature is not a very big deal, but I have still been wanting it a number of times.
The idea is this:

When double clicking a clip on the timeline, you get quite a few possibilities, like stretching, pitch shifting and gain control. I think it would be really handy if you could also get the option of panning. That way you could easily make simple stereo effects without automation. Or even have two clips on the same track with the same plugins, but hear one of them to the left and the other one to the right.

It would also make a difference in chronology: When panning the track, the panning comes last in the mix chain. If you could pan the clip in itself, then the panning would come first, and the plugins would still be in normal stereo mode.

To avoid any doubt: Oh, yes I do love Qtractor without this feature aswell.

Tested with seq64. The rate of play in Qtractor changes, but not the bpm number.

Hi,

I'm in the process of developing a qt based lv2 sampler, and have come across an unexpected behavior in qtractor. I am scheduling workers to load each wav file. However if I schedule more than just 2 or 3 workers, for some reason only the first few fire off and then it just stops scheduling more.

My sampler code is really large at this point and it's not public yet, but I have written a really simple lv2 plugin that I can reproduce this issue with:
https://github.com/jmage619/test_work.lv2

This test plugin simply spawns 10 workers each time it is activated, and prints info of the workers to stderr, so I see the messages in the qtractor message window.

Unfortunately the behavior is not consistent. Sometimes I have to de-activate and activate the plugin ~50 times before I see it fail to schedule the workers, other times it happens within the first few times after loading.

I do not experience this behavior in ardour, but qtractor is my target DAW since it's what I prefer. I first noticed this in the current version of qtractor 0.8.0 in fedora 24, and I also built qtractor from source, but the issue still exists on the current master.

Please let me know if you would like any more details.

Thanks!
Jeff

Recent Qtractor from git, song with MIDI and audio tracks loaded
(Qtractor does this for a long time yet)

1. Place the song pointer on a position

2. Press SPACE to start playing

3. Press SPACE to stop playing

4. Place the song pointer back

5. Press SPACE to start playing
   -> Everything is fine

6. Place the song pointer on a position

7. Press SPACE to start playing

8. Don't press SPACE to stop playing

9. Place the song pointer back while Qtractor is playing
   -> Some audio clips are played early, not only some milliseconds but totally out of sync, even with small jackd buffer sizes. Stopping/starting Qtractor cures the problem.

It seems that placing the song pointer (I use middle click) while Qtractor is playing doesn't do the same thing (loading audio buffers?) as stopping the song, placing the song pointer and starting it.

Like with ardour: add an instrument track.
A track which take as input MIDI events and produce real audio.
It's an hybrid between qtractor audio track and qtractor midi track.
The problem with the midi track is that if the plugin doesn't react to the MIDI messages send by the MIDI mixer strip, then the volume is not controled.
With the instrument mixer strip, the plugin will produce audio and the mixer strip will control directly the audio output of the plugin and not via midi messages.

As a very passionate and grateful Qtractor user, there are a couple of issues I tend to stumble upon when working in Qtractor. Two of these occur when automating.

1/ Say I'm using the same plugin for multiple tracks (for example a Calf Filter for a bass track and another Calf Filter for an organ track), and I'm automating these to sound as good as possible. Sometimes (not always, but also not seldom) after reopening the project, one of the automations have copied the other. So one Calf Filter automation is gone, or rather is exactly like the other one. If I then automate it once again to make it sound good, it will most likely (actually I think "always" is more correct) go back to be a copy of the other automation after reopening the project.

For a while I suspected this would only happen if I dragged the plugin from the one track to the other, simply copying it, but it happens also when adding a new instance.

This can be a bit frustrating and eat up a lot of time. Especially when it happens to multiple plugins in the same project - when you have to re-adjust a filter here, a reverb there and then check that the other plugins aren't out of place.

2/ A newer issue (at least for me) is that automation values have suddenly adjusted themselves when reopening a project. If I set a gain value to 1,4, I reopen and find it to be something like 1,382. They seem to always adjust just a tad down, so it rarely does any harm. Still, there was a reason I put it to 1,4 in the first place.
I have the high resolution plugin automation enabled, I don't know if that has anything to do with this.

These are just a couple of small things, but they still make me spend quite a lot of extra time simply adjusting automations I've already adjusted.

But to clear all doubts: Qtractor is still my favourite. <3

Qtractor hard crashes when I add a plugin that (apparently) wants to render it's UI using GTK. When enabling debugging I get the following error message:

suil error: Unable to open wrap module /usr/lib64/suil-0/libsuil_gtk2_in_qt4.so (/usr/lib64/suil-0/libsuil_gtk2_in_qt4.so: cannot open shared object file: No such file or directory)

This is easily solved by compiling suil with gtk support, but I do think that Qtractor shouldn't crash when it can't find a lib. Is there a way to prevent this?

Also, there seem to be some checks to prevent these situations in configure.ac but these seem to explicitly only check when not using Qt4. That might be an error?
(For reference: I'm running a Qt4 build)

Hi

have been busy setting up hardware and am still [1] but fun moments increase: Jam around. Doing so there is a thing that - ehh is not that - lets say - could be improved and maybe there is some time where there are some spare cycles left for (watch out here comes yet another wishlist):

• add keyboard shortcuts for all track movements e.g Ctrl (or Alt have no idea what others do here) + Arrow Up for moving track up.
• if no clip is selected in it: why not delete current track by pressing 'Del'?
• guess this is more effort: How about moving track up and down by drag 'n drop (if there is something planned about selecting multiple tracks - I'd prefer 'Shift)?

[1] https://drive.google.com/drive/folders/1VUMqcRO8WxWpwMKYy06WZPZcSgrokq0h?usp=sharing

• Create a MIDI track
• Insert a synth plugin, e.g. Dexed or Linuxsampler and configure it
• Connect your MIDI keyboard and click on the track so you can play notes
• Place an MIDI INSERT before the synth plugin, don't connect SEND or RETURN
• Play some notes

In less than a minute I get hanging notes and strange effects like playing notes when I release(!) a key.

A fresh install doesn't do so but only look in /usr/lib/vst . One can go to View->Options->Plugins and add the /usr/lib/lxvst path. And then, Qtractor will look into it, but no more in /usr/lib/vst which can be confusing for a end-used when rescanning.

A suggestion would be for Qtractor to use the 2 environment PATH variables: LXVST_PATH and VST_PATH as a default which the distro and/or sys-admin is supposed to fit with what's relevant. In my case, I've:

LXVST_PATH=/usr/local/lib/lxvst:/usr/lib/lxvst:/home/my_user/.lxvst
VST_PATH=/home/my_user/.vst:/usr/lib/vst:/usr/local/lib/vst

This could removes non-user-friendly ambiguities with PATH and get them straight to make music.

HTH

i would like to do a request for a button that toggles yes or no for JackTransport setting.

We have set Qtractor JackTransport to "FULL", because we sync the computer that is running QTractor to another computer (the Master), using JackTransport.
Having a button would give quick access to the mode where one can do some work privately or get connected to the other computer.

The setting to Slave, Master or Full can already have been (F12) - the button chooses None or Slave/ Master/Full.

Hi,

When importing a MIDI file, the tempo suggested by the file is overwritten by default tempo. On PC (fast) the effect is not visible but on RaspberryPi (slow) the imported tempo is displayed for a short while in toolbar(<1s) and then overwritten by the tempo set before in the session.

Here is the update of the french translation file.

qtractor_fr.zip

qtractor could be a open source alterative to Adobe Audition you just need to add a Waveform Editor like this

auto heal
https://www.youtube.com/watch?v=dPkEjEu_8I4
declicker
https://www.youtube.com/watch?v=ajo40QvcfI0

https://helpx.adobe.com/audition/using/displaying-audio-waveform-editor.html
I don't know why I want to help being I can't use it.

There's probably nothing new in wanting subgroups in Qtractor.
I also know Qtractor is a proud, intuitive sequencer, not a bloated DAW.

Nevertheless I often dream of sub-grouping when working in Qtractor.
Here's what my dream looks like:

1/ I right click on a track, let's say Track 1.
2/ Up comes the menu, I hover to the option "Link track", and on the submenu I choose which track to link it with. Let's say Track 4.
3/ As I press the mouse button, a window pops up, wanting me to name this group. And to choose outputs, maybe add some more tracks to the input. I add Track 3 and name the group "Chords". Then I press ok.
4/ Suddenly I have a new track in my working space. It's not a midi track, it's not an audio track, it's the group track! And this one is called Chords. Track 1, 3 and 4 are even automatically routed through this group track, where I can add plugins and automation just like in any track.

Well, I'm not expecting this dream to come true. But from a user point of view, I do think it's a good suggestion.

Is it possible to connect MIDI to audio filters, that are accepts MIDI input (vocoders, MIDI controlled filters) in qtractor? If not, that would be a great improvement.

can the Time line, that starts at "1", get an offset option?

This would allow the time line to start for example with "0".
In our case, this would correspond to "0" set on JackTransport.

With a tempo and beat setting of 30 4/32, the playback head AND the JackTransport would show the same number - much less confusion there :)

Hi Rui, I've been trying to open the beatslash-lv2 plugins in Qtractor 0.8.5 today and it makes Qtractor to crash (segfault) after loading the beatslash GUI.
Guestimate is that BeatSlash are CV compatibles but Qtractor doesn't handle that.

Would that then be possible to avoid such plugins (CV controled) to load up then makes Qtractor to crash? It would be much more user-friendly than the actual loading up + crash.

Here are some minor "inconveniences" I spotted while browsing the web site. Those are small, so I don't think it is worth to open separate issues:

• The description to access the Git repository seems to point to an old URL. Correct URL: git clone https://sourceforge.net/p/qtractor/code (please check)
• Can you please set the background colour of highlighted text to either some lighter grey or remove the shadow? It becomes unreadable:
  

Keep up the great work and thanks in advance!

I use qtractor from git repo on fedora 23.
I loaded the fabla plugin on a track. When I open the gui, the fabla presets are not found.
I loaded the same plugin on ardour and here, it works fine.

Qtractor for win mac

I've got the newest qtractor running on a Debian Jessie system and an Arch Linux system. In both cases, if I have a large set of tracks (so that I have to scroll down to see the bottom one), and I'm scrolled to the bottom, qtractor will scroll up whenever I move the playhead. It doesn't matter if I move it with the backspace key or by dragging the red bar with the mouse.

Hi Rui,

I have a small feature request. Whilst I can already navigate between tracks using the arrow keys on my keyboard I was wondering if that action can be added to the shortcut menu.
I'm asking this for two reasons:

• The up/down arrows only work once you've first selected a track. When no track is selected they scroll the track widget. If one has dedicated buttons mapped to next/previous track they will always work.
• I'd like to use my MIDI controller to navigate between tracks and the shortcut menu allows one to map any command to a MIDI message (which is awesome btw!)

What do you think?

When triggering a track or global action with an MMC Controller (MIDI device) there is no feedback being sent to the controller. Feedback is only sent when the action is triggered within Qtractor itself for example by clicking in the UI. This means there's no feedback loop to the controller so the controller cannot correctly show Qtractor's state.

This seems to be caused because qtractorMainForm::midiMmcNotify which is used to handle incoming MMC messages calls qtractorMainForm::setTrack which then calls pTrack->set<action>(bOn). None of these includes any MMC feedback.
Compared to pressing a button, which is handled by qtractorTrackStateCommand::redo which calls pTrack->set<action>(bOn) directly but also includes code to send feedback to an MMC controller.

Any idea how this could/should be fixed?

...
checking jack/metadata.h usability... yes
checking jack/metadata.h presence... yes
checking for jack/metadata.h... yes
checking for system... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating qtractor.spec
config.status: creating src/src.pri
config.status: error: cannot find input file: `src/qtractor_vst_scan.pri.in'

When using plugins with lots of presets (for instance TAL NoizeMaker) or lots of automation possibilities (for instance U-he's Zebra2), the list of options continue outside of my screen.
Especially when using a small computer.
And as far as I can see, I have no way of accessing the part of the list that's on the right side of my screen. Well, with the cursors I can actually access the presets or automation settings, but I cannot see which one I'm accessing.

So a feature request would be a way of scrolling further when the screen is full.

Was this possible to understand?

While working on 'magic' MIDI import dialog I saw a possible source of qtractor crashing with segfault. Consider this:

1. Open 'Add track'
2. Select 'MIDI': That calls qtractorPluginList::setChannels several times and finally with channels = 2 / iFlags = qtractorPluginList::MidiTrack. That creates by qtractorMidiManager::createMidiManager which adds a newly created MidiManager to the session by calling qtractorSession::addMidiManager.
3. Cancel Dialog and confirm to discard changes. The track is deleted which deletes PluginList which calls qtractorPluginList::setChannels(0,0). The MidiManager is removed by qtractorSession::removeMidiManager and then deleted.

Problem: In qtractorAudioEngine::process which is called by Jack's worker thread the MidiManagers are iterated (qTractorAudioEngine.cpp line 923). If this done while changing list (2./3.) the list might be in unfinished condition -> boom. Seems to me MidiManager-list has to be made thread safe...

I get this when I try to run configure:

./configure: line 5156: syntax error near unexpected token JACK,' ./configure: line 5156: PKG_CHECK_MODULES(JACK, jack >= 0.100.0, ac_libjack="yes", ac_libjack="no")'

I generated the configure file with autoconf:

x@x:~$ autoconf --version
autoconf (GNU Autoconf) 2.69

x@x:~$ qjackctl --version
Qt: 5.5.1
QjackCtl: 0.4.2

x@x:~$ jack --version
This is jack 3.1.1 (C)2004 Arne Zellentin [email protected]

Any ideas?

Qtractor periodically starts playing back clips at the wrong time.

This has happened to me on many versions of qtractor, on different operating systems with different audio hardware.

It tends to happen more when I have a more audio tracks with more edits.

It doesn't seem to happen when I play a track from the beginning, only when I play it from somewhere in the middle of the song.

It doesn't happen consistently. I can't reliably reproduce the problem, it just happens randomly.

I have noticed that when a clip gets "dislocated" like this, it will continue to be so even if I start and stop the track. The only was to "relocate" the clip is the manually reposition the playback cursor. Then things playback correctly.

It seems like generally the clips are playing back earlier than they should.

Sorry that this is a fairly vague bug report.

[...]
checking for qmake-qt5... /usr/bin/qmake-qt5
checking for qmake... /usr/x86_64-pc-linux-gnu/lib/qt5/bin/qmake
checking for Qt library version >= 5.1... no; Qt 5.1 or greater is required

Error:
  * In program cave perform install --hooks --managed-output --output-exclusivity with-others =media-sound/qtractor-0.7.8:0::media --destination installed --x-of-y 4 of 4:
  * When installing 'media-sound/qtractor-0.7.8:0::media':
  * When running an ebuild command on 'media-sound/qtractor-0.7.8:0::media':
  * Install failed for 'media-sound/qtractor-0.7.8:0::media' (paludis::ActionFailedError)
[...]

# qmake-qt5 --version
QMake version 3.0
Using Qt version 5.7.0 in /usr/x86_64-pc-linux-gnu/lib

I had to add

export CXXFLAGS="${CXXFLAGS} -std=c++11"

to our build script to allow qtractor-0.7.8 to successfully configure/compile with Qt 5.7.0.

The midi "vu meter" don't represent the actual volume of the audio coming from the plugin.
Would be a great help with mixing.