by way of lennart's blog, i came across this very instructive video:
http://0pointer.de/blog/projects/video.htmlxiph.org's head honcho monty deals with the basics of digital media. if
all that signal theory technobabble has always freaked you out, here's a
way to get your feet wet without too much discomfort.
On Fri, Sep 24, 2010 at 3:05 PM, Robin Gareus <robin@xxxxxxxxxx> wrote:
> ..and in case there are files with whitespaces in the filename, change
> the default string separator:
> # do stuff
> unset IFS
Or remove spaces from all filenames. Why would one want spaces in filenames anyway ?
To me it feels a bit like putting spaces in variable names, which isn't a good idea either.
echo "This command changes all spaces in file names into underscores"
echo " for ALL FILES IN THIS DIRECTORY !"
echo " Type ENTER to continue or ^C to quit"
for f in *; do
oldname=`echo $f |sed 's/ /~/g'`
newname=`echo $f |sed 's/ /_/g'`
if [ $oldname != $newname ]
echo mv $f $newname
mv "$f" $newname
It's TYOQA (The Year Of Qtractor Automation:) what else?
But wait, there's three months to go yet. Meanwhile, the foundations
have already been laid and one can now tell that a rocky milestone is
ready to get bumped. Ouch!
Qtractor 0.4.7 (furious desertrix) is out!
- MIDI learn/controller mapping for all plugin parameters (NEW)
- Extended Clip fade-in/out WYSIWYG curves (NEW)
- MIDI resolution overflow (FIX)
- MIDI tempo standard base on quarter-note (FIX)
- Extended MIDI controller mapping for mixer/tracks (NEW)
- Audio metronome gain control (NEW)
- Mute/solo tracks while looping (FIX)
- MIDI Clock support (NEW)
- Audio clip import while looping (FIX)
- MIDI track bank-select/program-change transparency (FIX)
- VeSTige headers included for native VST plugin support (NEW)
- JACK transport sync support (FIX)
- Clip tempo-adjust tool (NEW)
- Audio tracks auto-monitoring (FIX)
- Transport back/forward stops on loop points (NEW)
- MIDI tracks redundant mute/solo (FIX)
- source tarball:
- source package (openSUSE 11.3):
- binary packages (openSUSE 11.3):
- user manual (nevermind outdated):
Weblog (upstream support):
Qtractor is free, open-source software, distributed under the terms of
the GNU General Public License (GPL) version 2 or later.
- While moving multi-selected MIDI events around the clip editor (aka
piano-roll), with help of keyboard arrow keys, that is, was not clear
which one was the so-called "anchor" event, the one which positioning
gets honored for snap-to-beat business. Not anymore: the anchor event
now defaults to the earliest in time or the one the user's last
- MIDI control observer pattern implementation has sneaked in, making it
ready for the so-called and long-awaited "MIDI Learn" feature and
arbitrary MIDI controller assignment, for plugin parameters in particular.
- MMC DEFERRED PLAY doesn't cause transport state to stop if currently
rolling (mitigating bug #3067264).
- Audio clip merge processing might have been skipping a few initial
frame blocks, now fixed.
- Clip selection and plugin parameter hash optimization.
- Anti-glitch audio clip macro fade-in/out fixed again.
- New clip fade-in/out slopes (curves) are introduced, partially adapted
and refactored from those easing equations of Robert Penner's fame.
- Clip fade-in/out non-linear slopes are now shown as actual WYSIWYG curves.
- Escape key now closes generic plugin widgets as ever found usual
- Picking nits: unselect current track when clicking on any gray empty
area, also accessible from a new menu item: Track/Navigate/None.
- A nasty and deadly MIDI resolution overflow has been finally fixed,
allowing for long MIDI sequences (1h+) to load correctly on 32bit
machines from now on (was perfectly fine on 64bit though).
- MIDI editor selection hash optimization in face of reasonably huge
- MIDI controller mapping finally refactored to support some other MIDI
event types than just CC (0xBn) ones.
- Nitpicking fix: corrected main track-list (left pane) display when no
track is currently selected.
- libX11 is now being added explicitly to the build link phase, as seen
necessary on some bleeding-edge distros eg. Fedora 13, Debian 6. (fixing
- New audio metronome bar and beat sample gain options.
- Progressively, the observer pattern is being finally introduced,
targeting all potentially automation controls and widgets as plain
ground-zero for the (ultra-)long overdue automation feature.
- MIDI controller mapping of still non-existing tracks were being
implicitly assigned to the last, highly numbered, existing track. Now fixed.
- Moving from old deprecated Qt3'ish custom event post handling into
regular asynchronous signal/slot strategy.
- Muting/soloing tracks while playback is looping was leaving current
audio clip out-of-sync whenever that same track is later un-muted on any
other preceding clip. Now hopefully fixed.
- MIDI Clock support makes its first appearance.
- All tempo (BPM) calculations are now compliant to the MIDI
conventional equivalence between beat and quarter note (1/4, crotchet)
as common standard time division.
- Automatic audio time-stretch option is not enabled by default anymore.
- Standard warning Apply button is now only shown when dismissing dialog
changes are actually valid.
- Make sure non-dedicated metronome and player buses are properly reset
and reopen when changing regular audio buses (hopefully fixing bug item
#3021645 - Crash after changing audio bus).
- Hopefully, an outrageously old bug got squashed away, which was
causing random impromptu crashes, most often when importing audio clips
while looping and play-head is any near the loop end point.
- General standard dialog buttons layout is now in place.
- Fixed main track view off-limits play-head positioning.
- Main tool-bar Time and Tempo spin-boxes, may now have their colors
correct, as for most non-Qt based theme engines (ie. Gnome). Green text
on black background has been and still is the the intended aspect design ;)
- MIDI file import and internal sequence representation has been changed
to be inclusive on all bank-select (CC#0,32) and program-change events
which were previously discarded while honoring MIDI track properties.
Interleaved SysEx events are now also preserved on their original
sequence positions instead of squashing a duplicate into the MIDI bus
- Attempt to include the VeSTige header by default, as for minimal VST
- JACK transport support has been slightly rewritten, in fact the sync
callback is now in effect for repositioning.
- The MIDI clip editor (piano roll) widget won't be flagged as a tool
- A tempo adjustment tool is making inroads from the menu, as
Edit/Clip/Tempo... (factory shortcut: F7).
- Audio tracks auto-monitoring is now effective on playback.
- Make sure to ask whether a dirty MIDI clip should be saved, upon
resizing or stretching its edges (fixes bug #3017723).
- Backward and Forward transport commands are now taking additional
stops on loop points.
- Attempt to optimize track solo/mute redundant transactions, in special
regard to MIDI track events which were being duplicated on soloing and
temporarily muted on unsoloing.
Cheers && Enjoy (be happy!)
rncbc aka Rui Nuno capela
Friends, MusE 1.1 is here!
MusE is a combined midi and audio sequencer which tries
to cover most bases for the linux computer studio.
MusE is one of the oldest sequencers on the Linux audio scene and is
today a very stable open source solution for everyday music making.
This release adds some new features, lots of bugfixes and a bunch
of usability improvements.
MusE : http://muse-sequencer.org
* Jack midi support.
* Allow native VST guis for plugins
* Audio and midi routing popup menus now stay open, for making rapid
* MusE now has two mixers, with selectable track type display.
* External midi sync fixes and improvements, should be very stable
* Some pianoroll improvements
* Some crash fixes
* Drum editor fixes
* Various arranger fixes and improvements
* Various improvements for plugin guis
* Routing fixes
* Stability fixes for plugins
* Various DSSI fixes
* Rec enabled track moves with selection when only one track is rec enabled
* Jack midi, routing system, multichannel synth ins/outs, midi strips
and trackinfo pane.
* Dummy audio driver: Added global settings for sample rate and period size.
* Arranger track list: Quick 'right-click' or 'ctrl-click' or
'ctrl-mouse-wheel' toggling of Track On/Off.
* Allow changing timebase master
* Option to split imported midi tracks into multiple parts.
* Several new keyboard shortcuts for various operations, see shortcut editor
* Several colour tweaks and other cosmetic changes
* Various stability fixes
* Countless fixes and tweaks, about a 300 lines in the Changelog,
check it for a complete list of blood sweat and tears
[What is MusE again?]
MusE is multitrack virtual studio with support for:
* jack midi
* internal softsynths, including soundfont player FluidSynth
and sample player Simple Drums
* DSSI softsynths, including VST instruments
* with a patch to DSSI, VST-chunks are handled
* Drum editor
* Conventional arranger
* midi automation
* and lots more
* Jack transport
* LADSPA plugins
* VST plugins through dssi-vst
* audio automation, old sch00l
* and lots more
For a complete list of changes, check the ChangeLog in
the package or online at the sourceforge site:
Keep on rocking!
The MusE team
On Wed, Sep 29, 2010 at 06:11:36AM -0700, Patrick Shirkey wrote:
> Otherwise in the interests of keeping a relatively convivial tone I would
> like to thank you for spotting the flaws that you have found.
Here's one more:
This the frequency response (no EQ or whatever) using the IIR crossover,
set to 500 Hz and 3 kHz. Those 'qualitatively more experienced DSP
engineers' don't apparently have the experience to perform even the
simplest of tests. Nor do they know that the type of filter used will
produce antiphase signals at the crossover frequency.
(Hint: invert the mid band).
There are three of them, and Alleline.
Hello guys, peace and music to all of you.
Here's my story:
I won a laptop some months ago, and with the Windows 7's arrival I
decided to try a Linux distro, more precisely Ubuntu, for its facility
and also, for the Gnome's accessibility from the CD boot to the final
instalation, which is an enormous advantage for us blind users, when we
want to setup a computer independently. I use computer for ten years and
it's good to see Linux and Apple's developers going towards facilities
to everybody... I've mentioned Apple because seems that Apple's
Voiceover can also be accessed even during the instalation according to
an article I've read on the web.
Anyway, I've tested Ubuntu 9.10 and it wasn't that good because it had
some audio issues including with the Orca's usage, so I decided to wait,
and soon came Ubuntu 10.04 and, for the moment, it took all the chances
of Windows getting wrapped into my laptop. Besides, with a few, very few
programs I can do all the things I need to do... Of course things may
change in the future, but it's good to work in a system so light,
secure, and it's even better to find a supportive comunity.
Last saturday I decided to move my desktop computer, an Athlon X2 4000,
Asus M2N-SLI, 2GB of RAM with two hard disks, to Ubuntu 10.04.1 64bits
version. I really got amazed with the performance, even the Orca screen
reader is more responsive with the 64bits version. I'm interested in
audio production using Linux, so I need clues.
I have two audio cards, the mother board's built-in and the Delta
Audiophile 2496, the ladder one detected as card 0, wich according to my
understanding is the default card. But I was unable to get output from
the Delta, so I had to select the built-in sound card as my default
output for the moment. Then, after further reading I could install jackd
and Ardour for a test, and with Ardour I get all the feedback I need
while playing sounds through Delta. But of course, my goall is to make
the system work fully with the Delta.
What should I do to build a stable audio set using Ubuntu? And of
course, what are the must have programs? Since Orca is GTK-based, I'd
prefer to stay far from KDE due to accessibility issues. The thing I've
loved about Ardour is that I'm able to control jack without having to
access the jack GUI, which is KDE. But of course, if I can adjust
settings by editing configuration files it'll be better.
Any tips on how to make things work decently will be very appreciated.
Sorry for some obvious questions that I might have asked, and sorry for
Thanks in advance for all the input.
Warm regards from São Paulo, Brazil.
FYI, I joined the meego kernel list -- the missing ALSA hrtimer will be added:
On Sat, Sep 25, 2010 at 12:36 PM, Arjan van de Ven
> On 9/25/2010 11:20 AM, Niels Mayer wrote:
>> Unfortunately, in meego, snd-hrtimer doesn't exist. Only modules in snd-* are: ...
> hmm you're right
> I've added it now.
More interesting, all the goodies in planetccrma/rpmfusion/fedora
repos will be available in Fedora 14 with a Fedora supported Meego
Desktop; the time for needing hacks like http://nielsmayer.com/meego/
is limirted. Furthermore the important tools will be documented:
https://fedorahosted.org/musicians-guide/ and Linux audio, whether on
a desktop or netbook or tablet, will gain further visibility and
support. And meego-using multimedia users will gain a realtime kernel,
perhaps, by using CCRMA's directly on Fedora 14 sometime in the
future... good news all around, eh?
///// ///// ///// ///// /////
Fedora 14, nicknamed "Laughlin," will be the first Red Hat supported
distribution to let users choose MeeGo as their desktop. MeeGo is a
Linux desktop architecture for mobile devices, netbooks, embedded
Linux devices (such as In Vehicle Infotainment systems). It is based
in the GNOME mobile platform but has been beefed up with additional
technologies (Clutter, GUPnP and libsocialweb). Fedora 14 will include
the MeeGo Netbook UX specifically for netbook users as a "user
environment that sits of top of Fedora and associated MeeGo core
services. The netbook user interface and user interaction model for
the target devices then is on top of that. ... This expands on the
existing support we've had for Moblin in Fedora 12 and 13. "
///// ///// ///// ///// /////
PS: I guess it wouldn't be too early to ask -- preexisting Qt4
"desktop" apps like
http://qtractor.sourceforge.net/http://qjackctl.sourceforge.net/http://qsynth.sourceforge.net/ end up taking some time getting used
to, due to the limited screen real estate on a netbook as well as
windows send you to a different screen and make it difficult to use in
conjunction with other application windows simultaneously.
Thus three questions related to using existing Qt4 desktop apps on Meego:
(1) A way on for meego to popup new non-modal application level
windows, such as "Mixer" and "Connection" in qtractor -- in the same
"screen" as the one that launched it. Alternately is there a way for
these windows in qtractor/qsynth/qjackctl to become panels in the
(2) A way for existing application icons in qtractor to be displayed
smaller, with less border/whitespace, so that they can fit more
densely in a panel. Is there an appropriate way to set different kinds
of application defaults /styles/skins for using such Qt4 applications
on a lower resolution screen -- such as referencing display DPI?
(3) A way for Qt4 application icon panels such as used in qtractor, to
be rendered as dynamic "mouseover" popups, or "window-shade" style
overlays, providing the functionality of the application icons,
without taking up static real estate on a cramped screen?
Just uploaded a new video tutorial to YouTube:
It's about using the Sirlab Vocoder LADSPA plugin in Qtractor. I ditched
recordMyDesktop in favor of ffmpeg with jack_capture within a nested
Xephyr session with a 1280x720 resolution (apparently YouTube likes this
best). The quality improved drastically.
I've read about hardware monitoring, and jackd man page says my card supports it. What I would like to get is increse periods so jack has big buffer to avoid xruns, and use hwmon to avoid latency problems. Is this possible and if yes, how? Do I just change "H/W2" input to "H/W In 0" (and similar for "H/W3")? If so, how would I hear "PCM Out" (in this case, jackd, I think)? Hardware mixer before going to the amp? Thanx!
FreeB(eer)S(ex)D(rugs) are the real daemons
Patrick Shirkey <pshirkey(a)boosthardware.com> wrote:
> On Wed, September 29, 2010 4:17 pm, fons(a)kokkinizita.net wrote:
> > On Wed, Sep 29, 2010 at 12:19:09PM -0500, Jan Depner wrote:
> >> Damn, I just noticed that you said IIR crossover - Steve recommended
> >> against using the IIR crossover for serious work. In fact, it says that
> >> in the tooltip in Edit->Preferences. I think he knew it wasn't optimal
> >> when he threw it together. If you know how to fix that it would be
> >> great.
> > If you fix the filters then the IIR crossover would actually be the
> > better one. The FFT-based filters are much too steep (this can be
> > fixed as well of course).
> We are looking into all of your concerns.
> FYI, by three experienced people I was referring to Steve Harris, Jack
> O'Quin and my friend who is assisting with analysis of your diagnosis of
> the problems/bugs inherent in the current design. As we are all busy and
> you seem to have spent a fair amount of time analysis the issues it will
> take a us a couple of days to run a full set of tests. We are happy to
> isolate the issues you have presented as priority concerns.
> Perhaps an easier way to do this in the future is to just present your
> evidence up front instead of trashing other peoples hard work with vague
> off hand and out of context remarks.
> It doesn't contribute to your credibility in the slightest. If anything it
> just makes you come across as an arrogant bitch. I'm sure that is not the
> public face you want to present to the world and neither is it the status
> that we want to confer on you either.
> Just my 2 x 1/8oz gold coins though.
You should have kept them in your pocket and kept your mouth (keyboard?)
shut. Next time, when you are boiling, go take a shower, relax, get a
good night's sleep and then think of a more constructive way to go
Can all of the people concerned just take a step back please?
P.S. If you are wondering "who the hell is he?", the answer is "nobody":
I've posted once or twice over the past year, but I've been mostly
lurking, trying to learn a few things. I don't know much about the
technical matters but I can see a disaster coming as well as
anybody. All I'm trying to do is avert it, but I can't do more than
point out it's here. It's up to you (all of you) to steer the discussion
into more productive channels.