-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add an example launchfile which works for standard cameras on OS X #14
Comments
Can you post the contents of your launchfile? |
This is v4l.launch where "v4l2src" is replaced by "qtkitvideosrc". |
In |
Also, it looks like Can you run (and post the output of) the following:
|
Doesn't seem to have any effect. I can still type whatever in the place of /dev/video0 and it will still run, using the primary camera. |
--and--
|
I changed the gscam_config parameter to have video/x-raw-yuv, which is supported according to the above file, but I didn't see a change in behavior. |
how about |
Still the same results. However, I notice that in both cases if I am looking at the video stream through another program, that starting gscam causes the video stream to change format to 640x480. So things are definitely happening, I'm just not sure what. Is normal procedure for the gscam topic to appear, as well as the other two topics? Is it sensible to query the gscam topic in hopes that the video data is published there? |
I assumed that you weren't seeing any images on those topics. When you bring up |
Oh, pardon my ignorance. I was working off the camera calibration tutorial and:
left me thinking that there were no other topics published. However, loading up |
Cool! I'd expect that w.r.t. listing topics, you want to run |
Alas, that part is remaining stubborn. I have two cameras on my system, but even going to "3" makes no difference. I would have expected it to fail when I typed in random garbage for the address, but it simply seems to ignore that part of the config line. Note: if I change the video back to rgb it freezes, as well as if I pass an incorrect width or height. It's parsing that line, it's just the video device that's being ignored. |
@jbohren I figured out what you were saying earlier. I was replacing "/dev/video0" by "dev/video1". However, you were suggesting "0" or "1", which does work. So thanks, it's 100% functional now. I'll submit a patch soon. |
One thing I'm still having a little trouble with is figuring out "set_camera_info". The directions at http://wiki.ros.org/camera_calibration/Tutorials/MonocularCalibration indicate
which I change to reflect that the camera is published on "/qtkit". However, I still get an error:
Is there a way for me to verify that gscam is publishing the set_camera_info topic? |
|
Perfect. That made it clear to me that the appropriate command was |
Yeah, you can blame me for that. It should be |
Does gscam also publish /camera/camera_info? https://github.com/uzh-rpg/rpg_monocular_pose_estimator/blob/master/monocular_pose_estimator/src/monocular_pose_estimator.cpp#L34 wants to subscribe to a node named as such. |
Yes it does. It publishes |
Got it. The problem was that the code I'm trying to use was looking for these in a hard-coded place. I'm now able to visualize the output: Thanks a million, @jbohren. I really appreciate you bearing with me as I worked through this. |
…e_gscam2 Change package name to gscam2
As a result of resolving issue #13 (problems compiling on OSX), I came across this second problem. When launching gscam
image_raw
andcamera_info
topics are not published. The only published topic is the gscam node itself, which in this case is still called "/v4l/gscam_driver_v4l".Note that the hardware seems to be active, so it might be that I haven't launched all necessary processes. I'm currently running only roscore and gscam.
The text was updated successfully, but these errors were encountered: