The VideoLAN Forums

I am getting errors using dshow to stream webcam video to http - it does work, but each time I start streaming I get the following errors:

File reading failed:
VLC could not open the file "C:\Program Files\VideoLAN\VLC\contrast=1". (Bad file descriptor)
Your input can't be opened:
VLC is unable to open the MRL 'file:///C:/Program%20Files/VideoLAN/VLC/contrast%3D1'. Check the log for details.
File reading failed:
VLC could not open the file "C:\Program Files\VideoLAN\VLC\saturation=1.3". (Bad file descriptor)
Your input can't be opened:
VLC is unable to open the MRL 'file:///C:/Program%20Files/VideoLAN/VLC/saturation%3D1.3'. Check the log for details.

Once I dismiss the errors the stream starts and seems to run without problems. The command line I am using is as follows (but obviously with a 'real' IP in place of [IP_GOES_HERE]):

vlc dshow:// vdev="USB Video Device" adev="None" --sout-transcode-vfilter adjust --brightness=1 contrast=1 saturation=1.3 --sout=#transcode{vcodec=WMV2,vb=800,width=320,height=240,acodec=wma2,ab=128,channels=2,samplerate=44100}:duplicate{dst=http{dst=[IP_GOES_HERE]:8080/yppscounter.wmv},dst=display}

Okay, I spoke too soon. Now VLC crashes intermittently on startup - while streaming I get constant errors like the following:

main error: ES_OUT_RESET_PCR called
main error: ES_OUT_SET_(GROUP_)PCR is called too late (pts_delay increased to 5150 ms)
main error: ES_OUT_RESET_PCR called
main error: ES_OUT_SET_(GROUP_)PCR is called too late (jitter of 5685 ms ignored)

I found that setting up the stream manually through VLC worked fine - I was only having problems when starting the stream from the command line. After spending the morning trying various options, I finally found that the following command line works:

vlc dshow:// --dshow-vdev="USB Video Device" --dshow-adev="None" --dshow-size="320x240" --sout=#transcode{vcodec=WMV2,vb=800,width=320,height=240,acodec=none}:duplicate{dst=http{dst=[IP_GOES_HERE}/yppscounter.wmv},dst=display}

The key appears to be using "--dshow-vdev" etc. instead of just "vdev". No errors now, everything seems to be running smoothly. I'm still stumped as to why it was running fine for months with the old command line, and suddenly started having all these issues - but at least it's working now (touch wood).