Weird dependencies behavior / Version questionning

[DrumSlayers]

Hello,

I'm trying to install (and run) asls-server, using npm to install them.
I tried node 18, node 22, linux and windows, and i'm facing the following each time :

PS C:\Users\xxxxx\Documents\GIT\asls-server> node .\DMXWebRTC.js
C:\Users\xxxxx\Documents\GIT\asls-server\node_modules\bindings\bindings.js:135
  throw err;
  ^

Error: Could not locate the bindings file. Tried:
 → C:\Users\xxxxx\Documents\GIT\asls-server\node_modules\@cubicleai\wrtc\build\wrtc.node
 → C:\Users\xxxxx\Documents\GIT\asls-server\node_modules\@cubicleai\wrtc\build\Debug\wrtc.node
 → C:\Users\xxxxx\Documents\GIT\asls-server\node_modules\@cubicleai\wrtc\build\Release\wrtc.node
 → C:\Users\xxxxx\Documents\GIT\asls-server\node_modules\@cubicleai\wrtc\out\Debug\wrtc.node
 → C:\Users\xxxxx\Documents\GIT\asls-server\node_modules\@cubicleai\wrtc\Debug\wrtc.node
 → C:\Users\xxxxx\Documents\GIT\asls-server\node_modules\@cubicleai\wrtc\out\Release\wrtc.node
 → C:\Users\xxxxx\Documents\GIT\asls-server\node_modules\@cubicleai\wrtc\Release\wrtc.node
 → C:\Users\xxxxx\Documents\GIT\asls-server\node_modules\@cubicleai\wrtc\build\default\wrtc.node
 → C:\Users\xxxxx\Documents\GIT\asls-server\node_modules\@cubicleai\wrtc\compiled\22.15.0\win32\x64\wrtc.node
 → C:\Users\xxxxx\Documents\GIT\asls-server\node_modules\@cubicleai\wrtc\addon-build\release\install-root\wrtc.node
 → C:\Users\xxxxx\Documents\GIT\asls-server\node_modules\@cubicleai\wrtc\addon-build\debug\install-root\wrtc.node
 → C:\Users\xxxxx\Documents\GIT\asls-server\node_modules\@cubicleai\wrtc\addon-build\default\install-root\wrtc.node
 → C:\Users\xxxxx\Documents\GIT\asls-server\node_modules\@cubicleai\wrtc\lib\binding\node-v127-win32-x64\wrtc.node
    at bindings (C:\Users\xxxxx\Documents\GIT\asls-server\node_modules\bindings\bindings.js:126:9)
    at Object.<anonymous> (C:\Users\xxxxx\Documents\GIT\asls-server\node_modules\@cubicleai\wrtc\binding.js:1:37)
    at Module._compile (node:internal/modules/cjs/loader:1730:14)
    at Object..js (node:internal/modules/cjs/loader:1895:10)
    at Module.load (node:internal/modules/cjs/loader:1465:32)
    at Function._load (node:internal/modules/cjs/loader:1282:12)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:235:24)
    at Module.require (node:internal/modules/cjs/loader:1487:12)
    at require (node:internal/modules/helpers:135:16) {
  tries: [
    'C:\\Users\\xxxxx\\Documents\\GIT\\asls-server\\node_modules\\@cubicleai\\wrtc\\build\\wrtc.node',
    'C:\\Users\\xxxxx\\Documents\\GIT\\asls-server\\node_modules\\@cubicleai\\wrtc\\build\\Debug\\wrtc.node',
    'C:\\Users\\xxxxx\\Documents\\GIT\\asls-server\\node_modules\\@cubicleai\\wrtc\\build\\Release\\wrtc.node',
    'C:\\Users\\xxxxx\\Documents\\GIT\\asls-server\\node_modules\\@cubicleai\\wrtc\\out\\Debug\\wrtc.node',
    'C:\\Users\\xxxxx\\Documents\\GIT\\asls-server\\node_modules\\@cubicleai\\wrtc\\Debug\\wrtc.node',
    'C:\\Users\\xxxxx\\Documents\\GIT\\asls-server\\node_modules\\@cubicleai\\wrtc\\out\\Release\\wrtc.node',
    'C:\\Users\\xxxxx\\Documents\\GIT\\asls-server\\node_modules\\@cubicleai\\wrtc\\Release\\wrtc.node',
    'C:\\Users\\xxxxx\\Documents\\GIT\\asls-server\\node_modules\\@cubicleai\\wrtc\\build\\default\\wrtc.node',
    'C:\\Users\\xxxxx\\Documents\\GIT\\asls-server\\node_modules\\@cubicleai\\wrtc\\compiled\\22.15.0\\win32\\x64\\wrtc.node',
    'C:\\Users\\xxxxx\\Documents\\GIT\\asls-server\\node_modules\\@cubicleai\\wrtc\\addon-build\\release\\install-root\\wrtc.node',
    'C:\\Users\\xxxxx\\Documents\\GIT\\asls-server\\node_modules\\@cubicleai\\wrtc\\addon-build\\debug\\install-root\\wrtc.node',
    'C:\\Users\\xxxxx\\Documents\\GIT\\asls-server\\node_modules\\@cubicleai\\wrtc\\addon-build\\default\\install-root\\wrtc.node',
    'C:\\Users\\xxxxx\\Documents\\GIT\\asls-server\\node_modules\\@cubicleai\\wrtc\\lib\\binding\\node-v127-win32-x64\\wrtc.node'
  ]
}

Node.js v22.15.0

On linux, cubicleai/wrtc installation triggers webrtc lib build, which imply chromium building and 32G of ram seem to be not sufficient for this 😅 (Failling with OOM)

Have you any clues about tools / versions to use ?

Thanks !

[DrumSlayers]

After some tries, i found something even weirder :

Package.json ask for

• @cubicleai/wrtc": "^0.7.0" , but 0.7.0 is compatible with nothing newer than node 18
• @semantic-release/npm": "^12.0.1", but 12.0.1 ask for node ">=20.8.1", not earlier.

What is the magic? 😅 will appreciate any answer !

[DrumSlayers]

So, digged further, I found that @cubicleai/wrtc binaries are served from an AWS S3 bucket that does not exist anymore.

Changed the lib in the code to "@roamhq/wrtc": "^0.8.0", since it seems to be based on same wrtc functions.

However, between asls studio and asls server, I get stuck in "Sending SDP offer"
ASLS Server side : Websocket offer from: ::ffff:172.27.128.1
ASLS Studio side : Sending SDP offer

I can retry in a loop, it does not go any further.

With some debug output, i see a WebRTC offer " {"type":"__WRTC_OFR"} " in websocket, but that contain no any information (21 bytes only).
It obviously misses the SDP offer 😅

Is it normal behavior ? What is going wrong ?

EDIT : A quick look into ASLS Studio code : I get the following response , sent by this line
https://github.com/ASLS-org/studio/blob/94896117968776897985ed7dc951882de216aeaa/src/plugins/webshow.js#L126C1-L127C1

[timekadel]

Hi @DrumSlayers,

You're absolutely right, there's indeed a bunch of dependency quircks in this repository, particularly with the modules responsible for the WebRTC communication. I'm currently working on a web protocol proposal called WSC (Web Show Control), and I’ve already patched most of those issues locally. I just haven’t had a chance to document and push the changes yet.

I’ve got some free time this week, which should be perfect for cleaning things up and getting the repo back in shape, I’ll keep you posted once I’ve pushed the updates!

Really appreciate your interest in ASLS, it’s a huge motivation boost!

[mehdilauters]

Hello, same problem here, we are really interrested in this software as the interface and functionnality looks really good compared to annoying expensive solutions with locked hardware and no browser support.
It should be really interesting to get some clues to fix the problem so we could test it in real setups, and maybe I can create a merge request with a full working docker image and docker-compose setup to make it really easy to test and deploy.

What is the quick fix to start it? (like maybe older versions of server and ui?)

[stereo3d]

Congratulations, for the nice work, is there any update on the dependencies and WSC issue?