Hm... I guess you could get one of those integrated mixer/usb audio interface devices. I was thinking you might get a straight audio interface and use your existing mixer. You'd plug your ins/outs on the mixer through the interface. This is the maximally flexible way of doing it, as you can change your mixer over time or in different situations, but keep the same interface. But getting a small interface/mixer unit would be cheaper and you'd still get a vastly improved recording quality over plugging your instruments into your sound card.

While I'm thinking about it, when you get your audio interface, use 48kHz as your sampling rate. 44.1 is "good" and I consider 96k overkill. I still don't understand why 96k is available at all, since the highest frequency recorded at this rate is is 48KHz - more than twice the range of human hearing. 48kHz records at 24kHz, which is the upper limit of human hearing plus a little headroom, which lets you give things a nice sparkle and shimmer if you want, as opposed to 44.1, which records at 22, which is almost exactly the upper limit of someone young with exceptionally sharp ears.

Man, really thanks for that advice.
I always looked for the 96Khz because, well, 96 > 48 and i thought that 48 was worst.
So apparently it's just marketing. Pay more for nothing, the slogan for our world.

Some people think they can hear a difference between 48 and 96, but thus far, I've noticed that people who actually understand the science (this was my major at university. All hail Nyquist! ) hear no difference at all.

Some people think they can hear a difference between 48 and 96, but thus far, I've noticed that people who actually understand the science (this was my major at university. All hail Nyquist! ) hear no difference at all.

This is incorrect. The truth is that :
Some people believe (rightly or wronly) they actually feel a difference between 48 and 96, but thus far, I've noticed that people who actually get some understanding of the science claim (rightly or wrongly) that there are no grounds for such belief.

audiodef wrote:

So yeah, my opinion is "it's the power of marketing"... I just think 48 is good for recording and mastering, then you export the final mix to 44.1 to make it compatible with the most playback devices.

My personal opinion is very different and leads to a very different advice.
This comes from the following experience anybody can do :

Collect half a dozen of audiopĥiles among those scientists convinced by the fact they cannot hear any difference between 48 and 96.
With the same hardware, record in 48 some good quality instruments (Cello solo - Orchestra... well... I mean forget the overdriven guitar...), record the same thing in 192
Resample both to 44.1.
Offer your guests to choose between the two 44.1 playbacks, not the one they find the best but the one they like the more !
Guess what they unanimously say !

BTW bit depth is even more important and actually... hearable... but this is another discussion.

=> My advise is : always record to the highest possible frequency (even if you do not know why you should)

I did a little googling and found both projects are in fact part of the C++ Library for Audio and Music (CLAM). They are example applications distributed with the library/framework. The correct homepage is: http://clam-project.org/index.html

I'm not sure if the ebuilds work as they exist in the overlay. I just wanted to find out what they did and went looking for more information. Finding out the homepage information is outdated made me hesitate to try installing them. I also didn't see any ebuilds for CLAM.

It seems that lv2-1.0.0 in the main Portage tree is meant to replace lv2core in the proaudio overlay. The following are two packages whose ebuilds I modified to depend on lv2 instead of lv2core, in order to prevent a Block when updating.

media-plugins/calf-0.0.18.6-r1:

Code:

# Copyright 1999-2011 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

EAPI="2"

inherit base multilib

DESCRIPTION="Calf is a set of open source instruments and effects for digital audio workstations"
HOMEPAGE="http://calf.sf.net/"
SRC_URI="mirror://sourceforge/${PN}/${P}.tar.gz"
RESTRICT="mirror"

First try at trying to setup the proaudio stuff. Lash-0.6.0_rc2 fails to emerge with the following error message:

Any suggestions would be appreciated.

It seems the docs are tripping you up. There's no doc use flag, so must be something on your system that's interfering with the final install phase. I just compiled it without error. What's your emerge --info?

FYI, you're welcome to post here, but this thread is actually for little fixes and hacks that aren't necessarily in line with the goals and methods of the pro-audio overlay. You might want to post here, since your issue is about something that should work right out of the pro-audio overlay box:

I just finished emerging a guitar workstation with guitarix and sooperlooper as the main applications. The ebuild for zita-convolver is broken currently. The upstream developer of the actual zita-convolver package has moved the hosted location for the 2.0.0 version as he has a 3.0.x version available now. I managed to find the 2.0.x file and drop it into the /usr/portage/profiles/ folder and solve the problem temporarily. however this issue will need to be resolved in order to keep guitarix building properly.

And on a side note I want to tank everyone working on this project for helping to make a fantastic set of softwares available easily.

I just finished emerging a guitar workstation with guitarix and sooperlooper as the main applications. The ebuild for zita-convolver is broken currently. The upstream developer of the actual zita-convolver package has moved the hosted location for the 2.0.0 version as he has a 3.0.x version available now. I managed to find the 2.0.x file and drop it into the /usr/portage/profiles/ folder and solve the problem temporarily. however this issue will need to be resolved in order to keep guitarix building properly.

And on a side note I want to tank everyone working on this project for helping to make a fantastic set of softwares available easily.

Reducing redundancy. This is now a list of what ebuilds that have been fixed. Please visit this page to view more details. This post will simply be edited to add or delete package names, rather than adding more posts to this thread. This makes it easier to bookmark this post and refer to it.