Sorry for the ‘noob’ questions in advance! I wish to run a server and client on the same machine for the purposes of testing public vs private servers and so on, but have a beginner question:
How do you run a server and client at the same time on the same machine? I can see how to launch the server, but in order to see the client window I have to close the server window, which presumably means the server isn’t running anymore?
So maybe my question is also - does the server keep running if the window is closed (but Jamulus remains open)?
(Maybe this is documented somewhere but jiggered if I can find it!)
Running 3.4.7 on MacOS 1-.15.4
Thanks!!
Last edit: thirdspace 2020-04-13
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Mike - I'm new to Jamulus also...but running 3.4.7 on an iMac 10.13.6. This works for me: start the server in terminal. The Jamulus icon shows as running in the doc. Close that, but keep server app running in terminal. Then reopen Jamulus from the doc. You should see your server at the top of the list when you start to connect. Good luck!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks Bill and Gilongo - I know this is pretty basic stuff but both answers seem the wrong way round to me. If I start the server from Terminal, the server window opens. If I close this window, the server stops, no?
However, if I open Jamulus client first then start the server from terminal I can have both windows open at the same time. Then I can create a public server, and use the client app to connect to it, when I can see that it has appeared in the public server list. If I close the server window, my server disappears feom the server list so I assume it is no longer running. Sorry if I have misunderstood anything in your answers but I can't see how to do this if you start the server first, as in the manual.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
However, if I open Jamulus client first then start the server from terminal I can have both windows open at the same time. Then I can create a public server, and use the client app to connect to it
Yes, that's correct. You need to keep the server running while you (and other people) connect to it.
However, I suspect you may be confused by the line "You can stop the server by quitting the server window...." is that right? Maybe we should just remove that as it would probably be obvious to anyone how to stop their server when they wanted to.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Many thanks for the reply. Actually I was confused by the line "If you want to run a client on the same machine, simply start Jamulus as you would normally (it will be in client mode)." To me that sounds like having started the server, you can then start Jamulus in client mode - which I can't see how to do. I can now see that you start a in client mode first, then start a server if you want both to run at the same time on the same machine. Unless there's some terminal command way of opening a client window after opening a server window?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Oh OK, sorry. Once you've got the Jamulus server window up (and configured it how you want), you can run the client on the same machine by launching Jamulus as you would do normally (ie to connect to a server). This depends a bit on where you put the Jamulus application when you first installed it (and perhaps how you normally launch applications), but if it's in Applications, you just double-click on it from there, or if you have it in your Dock you can click on that, or if use Launcher, use that etc. You will then have two windows: one with the Client and one with the Server.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Apologies - but still a bit confused by this. I can only see both client and server if I do the following:
Double click Jamulus icon launches client
Then launch server from Terminal (I'm on a Mac)
If I lauch the server (window) fisrt, then double clicking the Jamulus icon (Finder or Dock) has no result.
Did you mean by "you can run the client on the same machine by launching Jamulus as you would do normally (ie to connect to a server)" that I could launch the client window with a Terminal command, as that is how I launch the server window?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Right now, the only way you can launch the server on Mac is via the Terminal window. You can launch the client via Terminal too of course (without the -s option, obviously), but you don't have to.
That said, I don't know why double clicking the Jamulus icon has no result in your case. Perhaps if you try launching it via the Terminal and see if there's any error message shown. Also worth looking to see if Console is reporting any errors with it and if you find anything paste it here?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think I understand Mike Watkinson's problem which I believe is one of the right sequence of how to start client and server:
If I start ( on a 1 year old updated Mac) the server from the terminal app first, the server starts. But if then, in a second step, I try to start the Jamulus app (from dock or from app folder) in client mode by simply double clicking it, the client window/app does not open and the already open server window just highlights. So it seems my Mac thinks I want to open the already running server.
So I wrote me a little cue card with the right sequence, which always works for me:
Start Jamulus client software ... but do not connect to any server, yet
Open terminal window
Start Jamulus server with respective command line that includes path and server commands such as e.g. -w for the welcome message ...
Now, I can connect to any server or my own server. Sometimes I can find my server in the list from the get-go, sometimes my initial connect has to be with 127.0.0.1
Mike, is that what you meant? I hope I could help
Memo: Join my daily Jazz Jam Session on the Ofi Jz Lge 7&9pm cet server - my server welcome message shows the current suggested playlist
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
FWIW I have had the same problem, with the interesting complication that after thrashing around not understanding which had to open first, client or server, that I managed to have a client process running but no client window. (This prevented me from starting a client after I'd started the server.) Killing all Jamulus processes and starting over in the proper order, of course, fixed everything.
Would it be possible to give the user a head's up, if they try to start a server on a machine where a client is running?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Having to start the Jamulus server on a Mac using the command line is not nice at all. We should find a way to improve that to be more user friendly. Hopefully there is a solution where you have two icons for client and server on a Mac, similar to what we have for Windows.
I have created an issue on Github for this problem: https://github.com/corrados/jamulus/issues/89
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry for the ‘noob’ questions in advance! I wish to run a server and client on the same machine for the purposes of testing public vs private servers and so on, but have a beginner question:
How do you run a server and client at the same time on the same machine? I can see how to launch the server, but in order to see the client window I have to close the server window, which presumably means the server isn’t running anymore?
So maybe my question is also - does the server keep running if the window is closed (but Jamulus remains open)?
(Maybe this is documented somewhere but jiggered if I can find it!)
Running 3.4.7 on MacOS 1-.15.4
Thanks!!
Last edit: thirdspace 2020-04-13
Hi Mike - have a look at the wiki on this: https://github.com/corrados/jamulus/wiki/Server---Mac
If you have any questions or comments for improvements, let us know!
Mike - I'm new to Jamulus also...but running 3.4.7 on an iMac 10.13.6. This works for me: start the server in terminal. The Jamulus icon shows as running in the doc. Close that, but keep server app running in terminal. Then reopen Jamulus from the doc. You should see your server at the top of the list when you start to connect. Good luck!
Thanks Bill and Gilongo - I know this is pretty basic stuff but both answers seem the wrong way round to me. If I start the server from Terminal, the server window opens. If I close this window, the server stops, no?
However, if I open Jamulus client first then start the server from terminal I can have both windows open at the same time. Then I can create a public server, and use the client app to connect to it, when I can see that it has appeared in the public server list. If I close the server window, my server disappears feom the server list so I assume it is no longer running. Sorry if I have misunderstood anything in your answers but I can't see how to do this if you start the server first, as in the manual.
Yes, that's correct. You need to keep the server running while you (and other people) connect to it.
However, I suspect you may be confused by the line "You can stop the server by quitting the server window...." is that right? Maybe we should just remove that as it would probably be obvious to anyone how to stop their server when they wanted to.
Many thanks for the reply. Actually I was confused by the line "If you want to run a client on the same machine, simply start Jamulus as you would normally (it will be in client mode)." To me that sounds like having started the server, you can then start Jamulus in client mode - which I can't see how to do. I can now see that you start a in client mode first, then start a server if you want both to run at the same time on the same machine. Unless there's some terminal command way of opening a client window after opening a server window?
Oh OK, sorry. Once you've got the Jamulus server window up (and configured it how you want), you can run the client on the same machine by launching Jamulus as you would do normally (ie to connect to a server). This depends a bit on where you put the Jamulus application when you first installed it (and perhaps how you normally launch applications), but if it's in Applications, you just double-click on it from there, or if you have it in your Dock you can click on that, or if use Launcher, use that etc. You will then have two windows: one with the Client and one with the Server.
Apologies - but still a bit confused by this. I can only see both client and server if I do the following:
Double click Jamulus icon launches client
Then launch server from Terminal (I'm on a Mac)
If I lauch the server (window) fisrt, then double clicking the Jamulus icon (Finder or Dock) has no result.
Did you mean by "you can run the client on the same machine by launching Jamulus as you would do normally (ie to connect to a server)" that I could launch the client window with a Terminal command, as that is how I launch the server window?
Right now, the only way you can launch the server on Mac is via the Terminal window. You can launch the client via Terminal too of course (without the -s option, obviously), but you don't have to.
That said, I don't know why double clicking the Jamulus icon has no result in your case. Perhaps if you try launching it via the Terminal and see if there's any error message shown. Also worth looking to see if Console is reporting any errors with it and if you find anything paste it here?
I think I understand Mike Watkinson's problem which I believe is one of the right sequence of how to start client and server:
If I start ( on a 1 year old updated Mac) the server from the terminal app first, the server starts. But if then, in a second step, I try to start the Jamulus app (from dock or from app folder) in client mode by simply double clicking it, the client window/app does not open and the already open server window just highlights. So it seems my Mac thinks I want to open the already running server.
So I wrote me a little cue card with the right sequence, which always works for me:
Now, I can connect to any server or my own server. Sometimes I can find my server in the list from the get-go, sometimes my initial connect has to be with 127.0.0.1
Mike, is that what you meant? I hope I could help
Memo: Join my daily Jazz Jam Session on the Ofi Jz Lge 7&9pm cet server - my server welcome message shows the current suggested playlist
Oh OK. That makes sense.
I've clarified that in the install instructions here: https://github.com/corrados/jamulus/wiki/Server---Mac
Last edit: Gilgongo 2020-04-17
FWIW I have had the same problem, with the interesting complication that after thrashing around not understanding which had to open first, client or server, that I managed to have a client process running but no client window. (This prevented me from starting a client after I'd started the server.) Killing all Jamulus processes and starting over in the proper order, of course, fixed everything.
Would it be possible to give the user a head's up, if they try to start a server on a machine where a client is running?
Having to start the Jamulus server on a Mac using the command line is not nice at all. We should find a way to improve that to be more user friendly. Hopefully there is a solution where you have two icons for client and server on a Mac, similar to what we have for Windows.
I have created an issue on Github for this problem: https://github.com/corrados/jamulus/issues/89
Thank you- much appreciated
Fixed in version 3.5.2