-
Notifications
You must be signed in to change notification settings - Fork 166
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
video does not work #1
Comments
Same here with Archlinux and Debian. Someone has to replace the psyco code with something that is maintained and that works with current versions of Python (2.7, 3.3). Maybe gstreamer? |
Pypy should be the proper replacement for psyco, but I haven't tested yet if it works with all libraries required for python-ardrone. Running a Python application with pypy is simply a matter of starting it with pypy myapp.py But I fear pygame is not compatible, so one would have to find an alternative to display the video output. |
I am using opencv to grab the video and it seems to work just fine. Take a look at my project (https://github.com/Sanderi44/AR-Drone-Fire-Detection) to see how I am doing it. I haven't changed anything in this library, but I would suggest using this simple method for image processing with the AR Drone 2 |
Also broken for me, but I got it working with opencv: import cv2
cam = cv2.VideoCapture('tcp://192.168.1.1:5555')
running = True
while running:
# get current frame of video
running, frame = cam.read()
if running:
cv2.imshow('frame', frame)
if cv2.waitKey(1) & 0xFF == 27:
# escape key pressed
running = False
else:
# error reading frame
print 'error reading video feed'
cam.release()
cv2.destroyAllWindows() |
This still works. One has to have openCv installed/built with ffmpeg (e.g. |
I have a Ubuntu 12.04 LTS OS with Python 2.7.3
I can fly the drone and this works great.
Sadly psycon is no longer maintained and a dead project. And psycon does not work with Python 2.7, only with Python 2.6
Is there any possibility that this might be fixed in the future? Is there any workaround/fix/solution to this?
The text was updated successfully, but these errors were encountered: