Forum

AsString & SharedMemory (Windows)

#1

Hello, i gave it a try to send a texture over sharedmemory,so FileTexture -> AsString(Texture) -> SharedMemory(Windows), look like the output of sharedmemory is truncated after third carachater, is that related to sharedmemory format or what ?

dank je wel :D

#2

setting
*File Format on AsString (EX9.Texture)
*Size in Bytes on SharedMemory (Windows)
**Format
**Width
**Height
**Bytes per Pixel on SharedMemory (EX9.Texture)

to the correct settings seems to be a pain in the a…

using an IOBox (Enumeration) on Format of SharedMemory (EX9.Texture) seems not to work .
results are different from just using the pin.

anyway, be prepared for crashes.
i had some while making this little patch.

SharedTextures.v4p (10.7 kB)

#3

hi kalle :) tryed ur patch , some times (seems casually), i can see a grey stripe in the render, no crash, no texture :) strange pain in the a…

#4

mkay, 2 things here:

  • the SharedMemory (EX9.Texture) is not supposed to be able to read a string written to sharedmemory by AsString (EX9.Texture) as kalles patch suggests. while the asstring node returns the complete string representation of a file in a specific format (including header, pallette…) SharedMemory (EX9.Texture) only expects plain pixelbyte arrays in a layout like ARGB per pixel. so if in your application you can provide such a memorylayout SharedMemory (EX9.Texture) will be able to interpret it correctly. i’ve improved the according helppatches…
  • as hierro points out SharedMemory (Windows) Output is indeed buggy. fixed that for beta>25. then it will be possible to have a setup like: AsString -> SharedMemory…SharedMemory -> DynamicTexture (String)
#5

so waiting for next release :D thank u for feedback

#6

ah ok.
i always liked misusing nodes…

© vvvv group