16 Feb
2008
16 Feb
'08
9:56 a.m.
Hi LAUs,
After some time in quarantine, meaning that it just passed almost 40
days since its last public appearance, the frivolous debutante has
matured a bit but not that much. Truth is, it is not quite healed and in
fact, it is getting seriously bloated ;)
Qtractor 0.1.1 (futile duchess) has been released!
Qtractor is an Audio/MIDI multi-track sequencer application, written in
C++ around the Qt toolkit. Its primordial 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 Desktop Audio/MIDI Workstation GUI specially
dedicated to the personal homestudio. It sits confortably tagged as for
the techno-boy bedroom home-studio. There's no genre segregation here,
it also applies to techno-girls ;).
Now seriously, it even has its own Wikipedia entry already:
http://en.wikipedia.org/wiki/Qtractor.
Back to business, these are the major highlights for this release:
- Draft user manual, contributed by James Laco Hines.
- Native Linux VST plug-in support.
- Initial DSSI plug-in support (audio effects only atm.)
- User configurable keyboard shortcuts.
- JACK server auto-start.
- Clip fade-in/out relative resizes.
- Auto time-stretch now optional.
- MIDI capture/record input quantize.
- Major plug-in infrastructure rewrite.
- Seamless plug-in drag-and-drop.
Check it out, from the official project web site:
http://qtractor.sourceforge.net
http://sourceforge.net/projects/qtractor
Direct link for the source tarball download:
http://downloads.sourceforge.net/qtractor/qtractor-0.1.1.tar.gz
The new user manual draft is also made available:
http://downloads.sourceforge.net/qtractor/qtractor-0.1.1-user-manual.pdf
Literal change-log follows. since the last 0.1.0 (frivolous debutante)
alpha release:
- After some great user demand, keyboard shortcuts are finally
configurable, as found provisionally under Help/Shortcuts...,
for the main application menu and for the MIDI editor as well.
- Debian package gets SSE optimization disabled as default.
- At least some transport actions get to be non auto-repeatable
when pressed for much too long, as Play and Record, avoiding
the tumbling imposed from the keyboard.
- For the first time ever, jackd auto-start is now allowed (!).
- OSC service support through liblo gets optional at configure
time, now leading the way to proper DSSI plug-in hosting.
- All plug-in widget controls count are now capped to one hundred.
- Plugin paths setup is now made available on the options dialog,
overriding each of respective default settings, as implicit from
the LADSPA_PATH, DSSI_PATH and VST_PATH environment variables
(see View/Options.../Display/Plugin Paths).
- Clip fade-in/out lengths are now kept relative to tempo changes
and also to clip offset and length changes (clip resizes).
- Automatic time-stretching for all audio clips when session tempo
changes, may now be disabled/enabled as a global session option
(see View/Options.../Audio/Playback/Automatic time-stretching).
- Double-clicking on an empty area (de)selects all clips on track.
- MIDI capture (record) quantization is now an option, possibly
handy for some jerky performance musicians, as the one found
in myself ;) (see View/Options.../MIDI/Capture/Quantize).
- The global options dialog (View/Options...) has seen its Display
tab page being moved back and to the right.
- Major rewrite of the plug-in infrastructure, adding primordial
support for DSSI and native VST plug-in flavors.
- Drag-and-drop of plug-in instances are now allowed intra- and
inter-mixer strip chains, either on tracks or buses.
- Turning track record off while recording is rolling was leaving
the session in a inconsistent recording status, now fixed.
- A random but instant crash upon audition/pre-listening player
onset was hopefully fixed.
Cheers && Enjoy
--
rncbc aka Rui Nuno Capela
16 Feb
16 Feb
2:57 p.m.
On Sat, Feb 16, 2008 at 02:56:18PM +0000, Rui Nuno Capela wrote:
Hi LAUs,
After some time in quarantine, meaning that it just passed almost 40
days since its last public appearance, the frivolous debutante has
matured a bit but not that much. Truth is, it is not quite healed and in
fact, it is getting seriously bloated ;)
Qtractor 0.1.1 (futile duchess) has been released!
Great work! I am really looking forward to the time when vsti and
dssi instruments will be implemented!
Regarding the vst compiling, could you not use the free and open
source headers from Javier Serrano Polo used by dssi-vst and
lmms?
James
5:32 p.m.
James Stone wrote:
On Sat, Feb 16, 2008 at 02:56:18PM +0000, Rui Nuno
Capela wrote:
yep, dssi and vsti support (either native linux or windows through
dssi-vst) will come soon. i am working on it and still have some
low-level design decisions to make, specially regarding a seamless
integration of midi driven plug-ins. you know, with vst there's also the
possibility of midi plug-in effects ...
Hi LAUs,
After some time in quarantine, meaning that it just passed almost 40
days since its last public appearance, the frivolous debutante has
matured a bit but not that much. Truth is, it is not quite healed and in
fact, it is getting seriously bloated ;)
Qtractor 0.1.1 (futile duchess) has been released!
Great work! I am really looking forward to the time when vsti and
dssi instruments will be implemented!
Regarding the vst compiling, could you not use the
free and open
source headers from Javier Serrano Polo used by dssi-vst and
lmms?
this has been already asked and answered elsewhere... here:
http://www.rncbc.org/drupal/node/66#comment-1649
bottom line seems to be that the vst-sdk support that are now being
required for qtractor is for _native_ linux vst plug-ins and not for
win32 dlls linked trough wine as is what dssi-vst does
otoh, qtractor does have now this dssi interface, so you can have
windows vst support by proxy though dssi-vst and thus wine too. got that?
cheers
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
18 Feb
18 Feb
8:49 a.m.
On 16/02/2008, Rui Nuno Capela <rncbc(a)rncbc.org> wrote:
James Stone wrote:
I see the "asked" part on that page, but I don't entirely see the
"answered".
If your only requirement is to be able to include aeffect.h and
aeffectx.h, you should just be able to drop in the "vestige" headers
from LMMS or dssi-vst. Doesn't matter whether it's intended to
support Win32 or native Linux plugins. You won't get support for
everything in VST, but a redistributable binary that supports much of
it has got to be worthwhile, surely.
The author claimed in LMMS list postings that these headers were
reverse engineered from working VST host and plugin code without
seeing the original SDK or accepting the Steinberg SDK license.
Obviously I cannot know whether that is really the case, but judging
from the code, I think it is plausible. Until anyone produces any
evidence otherwise, I for one would be happy to give it the benefit of
the doubt.
Chris
Regarding the vst compiling, could you not use
the free and open
source headers from Javier Serrano Polo used by dssi-vst and
lmms?
this has been already asked and answered elsewhere... here:
http://www.rncbc.org/drupal/node/66#comment-1649
bottom line seems to be that the vst-sdk support that are now being
required for qtractor is for _native_ linux vst plug-ins and not for
win32 dlls linked trough wine as is what dssi-vst does
9:41 a.m.
hi Chris,
On Mon, February 18, 2008 13:49, Chris Cannam wrote:
On 16/02/2008, Rui Nuno Capela <rncbc(a)rncbc.org>
wrote:
simple as it could ever be: it does not build with the vestige headers
alone. there are somethings missing. i know that it would suffice to
copy-and-paste those things from the original steinberg headers, but...
you know, i just can't, nor have the skill, to do that with my eyes shut
;)
eheh
now seriously, the native linux vst support is still a grey area.
energyxt2 is to blame to have started it all in first place. then come
jost from jucetice, which pretty awesome pice of work. now it's renoise.
only jost has the nerve to be open-source, though, yeah.
why did i got that in qtractor too? i'll give you three reasons: fun, fun
and fun. :D sorry, just can't help it
cheers
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
James Stone wrote:
I see the "asked" part on that page, but I don't entirely see the
"answered".
If your only requirement is to be able to include aeffect.h and
aeffectx.h, you should just be able to drop in the "vestige" headers from
LMMS or dssi-vst. Doesn't matter whether it's intended to
support Win32 or native Linux plugins. You won't get support for
everything in VST, but a redistributable binary that supports much of it
has got to be worthwhile, surely.
The author claimed in LMMS list postings that these headers were
reverse engineered from working VST host and plugin code without seeing the
original SDK or accepting the Steinberg SDK license. Obviously I cannot
know whether that is really the case, but judging from the code, I think
it is plausible. Until anyone produces any evidence otherwise, I for one
would be happy to give it the benefit of the doubt.
Regarding the vst compiling, could you not use
the free and open
source headers from Javier Serrano Polo used by dssi-vst and lmms?
this has been already asked and answered elsewhere... here:
http://www.rncbc.org/drupal/node/66#comment-1649
bottom line seems to be that the vst-sdk support that are now being
required for qtractor is for _native_ linux vst plug-ins and not for
win32 dlls linked trough wine as is what dssi-vst does 
10:05 a.m.
Rui Nuno Capela wrote:
hi Chris,
On Mon, February 18, 2008 13:49, Chris Cannam wrote:
We all know that you already took a look at the original VST SDK headers
- at least once, didn't you? You're banned for life to write your own
reverse engineered version.
Your only option is to write a small app to memset to zeros that part of
your memory. Backup your brain first. Also, be sure your application
doesn't reset the part of your brain in which you stored the location of
your backup.
Good luck.
-c.
On 16/02/2008, Rui Nuno Capela
<rncbc(a)rncbc.org> wrote:
simple as it could ever be: it does not build with the vestige headers
alone. there are somethings missing. i know that it would suffice to
copy-and-paste those things from the original steinberg headers, but...
you know, i just can't, nor have the skill, to do that with my eyes shut
;)
eheh
James Stone wrote:
I see the "asked" part on that page, but I don't entirely see
the
"answered".
If your only requirement is to be able to include aeffect.h and
aeffectx.h, you should just be able to drop in the "vestige" headers from
LMMS or dssi-vst. Doesn't matter whether it's intended to
support Win32 or native Linux plugins. You won't get support for
everything in VST, but a redistributable binary that supports much of it
has got to be worthwhile, surely.
The author claimed in LMMS list postings that these headers were
reverse engineered from working VST host and plugin code without seeing the
original SDK or accepting the Steinberg SDK license. Obviously I cannot
know whether that is really the case, but judging from the code, I think
it is plausible. Until anyone produces any evidence otherwise, I for one
would be happy to give it the benefit of the doubt.
Regarding the vst compiling, could you not use
the free and open
source headers from Javier Serrano Polo used by dssi-vst and lmms?
this has been already asked and answered elsewhere... here:
http://www.rncbc.org/drupal/node/66#comment-1649
bottom line seems to be that the vst-sdk support that are now being
required for qtractor is for _native_ linux vst plug-ins and not for
win32 dlls linked trough wine as is what dssi-vst does
now seriously, the native linux vst support is still a
grey area.
energyxt2 is to blame to have started it all in first place. then come
jost from jucetice, which pretty awesome pice of work. now it's renoise.
only jost has the nerve to be open-source, though, yeah.
why did i got that in qtractor too? i'll give you three reasons: fun, fun
and fun. :D sorry, just can't help it
cheers
--
www.cesaremarilungo.com
10:14 a.m.
On Mon, February 18, 2008 15:04, Cesare Marilungo wrote:
Rui Nuno Capela wrote:
whom are you talking to? me or the lmms guy? i assure you i didn't look at
it twice (but my gcc has:)
byee
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
hi Chris,
On Mon, February 18, 2008 13:49, Chris Cannam wrote:
We all know that you already took a look at the original VST SDK headers
- at least once, didn't you? You're banned for life to write your own
reverse engineered version.
Your only option is to write a small app to memset to zeros that part of
your memory. Backup your brain first. Also, be sure your application
doesn't reset the part of your brain in which you stored the location of
your backup.
On 16/02/2008, Rui Nuno Capela
<rncbc(a)rncbc.org> wrote:
simple as it could ever be: it does not build with the vestige headers
alone. there are somethings missing. i know that it would suffice to
copy-and-paste those things from the original steinberg headers, but...
you know, i just can't, nor have the skill, to do that with my eyes
shut ;)
eheh
James Stone wrote:
> Regarding the vst compiling, could you not use the free and open
> source headers from Javier Serrano Polo used by dssi-vst and lmms?
>
>
this has been already asked and answered elsewhere... here:
http://www.rncbc.org/drupal/node/66#comment-1649
If your only requirement is to be able to include aeffect.h and
aeffectx.h, you should just be able to drop in the "vestige" headers
from LMMS or dssi-vst. Doesn't matter whether it's intended to
support Win32 or native Linux plugins. You won't get support for
everything in VST, but a redistributable binary that supports much of
it has got to be worthwhile, surely.
The author claimed in LMMS list postings that these headers were
reverse engineered from working VST host and plugin code without
seeing the original SDK or accepting the Steinberg SDK license.
Obviously I cannot
know whether that is really the case, but judging from the code, I
think it is plausible. Until anyone produces any evidence otherwise,
I for one
would be happy to give it the benefit of the doubt.
17 Feb
17 Feb
4:50 p.m.
On Saturday 16 February 2008, Rui Nuno Capela wrote:
Hi LAUs,
After some time in quarantine, meaning that it just passed almost 40
days since its last public appearance, the frivolous debutante has
matured a bit but not that much. Truth is, it is not quite healed and in
fact, it is getting seriously bloated ;)
Qtractor 0.1.1 (futile duchess) has been released!
Hi,
i follow this project from its days of its first appearance on your website..
It looks very promising and i even recorded little snippets with different
versions already.
Keep up the good work :)
Thanks and regards,
Flo
--
Palimm Palimm!
http://tapas.affenbande.org
5:11 p.m.
Rui Nuno Capela wrote:
Hi LAUs,
After some time in quarantine, meaning that it just passed almost 40
days since its last public appearance, the frivolous debutante has
matured a bit but not that much. Truth is, it is not quite healed and in
fact, it is getting seriously bloated ;)
Qtractor 0.1.1 (futile duchess) has been released!
Qtractor is an Audio/MIDI multi-track sequencer application, written in
C++ around the Qt toolkit. Its primordial 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 Desktop Audio/MIDI Workstation GUI specially
dedicated to the personal homestudio. It sits confortably tagged as for
the techno-boy bedroom home-studio. There's no genre segregation here,
it also applies to techno-girls ;).
Now seriously, it even has its own Wikipedia entry already:
http://en.wikipedia.org/wiki/Qtractor.
Back to business, these are the major highlights for this release:
- Draft user manual, contributed by James Laco Hines.
- Native Linux VST plug-in support.
- Initial DSSI plug-in support (audio effects only atm.)
- User configurable keyboard shortcuts.
- JACK server auto-start.
- Clip fade-in/out relative resizes.
- Auto time-stretch now optional.
- MIDI capture/record input quantize.
- Major plug-in infrastructure rewrite.
- Seamless plug-in drag-and-drop.
Check it out, from the official project web site:
http://qtractor.sourceforge.net
http://sourceforge.net/projects/qtractor
Direct link for the source tarball download:
http://downloads.sourceforge.net/qtractor/qtractor-0.1.1.tar.gz
The new user manual draft is also made available:
http://downloads.sourceforge.net/qtractor/qtractor-0.1.1-user-manual.pdf
Literal change-log follows. since the last 0.1.0 (frivolous debutante)
alpha release:
- After some great user demand, keyboard shortcuts are finally
configurable, as found provisionally under Help/Shortcuts...,
for the main application menu and for the MIDI editor as well.
- Debian package gets SSE optimization disabled as default.
- At least some transport actions get to be non auto-repeatable
when pressed for much too long, as Play and Record, avoiding
the tumbling imposed from the keyboard.
- For the first time ever, jackd auto-start is now allowed (!).
- OSC service support through liblo gets optional at configure
time, now leading the way to proper DSSI plug-in hosting.
- All plug-in widget controls count are now capped to one hundred.
- Plugin paths setup is now made available on the options dialog,
overriding each of respective default settings, as implicit from
the LADSPA_PATH, DSSI_PATH and VST_PATH environment variables
(see View/Options.../Display/Plugin Paths).
- Clip fade-in/out lengths are now kept relative to tempo changes
and also to clip offset and length changes (clip resizes).
- Automatic time-stretching for all audio clips when session tempo
changes, may now be disabled/enabled as a global session option
(see View/Options.../Audio/Playback/Automatic time-stretching).
- Double-clicking on an empty area (de)selects all clips on track.
- MIDI capture (record) quantization is now an option, possibly
handy for some jerky performance musicians, as the one found
in myself ;) (see View/Options.../MIDI/Capture/Quantize).
- The global options dialog (View/Options...) has seen its Display
tab page being moved back and to the right.
- Major rewrite of the plug-in infrastructure, adding primordial
support for DSSI and native VST plug-in flavors.
- Drag-and-drop of plug-in instances are now allowed intra- and
inter-mixer strip chains, either on tracks or buses.
- Turning track record off while recording is rolling was leaving
the session in a inconsistent recording status, now fixed.
- A random but instant crash upon audition/pre-listening player
onset was hopefully fixed.
Cheers && Enjoy
--
rncbc aka Rui Nuno Capela
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
Just one thing: when I add some LADSPA effects to an audio track, I
expect to hear them applied while recording/monitoring too. Most DAWs
have this behaviour.
Apart from this, Qtractor is really promising.
Keep up with the good work.
-c.
--
www.cesaremarilungo.com
18 Feb
18 Feb
4:22 a.m.
On Sun, February 17, 2008 22:11, Cesare Marilungo wrote:
Rui Nuno Capela wrote:
ok, did i say qtractor is a daw? just kidding. you're right, track
plug-ins should be applied to the monitored signal path (the pass-thru
one), not the one captured that gets recorded on file.
i'll take note and will try to implement that asap.
Qtractor 0.1.1 (futile duchess) has been released!
Just one thing: when I add some LADSPA effects to an audio track, I
expect to hear them applied while recording/monitoring too. Most DAWs have
this behaviour.
Apart from this, Qtractor is really promising.
Keep up with the good work.
thanks. actually, qtractor has been improving bit by bit thanks most to
user opinion and bug reports, critiques and heads-up. if it came from my
sole use case it probably could end like something very, erm... twisted ;)
cheers.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
6257
days inactive
6259
days old
linux-audio-user@lists.linuxaudio.org
9 comments
5 participants
participants (5)
-
Cesare Marilungo -
Chris Cannam -
Florian Schmidt -
James Stone -
Rui Nuno Capela