Page 1 of 2

repeated/frozen image mystery

Posted: Sat Dec 22, 2012 5:59 am
by neutron68
I've seen a problem every time I take frames from the D-link DCS-900 webcam for an all-day time lapse movie.

I've been starting capturing frames around 8:00am.
By 1:15-3:00pm, the webcam stops sending new images.
At some point, the webcam keeps sending the same image over and over - a freeze-frame, of sorts.
Of note, the time code that Yawcam puts in the frames changes, but the image stays the same.

Has anyone else seen this and know how to solve it?

On 12-11-2012, the images started repeating after 372 frames (around 2:52pm - 8hr. 52min)
On 12-12-2012, the images started repeating after 352 frames (around 1:56pm - 7hr. 56min)
On 12-21-2012, the images started repeating after 316 frames (around 1:15pm - 7hr. 15min)

I'm not sure what is causing the repeated image?
Perhaps logging into the webcam remotely is disrupting Yawcam's image capture?
I know I looked at the webcam remotely after lunch on 12-11 and on 12-21.
I didn't log in on 12-12, however.
Perhaps someone I've given the webcam login code is logging in?

-edit-

Oh, I just found other reports of this:

http://www.yawcam.com/forum/viewtopic.p ... b1fd76da93

I guess there's no fix yet?

Eric

Re: repeated/frozen image mystery

Posted: Sun Feb 03, 2013 2:45 am
by neutron68
I just tried the BETA 1-29-2013 version. It does not solve the repeated/frozen image problem. But, it may have slightly different symptoms than I saw in version 0.3.9.

I tried a time-lapse movie today 2-2-2013 capturing 1 frame every 60 seconds. I saw many instances of 2-3 repeated frames. That seems new to me. I also saw several strings of repeated frames that went on for 5-20 frames. When I caught those, I closed the Yawcam application and restarted it.

Would the problem of repeated frames be solved if the software were changed to log into the camera for EACH frame?

Eric

Re: repeated/frozen image mystery

Posted: Sun Feb 03, 2013 1:22 pm
by malun
Thanks for the feedback. If I understand you right:
With version 0.3.9 you get frozen images after something about 7 hours and that won't recover?
With the beta 2013-01-29 you get frozen images during some periods but they recover and get updated again?

Do you get any error messages in the console tab?
Could you please run Yawcam in debug mode and send the log file in an email to me?
More info on how you create that log file here:
viewtopic.php?f=2&t=1495

neutron68 wrote:Would the problem of repeated frames be solved if the software were changed to log into the camera for EACH frame?

No, not if there is some kind of problem with the network connection to the camera. Then Yawcam won't be able to connect to the camera.

When I built the "device error monitor" I did some of the tests with a network camera. When the camera is disconnected from the network Yawcam gets frozen images, but starts trying to reconnect the camera again. As soon as the camera is connected to the network again, Yawcam is able to reconnect to the camera and the images won't be frozen any more.

/mlun

Re: repeated/frozen image mystery

Posted: Sun Feb 03, 2013 6:48 pm
by neutron68
malun wrote:Thanks for the feedback. If I understand you right:
With version 0.3.9 you get frozen images after something about 7 hours and that won't recover?
With the beta 2013-01-29 you get frozen images during some periods but they recover and get updated again?/mlun

Correct, 0.3.9 it never recovered.
Correct, that's what it looks like with the 1-29-13 beta.

malun wrote:Do you get any error messages in the console tab?
Could you please run Yawcam in debug mode and send the log file in an email to me?
More info on how you create that log file here:
viewtopic.php?f=2&t=1495/mlun

No, I don't recall seeing any messages when I looked at the console tab. I didn't look every time.
Sure, I can do that. I'm happy to help diagnose this.

Eric

Re: repeated/frozen image mystery

Posted: Mon Feb 04, 2013 12:04 am
by neutron68
OK. I just tried a frame capture in debug mode and have a debug file to share.

I captureed 259 frames, and the frames started repeating at frame 76 onwards.
During the first 75 frames, there were many instances of duplicate frames.
For example, frames 4,5 and 6 were all the same, then 7 was a new frame, but was repeated in frame 8, and 9.

I'll PM you the debug file.

Eric

Re: repeated/frozen image mystery

Posted: Sat Feb 23, 2013 6:36 pm
by neutron68
I received a message from one of the forum admins regarding running yawcam in an alternate debug mode that produces different output.
I read it on Feb. 10 via my cell phone while I was traveling.

Now, I can't find the message in the forum or in my Private Messages.

Can you resend the alternate debug instructions?

Thanks,
Eric

Re: repeated/frozen image mystery

Posted: Sat Feb 23, 2013 6:45 pm
by malun
I think you got it as an email.
Now, you have a new email again.

/malun

Re: repeated/frozen image mystery

Posted: Sat Feb 23, 2013 6:51 pm
by neutron68
Thanks for the resend! After you mentioned email, I went back and found your original message.

There's just so many avenues of communication now! (PM, forum, email, Facebook, IM on phone).
It's hard to remember where I read something, these days!

I'll now run Yawcam with the "text file hack": javarendering.txt.
(viewtopic.php?f=4&t=1264)

I take it I should NOT run with the debug mode this time (which generates a verbose text file)?

Eric

Re: repeated/frozen image mystery

Posted: Sat Feb 23, 2013 7:43 pm
by neutron68
I'm Running Yawcam 0.4.0 with the "javarendering.txt" file in place.

The first 33 frames were all different. Then frames 34 and 35 were repeats of frame 33.

--additional--

I'm up to 132 frames now...more double and triple repeated frames.

--additional--

I'm up to 294 frames now...more double and triple repeated frames.

Eric

Re: repeated/frozen image mystery

Posted: Sun Feb 24, 2013 11:48 am
by malun
A debug file is always helpful. The new version 0.4.0 is less verbose than previous versions in this area.
But if you are running the ordinary way now, that's okay :-)

I guess you still don't get any messages from the device monitor in the console tab?

/malun

Re: repeated/frozen image mystery

Posted: Sun Feb 24, 2013 11:51 am
by malun
Another thing. If it's okay with you, I would like you to email me some images.
Could you send me frame 33, 34, 35 and 36 ?

/malun

Re: repeated/frozen image mystery

Posted: Sun Feb 24, 2013 2:15 pm
by malun
I'm on to something.

If I only enable the file output and close the preview and capture window, Yawcam will pause the device between the images are taken.
(This is to save CPU usage when nothing is using the camera)
This also means that the Device monitor will be paused. It's only running when the device is running.
That's why you don't get any messages from the device monitor in the console.

I guess you are running with the preview window closed?

It's possible that the problem is related to when Yawcam starts up the device from paused mode.
Could you please make new try and run Yawcam with the file output enabled but also with the preview window open?
(This will force Yawcam not to pause the device.) Perhaps that could make a difference?

/malun

Re: repeated/frozen image mystery

Posted: Sun Feb 24, 2013 3:39 pm
by malun
I was able to reproduce the problem on my machine!
This is good. It's now easier to debug.

/malun

Re: repeated/frozen image mystery

Posted: Wed Feb 27, 2013 12:37 am
by neutron68
Hi, it's Tuesday...just checking back.

Correct, I had the preview window closed.
Correct, I was not running in debug mode - mainly because you said there wasn't any helpful evidence in it the last time I ran in debug mode.

Do you still want the repeated frames you asked about?

I am guessing that since you have been able to reproduce the repeated frames, you may not want/need my repeated frames?

Let me know.

Eric

Re: repeated/frozen image mystery

Posted: Wed Feb 27, 2013 12:52 am
by z3r0c00l12
Just a quick side note, maybe it's a matter of the image not being refreshed or grabbed from the cache since it's an IP camera?

I could be completely wrong though.