I’m trying to support as many concurrent users as possible in a janus-gateway, and am doing some optimizations. One of the things I’m trying to do is to separate the mjr to opus/mp4 conversion process away from the main janus-gateway assuming this would lower the load of the main janus-gateway that’s responsible for relaying and recording streams.
I run a separate server that has the exact same version of the janus-gateway installed, and try to use janus-pp-rec to convert mjr to opus/mp4. I get the following error. The same process with the same mjr files works flawlessly in the main janus-gateway (the original server that generates the mjr).
ubuntu@ip-<>:~/mjr$ /snap/bin/janus-gateway.janus-pp-rec --header bus_audio.mjr -d 7
Janus version: 1102 (1.1.2)
Janus commit: e8d1395d3de9caa5e244605ec1a7281cd7d3ecf1
Compiled on: Thu Jan 19 10:45:44 UTC 2023
Logging level: 7
Source file: bus_audio.mjr
-- Showing header only
[ERR] [postprocessing/janus-pp-rec.c:main:358] Could not open file bus_audio.mjr
So first of all, is this even necessary, i.e. would the janus-pp-rec conversion put a significant load on the server? And if so, am I doing it correctly?
I wasn’t able to get it working after troubleshooting the file and its permissions. For what it’s worth, it actually also doesn’t work in the original janus-gateway if I move the mjr file away from the original recording folder.
I managed to find a solution tho. By installing janus-tools (sudo apt install janus-tools) and using that janus-pp-rec, I was able to convert mjr on a separate machine.
That said, @lorenzo I still would like to ask: Do you recommend this approach? I am not sure if doing the conversion on a different machine is even necessary if the janus-pp-rec conversion is light enough. I’m talking about a janus-gateway with about 800 concurrent users streaming to it, and recording is enabled.