Hi,
A couples months ago we started a forum at linuxmusicians.com . Our aim
is to bring Linux musicians together and help each other to make music
on the Linux platform. We want to promote FLOSS software for making
music. We also want to make making music on Linux more accessible for
newbies and less computer minded people. We think a forum is a good
platform for this.
For making music on Linux, we need of course good software. To
inspire and help people to become a Linux audio developer, we launched a
special part for developers on our forum, which you can find here:
http://linuxmusicians.com/viewforum.php?f=44
As mentioned before, this should be a good and accessible place for
newbie programmers. But we also like to invite more experienced
developers to share their stuff, knowledge and help some newbies with
their first steps. Would be cool if some of you guys will visit the
forum sometimes a month (for example) and give some feedback to newbie
programmers or projects. If someone like to write an article about how
to become a Linux audio programmer and how to start, you're very welcome!
We are aware of the fact that there is also a linux-audio-dev
mailinglist and IRC channel. We also think the Linux audio development
community should operate as centralized as possible. So people can learn
from each other and make a good interaction between different apps and
projects as good as possible. That's why we wrote a short introduction
in which we make new developers aware of the existence of these places.
http://linuxmusicians.com/viewtopic.php?f=44&t=780
We hope we can inspire young and talented people to become a Linux audio
developer. We hope that you guys will support this initiative and are
willing to help new developers find their ways in the world of Linux
audio development.
Kind regards,
\r
Hello All!
I am just starting to use JACK and trying to run some of the example
clients. I am able to hear audio from the metronome example by connecting
the metronome output to the system playback ports.
However, when I connect metronome output to the simple_client input, I do
not hear any audio output. Since the simple client copies data from the
output port to the input port, I notice that the it should work in the same
fashion. Would anyone have any suggestions as to what could be possibly
wrong?
I am using qjackctl to launch the jack server and view the connections
between the different readable clients and the connections seem to show up
fine.
Thanks for your help. Happy New Year!
Regards,
Gopal
gopal.e(a)gmail.com
Merry season greetings!
After a very long quarantine period, and while after the last Flirty
Ditz romance, this pet has calmly bumped a few more steps ahead. Please
welcome, my Christmas present to y'all,
Qtractor 0.3.0 (fluffy doll) has been released!
Same old intro follows:
Qtractor is an audio/MIDI multi-track sequencer application, written in
C++ on top of Qt Software's Qt4 framework, having JACK and ALSA as its
main infrastructures and Linux as native and exclusive platform.
Specially suited to the lone-wolf composer, arranger and (re)creative
music-maker personal home-studio, it still hopes to evolve as a fairly
featured desktop audio/MIDI workstation or at least, a prototypical part
of it ;)
Release highlights:
* Paste-Repeat command. (NEW)
* Punch in/out recording. (NEW)
* Session/project template support. (NEW)
* Current track auto-monitoring. (NEW)
* MIDI buses now supporting multi-timbral instrument plug-ins. (NEW)
* Individual clip gain/volume, normalize and audio/MIDI file export. (NEW)
* Copy/paste to desktop environment clipboard. (NEW)
* and many, many fixes and new bugs ;)
Website:
http://qtractor.sourceforge.net
Project page:
http://sourceforge.net/projects/qtractor
Downloads:
- source tarball
http://downloads.sourceforge.net/qtractor/qtractor-0.3.0.tar.gz
- user manual
http://downloads.sourceforge.net/qtractor/qtractor-0.3.0-user-manual.pdf
Weblog (think 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.
Features:
- Multi-track audio and MIDI sequencing and recording.
- Developed on pure Qt4 C++ application framework (no Qt3 nor KDE
dependencies).
- Uses JACK for audio and ALSA sequencer for MIDI as multimedia
infrastructures.
- Traditional multi-track tape recorder control paradigm.
- Audio file formats support: OGG (via libvorbis), MP3 (via libmad,
playback only), WAV, FLAC, AIFF and many, many more (via libsndfile).
- Standard MIDI files support (SMF format 0 and 1).
- Non-destructive, non-linear editing.
- Unlimited number of tracks per session/project.
- Unlimited number of overlapping clips per track.
- XML encoded session/project description file.
- Point-and-click, multi-select, drag-and-drop interaction (drag, move,
drop, cut, copy, paste, delete, split)
- Unlimited undo/redo.
- Built-in mixer and monitor controls.
- Built-in connection patchbay control and persistence (a-la QjackCtl).
- LADSPA, DSSI and native VST plug-ins support.
- Unlimited number of plug-ins per track or bus.
- Plug-in presets, programs and chunk/configurations support.
- Audio/MIDI clip fade-in/out (linear, quadratic, cubic).
- Audio/MIDI clip gain/volume, normalize and export.
- Audio clip time-stretching (WSOLA-like or via librubberband),
pitch-shifting (also via librubberband) and seamless sample-rate
conversion (via libsamplerate).
- Audio/MIDI track export (mix-down, merge).
- Audio/MIDI metronome bar/beat clicks.
- MIDI clip editor (matrix/piano roll).
- MIDI instrument definitions (a-la Cakewalk(tm))
- JACK transport sync master.
- MMC control surface enabled.
- Configurable keyboard shortcuts.
Change-log:
- Almost complete rewrite of the plugin configuration and parameter
initialization logic.
- MIDI bank/program selection is now taken into account on plugins
initialization and replication.
- Fixed initial parameter values for native VST plugins.
- Track form plugin lists are now properly (re)initialized when track
type changes.
- Generic plugin forms now have the option to show/hide the parameter
widgets through the new "Params" button.
- New auto-monitor toggle option (menu Track/Auto Monitor): the current
selected track is now set on monitor and MIDI channel omni-mode
automagically, as a convenient workflow feature (kindly suggested by
Holborn).
- MIDI clip editor Tools menu is not disabled anymore when there's no
selection, drop-down menu items are instead.
- Make all recorded clips to honor either the punch-out or play-head
accumulated position; resolve all pending MIDI sequence note events on
record stop/close.
- Major silent move: audio plugins chain are now applied in a
pre-fader/meter basis as is usually implied from the mixer strip layout
ie. signal flows from the top to the bottom.
- All MIDI buses may now have plugins inserted so that multi-timbral
synth/sampler plugins get driven to their fullness.
- MIDI track plugin's dedicated audio output bus may now be effective,
as it seems, good old master audio output bus was being used, no matter
what.
- Paste-repeat command has been introduced, now allowing to replicate
and concatenate the clipboard contents over the time-line, with a given
repeat-count and optional period (see menu Edit/Paste Repeat... on the
main and MIDI clip editor windows).
- Normalize tool on MIDI clip editor got rewritten from its previous
brain dead, useless and utterly wrong operation.
- All time offsets and lengths are now zero-bar/beat based when
displayed in the BBT (bar.beat.ticks) format.
- MMC STEP gets adjusted to current snap-per-beat setting.
- Fixed broken initial buffering that was randomly crippling those audio
clips that fit integrally in cached and while on playback.
- Fix initialization of multiple instances of DSSI plugins which
implement run_multiple_synths (eg. fluidsynth-dssi), preventing an
instant crash on activation.
- Exclude deprecated VST elements from compilation.
- Export tracks dialog has new punch in/out range option.
- Somehow realized that looping and punch-recording are two mutually
exclusive states, at least until loop recording (ie. takes) gets real.
- Fixed bug #2249291 - Crash on tempo change; affecting the WSOLA based
time-stretching on all non-stereo audio clips.
- Incomplete audio peaks were being cached prematurely, fixed.
- Make way for paste/dropping items from the system clipboard over the
main track view. Cut/Copy/Paste/Delete of file items have now this
workaround fixed, wrt. Files widget keyboard shortcuts, respectively.
- Clip gain/volume propriety is now in place and reflected in audio clip
waveform drawing in particular.
- A new hideous progress bar is now lurking in the main status line, as
found convenient to display progress of the also new clip tools
(normalize, export, etc.).
- Clip normalize tool is now available (Edit/Clip/Normalise).
- Audio and MIDI clip file export is now available as a tool (see
Edit/Clip/Export...).
- Punch in/out (range) recording is now in experimental shape, with
minimal settings and functionality, already accessible through the main
menus, transport toolbars and visible on main tracks view and MIDI
editors as magenta colored line markers.
- External MIDI control events for channel volume (7) and channel
panning (10) are now handled properly through session tracks.
- Session file templates make its debut with new usability option, on
whether new sessions are created based on existing template file (see
View/Options.../Display/Session/New session template; nb. session
templates are just regular session files but loaded and saved with no
media content (no clips nor files).
- Grayed/disabled palette color group fix for dark color themes.
- Implicit attempt to flush all pending notes for some, if not most
plugin instruments (eg. VSTi), on playback stop.
- Fait-divers: desktop menu file touched to openSUSE conventions.
- Internal refactoring alert: Session and Options instances are now
being redesigned as singletons, preparing to get out of the way from the
master GUI/MainForm instance.
- Clip drawing methods refactored so let the fade-in/out handles get
seen with transparency over the clip graphics content.
- Reset and continue looping even still when continue past end transport
option is not set and playback is rolling.
Hope it makes through a Happy New Year with flying colors ;)
Cheers && Enjoy!
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
Hi,
this mail is a short reminder that the LAC2009(1) Call for Papers is currently
active and awaiting your papers at (2).
The paper submission period ends on
Thursday, January 15, 2009, 24:00 UTC
so use the (hopefully) free time of the Christmas holidays to get your paper
into shape and upload it in time!
Hope to see you there,
Frank, on behalf of the LAC2009 organization team
(1) The LAC (Linux Audio Conference) is an annual event where developers,
users and composers from all around the world come together for 4 days
to present current developments, new compositions and other news to the
public, listen to concerts, and generally have a good time together.
The LAC2009 is taking place at the Casa della Musica in Parma, Italy,
from April 16th to 19th, 2009. The conference homepage is at
http://lac.linuxaudio.org/2009/.
(2) Paper submission information:
http://lac.linuxaudio.org/2009/call-for-papers/
Paper submission upload form:
http://lac.linuxaudio.org/2009/openconf/openconf.php
"God does not play dice" said Einstein, but the assignment of IRQ's at
boot surely seems to be a bit of a random game (which only proves that
Linus isn't God, I suppose ...)
I would like to automagically increase the priority of the IRQ
associated with my soundcard - peek at "the dice" before placing my bet
so to say - how do I do that?
I used to have:
chrt -f -p 80 `pidof IRQ-20`
.. in rc.local, but sometimes the relevant IRQ changes to 19 (giving
IRQ-20 to something else), which may or may not cause a hanging system.
from (todays) /proc/interrupts:
[...]
19: 49 0 IO-APIC-fasteoi ehci_hcd:usb1,
uhci_hcd:usb2
20: 8416716 0 IO-APIC-fasteoi firewire_ohci, HDA Intel,
uhci_hcd:usb5
While attemting to install alsa1.0.18a on a system based on Linux2.6.24,
I am stuck with:
alsa-kernel/core/hrtimer.c:29: error: implicit declaration of function
‘hrtimer_forward_now’
This function was introduced with kernel 2.6.25 - which also happens to
be the first kernel where RT-patches breaks for midi.
Anybody has got an idea for a workaround?
Hi :)
I'm double-sorry if a mail some minutes before came through the list,
but while I take a look at my account on the homepage of my provider,
there seems to be something wrong. I take a breather and will read any
mails within the next days, but not today, I also can't reply to the old
thread from were I'm writing now.
I just want to inform, that I repaired Suse 11.0 for JACK, but that
there still is a problem for other people.
If someone will do a YaST2 update for all packages, if a newer version
is available, than only libjack will be upgraded, but not jack and then
their JACKs will be broken, so if people do an update and they have 1.
JACK installed and 2. the Packman repository enabled, at the moment they
need to take care about libjack, they need to manually keep libjack, or
they should disable the Packman repository. Status quo of this was at
around 19:50, then there was no 0.116 jack or jack2 available, but a
libjack 0.116.
Cheers,
Ralf
I'm not banned for some mailing list and some of the recipients are very
kind, but their lists are joined by people who maybe should pay
attention to this.
If you want people to report bugs, than
- don't laugh about them and say that they are the only one with that
problem and they should search the web before they do stupid bug
reports. Be careful, sometimes the user might have more knowledge and
you only think you're right.
- you say they are right, but the bug isn't caused by your software,
package-build, wiki, they should search the web and find out them self
where they have to report bugs. Users might be stupid, but they won't
report a bug for their office suit to ALSA and reporting a bug that has
to do with an audio application, might be reported to ALSA, JACK, the
kernel community, because they all have to do with such a bug
- allow people to report without getting subscribed
I'm suggesting this because I misbehaved, when I asked because of a bug.
Now I'm banned for a forum and a mailing list, but they grant me, that I
have pointed out something that was unknown.
But I wasn't the one who pointed out this bug, the web was full of posts
from other people, before I even noticed this bug. When they try to
report something and been laughed at etc., they don't go on like I did,
they won't be idiots like I'm. They won't be banned.
A lot of people change over to windows, a lot of people report bugs and
nobody cares about, a lot of people won't spend hours in reporting
something, by reading rules how to do this, e.g. I was exhorted to write
the German word "das" correctly, because there are rules, that this word
sometimes must be written "dass" instead of "das".
I often reported bugs to people who than said, they are making music too
and that bug didn't exist, a year later it's noticed in a developer list
and they have long threads about it and they wonder why nobody reported
this before.
People don't try to asked, because they have fear to asked in a wrong
kind, the wrong questions. If you report a bug you often hear use this
distro instead of this distro, if you don't like it, or use Windows
instead of Linux, if you don't like it. But you do like a special
distro, application etc. ...
Things went terrible wrong in the community and it's not a borderline
and dyslexic personality like me ... "normal" people have fear to use
Linux, to ask the community.
If anybody is interested in what I noticed about Linux audio and MIDI,
which bugs I have myself etc., I will go on, because I will stay at
Linux for nearly everything, but I guess I have to find something else
for multimedia. Hints for alternatives to Linux are welcome.
Don't worry, I won't write anything again if I'm unwanted.
Good luck for multimedia Linux!
Hi Gustin :)
it's easy to get named a troll. What should a user do, that has troubles
with JACK?
I like the 64 Studio community, unfortunately the version for the 64
Studio 2.1 stable version is 0.103.
It's silly if a user reports a bug about that version, while the JACK
developers needs statements about 0.116.
There are distros like Suse, that supports 0.116 by community packages,
e.g. for Suse it's the Packman repository.
I had contact to the packager by the Linux Club.
People reported that bug e.g. to the Ardour forums, a long time before I
had this bug. There they say, it's a JACK bug, but this isn't true, it
was a packman bug. http://ardour.org/node/2271
I don't want to talk again about this, because I'm personal involved in
this, maybe someone of those who replied off-list can give other
examples, I won't quote private mails.
Testing of RCs often is unwanted. I tried to make a howto and needed
help and that was unwanted. And people don't report bugs to the right
places, 1. because they don't know the right places and 2. because they
know, that they will get bashed.
When I reported the JACK package bug for Packman I get sarcasms. I was
a troll, who made everything wrong, because I have no knowledge. Nobody
but me should have this bug too, written by the packer, who asserted
that he makes music with the packages from Packman. This must be a lie,
because this package is broken for everyone.
1. If you like to help and write a howto, but you need some help because
you e.g. don't know that compilers differ for several Linux, you need to
add headers for some applications, than you do something that is unwanted.
2. If you report that something don't work, you need help, than you are
a troll, because it's not true.
I'm not the only one. Why can you find bugs in the web, that are not
reported to the right people?
I got mails off-list, with statements similar to "I recently got raked
over the coals by ...".
Which distribution can I use, that is wanted by the developers? How do I
have to report bugs? When I say "Hello, there's a bug" I don't want the
answer, that I'm a noob, nobody has this bug, while the whole community
has got the same bug.
I'm not the "Girl, interrupted" when I reported a bug and I'm not a
individual case. I get crazed, when people are unconvincable, they don't
need to excuse, while people like me get banned.
The only thing users can do, is to report bugs anonymous, in forums
somewhere in the web, instead of talking to the right people.
Misspelling for a user who reports something should be allowed.
Posting a bug that was posted before, should be allowed.
Posting a bug of a front or back end to the back or front end people
should be allowed.
To be stupid should be allowed.
But it isn't.
Cheers,
Ralf
PS: I have a bad conscience because I wrote this troll like stuff. I
also get off-list mails that this will break the work. But I guess it's
a topic, if Linux is also for Users. I never developed anything for
Linux, but I was a developer too. I don't understand the problem with
bug reports. At the moment it looks like I'm not banned in much mailing
lists, as it was written.
