Any chance of a debian repository to go with it? Or should it be mostly self-complile?
-----Original Message-----
>From: Nils Gey <ilfhi(a)gmx.de>
>Sent: Aug 5, 2008 7:30 AM
>To: linux-audio-user(a)lists.linuxaudio.org
>Subject: Re: [LAU] Linux Plugin-website (Lv2, LADSPA, DSSI , Linuxvst etc.)
>
>I have registered a sourceforge project for this and already got it through.
>Lets see what I can do.
>
>Nils
>
>
>On Mon, 4 Aug 2008 17:42:11 +0200
>Nils Gey <ilfhi(a)gmx.de> wrote:
>
>> Hi list,
>>
>> Recently I noticed that there a many plugins avaible on the web which are not included in my distribution. Off course they are not, how can the maintainers know any plugin which is avaible?
>>
>> I searched a bit (found nothing) and got the idea that probably a website dedicated to Linux audio plugins and virtual instruments would be a nice thing.
>>
>> A database where users can upload their plugins(-sourcecode) other users could review them and so on. Maybe it could be the central place for plugins to be shown and distributed so that every plugin can get the attention which it deserves.
>>
>> Comments?
>>
>> Nils
Hi list,
Recently I noticed that there a many plugins avaible on the web which are not included in my distribution. Off course they are not, how can the maintainers know any plugin which is avaible?
I searched a bit (found nothing) and got the idea that probably a website dedicated to Linux audio plugins and virtual instruments would be a nice thing.
A database where users can upload their plugins(-sourcecode) other users could review them and so on. Maybe it could be the central place for plugins to be shown and distributed so that every plugin can get the attention which it deserves.
Comments?
Nils
Hi Folks
After a long (15 years) break in music making/recording, I have just set
myself up with a new virtual studio - bit of a culture shock when all my
previous experience was analogue plus Notator on an Atari.
I'm running Gentoo Linux (x86_64) on a dual-core ThinkPad with 1.5Gb
RAM. To save unnecessary processing overhead and because I like a
'clean' desktop, I am using the Fluxbox window manager.
My current studio consists of:
* Jack
* Rosegarden
* Zynaddsubfx
* Xsynth
* Fluidsynth
* Hydrogen
* Samson C01U USB microphone
* Behringer UCA202 audio adapter
* Roland/Edirol PC-300 MIDI controller
In an attempt to fix any latency issues, I have used the RT-modified
ketchup to get myself a kernel 2.6.25.8-rt7. RT profile is selected,
timer at 1kHz. I have stripped much of my day-to-day stuff out of the
kernel configuration so that I have a dual-boot configuration, one for
'normal' work, the other just for audio. I have also created a separate
profile for the RT kernel so that only essential services are started.
Whilst going from the 'low-latency desktop' of my standard kernel to the
RT kernel has made a huge difference in the number of xruns that I am
seeing on Jack, it hasn't cured them completely.
My test configuration routes my MIDI keyboard through Jack, to
Rosegarden to Jack, to Zynaddsubfx to Jack, to ALSA out. I find that
whilst playing - even when pushing down an unreasonable number of keys
very quickly - I don't get any clicks or pops. I do, however, get the
occasional xrun. Weird thing is that sometimes I get them when I'm
hardly doing anything at all.
Jack connection parameters are priority=9, Frames/Period=512, Sample
Rate=44100, Periods/Buffer=3.
At the end of dmesg, there seem to be a lot of errors or warnings -
don't know if they're significant. I've put them here:
<http://www.smiffysplace.com/files/dmesg_rt_20080731>
(For some reason, the top bit of dmesg got lost - hope this doesn't
matter. Can re-create if required.)
Kernel config is here:
<http://www.smiffysplace.com/files/kconfig_rt_20080731>
PAM is configured for the audio group (yes I am in it!):
@audio - rtprio 99
@audio - memlock 250000
@audio - nice -10
I've now pretty well exhausted the results of my Googling but am still
not sure what I'm doing wrong or if these xruns may be safely ignored
(I'm assuming they can't be). Any suggestions would be greatly appreciated!
Cheers
M
--
Matthew Smith
Smiffytech - Technology Consulting & Web Application Development
Business: http://www.smiffytech.com/
Personal: http://www.smiffysplace.com/
LinkedIn: http://www.linkedin.com/in/smiffy
Any ideas what would cause seriously weird crackling any time I push a soft
synth too hard (ie too many keypresses, etc)? Odd thing is, I'm not getting
any XRUNS accompanying it..
Running Ubuntu Studio 8.04 if it helps.
Thanks!
~holotone
http://holotone.net/
This was posted yesterday, hot off the press, found somehow by googling.
No more of this bug message!
Got a few (only a few) complaints about using smp process with rt preempt (I
believe this is an old story and harmless).
Now, if only I knew why hald start kills DMA and resets the IDE lines, I would
try to use this kernel.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I have a multitude of issues with freebob on several computers/distros.
Here I only want to ask for help with FC9 plus CCRMA:
I have a VIA-FW-Controller on a PCI-Card in a AMD64-box. Connecting my
Presonus Firebox to this sometimes works flawlessly and I had sessions
for several hours in 64Studio 2.1 on this box.
But alas: in 4 out of 5 cases the box does not invoke the ieee1395:
raw1394 raw device initialisation.
tail -f /var/log/messages shows up stuff like "recieved ... during reset
ignoring" and does nothing.
On FC9 with CCRMA-Kernel the best it does is:
"Error parsing configrom for node 0-00:1023"
Then I get the beloved message:
"ieee1394: raw1394: /dev/raw1394 device initialized"
BUT: only /dev/raw1394 exists, ieee1394 does not. Thus jackd dies as
freebob tries to initialize the driver backend.
I noticed also, that a dv1394 Device is created, which I have not seen
for some time now...
Please consider to unlist the following causes for that:
1.) permissions: all is set properly I have good success with the same
setup in 64Studio
2.) presonus-trouble: the box works OK (see above) I tried it both
host-powered and with the power-supply attached to the box...
Waht really makes me nervous is, that the VIA-Controller I use is named
second-best next to TI-chips on the FFado-page whereas a O2 Micro I use
with acceptable success on my notebook is branded as worst of the barely
working (this chip *never* failed to initialize the firebox at least...)
So what can I do?
I have a recommended FW-Controller and a working interface but FC9 still
fails me ...
:(
best regards
HZN
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIlZgt1Aecwva1SWMRAjc3AJ4p3biILhIR8VRuswl7rPcnv+/WZACggISc
QUDHkowxGMrzHC5ch44PBNU=
=aW7i
-----END PGP SIGNATURE-----
a2jmidid is a project that aims to ease usage of legacy ALSA sequencer
applications, in a JACK MIDI enabled system.
a2jmidid implementation is based on jack-alsamidi-0.5 that is [almost]
same as jackd ALSA "seq" MIDI backend, both created by Dmitry Baikov.
Static bridges are based on code by Sean Bolton and Lars Luthman.
Homepage with screenshots: http://home.gna.org/a2jmidid/
Tarball download: http://download.gna.org/a2jmidid/
Changes since version 3:
* Fix typos in docs
* Disable use of C++ demangling in sigsegv. Fix for sr #2074
* Fix a2j_control help text (thanks kfoltman!)
* Request fixed JACK client name. Fix for bug #12139
* Handle missing svnversion executable nicely. Fixes bug #12138
Changes since version 2:
* Improved port naming, support for bidirectional ports
* Allow exporting of hardware ports (disabled by default)
* Switch from autotools to waf
* Remove support for old JACK MIDI API variants
* Remove usage of posix semaphores that could cause sleep in realtime context, in rare circumstances
* D-Bus background service mode. The old manual mode is still working.
* Log file when running in background service mode.
* Improved documentation
* Import, with slight modifications, static bridges created by Sean Bolton and Lars Luthman.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
a2jmidid is a project that aims to ease usage of legacy ALSA sequencer
applications, in a JACK MIDI enabled system.
a2jmidid implementation is based on jack-alsamidi-0.5 that is [almost]
same as jackd ALSA "seq" MIDI backend, both created by Dmitry Baikov.
Static bridges are based on code by Sean Bolton and Lars Luthman.
Homepage with screenshots: http://home.gna.org/a2jmidid/
Tarball download: http://download.gna.org/a2jmidid/
Changes since version 2:
* Improved port naming, support for bidirectional ports
* Allow exporting of hardware ports (disabled by default)
* Switch from autotools to waf
* Remove support for old JACK MIDI API variants
* Remove usage of posix semaphores that could cause sleep in realtime context, in rare circumstances
* D-Bus background service mode. The old manual mode is still working.
* Log file when running in background service mode.
* Improved documentation
* Import, with slight modifications, static bridges created by Sean Bolton and Lars Luthman.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
Quoting Joe Hartley <jh(a)brainiac.com>:
> BTW, this *has* been done already:
> http://news.bbc.co.uk/2/hi/technology/2737331.stm
You've gotta love the photo in the article. The balding geek with the
electric guitar quoted saying "You can send each string on a separate sound
channel".
Every string on it's separate channel? Now _that_ is rock'n'roll.
;)
Sampo
Hi,
Does anyone know of any cheap and small S/PDIF i/o (toslink or coax)
interfaces which work on a laptop? USB, PCMCIA, Expresscard, firewire,
whatever. Size is what really matters, not how it's connected.
Oh, and it should also work in Linux. ;)
My ideal would be a USB cable with two coaxial SPDIF connectors on the other
end.
All I really would need is something which takes in two channels of
bit-perfect 24-bit digital audio (192k is not needed) and outputs two
channels through spdif. A headphone / line output would be a nice bonus but
not required.
Sampo