Okay, I'll see if I can make up for my awful post from before with a
constructive question.
If you wanted to quickly prototype an idea for a DSP routine, how would
you go about it? It would need to work in real-time, but it wouldn't
really need to be super-efficient for testing ideas.
Thank you for the help.
-- Darren
Hi everyone,
and interesting thread has been going on the olpc devel list.
It would be interesting to get your comments on one
of the statements that were posted there (I'll
leave you to check the thread on the list archives
http://lists.laptop.org/pipermail/devel/).
This particular e-mail goes (in response to me asking why they
were complaining about alsa and asking for OSS:
"OSS in general, or OSS on Linux? He did say "OSS 4", which is
the current version of the API. Solaris and all *BSD use it,
along with random SysV-like things. As far as sound on the
UNIX-like platforms goes, OSS is the standard. Probably it
ought to be proposed for the next POSIX/UNIX standard.
You can read Hannu's take on the matter in his blog. This
entry is particularly informative, but note that the code
has since been released under the GPL.
http://4front-tech.com/hannublog/?p=5
More on the ALSA defects:
http://lkml.org/lkml/2007/7/6/397
Basically we got swindled. ALSA has not been the utopia that
it was claimed to be. ALSA sucks. It's not even documented."
Hannu's text sometimes reads as propaganda. But it would be
nice to hear the opinion of other developers. As far as I am concerned,
for about five years now I have not even looked at OSS anymore.
But should I reconsider?
Thanks
Victor
Hi,
There is a Free Software event in south of France this summer.
We would like to make a place for libre audio and libre culture, which
includes conferences and workshop around the tools (softwares), the
diffusion (medias, communities, ...), the licences, the users (examples of
audio studio using free technologies, examples of libre artits, ... )
So don't hesitate to send your propositions
Here is the official call for conference :
>From 1st to 5th July 2008, the Ninth Libre Software Meeting(9th LSM) will
take place in Mont-de-Marsan, in south of France. Hundreds of conferences,
workshops and showings will be programmed.
To maintain the interest of the public, it is important for LSM to renew the
content of different themes. So, if you participate in a new or unknown
project, if you wish to share your passion and your libre software
experience, we will gladly welcome you during LSM 2008.
We start a large call for communications on the following axes :
- thematic conferences - all subjects are interesting, particularly
those we have not thought about ...
- projects or libre softwares presentations
- workshop animations (development, initiation, ... )
To propose to the public a rich and various content, please send your
propositons, suggestions and ideas before February 8th to appel2008 at
rmll.info
*Contacts :* (program directors)
Nicolas Ducoulombier : nicolas at ldd.fr <nicolas%20at%20ldd.fr>
Christophe Merlet : redfox at redfoxcenter.org<redfox%20at%20redfoxcenter.org>
The definite programme, theme list, conferences and contributors will be
highly influenced by the feedback we will get from this call for
contributions.
Do not hesitate to participate and give worthy projects wide visibility.
--
Benjamin Coudrin
benjamin.coudrin(a)gmail.com
(+33)6.09.11.00.83
miniloop is a simple live looping program. It can load a number of
stereo audio loops of equal length from the disk and loop them in sync
with each other, sending each loop to a different pair of JACK audio
outputs. These outputs are intended to be subsequently fed into an
external software mixer, such as Ardour. For live performance, you
will want to control the mixer using a MIDI control surface.
miniloop is similar in intent to Stephen Sinclair's LoopDub. I
actually created miniloop to explore some design ideas that I had
while working on LoopDub. Given that, it is appropriate to provide a
comparison between the two programs. The most important difference is
that LoopDub uses a built-in mixer, while miniloop uses an external
mixer. This means that miniloop is more flexible, but requires a more
complex software setup. Another important difference is the user
interface, which is radically different, and, I hope, somewhat easier
to use. Finally, LoopDub has many features that miniloop lacks;
miniloop is currently quite small (~500 SLOC) and quite feature-poor,
and I intend to keep it that way.
Project homepage here:
http://code.google.com/p/miniloop/
Download here:
http://code.google.com/p/miniloop/downloads/detail?name=miniloop-0.0.zip
Not sure whether this is any good with respect to real-time audio.
"LatencyTOP is a Linux tool for software developers (both kernel and
userspace), aimed at identifying where system latency occurs, and what
kind of operation/action is causing the latency to happen. By identifying
this, developers can then change the code to avoid the worst latency
hiccups."
<http://www.latencytop.org/>
It's part of Intel's OSS initiative:
<http://oss.intel.com/>
Hi all,
the a bit provocative title is not here to start a flame war but to spark a
constructive discussion about the
viability and future of the LV2 plugin standard in the professional audio
application market.
Some background:
as you probably know Steinberg just released VST3 and developers do not seem
happy with it
as it is not backwards compatible, not many new features and it seems less
portable amongst platforms than VST2.4.
Users are unhappy and started a long discussion:
http://www.kvraudio.com/forum/viewtopic.php?t=204080&postdays=0&postorder=a…
The discussion was picked up on the Reaper forum too.
For anyone not familiar with Reaper, it is a very good audio,midi sequencer.
http://www.reaper.fm
It is a windows app but runs very well under wine and the company writes
this on their page.
Users like Alex Stone are using it on wine in conjunction with LinuxSampler
The authors are Justin Frankel from Nullsoft and others. For those that
don't know the name, he is the one
that wrote winamp, gnutella, nullsoft installer etc.
On a forum he said he played with the idea of open sourcing reaper.
It is being ported to OS X and probably will get ported to Linux too, given
the very good performance it achieves on wine.
Now back to LV2:
The VST3 discussion on the reaper forum resulted in users proposing to
create a new plugin standard
in order to "break free" from proprietary standards so they are proposing to
add LV2 support to Reaper.
Justin from Reaper answered the following on the forum:
-------
I looked at LV2, there's a lot of stuff which I disliked.. for example,
"ports" being for parameters and audio buffers (and presumably MIDI events),
and all having the possibility of colliding, isnt well thought out.
Also if you want to add parameters to a new revision of a plug-in, then you
have to change the URI? ick.
Or what if you want to change the I/O of a plug-in on the fly..
-Justin
---
see here for the full thread:
http://www.cockos.com/forum/showthread.php?t=17198&page=2
I did not look at LV2 so I cannot judge, but I think LV2 developers should
discuss about these issues and concerns with
Justin in order sort out problems, and given the joung nature of LV2 , in
case important design flaws get uncovered, change the specs a bit.
Reaper is rapidly building up a large user base (users switching away from
cakewalk sonar and cubase to reaper) as the application provided excellent
performance, is easy to use
and new features are being incorporated at a fast pace.
Dave Philips seem to love the app too as he mentioned it in Linux Journal
and he posts frequently on the forum.
http://www.linuxjournal.com/node/1005911
I think LV2 and Reaper developers should join forces because together
perhaps it will be possible to impose a new open plugin standard
which will get adopted by other commercial applications too and supersede
VST2.4 over time.
not sure if the reaper devs are reading LAD, so perhaps LV2 developers
should answer on the reaper forum too in order to sort out the
issues raised by Justin.
Everyone is invited to add his own point of view and I hope that the outcome
will be a positive collaboration between LV2 and Reaper.
thanks everyone,
Benno
On Jan 22, 2008, at 2:45 PM, M-.-n wrote:
> more linux music on the go ?
> http://www.openpandora.org
> http://pandora.bluwiki.com/
definitely one to watch .. i hear a rumour that devboards are out and
about for this already .. should be good to go in march if all goes
well, and the world doesn't slide into a mass depression in the
meantime .. ;)
also, the neo1973-GTA02 version should be a nice little machine for
portable music-making, soon enough. i'm having a blast with
pulseaudio on my gta01 .. gonna be nice to have some power increase
(and new graphics) in the new version. insmod gadget-audio for the
win, w00t!
;
--
Jay Vaughan
Hello all, my name's Alex Stone, and Benno From Linuxsampler pointed me in
this direction to see what you guys who build stuff are up to.
Frankly I've been amazed at the talent on display to use a phrase. Linux
audio has come a long way since i last peeked in some 8 or 10 years ago. I'm
currrently usiing a programme called Reaper, in wine in Linux, but i am keen
to see a complete native solution come to maturity. I've had the privilege
of communicating with some of you already, and as my linux journey is a
recent one, i've been assisted, and encouraged by some great fellas, who
know their stuff.
Anyway, the introductions are done, and handshakes are made. I hope i can
contribute something here from a user's perspective, and as someone fairly
well versed in using audio and production programmes on the 'other side of
the fence'. I've finally seen the light, and gained my freedom.
As a former orchestral player, i'm more inclined to use programmes from a
classical composer's perspective. and as some of you know already, i've
tried to convey what it's like to write classical music with a computer, and
the challenges that go with that, the biggest of all usually being the
number of audio or midi ports available, and the capability possible for
using a large number of instruments, often with several for one section with
variations in articulation.
My respects and thanks to those who have helped and encouraged so far, and i
hope i can give something back as my knowledge continues to grow..
Alex Stone.
Hi again!
Well Phil you said, that the new protocol wouldn't be understood by
anything. So why not first take it easy and take a look at what already
exists. OSC was mentioned here a couple of times? Might that be an idea?
And about the two APIs: why not? If you think about it thorroughly I'm sure
one can come up with a protocol, of which MIDI is a subset. Thus some
interaction between to apps (one using MIDI, one using the new thing) could be
possible.
At the moment we have audio and MIDI ports, add a third kind of ports. And
thus if you use plain old MIDI there's no more overhead, than there should be.
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
Dear Linux Audio users,
A new jack release (0.109.0) is available:
http://sourceforge.net/project/showfiles.php?group_id=39687
Enjoy,
Pieter
(Releaser-ad-interim)
Changelog
=========
API changes:
* add jack_thread_wait API
* remove port_(un)lock functions
* add new time APIs
* add port aliases
* add new client registration callback
* add port connect callback
Backends:
* ALSA: fix for use of snd_pcm_link
* ALSA: hardware jack-midi support
* ALSA: fix for enabling big-endian 16bit format discovery
* ALSA: hardware jack-midi support
* FreeBoB: fix deallocation segfault
* FireWire: add 'firewire' backend for use with FFADO
* OSS: add support for proper triggering in OSS driver when in full
duplex mode
* ALSA: fix illegal use of ALSA API
* OSS: disable software mixing and samplerate conversions on OSS 4.x
* CoreAudio: fix sample rate management
Other
* add JACK_PROMISCUOUS_SERVER handling
* make /dev/shm the default tmpdir
* add -Z flag to cancel zombification on timeout
* add per-port update total latency
* increment default watchdog timeout to 10sec