mkdir -p /usr/local/lib/dssi/dssi-vst mkdir -p /usr/local/lib/ladspa mkdir -p /usr/local/bin install dssi-vst.so /usr/local/lib/dssi install dssi-vst.so /usr/local/lib/ladspa install dssi-vst-server.exe.so dssi-vst-server dssi-vst-scanner.exe.so dssi-vst-scanner dssi-vst_gui /usr/local/lib/dssi/dssi-vst install: can't get informations about (I translated this sentence from czech language) „dssi-vst-server“: No such file or directory install: can't get informations about „dssi-vst-scanner“: No such file or directory make: *** [install] Error 1
I don't know where is my problem. What should I do <
I have install DSSI-VST+vstsdk2.4 in Linux Mint, but some plugins don't work(or not open correctly), Antress Modern Plugins, Kontakt 3, SampleTank 2.5, and others...
Have you a solution for this case?
My DAW is "Cockos Reaper", in this case the plugins vst2.4 don't work too...
Hmm, I shall have to have a go with this version of wine. I wonder whether it's changed something significant.
Your file dssi-vst-server.exe is very small, probably too small to be a plausible executable binary. Is it actually the script that the Makefile is expecting to be called dssi-vst-server? Try running "file" on it, and, if it is a script, try simply renaming it from dssi-vst-server.exe to dssi-vst-server. And, I suppose, the same for dssi-vst-scanner.exe. And then make install. Well, it has to be worth a try!
Plugin support is rather an inexact science with an emulation system like this -- a lot depends on the version of Wine that you are using, and on the plugin itself. I would suggest that you cross-check with the compatibility list at http://ladspavst.linuxaudio.org/ to get an idea of the expected level of compatibility with various plugins.
If you can give detailed descriptions of the way in which individual plugins fail, and particularly if you can see any consistencies (i.e. a number of plugins all fail in the same way), then do let us know -- it might be something that could be acted upon.
my Wine is latest version ever(now 1.1.18), I know about plugins compatibility, but Antress Modern Plugins work correctly previously, and in this time don't work, I'm working on a distro with native VST suport, and my results is the best, but some plugins are necessary for finalize my job...
now I try to use VeSTige to compile DSSI-VST and Ardour VST 3.0
Thanks for reply, i'm very interested in evolution of this project, tell me evertime...
Hello Raudipeas, I think we have the same problem and don't know how to solve it. after make install, it printed out "dssi-vst-server' and "dssi-vst-scanner" - no such file or directory. I will try to rename dssi-vst-server.exe to dssi-vst-server and the same for dssi-vst-scanner.exe... and then will try make install.
Hello, I can't execute a vsti plugin, I got this message, although I tried to rename dssi-vst-server as dssi-vst-server.exe :
syner@synerbook:~/progs/dssi-vst-0.8$ vsthost SUPERWAVEP8.dll Returning file identifiers: XqmkYc5RQbpUoZY3PBunIWgj Failed to find dssi-vst-server executable: No such file or directory vsthost: bailing out
I don't know why it can't find a dssi-vst-server executable
I remember some wrappers from Windows, it looks like a vsti plugin dll, but wraps other dlls. I am focusing on Renoise. I found an interesting tutorial video using dssi: http://video.aol.com/video-detail/renoise-tutorial-windows-vst-instruments-in-linux/2249818521. Is it possible to make a dll, that I can find in Renoise instrument's section ? Renoise would scan that plugin on the startup and recognized it like a vst instrument, but it would be a dssi-vst-wrapper, so you could load a win vst instrument ? Connecting through jack is very difficult. So this is a thought for a vst-wrapper for renoise, the best tracker I have ever seen. (except Octamed of course :-D)
I'm trying to run a VST plugin that relies on it's method idle() being called by the host on a regular basis to update it's GUI. I have read in the dssi-vst website that:
"Graphical elements in the plugin GUI that are intended to respond to audio input may be inactive."
So I understand it is an unimplemented feature and thus an expected behaviour. I was just wondering how hard would this be to fix and if anyone could help me out working on this. What files of dssi-vst should I start looking at? and what functions should I modify/add?
Sorry to take so long to respond to any of these: call it forum operator confusion in failing to see that there were new posts. Must do better.
syner, the most obvious (too obvious?) reason for the "Failed to find dssi-vst-server" error is that the dssi-vst-server program is not installed in the expected place - the plugin searches in locations relative to the DSSI plugin path for its auxiliary programs. If you haven't done so already, try "make install" to install. Using the plugin without installing it is more complicated.
rikrd, your analysis is right I think. Fixing this _ought_ to be quite simple, though there may be threading issues to think about. The whole of the VST-side logic is found in dssi-vst-server.cpp, and the question really boils down to "where should we periodically invoke the effEditIdle dispatcher from?"
Hi im trying to install and i have the following errors: make wineg++ -m32 -Ivestige -Wall -fPIC dssi-vst-server.cpp -o dssi-vst-server -L. -lremoteplugin.w32 -lpthread dssi-vst-server.cpp: In member function ‘virtual void RemoteVSTServer::hideGUI()’: dssi-vst-server.cpp:568: aviso: variable ‘fd’ sin usar /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.3.3/libstdc++.so when searching for -lstdc++ /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.3.3/libstdc++.a when searching for -lstdc++ /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.3.3/libstdc++.so when searching for -lstdc++ /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.3.3/libstdc++.a when searching for -lstdc++ /usr/bin/ld: cannot find -lstdc++ collect2: ld devolvió el estado de salida 1 winegcc: g++ failed make: *** [dssi-vst-server.exe.so] Error 2
i have listdc++6 installed if it help for something thank u
ok i got it,i didnt read the note for ubuntu x64 and ive got these libs now but i having another error
make g++ -Ivestige -Wall -fPIC dssi-vst_gui.cpp rdwrops.o -o dssi-vst_gui -llo dssi-vst_gui.cpp:24:19: error: lo/lo.h: No existe el fichero ó directorio dssi-vst_gui.cpp:25:28: error: lo/lo_lowlevel.h: No existe el fichero ó directorio dssi-vst_gui.cpp:33: error: ‘lo_server’ no nombra a un tipo dssi-vst_gui.cpp:36: error: ‘lo_address’ no nombra a un tipo dssi-vst_gui.cpp:59: error: ‘lo_arg’ no se ha declarado dssi-vst_gui.cpp: In function ‘int debug_handler(const char*, const char*, int**, int, void*, void*)’: dssi-vst_gui.cpp:68: error: ‘lo_type’ no se declaró en este ámbito dssi-vst_gui.cpp:68: error: ‘lo_arg_pp’ no se declaró en este ámbito dssi-vst_gui.cpp: At global scope: dssi-vst_gui.cpp:77: error: ‘lo_arg’ no se ha declarado dssi-vst_gui.cpp:85: error: ‘lo_arg’ no se ha declarado dssi-vst_gui.cpp:93: error: ‘lo_arg’ no se ha declarado dssi-vst_gui.cpp: In function ‘int show_handler(const char*, const char*, int**, int, void*, void*)’: dssi-vst_gui.cpp:98: error: ‘hostaddr’ no se declaró en este ámbito dssi-vst_gui.cpp:102: error: ‘lo_send’ no se declaró en este ámbito dssi-vst_gui.cpp: At global scope: dssi-vst_gui.cpp:108: error: ‘lo_arg’ no se ha declarado dssi-vst_gui.cpp: In function ‘int hide_handler(const char*, const char*, int**, int, void*, void*)’: dssi-vst_gui.cpp:113: error: ‘hostaddr’ no se declaró en este ámbito dssi-vst_gui.cpp:117: error: ‘lo_send’ no se declaró en este ámbito dssi-vst_gui.cpp: At global scope: dssi-vst_gui.cpp:123: error: ‘lo_arg’ no se ha declarado dssi-vst_gui.cpp:132: error: ‘lo_arg’ no se ha declarado dssi-vst_gui.cpp: In function ‘void readFromPlugin()’: dssi-vst_gui.cpp:162: error: ‘hostaddr’ no se declaró en este ámbito dssi-vst_gui.cpp:164: error: ‘lo_send’ no se declaró en este ámbito dssi-vst_gui.cpp:170: error: ‘hostaddr’ no se declaró en este ámbito dssi-vst_gui.cpp:172: error: ‘lo_send’ no se declaró en este ámbito dssi-vst_gui.cpp: In function ‘int main(int, char**)’: dssi-vst_gui.cpp:235: error: ‘oscserver’ no se declaró en este ámbito dssi-vst_gui.cpp:235: error: ‘lo_server_new’ no se declaró en este ámbito dssi-vst_gui.cpp:236: error: ‘lo_server_add_method’ no se declaró en este ámbito dssi-vst_gui.cpp:244: error: ‘lo_url_get_hostname’ no se declaró en este ámbito dssi-vst_gui.cpp:245: error: ‘lo_url_get_port’ no se declaró en este ámbito dssi-vst_gui.cpp:246: error: ‘lo_url_get_path’ no se declaró en este ámbito dssi-vst_gui.cpp:248: error: ‘lo_server_get_url’ no se declaró en este ámbito dssi-vst_gui.cpp:250: error: ‘hostaddr’ no se declaró en este ámbito dssi-vst_gui.cpp:250: error: ‘lo_address_new’ no se declaró en este ámbito dssi-vst_gui.cpp:254: error: ‘lo_send’ no se declaró en este ámbito dssi-vst_gui.cpp:274: error: ‘lo_server_recv_noblock’ no se declaró en este ámbito make: *** [dssi-vst_gui] Error 1
It doesn't appear to be practical to support set/getChunk without some modifications to the DSSI API itself and to its hosts. Unfortunately, this implies quite a lot of coordination to make the results widely available.
Andrew Deryabin has produced some modifications to dssi-vst, DSSI, and Rosegarden 1.7.3 to support get/setChunk, but these have not yet been integrated into any standard public version of any of them - partly I think owing to simple lack of developer time to review them and consider the implications for problems and compatibility issues. I think this will happen, it just hasn't happened yet.