Sujet [News] Ninjam, le skype des musiciens

Citation : non, c'est impossible. les latences d'encodages decodages vont reduire avec la vitesse des procos, mais en ce qui concernela latence du reseau, il est impossible de la stabiliser, on peine deja parfois en reseau local (la latence existe), alors a l'echelle du net....

Citation : Ne serais-ce pas imaginable d'intégrer un clic, voir un hôte pour vst?

Citation : NINJAM server setup guide
To set up a NINJAM server, first find a host that has an abundance of outbound bandwidth. Or if you want to use NINJAM on a LAN with all of the hosts local, that is an option as well. The server can currently run on Windows, OS X, Linux, and FreeBSD. To download the server for your platform, see the download page.

To install the server, extract the archive (or copy the contents of the .dmg if on a mac) to a directory, then edit the example configuration file to suit your needs. Here is a list of the most commonly used configuration items and what they mean:

* Port n - port for server to listen on. The default is 2049.
* MaxUsers n - maximum number of users allowed.
* AnonymousUsers yes|no - allow users to log in anonymously (if no, only users with a valid login/password will be allowed)
* AnonymousUsersCanChat yes|no - allow anonymous users to send chat messages (if no, they can play, but can't contribute to the chat)
* ServerLicense filename.txt - forces users to view and agree to the license provided to connect. This is useful if you want to run a public server and make people who contribute to a jam license their parts under a Creative Commons or similar license (or whatever license you choose)
* ACL mask allow|deny|reserve - This adds an entry to the Access Control List (ACL). The configuration file can have any number of these, and the first match is used. mask is in the format of x.x.x.x/y, i.e. 192.168.0.0/16 or 66.88.120.240/28. allow specifies to allow connections, deny specifies to not, and reserve specifies to always allow (even if there are too many users connected).
* User username password [permissions] - This adds an authorized user to the user list. If permissions are specified, the default permissions are overridden. Specify * for all access, or include any combination of the following to enable them:
o C - allow this user to chat with other users
o T - allow this user to set the server topic
o B - allow this user to adjust BPM / BPI of server
o K - allow this user to kick other people
o R - allow this user to log in even when server is full



Once you've set the configuration the way you think you will like it, you can run the server:

* On OS X/Linux/FreeBSD (OS X will require you to open a terminal and go to the proper directory):
./ninjamsrv configfilename.cfg
* On Windows (after opening a command line, and going to the proper directory):
ninjamsrv configfilename.cfg

If you need ot change the configuration once the server is running, you can restart it by hitting R (on Windows), or by using the command "killall -INT ninjamsrv" (on Linux/FreeBSD/OS X).