Main menu
You are here
Qtractor 0.9.11 - The Mauerfall'30 Release
9 November, 2019 - 19:00 — rncbc
Qtractor 0.9.11 (mauerfall'30) is out!
Qtractor is an audio/MIDI multi-track sequencer application written in C++ with the Qt framework. Target platform is Linux, where the Jack Audio Connection Kit (JACK) for audio and the Advanced Linux Sound Architecture (ALSA) for MIDI are the main infrastructures to evolve as a fairly-featured Linux desktop audio workstation GUI, specially dedicated to the personal home-studio.
http://qtractor.org
https://qtractor.sourceforge.io
http://qtractor.sourceforge.net
https://sourceforge.net/projects/qtractor
https://sourceforge.net/projects/qtractor/files
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
https://sourceforge.net/p/qtractor/wiki/
Qtractor is free, open-source Linux Audio software, distributed under the terms of the GNU General Public License (GPL) version 2 or later.
Hallo!
Not making history or a revolution but as peaceful as thirty years ago ;)
And the change-log goes as follows:
- MIDI Instrument and patch, bank and program names are now correctly updated on their respective track-list (left pane) columns.
- Avoid copying/replicating dirty MIDI clip files, for yet untitled/scratch sessions.
- Transport/Backward commands now honoring edit-tail, loop-end and punch-out points, when playback is not rolling.
- A session name (sub-)directory is now suggested on every new session properties dialog.
- Avoid adding any extraneous clip replica when Ctrl+dragging on either of its edges.
- When using autotools and
./configure --with-qt=..., it is also necessary to adjust thePKG_CONFIG_PATHenvironment variable (after a merge request by plcl aka. Pedro López-Cabanillas, while on qmidinet, thanks). - Fixing a potential crash-effect in switching MIDI output buses on tracks that are set to show audio output monitoring meters, is on going still.
Description:
Website:
https://qtractor.sourceforge.io
http://qtractor.sourceforge.net
Project page:
Downloads:
- source tarball:
qtractor-0.9.11.tar.gz - source package (openSUSE Tumbleweed):
qtractor-0.9.11-51.rncbc.suse.src.rpm - binary package (openSUSE Tumbleweed):
qtractor-0.9.11-51.rncbc.suse.x86_64.rpm - AppImage packages:
qtractor-0.9.11-51.x86_64.AppImage
Git repos:
https://github.com/rncbc/qtractor.git
https://gitlab.com/rncbc/qtractor.git
https://bitbucket.org/rncbc/qtractor.git
Wiki (help wanted!):
- static rendering:
http://qtractor.org/doc
https://qtractor.sourceforge.io/doc
http://qtractor.sourceforge.net/doc - user manual & how-to's:
qtractor-manual-and-howtos.epub
qtractor-manual-and-howtos.pdf
License:
Enjoy && Keep the fun.
Comments
A few requests
Hi,
first of all, I would like to thank you for spending the time creating and maintaning ( I've seen the frequency of the updates) this great application.
I have just changed to QT a few months ago, after having tried all the other midi sequencers available for Linux for quite some time now. They all have pros and cons, but there has been some changes in my workflow and have found QT to be the most appropiate for it.
I make music using a syntheziser and record the midi data to QT with it. I don't draw the notes on the clip (although that would be handy in case the keyboard was not available), but I do open the clip window often to check what I've done, and occasionally, correct mistakes or adjust some notes when not using quantization.
I version 9.10, there was a nice improvement (remembering clip window position) I've been wishing since day one. But although the window state is now saved, I still find myself re-adjusting things like, zoom level, rezising the piano pane, hiding the velocity panel (it shows up everytime the window is re-opened). I have to do this every time the session is opened.
In other words, everything seems to be remembered during the session (except the velocity panel state). But when the session is re-opened, only the clip window state is remembered. Everything else inside that window is reset. I also noticed that the clip window is relocated a few centimeters above the bottom of the screen (where I had placed it). That appears to be exactly on top of where my system task bar would be (I have it hidden to save space).
I wonder if this is the current behavior or if its happening to me only. The correction of this would make the process more enjoyable.
Another thing that I would like to request is the posibility to make all those clip windows settings to apply to all the clips belonging to the same track. Every time a new clip is created, the settings have to be redone and I often find myself replacing a clip with a new recording, or recording different takes.
Making the "escape" key able to close the clip window would be very handy. And lastly, when I changed the shortcut for the "zoom in" function, it only applied for the main window and not for the clip window.
This is it for now. I'll be giving more feedback as I go deeper into the functionality, if you don't mind.
QT has potential and I'm very greatful it exists.
Thanks again!
re. A few requests
hi, thanks for stopping by, you're of course welcome!
...I still find myself re-adjusting things like, zoom level, rezising the piano pane, hiding the velocity panel (it shows up everytime the window is re-opened). I have to do this every time the session is opened...
yes, you're right: only the window position and size are saved on a per clip basis; all other are set application global; however, the left piano keyboard and the bottom velocity panes are both fixed--you can change its size and visibility but they will be always reset to original hard-coded defaults whenever you open the clip editor anytime later... all of these may see the light, say eh... soonish? :)
...the clip window is relocated a few centimeters above the bottom of the screen (where I had placed it)...
this one has more to blame on your desktop environment than to qtractor itself, for which it doesn't know a thing about it to help you in that matter, sorry :)
...make all those clip windows settings to apply to all the clips belonging to the same track...
that would unnecessarily complicate things a bit: let's just keep it all on two levels:
1) application global as is now saved as user preferences;
2) and individual clip level, saved to session file and defaults to the latest current in 1);
besides window position and size, which are already taken care of, the clip editor settings/preferences that we're talking are:
- zoom levels;
- piano keyboard left-pane width;
- velocity/event values bottom-pane height;
[UPDATE] all of the above sneaked in qtractor >= 0.9.11.8git.a3c8f0 :)
...making the "escape" key able to close the clip window would be very handy...
nope. the "Esc" key has an already very specific task on the UI since day one: cancel any floating selection and/or pending editing operation; and that will remain like so, sorry.
...when I changed the shortcut for the "zoom in" function, it only applied for the main window and not for the clip window...
that's because the Main tracks and the MIDI clip editor windows have their own and distinct shortcut set; you may check on their respective Help > Shortcuts... menus; so, if you wish to use the same keyboard shortcut for both you'll just have to set it on both places.
hth.
cheers && thanks
ps. please always try to refer to QTractor by it's full name; while QT is for the software toolkit/framework upon which it's built ;)
"[UPDATE] all of the above
"[UPDATE] all of the above sneaked in qtractor >= 0.9.11.8git.a3c8f0 :)"
Thank you! Looking forward to this!
"that's because the Main tracks and the MIDI clip editor windows have their own and distinct shortcut set"
I had not realized that. So I can now assign a shortcut to close the window :-)
"this one has more to blame on your desktop environment than to qtractor itself, for which it doesn't know a thing about it to help you in that matter, sorry :) "
If I maximized the clip's window and closed the session, next time I start the session, the window shows up maximized (as expected). But if I set the window to cover only half the screen (from the bottom, covering the main window's status bar, to the middle), next time the session is started, the window is still the same size, but the bottom is placed right on top of the main window's status bar, not all the way down. Is this still to do with my desktop environment? if so, any hints of what could be causing this?
Anyway, I appreciate considering my requests and I'm looking forward to try the next update!
Qtractor key features
By the way, other key features that led me to qtractor were the multiple tempo/time signatures, and automatic time-streching.
I can't emphasize how useful thease are to me. When I'm making the mockup during the composition, I tend to use multiple tempos/signatures at different secctions and I also tend to change them often (I have noticed that my perception of tempo is affected by mood or time of day) until I settle on an average of all the changes I've made.
Having qtractor adjust automatically, no only the midi tracks, but the audio tracks, its a super time saver!
I can't tell you the nightmare it was doing this in the previous linux daw I was using. Every time a change in tempo was made, I had to manually adjust all the audio clips by trial an error!
I still have some sessions unfinished because there are some tempo changes I made last time and don't even want to see the mess.
This leads me to another question. How reliable the audio time-streching in qtractor is before the sound starts to deteriorate?
Just in case I'm only using it during the mockups. I don't do the final audio recording until I had settled on a tempo.
I just wanted to mention that. Thanks again!
re. Qtractor key features: automatic time-stretch
hi, thanks for the kind feedback, really appreciated.
- How reliable the audio time-streching in qtractor is before the sound starts to deteriorate?
well, a proverbial it depends applies.
- results might vary, depending on which time-stretching algorithm is in use; fyi. you can opt between the two available: a. native WSOLA time-stretching or b. (lib)RubberBand time-stretching, which is in effect when WSOLA is off.
- in general, it depends on the source audio material or content, whether it's mostly percussive, melodic, monophonic, polyphonic, etc. one algorithm might sound best for one and horribly for another: your ears are always the judge ;)
- time-stretch ratios below 50% (-50%) and above 150% (+50%) are not advisable, unless what you really want is a "metallic", "robotic" or "sci-fi" audio effect instead ;) again, depending to the original material and chosen algorithm, those advisable limits might vary both ways, more or less.
that is as always, YMMV ;)
hth.
cheers && thanks again
Add new comment