[BUG]: VideoReceiveSample received texture not updating

[Julius-Caesar6]

[BUG]: VideoReceiveSample received texture not updating

[karasusan]

@Julius-Caesar6
Can you give me a code snippet to replicate your issue?

[Julius-Caesar6]

Of course. In the VideoReceive sample in VideoReceiveSample.cs from line 81 ("video.OnVideoReceived += tex =>") instead of line 83: "receiveImage.texture =tex;", paste this code:
` // Original line where rawImage texture is set to tex.
// receiveImage.texture = tex;
Texture2D originalReceivedTexture = tex as Texture2D;

                    // Setting rawImage texture to the Texture2D also works and gives the correct live view.
                    // receiveImage.texture = originalReceivedTexture; 

                    // Get pixels of texture into array of Colors.
                    Color[] texturePixels = originalReceivedTexture.GetPixels();

                    // Pixel manipulation ... (for example grayscaling)

                    // Apply pixels back to new texture
                    Texture2D processedTexture = new Texture2D(tex.width, tex.height);
                    processedTexture.SetPixels(texturePixels);
                    processedTexture.Apply();
                    
                    // In this instance in play mode the rawImage only shows a gray image. 
                    receiveImage.texture = processedTexture;`

So what happens is that by doing nothing to the pixels yet and just getting them from one texture and setting them to another, the live aspect is somehow lost. I don't necessarily need to set the pixels to a new texture (in this snippet it is just to illustrate), but need the live pixel values of "tex".

Thank you for your time and help!

[karasusan]

@Julius-Caesar6
Hi, thanks for the detail, I replicated your issue.
originalReceivedTexture is updated asynchronously on GPU. CPU memory in texture is not updated, therefore GetPixels returns gray color buffer.

Can you try ReadPixels instead of GetPixels? ReadPixels can read CPU memory from rendertarget.
In addition, reading CPU memory is high cost generally, please check the performance.  

[Julius-Caesar6]

@karasusan
Thank you for you reply!
I will try your recommendations and see if I can get it working.