19 Apr
2004
19 Apr
'04
4:18 p.m.
Torben Hohn and I are pleased to announce the initial release of
jack_fst, a small JACK client designed to run VST FX and VST/i's with
connections to the rest of the JACK world, and, for VST/i's the ALSA
sequencer.
Tarball is available at:
http://linuxaudiosystems.com/fst/jack_fst-1.2.tar.gz
You will need the recently announced FST, a recent version of Wine,
GTK+2 and JACK (from CVS at this time).
Here is a list of VST plugins (actually) that are known to run
successfully with jack_fst:
Ambience.dll
AnechoicRoomSimulator.dll
BarsStripes.dll
Big Tick Hexaline.dll
BLOCKFISH.dll
Boss DS-1.dll
Boss SD-1.dll
Classic EQ.dll
Crystal.dll
Cyanide2.dll
DebaserDemo.dll
DeeLay_sm.dll
Delay Lama.dll
deloizer095.dll
DFX Transverb.dll
dominion v1.2.dll
Drumatic_22.dll
endorphin.dll
E-Phonic XPressor.dll
FLOORFISH.dll
Frohmage.dll
GoldenGate.dll
H2O.dll
JS Vibrato V1.0.dll
LoopaZoid.dll
mabento.dll
MadShifta.dll
mda DX10.dll
mda ePiano.dll
mda Piano.dll
MjMultibandCompressor.dll
MjRotoDelay.dll
ParisEQ.dll
relofter.dll
resolator_1.03_demo.dll
RetroDelay.dll
SIR.dll
sloper.dll
SoloString_v10.dll
SPITFISH.dll
Stretch & Squash.dll
SupaPhaser.dll
Syntar.dll
Tape Delay.dll
THD.dll
themodulator2.dll
Trancemitter.dll
19 Apr
19 Apr
9:51 p.m.
On Mon, 2004-04-19 at 13:11, Paul Davis wrote:
Torben Hohn and I are pleased to announce the initial
release of
jack_fst, a small JACK client designed to run VST FX and VST/i's with
connections to the rest of the JACK world, and, for VST/i's the ALSA
sequencer.
Tarball is available at:
http://linuxaudiosystems.com/fst/jack_fst-1.2.tar.gz
You will need the recently announced FST, a recent version of Wine,
Can you elaborate in terms of which version of wine you have used
successfully? (ie: wine = x.y.z or wine >= x.y.z?)
-- Fernando
20 Apr
20 Apr
12:06 p.m.
On Mon, Apr 19, 2004 at 10:06:11PM -0400, Paul Davis wrote:
i am using wine 20040121. but yesterday i have found a little bug
causing a segfault in the voxengo plugins. after fixing it they work in
vstserver but not yet under libfst.
this bug is fixed in pauls version. so i would recommend that.
--
torben Hohn
http://galan.sourceforge.net -- The graphical Audio language
Can you
elaborate in terms of which version of wine you have used
successfully? (ie: wine = x.y.z or wine >= x.y.z?)
i am using wine 20040309. i think torben has a slightly earlier
version than this which has worked for him to the same extent. 
19 Apr
19 Apr
10:19 p.m.
Our Wine based VST hosting app is doing much better with very recent
Wine's: we are happy with the April 4th build. Most of the compatibility
issues are with GUIs.
Also if you're using threading, they recommend a not-too-recent 2.3.2
glibc to help with threading issues. We are using 2.3.2-4.80.8 and it
looks good so far. Apparently getting threading to work between wine and
glibc has been tricky.
For what it's worth... mo
On Mon, 2004-04-19 at 18:44, Fernando Pablo Lopez-Lezcano wrote:
Can you elaborate in terms of which version of wine
you have used
successfully? (ie: wine = x.y.z or wine >= x.y.z?)
-- Fernando
10:51 p.m.
Our Wine based VST hosting app is doing much better
with very recent
Wine's: we are happy with the April 4th build. Most of the compatibility
issues are with GUIs.
oh, absolutely. i have yet to find a VST that i can't run if i don't
open the editor. admittedly, i am deliberately only trying free VSTs,
but the contrast is remarkable. and for ardour users: ardour can build
its own GUIs for most VST plugins if you need it to.
Also if you're using threading, they recommend a
not-too-recent 2.3.2
glibc to help with threading issues. We are using 2.3.2-4.80.8 and it
looks good so far. Apparently getting threading to work between wine and
glibc has been tricky.
heh. thats where libfst comes in. we started from the mono hack, which
was known to not support threads. i then managed to apply some rather
deep experience i have had with threading on x86 systems to the
problem. nothing particularly clever, but libfst allows us to take a
thread created outside of wine and get wine to "adopt" it, thus
allowing win32 code to be executed by it. ok, so its pretty clever :)
we are at least 50% optimistic that this part of libfst will make it
into wine at some point in the not too distant future.
i will be talking about this work at ZKM in less than 2 weeks.
--p
20 Apr
20 Apr
12:08 p.m.
On Mon, Apr 19, 2004 at 07:12:00PM -0700, Michael Ost wrote:
Our Wine based VST hosting app is doing much better
with very recent
Wine's: we are happy with the April 4th build. Most of the compatibility
issues are with GUIs.
Also if you're using threading, they recommend a not-too-recent 2.3.2
glibc to help with threading issues. We are using 2.3.2-4.80.8 and it
looks good so far. Apparently getting threading to work between wine and
glibc has been tricky.
so are you actually doing the same as libfst ?
--
torben Hohn
http://galan.sourceforge.net -- The graphical Audio language
1:11 p.m.
On Tue, 2004-04-20 at 09:04, torbenh(a)informatik.uni-bremen.de wrote:
On Mon, Apr 19, 2004 at 07:12:00PM -0700, Michael Ost
wrote:
I haven't looked into libfst, but it sounds like 'yes'. However our code
isn't open, as I assume libfst is. Given that I'd be happy to offer help
and insight based on our years working on vst support (ugh!), but we
won't be using it or working on it in the near term.
- mo
Our Wine based VST hosting app is doing much
better with very recent
Wine's: we are happy with the April 4th build. Most of the compatibility
issues are with GUIs.
Also if you're using threading, they recommend a not-too-recent 2.3.2
glibc to help with threading issues. We are using 2.3.2-4.80.8 and it
looks good so far. Apparently getting threading to work between wine and
glibc has been tricky.
so are you actually doing the same as libfst ?
1:37 p.m.
so are you
actually doing the same as libfst ?
I haven't looked into libfst, but it sounds like 'yes'. However our code
1:32 a.m.
Paul Davis wrote:
Torben Hohn and I are pleased to announce the initial
release of
jack_fst, a small JACK client designed to run VST FX and VST/i's with
connections to the rest of the JACK world, and, for VST/i's the ALSA
sequencer.
Tarball is available at:
http://linuxaudiosystems.com/fst/jack_fst-1.2.tar.gz
You will need the recently announced FST, a recent version of Wine,
GTK+2 and JACK (from CVS at this time).
Here is a list of VST plugins (actually) that are known to run
successfully with jack_fst:
I'm getting the following error with jack_fst
make all-am
make[1]: Entering directory `/home/lawrie/src/rpm/SOURCES/jack_fst-1.2'
if gcc -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -I/usr/include/gtk-2.0
-I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0
-I/usr/include/pango-1.0 -I/usr/X11R6/include -I/usr/include/freetype2
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
-I/usr/include/vst -MT jfst.o -MD -MP -MF ".deps/jfst.Tpo" \
-c -o jfst.o `test -f 'jfst.c' || echo './'`jfst.c; \
then mv -f ".deps/jfst.Tpo" ".deps/jfst.Po"; \
else rm -f ".deps/jfst.Tpo"; exit 1; \
fi
In file included from jfst.c:25:
/usr/include/vst/aeffectx.h:934: parse error before "VstFileType"
/usr/include/vst/aeffectx.h:951: parse error before '}' token
make[1]: *** [jfst.o] Error 1
make[1]: Leaving directory `/home/lawrie/src/rpm/SOURCES/jack_fst-1.2'
make: *** [all] Error 2
Commenting out the VstFileType line allows it ito build and run ( at
least with the two VST plugins Ive tried so far)
--
Lawrie Abbott
8:46 a.m.
I'm getting the following error with jack_fst
make all-am
make[1]: Entering directory `/home/lawrie/src/rpm/SOURCES/jack_fst-1.2'
if gcc -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -I/usr/include/gtk-2.0
-I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0
-I/usr/include/pango-1.0 -I/usr/X11R6/include -I/usr/include/freetype2
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
-I/usr/include/vst -MT jfst.o -MD -MP -MF ".deps/jfst.Tpo" \
-c -o jfst.o `test -f 'jfst.c' || echo './'`jfst.c; \
then mv -f ".deps/jfst.Tpo" ".deps/jfst.Po"; \
else rm -f ".deps/jfst.Tpo"; exit 1; \
fi
In file included from jfst.c:25:
/usr/include/vst/aeffectx.h:934: parse error before "VstFileType"
/usr/include/vst/aeffectx.h:951: parse error before '}' token
make[1]: *** [jfst.o] Error 1
make[1]: Leaving directory `/home/lawrie/src/rpm/SOURCES/jack_fst-1.2'
make: *** [all] Error 2
Commenting out the VstFileType line allows it ito build and run ( at
least with the two VST plugins Ive tried so far)
did you run the fixheaders script on the VST headers before building
FST? the configure script would have told you to do that. fixheaders
specifically corrects this problem.
--p
9:12 a.m.
Paul Davis wrote:
Yes, I did run the fixheaders script and it 'fixes' one 'VstFileType
'
instance but doesnt touch this particular one.
Lawrie
I'm getting
the following error with jack_fst
make all-am
make[1]: Entering directory `/home/lawrie/src/rpm/SOURCES/jack_fst-1.2'
if gcc -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -I/usr/include/gtk-2.0
-I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0
-I/usr/include/pango-1.0 -I/usr/X11R6/include -I/usr/include/freetype2
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
-I/usr/include/vst -MT jfst.o -MD -MP -MF ".deps/jfst.Tpo" \
-c -o jfst.o `test -f 'jfst.c' || echo './'`jfst.c; \
then mv -f ".deps/jfst.Tpo" ".deps/jfst.Po"; \
else rm -f ".deps/jfst.Tpo"; exit 1; \
fi
In file included from jfst.c:25:
/usr/include/vst/aeffectx.h:934: parse error before "VstFileType"
/usr/include/vst/aeffectx.h:951: parse error before '}' token
make[1]: *** [jfst.o] Error 1
make[1]: Leaving directory `/home/lawrie/src/rpm/SOURCES/jack_fst-1.2'
make: *** [all] Error 2
Commenting out the VstFileType line allows it ito build and run ( at
least with the two VST plugins Ive tried so far)
did you run the fixheaders script on the VST headers before building
FST? the configure script would have told you to do that. fixheaders
specifically corrects this problem.
--p
7345
days inactive
7346
days old
linux-audio-dev@lists.linuxaudio.org
11 comments
5 participants
participants (5)
-
Fernando Pablo Lopez-Lezcano -
Lawrie Abbott -
Michael Ost -
Paul Davis -
torbenh＠informatik.uni-bremen.de