Greetings:
I'd like to make some desktop video captures (with audio) like xvidcap
can make, but that program doesn't work with Jack. Is there a way to use
xvidcap with Jack, or is there another recommended solution ?
Grazie,
dp
Hello. What open source and free(dom) reverbs do we have available?
I authored GVerb and wish to have something better.
What free (possibly not open source) reverbs do you use?
What kind of reverb presets people use for vocals?
Lately I have listened to Madonna's Confessions tour DVD
which has good reverb effects. I would like to know more
about that kind of working presets. Also, Timbaland uses good
vocal processings (Nelly Furtado/Say it right, Timbaland/
The way I are). I would like to know more if I wish to
develop such a vocal reverb myself.
Juhana
--
http://music.columbia.edu/mailman/listinfo/linux-graphics-dev
for developers of open source graphics software
Hi,
I was wondering, does anyone know the URL to the LAC2006 videos? The link
provided here is broken: http://lac.zkm.de/2006/downloads.shtml
I'm particularly interested in the Aliki workshop video.
Cheers!
Hector
--
===============================
http://www.hcenteno.net
On Wednesday 01 August 2007 05:43,Florian Schmidt wrote:
> Message: 2
> Date: Wed, 1 Aug 2007 09:34:58 +0200
> From: Florian Schmidt <mista.tapas(a)gmx.net>
> Subject: Re: [LAU] [ANN] lash_wrap - A small LASH wrapper
> To: linux-audio-user(a)lists.linuxaudio.org
> Cc: "njcross(a)sbcglobal.net" <njcross(a)sbcglobal.net>
> Message-ID: <200708010934.58960.mista.tapas(a)gmx.net>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Wednesday 01 August 2007, njcross(a)sbcglobal.net wrote:
> > Just to say thank you for lash_wrap. Seems to work as you stated. I tried
> > it with Ardour, Audacity and ReZound and as long as you save your work
> > before closing it works well. Thank you!
>
> A little caveat i found though:
>
> Apps that create their connections themself are not handled very well by
> lash_wrap. E.g. hydrogen, freqtweak etc... It would be cool if these apps
> had an option not to create any connections by themself on startup..
>
> Flo
I haven't got Hydrogen and Freqtweak on my system at present :-/.
When I can replicate the errors you found I'll post.
I'm just so pleased to be able to use, say, kluppe etc lashd, v.cool...
:-)
A friend of mine is willing to loan me a laptop to do some recording.
It's a PIII with Windows ME on it. He's installed Audacity on it.
Even so, I'd prefer to run Linux, and I can't trash the hard drive on
him. So, is there a live Linux CD with Audacity which would be
good for this application? Hmmm, I'll need to write the sound file
to the hard drive, and I don't know if the drive is VFAT or NTFS.
If it's NTFS that would limit which live CDs might work for me, if
any. Thoughts folks?
Thanks....
--
Kevin
On 7/31/07, Thomas Vecchione <seablaede(a)gmail.com> wrote:
> Dang it, I apologize to the list, I forgot this list DOES reply to the list
> when I hit reply, and nto reply to all.
>
> Seablade
I must admit this is a issue I wanted to raise for a while now...
For those of you who haven't heard, there has been a very long debate
on whether replyto munging was or wasn't a god practice. Each side had
a reference paper stating a number of pros and cons :
- http://www.unicom.com/pw/reply-to-harmful.html
- http://marc.merlins.org/netrants/reply-to-useful.html
The fight between Simon Hill and Chip Rosenthal finaly ended in 2001
when a new RFC obsoleting RFC 822 appeared, RFC2822.
Here's a paper from Neale Pickett stating the final story :
http://woozle.org/~neale/papers/reply-to-still-harmful
I strongly consider turning munging off on LAD and LAU. I know this
might start some flames, but isn't it good free software philosophy to
stick to the standards, especially when it comes to a recently
reviewed RFC ?
If someone can give me an argument that is not present in the 3
previously linked documents stating why we need to munge our headers,
I'll turn munging off next week.
Regards,
__________________
Marc-Olivier Barre.
Your favorite list administrator :-)
On Wednesday 26 July 2007 16:52, linux-audio-user-request(a)lists.linuxaudio.org
wrote:
> Message: 5
> Date: Thu, 26 Jul 2007 00:14:47 +0200
> From: Florian Schmidt <mista.tapas(a)gmx.net>
> Subject: [LAU] [ANN] lash_wrap - A small LASH wrapper
> To: linux-audio-dev(a)lists.linuxaudio.org
> Cc: A list for linux audio users
> <linux-audio-user(a)lists.linuxaudio.org>
> Message-ID: <200707260014.47956.mista.tapas(a)gmx.net>
> Content-Type: text/plain; charset="us-ascii"
>
>
> Hi,
>
> i planned to write this for quite a while and finally got to it [though
> it's not 100% working yet - It's a small program. If experienced unix
> hackers might look over y use of waitpit i'd be happy :)]:
>
> lash_wrap
>
> It's a small program which can be used to "smuggle" non LASH apps into a
> LASH session provided they meet some requirements:
>
> - If they are jack clients, there must be a way of determining the jack
> client name at startup time
>
> - If they are ALSA seq clients the client ID must be known at client
> startup time or their alsa seq name must be uniquely determined
>
> - They must require a way to specify their state via the commandline (e.g.
> we can tell ardour to load a certain ardour session at startup)
>
> So here's how i would smuggle ardour2 into a LASH session:
>
> lash_wrap -j ardour -- ardour2 ~/sound/ardour/brazil/brazil.ardour
>
> The -j [--jack-name] option tells lash_wrap it must register the jack
> name "ardour" with LASH. the "--" seperates the options for lash_wrap from
> the commandline to start the program in question.
>
> If we wanted also all ALSA SEQ connections of ardour to be restored we
> could do:
>
> lash_wrap -a ardour -j ardour -- ardour2
> ~/sound/ardour/brazil/brazil.ardour
>
> The -a [--alsa-name] option specifies a name which will be used to find out
> the client ID of ardour by regularly searching all ALSA clients until one
> named "ardour" is found. This ID is then passed to LASH.
>
> CAUTION!!!! YOU MIGHT LOSE WORK!! READ ON:
>
> - lash_wrap does not care for saving the state of the app in question. So
> before hitting "close" in your favourite LASH session handler, be sure to
> save the session in e.g. ardour manually.
>
> - if the passed jack or alsa client names do not match for whatever
> reasons, then connections won't be restored properly.
>
> You have been warned. Nonetheless this might be useful for people who
> otherwise use scripts to manage their audio sessions.
Just to say thank you for lash_wrap. Seems to work as you stated. I tried it
with Ardour, Audacity and ReZound and as long as you save your work
before closing it works well. Thank you!