# Waiting for session start

**URL:** <http://forum.playasynth.com/t/waiting-for-session-start/35>\
**Category:** General discussion\
**Created:** [July 20, 2017, 9:20am UTC](http://forum.playasynth.com/t/waiting-for-session-start/35 "2017-07-20T09:20:11Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![dvdlei](http://forum.playasynth.com/letter_avatar_proxy/v4/letter/d/a587f6/32.png) [@dvdlei](http://forum.playasynth.com/u/dvdlei)\
**Post date:** [July 20, 2017, 9:20am UTC](http://forum.playasynth.com/t/waiting-for-session-start/35/1 "2017-07-20T09:20:11Z")

</div>

Hi,

I just connected my Yamaha Montage synth to help you out testing this great new initiative.

I think I followed all steps but am not able to get it working.

1.I installed the host application and assigned the ASIO driver and correct inputs and pressed connect to make the synth available.  
2. On the website I pressed the button to start a session  
3. In my client app I connect to the session and it keeps saying, waiting or session start.

---

<div class="post-metadata">

**Author:** ![Play-a-Synth](http://forum.playasynth.com/letter_avatar_proxy/v4/letter/p/3be4f8/32.png) [@Play-a-Synth](http://forum.playasynth.com/u/Play-a-Synth)\
**Post date:** [July 20, 2017, 1:51pm UTC](http://forum.playasynth.com/t/waiting-for-session-start/35/2 "2017-07-20T13:51:04Z")

</div>

Hi,

it seems that neither of the applications could communicate to the server properly, are you behind  
a firewall or a router which blocks outgoing connections? The applications will only try to connect  
to the other side for 30 seconds and then stop.

Sorry for the delay, I have a full time job doing other things, so I can only answer  
in the afternoon/evening local time + weekends.

---

<div class="post-metadata">

**Author:** ![dvdlei](http://forum.playasynth.com/letter_avatar_proxy/v4/letter/d/a587f6/32.png) [@dvdlei](http://forum.playasynth.com/u/dvdlei)\
**Post date:** [July 20, 2017, 7:37pm UTC](http://forum.playasynth.com/t/waiting-for-session-start/35/3 "2017-07-20T19:37:55Z")

</div>

Hi Zoid,

No problem, thanks for replying to my question. I would think that outgoing connections are all open in my firewall but will retry with the full firewall disabled. Can you share some more details about the exact connections / ports required for both the client and the host to run properly?

---

<div class="post-metadata">

**Author:** ![Play-a-Synth](http://forum.playasynth.com/letter_avatar_proxy/v4/letter/p/3be4f8/32.png) [@Play-a-Synth](http://forum.playasynth.com/u/Play-a-Synth)\
**Post date:** [July 21, 2017, 2:01pm UTC](http://forum.playasynth.com/t/waiting-for-session-start/35/4 "2017-07-21T14:01:42Z")

</div>

There are no specific ports used by the client or the host, I think the range is 49000 - 65535, these are UDP ports. The applications then try to connect to the server at port 45555.

I don’t really know what could prevent the connection, I tested the connection yesterday with someone who is behind a campus hardware firewall and the connection worked ok. I know that if you are behind mobile data or some kind of a business NAT or firewall then the connection won’t work with the current system.

---

<div class="post-metadata">

**Author:** ![Play-a-Synth](http://forum.playasynth.com/letter_avatar_proxy/v4/letter/p/3be4f8/32.png) [@Play-a-Synth](http://forum.playasynth.com/u/Play-a-Synth)\
**Post date:** [July 23, 2017, 9:54am UTC](http://forum.playasynth.com/t/waiting-for-session-start/35/5 "2017-07-23T09:54:39Z")

</div>

I found one possible problem relating to this, the server expects that you connect using IPv4 protocol but the application might find a IPv6 address for the server which means that server won’t accept these connections. I’ll change this behavior for the next version of the applications so that they always use IPv4, at least for now. This change might help also other people who have had a problem connecting to a session.

---

<div class="post-metadata">

**Author:** ![dvdlei](http://forum.playasynth.com/letter_avatar_proxy/v4/letter/d/a587f6/32.png) [@dvdlei](http://forum.playasynth.com/u/dvdlei)\
**Post date:** [July 23, 2017, 12:09pm UTC](http://forum.playasynth.com/t/waiting-for-session-start/35/6 "2017-07-23T12:09:00Z")

</div>

Thanks for your update Zoid. Let me know once a new version of the application is released and I will be more than happy to test again.

---

<div class="post-metadata">

**Author:** ![Play-a-Synth](http://forum.playasynth.com/letter_avatar_proxy/v4/letter/p/3be4f8/32.png) [@Play-a-Synth](http://forum.playasynth.com/u/Play-a-Synth)\
**Post date:** [July 24, 2017, 4:15pm UTC](http://forum.playasynth.com/t/waiting-for-session-start/35/7 "2017-07-24T16:15:34Z")

</div>

I updated both the client and host application with the fix. I hope that this update fixes the problem, but I cannot be certain.

---

<div class="post-metadata">

**Author:** ![dvdlei](http://forum.playasynth.com/letter_avatar_proxy/v4/letter/d/a587f6/32.png) [@dvdlei](http://forum.playasynth.com/u/dvdlei)\
**Post date:** [July 25, 2017, 9:00am UTC](http://forum.playasynth.com/t/waiting-for-session-start/35/8 "2017-07-25T09:00:57Z")

</div>

Thank you zoid, I will try to test this asap and will let you know the outcome.

---

<div class="post-metadata">

**Author:** ![dvdlei](http://forum.playasynth.com/letter_avatar_proxy/v4/letter/d/a587f6/32.png) [@dvdlei](http://forum.playasynth.com/u/dvdlei)\
**Post date:** [July 27, 2017, 8:35am UTC](http://forum.playasynth.com/t/waiting-for-session-start/35/9 "2017-07-27T08:35:30Z")

</div>

I now managed to connect to my own session and play my synth. I will try to make it available during the day for others to test. Another question, for program changes you will need to set MSB 64 LSB 65. However the current controls are not that friendly to directly enter this information, maybe an idea for a future update of the client?

---

<div class="post-metadata">

**Author:** ![dvdlei](http://forum.playasynth.com/letter_avatar_proxy/v4/letter/d/a587f6/32.png) [@dvdlei](http://forum.playasynth.com/u/dvdlei)\
**Post date:** [July 27, 2017, 11:38am UTC](http://forum.playasynth.com/t/waiting-for-session-start/35/10 "2017-07-27T11:38:10Z")

</div>

I’ve now been able to test this with a friend logged in from a different location. It worked really well and the latency was less than expected. Great job. I will keep the Yamaha Montage online for others to play around.

---

<div class="post-metadata">

**Author:** ![Play-a-Synth](http://forum.playasynth.com/letter_avatar_proxy/v4/letter/p/3be4f8/32.png) [@Play-a-Synth](http://forum.playasynth.com/u/Play-a-Synth)\
**Post date:** [July 27, 2017, 12:27pm UTC](http://forum.playasynth.com/t/waiting-for-session-start/35/11 "2017-07-27T12:27:58Z")

</div>

Great to hear.

You are right about changing the presets, I did not consider that some synths might require setting the MSB and LSB to some other value than 0. I will try to update the client during the weekend so that you can directly input the number as well.

---

<div class="post-metadata">

**Author:** ![dvdlei](http://forum.playasynth.com/letter_avatar_proxy/v4/letter/d/a587f6/32.png) [@dvdlei](http://forum.playasynth.com/u/dvdlei)\
**Post date:** [July 27, 2017, 12:39pm UTC](http://forum.playasynth.com/t/waiting-for-session-start/35/12 "2017-07-27T12:39:31Z")

</div>

Ok, for this first time someone unknown is connected to my synth! This feels really strange 🙂 Is there any way to see who is connected and maybe a way of chatting with this person?

---

<div class="post-metadata">

**Author:** ![Play-a-Synth](http://forum.playasynth.com/letter_avatar_proxy/v4/letter/p/3be4f8/32.png) [@Play-a-Synth](http://forum.playasynth.com/u/Play-a-Synth)\
**Post date:** [July 27, 2017, 12:46pm UTC](http://forum.playasynth.com/t/waiting-for-session-start/35/13 "2017-07-27T12:46:33Z")

</div>

I think it was me, just trying out to see what the latency is like 😛

I haven’t really thought about the chatting part but we’ll see in the future if it is something that people would want.
