Quel est la différence technique entre les deux filtres suivant ?
52 mm - 850nm Infrared Infra-Red Filter
NIR Optical Filter, 850DF55, 25.4mm painted edge
Merci 
==google translation==
Hi,
What is the technical difference between the following two filters?
52 mm - 850nm Infrared Infra-Red Filter
NIR Optical Filter, 850DF55, 25.4mm painted edge
Thank you
i’m currently building a reacTVision-based tangible sound interface. my setup is typical and includes a PS3eye camera with a selection of objects tagged with fiducial markers. for interface, i want to build a cylindrical object with a round Acrylic surface on top, where tagged objects will be placed. i’m wondering what are the standard / best / ideal sizes for such structure? obviously, the cylinder needs to be in a comfortable height for interaction, and the acrylic top should be big enough to have space for many tagged objects, yet still compatible with the PS3eye’s lens.
any suggestions?
thanks,
K.
I am totally beginner.
I am using macbook Pro.
I found this. Any comment and suggestion would be very appreciated.
]]>Regards Prowler[youtube]http://www.youtube.com/watch?v=g_txF7iETX0[/youtube]
]]>I love the idea! Looking forward to it.
Mike
]]>I had to use a H.264 codec (set with lowest datarate) to reach this value. Also, the framerate was set to 60 in the camera settings. This configuration seems stable - as long as it works - because at one point the camera stops to send pictures to CCV and the only solution to get your image back is to reduce the wished framerate to 30 or less (and then you get only 25 or 36 frames per second).
Note the result is exactly the same whatever usb port is used (tested on a 2nd generation 15” MacBook Pro - Core 2 Duo 2.2 GHz).
This Macam’s version does also have settings for the white-black scale. Do not forget to set the “White Level” to a mid or high value setting otherwise you will get a black frame.
The “official” Macam 0.9.2 cannot go beyond 31 fps but can remain with this setting for a long time without any problem. And it doesn’t have the settings for white and black neither.
One can get all the specific Macam versions here : http://www.openframeworks.cc/files/
What seems strange is the camera resolution reported by CCV : always 320 x 320 pixels (why not 320 x 240 ?), whatever driver’s version used.
]]>
I have just purchaced a Point Grey Firewire MV IEEE 1394a camera which comes with Driver CD which has the flyCapture version 1.8.
The camera works extremely well on Windows XP and on Windows Vista with CCV 1.2, however as soon as I try to get it running on my Windows 7 Machine CCV either dosent come up at all as long as the camera is connected and gives a screenshot of the CCV dashboard as soon as I pull the plug of the camera or it simply crashes though it runs perfectly in flycapture, I have also tried installing the flycapture 2.0 and the CCV 1.3 installer nothing seems to work.
I have also tried using the ubCorePro32 driver and still CCV crashes
Has anyone come across a problem similar to the one that I am facing or am I missing out something
PLEASE HELP
]]>
I build a FTIR wall with a screen size of ~1,2m x 0,9m. Now I have to search for a camera.
I see the cameras at http://www.peauproductions.com and I think that this is the best way for me, because I have to build the MT quickly.
I have as a test system a Notebook with Intel Core 2 Duo P8700 2,53 GHz with 4 GB RAM, but I have only a built-in graphic card (Intel GMA X4500HD (IGP) shared memory) which could be a bottleneck?
Perhaps it will be better to get this one?
Core 2 Duo T9600 2x 2.80GHz with NVIDIA GeForce 9300M GS 256MB
Or should I use instead of a notebook a desktop PC system?
Bit the main question is about the camera. With my screen size of 1,2m x 0,9m I want to have a compact system. So I only have a distance between 55cm - 75cm.
So I see (excel file of peauproducations), that 55cm won’t work, I need a distance of ~70cm.
But I also read that the edges won’t recognize finger tips very good with the 2,1mm lens. What could I do?
Make the screen size a little bit smaller?
It is all because the Wall-system. I can not make a wall with a depth of > 60cm. So I have to use a first surface mirror or I saw this special mirror foil. Can I use this one to look through it with the camera? Or should I better use a front surface mirror? I need the mirrot to make a greater distance between projection layer and projector, and to increase the distance plexiglass <-> webcam for blob detection.
Perhaps someone can help me with this problem?
Thanks a lot in advance & Best Regards.
]]>
As you may seen it before, here are the specs:
- 4 channel audio input:16 bits/channel, 48kHz, SNR 90db
- 56º or 75º Field of View zoom lens
- 2.1 F-stop, <1% distortion, fixed focus (25cm to 8 at 75º FOV)
- 640 x 480 at 60 frames/second
- 320 x 240 at 120 frames/second
- USB.0 high-speed data transfer
- Uncompressed video or optional JPEG compression
This makes the PS3Eye ideal for multitouch applications. The best part is the price $39.99! I found mine here.
Now, the main problem with this camera is that there are no drivers for Windows. The camera’s chipset info is virtually non-existent on the web.
After examining the camera internals (pictures here) I found that it features the OV534-LB50 camera USB 2.0 bridge and the OV7720 CMOS VGA sensor. Both of these are made by OmniVision.
I started thinking to my self: “This camera is awesome and it will be such a great and inexpensive replacement for Firefly MV and the like. If we could just get it to work under Windows...”
Initially, I started poking around with the USB trying to send some commands to the PS3Eye and see what happens…
After many long nights I’m bringing you the result:
- Full VGA (640x480) 60fps video capture test app that features uncompressed high quality raw video
- Low CPU overhead (since there is no decompression involved on the PC)
- Very low latency (1 frame time period)
The camera currently streams video in YUYV format, therefore each frame is 640*480*2 bytes.
At 30fps this amounts to about 17.5MB/s which is pretty low in comparison to the total USB 2.0 bandwidth.
At 60fps the amount of data gets higher and it could be affected by other peripherals connected to the USB host controller.
This is why it is recommended that the camera be the only device connected to the USB host controller.
Most of the CPU overhead that I currently have is the color conversion code that is implemented in straight C/C++ without any SIMD optimizations.
For real (MT) applications this code will go away, since we will be extracting raw grayscale image (every second byte of YUYV).
My driver exposes PS3Eye camera as a device with direct access, thus eliminating the complexities and the overhead of DirectShow system.
For multitouch applications (where low latency is a key) I will be working on custom PS3EYE capture filter for use in TouchLib. In parallel I will be working on a DirectShow filter that will allow wide use of this camera on Windows.
Installation:
- Unplug the PS3Eye camera from your comupter.
- Download and run the latest CL-Eye Platform file.
- Click ‘Install’ and follow the setup process.
- Plug in the camera.
After successful installation, your Device Manager should look similar to this:
Now run the PS3EyeTest.exe program, and the captured video as well as the FPS counter will be displayed.
I added the camera image controls:
Go, try it for yourself…
Enjoy!
~Alex
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
*UPDATE* 08-25-2009
New version of the driver (v3.0.0.825)
Open Source PS3Eye DirectShow Driver Component!!!
[frame]http://widget.chipin.com/widget/id/a717a49af8cdfabd[/frame]
]]>First off, my testing environment. Running Ubuntu 8.10 AMD64 with a custom kernel. Note: the standard issue model should do just fine, mine is trimmed down and optimized for my processor. These instructions should apply just fine to other distributions, but you will have to modify the commands accordingly (such as using root instead of sudo, and your package manager). I am going to assume that you have a basic knowledge of the terminal and all necessary build tools installed ("sudo apt-get install build-essential” on Ubuntu).
Now, on to the fun stuff. Thanks to a group on Linuxtv.org, we have a nice new V4L driver available for this. The first step is to install ‘hg’ (included in the “mercurial” package on Ubuntu), and download the latest version of said driver:
sudo apt-get install mercurial
hg clone http://linuxtv.org/hg/~jfrancois/gspca/
You should have a folder named “gspca” in the current terminal directory. Now we want to change into that directory and begin the build process:
cd gspca
make
At this point, make might complain about any number of things. You will want to check and make sure it is installing for your *current kernel* (check with “uname -r” if you are unsure). That is the biggest issue. If it complains about something else, post here and I or someone else will try to help as much as possible. If your build is successful, go ahead and install it:
sudo make install
You should now have a patched V4L installed, and the driver should be working. Let’s go ahead and test this. Change into the test programs directory (assuming you are still in “gspca"), and build the driver test file:
cd v4l2-apps/test/
make driver-test
Now plug in your camera, and it is time to see if the driver install worked.
./driver-test
. This should produce an output string with information about the file format, and what is being transferred, etc.. If it says “no /dev/video*”, make sure the camera is plugged in. It seems to autodetect the proper video device, so other cameras or video capture cards shouldn’t be a problem.
If you have made it this far, congratulations. Time to see some actual results in video form. Install one of the configurable video programs (Mplayer, VLC, Xawtv, etc..). VLC is probably the easiest to use here so:
sudo apt-get install vlc
Open VLC, then go to Media > Open Capture Device. In the configuration window, set it to V4L2, video device: /dev/video0, audio device: /dev/audio1. Your video and audio devices may be different, this assumes no other video inputs and one audio input (motherboard mic input in my case). In a second or two, you should see some nice 640x480 video in proper color, and the audio should be working. This concludes this part of the install process, as I haven’t yet tried anything further myself (will test tbeta and some other programs soon and report back).
The problems seem to be: jumpy video, and VLC crashes if custom settings are used (e.g. for resolution and framerate). The occasional jumpy video can be blamed on the huge amount of raw video data being processed, and I am still looking into the custom settings problem. I imagine that as drivers for this camera progress, performance will too.
This concludes my tutorial, I hope it helps some. Please feel free to chime in with any questions or comments.
[edit] Oops, almost forgot to give credit. I had nothing to do with developing drivers, the guys at linuxtv.org (specifically “jfancois”, but I am sure there are others) took care of that. Getting it to work was largely thanks to excerpts from the PS2 Dev forums, specifically “jimparis” and “ao2”. Thread: http://forums.ps2dev.org/viewtopic.php?t=9238&postdays=0&postorder=asc&start=0
]]>