Pd (64-bit): Cannot Start Webcam - [pix_video]: no valid video backend found
After installing GEM I've tried to test the Pd program "Movement". Althhough GEM has been installed, I always receive the error message "[pd_video]: no valid video backend found" and the window is blank.
Here's the Pd program:
05c-movement2.pd
I'm using Pd Vanilla 64-bit.
How do I get my webcam running, so I can see it is filming?
Hi @ddw_music,
here are the following information you need to know:
Here is the entire console output, after starting a window:
GEM: Graphics Environment for Multimedia
GEM: ver: 0.94.git v0.94
GEM: compiled on Feb 12 2019
GEM: maintained by IOhannes m zmoelnig
GEM: Authors : Mark Danks (original version)
GEM: Chris Clepper
GEM: Cyrille Henry
GEM: IOhannes m zmoelnig
GEM: with help by Guenter Geiger, Daniel Heckenberg, James Tittle, Hans-Christoph Steiner, et al.
GEM: found a bug? miss a feature? please report it:
GEM: homepage https://gem.iem.at/
GEM: bug-tracker https://bugs.gem.iem.at/
GEM: mailing-list https://lists.puredata.info/listinfo/gem-dev/
GEM: compiled for MMX/SSE2 architecture
GEM: using SSE2 optimization
GEM: detected 8 CPUs
GEM: image loading plugins: magick SGI STB jpeg tiff
GEM: film loading plugins: DirectShow
GEM: image saving plugins: SGI STB jpeg magick tiff
GEM: model loading plugins: ASSIMP3 OBJ
GEM: video capture plugins: VIDS decklink vnc
[pix_video]: backend #0='VIDS' : videoInput
[pix_video]: backend #1='decklink' <--- DISABLED
[pix_video]: backend #1='vnc' : vnc
[pix_video]: no valid video backend found
@RayManiac You could try downloading extendedview....... https://puredata.info/downloads/extended-view-toolkit ......... it is a very useful library anyway.
Then open 03b_ev_example_360_degree_livecam.pd
That is the only patch that will open my webcam in Gem.
If it works then this will work...... I have stripped out the fish-eye lens warp.......03b_ev_example_livecam.pd
@ddw_music Yes, specifically Windows WDM for windows and I am pretty sure gemw32window.dll is required still and should be in the Gem folder.
I wonder though whether 32-bit applications have to be enabled in Widows 10 for that to run.
David.
@whale-av this works! Thank you! But why was the camera from movement example not working?
I also noticed, if I switch the camera device in the 03b_ev_example_360_degree_livecam.pd example I get a white blank screen in the window.
Although this code is working, I get the error message, that the GLSL shader could not be found. Should I download GLSL shader files?
Output:
Kollabs: (c)2012 Marian Weger
Kollabs: version 0.2a under GNU General Public License
GIL: (c)2011 Marian Weger
ev_360: (c)2012 Cyrille Henry / Peter Venus / Marian Weger
ev_360: /part of EXTENDED VIEW toolkit/ gpl v3
[glsl_vertex]: could not find shader-file: 'C:/Users/Username/Desktop/extendedview-extended_view_toolkit-f9e87d6/ev-pano/ev_360.vert'
[glsl_program]: unable to get shaderID for 0.000000...skipping!
[glsl_program]: unable to get shaderID for 0.000000...skipping!
linking: link 0 0
[pix_texture]: using mode 0: TEXTURE_2D
ev_360: (c)2012 Cyrille Henry | Peter Venus | Marian Weger
ev_360: part of EXTENDED VIEW toolkit | gpl v3
Kollabs/DS (0): loaded ../../data/ev_example_360_degree_livecam.txt
Kollabs/DS (0): recalled scene 0.
[glsl_vertex]: could not find shader-file: 'C:/Users/Ramón Wilhelm/Desktop/extendedview-extended_view_toolkit-f9e87d6/ev-pano/ev_360.vert'
[glsl_vertex]: need to load a shader
[glsl_fragment]: need to load a shader
[glsl_program]: can't link zero shaders
@RayManiac I have studied the extendedview patch and never managed to work out exactly why it works where no other patch works.
I think it has to do with the initialization of the parameters for [pix_video] but I didn't get to the bottom of it.
The white screen is I think just a non-existant device. Do you have a second camera?
[glsl_vertex] should be part of Gem.
I cannot see why it cannot find ev_360.vert as it seems to be looking in the correct folder.
Maybe spaces in the path?
I had renamed the extended view toolkit folder to "extview" at some point..... so maybe.
Or it could be path settings in Pd....... but it has searched the correct folder so.......?
I am sure that if you look in the ev-pano folder the file will be there.
Daft question........ you did unzip the download?
It isn't because of paths...... they are all declared in [ev-main/ev_declare] called by [pd init] in every patch.
David.
@whale-av No, I have only one camera device connect to my computer. I unzipped the entire download and opened it with Pd.
I look after spaces in the path. I want to make sure, that everthing is alright. If I got further problems I'll let you know.
Thank you!
Edit: Strange, after I opened the 03b_ev_example_360_degree_livecam.pd and the 05c-movement2.pd, I can suddenly run the camera.
But if I close the 03b_ev_example_360_degree_livecam.pd, my camera is not working in 05c-movement2.pd anymore.
I've installed PureData Version 0.47 on my Windows Notebook with GEM 0.93.3 (32-Bit) and I can run my webcam without any errors.
My Notebook has the following properties:
OS: Windows 10 Pro Version 1903
RAM: 6 GB
System Type: 64 Bit
Processor: Intel(R) Core(TM) i5-3337U CPU @ 1.80 GHz
I ask myself why this versions work on my notebook properly and not on my PC?
Here's the output of my console:
GEM: Graphics Environment for Multimedia
GEM: ver: 0.93.3
GEM: compiled: Nov 10 2011
GEM: maintained by IOhannes m zmoelnig
GEM: Authors : Mark Danks (original version)
GEM: Chris Clepper
GEM: Cyrille Henry
GEM: IOhannes m zmoelnig
GEM: with help by Guenter Geiger, Daniel Heckenberg, James Tittle, Hans-Christoph Steiner, et al.
GEM: found a bug? miss a feature? please report it:
GEM: homepage http://gem.iem.at/
GEM: bug-tracker http://sourceforge.net/projects/pd-gem/
GEM: mailing-list http://lists.puredata.info/listinfo/gem-dev/
GEM: compiled for SIMD architecture: SSE2 MMX
GEM: using SSE2 optimization
[pix_video]: backend #0='DS' : directshow dv iidc analog
GEM: GLEW version 1.5.4
GEM: Start rendering
GEM: Stop rendering
@RayManiac Yes...... Gem 0.93 32-bit was always working.
The only thing I can find in the extendedview 360 cam (that works) is that a "1" is banged into the left inlet of [pix_video] as the patch is created.
Try that with 05c-movement2.pd.....?
David.
@whale-av said:
@RayManiac Yes...... Gem 0.93 32-bit was always working.
The only thing I can find in the extendedview 360 cam (that works) is that a "1" is banged into the left inlet of [pix_video] as the patch is created.
Try that with 05c-movement2.pd.....?
David.
@whale-av: I already run 05c-movement2.pd. It worked. If I compare the [pix_video] output from my notebook with the output of my PC I notice the videoInput is completely different. Maybe it is a software error on my PC?
Thanks you this hint about the extendedview360cam. It might be useful.
There is a bit of debate around this lately but I would suggest to try Ofelia. You just find it on Deken and the webcam support is great.
GEM is very robust and offers a great user experience, but Ofelia saves you a lot of time when it comes to video formats, streaming and images.
@dom1817 Thank you!
@whale-av said:
@RayManiac You could try downloading extendedview....... https://puredata.info/downloads/extended-view-toolkit ......... it is a very useful library anyway.
Then open 03b_ev_example_360_degree_livecam.pd
That is the only patch that will open my webcam in Gem.
Fast-forward a couple of years -- I just had a student with exactly the same problem, in Windows (couldn't open [pix_video] using the videoInput backend).
I had the student try extendedview -- the camera opened!
So then I wondered why... does extendedview implement a backend that Gem doesn't? (Seems not -- there are no files named anything like videoinput.)
Or some super-secret messages? So I added a [print] into ev_cam_dsp -- 3 cables into pix_video, one is gemlist so I'm not printing that, got the other two.
And...
to_pixvid: device 0
That's it. Nothing more than that. Just "device 0" -- so I asked the student to create a patch and send this message to [pix_video] before opening the gemwin -- and it worked.
So, for posterity: if pix_video isn't opening in Windows, it might be necessary to send it a "device" message (even though this might not be necessary in other OSes or even on other Windows machines). Not guaranteed to solve the problem in every case, but I think this explains why ev_cam worked for whale-av.
hjh
Oops! Looks like something went wrong!