Hi Devs, hi Chris
I've just compiled dssi-vst 0n openSUSE10.0 successfull. I'm using wine
0.9.8, liblo 0.22 (build failed with liblo 0.23 because of a linking
prob) and vstsdk 2.4.
dssi-vst works nearly well with the latest rosegarden4 for suse (and the
JAD2 RT kernel). I also get energyXT.dll to work standalone and inside
rosegarden.
dssi-vst works now more stable and faster. Thanks Chris for this
helpfull software and your distribution friendly licence. JackLab will
offer a binary rpm of dssi-vst 0.4 the next days.
More Info www.jacklab.net
Michael
> dssi-vst-server.cpp: undefined reference to `pthread_mutex_trylock'
Does the file (I don't have it to hand and am not at a
proper computer) have
#include <pthread.h>
at the top? If not, what if you add it? It may just
be that another header includes this on other
systems, but not on yours.
Chris
hi, i've been waiting for some help on building dssi-vst 0.4 (recently released), but thought i'd ask around some more ...
On Wed, 2006-03-01 at 13:17 +0000, Chris Cannam wrote:
> dssi-vst: a DSSI plugin wrapper for Win32 VST plugins
> =====================================================
>
> dssi-vst 0.4 is now available.
>
> The main change since the 0.3.1 release is that dssi-vst now builds with newer
> versions of the Wine tools. Wine 0.9.5 or newer is now required.
>
> This release also builds with version 2.4 of the VST SDK, although it should
> still work with the older 2.3 as well.
>
> Download it from:
> http://sourceforge.net/project/showfiles.php?group_id=104230&package_id=127…
>
> You will also need the VST SDK, from:
> http://www.steinberg.de/Steinberg/Developers8b99.html
>
> More information about DSSI:
> http://dssi.sourceforge.net/
>
oh, i've been waiting for this ... thanks for updating to be compatible
with latest Wine!!!
unfortunately, i get errors when trying to build:
[mrmachine@machine dssi-vst-0.4]# make
g++ -I./vstsdk2.4/pluginterfaces/vst2.x -Wall remotepluginclient.cpp -c
g++ -I./vstsdk2.4/pluginterfaces/vst2.x -Wall remotepluginserver.cpp -c
g++ -I./vstsdk2.4/pluginterfaces/vst2.x -Wall -c -o rdwrops.o
rdwrops.cpp
g++ -I./vstsdk2.4/pluginterfaces/vst2.x -Wall -c -o paths.o paths.cpp
ar r libremoteplugin.a remotepluginclient.o remotepluginserver.o
rdwrops.o paths.o
ar: creating libremoteplugin.a
wineg++ -I./vstsdk2.4/pluginterfaces/vst2.x -Wall dssi-vst-server.cpp -o
dssi-vst-server -L. -lremoteplugin
dssi-vst-server.cpp: In member function ‘virtual void
RemoteVSTServer::hideGUI()’:
dssi-vst-server.cpp:566: warning: unused variable ‘fd’
dssi-vst-server-5Pa9Gf.o(.text+0x147e): In function
`RemoteVSTServer::process(float**, float**)':
dssi-vst-server.cpp: undefined reference to `pthread_mutex_trylock'
collect2: ld returned 1 exit status
winegcc: g++ failed.
make: *** [dssi-vst-server.exe.so] Error 2
i'm using a CCRMA-enabled Fedora Core 4.
shayne
So it looks like I may be at LAC2006. I was thinking of bringing my SO
and spending a few days sightseeing after the conference, since we've
never been to Germany. Any recommendations for interesting stuff to do
in the area? We are into nature hikes, history, good restaurants -
pretty boring actually ;-)
Lee
Wow - that's quite a backlog of work.
The software looks fascinating - and the bush-o-matic is priceless!
Loved the personal stuff - you have a beautiful family.
Thanks for sharing, Brad. :)
- Maluvia
>Hey everyone --
>
>Sorry about the multiple postings, but I figured what the heck...
>
>I've just put on-line a whole lot of work I've done; papers, pieces,
>software, etc. Here's the link for the 2-3 people (beyond my immediate
>family) who might be interested:
>There's a fair amount of unix/linux work scattered throughout, including
>the big "My Music Book" thing I did a few years ago.
>
>Hope you enjoy this!
On Wednesday 01 March 2006 12:51, Julian Storer wrote:
> James Courtier-Dutton wrote:
> > "default" means just that. use the name "default" instead of
> > plughw:.... or hw:0,0
[...]
>
> Ok, at the risk of "spreading the myth" that the ALSA documentation is
> bad... is this stuff actually explained anywhere?? It took me a day of
> googling just to find out what the two numbers after "hw" meant! I never
> saw anything mention "default" or "plug:front", etc.
http://www.alsa-project.org/alsa-doc/alsa-lib/pcm.html#pcm_dev_names
Regards,
Pedro
hi everyone!
just a quick heads-up: html postings or other "enriched" atrocities are
banned on linux-audio-*. unfortunately, the mailman response "message
has a suspicious header" is less than helpful. if you see your postings
bounce with this error, in 99 of 100 cases you are trying to send either
html or binary attachments.
this warning applies especially to our friends at gmail.com /
googlemail.com. their web interface seems to send out dodgy mails by
default.
best,
jörn
--
jörn nettingsmeier
home://germany/45128 essen/lortzingstr. 11/
http://spunk.dnsalias.org
phone://+49/201/491621
if you are a free (as in "free speech") software developer
and you happen to be travelling near my home, drop me a line
and come round for a free (as in "free beer") beer. :-D
Quoting Julian Storer <jules(a)rawmaterialsoftware.com>:
> Hi folks
>
> A while ago there was some talk on the newsgroup about my Juce library,
> and people were asking if/when I'd add support for audio under Linux..
> well it's taken me a while to get round to it, but I finally battled
> through the hostile, undocumented jungle of ALSA, and the latest Juce
> release does finally make a noise under Linux!
This is truly great news. I really appreciate the effort you have put into
the port, and to supporting Linux.
Alas, ALSA. It's very unfortunate that you chose ALSA as the API for Linux.
For me, applications without jack support are of zero interest.
I live in a world where i can just connect every soft synth and drum machine
and midi sequencer via jack to ardour, sync them via jack transport, do
mastering inside this environment with Jamin.
I'm capable of exporting & mastering faster-than-realtime, because all the
software inside the "jack loop" will all run in perfect sync, in-time &
on-time with jack instead of the soundcard.
These are the benefits from jack. This is why I will give almost no
consideration for an application which isn't jackd compatible.
The worst thing that can happen is that you get disencouraged. I really do
hope you won't get. Like Paul said, the jackd api is super-simple, you
should have no trouble at all making a driver for JUCE which uses jackd.
Please, pretty please, with sugar, whip cream and a coctail cherry on top.
Don't give up! :)
(And i guess you've already worked through the GUI & input issues of porting
JUCE to Linux, so one more driver should be a breeze)
Sampo
Dear Linux audio people,
sverb 0.90 is out at:
http://sed.free.fr/sverb
sverb is an order 15 cfdn reverb.
Changes:
More presets were added.
If someone wants to contribute a ladspa support, it's welcome.
We could have one effect for each preset (with names like
"short reverb 1", "huge reverb").
Then, for each preset, we can control the reverb with two parameters
(t60(0) and t60(pi)), which would make a nice and tiny GUI.
(Maybe also add a dry/wet control.)
We also need to handle stereo, with a basic decorrelation
for example (different delays for left and right channel).
Since sverb has three internal operating modes (float, int, asm),
I think three .so would be nice. For the asm and int libraries,
we could add a third control for the bit resolution (or leave
it to a default, currently 14, but which could be set at compile
time why not).
Before going to 1.0, I need some feedback about the quality of
the various reverbs (I know that big 2 is not that good).
Also, if someone knows how to define good parameters (by hand
or algorithmically) for the delay lines, help is very welcome.
Take care of yourself,
Cedric.