Unfortunately I am not experienced with writing C-code. I found two websites with programmers that have a lot of experience with writing VST software. I think it is written in C (++) but I am not sure. https://www.hermannseib.com/english/vsthost.htm http://www.synthedit.com/ SynthEdit ofers also a SDK for C-code. May be this can help to wite the VST code for Jamulus?
Right, the key is awareness. Something to mention inside the manual.
Hello Roland, First you have to enable all the soundcards inside the windows sound menu in order to let ASIO4ALL to find the cards. I read you did. Then open the ASIO4ALL setting panel. In case you can't see it in the menu (just as Luuk posted above), you have to reinstall ASIO4all with the settings box checked now. After opening you have to select the right soundcard. To see the properties you have to press the icon right down in the panel to see the card settings. In case your cards don't support...
Hello Luuk, That is true in the case the user has actively checked the online settings box during installation, this menu wil be available. In default the box is uchecked during installation and ASIO4ALL is installed without settings menu option. For most client users, it isn't obvious to check this box on forehand except when you know why.
Ok thanks for the answer Volker. I extracted the argumentlist from the main.cpp file. Here it is. " -i, --inifile initialization file name (client only)\n" The comment explains that this argument is for the client only. I didn't explore the code further, so I was not aware that the server uses the same variable for retrieving the inifile. THX.
I figured out how to run multiple servers on a windows 7 PC. I play in different groups and to do this I want to use different private servers to avoid mix up. It seemed to work, even with 3 servers simultaneous in parallel! but it takes some time to configure the inifiles and server commandlines before each start. The commanline option allows to use jamulus servers with different ports and settings but a workarround is needed to avoid that all the Jamulus servers will share the same settings inside...
Thanks Volker. The only way to discover this kind of cases and to learn from it is by try and error. In this case It was me that had to spend time, but I am happy that it helps you to improve.
I have had the same problem today but reinstallation of both jamulus and ASIO4all didn't work. It took me several hours to figure out what the problem was. I had to use another ASIO host to enable the ASIO4all controlpanel in order to set the sample rate from the wrong 44.1kHz on the right 48kHz. There are soundcards that use 44.1 kHZ for standard but you can't correct this before ASIO4all has started. The problem is that Jamulus stops without giving the user any access to the ASIO driver controlpanel...