Hi!
A visually impaired Linux user here. I recently came across this great
thread[1] and decided to write this message. My goal is a little
different from the original topic author (generating MIDI via code VS.
recording via a keyboard) so I decided to start a new discussion.
Here's my situation (warning: very long post!):
First of all, I'm just an amateur and a beginner with nearly zero
knowledge about music production. I had very little contact with DAWs,
even in Windows... The closest I've gotten to a "DAW" that I tried to
use was Anvil Studio (many years ago), which wasn't accessible either.
The little that I know about MIDI editors and DAWs is from what I read
looking for such programs in Linux.
I'm using Slackware Linux, with Speakup[2] as my console screen reader
(with Espeak[3] through the Espeakup[4] connector, because I don't
have a hardware voice synth), and Orca[5] as the screen reader for X
(note: I use only ALSA, without Pulseaudio).
I'm trying to create some kind of audio setup for quite some time
(since around 2010). Back then, I read everywhere that it was needed
to recompile the kernel with a realtime patch. Then I found the
courage and did just that, but:
* I never got JACK to really work. It complained that the soundcard
was already being used, probably because of my screen readers which
are softsynths (again, I don't have a hardware synth nor a Braille
display), and I suspect they take all the soundcard for themselves.
JACK only got to start if I used a second soundcard, an M-Audio Fast
Track Pro (which I bought because it seemed to work on Linux), but it
didn't go too well either. Only much later (last year, 2013) I came
across this post
http://joegiampaoli.blogspot.com/2011/06/m-audio-fast-track-pro-for-debian-…
It seems the Fast Track Pro is already supported on newer (3.X)
kernels, but I still didn't test that.
* Most audio related apps were (and still are) made with QT GUIs.
Though QT's accessibility API exists for a long time (and is well
documented[6]), there were no means for Orca to communicate with it
yet, so all those apps were completely inaccessible.
* With the recompiled kernel, my video driver installation broke (I
wasn't even using proprietary drivers or anything). X only showed a
blinking cursor on the screen. Orca worked just fine, but it was a
problem when a sighted person needed to use the computer.
So, I went back to the stock kernel (where the video driver worked)
and gave up, for the most part. I settled on doing everything from my
keyboard (which requires some sighted assistance), then sending the
result as a wav file to my computer, then processing it with SoX[7]
(which I use all the time) and/or Ecasound[8]. But recently I began
thinking of using sounds from softsynths or other programs (for
example, LinuxSampler[9]) instead of my keyboard's internal sounds,
and for that, I think it would be best if I could record MIDI directly
into my computer. So, the search started again, and I began testing
some command line applications (most of which were already mentioned
on the thread in [1]):
* CuSe[10]: stands for "Cursed Sequencer", and like the name suggests,
is Curses based. Interestingly, it was made specifically with visually
impaired users in mind. Some features look interesting, like punch
in/out, a step sequencer, and (the most interesting of all) a "remote
control" like thing, where it's possible to configure key combinations
for controlling the software through the hardware synth's keyboard
(avoiding the need to run back and forth between the synth and the
computer). But it doesn't seem to have some features I want, like
adding/editing lyrics to the notes, MIDI CCs and SysEx events.
Unfortunately, I was never able to get any sound from it (be it
through FluidSynth or my MIDI keyboard).
* Midish[11]: already mentioned on the thread in [1], it supports
recording and playing MIDI, adding events and SysEx messages, and it
has nice filtering features, making it possible to split the keyboard
or transform one event into another. It only supports raw MIDI ports
and it took me a lot of time to figure that to make it work, I needed
to "modprobe snd_virmidi", then (a)connect the virmidi ports to my
synth's ports, then configure the inputs and outputs via the
"~/.midishrc" file. It was the program I got working more
successfully, and I placed my hopes on Midish for a long time, reading
and rereading the manual to see if I could make it do what I wanted. I
was able to record MIDI via my keyboard (though I wish there was a
"remote control" feature or something similar). However, sometimes I
also wanted to insert notes manually, and as already pointed out in
this message from the thread in [1]
http://lists.linuxaudio.org/pipermail/linux-audio-user/2014-February/096120…
that isn't the most intuitive task, and Midish doesn't seem to let me
add lyrics or edit notes (only cut/copy/paste measures)... Well,
unless I save the song to Midish's format and open it in a text
editor, but I don't want to have to memorize which note numbers are
which :P. Or unless I'm missing something else.
* Midiedit[12]: contrary to Midish, this only edits and doesn't
record. It's contained in only one file and is a Perl script. It has
two interfaces: a Curses based one and a "text editor" based one. With
the Curses interface, it can playback MIDI files (I used Aconnect to
hook its ports to FluidSynth and the sounds played), and as the name
suggests, edit. Events (notes, CCs, program changes etc.) can be
inserted, edited and deleted. They're displayed sequentially in a
list, one per line, with their starting position in ticks, duration
and channel. They can be navigated by using the Up and Down arrows,
then edited (the bottom screen shows the available actions and which
keys do what). One thing I love about it is that it plays back the
notes when the cursor focuses on them. Another thing is that it treats
each note as a single event, by matching the note ons with their
respective note offs, which makes managing notes much easier. So far
so good, but everything always has some "cons". I wish it could mute
or solo tracks, and have a separate view for each track. The search
function can be used to jump straight to the notes from a specific
channel, and cycle through the results with "n" and "N" (similar to
Vi/Vim), but the notes from the other tracks are still there and it
gets confusing easily (at least for me). It doesn't seem to have an
action implemented on the interface to handle lyrics and text events,
but these still can be edited through the "text editor" interface,
which is called "dump mode". In this mode, it opens your text editor
of choice (the one in the "$EDITOR" environment variable) and
represents the MIDI file's contents as readable Perl code (based on
the dump output from the MIDI::Perl[13] module). All events (including
text events, lyrics and SysEx) can be edited this way, (although
obviously it doesn't play back the notes, and we don't have the luxury
of the unification of note ons and offs). After saving and closing the
editor, the Perl code is processed and the content is written back to
the MIDI file.
* From the same author of Midiedit, there are other interesting Curses
based MIDI tools[14], like Midifade[15], which generates "sliders"
for controlling MIDI events through the PC keyboard (on the command
line, we specify how many sliders to generate, the ALSA port, the MIDI
channel and which event each slider will control), and can, for
example, change Ecasound's controller parameters, or the "knob"
parameters from a softsynth.
That's it for the CLI apps I tested. Midish and Midiedit are the ones
I had most "luck" with, but my attempts with them weren't that
productive either.
My search for an accessible MIDI editor or DAW continues. Recently, I
updated Slackware to 14.1. I'm using the stock kernel, no realtime
patches or anything yet. First I want to know if I really need it (I
read that because of changes in recent kernels, RT patches aren't
strictly necessary anymore), and if there's some app that I'm able to
use (if not, there's no point to even try compiling a realtime kernel
:P). I finally got the QT-AT-SPI[16] bridge to compile, meaning I can
access QT GUI apps to some degree now. So, I decided to test some of
the most popular Linux DAWs, those QT based audio apps that taunted me
since I first read about audio production on Linux (basically, the
only options that were available and which I couldn't use).
>From the list of features I read, the one that appealed to me the most
was MusE[17]:
* The possibility of mixing MIDI with audio (samples, loops, vocals etc.).
* Instrument definition files for various brands of keyboards that
ease the use of those synthesizers, making it so that we don't need
to memorize patch names/numbers and controller numbers.
* MIDI recording.
* Editing of all types of MIDI events. Besides the visual editor,
there's a "event list editor" (I suppose it's something like in
Midiedit), so maybe it could work for me.
* A few internal instruments (some synths and a FluidSynth frontend).
* DSSI support.
* (apparently) native VST support too (and I assume, a few Windows
VSTs through DSSI-VST).
* And the "remote control" feature :D!
Of course there's the multitude of functions that depend on the mouse
(which I can't use), but it seems to have customizable shortcuts. It's
a graphical application, obviously very far from being text-based, but
I read that it also has some Python bindings, so maybe a few things
can be scripted...?
However, sadly, all isn't as good as it sounds. I installed MusE 2.1.2
and opened the interface. The menus work fine, but the screen reader
has problems reporting the interface elements (for example, it says
"spinbox" or "checkbox" but doesn't specify wish item that control
corresponds to. The "MusE Settings -> Global Settings" screen is full
of these examples and unreadable through the screen reader). I just
took a quick "look" at the interface to have an idea of what the
screen reader could read. I didn't test recording or anything yet,
mainly because of the aforementioned problem with JACK, nor could sort
out the setup part about "/dev/rtc"...
While we're on the subject of MusE, a question for the "MusErs": if I
don't use JACK (or use the "-a" switch), won't MusE ever play anything
through the PC's speakers (imported audio, internal instruments,
FluidSynth soundfont sounds)? Or will it just be unable to communicate
with JACK aware applications?
I'm thinking if I'll insist on MusE for a bit more, and if I do, maybe
I'll contact the developers about the accessibility issues.
Based on my limited knowledge of MIDI editors and DAWs which I
acquired from what I've tested or read about so far, desired features
for my dream DAW would be:
* Curses based interface.
* Both JACK and some form of ALSA Seq support (even if it's only with
raw MIDI ports, or some workaround involving sending commands through
Amidi :P). JACK would be for more complicated setups. ALSA would be
for when I only want to do some quick MIDI editing and don't want to
use a second soundcard just because of JACK (I need my screen reader,
so I can't turn it off to free the first card).
* Playback of MIDI files.
* Support of a metronome click, and a "count in" feature for recording.
* A "remote control" feature, or a way to start recording (or the
count in) only when I press a key on my hardware instrument.
* Each note shown as only one event, by matching the note on with it's
respective note off. This way we don't need to struggle scrolling
through the events trying to match the ons and offs.
* Possibility of inserting/editing/deleting all types of events,
including text events, lyrics and SysEx messages.
* A way to select a track to be "active".
* A separate list of MIDI events for each track (only showing the
contents of the "active" track), where events can be browsed with
arrow keys and be edited or deleted. Also, the possibility of
inserting new events through the interface (without using the MIDI
keyboard).
* Playback of notes when the cursor focuses on them.
* Ability to mute and solo tracks.
* Support for instrument definition files, to ease the use of hardware
synths (maybe some softsynths too). With that, I'd be able to select
the patches and controllers specific to my hardware synth directly
from the computer and with help of my screen reader, reducing the need
of asking for sighted assistance to know the patch names.
* DSSI support, or the possibility of interacting with some command
line based DSSI host.
* The ability to assign the MIDI channel and an instrument
(ALSA/JACK/whatever ports and patch names) to each track (or is this a
work better suited to a "patchbay" like app?).
* Rendering of MIDI tracks to audio with the used synths' sounds.
* Customizable keyboard shortcuts.
* Some form of scripting support, like Perl or Python or Lua bindings,
and the ability to assign user scripted functions to some keybinding
in the editor.
Some more complex features:
* The ability to have both MIDI and audio in the same project. The
audio doesn't need to be editable (just "importable"), only needs to
have its starting position adjustable to be in sync with the MIDI
tracks (triggered via some MIDI event maybe?).
* Recording of MIDI while playing back the audio tracks, keeping them in sync.
* Maybe a pattern editor, where the lists of events become a phrase,
chains of phrases make patterns and chains of patterns make a song
(but maybe it's too complex and is a discussion for another day :P).
And that was my utopic idea for an accessible Linux DAW. I don't know
how hard it is to implement all of that, specially the "MIDI alongside
audio" part. Unfortunately I understand nothing about audio
programming (honestly, I already tried :P) and very little about music
production, so a lot of features I pointed out might be complete
nonsense, or might be accomplished in a much better way (if anyone
knows a way, preferably via command line, please let me know).
As for the "patchbay" (with "jack_connect" etc.), I think even a
simple Shell Script with Dialog based menus would be fine.
As for post processing and mixing (applying LADSPA/LV2 effects etc.),
it can be left to some other app (Ecasound for example) after all
tracks are rendered to audio.
And last but not least, on the thread in [1], I found Teqqer[18]. I
couldn't test it yet because of the JACK problem (I seriously need to
sort that out), but I took a look at the default config variables in
the Python source code, and it looks like scripting support and
customizable shortcuts are mostly taken care of. From what I
understand from the shortcuts, the interface for inserting/editing
MIDI events is a bit similar to Midiedit (Up/Down to cycle through
events, although note ons and offs are separate) and it seems to have
one view for each track (Left/Right to cycle through tracks), and it
even supports patterns! :D So, minus the recording part (from what I
understood, it wasn't made for that), the lack of ALSA (without JACK)
support, I think it has the potential to become something like what
I'm looking for (plus, I always wanted to try a tracker, but never
found a "screen reader friendly" one). I'll definitely be watching
Teqqer to see where it goes!
While my dream DAW doesn't come true, does anyone know a command line
way to record MIDI while simultaneously playing an audio file and
keeping both in sync (even if it involves JACK)? I think Ecasound can
be setup to do the opposite, playing back a MIDI file while recording
audio (but it doesn't support MIDI recording, just playback... Or does
it? :P).
Well, that's it. Sorry for the overly long post. Thanks for your time!
[1]: http://lists.linuxaudio.org/pipermail/linux-audio-user/2014-January/095910.…
[2]: http://www.linux-speakup.org/
[3]: http://espeak.sourceforge.net/
[4]: https://github.com/williamh/espeakup
[5]: https://wiki.gnome.org/Projects/Orca
[6]: http://qt-project.org/doc/qt-4.8/accessible.html
[7]: http://sox.sourceforge.net/
[8]: http://nosignal.fi/ecasound/
[9]: http://www.linuxsampler.org/
[10]: http://pi4.informatik.uni-mannheim.de/~haensel/cuse/index_en.html
[11]: http://www.midish.org/
[12]: http://www.pjb.com.au/midi/midiedit.html
[13]: http://search.cpan.org/perldoc?MIDI
[14]: http://www.pjb.com.au/midi/index.html
[15]: http://www.pjb.com.au/midi/midifade.html
[16]: http://projects.kde.org/qtatspi
[17]: http://www.muse-sequencer.org/
[18]: https://github.com/fps/teqqer
--
____________________
Blog: http://aiyumi.warpstar.net/
Hello,
After an intensive development of my ten year old project Wav Composer
Not toilet, from September 2013 up to the new year, I was intending to
make a new release in February, and then March, and then...
Unfortunately an official release has not materialized so I'm just
saying here is the code, do what the kcuff you like with it.
-=-=-=-=-=-= What?
Wav Composer Not Toilet is a text based non-professional non-realtime
non-interactive modular audio synthesis, sampler, and sequencer by a
hobbyist developer scratching an itch which has eased off for now.
-=-=-=-=-=-= What's new?
The main focus of recent development was intended to create greater
flexibility for the user in how modules and 'data objects' are
specified within a file. This flexibility allows:
* arbitrary ordering of items
* optional items
* optional groups of items
* multiple choice items
* self connection of optional inputs
This is available in the master branch and can be built like so:
git clone https://github.com/jwm-art-net/wcnt.git
cd wcnt
sed -i 's/DEFS=-ggdb/#DEFS=-ggdb/' Makefile
make
make examples
(the sed command above will remove debugging info that should be
removed in a release). After running `make examples` look in the
examples/ directory to see what wcnt has done.
Wav Composer Not Toilet is hardcoded to use a limited selection of
LADSPA plugins and no others, these are:
* Bode Frequency Shifter
* C* PlateX2
* DC Offset Remover
* Fast Lookahead Limiter
* Glame Low and High pass filters (+ Butterworth versions)
* Single Band Parametric EQ
The examples will fail to complete if these are not available. They
reside in the C* (formerly Caps) and SWH LADSPA plugin suites.
However, in the custom_names branch on github a generic LADSPA module is
available which allows specification of arbitrary LADSPA plugins. It is
working to a basic extent but unfinished.
Carry on.
char*s
James Morris
Hello everybody
I mainly read the ML and apologize in advance for the annoyance of such
a dumb question, but I have been in search of a good synthesis-only
percussive sound generation solution for so long I cannot remember.
When I play with the latest sunvox, that I use on mobile platforms
(Meego / Harmattan and Maemo) and hear the wonders that Alex made with
the kicker and DrumSynth module, I really wonder how come are there no
such thing as a solid (Native, ideally LV2, but realistically DSSI)
drumsynth plugin? Or maybe I'm missing something?
I would really like to.
Phil
--
Philippe Coatmeur
* http://opensimo.org/play
* http://opensimo.org/adamweb/
* https://github.com/xaccrocheur
On 04/03/2014 09:58 PM, Chris Bannister wrote:
> On Wed, Apr 02, 2014 at 07:26:25PM -1000, david wrote:
>> Who knows, maybe 300-400 years from know, today's rock operas will be high
>> opera! Complete with the fat lady singing and scholarly musicologists
>> writing dissertations on the use of pinball machines as musical
>> instruments...
>
> Ummm, it has already been done! Tommy. :)
> http://en.wikipedia.org/wiki/The_Who's_Tommy
> http://www.youtube.com/watch?v=ZfZQLXs72Lo
Thanks, only that's a musical, not an opera. ;-)
Of course, at the rate that English has been changing over the last
800-1000 years, by then our idea of English will probably be
incomprehensible to whoever's alive then ...
My guitar instructor in high school was lead guitarist in one of the
local bands of the time. He wrote a rock opera and performed it with his
band to get his Masters degree in Communications.
--
David W. Jones
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://dancingtreefrog.com
Hey,
I like to open a discussion about Bitwig and what 'we' (users, but
mostly developers) can learn from it.
I worked just about 30min with Bitwig so far. Just a few thoughts.
What is nice to notice is that the actions you try to do as a user is
possible pretty often. They seems to know which actions
computermusicians tend to perform and they make that possible in an easy
way.
Automation is very smooth it seems.
It's also a nice feeling that you work with a finished product, good
chance you can make and finish the project you've in mind.
It's handy that it comes with a bunch of samples, but why can't we make
a sample pack and make that easy to install on Linux and add it
(automatically) to let's say Qtractor?
The sound quality of the included instruments seems to be ok, but I
doubt whether it is comparable to stuff like AMS/Ingen, zynaddsubfx,
pianoteq.
Making a good song is still hard, also in a sophisticated application
like Bitwig.
For very advanced features you probably need Bitwig, but the tools on
Linux aren't bad I think. I'm asking myself how big the gap is. To me it
looks like the gap itself is not that big, but the last 10% of finishing
and polishing an app, makes a huge difference for the end user. The
Linuxaudio Floss tools lacks that finishing touch, completeness and
level of integration pretty often (which is logical if you look at the
manpower).
Regards,
\r
Hello,
I've been using a realtime kernel some time ago. I hadn't a very
intensive use of it so I didn't even notice if its configuration was
very right or wrong, it seemed fine, but I ended up uninstalling it and
doing fine without.
As of now I'm running Debian Jessie, and lately I've been trying the
latest kernel Debian from their repos (currently, from wheezy-backports).
However, JACK can't seem to get to work with realtime. Here is part of
the log:
14:11:39.082 JACK démarre...
14:11:39.083 /usr/bin/jackd -r -dalsa -r44100 -p512 -n2 -D -Chw:Pro,0
-Phw:Pro,0
Cannot connect to server socket err = Aucun fichier ou dossier de ce type
Cannot connect to server request channel
jack server is not running or cannot be started
14:11:39.110 JACK a été démarrer avec le PID=3903.
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve
property `GtkRange::activate-slider' of type `gboolean' from rc file
value "((GString*) 0x1cb8c40)" of type `GString'
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
jackdmp 1.9.10
Here is the content of /etc/security/limits.d/audio.conf
# Provided by the jackd package.
#
# Changes to this file will be preserved.
#
# If you want to enable/disable realtime permissions, run
#
# dpkg-reconfigure -p high jackd
@audio - rtprio 95
@audio - memlock unlimited
#@audio - nice -19
Note: the dpkg-reconfigure is "wrong" since in my case I use "jackd2".
Content of /etc/default/rtirq:
(...)
# IRQ thread service names
# (space separated list, from higher to lower priority).
RTIRQ_NAME_LIST="rtc snd usb i8042"
# Highest priority.
RTIRQ_PRIO_HIGH=90
# Priority decrease step.
RTIRQ_PRIO_DECR=5
# Lowest priority.
RTIRQ_PRIO_LOW=51
# Whether to reset all IRQ threads to SCHED_OTHER.
RTIRQ_RESET_ALL=0
# On kernel configurations that support it,
# which services should be NOT threaded
# (space separated list).
RTIRQ_NON_THREADED="rtc snd"
# Process names which will be forced to the
# highest realtime priority range (99-91)
# (space separated list, from highest to lower priority).
# RTIRQ_HIGH_LIST="timer"
Results of a few commands,
$ uname -a
Linux cacacomp 3.12-1-rt-amd64 #1 SMP PREEMPT RT Debian 3.12.9-1+rt1
(2014-02-20) x86_64 GNU/Linux
$ cat /boot/config-3.12-1-rt-amd64 | grep PREEMPT
CONFIG_TREE_PREEMPT_RCU=y
CONFIG_PREEMPT_RCU=y
CONFIG_PREEMPT_NOTIFIERS=y
CONFIG_PREEMPT=y
CONFIG_PREEMPT_RT_BASE=y
CONFIG_HAVE_PREEMPT_LAZY=y
CONFIG_PREEMPT_LAZY=y
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT__LL is not set
# CONFIG_PREEMPT_RTB is not set
CONFIG_PREEMPT_RT_FULL=y
CONFIG_PREEMPT_COUNT=y
CONFIG_DEBUG_PREEMPT=y
# CONFIG_PREEMPT_TRACER is not set
$ cat /boot/config-3.12-1-rt-amd64 | grep _RT_
CONFIG_RT_MUTEXES=y
CONFIG_PREEMPT_RT_BASE=y
CONFIG_PREEMPT_RT_FULL=y
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# lsusb
Bus 002 Device 003: ID 5986:0315 Acer, Inc
Bus 002 Device 004: ID 0763:2012 Midiman M-Audio Fast Track Pro
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
=> I have a M-Audio Fast Track Pro USB card.
# grep CONFIG_RT_GROUP_SCHED /boot/config-3.12-1-rt-amd64
#
(empty, this string isn't in my kernel config file)
I realize I didn't tick "realtime" in qjackctl, so I start it again but
JACK log is the same:
15:12:46.782 JACK démarre...
15:12:46.783 /usr/bin/jackd -v -dalsa -r44100 -p512 -n2 -D -Chw:Pro,0
-Phw:Pro,0
Cannot connect to server socket err = Aucun fichier ou dossier de ce type
Cannot connect to server request channel
jack server is not running or cannot be started
15:12:46.797 JACK a été démarrer avec le PID=7290.
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
jackdmp 1.9.10
...
There are very few references of this specific error message I found on
the web, but none seem to be related with my case.
# service rtirq status
PID CLS RTPRIO NI PRI %CPU STAT COMMAND
45 FF 90 - 130 0.0 S irq/8-rtc0
556 FF 85 - 125 0.0 S irq/43-snd_hda_
429 FF 80 - 120 0.0 S irq/16-ehci_hcd
430 FF 79 - 119 5.3 S irq/23-ehci_hcd
44 FF 75 - 115 0.0 S irq/1-i8042
43 FF 74 - 114 0.6 S irq/12-i8042
30 FF 50 - 90 0.0 S irq/9-acpi
128 FF 50 - 90 0.0 S irq/40-ahci
424 FF 50 - 90 0.0 S irq/41-mei_me
431 FF 50 - 90 0.0 S irq/16-mmc0
456 FF 50 - 90 0.6 S irq/18-rtl_pci
499 FF 50 - 90 0.0 S irq/16-jmb38x_m
522 FF 50 - 90 0.0 S irq/42-i915
2675 FF 50 - 90 0.0 S irq/44-eth0
3 FF 1 - 41 0.0 S ksoftirqd/0
19 FF 1 - 41 0.0 S ksoftirqd/1
$ ./realTimeConfigQuickScan.pl
== GUI-enabled checks ==
Checking if you are root... no - good
Checking filesystem 'noatime' parameter... not found - warning
/boot does not have the 'noatime' parameter set
For more information, see
http://wiki.linuxaudio.org/wiki/system_configuration#filesystems
Checking CPU Governors... CPU 0: 'powersave' CPU 1: 'powersave' - not good
Set CPU Governors to 'performance' with 'cpufreq-set -c <cpunr> -g
performance'
See also: http://linuxmusicians.com/viewtopic.php?f=27&t=844
Checking swappiness... 60 - not good
** vm.swappiness is larger than 10
set it with '/sbin/sysctl -w vm.swappiness=10'
See also: http://linuxmusicians.com/viewtopic.php?f=27&t=452&start=30#p8916
Checking for resource-intensive background processes... none found - good
Checking checking sysctl inotify max_user_watches... < 524288 - not good
increase max_user_watches by adding 'fs.inotify.max_user_watches =
524288' to /etc/sysctl.conf and rebooting
For more information, see
http://wiki.linuxaudio.org/wiki/system_configuration#sysctlconf
Checking access to the high precision event timer... readable - good
Checking access to the real-time clock... readable - good
Checking whether you're in the 'audio' group... yes - good
Checking for multiple 'audio' groups... no - good
chrt: failed to set pid 0's policy: Opération non permise
Checking the ability to prioritize processes with chrt... no - not good
Could not assign a 80 rtprio value. Set up limits.conf.
For more information, see
http://wiki.linuxaudio.org/wiki/system_configuration#limitsconfaudioconf
Checking kernel support for high resolution timers... found - good
Kernel with Real-Time Preemption... found - good
Checking if kernel system timer is set to 1000 hz... not found - not good
Try setting CONFIG_HZ to 1000
Checking kernel support for tickless timer... not found - not good
Try enabling tickless timer support (CONFIG_NO_HZ)
== Other checks ==
Checking filesystem types... ok.
not found.
** Warning: no tmpfs partition mounted on /tmp
For more information, see:
- http://wiki.linuxaudio.org/wiki/system_configuration#tmpfs
- http://lowlatency.linuxaudio.org
** Set $SOUND_CARD_IRQ to the IRQ of your soundcard to enable more checks.
Find your sound card's IRQ by looking at '/proc/interrupts' and lspci.
So, I'd like to know what prevents Jack from getting RT priorities.
And that's about all. I'm stuck. Hope you guys see where is the problem
more than I do and can point my to some direction.
Regards,
01
Here is a link to a public beta of my new VST plug-in, a spectral delay
effect - http://lanternfishaudio.wordpress.com/downloads/. It is only
available on Linux for the time being and the GUI will stop loading in
2014.07.01 but audio processing part will still work. After that time
either the beta period will be extended, the plug-in released commercially
or if there is not enough interest as open source. There is a manual
explaining how to use or install it. It is still in fairly early stages of
developments but should be usable for most users with decent hosts.
It will work on Renoise and Ardour 3 and does not work on Qtractor 0.5.11
which reports it's sampling rate as 0 which, while a perfectly respectable
number, is not a valid sampling rate IMO.
