I try to make some photos and twitter here and there about the linux
audio conference 2014.
Hashtag is #lac2014
Follow me or write your own!
https://twitter.com/NilsGey
Have Fun live or with the stream!
Nils
There is one usage case, i can call - reversing recorded piano and some other
instruments. One case, when sequencer and even instrument settings are not
last step before mastering. I'm not expert and at all badly aware of existing
music to mention examples, but i know at least one - in Black Mesa game - some
soundtracks, marked as "mesa remix". I don't see it bad to mention such stuff
there, since it is done completely by fans, no matter with what resources and
software.
Additionally, in gui clips may display inline status, with indicators for
direction and all other clip-individual info, such as speed (probably, that's
all - don't know, what other indicators are good to have there).
For the N-th time I've set aside a day to try and read
some of the ALSA documentation. For the N-th time I've
completely lost my way in a web consisting of
* The complete lack of any documentation that
explains the concepts, the big picture, and
the terminology.
* Completely useless docs, of the form:
function xxx_set_yyy (parm_zzz)
sets the yyy of xxx to zzz.
or similar, in other words something generated
automagically and completely uninformative and
redundant. In particalur if it's impossible to
find out what yyy is supposed to be or do in
the first place.
* Uncomprehensible English.
* When trying to learn something from actual
source code or examples, layer upon layer of
syntactic sugar making it virtually impossible
to understand what's going on.
All this more than ten years after ALSA was
announced. I *do* understand those hardware
manufactureres who just refuse to try and
write an ALSA driver.
In this case my very humble endeavour was just
to find out if or not it would be possible to
create something similar to the alsa_jack plugin
that would actually present itself as a sound
card, so that (badly written) apps would be
prepared to use it.
If someone knows the answer to that question
and can also explain it I'll commend him/her
in my prayers.
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
Hello everyone,
lately I had to fight big XRUN troubles, and thanks to this forum I
finally solved that. This excellent thread saved me:
http://linuxaudio.org/mailarchive/lau/2012/9/5/192706
On my long quest, I tried to see a little bit more what happened with
the IRQs on my system. I searched for a kind of 'top' utility to monitor
the interrupts, but the only apps I found were either deprecated, or
missed some cool features.
So, I ended up writing my own tool to monitor the file /proc/interrupts.
It's available a this address:
https://gitorious.org/elboulangero/itop
As its name indicates, it behaves pretty much like top, but for interrupts.
It's quite a simple thing, that I tried to enhance a bit with some cool
features:
+ refresh period can be specified.
+ two display modes: display interrupts for every CPU, or only a sum
of all CPU.
+ display every interrupt (sorted like /proc/interrupts), or only
active interrupts (sorted by activity).
+ in case the number of interrupts changes during the execution of
itop (due to a rmmod/modprobe), it's handled without any fuss.
+ command-line options are also available as hotkeys for convenience.
+ at last, the program display a summary on exit. The idea is that
this summary could be copied/pasted in emails to help debugging.
If anyone is interested, feel free to try and comment !
Cheers
The Guitarix developers proudly present
Guitarix release 0.29.0
For the uninitiated, Guitarix is a tube amplifier simulation for
jack, with effect modules and an additional stereo effect chain.
Among with a couple changes in the source and some bug-fixes, this
relase comes with a couple of new plugs (gx & LV2), were most of them
comes from our new Development Member Fedor Uporov.
The Simulation plugs been developed with the new Analog Circuit
Simulation Toolkit by Andreas Degert.
new plugs:
* Record Mono/Stereo (gx)
* JCM800PRE (Preamp simulation) (gx)
* GCB_95 (WahWah simulation) (gx)
* Duck Delay Mono/Stereo (gx / LV2)
* Reverse Delay (gx)
* Graphic EQ (gx / LV2)
* Ring Modulator Mono/Stereo (gx)
* Plate Reverb (gx)
* Panorama Enhancer (gx)
* Bass Enhancer (gx)
* BarkGraphicEQ (24band LV2)
Please refer to our project page for more information:
http://guitarix.sourceforge.net/
Download Site:
http://sourceforge.net/projects/guitarix/
Forum:
http://guitarix.sourceforge.net/forum/
Please consider visiting our forum or leaving a message on
guitarix-developer(a)lists.sourceforge.net
<mailto:guitarix-developer@lists.sourceforge.net>
Hello all,
anyone knows where to find a state diagram for PCM devices ?
What I want to find out in particular is
- if a device supports the pcm_resume() function, and it returns 0,
is a pcm_start() required or not (it is if pcm_resume() is not
supported) ?
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)