Output video frame data pixel by pixel
-
The Chop Pixel actor converted it. It accepted the RGB in but output YUV even when set to a size of 1x1.
-
Can't remember if I entered this as a bug?
-
Just confirmed that this is still the case in F33 on windows.
Attached a simple patch that shows a 2x1 coming from a chop pixels when in YUV mode even though set to RGB right before.Will enter bug now.
4ccad4-noisechop.izz -
Dear DusX,
Thanks for the bug report. Will follow up.Best Wishes,Mark -
I recently did this with the Measure Color Actor with it set to 0% size in both directions. I wasn't trying to output each and every pixel though, and since it's position is described by percentages, that might be a problem.
-
What does setting its size to 0% accomplish?
I suppose the other option would to create a custom plugin/
@Mark, if making a actor (with sdk in C++) is there a limit to the number of outputs I would be able to send per frame? (frame rate X cycle rate ?)
Or would outputting another data format be faster.. eg comma delimited list for each row of data?
I don't expect to work with large video files, even 80 x 60 px would be enough. -
0% outputs a single pixel with the Measure Color Actor - I was using a grid of them to pixel map video to a grid of individual RGB LEDs.
-
Looking at the actor, I wonder if the help text for the input fields is correct?
It states that setting the hor and vert locations to 0 causes it to read data for a single pixel.
However this should leave you stick in the top left corner.
Seems that setting the width and height to zero should give the single pixel read, and then you can use the hor and vert positions to move your reader around.
The actors display show ti working this way as well, so it seems the help text must be wrong. -
You're right - I forgot about that. Horiz and Vert are percentage positions starting in the upper-left corner, it's one pixel when width and height are set to 0. You can see in the screen cap that the small feedback window shows one pixel being sampled in different positions, depending on the H and V settings. -Rick
-
Thanks Rick. I was just pointing out the error in the help docs.
I once tried to use this method to read each pixel.. but found the positioning rather difficult.
I have been (like you I guess) using it to read a matrix of values from video and map to DMX.. works well.
Just haven't got it down to scanning ever pixel, I'm defining tiled regions.
