Since new Version 1.83 no connection

Community
1

I have since the new version some big problem.
Please can some one help me.

This is the report

(ERROR) A JavaScript error occurred in the main process:
Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
at doWrite (_stream_writable.js:414:19)
at writeOrBuffer (_stream_writable.js:402:5)
at Socket.Writable.write (_stream_writable.js:302:11)
at PythonShell.send (C:\Users\Stephan Schelens\Desktop\OSC INTERFACE\open-stage-control-1.8.3-win32-x64\resources\app\server\node_modules\python-shell\index.js:285:1)
at MidiConverter.send (C:\Users\Stephan Schelens\Desktop\OSC INTERFACE\open-stage-control-1.8.3-win32-x64\resources\app\server\src\server\midi.js:55:1)
at OscServer.sendOsc (C:\Users\Stephan Schelens\Desktop\OSC INTERFACE\open-stage-control-1.8.3-win32-x64\resources\app\server\src\server\osc\index.js:91:1)
at Object.send (C:\Users\Stephan Schelens\Desktop\OSC INTERFACE\open-stage-control-1.8.3-win32-x64\resources\app\server\src\server\osc\index.js:237:1)
at Object.sendOsc (C:\Users\Stephan Schelens\Desktop\OSC INTERFACE\open-stage-control-1.8.3-win32-x64\resources\app\server\src\server\callbacks.js:357:1)
at Socket. (C:\Users\Stephan Schelens\Desktop\OSC INTERFACE\open-stage-control-1.8.3-win32-x64\resources\app\server\src\server\server.js:179:1)
at Socket.emit (events.js:203:13)

Thx for any help
Cheers

2

I’ll need some context please: when does it occur exactly and what’s the server config (screenshot or better config export from the launcher) ?

3

Hi Jean,

her is the config. file and a picture from the launcher:

Open_Stage_Launcher_Pic
Open_Stage_Launcher_Pic1980Ă—1080 95 KB
Open_Stage_Setup.config (103 Bytes)

4

I opened up the launcher today and start the server. It shortly connects but when i push a button it disconnects and the error message apears.

5

Could you copy the entire log from the console here and not just the last error ?

6

Yes sure

Open_Stage_Launcher_Pic2
Open_Stage_Launcher_Pic21980Ă—1080 214 KB

7

I think there are other messages I can’t see, given the scrollbar on the right, you can select the whole text with ctrl + a, copy it with ctrl + c and paste it here.

8

Allright:

(INFO) Server started, app available at
http://192.168.178.41:8000
http://127.0.0.1:8000
(DEBUG, MIDI) device “C” created
(DEBUG, MIDI) device “C” created
(DEBUG, MIDI) device “Art” created
(DEBUG, MIDI) device “Art” connected to input port 9 (Shortcuts 9)
(DEBUG, MIDI) device “Art” connected to output port 7 (Articulation 7)
(DEBUG, MIDI) device “Shortcut” created
(DEBUG, MIDI) device “Shortcut” connected to input port 10 (Dorico 10)
(DEBUG, MIDI) device “Shortcut” connected to output port 8 (Shortcuts 8)
(DEBUG, MIDI) device “Dorico” created
(ERROR, MIDI) can’t connect input to port 11: UC-33 USB MIDI Controller 11
(DEBUG, MIDI) device “Dorico” connected to output port 9 (Dorico 9)
(ERROR, CLIENT) Uncaught Error: unknown hex color: false
at r (http://192.168.178.41:8000/client/open-stage-control-client.js?version=1.8.3:1102:8543)
at r (http://192.168.178.41:8000/client/open-stage-control-client.js?version=1.8.3:1102:1560)
at r (http://192.168.178.41:8000/client/open-stage-control-client.js?version=1.8.3:1102:1831)
at exports (http://192.168.178.41:8000/client/open-stage-control-client.js?version=1.8.3:2623:402)
(ERROR) A JavaScript error occurred in the main process:
Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
at doWrite (_stream_writable.js:414:19)
at writeOrBuffer (_stream_writable.js:402:5)
at Socket.Writable.write (_stream_writable.js:302:11)
at PythonShell.send (C:\Users\Stephan Schelens\Desktop\OSC INTERFACE\open-stage-control-1.8.3-win32-x64\resources\app\server\node_modules\python-shell\index.js:285:1)
at MidiConverter.send (C:\Users\Stephan Schelens\Desktop\OSC INTERFACE\open-stage-control-1.8.3-win32-x64\resources\app\server\src\server\midi.js:55:1)
at OscServer.sendOsc (C:\Users\Stephan Schelens\Desktop\OSC INTERFACE\open-stage-control-1.8.3-win32-x64\resources\app\server\src\server\osc\index.js:91:1)
at Object.send (C:\Users\Stephan Schelens\Desktop\OSC INTERFACE\open-stage-control-1.8.3-win32-x64\resources\app\server\src\server\osc\index.js:237:1)
at Object.sendOsc (C:\Users\Stephan Schelens\Desktop\OSC INTERFACE\open-stage-control-1.8.3-win32-x64\resources\app\server\src\server\callbacks.js:357:1)
at Socket. (C:\Users\Stephan Schelens\Desktop\OSC INTERFACE\open-stage-control-1.8.3-win32-x64\resources\app\server\src\server\server.js:179:1)
at Socket.emit (events.js:203:13)

9

The MIDI process crashes because of

(ERROR, MIDI) can’t connect input to port 11: UC-33 USB MIDI Controller 11

I'll try to make it more robust to this kind of error (and provide more a readable error), meanwhile you should be able to fix it by using port numbers that exist.

10

It works :wink: Crazy that some little mistake has such a big issue

Thank you so much

11

I’m currently having the same issue with a friend on windows

12

Console log :

(INFO, MIDI) Inputs
-1: Void (bypass)
0: TouchOSC Bridge 0
1: Profire 2626 MIDI 1
(INFO, MIDI) Outputs
-1: Void (bypass)
0: Microsoft GS Wavetable Synth 0
1: TouchOSC Bridge 1
2: Profire 2626 MIDI 2
(INFO) Server stopped
(INFO) Server started, app available at

(ERROR, MIDI) can’t connect input to port 0: TouchOSC Bridge 0 (ERROR) A JavaScript error occurred in the main process: Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed at doWrite (_stream_writable.js:414:19) at writeOrBuffer (_stream_writable.js:402:5) at Socket.Writable.write (_stream_writable.js:302:11) at PythonShell.send (C:\Program Files\open-stage-control-1.8.2-win32-x64\open-stage-control-1.8.2-win32-x64\resources\app\server\node_modules\python-shell\index.js:285:1) at MidiConverter.send (C:\Program Files\open-stage-control-1.8.2-win32-x64\open-stage-control-1.8.2-win32-x64\resources\app\server\src\server\midi.js:55:1) at OscServer.sendOsc (C:\Program Files\open-stage-control-1.8.2-win32-x64\open-stage-control-1.8.2-win32-x64\resources\app\server\src\server\osc\index.js:91:1) at Object.send (C:\Program Files\open-stage-control-1.8.2-win32-x64\open-stage-control-1.8.2-win32-x64\resources\app\server\src\server\osc\index.js:237:1) at Object.sendOsc (C:\Program Files\open-stage-control-1.8.2-win32-x64\open-stage-control-1.8.2-win32-x64\resources\app\server\src\server\callbacks.js:357:1) at Socket. (C:\Program Files\open-stage-control-1.8.2-win32-x64\open-stage-control-1.8.2-win32-x64\resources\app\server\src\server\server.js:177:1) at Socket.emit (events.js:203:13) (INFO) Server stopped (INFO) Server started, app available at http://192.168.43.75:8000 http://127.0.0.1:8000 (ERROR, MIDI) can’t connect input to port 0: TouchOSC Bridge 0 (INFO) Server stopped (INFO) Server started, app available at …

we tried different midi connection but nothing worked

14

@StephanS what did fix it for you ? I realized the error I quoted actually shows the port does exist

15

Hi Jean,

I listed my midi devices in the launcher and i noticed that the list jumbled. I put the right ports in the launcher and the error is gone.

16

@zoltan out of curiosity, what’s the point in using touchosc bridge since O-S-C can send osc & midi directly ?

17

It was just a test, we tried any port in the list.
As in windows version is not able to use “virtual_midi:virtual” we were testing all combinations “mididevice:input, output”

18

Did all combinations failed or just this one ?

19

all :confused:
We were unable to make it worked

20

Next release will bring more meaningful error messages, hopefully we’ll be able to understand what’s going on here.

1 Like
21

Turns out there's a limitation on windows that prevents connecting more than one client to a MIDI port. The workaround is to use virtual ports. Until a free & open source solution comes up I wont be able to fix it in O-S-C.

1 Like