Linux-audio-user June 2007

linux-audio-user@lists.linuxaudio.org

130 participants
108 discussions

[LAU] TAP and other LADSPA plugins cause... dead silence?

by Ken Restivo

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've noticed a phenomenon many months ago: certain LADSPA plugins, when I enable them, cause all audio to stop coming out of the effects chain. This was a common problem with jack-rack. it got so annoying, I stopped using jack-rack. The same plugins that would cause jack-rack to go silent, worked fine in Ardour. So I started using Ardour (0.99) instead for effects. Now, on a 64-bit dual-core Intel machine, I'm noticing the problem even in Ardour (2.0.2). And in ecasound too, and jack-rack. If for example I add the TAP Rotary Speaker plugin to any of Ardour2, jack-rack, or ecasound, all audio stops. If I remove the TAP Rotary Speaker, audio is fine. Why is this? - -ken -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFGSrEme8HF+6xeOIcRAn/5AJ0ZXMAKlyaBinWnd5f/gjScxkojXwCfZ867 1n3py1Y2VYV9AjUO/ro3Njg= =Pxto -----END PGP SIGNATURE-----

18 years, 9 months

[LAU] Version 1.2 of MMA is now available

by Bob van der Poel

Version 1.2 of MMA - Musical MIDI Accompaniment - is now available for downloading. Included in this release: A new command set which lets MMA create and play MIDI files on-the-fly, Some additional synchronization options, Smoother volume changes with (De)Crescendos, Minor bug fixes/improvements. See the entire change log in the included CHANGES-1.1 file. MMA is a accompaniment generator -- it creates midi tracks for a soloist to perform with. User supplied files contain pattern selections, chords, and MMA directives. For full details please visit: http://www.mellowood.ca/mma/ If you have any questions or comments, please send them to: bob(a)mellowood.ca -- Bob van der Poel ** Wynndel, British Columbia, CANADA ** EMAIL: bob(a)mellowood.ca WWW: http://www.mellowood.ca

18 years, 9 months

[LAU] midi under wine

by Atte André Jensen

Hi While I'm waiting for my micron to arrive I thought I'd prepare a bit. I ran micronizer (windows editor software) through wine, and while I don't have a micron yet, it seems to work fine. However I see the following in the terminal I started wine in: RtMidiIn::initialize: no MIDI input devices currently available. RtMidiOut::initialize: no MIDI output devices currently available. So my question is: what should be done for a wine program (for instance micronizer) to use some alsa midi device for midi in/out? Is there any online documentation I should look at? -- peace, love & harmony Atte http://atte.dk | http://myspace.com/attejensen http://anagrammer.dk | http://atte.dk/compositions

18 years, 9 months

Re: [LAU] building Freecycle for x86_64 ?

by Viceic Predrag

> Compiling without libinstpatch didn't work When you make changes in cond.pri, you must re-run qmake. It helps if you "make clean" and remove Makefiles (in the root dir and in src/) Regards, Predrag Le mercredi, 6 juin 2007, Emanuel Rumpf a écrit : > 2007/6/6, Predrag Viceic <viceic(a)net2000.ch>: > > Hi, > > > > libinstpatch can be disabled in > > > > src/cond.pri > > Thanks for the hint ! > > but then you loose soundfont export. > > > If I remember well, Piem (http://piem.org/debian/) has the builds of > > Freecycle > > and the "correct" libinstpatch. > > Cheers, > > > Predrag > > http://freecycle.redsteamrecords.com > > > > Ah, that helped... > > Compiling without libinstpatch didn't work > so after downloading the deb-package for libinstpatch from: > http://piem.org/debian/unstable/i386/ > ( because compiling libinstpatch myself, did not work) > > I managed to compile freecycle (debian unst. 32) this way: > > first edit src/cond.pri as appropriate (no changes required, but I enabled > portaudio and portmidi) > now run qmake3: /usr/share/qt3/bin/qmake IN THE src directory, not the base > directory! > now run /usr/share/qt3/bin/qmake in the base directory > fix src/soundplayer.cpp line 77 as described (remove () braces ) > now make > > Cheers, > Emanuel

18 years, 9 months

[LAU] hardware synth editor

by Atte André Jensen

Hi I'm thinking seriously about getting an Alesis Micron. But I understand they are a pain to program, so I'm looking for an editor software. I looked at jsynthlib, and it seems it should be possible to write a driver for the Micron. However the project seems a little (or more) dead. What software do you guys use to edit your hardware synths? NB: I'm not interested in a librarian, only software that'll allow me to edit patches... -- peace, love & harmony Atte http://atte.dk | http://myspace.com/attejensen http://anagrammer.dk | http://atte.dk/compositions

18 years, 9 months

[LAU] Skype and multiple sound cards ?

by Florin Andrei

I've a system with two sound cards. One of them is on the motherboard, the OS detected it as: alias snd-card-0 snd-hda-intel options snd-card-0 index=0 options snd-hda-intel index=0 remove snd-hda-intel { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-hda-intel The other "card" is a USB thing (actually a dedicated headphone preamp, pretty good sound quality). Until now, I was only using the USB preamp for everything (mostly XMMS and Flash). To do that, I created this file in my home directory: $ cat .asoundrc defaults.pcm.card 1 defaults.ctl.card 1 So, with that file in place, pretty much all applications just used the secondary sound card (the USB preamp) as their output device. Skype _only_ sees that device, it does not appear to detect the onboard card. The problem is, the USB preamp does not have a microphone input. I would like to use the USB preamp as the default output for everything (including Skype), and the onboard Intel chip as the microphone input for Skype. Any idea? Some tweaks to .asoundrc perhaps? -- Florin Andrei http://florin.myip.org/

18 years, 9 months

[LAU] Seq24 jack transport anomalies.

by Brian Dunn

Does anyone else out there get into frustrating situations with the seq24 jack transport features? seq24-0.8.7 often when I restore a lash session and hit play on the seq24 main window the jack transport starts rolling, but the play marker in all of my seq24 loops gets stuck in the middle of the loop icons, and no notes are sent. then often when I press stop a wave of midi data bursts from the sequencer. Clicking "Disconnect" on the Jack Sync tab of the Options window in seq24 re-enables loop play back, but no longer synced with the jack t port. clicking connect again induces the same quirk, the play bar gets stuck but the j t port rolls. Sometimes closing seq24, and then reopening it and manually loading the file in the lash directory fixes the glitch, sometimes it doesn't. I have the "Jack Transport" and "Master Conditional" boxes checked, and the sequencer is in "live mode." Is this a bug? does this happen to anyone else? I can't really isolate what seems to cause it, but usually if it happens in one project, it will happen in all lash projects. /brian

18 years, 9 months

[LAU] JACK MIDI - where? how?

by Josh Lawrence

I just downloaded dino, and it became pretty clear that I don't have jack midi working. I'm running jack version 0.103.0 on debian sid. is there a way to enable jack midi functionality to my existing jack without having to pull the whole thing apart and put it back together? thanks, -- Josh Lawrence http://www.hardbop200.com http://www.joshlawrencetrio.com

18 years, 9 months

[LAU] Make your own soft synths with open source audio programming languages

by Cesare Marilungo

Hi, I just posted a brief tutorial on my blog on this topic, covering Csound, SuperCollider and Chuck. If you're interested, please check it out and send some feedback: http://www.cesaremarilungo.com/blog/2007/06/02/make-your-own-soft-synths-wi… Cheers, c. -- http://www.cesaremarilungo.com

18 years, 9 months

[LAU] Re: Re: [ANN] jack_capture V0.9.6

by Kjetil Svalastog Matheussen

Paul Winkler: > > On Tue, Jun 05, 2007 at 12:29:11PM +0200, Kjetil S. Matheussen wrote: > > You don't have to think. If you have something cool going on in your > > loudspeakers and need to record something now, in a hurry... > > Cool. How does it decide by default which jack ports to capture? > Does it just do all available alsa_pcm playback channels? > Almost. Unless othervice specified, it will use the two first channels that satisfies being JackPortIsPhysical|JackPortIsInput, which usually (on linux at least) means alsa_pcm:playback_1 and alsa_pcm:playback_2.

18 years, 9 months

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Linux-audio-user June 2007