-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple instances of the CasparCG object seems to collide. #15
Comments
Looks like the |
Ah! I am trying to find the bug right now in the code. |
I wrote a fix but haven't had a chance to test it. The problem is that the |
I can test the fix tomorrow for you! |
I am getting the following after a while: /var/www/node/node_modules/caspar-cg/lib/connection.js:151 |
I looked over the code and found a couple of places that were using If you turn on the debug option it will log most everything that happens. Can you post what is logged when this happens? |
Seems to work with the new commit by some reason??? |
Did this simple test and doesn't seem to work :( var CasparCG = require("caspar-cg"); ccg = new CasparCG({ ccg_asd = new CasparCG({ io.sockets.on('connection', function (socket) {
}); Both connect to 181. |
Recently did a project where I had to use multiple servers. The node library seems to collide when setting up multiple objects with different configs. It only uses the last set object and writes everything to that.
Will post code later today.
The text was updated successfully, but these errors were encountered: