I m on another project, and i m having this warning arriving in TTY when i insert in my project the resample patch attached here, and connect it :
02:11:43 ERR : Error caught in the act: TAddFlow : Access violation at address 0067E253 in module 'vvvv.exe'. Read of address 00000360
0:08:22 * : [validatevalue: error occured in ](validatevalue: error occured in ): Access violation at address 0043B0E6 in module 'vvvv.exe'. Read of address 00000001
This project is very different and in a way far less complicated than last time.
I have ONE Ip camera goig to html renderer, that i m aquiring with VHSCrap to feed the videoin ( ipcamera driver doesnt show up any image when called directly from enum pins).
From this camera i m sending its texture with S(node) and filtering it in differents shaders before mixing those differents filter in Blend’s svvvitcher’s shader.
When i insert and connect in my patch RESAMPLE_BANG.v4p, i began to have troubles in the TTY.
This patch enables me to capture in live what is coming from the camera, and to reinsert it in place of the original signal. a kind of video sampler.
At the beginning i was doing this on frame base methode, taking the mainloop. Here is my post : http://vvvv.org/forum/sampling-video
I was thinking that maybe frame delay was a problem, as I had blank frames on this technique so i changed all the patch and i went on lfo technique, wich doesn t show up troubles of capture, but is now showing this access violation.
I presume there is somewhere a conflict with image queueing ? is there any way to prevent from it ?
I have from 5 to 8 shaders on 16 possible working continuously in direct in 1024x728 with a rendering in 1024x728.
Graphic card is a ATI 5770 with 1Go DDRAM and seems ok.
Gui is very simple and in GDI to let some memory left. Patch is remoted in artnet.
I have some latency with beta 23 when opening subpatches and calling vvvv menu
If i make a test with only the camera and this subpatch, i dont have the access violation.
sampling texture in live (26.1 kB)