You are here

Add new comment

rncbc's picture

re. 1. A faster, more efficient workflow...
...draw a MIDI clip with the mouse, and not have to give it a name in a dialog window
- you can set initial midi clip extents from the edit-head and tail cursors positions (the left and right blue lines).
- the name you're asked when creating a new midi clip is in fact the session name, which is only asked once on a untitled session (or project, or song, w/e you may call it).
- when merging, you're asked for midi file-name (and/or path), which is to hold the merged data, again not quite the name of the merge clip; yes, there's room for some default file-naming here, as is in fact already suggested by the file-name that appears on the file requester dialog--this must to be guaranteed to be a brand new file-name, so that it doesn't replace any existing one.

(perhaps just a generic name, which I could re-name later if I need to). The same applies to the dialog for merging clips, I think it should just be given a generic default name and not show a dialog window. Also, I feel it's preferable to be able to loop a MIDI item most of the time, rather than having to create many copies of it.

re. 2. A more detailed user manual.
...I'd be happy to contribute
- double thanks then :)

re. 3/4. plugins and ubuntu support
...plugins in /usr/lib/vst, /usr/lib/ladspa, etc...
- and that is the case on qtractor too. that is, the default plugin search paths are as follows:

LADSPA
/usr/local/lib/ladspa, /usr/lib/ladspa (32bit systems)
/usr/local/lib64/ladspa, /usr/lib64/ladspa (64bit systems)
DSSI
/usr/local/lib/dssi, /usr/lib/dssi (32bit systems)
/usr/local/lib64/dssi, /usr/lib64/dssi (64bit systems)
VST
/usr/local/lib/vst, /usr/lib/vst (32bit systems)
/usr/local/lib64/vst, /usr/lib64/vst (64bit systems)
LV2
/usr/local/lib/lv2, /usr/lib/lv2 (32bit systems)
/usr/local/lib64/lv2, /usr/lib64/lv2 (64bit systems)

hth.
cheers