TTY errors that I don't understand (video doesn't play, audio works)

vvvv beta question
1

This is a part of the TTY output. I try to play a video (send a new filename to a filestream node that is conbnected to audioout and videotexture). The audio starts playing, but I don’t see any video…

00:01:52 : Adding node to filtergraph: VideoTexture (EX9.Texture VMR9 YUVMixingMode)
00:01:52 : Connecting from: FileStream (DShow9).Video to: VideoTexture (EX9.Texture VMR9 YUVMixingMode).Video
00:01:52 * : nil pins can not be connected in directshow graph
00:01:52 ERR : The operation cannot be performed because the pins are not connected. [=> LAST LIINE WAS TRANSLATED BY ME, SO I SUPPOSE THIS IS A OS MESSAGE](=> LAST LIINE WAS TRANSLATED BY ME, SO I SUPPOSE THIS IS A OS MESSAGE)

But in a ‘simpler’ patch the module that gets the filenames and plays the video’s does work correctly, and it has worked in this patch sometimes, but most of the time it doesn’t work. I don’t have a clue as to why this problem occurs.

Why would/could the pin be ‘nil’?
Anyone ever seen similar behaviour? Any hints on things I could try to resolve this (permanently if possible). It’s been pestering me for a long time now… and I should get this thing stable asap.

Thanks a lot for any help.

2

A thing I think about now… could the fact that the filename is empty when the patch starts have anything to do with it? Could this cause something to not be connected when starting, and make all of the other things fail?

I tried this in the simpler patch and that doesn’t seem to matter, allthough I get the same error messages, so these are clearly produced by the empty filename, but then why do they also appear in the other patch?

I send relative paths to the filename pin, and it feels to me as if the audio-codec accepts it and the video-codec doesn’t (allthough it does in the simple patch).

3

Some things I learned while trying to resolve this issue…

I had a AsTexture node connected to a renderer, in order to be able to see the output I wanted to send to the 2nd monitor also on the first monitor. Allthough the 2nd (local) renderer was disabled, it seems to have caused a lot of trouble, so I won’t do this anymore (how do other people monitor their fullscreen output locally?).

And be very careful when sending empty strings to the filename pins of either FileStream of FileTexture nodes!