Get available pixel formats for camera device #31
Comments
|
Interesting! Thanks for the report, Spencer. Can you try with master and see if you get the same behavior? (Assuming you haven't already, of course. ) |
|
Whoops, no, it should be fixed by #21, but I haven't merged that yet. Will do so sometime today. |
|
Kevin, I replied to your kind message in JuliaLang/julia#8288. But since the issues I am having right now have more immediately to do with trying VideoIO, I thought I´d repost the message here. I Installed VideoIO (following the instructions on GitHub) but it did not work on my Mac OSX 10.9.4 with Julia v0.3. The downloading of the sample movie Io stream worked fine, but the window display was black (no image). When I tried f = VideoIO.opencamera() failed to capture any live video from my camera (MacBookPro 2010). julia> f = VideoIO.opencamera() [AVFoundation input device @ 0x7fece837c5e0] |
|
I just tagged a new version of I'm a little concerned about the window display being black--that sounds like an issue with either the @timholy, any thoughts on those? |
|
I did the Pkg update, and then tried both the instructions in the main VideoIO page and the ones from Spencer above. However, I still get a black window with the downloaded IO stream as follows: julia> VideoIO.playvideo(f) With the built-in video, I saw this Any thoughts? |
|
If you're using recent versions of both VideoIO and Images, I don't understand why the image is a 3d |
|
Thanks for checking this out. I did not use my images or anything with 3d as far as I know. I used the following example straight from thee VideoIO GitHub page: Aternatively, you can just open the camera#VideoIO.viewcam() I obtained the errors I posted already in the messages above. |
|
Since the last Pkg.update(), I obtained a Warning when I typed "using ImageView" at the Julia prompt. |
|
The 3d in my comment was because of So basically if you're running a recent version of the package I don't understand how you could possibly be getting that error. (The example works for me.) I also don't get the same ambiguity warning you do, although julia's ambiguity warnings are occasionally flaky. So, let's ask: what does |
|
julia> versioninfo() 12 required packages:
|
|
Somehow you ended up on te master branch of Images, which in your repo is Pkg.release("Images") On Wednesday, September 10, 2014, Maximiliano Suster <
|
|
Fantastic, at least I got to see the movie now! However, it was not all smooth as a number of errors appeared in the shell and also a warning widget. Could these errors be related to resizing the window frame during the viewing? Here is the shell output during the movie: |
|
Yes, some of those errors are definitely from resizing Tk. The crash is On Wed, Sep 10, 2014 at 10:37 AM, Maximiliano Suster <
|
|
Resizing during playback works fine for me, and I don't see such errors. If you FYI my tk version is 8.6. |
|
ok. I will update TK and try again. I don´t think there was a specific sequence of events, just repeated dragging out of the window to get a better look at the movie. Meanwhile, are you aware of any further work towards the OpenCV wrapper which has not been merged with the Git repo yet? I checked the files in the Git repo, but this is still very early days . . . |
|
It's not my repo, and I'm not working on it (I'm going to focus my efforts on Images), so I have no idea about what hasn't been committed. For the latest you can just look for commits to that repository. Better yet, make some commits yourself 😄. |
|
Sure, the idea is to start working on this! However, before I embark on completely new terrain with Julia image processing/analysis, I would much prefer to know what has been done, who else is working on this and whether there is much else in the pipeline. I noticed that Alexander Sun was the one working on this (GSoC 2014 project) but I have not received any reply from him yet about the repo (even though something presumably was updated 3 days ago). Anyway, I am looking into what I may be able realistically to contribute towards the wrapper - would be nice. |
|
@ssfrr, I've committed #21 (and a few other changes/fixes) which might help this issue. Can you run @maxruby, the segfault that you saw should hopefully be fixed by JuliaGraphics/Tk.jl#81. Can you also update and try again? Note that the warnings when resizing or doing other window manipulations might still be there--at least, I still see them occasionally. |
|
Lots of errors after doing Pkg.update() on my MacOSX upon your request (everything seem to be working before this update, except for VideoIO not accessing ffmpeg DEFAULT_CAMERA_DEVICE) When I checked Pkg.status(), I got (other I ran Simon Danish´s code that uses VideoIo, GLPlot, React and GLAbstraction. This worked before updating so something has happened with the update. device = "Innebygd iSight" Just for fun, lets apply a laplace filter:kernel = [-1 -1 -1; #async=true, for REPL use. Then you don't have to call renderloop(window) #Get Gpu memory object #Asynchronous updating with React: renderloop(window) I will try again updating and rechecking all the packages but if you have any ideas why this is happening, please let me know. |
|
Hmm, I'm still seeing the same behavior as the top post (upside-down image and "Selected pixel format" warnings. |
|
@maxruby, try running |
|
@ssfrr, Hmmm.. @staticfloat saw the same thing here, but found that it worked after that. Just to check, can you give the output of At any rate, we probably need to be querying the supported formats anyway. This depends on #27, so I'll try to work on that next. |
|
I just pushed a small change which will give a more informative error message when the user doesn't load |
|
OK. I included both import VideoIO and ImageView and I still had trouble. julia> include("/Users/maximilianosuster/RubymineProjects/daily_programmer/Julia/webcam.jl") |
|
React.jl was renamed to Reactive.jl, and it looks like you have both on So that we don't diverge too much more from the original report here, if On Sun, Sep 14, 2014 at 9:38 AM, Maximiliano Suster <
|
|
julia> VideoIO.versioninfo() |
|
Thanks. And this is defintely VideoIO v0.0.5 or later? |
|
Yep, |
|
and ImageView is 0.1.4, if that matters. |
|
Alright, I should have looked closer: the upside down image was actually caused by that merge! I just updated VideoIO. You'll probably still get the warnings (let me know), but the flipped image should be fixed. |
|
To be clearer: can you update with Pkg.update() and test again? :-) |
|
Bump. @ssfr, is this still an issue? |
|
Whoops, sorry for losing track of this. I just ran Pkg.update(), and as you predicted, I still see the warnings but the image is now right-side-up. |
|
Perhaps I can help with this? For me, VideoIO is working fine. Maybe there is something about the setup of the camera with VideoIO? |
|
Sorry I reread @ssfrr - I guess its all fine. |
kmsquire
changed the title
kmsquire
changed the title
|
Okay, thanks! I reworded the title to better reflect the remaining issue. As I mentioned previously, that depends on #27. |
|
This particular issue seems to have been fixed, although there are related issues (e.g., #148) |
When opening the camera on OSX the image is upside-down. It also prints the following:
But it's working!!
The text was updated successfully, but these errors were encountered: