(it was builded for Musix (Debian/Stable))
Installation:
sudo apt-get update
sudo apt-get install linux-image-2.6.21-rt4
All files:
Todos los archivos:
apt-cache search 2.6.21-rt4
acer-acpi-modules-2.6.21-rt4 - acer-acpi modules for Linux (kernel
2.6.21-rt4).
acerhk-modules-2.6.21-rt4 - Acer Hotkey driver for Linux (kernel 2.6.21-rt4)
cloop-module-2.6.21-rt4 - The compressed loopback block device kernel module
fsam7400-modules-2.6.21-rt4 - fsam7400 modules for Linux (kernel 2.6.21-rt4).
fuse-module-2.6.21-rt4 - Filesystem in USErspace (kernel module)
gspca-modules-2.6.21-rt4 - gspca modules for Linux (kernel 2.6.21-rt4)
ipw2100-modules-2.6.21-rt4 - ipw2100 modules for Linux (kernel 2.6.21-rt4)
ipw2200-modules-2.6.21-rt4 - ipw2200 modules for Linux (kernel 2.6.21-rt4)
linux-doc-2.6.21-rt4 - Linux kernel specific documentation for version
2.6.21-rt4
linux-headers-2.6.21-rt4 - Header files related to Linux kernel, specifically,
linux-image-2.6.21-rt4 - Linux kernel binary image for version 2.6.21-rt4
linux-manual-2.6.21-rt4 - Linux kernel section 9 manual pages for version
2.6.21-rt4
linux-source-2.6.21-rt4 - Linux kernel source for version 2.6.21-rt4
loop-aes-ciphers-2.6.21-rt4 - Ciphers for the loop-aes encryption Linux kernel
module
loop-aes-modules-2.6.21-rt4 - loop-AES encryption modules for kernel
2.6.21-rt4
ltmodem-modules-2.6.21-rt4 - ltmodem-source modules for Linux (kernel
2.6.21-rt4).
madwifi-modules-2.6.21-rt4 - modules for the Multiband Atheros Driver for WiFi
(kernel 2.6.21-rt4)
ndiswrapper-modules-2.6.21-rt4 - ndiswrapper linux kernel module
qc-usb-modules-2.6.21-rt4 - kernel module for QuickCam Express
realtime-lsm-module-2.6.21-rt4 - Realtime Linux Security module.
rfswitch-modules-2.6.21-rt4 - rfswitch modules for Linux (kernel 2.6.21-rt4).
rt2400-modules-2.6.21-rt4 - RT2400 wireless network drivers
rt2500-modules-2.6.21-rt4 - RT2500 wireless network drivers
rt2570-modules-2.6.21-rt4 - RT2570 wireless network drivers
More info:
http://linux.ilmainen.net/musix/linux-2.6.21-rt4/
--
`&'
# Marcos Guglielmetti
# Musix GNU+Linux, 100% Software Libre
_#_ http://www.musix.org.ar/en
(#)
/ O \ + archivos: ftp://musix.ourproject.org/pub/musix/
( === ) Ecología: http://autosus.wordpress.com/
`---'
Hola, ahora la lista de mail de freepats (armada para coordinar esfuerzos para
crear instrumentos libres basados en muestras de sonido (soundfonts,
hydrogen, etc)), anima a cualquier persona de cualquier lengua a suscribirse
y hablar en su lengua, pero hay más detalles abajo, en inglés y español:
[Freepats] Multilingual freepats mailing list
De: Roberto Gordo Saez <roberto.gordo(a)gmail.com>
Para: freepats(a)opensrc.org
Fecha: 19/05/07 14:43
[Spanish translation below / Traducción al español abajo]
This message is a semi-official announcement to inform everybody that the
freepats list is now open to multiple languages.
We have noticed that some people would want to participate, but they are
having problems writing in english. Based on our previous conversations
in this list, it seems that there are already many Spanish-speaking
people willing to participate. Of course, interested communities of any
part of the world, in any language, would be welcomed.
In the future, if more people joins, the list could be splitted into
several language-dependant lists. Currently we have very few messages in
this list, so we think that it would be better to center all efforts
in the same place.
Anybody can send non-english emails for coordination with other people, or
when your main target (the person or group you are most interested in
reading your message) does also speak your language.
It would be better to use English for announcements of general interest.
if you can. Also, keep in mind that other people (mainly Mark :-) )
may be wondering what are you talking about or may become interested and
ask you for information in english, to be able to participate on a
conversation.
I think it would be also a good idea to keep the subject of the email in
the same language than the body. This way, it would be easier for people
who does not understand a particular language to skip those emails.
In either case, do not take these guidelines too strictly, they are only
my own hints. It can be summarized in: do not stop yourself when posting
a message in any language. We will try to deal with it, and probably
someone can translate it when needed. Currently, most important for us is
to keep our efforts alive.
Let's try and see what happens with our Tower of Babel.
********
Spanish/español
Este mensaje es un anuncio semi-oficial para informar de que la lista de
correo de freepats está, a partir de ahora, abierta a múltiples idiomas.
Hemos notado que hay personas quieren participar, pero escribir en
inglés supone un obstáculo. Según las conversaciones anteriores en esta
lista, parece que hay actualmente bastantes personas hispanohablantes
interesadas en participar. Por supuesto, serán bienvenidas comunidades de
cualquier parte del mundo interesadas, en cualquier idioma.
En el futuro, si se apunta más gente, la lista podría dividirse en
varias listas según el idioma. Actualmente hay muy pocos mensajes en
esta lista, así que pensamos que sería preferible concentrar todas las
iniciativas en el mismo sitio.
Cualquiera puede enviar mensajes en su idioma nativo para coordinarse
con otras personas, o cuando sabes que el receptor principal (la persona
o grupo que más te interesa que atienda a tu mensaje) habla también tu
mismo idioma.
Sería preferible utilizar inglés en las noticias de interés general, si
te resulta posible. También, ten en cuenta que otras personas
(principalmente Mark :-) ) se preguntarán sobre lo que se está hablando
en una conversación o podrían interesarse por el tema y solicitarte
información en inglés, para poder participar en una conversación.
En mi opinión creo que sería también buena idea mantener el asunto
(subject) de los mensajes en el mismo idioma que el contenido. De esa
manera, a las personas que no entienden un idioma en concreto les
resultaría más sencillo saltarse esos mensajes.
En cualquier caso, no es necesario que tomes muy estrictamente estas
recomendaciones, ya que es sólo mi opinión. Podemos resumir todo en:
no tengas inconveniente en enviar mensajes en cualquier idioma,
intentaremos entendernos todos lo mejor posible y probablemente alguien
lo podrá traducir cuando sea necesario. Actualmente lo más importante es
facilitar las cosas ante cualquier iniciativa.
..........
--
`&'
# Marcos Guglielmetti
# Musix GNU+Linux, 100% Software Libre
_#_ http://www.musix.org.ar/en
(#)
/ O \ + archivos: ftp://musix.ourproject.org/pub/musix/
( === ) Ecología: http://autosus.wordpress.com/
`---'
hello people,
I try to configure qjackctl-0.2.2-2 on debian lenny and I get
checking whether QTDIR environment variable is set... no
configure: error: QTDIR must be properly set.
Spent quite a time on google by now, but none of the solutions changed
anything.
on this list I found the hint to set
QTDIR=/usr/share/qt3
somewhere else
QTDIR=/usr/include/qt3
or QTDIR=/usr/lib/qt3
but neither changed anything. The header-files (if its them, the
configure-script is looking for) are actually in /usr/include/qt3,
libqt3-headers, libqt3-mt-dev and qt3-dev-tools, all version 3:3.3.7-4,
are installed.
would not mind installing qjackctl via apt-get, but:
The following extra packages will be installed:
libjack0.100.0-0
I manually installed (and need) jack-audio-connection-kit 0.103.0-1
(with checkinstall) - don't think it is a good idea to say yes here.
Am I missing something very basic? in any case i would like to learn more.
cheers,
david
Folks,
Is there such a thing as a 'generic' MIDI keyboard with a LCD that
can display info retrieved from Linux synths apps ? Such a keyboard
interfaces directly with a Linux box runnign various sound-producing
apps. The controls on the keyboard itself can choose between Qsynth,
Zyn, etc... It could eventually even choose which soundfont in QSynth
or which sound in Zyn.
Does such a keyboard exist ?
Just asking ;-)
Cheers,
Al
Greetings:
Some time ago I wrote a rather lengthy user-level introduction to JACK.
It was published in a German Linux magazine, and I'd now like to put the
original on the Web. However, it surely needs updated, so I've placed
its current condition on-line here :
http://linux-sound.org/knowing-jack.html
At this time I'm looking for corrections and additions to the main text.
I've purposefully left out the screenshots, I'll update them myself
after the text is up to date.
I'm not using FreeBob or JackMIDI and would apprciate any information
readers think should go into the article.
Please advise if any information regarding the QJackCtl audio options
needs changed. Users often wonder what all those checkboxes actually do,
and I'd like to give them the right info.
Btw, this artice is *not* planned for publication again, and I'll
happily place it under a CC license if desired by the community. If
acceptable I'd like it to go on the linuxaudio.org site.
Feel free to respond to the lists or directly to me.
Best,
dp
Hi James, Brian,
Thanks for the comments!
Indeed, the voice is too repetitive. I should cut it off sometimes, and make
some more melody variation, jamming..
The backwards voice is a thing to try!
May be I should also add a some point change the tone (add other chords),
may be to make it sad in the middle. But at the end again joyfull..
Julien.
Folderol:
>> Hi guys,
>>
>> I'm trying to setup a `proof of concept' sound processing system on my
>> machine, using Linux. The system should cater rock/metal bands. Now I need to
>> know where to start and what to look at. There's so much documentation and so
>> many software out there that I'm getting confused and don't know where to
>> start. I have around a month to set up the system, so as to give a
>> presentation and a live demo at a local community event.
>>
>> I generally prefer to know my theory properly before practically implementing,
>> so please tell me what background knowledge I should ideally have to
>> implement such a system.
>>
>> Any links, hints, pointers etc. very much appreciated.
>>
>> Thanks a lot.
>>
>> P.S. I'm using Gentoo and have access to the pro-audio overlay. Also, since
>> this is just a proof of concept type project, I won't be spending on
>> hardware. I have a Sempron64 2500+ machine with 1GB of RAM and plenty of hard
>> disk space, although on 7200 rpm PATA. I think I can borrow a Creative SB
>> Live 5.1 sound card from my boss for the project.
As a start I suggest installing jack, ardour and all ladspa plugins
available.
You can also boot the dynebolic cd to check out various media software in
a quick way: http://www.dynebolic.org/
> To start off with, I would suggest you get 64studio. It will give you
> most, if not all, the packages you want as standard.
>
> I have it working very well on a similar Sempron setup (as well as other
> machines).
>
Well. He is already using Gentoo using the pro-audio overlay.
gentoo+pro-audio probably has a lot more (audio) packages than 64studio.
Hi,
I'm experimenting with fluidsynth at its simplest form, that is,
directly from the command line and using the fluidsynth shell. So I
start fluidsynth like this:
fluidsynth -m alsa_seq -a jack /usr/local/share/SF/Unison.sf2
Jack is already started using qjackctl. As soon as I use qjackctl to
connect a MIDI keyboard to that fluidsynth instance, the following
messages are shown by fluidsynth, non stop, wohtout even playing a note:
fluidsynth: warning: ALSA sequencer buffer overrun, lost events
The MIDI kyb is connected via a M-Audio 1010LT card.
Are these messages important and if not, how to make them go away
without altering the source code ?
Thanks.