NukeServerSocket v1.7


 
This location is for Registered Users Only.
Perhaps you need to login or register.
Contributor: Virgil Sisoe
A Nuke plugin to run code from external applications.
Requirements:
14.0, 13.2, 13.1, 12.2, 11.3 or later
Linux, Mac, Windows
25 Nov 2023
301

NukeServerSocket README

Main BuildLast commitlicense

NukeTools

xx


For the full readme and installation instructions, check the GitHub repository.


Changelog

v0.6.2 2023-11-19

  • Fixed a bug that would cause the extension to not properly use the Script Editor engine.

v0.6.1 2023-10-04

  • Fixed a bug where Nuke's execution button was not found under certain circumstances.

v0.6.0 2023-03-12

  • Fixed Nuke 14 compatibility issues by removing WebSocket connection.
  • Switchable log panels.
  • Under the hood refactoring.

Full changelog


A Nuke plugin to run code from external applications.

Features

  • Receive Python or BlinkScript code from any client in your local network.
  • Connect more than one client to the same Nuke instance.
  • Receive/Send nodes from another Nuke instance in your local network.
  • WebSocket-ready for browser-based text editors.

    Note: WebSocket connection does not work in Nuke 14/15.


Note: Nukepedia versions don't reflect the actual version of the plugin.

MIT License Copyright (c) 2021 Virgil Sisoe Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please login in order to download these files.

Comments   

 
-1 # mani di 2021-08-01 09:45
Amazing stuff! Thank you!

note: you have a misspell a bit github link (colon missing)
 
 
+1 # sankara rao potnuru 2022-01-23 19:51
Very useful, Thank you.
 
 
0 # Johan Alfort 2023-01-10 11:52
Hi, just wondering if this is getting Nuke 14 support as it seems to be broken. loads of errors in the terminal:

Traceback (most recent call last):
File "C:/Users/[Hidd en]/.nuke/menu. py", line 2, in
import NukeServerSocke t
File "C:\Program Files\Nuke14.0v 1\pythonextensi ons\site-packag es\shiboken2\fi les.dir\shiboke nsupport\__feat ure__.py", line 142, in _import
return original_import (name, *args, **kwargs)
File "C:\Users/[Hidden]/.nuke\NukeServerSocke t\__init__.py", line 2, in
from . import src
File "C:\Program Files\Nuke14.0v 1\pythonextensi ons\site-packag es\shiboken2\fi les.dir\shiboke nsupport\__feat ure__.py", line 142, in _import
return original_import (name, *args, **kwargs)
File "C:\Users/[Hidden]/.nuke\NukeServerSocke t\src\__init__.py", line 15, in
from . import main
File "C:\Program Files\Nuke14.0v 1\pythonextensi ons\site-packag es\shiboken2\fi les.dir\shiboke nsupport\__feat ure__.py", line 142, in _import
return original_import (name, *args, **kwargs)
File "C:\Users/[Hidden]/.nuke\NukeServerSocke t\src\main.py", line 16, in
from .connection import QServer, SendTestClient, SendNodesClient
File "C:\Program Files\Nuke14.0v 1\pythonextensi ons\site-packag es\shiboken2\fi les.dir\shiboke nsupport\__feat ure__.py", line 142, in _import
return original_import (name, *args, **kwargs)
File "C:\Users/[Hidden]/.nuke\NukeServerSocke t\src\connection\__init__.py", line 3, in
from .nss_server import QServer
File "C:\Program Files\Nuke14.0v 1\pythonextensi ons\site-packag es\shiboken2\fi les.dir\shiboke nsupport\__feat ure__.py", line 142, in _import
return original_import (name, *args, **kwargs)
File "C:\Users/[Hidden]/.nuke\NukeServerSocke t\src\connection\nss_server.py", line 8, in
from PySide2.QtWebSo ckets import QWebSocketServe r
File "C:\Program Files\Nuke14.0v 1\pythonextensi ons\site-packag es\shiboken2\fi les.dir\shiboke nsupport\__feat ure__.py", line 142, in _import
return original_import (name, *args, **kwargs)
ModuleNotFoundError: No module named 'PySide2.QtWebSo ckets'


Or is there a way to bypass this?
Thanks!
 
 
0 # Michael McReynolds 2023-03-07 20:33
Quoting Johan Alfort:

Or is there a way to bypass this?


It looks like it's trying to load the QtWebSockets module, which for some reason, doesn't exist in Nuke 14's PySide.

If you don't need a websocket, which I am guessing you don't if you aren't interacting through a browser based text editor (you are using either VSCode or Sublime), you can simply turn all those parts off.

It looks like websockets is just used in 3 files : nss_client, nss_server, nss_socket

Just go in there and comment out or delete the import at the top of all three files since QtWebSockets doesn't exist to import.

from PySide2.QtWebSo ckets import QWebSocket

and then you have to make sure to deal with QWebSocket everywhere it's mentioned.

Twice it's returned so just return None instead

return QWebSocket()

and

return QWebSocketServe r('NukeServerSo cket', QWebSocketServer.NonSecureMode)

to

return None

and set the possibility of it trying to use a websocket to False
in nss_socket.py

self.is_websock et = isinstance(self .socket, QWebSocket)

to this

self.is_websock et = False

Save up your files and you should be back in business. That is as long as you aren't using web based editing.
Cheers!
 
 
+1 # Virgil Sisoe 2023-03-13 15:40
Quoting Michael McReynolds:
Quoting Johan Alfort:

Or is there a way to bypass this?


It looks like it's trying to load the QtWebSockets module, which for some reason, doesn't exist in Nuke 14's PySide.

If you don't need a websocket, which I am guessing you don't if you aren't interacting through a browser based text editor (you are using either VSCode or Sublime), you can simply turn all those parts off.

It looks like websockets is just used in 3 files : nss_client, nss_server, nss_socket

Just go in there and comment out or delete the import at the top of all three files since QtWebSockets doesn't exist to import.

from PySide2.QtWebSockets import QWebSocket

and then you have to make sure to deal with QWebSocket everywhere it's mentioned.

Twice it's returned so just return None instead

return QWebSocket()

and

return QWebSocketServer('NukeServerSocket', QWebSocketServer.NonSecureMode)

to

return None

and set the possibility of it trying to use a websocket to False
in nss_socket.py

self.is_websocket = isinstance(self.socket, QWebSocket)

to this

self.is_websocket = False

Save up your files and you should be back in business. That is as long as you aren't using web based editing.
Cheers!


Michael, thanks for taking out the time to help others. You are more than welcome to open a pull request next time you find a solution to a problem.
 
 
0 # Johan Alfort 2024-02-28 10:09
Very sorry for the really late reply, moved away from this tool but will start using it again so many thanks for the guidance!
 
 
0 # Virgil Sisoe 2023-03-13 15:36
Those issues are now gone in the new update. If you have any other problem, please open an issue on the GitHub repository, as Nukepedia does not notify me about those posts.
 
 
+1 # yuri carrara 2023-10-17 09:53
Great tool, I'm trying to understand if it's possible to breakpoint, but at the moment I'm not able to. Is that me or there is no breakpoint support?
 
 
+1 # Virgil Sisoe 2023-10-17 20:33
Hi! Thanks for trying the tool! If by 'breakpoint' you mean debugging breakpoint, no, the application does not support debugging at the moment. I have it in my list of TODOs, an integration with the Visual Studio Code Debugger. However, I also welcome any PR if you have some ideas.
 

You have no rights to post comments

We have 2137 guests and 121 members online