You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Install IP Webcam (by Pavel Khlebovich) from the play store on your Android
device
2. Configure and run the app
3. Connect to the app using http://a.b.c.d:8080/videofeed
What is the expected output? What do you see instead?
Expected Output: 25fps+ in iSpy.
Actual Output: Initial 15fps dropping to around 6fps
What version of the product are you using? On what operating system?
iSpy 4.8.4.0, Windows 7 Professional 64bit on an i7 950, 6G RAM, Intel SSD for
recording onto.
Please provide any additional information below.
To eliminate the Android device as the bottleneck I also connected to the apps
own web page to view the video feed - it appeared ok and was updating quickly.
I then configured ManyCam to connect to the Android device and used that as a
video source in iSpy. I started to get 25fps in iSpy.
I've tried this now on an LG Optimus L3, a Motorola Xoom, and a Samsung Galaxy
S3 - all give roughly between 4 - 7fps in iSpy and 25fps+ when iSpy is using
the ManyCam source.
Original issue reported on code.google.com by [email protected] on 19 Mar 2013 at 11:39
The text was updated successfully, but these errors were encountered:
Please see this to help with the fix
http://foscam.us/forum/low-fps-on-foscam-cameras-t1088-10.html#p4912
Excerp
Official answer from foscam engineers
Our engineers installed iSPY to test,it is really 4Fps.
The reason is as this third party software based on the CGI command,using the
CGI command to get the audio and video data.
Network processing section using up much CPU source,but for the IE active x,is
based on the bottom protocol,so there is no problem with our IE active x to get
15 Fps.
The solution is:
1.Unless iSPY can base on our SDK,according to our bottom protocol.
Original issue reported on code.google.com by
[email protected]
on 19 Mar 2013 at 11:39The text was updated successfully, but these errors were encountered: