Dear all,
The holiday season is over and I actually took advantage of it by not
working on this month's round-up but by making music. With the help of
Leigh Dyer's outstanding seq24 tutorials I'm trying to master seq24 and
so far I'm really enthusiastic about this sequencer. I've started
remixing an older track of mine and seq24 has already proven itself a
very valuable tool.
But I did read up on relevant mailinglists and forums to keep in pace
with the developments in Linux Audio Land. And December did yield some
interesting topics, like the RT_GROUP_SCHED option (cgroups) discussion
on the Jack-Devel mailinglist and the refutation that CPU frequency
scaling has no use for low-latency real-time audio, and then there was
the sheer amount of music made with Linux of course!
Best,
Jeremy
PS. Thanks to the people from LinuxMAO, without them I'd miss out on a
lot of developments, releases and other non-trivial events worth mentioning!
Here is a track I made on Neil Modular Track which I also develop.
http://www.youtube.com/watch?v=qsVA5p2iHVM
You can get it here: https://sites.google.com/site/neilsequencer/
--
"Cheshire-Puss," she began, "would you tell me, please,
which way I ought to go from here?"
"That depends a good deal on where you want to get to," said the Cat.
"I don't care much where--" said Alice.
"Then it doesn't matter which way you go," said the Cat.
Hey,
this has been so fun for me I figured it could be for some of you
also... Today in 2-3 hours I've built a 2 string fretless bass following
more or less this instructable:
http://www.instructables.com/id/2-String-Paddle-Bass/
short demo (sorry for unfriendly site... don't know where else to put
it):
http://www.mediafire.com/?rm3wjl3rakmj36h
It's incredible the sound it has considering it's a piezo stuck between
some scrap wood and weed-eater strings
The piezo is putten directly into the soundcard and it clips... I should
parallel it with a zener diode... BTW what is the max voltage before
clipping on soundcards? is it soundcard-dependant?
No offense to real basses meant... of course it's only a game... but I
suggest trying it!
cheers
renato
Hi all,
Does anyone know of a MIDI monitor (a la KMidimon, or Qmidiroute, which
I usually use) that has native support for JACK MIDI? I recently
upgraded to a Saffire PRO 40 Firewire audio interface, and its MIDI
ports, which are exposed via JACK only, don't seem to be working
consistently, at least when used with ALSA apps via a2jmidid. I'm pretty
sure there's nothing wrong with a2jmidid, but it'd still be nice to take
it out of the equation for debugging purposes.
I did fine one app, called Midimon:
http://sourceforge.net/projects/midimon/
but I'm not sure if it's still maintained; it had some build issues (but
they were easy enough to fix).
Thanks
Leigh
=============
gigedit
=============
after much head-scratching I finally figured out how to add layers (aka
'dimensions') to a sample instrument in LinuxSampler/Gigedit
q: so let's say I have 3 samples as 3 dimensions stacked on one key
I can slide the window around so that with increasing note-on velocity
samples 2 & 3 will play
I can also drag the velocity windows (i.e. making them wider or
narrower) for each sample in a 'stack'
but there is no indication as to where the breakpoints occur for velocity
q: does anyone know how to determine the numerical value of the break
points for each dimension's velocity 'window'?
==============
zynaddsubfx
==============
I open the bank window and create an instrument slot by first selecting
the 'write' button and clicking on an empty slot and naming it 'foo'
I start fiddling with params get a sound I like
wanting to store this
I click on the 'write' button again
then click on the slot called 'foo'
thinking I've saved the sound to slot 'foo'
I click on another instrument and then click back on the 'foo' sound I
created
and the sound is the default sine wave
q: can someone tell me how to save an individual sound into a bank?
Hello everyone!
I have mentioned a simple lv2-host and have been convinced, that something
like that existed. But after some searching on google and apps.linuxaudio.org
and the lv2plug.in site, it seems I'm mistaken or the tool is hiding from me
with great tanacity and success. Can any one give me a pointer?
Kindly yours
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
Hello SM!
I'm not sure, but if they took features of the already existing DSSI in
consideration - and they took a lok at VST - then UIs should already be
seperate from the DSP/engine code. I think, that's how, they are used in that
test plugin host. But that may all be complete bollocks on the other hand,
since I'm just guessing based on a few facts I know.
Kindly yours
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
howdy
so i lied, bluffed all the way, so what? should I be sorry? what you'd
expect from this one self-called ber-procrastinator ? and then there's
hope. alas, not the messiah, rather my development drive at my own pace.
believe it or not, it is on-going and it will sure happen real soon ;)
no sweat. The whole automation prophecy will be realized and delivered.
yes, TYOQA just failed, slipped a bit. it doesn't mean it was abandoned
though or, uh, procrastinated... well, it's only a happy new year after
all:)
the road to automation is being already being paved and walked although,
i must say, it is no yellow-bricked one. the drive has begun.
definitely, 2011 will be TYOQA (aha, read that again with a bold tee:)!
more than automation, which infrastructure is already lurking in there,
trus me, all work is being carried out at the backyard for the time being.
blossoms might just pop out this spring ;)
one thing i may wish to leave sound and clear: it is very likely that,
in the very near future, that there will be some dot-release before the
all-mighty-one release, whatever. now that the surprise-effect is gone,
the long overdue and hailed beta release cycle that will present you and
carve its deeds on stone with the dynamic-curves and automation features
et al., will be nothing less nor before the coming version numbered as
the 0.5.x scheme. then, and only then, the current alpha-cycle will be
concluded. of course, that will be also the time for translations to be
called in. just be a little more patient :)
and then i lied a second time, when said those parodied f&d release
code-names were exhausted. thanks to a lengthy but intermittent
fall/winter-of-coding period, i had the chance to wake up one morning
with the imagination score in its lowest end and roar an inner WTH! as
they say around here, there's no second without a third. so another lie
is there waiting to be told. or is it not? there, one would say: time
will tell...
Release highlights:
* Archive/Zip session file bundle (save as... .qtz) (NEW)
* Mixer MIDI controller mapping/learn (NEW)
* LV2 GTK UI support (NEW)
* LV2 Persist extension support (NEW)
* MIDI Tools on main track/clips view(NEW)
* Floating tool-tips while dragging/moving/pasting (NEW)
* Rescale and Timeshift MIDI tools (NEW)
* MIDI Quantize percentage (NEW)
* Track range selection (NEW)
* Audio insert send, wet/dry controls (NEW)
* Audio clip pitch-shifting (FIX)
* Metronome dedicated outputs related crash (FIX)
* Stop transport tool/button action (NEW)
* Mouse-wheel zooming (NEW)
and a few more assorted features and fixes--see below the complete
(boring) change-log for gruesome details.
Nuff said.
Qtractor 0.4.8 (fiery demigoddess) released!
Website:
http://qtractor.sourceforge.net
Project page:
http://sourceforge.net/projects/qtractor
Downloads:
- source tarball:
http://downloads.sourceforge.net/qtractor/qtractor-0.4.8.tar.gz
- source package (openSUSE 11.3):
http://downloads.sourceforge.net/qtractor/qtractor-0.4.8-2.rncbc.suse113.sr…
- binary packages (openSUSE 11.3):
http://downloads.sourceforge.net/qtractor/qtractor-0.4.8-2.rncbc.suse113.i5…http://downloads.sourceforge.net/qtractor/qtractor-0.4.8-2.rncbc.suse113.x8…
- user manual (archeologically dated):
http://downloads.sourceforge.net/qtractor/qtractor-0.3.0-user-manual.pdf
Weblog (upstream support):
http://www.rncbc.org
License:
Qtractor is free, openosource software, distributed under the terms of
the GNU General Public License (GPL) version 2 or later.
Change-log:
- MIDI controller mapping/learn is now possible on all mixer controls
(monitor, gain, panning, record, mute, solo).
- An internal rewrite (aka. refactoring) have been carried out, making
sure that all track state action buttons (R, M, S) are now all under the
observer pattern umbrella.
- Single track range selection is now available on main menu
(Edit/Select/Track Range; default keyboard shortcut: Ctrl+Shift+R);
additionally to vertical range and horizontal track actions
(Edit/Select/Range, Track) all these operations can now toggle over the
previous selection.
- Direct clip selection from Files list item has been brute-forcefully
implemented (after being challenged by Jiri Prochaszka aka Anchakor:).
- Files tree widget sticky "New Group" item fixed.
- A new menu option has been added (View/Tool Tips) to show/hide a
floating tool-tip while dragging, moving, resizing or pasting selected
clips or events over the main tracks view and MIDI clip editor
(piano-roll) respectively, displaying current target position and status.
- Attempt to reset audio/MIDI time drift compensator on every engine
start and loop turnaround.
- Moving the punch-out marker over the main track time ruler was failing
to shrink the punch-in/out range, now it does (not).
- MIDI clip tools (quantize, transpose, normalize, randomize, resize,
rescale and the new timeshift) are now all accessible from the main
tracks view (Edit/Clip/Tools menu) and apply to all events on current
selected clip(s).
- LV2 Persist extension support is being introduced.
- A new timeshift MIDI tool has been added, after an awesome patch by
Jiri Prochaszka aka Anchakor; applies to selected events between edit
markers, distorting their time and duration (optionally), either slowing
down and accelerating, based on a given parameter P value.
- Audio clip/buffer pitch-shifting fixes with regard to latency
correction due on the RubberBand library one-pass (real-time) processing
mode.
- New Send Gain and Dry/Wet control parameters have been implemented for
audio Inserts pseudo-plugins.
- MIDI channel/master volume enqueued events are now affected by the
current track/bus volume (0-100%).
- Prevent old rounding error when resetting to plugin parameter default
value with the mouse middle-button click while hovering a slider widget
(observer).
- A quantize percentage has been added to MIDI clip editor quantize tool
(Tool/Quantize...) for time and duration quantization (0% for none; 100%
for full regular quantization).
- Metronome bus/ports are now created at engine start and not when user
switches it on anymore.
- Make sure all audio clip buffers are in sync upon smooth-ramping going
off and playback is rolling.
- Copy-pasting across controller event types is now possible on the MIDI
clip editor (aka piano-roll).
- Finally indulged, the genuine transport stop button makes its
appearance on main toolbar and menu.
- Main tracks grid visibility option (View/Snap/Grid).
- Yet another off-by-one (frame) audio buffer bug got squashed away:
rare symptom was that some audio clips were being left dead silent right
after playback of their first looping period.
- Plugin parameter name/label now a proper attribute of its respective
MIDI Controller observer instance, allowing to be shown on dialog title
(MIDI learn).
- Default session file format saved on JACK session demand is now the
bundle archive/zip one (.qtz).
- Plugin selection dialog now shows whether a plugin features its own
editor (GUI) and/or external state configuration (EXT).
- Help/Shortcuts... window positioning and sizing are now preserved.
- All plugin chain changes over the track properties dialog now sure
counts as a dirty action (possibly fixing bug #3104129).
- Newly extracted archive/zip session directories are now removed
automatically from the file-system on session close, prompting the user
for confirmation (cf. View/Options.../Display/Confirm Removals).
- Ctrl+mouse-wheel is now set for zooming in/out, on main track-view and
all applicable MIDI clip editor views (piano-roll), according to current
zoom mode (see View/Zoom Horizontal, Vertical or All for both ways
simultaneously).
- New MIDI clip editor (piano-roll) mouse hovering effect (eye-candy++).
- After too many a user request, a brand new session archive file type
is being introduced (.qtz) which tries to bundle in one single zip
archive all the media and contents of a session.
- Add that to eye-candy: either loop or punch-in/out outer ranges are
now shaded on the main track-view, thumb-view and MIDI clip editor
(piano-roll) views.
- LV2 GTK UI plug-in hosting is now roaring its ugly head (EXPERIMENTAL).
- Ignore all initial and decremental notifications of audio engine's
buffer-size changes.
- Internal audio buffer loop points were not being set properly for
non-zero clip offsets, leaving some as severely out-of-sync while
rolling over loop turns. Now fixed again, hopefully.
- Avoid audio peak file clashing when deriving from audio sample files
with distinct absolute paths but the very same file (base)name.
- A new MIDI editor (piano-roll) tool has been added: Rescale event
times, durations and/or values by a percentage between 1 and 1000%
(adapted thanks to patch #3081954, by Jesse Lucas).
- Attempt to mitigate audio clip sequencing glitches on
single-core/single-thread machines.
cheers && enjoy (be happy!)
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org