Hi
A quick note to the followers of the guitarix development,
we have move our repository to git now, you can clone the repository
with the following command :
git clone git://git.code.sf.net/p/guitarix/git guitarix
or browse it here:
http://sourceforge.net/p/guitarix/git/
the SVN repository is still online, but already outdated, and will be
removed sooner or later.
greets
hermann
> Message: 3
> Date: Tue, 31 Jan 2012 13:38:54 +0000
> From: Fons Adriaensen <fons(a)linuxaudio.org>
> Subject: Re: [LAU] Audacity + persistent JACK ports -- was: DC offset
> To: linux-audio-user(a)lists.linuxaudio.org
> Message-ID: <20120131133854.GB7388(a)linuxaudio.org>
> Content-Type: text/plain; charset=us-ascii
> The second is the way Audicity manages its record signal chain. It
> exists (or is active) only when armed for record. This emulates the
> low-cost tape decks of 30 years ago (where it was done to share the
> electronics). But even the more advanced consumer ones at that time
> (those with a separate record head) had the record signal chain
> active all the time, and for anything 'pro' it is really essential.
> You really want to be able to set up a recording session, check
> levels, create a monitor mix, etc. once and while stopped, and not
> having to repeat this each time you arm for record.
I agree that for software today there should be better solutions, but
anyway, even with one head for both, the tape decks 30 years ago (not
all where alCheapo, even with one head for both only) didn't need
repeating the check of levels. OTOH "tape monitoring [1]" with one head
only is impossible ;) and even if an analog tape deck had separated
heads for rec and play, the monitor latency was something beyond of what
we'll have for DAWs today.
Re-doing leveling all the times is a no-go. If this is needed for
Audacity, it must be fixed soon. It wasn't an issue for the one head [1]
multi-track recorder I used in the 80s.
- Ralf
[1] We run into issues regarding to definitions. The kind of monitoring
and the number of heads :D. E.g. folks will see 2 heads in their
elCheapo tape decks ;D.
Hi all,
I recently tried compiling paulstretch on ubuntu 11.04, and found that it
ran into some problems compiling. Here's the output from running
compile_linux_fftw.sh:
PAaudiooutput.cpp:29:9: error: ‘PaStreamCallbackTimeInfo’ does not name a
type
PAaudiooutput.cpp:29:35: error: ISO C++ forbids declaration of ‘outTime’
with no type
PAaudiooutput.cpp:29:43: error: ‘PaStreamCallbackFlags’ has not been
declared
PAaudiooutput.cpp: In function ‘void PAaudiooutputinit(Player*, int)’:
PAaudiooutput.cpp:40:94: error: invalid conversion from ‘int (*)(const
void*, void*, long unsigned int, const int*, int, void*)’ to ‘long unsigned
int’
PAaudiooutput.cpp:40:94: error: too few arguments to function ‘PaError
Pa_OpenDefaultStream(PortAudioStream**, int, int, PaSampleFormat, double,
long unsigned int, long unsigned int, int (*)(void*, void*, long unsigned
int, PaTimestamp, void*), void*)’
/usr/include/portaudio.h:355:9: note: declared here
I did some googling, and it seems that paulstretch is written to use, and
depends on, portaudio version 1.9 (package portaudio19-dev on ubuntu).
However, this conflicts with the more recent version of portaudio, which
Jack (and all my Jack apps) seem to depend on. Does anyone know of a way
around this? Failing that, does anyone know what the likelihood is of
paulstretch being patched to use the newer version of portaudio? (Is
development on it still active?)
Thanks for your help,
James