(Ie tested my Oak4D 9 (RVC4) PoE through the Oak viewer and camera seems fine i can see the depth and image feeds outside of touchdesigner, then I got mostly through the github setup with TD build 2025.33070 , but having trouble. the first step to install from python seemed to go ok. seems like I have the depthai 3.8.0…then I couldn’t really load the TDOAK tox just by itself, but I could launch the TDOAK.toe file. on the TDOAK tox it lists my device IP I can connect it, it says connected and rgb stream is created, but FPS is 0 and on the scriptTOPs the image is blank not receiving anything. probalby missing some steps but I figured those few things would have created the basic rgb stream. what did I miss?
After some digging with Claude, I was able to get a functioning stream for rgb and subsequently depth stream with a custom pipeline DAT.
This one did not work, due to the explicit BGR888p
import depthai as dai
def build(pipeline):
cam = pipeline.create(dai.node.Camera).build()
out = cam.requestOutput((1280, 720), type=dai.ImgFrame.Type.BGR888p)
queues = {'rgb': out.createOutputQueue()}
return queues, ['rgb']
but this one did:
import depthai as dai
def build(pipeline):
cam = pipeline.create(dai.node.Camera).build()
out = cam.requestOutput((1280, 720)) # no explicit type
queues = {'rgb': out.createOutputQueue()}
return queues, ['rgb']
Hi,
Some of the cameras do not support certain ImgFrame types, so you will need to change them or remove the explicit type like you did. If you set TOUCH_TEXT_CONSOLE to 1 in your environment settings you should be able to see an error message from the DepthAI python library that lists the supported types for the selected camera
Huck
Hi @bradonwebb
thanks for testing this a bit.
I removed the frame type from the .requestOutput() functions of the camera, they will now all be defaulting to the camera’s default (usually NV12 from what I read)
The change is pushed and you should be able to just update the package.
Can I ask what issues you had when trying to use the tox file by itself?
cheers
Markus
If I just drag the TDOAK.tox into a blank project, the issue is that it cannot find the device from the device menu flydown its just an empty menu. I click the refresh button (which works in the toe file); it finds the Oak IP device just fine in that context. I’m guessing maybe there is a script in the toe file that does some wiz bang init stuff to make the device discoverable?
I don’t have much more info than that, I can try to debug it more until I get an error message of some kind. it just worked in the Toe but not the tox. I didn’t exactly follow step 2 on the github casue I didn’t know how this worked. mod.TDOAK.toxPath('TDOAK')
so I just dragged the tox in but could be that it doesn’t init that way.
UPDATE: I was able to get the tox working, it could be that the tox requires dependent files in the src folder, if I drag the tox into a new project, and then save my own toe file, close it, and then re-open it initializes properly… could be the relative paths for scripts or something didn’t init unless you save the toe file which sets all the correct pathing to the relative repo files.