5 Oct
2009
5 Oct
'09
1:36 p.m.
Fall is upon us.
Summer is gone. Trivial speaking, as it marks yet one's another
birthday, mine that is. It also marks the approaching bankruptcy of this
funny F&D release code-names. One can also think as the last and stable
release before a probable next generation do break all loose. Automation
and full MIDI control is popping up over the horizon. So take all
children home and be prepared for the worst. Nah, don't be that afraid.
With some help from good friends, everything can and shall be arranged.
No second thoughts. No hard feelings. Meanwhile...
Qtractor 0.4.3 (fussy doula) released!
Release highlights:
* Audio send/return aux. inserts (NEW)
* Mixer peak meters gradient eye-candy (NEW)
* MIDI System Exclusive (SysEx) setup manager (NEW)
* MIDI Playback/Queue timer resolution option (NEW)
* MIDI Instrument definitions from SoundFont 2 files (NEW)
* MIDI Output bus default instrument (NEW)
* Buses dialog manager update (FIX)
* Plugin references by label (FIX)
* First audio metronome beat/bar (FIX)
* Ghost clip selections (FIX)
* Overlapping MIDI clips (FIX)
Website:
http://qtractor.sourceforge.net
Project page:
http://sourceforge.net/projects/qtractor
Downloads:
- source tarball:
http://downloads.sourceforge.net/qtractor/qtractor-0.4.3.tar.gz
- source package (openSUSE 11.1):
http://downloads.sourceforge.net/qtractor/qtractor-0.4.3-1.rncbc.suse111.sr…
- binary packages (openSUSE 11.1):
http://downloads.sourceforge.net/qtractor/qtractor-0.4.3-1.rncbc.suse111.i5…
http://downloads.sourceforge.net/qtractor/qtractor-0.4.3-1.rncbc.suse111.x8…
- binary packages (Ubuntu 8.04 LTS):
http://downloads.sourceforge.net/qtractor/qtractor_0.4.3-1.rncbc.ubuntu804_…
http://downloads.sourceforge.net/qtractor/qtractor_0.4.3-1.rncbc.ubuntu804_…
- binary packages (Ubuntu 9.04):
http://downloads.sourceforge.net/qtractor/qtractor_0.4.3-1.rncbc.ubuntu904_…
http://downloads.sourceforge.net/qtractor/qtractor_0.4.3-1.rncbc.ubuntu904_…
- user manual (ever still outdated):
http://downloads.sourceforge.net/qtractor/qtractor-0.3.0-user-manual.pdf
Weblog (upstream support):
http://www.rncbc.org
License:
Qtractor is free, open-source software, distributed under the terms of
the GNU General Public License (GPL) version 2 or later.
Change-log:
- External preset files are not removed nor deleted from the file-system
anymore.
- Connections support for UTF-8 encoded client/port names.
- Force track and clip properties dialog widget to be modal as it should
from their beginning dawn.
- Audio effect send/return aux. inserts are implemented as special
pseudo-plugins (Plugins/Inserts).
- Reset play-head position on auto-backward and keep playback rolling
when continue past end transport option is not set.
- MIDI clip editor (aka piano-roll/matrix aditor) gets better on the
virtual piano keyboard eye-candy side of things ;).
- Plugins are now also referenced by label, avoiding plugin index
clash/misses eg. when plugin object file/path changes or is moved
externally.
- Keyboard focus is now cleared/reset from the main toolbar time and
tempo spin-boxes when editing gets finished (eg. Enter key is pressed).
- First audio metronome beat/bar now played back correctly (fixes bug
#2841437).
- Client to/from port (dis)connections now found consistent as good
ol'QjackCtl behavior (fixes bug #2834657).
- All dirty open MIDI clip editors are now prompted to save before the
main application closes (fixes bug #2835516).
- Mixer level meters get their long deserved gradient look.
- Fixed any ghost clip selections that were haunting the main track
view, specially after undo/redo.
- Increased tolerance on reading corrupt MIDI files (SMF).
- A MIDI SysEx manager is being finally introduced, in some primordial
rather basic form though. MIDI System Exclusive (SysEx) event strings
may now be freely assigned to MIDI output buses only, allowing for
proper setup of external outboard MIDI equipment. Each bus may have an
unlimited SysEx queue that gets sent out on every connection change (see
View/Buses.../MIDI/SysEx...).
- A default MIDI instrument name may now be assigned to any MIDI output
bus (see View/Buses.../MIDI).
- More legacy headers, stdio.h and stdlib.h, are yet again necessary to
build with gcc/g++ >= 4.4 (as patch noted by Alexis Ballier on Gentoo
bug report #274168, thanks).
- Bus manager dialog (View/Buses...) gets new columns on the left pane
buses list as for displaying number of channels and bus mode.
- Crash when updating bus probably fixed (bug #2811630).
- Fixed glitch displaying beat snap/grid lines on MIDI clip editor,
incidental to clips located at absolute zero time.
- Overlapped MIDI clips were rendering garbled note events to DSSI/VSTi
plugins, now fixed.
- New MIDI Playback/Queue timer (resolution) option is now available
(see View/Options.../MIDI).
- MIDI instrument definitions may now be imported from plain SoundFont
files.
Cheers && Enjoy.
--
rncbc aka Rui Nuno Capela
rncbc at rncbc dot org
http://www.rncbc.org
5 Oct
5 Oct
2:23 p.m.
New subject: Half speed audio playback issue
Hi all,
Just wondering if any of you can give me a few clues as to what the possible
culprits might be in the case of half speed (one octave down) audio playback.
I have recorded live audio into Audacity (stereo @48Khz) and exported it out
to a sound file (Ogg, MP3). It plays fine in Amarok, but at half speed in both
Ardour and Qtractor. Audacity is going straight to ALSA, Amarok through Xine
to ALSA.
Looks like some kind of problem with Jack, which is very possible, but I had
no problem with using fluidsynth through Rosegarden (I could not load an
audio file into it to test though?). I tried to play straight into guitarix,
rakarrak, etc. previously and ended up with really bad distorted sound, that
also sort of sounded like sampling/processing was not up to speed. I tried
with an rt kernel, but no difference (flaky audio hardware is possible).
Anyway, if you have experienced this before just let me know what you think
it is. Need to dig in further myself, but a few clues from more experiences
Linux "audionaughts" will probably help narrow it down faster.
Any input appreciated.
Thanks.
Raymond Martin
2:31 p.m.
New subject: Half speed audio playback issue
Hello Raymond!
Just half speed audio with the original pitch is very strange. Usually that
requries some good FFT-based time-stretching. The octave donw thing and half
speed is easy. It means: 1. wrong number of channels or 2. wrong internal
samplerate (much more likely). Does it sound clean? Did you check the format
of the file using the program file, or even better the sndfile-programs. I
believe, that's what they are called as packages on Debian (and probably other
distros).
The half speed issue should have nothig to do with suboptimal hardware.
Distorted sound, glithcy audio, pops while recording possibly, but even those
mostly result from bad settings to JACK or simply slow CPUs.
Sorry, I can't tell you more, but perhaps that might calm you down somehow,
or help you looking.
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
3:41 p.m.
New subject: Half speed audio playback issue
Would it be the case that Ardour etc are thinking this is a mono
file? A stereo file played as mono could sound half-speed (maybe
somewhat distorted, depending on the differences betweeen the channels).
Victor
----- Original Message -----
From: "Raymond Martin" <laseray(a)gmail.com>
To: <linux-audio-dev(a)lists.linuxaudio.org>
Sent: Monday, October 05, 2009 7:23 PM
Subject: [LAD] Half speed audio playback issue
Hi all,
Just wondering if any of you can give me a few clues as to what the
possible
culprits might be in the case of half speed (one octave down) audio
playback.
I have recorded live audio into Audacity (stereo @48Khz) and exported it
out
to a sound file (Ogg, MP3). It plays fine in Amarok, but at half speed in
both
Ardour and Qtractor. Audacity is going straight to ALSA, Amarok through
Xine
to ALSA.
Looks like some kind of problem with Jack, which is very possible, but I
had
no problem with using fluidsynth through Rosegarden (I could not load an
audio file into it to test though?). I tried to play straight into
guitarix,
rakarrak, etc. previously and ended up with really bad distorted sound,
that
also sort of sounded like sampling/processing was not up to speed. I tried
with an rt kernel, but no difference (flaky audio hardware is possible).
Anyway, if you have experienced this before just let me know what you
think
it is. Need to dig in further myself, but a few clues from more
experiences
Linux "audionaughts" will probably help narrow it down faster.
Any input appreciated.
Thanks.
Raymond Martin
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
3:52 p.m.
New subject: Half speed audio playback issue
Hi Victor,
Would it be the case that Ardour etc are thinking this
is a mono
file? A stereo file played as mono could sound half-speed (maybe
somewhat distorted, depending on the differences betweeen the channels).
The problem seems to have been the data spread out over 4 channels instead
of 2, thus halving the output in terms of speed and consequently pitch.
Thanks.
Raymond
5:16 p.m.
New subject: Half speed audio playback issue
I thought something like that was happening. But I'm curious: if a 2-channel
file is played over 4-channels it should go up an octave, should it not?
You'd
have half as much data for 4 channels as you'd have for 2 channels and so it
would seem like it's going faster? Or my reasoning is wrong somewhere (it
could
well be, I often get things like that mixed up)?
Victor
----- Original Message -----
From: "Raymond Martin" <laseray(a)gmail.com>
To: <linux-audio-dev(a)lists.linuxaudio.org>
Sent: Monday, October 05, 2009 8:52 PM
Subject: Re: [LAD] Half speed audio playback issue
Hi Victor,
Would it be the case that Ardour etc are thinking
this is a mono
file? A stereo file played as mono could sound half-speed (maybe
somewhat distorted, depending on the differences betweeen the channels).
The problem seems to have been the data spread out over 4 channels instead
of 2, thus halving the output in terms of speed and consequently pitch.
Thanks.
Raymond
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev 
4:19 p.m.
New subject: Half speed audio playback issue
HI All
Just seen this mail,
My problem is that I export from my multi track machine running Beta 3
to my mastering machine with beta 3 as well.
All set at 48 K from Ardour on one to Ardour on the other.
I then export the two track master to disk at 44k 16bit.
The I use Audacity to make my Ogg files.
Thing is they now seem to run to fast on both machines, and when I send them
by Email.
Multi track machine has RME as sound card and inputs to my DDX at 48K master
The DDX outputs to the master box from the Spdiff out, this is locked I
assume to the DDX now locked to the RME card.
Am I missing some changes here?
When the ogg is emailed/played back they at a faster speed and the pitch
goes up accordingly
Hope there is enough info here..
Cheers
All
Bob
Blueslsd
2009/10/5 Raymond Martin <laseray(a)gmail.com>
Hi all,
Just wondering if any of you can give me a few clues as to what the
possible
culprits might be in the case of half speed (one octave down) audio
playback.
I have recorded live audio into Audacity (stereo @48Khz) and exported it
out
to a sound file (Ogg, MP3). It plays fine in Amarok, but at half speed in
both
Ardour and Qtractor. Audacity is going straight to ALSA, Amarok through
Xine
to ALSA.
Looks like some kind of problem with Jack, which is very possible, but I
had
no problem with using fluidsynth through Rosegarden (I could not load an
audio file into it to test though?). I tried to play straight into
guitarix,
rakarrak, etc. previously and ended up with really bad distorted sound,
that
also sort of sounded like sampling/processing was not up to speed. I tried
with an rt kernel, but no difference (flaky audio hardware is possible).
Anyway, if you have experienced this before just let me know what you think
it is. Need to dig in further myself, but a few clues from more experiences
Linux "audionaughts" will probably help narrow it down faster.
Any input appreciated.
Thanks.
Raymond Martin
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
5:50 p.m.
New subject: Half speed audio playback issue
Hi Frank,
Just seen this mail,
My problem is that I export from my multi track machine running Beta 3
to my mastering machine with beta 3 as well.
All set at 48 K from Ardour on one to Ardour on the other.
I then export the two track master to disk at 44k 16bit.
The I use Audacity to make my Ogg files.
Thing is they now seem to run to fast on both machines, and when I send
them by Email.
Multi track machine has RME as sound card and inputs to my DDX at 48K
master
The DDX outputs to the master box from the Spdiff out, this is locked I
assume to the DDX now locked to the RME card.
Am I missing some changes here?
When the ogg is emailed/played back they at a faster speed and the pitch
goes up accordingly
Are you sure sample rate conversion was done on the sound file when saved out?
The lack of conversion would result in a faster sound file due to more data
being packed into it. I do not see an explicit sample rate conversion function
in Audacity in the menus, just project settings. Perhaps it does not work for
you when you save.
Regards,
Raymond
6 Oct
6 Oct
8:30 a.m.
Rui Nuno Capela wrote:
Qtractor 0.4.3 (fussy doula) released!
Hi Rui :)
the last version I compiled was 0.4.2.1401 from svn, build Oct 2 2009
03:37:02.
For Linux Qtractor still is my favourite one :).
For further versions I would welcome a more comfortable "management" for
the .mid clips.
When working on a project I save this project by different names, to
enable it to go back to a later version. For Qtractor there's a problem.
After editing a MIDI clip, the changed clip is saved under the same
name, if you leave the editor without using the "save as..." option,
that means that when loading an older version of the project, the older
version can't be restored, when it is using the same clip. This is very
unusual behaviour for a sequencer. Having those .mid files isn't a bad
idea, but the way they are managed might need some improvements.
Thank you, all in all it's a good piece of software :), even if it's
still version 0.x.
Cheers,
Ralf
7 Oct
7 Oct
6:01 a.m.
On Tue, October 6, 2009 13:30, Ralf Mardorf wrote:
Rui Nuno Capela wrote:
qtractor version 0.4.2.1401, as found a few days ago on cvs, is by all
means the same as tagged release 0.4.3. trust me ;)
Qtractor 0.4.3 (fussy doula) released!
the last version I compiled was 0.4.2.1401 from svn, build Oct 2 2009
03:37:02.
For Linux Qtractor still is my favourite one :).
For further versions I would welcome a more comfortable "management" for
the .mid clips.
When working on a project I save this project by different names, to
enable it to go back to a later version. For Qtractor there's a problem.
After editing a MIDI clip, the changed clip is saved under the same
name, if you leave the editor without using the "save as..." option, that
means that when loading an older version of the project, the older version
can't be restored, when it is using the same clip. This is very unusual
behaviour for a sequencer. Having those .mid files isn't a bad idea, but
the way they are managed might need some improvements.
agreed, a better file/resource management is long todo list :)
the way qtractor refers to media content files (audio or midi) is somewhat
loose. so to speak.
as you might already figured out, files are referred by their paths. like
so-called "links" in other daws. so when you edit one midi file in one
session you're possibly changing the content of the file that is referred
from any other session, provided it is the same physical file (same file
path name).
while the midi clip editor tries to implement some kind of copy-on-write
for midi files, by incrementing a number/version suffix, that only occurs
on midi files that have been just imported into new clips, previously
recorded or revised clips will get their files unconditionally replaced
with editors content when you press save.
if, for instance, the given file path/name, is referred by two different
session/project files, you guess it right, any changes made to the clip
file will get reflected on both sessions. obvious, no? ;)
Thank you, all in all it's a good piece of
software :), even if it's
still version 0.x.
thanks for the support
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
5348
days inactive
5350
days old
linux-audio-dev@lists.linuxaudio.org
9 comments
6 participants
participants (6)
-
Frank Smith -
Julien Claassen -
Ralf Mardorf -
Raymond Martin -
Rui Nuno Capela -
victor