This is a call-for-testing of my new ALSA driver for Digidesign 002/003
family. If you have these devices, would you please test the driver with
your devices and report your experience about it.
Especially, I want you to test MIDI port for machine control, because
developers have no 'console' models, just tested with 'rack' models.
When installing and testing, please follow this instructions:
Patchset was already posted to alsa-devel and confirmed to
playback/capture PCM samples/MIDI messages by ALSA applications.
[alsa-devel] [RFC v2][PATCH 00/11] digi00x: new driver for Digidesign
Several issues are still remained:
* The port for MIDI machine control message is not tested yet, because
002/003 console model are required.
* When allocates 2 or more channel numbers for the device, after 15 to
20 seconds from playbacking, any PCM samples causes noisy sound. Then,
all of LED on the front panel light. The streaming still continues
* The actual effects of external clock source is not clear. When set
the clock source is somewhat external, even if stopping the clock
source, the device continues to sound PCM samples against my expectation.
* The meaning of asynchronous messages is unknown. This patchset adds a
functionality to receive it in userspace. You can test it with updated
libhinawa sample script.
In my plan, this patchset will proposed for Linux 4.2. But these issues
need to be clear till the merge-window.
been pushed to the guitarix git repository. Those are simulations of the
Fuzz Face JH1
Fuzz Face Fuller Mods
Fuzz Face Roger Mayer
Sustainer+Muff (Big Muff Pi)
High Frequency Brightener
They are generated from schematic files, with our Ampsim Toolkit.
Schematic files (gschem) been included in the tools directory.
As root, starting JACK1 0.124.1 on an almost totally vanilla
3.19.2-1-ARCH kernel fails. Output of kernel with JACK1 issue is
pasted below. The same system works fine with the 3.18.9-rt5-1-rt
Running "groups" tells me there is no group other than "root", so JACK
seems to misinterpret that there is an audio group on the "broken"
Any suggestions as to what's going on? Thanks, -Harry
PS: I'm aware of the reasons to not run JACK as the root user or login
as root for daily use.
 Output while running "broken" kernel:
[root@audio ~]# jackd -ddummy
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben
Hohn and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK is running in realtime mode, but you are not allowed to use
Your system has an audio group, but you are not a member of it.
Please add yourself to the audio group by executing (as root):
usermod -a -G audio (null)
After applying these changes, please re-login in order for them to take effect.
You don't appear to have a sane system configuration. It is very likely that you
encounter xruns. Please apply all the above mentioned changes and
start jack again!
I've been playing around with libsndfile, libvorbisfile, libmodplug, and
libao to provide background music and sound effects for a game engine. I
have a solid handle on making one noise at a time, but I don't understand
mixing. At first I thought I would have to write my own mixer and handle
the channels, sample rate, and sample size issues myself. I really don't
want to have to do that. Then I noticed in the libao documentation that
nothing says that I cannot spawn two threads, each of which calls
ao_open_live() and ao_play() on different sound files. Indeed, the docs
for ao_initialize() seem to suggest this can be done with the statement
that it be called in the main thread.
I tried this and it works so erratically that I'm not sure libao was
written with this in mind. I get these results in order of likelihood:
1) "Segmentation fault"
2) "*** glibc detected *** ./threadtest7: malloc(): memory corruption
(fast): 0x0000000001bc5390 *** Bus error"
3) "*** glibc detected *** ./threadtest7: double free or corruption (out):
4) A bit of the first file, then the second file.
5) Only the second file.
6) Both files messily mixed with a zipping noise. (very rare)
Is libao in fact intentionally capable of doing this? If not, what are my
options for mixing music and sound effects? I really don't want to use
SDL_mixer for a variety of reasons, chiefly because my program is
terminal-only. Virtual beer if you can guess what the program is.
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
Q: What is the most annoying thing in e-mail?
Hi guys, I've started/hacked a small project called GuitarSynth. It is
meant as a playfield for exploring pitchdetection and synthesis for
Guitar, since I'm a guitarist. You can get on Github (git clone
Its really basic but its fun to play with. It take an audio signal (your
guitar) extracts the fundamental pitch and drives some wavetable synths.
Feel free to manipulate it, I'll be happy to grant people write access
to the repo.
Btw on IRC my Nick is JimsonDrift, the name of my band (see
As promised just at the closing ceremony of LAC, an email opening the
discussion of User Experience on Linux Audio. To all Developers,
please use this as a checklist and consider supporting each item. It
will improve the user experience.
1: Splash Screen
If an app takes more than one quarter of a second to open, use a
splash screen to give feedback. Feel free to contact me directly to
collaborate on a splash screen graphic if necessary. Ensure the splash
is shown immediately, before lengthy operations such as scanning for
files or loading content.
Synths and Effect plugins often provide presets - show a preset
selection "in" the main UI, or 1 click away. A fast way to browse
presets greatly enhances UX when searching for a sound. Ideally
support "scroll-wheel" interaction for changing presets.
- Ctrl Q, Quit
- Ctrl W, Close Project
- Ctrl S, Save
- Ctrl Shift S, Save As
- Escape, Context sensitive "close"
I'm aware most of the recommendations above are obvious, and that many
programs support these already.
"Tim E. Real":
> > 6: Now turn the mouse pointer back on. Done.
> Ehm, missed on of the best parts:
> 6: Now return the mouse pointer to where it was when originally clicked.
> 7: Now turn the mouse pointer back on. Done.
Sounds like the perfect way to do it, and Radium works exactly the same way:
(that's a 60fps video. Firefox doesn't seem to display 60fps videos
correctly. Chrome does though)