I have a question regarding some Blender compositor functionality and the way Blender handles textures.
I was wondering would it be possible to use compositor output directly as a material texture input. So to say having a node that streams constantly output and bring it into shader editor through let’s say image texture node. That would give all the tools of compositor and let it use as independet texture editor for different render engines.
This brings me to my second question. When modifing textures, we can use viewer node to see output update in uv/image editor. So should we first save out the modified image or could we just read it from memory, as it should be already there. My logic says, that if modified texture would be saved onto disk, we would have to import it again and therefore lose more memory if instead we could access it directly inside Blender without the need to save it out and import again.
Does this sound realistic in any way?