Hello list!
I am using my AMD64 with hammerfall, FC3T1, and 2.6.10-lsm and it
works relitively fine (PD at approx. 10.97 ms latency) but I
still get the occasional xrun. How can I track down the cause?
Please help as I am somewhat at a loss how to get this machine
performance stable.
Thank you for your help!
-thewade
"Georg Holzmann" <georg.holzmann(a)student.kug.ac.at> writes:
> thanks.
Might be worthwhile to check out what's wrong with your mail
application. It's not generating correct references.
--
Esben Stien is b0ef(a)esben-stien.name
http://www.
irc://irc. /%23contact
[sip|iax]:
jid:b0ef@
Greetings:
Users are constantly wrestling with issues surrounding the software
mentioned in the subject line, and I would like to find out what
directions are planned for those projects. Here's what I see now:
1. The vstserver project is functionally dead. It cannot work with
newer versions of WINE, and it appears that Kjetil does not plan to keep
it updated to accommodate the new versions. Alas, this also means that
his nice vsti, ladspavst, and k_vst~ projects are also unusable. :(
2. The libfst project is essentially unmaintained. Again, WINE
versions wreak havoc with users who want to keep both fst and WINE
up-to-date. Paul and/or Torben: Is the libfst project going to see any
more activity from your end, or should it be considered an open project
and up for grabs ?
3. The dssi-vst bridge is still unknown to me because of issues with
RH9, and I've not had time to test it on FC3. But is there any general
feeling that dssi-vst is a better route to take, at least for the normal
user ? Btw, I like the DSSI API, but it seems slow in catching on with
developers. Is that perception correct ?
Please understand that I'm in no way criticising the work done on
these projects so far. In point of fact, I'm extremely happy they exist,
but I'm also in considerable doubt whether they can continue to be
useful without further maintenance. Users are writing to other users to
figure out how to fix small problems (usually with libfst), but these
repairs are not making their way back into the codebase, which seems
rather non-optimal to me. I'm also aware that the greater problems exist
because of WINE's inherent instability (WRT its development, not
necessarily its usability) and that Linux audio developers can't be
responsible for WINE fixes too. Perhaps more crosstalk between the WINE
developers and the LAD folk (similar to the recent discussion re: the
kernel list and LAD) would help smooth the way for a more consistent and
more manageable VST/VSTi bridge for Linux ?
So, any comments or useful suggestions ?
Best,
dp
I'm trying to write a drum part in hydrogen, but it needs to be in 3/4
time. I see no way to do that in version 0.9.1. The forums at
www.hydrogen-music.org recommend changin the "pattern length" to
achieve deifferent time signatures, but doing so doesn't have any
affect.
Even if that did work, I would have to triple my tempo, right? The
tempo control, besides disallowing manual entry and requiring you to
use the spin button (yuck), only goes up to 300. Since the song is in
112, I would need it to go up to 336, right? Or do I misunderstand
what patttern length means?
Any hydrogen experts out there?
I'm attempting to resurrect the aabuild "alsa from cvs"
script but running into an issue with building alsa itself,
and also unsure of "the right" method to blend in alsa from
cvs with a kernel source tree.
Any comments about how to improve these two functions would
be appreciated and any clue as to the error when compiling
alsa-lib would also go down well.
setup_alsa()
{
cd $CVSDIR/alsa
if [ ! -d ./CVS ]; then
echo "Just hit the enter key at the login prompt"
cvs -d ':pserver:anonymous@cvs.alsa-project.org:/cvsroot/alsa' login
cvs -z3 -d ':pserver:anonymous@cvs.alsa-project.org:/cvsroot/alsa' co -P .
else
[ "x$(find -type d -name CVS -cmin -720)" = "x" ] && cvs up -P -d
fi
cd $SRCDIR
rm -rf alsa/*
cp -a $CVSDIR/alsa/* alsa
find alsa/alsa-kernel -type d -name CVS | xargs rm -rf
rm -rf alsa/alsa-kernel/oss
cp -a alsa/alsa-kernel/* linux/sound
cp -a alsa/alsa-kernel/include/* linux/include/sound
cp -a alsa/alsa-kernel/Documentation/* linux/Documentation/sound
}
Are the above steps copying the the alsa-kernel parts into the
linux source tree correct these days ?
build_alsa()
{
cd $SRCDIR/alsa
for i in alsa-lib alsa-utils alsa-tools alsa-firmware alsa-plugins alsa-oss
do
cd $SRCDIR/alsa/$i
./cvscompile
done
}
I'm getting this error below in the first alsa-lib stage above...
...
Making all in src
make[3]: Entering directory `/usr/src/alsa/alsa-tools/ld10k1/src'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/usr/src/alsa/alsa-tools/ld10k1/src'
make[3]: Entering directory `/usr/src/alsa/alsa-tools/ld10k1'
make[3]: Leaving directory `/usr/src/alsa/alsa-tools/ld10k1'
make[2]: Leaving directory `/usr/src/alsa/alsa-tools/ld10k1'
make[1]: Leaving directory `/usr/src/alsa/alsa-tools/ld10k1'
/usr/share/aclocal/xdelta.m4:7: warning: underquoted definition of AM_PATH_XDELTA
run info '(automake)Extending aclocal'
or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
/usr/share/aclocal/wxwin.m4:36: warning: underquoted definition of AM_OPTIONS_WXCONFIG
... (heaps of similar warnings)...
/usr/share/aclocal/ORBit.m4:4: warning: underquoted definition of AM_PATH_ORBIT
aclocal:configure.in:12: warning: macro `AM_PATH_LD10K1' not found in library
configure.in:12: error: possibly undefined macro: AM_PATH_LD10K1
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
autoreconf-2.59: /usr/bin/autoconf-2.59 failed with exit status: 1
CFLAGS=-O2 -Wall -pipe -g
./configure
configure: error: cannot find install-sh or install.sh in . ./.. ./../..
make[1]: Entering directory `/usr/src/alsa/alsa-tools/qlo10k1'
make[1]: *** No targets specified and no makefile found. Stop.
make[1]: Leaving directory `/usr/src/alsa/alsa-tools/qlo10k1'
make[1]: Entering directory `/usr/src/alsa/alsa-tools/qlo10k1'
make[1]: *** No targets specified and no makefile found. Stop.
make[1]: Leaving directory `/usr/src/alsa/alsa-tools/qlo10k1'
make: *** [all] Error 2
--markc
Hello list. I've been looking for some documentation about how to
execute NoteEdit from terminal, but I don't find anything. In "man
noteedit" there are some options to execute some characteristics from
terminal, but it's not enough.
My idea is to import a midi file and show the score. I know
NoteEdit
does it bye Tse3, but I woudl like to know how to do it from terminal.
Does anyone have any information about commands with NoteEdit?
Thank you very much.
Hey Hey there,
turns out I'm doing Sound design for a play that's going up very
soon(2 run-throughs tomorrow, then we open thursday evening), and
I'd love to have some ambient city noise going on throughout most
of the play(it takes place in an apartment in New York City), but
I'm having trouble finding what I'm looking for. Does anyone have
any city sound effects? I've found lots of car horns, which is
mostly what drifts up, but it's still not convincing. There's
some field recordings on freesound of barcelona, but I'm still
waiting for a membership confirmation email before i can download
them. I'm using Ardour to record and edit the other sound effects
for the show, as well as some custom circuitry to do things like
make a phone ring onstage.
any other linuxy sound designers out there?
-spencer
Hi,
due to the lower latency of the 2.6 kernel I have decided to upgrade
to FC3. I have setup a test HDD to verify I get all my oddities
working before I actually upgrade my very stable FC1 that is currently
using jack_fst for VST.
Here is what I've learned so far:
Ndiswrapper:
My SMC2802W Wifi card and Ndiswrapper work with the 8 kb stack coming
by default in the Planet CCRMA 2.6.11 kernel. However, to make it work
one needs the kernel sources and one needs to _compile_ the kernel,
even if the binary is not used, for Ndiswrapper to compile.
DSSI
Works on the planet FC3 with the 2.6.11 as a synaptic update.
wine-20040505
This release is the musicians friend, or at least mine. After install
from rpm a link to lind d: to /media/cdrecorder is needed to make it
use the CD rom. Also some configuration editing was needed in
.wine/config e.g. the temp directory has to be deleted or defined.
dssi-vst
Does not compile with wine-200503031, 20041201 nor 20040505. No luck here.
fst-1.5
Compiles, but copies libfst.so to /usr/local/lib. jack_fst expects
libfst.so to be in /usr/lib, so some handy work is needed here to make
it work.
fst-1.6
Compiles, but install is missing a utility called mkinstalldirs which
makes the installation halt. One needs either to copy the
mkinstalldirs utility from fst-1.5 or then creage the requested
directories by hand for this to install. The install also installs
libfst.so to /usr/local/lib while jack_fst expects them to be in
/usr/lib. More handywork needed.
jack_fst-1.2
Requires wine-20040505 to compile. The Readme file seems to be an
implementation note rather than a user document. Jack-fst needs a lot
of guessing to make work. One needs the Steinberg SDK files and then
one needs to edit one of the jack_fst source files by hand to make it
compile. It can be done, but this is really, really ugly. I would have
given up unless I would have known I was able to make it work in FC1.
Native Instruments B4 organ.
This VST instrument is the reason for all this trouble. I have had it
working in FC1 for quite a while and I got it working last night with
jack_fst and the dependencies also in FC3, which concluded my testing.
Conclusions:
Making VST work in Linux was very difficult. I never managed make
dssi-vst vwork. None of the needed software installed without tweaking
and a lot of trial and error. This took a couple of long nights for
me, and I have been a Linux user for over 10 years and I have
installed jack_fst once earlier. My judgement is that it is quite
impossible for the average musician to make VST work under Linux. We
need to fix this and lower the threshold for VST under linux. The
tools are there, it is the polishing that is missing.
When I have the time to update my FC1 I will document every step in
notes on how to make VST work with jack_fst and publish them here for
public scrutiny.
br, Timo
I'm resuming my exploration of SC3
( http://supercollider.sourceforge.net/ ) and my strong aversion to
emacs has led me to search for a useful gtk2 frontend for sclang.
ggap ( http://ggap.sourceforge.net/ ) seems to be 99% ready for use.
http://ruinaudio.com/files/ggap_sc3.png
The author is very nice and has generously considered adding some SC3
specific features. I'm absolutely NOT the person to come up with a list
of features, but since I got the ball rolling I put together a intro to
SC3, and a list of SC3 features that are commensurate with the goals of
ggap. http://ruinaudio.com/files/ggap_ideas.txt
If any experienced SC3 users are interested in sharing thoughts about
what features might be useful please visit the ggap page, or email me,
or drop by #ggap on freenode.
thanks,
-ry
--
Ryan Gallagher <ruinaudio(a)comcast.net>