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
Axis IP Camera can be added, but no Image seen. #404
Comments
Looks like this might be similar or the same as #391 . |
What did you enter when you created the webcam? |
Just attempted with: http://10.17.36.12/mjpg/video.mjpg , same behavior. Attempted to just enter "10.17.36.12" - http:// was automatically prepended within the dialog box, but still same behavior. |
Same issue as #387 |
Cool! We're not the only ones. I was never able to get any frames off of
|
I don't have access to a windows machine to test this bug on. Is there anyone out there not on a Windows machine that is also experiencing this problem? |
I'm experiencing this on Ubuntu 14.04 with a non-axis MPJEG stream. (Streaming from my raspi cam). I can get the stream in browser and on smartdash simple camera viewer, but GRIP isn't previewing, showing frames, and timing out and throwing that exception on delete or stop |
Tested on Windows x64 with GRIP 1.1.0 and 1.1.1 - same issue. |
Sorry, punched the wrong button. Doing some more sampling now, hopefully will have something useful to report soon. |
Ok, another sample point - tried on a different PC running windows 10. Were able to get some camera images sporadically - image stream would either start and work fine, or not start at all. Seemed that sometimes it would work the very first time after a fresh grip session was started and the camera had just been reset, but the break on subsequent IP camera deletion/add cycles within the same session of Grip. Other times, it would not display anything on the first IP camera add, produced the above stack trace on deletion, then succeed displaying the stream on the second attempt to add an IP camera. All of this is on the windows 10 PC, still a 0% success rate on multiple windows 7 machines. I'm leaning toward there being something in the frame grabber thread which isn't going 100% as expected, then on deletion the thread hangs and triggers the timeout. What is causing the hang isn't immediately obvious though.... |
I was working with @gerth2 on this last night and we did some more testing on this. It looks like we had something on the roboRio that was taking over the frame grabber at some times. We disconnected the roboRio and had a 100% success rate on the Windows 10 machine assuming we didn't have an existing process accessing the frame grabber. We believe the issue with the Windows 7 machines relates to some security software/settings installed by our sponsor. We'll have a completely different (store purchased) Windows 7 laptop to try tonight to confirm that theory. Assuming that all checks out it may make sense to close this issue, but if somebody wants us to dig into the source code and see where the error is popping up on our current Windows 7 machines we can try to figure that out when we have the time. For others reporting similar issues, here's our setup that worked reliably every time in GRIP that you should be able to use as a baseline:
|
- The IPCameraFrameGrabber was stuck in an infinte loop waiting for the rest of the image to arrive. This was fixed by using a DataInputStream instead - An unexpected end of the stream would cause a null pointer exception. Now throws an EOFException. WPIRoboticsProjects#390 Closes WPIRoboticsProjects#390 Closes WPIRoboticsProjects#427 Closes WPIRoboticsProjects#404 Closes WPIRoboticsProjects#387 Closes WPIRoboticsProjects#436
- The IPCameraFrameGrabber was stuck in an infinte loop waiting for the rest of the image to arrive. This was fixed by using a DataInputStream instead - An unexpected end of the stream would cause a null pointer exception. Now throws an EOFException. WPIRoboticsProjects#390 Closes WPIRoboticsProjects#390 Closes WPIRoboticsProjects#427 Closes WPIRoboticsProjects#404 Closes WPIRoboticsProjects#387 Closes WPIRoboticsProjects#436 Related bytedeco/javacv#322
- The IPCameraFrameGrabber was stuck in an infinte loop waiting for the rest of the image to arrive. This was fixed by using a DataInputStream instead - An unexpected end of the stream would cause a null pointer exception. Now throws an EOFException. WPIRoboticsProjects#390 Closes WPIRoboticsProjects#390 Closes WPIRoboticsProjects#427 Closes WPIRoboticsProjects#404 Closes WPIRoboticsProjects#387 Closes WPIRoboticsProjects#436 Related bytedeco/javacv#322
- The IPCameraFrameGrabber was stuck in an infinte loop waiting for the rest of the image to arrive. This was fixed by using a DataInputStream instead - An unexpected end of the stream would cause a null pointer exception. Now throws an EOFException. WPIRoboticsProjects#390 Closes WPIRoboticsProjects#390 Closes WPIRoboticsProjects#427 Closes WPIRoboticsProjects#404 Closes WPIRoboticsProjects#387 Closes WPIRoboticsProjects#436 Closes WPIRoboticsProjects#460 Related bytedeco/javacv#322
- The IPCameraFrameGrabber was stuck in an infinte loop waiting for the rest of the image to arrive. This was fixed by using a DataInputStream instead - An unexpected end of the stream would cause a null pointer exception. Now throws an EOFException. WPIRoboticsProjects#390 Closes WPIRoboticsProjects#390 Closes WPIRoboticsProjects#427 Closes WPIRoboticsProjects#404 Closes WPIRoboticsProjects#387 Closes WPIRoboticsProjects#436 Closes WPIRoboticsProjects#460 Related bytedeco/javacv#322
Using GRIP 1.0.0 on a x64 windows system. Can view webcam live view in Chrome. Putting in the IP address of the camera seems to add it in GRIP, but no image preview is available. Framerate is reported at zero. No downstream connected blocks have any visual output.
Exception thrown when deleting the camera in GRIP:
An event subscriber threw an exception
Stack Trace:
System Info:
This issue is most likely downstream of the actual problem. Any good way to go about debugging why the image preview is not displaying in GRIP to start?
The text was updated successfully, but these errors were encountered: