> I'm hoping that you're thinking of a realtime display, in which the
> peaks roll off to create a true waterfall effect.
Baudline (http://www.baudline.com) is a fantastic viewer that does fft
cascade. I've used it for a couple of years, and it is great for figuring out
how different sounds "work", and it has an oscilloscope-type display as well.
Cheers,
Jason Downer
Hello.
I finally started making my pet music project and realized I need a
drum synth to make some cool sounds. psindustrializer is good but also
need some tr-909-style sounds. I remeber from my old windoze days I
used a nice piece of software called Stomper. Does anybody know any
software for linux with comparable capabilities? Or we need to write
one?
Stomper does not work under wine :(
Thanks.
Hello.
I had a couple of articles on drum synths. Check
ftp://ftp.funet.fi/pub/sci/audio/devel/lad/drumsynth/
I built the circuit in a00*.jpg at the time when this article
was fresh. The article b00*jpg mentions an earlier article.
I will check that out at library.
Hmm.. I coded a drum synth for Commodore VIC-20 at the time.
VIC provided an audio chip with three oscillators, noise,
and a common volume if I remember correctly. What I did was to
modulate osc pitch and volume parameters with a fast and accurate
(compared to Basic) assembly code. The drum sounds were assigned to
the keys. This was about 1984, inspired by Yamaha's digital RX drum
synths, not by analog drums.
Juhana
--
http://music.columbia.edu/mailman/listinfo/linux-graphics-dev
for developers of open source graphics software
>From: "Levi D. Burton" <ldb(a)puresimplicity.net>
>
>does the idea of documenting various lad design patterns make
>sense to anyone?
Such "LAD Gems" doc would be much needed here too.
(For audio dsp gems, take a look at "musicdsp.org".)
I would appreciate if somebody would take a look at
Ardour and document best gems found there. E.g., the GUI
and audio thread separation and start up sequences.
Likewise for Linuxsampler and one of its GUI frontends.
Juhana
--
http://music.columbia.edu/mailman/listinfo/linux-graphics-dev
for developers of open source graphics software
Hi.
I am sure this sounds a bit crazy to some of you, but be ensured,
I am not (yet) completely out of my mind and there are actually
real reasons for doing what I do :-).
I am now running jackd from within Emacs, using jack.el.
Find it here: http://delysid.org/emacs/jack.el
Basic usage:
* Install the elisp file and put (require 'jack) in your .emacs.
* Customize startup options: M-x customize-group RET jack RET
* I.e. jack-sample-rate and jack-period-size are two important candidates.
* Start jack: M-x jack-start
You will see the verbose output in a special buffer called *JACK output*.
* If you want/need to get rid of your jack instance, simply do
M-x jack-kill RET
* If you changed sample rate or any other startup parameter, do
M-x jack-restart RET
to make them effective.
Plans:
* Do something useful with xrun output, maybe some stats (suggestions?).
* Add support for dummy and oss drivers, and add remaining ALSA
params.
* Write a patchbay based on jack_lsp and jack_{dis,}connect.
Why am I doing this?
You might have noticed I am recently seriously working on
Emacs extensions related to Sound and audio. osc.el is working
nicely and om.el, a client to drobillas om-synth is just waiting
for a polish up. midi.el is parsing binary data already and
needs a bit more careful planning before it can really grow.
The idea behind jack.el was that I basically got fed up by jack
wasting either a virtual console, or a screen window. Both dont really
offer confortable scrollback, so the idea to make jack run from
within Emacs, and collect all its output into a Emacs buffer was born.
Some nice sideeffects: Load statistic is collected in a variable,
so if you are into elisp, you can do fancy stuff like:
(with-current-buffer (jack-output-buffer) jack-load)
to retrieve the current load :-)
Combine all this with things like csound-x (Csound support for Emacs)
and the SuperCollider Emacs frontend, and you get a truly
powerful composition and experimentation environment.
One day I'll learn CLM and CM, and add it to the mix as well :-)
--
CYa,
Mario
hi all,
i'm currently working on a rather large project which i'd like to
fully support under Linux .. it requires, however, a functioning MIDI
sub-system. for this reason, i'd like to ask members of LAD to
report on their experiences with using professional MIDI interfaces,
such as (for example) the Motu MTP AV, Digidesign MIDEX-8, etc?
what is the 'easiest' MIDI interface to get working under the average
Linux kernel? what sort of experiences do folks have with getting
MIDI working (on a programming level) using API's such as (but not
limited to) ALSA, and MidiShare?
for me so far, MidiShare seems to offer the most direct and usable
approach .. while ALSA is wraught with complexity and dependencies
which often seem out of control. i'd like to know what your
experience, as developers, has been with getting a working MIDI
subsystem under Linux ...
--
;
Jay Vaughan
Greetings:
I recently submitted another article for my monthly column at Linux
Journal on-line, it should show up within the next few days. I wanted to
let LA* folks know that I've placed the article's two short example
files here:
http://linux-sound.org/lj-seq24-examples.html
They aren't finished pieces, nor were they meant to be (though I'm
liking them enough to maybe work on them some more). I made them as
examples of what can be done with seq24 and a batch of Linux softsynths
(and one VST plugin). I had an enormous amount of fun doing these
pieces, and I want to extend great thanks to Rob Buse for seq24 and Nick
Dowell for amSynth.
The state of things in our little world is getting to the point where
it gets harder to write about the stuff because I'd really just rather
be making music with it. Vast thanks to all Linux audio developers for
making dreams come true. You guys rock, every one of you.
Now if I can just get seq24 working with JACK... ;)
Best regards,
Dave Phillips
With the recent adoption of the realtime rlimits patch into the mainline
kernel, people have needed a way of utilising this for their music software.
There is apparently a PAM module out there which can be used if one's system
uses PAM, but for people on Slackware (which doesn't use PAM) - and perhaps
other distributions as well - this is not an available option.
set_rtlimits is a small program I hacked up over the weekend to allow
controlled non-priviledged access to realtime scheduling through the new
RTPRIO resource limit. set_rtlimits needs to be setuid root but it only
runs at elevated priviledges when setting the resource limits. Furthermore,
the users who are permitted to use set_rtlimits are controlled through a
hardcoded central configuration file (/etc/set_rtlimits.conf), as are the
programs those users can run via set_rtlimits and the maximum realtime and
nice priorities the users can request for each program. Programs must be
specified using absolute paths, so a malicious user can't just run their own
ardour binary, for example.
There is no homepage for this yet; simply grab the source from
http://www.physics.adelaide.edu.au/~jwoithe/set_rtlimits-1.0.0.tgz
Documentation is by way of the included README and manpage.
Note that this is not polished software. It's not autoconf-ised, although
hopefully it won't require too much tweaking to compile on a variety of
systems. It probably isn't written in a very portable way, and although it
poses no security issues to the best of my knowledge (beyond the usual
issues with setuid root programs and realtime priorities) it has not been
extensively audited. Having said that it gets the job done for me and might
be useful for others. My time is limited at present which is why the rough
edges remain.
Development was done under Slackware 10.0 running kernel 2.6.12-rc5. Using
this program I have successfully run Ardour 0.9beta29 and muse 0.7.2pre1
with Jack 0.99.73 under 2.6.12-rc5 for short periods.
Bug reports, improvements, suggestions and patches are welcome; send to the
email address included in the tarball documentation.
Regards
jonathan
qjackLaM is a Latency Meter for jack.
There are 2 JackClients now: 1 only outputs, the other only reveives.
This should cause 0 impact on Jacks graphordering concerning the other clients.
Also new: qjacklam measures ALL possible ways by itself and displays the results in a table.
Get the source, cvs and fc3-binary via
http://developer.berlios.de/projects/qjacklam
.
have fun
Karsten
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
Version 0.2.1 of the Oscilloscope DSSI plugin is now available here:
http://www.student.nada.kth.se/~d00-llu/music_dssi.php?lang=en
It has fixes for some bugs spotted by Sean Bolton:
- The GUI will now actually quit when it receives a /quit command from
the plugin host
- There will be no /tmp/dssi_shm_tmpfile_* files left behind when the
plugin and GUI exits
- The Makefile uses pkg-config to get the compiler flags for DSSI, so
it should work now even if your DSSI header is installed in a
non-standard directory
Thanks to feedback from Sean Bolton and Chris Cannam on the DSSI
mailing list I know also know that the plugin works with
ghostess-20050516 and the latest CVS version of Rosegarden (but not
with any releases of Rosegarden).
--
Lars Luthman
PGP key: http://www.d.kth.se/~d00-llu/pgp_key.php
Fingerprint: FCA7 C790 19B9 322D EB7A E1B3 4371 4650 04C7 7E2E