search

jean-emmanuel / open-stage-control

Libre and modular OSC / MIDI controller
https://openstagecontrol.ammd.net
GNU General Public License v3.0
702 stars 88 forks source link

Blank window on MacOS #570

Closed btownshend closed 4 years ago

btownshend commented 4 years ago

Open Stage Control was previously working on my computer, but now the main screen is always b blank. I launch from the app (0.48.0) and the control panels opens correctly, but after I click start (and after "Allow" for the accepting network connections) the new window is completely black. This is true with all the settings at default or when pointing to my previously working .json file.

MacOS 10.14.6

image
jean-emmanuel commented 4 years ago

Hi, can you hit F12 in the blank window and check for error messages in the console that should appear ?

btownshend commented 4 years ago

That seems to drop into the Chrome debugger, but no error messages visible or on console:

On Oct 22, 2019, at 4:59 PM, jean-emmanuel notifications@github.com wrote:

Hi, can you hit F12 in the blank window and check for error messages in the console that should appear ?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jean-emmanuel/open-stage-control/issues/570?email_source=notifications&email_token=AAULBJ3B3SRNOP3UUFKRYR3QP6HX5A5CNFSM4JDZ5BXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB7SXIQ#issuecomment-545205154, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAULBJ6H6TSUR5ZA6EAJZTLQP6HX5ANCNFSM4JDZ5BXA.

jean-emmanuel commented 4 years ago

Once in the debuger, can you hit ctrl+r (or cmd+r, I'm not sure) to refresh the connection and see if anything prints ? Have you tried accessing the app with an external chrome instance ?

Was it previously working on the same version ? Did you update your system somehow ?

btownshend commented 4 years ago

It looks like the content of the page is just “SUCCESS”, no errors.

Connecting from the Chrome Browser just shows a window with the word “SUCCESS”.

This was all working on this computer a few months ago, but since then there may have been some minor upgrades of MacOS. When it stopped working I was running OSC 0.46, but upgraded to 0.48 to see if that helped (which it didn’t).

Brent

On Oct 23, 2019, at 3:02 AM, jean-emmanuel notifications@github.com wrote:

Once in the debuger, can you hit ctrl+r (or cmd+r, I'm not sure) to refresh the connection and see if anything prints ? Have you tried accessing the app with an external chrome instance ?

Was it previously working on the same version ? Did you update your system somehow ?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jean-emmanuel/open-stage-control/issues/570?email_source=notifications&email_token=AAULBJ5NX6MFVTKZOIIZAHDQQAOJRA5CNFSM4JDZ5BXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECA2SVA#issuecomment-545368404, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAULBJ6KCT7IJNBGCPTCKZTQQAOJRANCNFSM4JDZ5BXA.

jean-emmanuel commented 4 years ago

Could you try changing the port option ? It may be that the default port (8080) is already used by another application thus preventing o-s-c from serving the files properly .

btownshend commented 4 years ago

That was it! Not sure what was using 8080, but I’ll find out. Odd though that OSC doesn’t give an error when it tries to serve on 8080 if another process is listening on that port.

Brent

On Oct 23, 2019, at 9:07 AM, jean-emmanuel notifications@github.com wrote:

Could you try changing the port option ? It may be that the default port (8080) is already used by another application thus preventing o-s-c from serving the files properly .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jean-emmanuel/open-stage-control/issues/570?email_source=notifications&email_token=AAULBJZJRN6ZJMVHSRUQZITQQBZEZA5CNFSM4JDZ5BXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECB7G2A#issuecomment-545518440, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAULBJ3HUSNYPUOIZF7MSMTQQBZEZANCNFSM4JDZ5BXA.

btownshend commented 4 years ago

Was a lightroom plugin, photosmith, that runs a server (psahttp) on port 8080.

Brent

On Oct 23, 2019, at 9:13 AM, bst@tc.com wrote:

That was it! Not sure what was using 8080, but I’ll find out. Odd though that OSC doesn’t give an error when it tries to serve on 8080 if another process is listening on that port.

Brent

On Oct 23, 2019, at 9:07 AM, jean-emmanuel <notifications@github.com mailto:notifications@github.com> wrote:

Could you try changing the port option ? It may be that the default port (8080) is already used by another application thus preventing o-s-c from serving the files properly .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jean-emmanuel/open-stage-control/issues/570?email_source=notifications&email_token=AAULBJZJRN6ZJMVHSRUQZITQQBZEZA5CNFSM4JDZ5BXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECB7G2A#issuecomment-545518440, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAULBJ3HUSNYPUOIZF7MSMTQQBZEZANCNFSM4JDZ5BXA.

jean-emmanuel commented 4 years ago

Great ! Yes, that's odd, an error should have been raised, it does when I attempt to launch two instances of o-s-c on the same http port (with different osc ports, because this would also raise an error).

btownshend commented 4 years ago

It looks like o-s-c opens both a UDP and TCP port on 8080, whereas psahttp opens only a TCP port —just a thought, maybe your code is picking up a conflict on the UDP open (which is why it flags an error if two instances are started), but not during the TCP open?

Brent

On Oct 23, 2019, at 9:20 AM, jean-emmanuel notifications@github.com wrote:

Great ! Yes, that's odd, an error should have been raised, it does when I attempt to launch two instances of o-s-c on the same http port (with different osc ports, because this would also raise an error).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jean-emmanuel/open-stage-control/issues/570?email_source=notifications&email_token=AAULBJYBW7JSKP352S6U3LDQQB2TPA5CNFSM4JDZ5BXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECCAPGI#issuecomment-545523609, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAULBJ4XC6KPSVK4DTOFDODQQB2TPANCNFSM4JDZ5BXA.

jean-emmanuel commented 4 years ago

I started both applications with the same TCP port (port option, used of http) but with different UDP ports (osc-port option, used for osc messages) to make sure it wasn't the case :).

jean-emmanuel commented 4 years ago

Listening on the same port using different protocols (udp / tcp) works fine, otherwise the app would not have worked in the first place.

btownshend commented 4 years ago

I’m fine now, and we can close this issue, but if you’d like to debug the missing error message, I can send you the (MacOS) binary for psahttp if it would help to replicate the situation.

Brent

On Oct 23, 2019, at 9:35 AM, jean-emmanuel notifications@github.com wrote:

I started both applications with the same TCP port (port option, used of http) but with different UDP ports (osc-port option, used for osc messages) to make sure it wasn't the case :).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jean-emmanuel/open-stage-control/issues/570?email_source=notifications&email_token=AAULBJ3QR62PTBJRN6AHNBDQQB4NVA5CNFSM4JDZ5BXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECCCBSA#issuecomment-545530056, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAULBJ25IKIOWUZUTKCTCSDQQB4NVANCNFSM4JDZ5BXA.

jean-emmanuel commented 4 years ago

Thanks but I don't have any MacOs system so I guess this will have to wait until I get my hands on one ;)

btownshend commented 4 years ago

And it looks like psahttp uses the mongoose embedded web server (https://github.com/cesanta/mongoose https://github.com/cesanta/mongoose). Not sure if there is anything special about how it opens 8080 that results in different symptoms compared to multiple copies of o-s-c, though I can’t imagine what that would be...

Brent

On Oct 23, 2019, at 9:44 AM, bst@tc.com wrote:

I’m fine now, and we can close this issue, but if you’d like to debug the missing error message, I can send you the (MacOS) binary for psahttp if it would help to replicate the situation.

Brent

On Oct 23, 2019, at 9:35 AM, jean-emmanuel <notifications@github.com mailto:notifications@github.com> wrote:

I started both applications with the same TCP port (port option, used of http) but with different UDP ports (osc-port option, used for osc messages) to make sure it wasn't the case :).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jean-emmanuel/open-stage-control/issues/570?email_source=notifications&email_token=AAULBJ3QR62PTBJRN6AHNBDQQB4NVA5CNFSM4JDZ5BXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECCCBSA#issuecomment-545530056, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAULBJ25IKIOWUZUTKCTCSDQQB4NVANCNFSM4JDZ5BXA.

btownshend commented 4 years ago

No problem. FYI, I just tried running two copies of o-s-c with different OSC ports and I do indeed see the EADDRINUSE error for the 8080 listen, but don’t see any error when starting o-s-c while psahttp is running.

Brent

On Oct 23, 2019, at 9:47 AM, jean-emmanuel notifications@github.com wrote:

Thanks but I don't have any MacOs system so I guess this will have to wait until I get my hands on one ;)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jean-emmanuel/open-stage-control/issues/570?email_source=notifications&email_token=AAULBJ7TG6ZMHMZ5DK4KXODQQB5Z7A5CNFSM4JDZ5BXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECCDHOA#issuecomment-545534904, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAULBJ24OAWU7I5WOTGEJW3QQB5Z7ANCNFSM4JDZ5BXA.

jean-emmanuel commented 4 years ago

Starting with next release, this error will no longer be hidden.