Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.mac.system > #55220 > unrolled thread
| Started by | Don Bruder <dakidd@sonic.net> |
|---|---|
| First post | 2014-01-23 10:42 -0800 |
| Last post | 2014-01-23 22:06 -0500 |
| Articles | 20 on this page of 145 — 12 participants |
Back to article view | Back to comp.sys.mac.system
Any quick, easy way to compare two images? Don Bruder <dakidd@sonic.net> - 2014-01-23 10:42 -0800
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-23 14:24 -0500
Re: Any quick, easy way to compare two images? Don Bruder <dakidd@sonic.net> - 2014-01-23 13:00 -0800
Re: Any quick, easy way to compare two images? Tom Stiller <clusterfux.upmon@gmail.com> - 2014-01-23 21:11 +0000
Re: Any quick, easy way to compare two images? Don Bruder <dakidd@sonic.net> - 2014-01-23 16:38 -0800
Re: Any quick, easy way to compare two images? john hevelin <bwotte@panix.com> - 2014-01-24 01:57 +0000
Re: Any quick, easy way to compare two images? Doug Anderson <ethelthelogremovethis@gmail.com> - 2014-01-23 18:03 -0800
Re: Any quick, easy way to compare two images? Don Bruder <dakidd@sonic.net> - 2014-01-23 21:25 -0800
Re: Any quick, easy way to compare two images? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-01-23 16:31 -0500
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-23 16:57 -0500
Re: Any quick, easy way to compare two images? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-01-23 17:02 -0500
Re: Any quick, easy way to compare two images? Don Bruder <dakidd@sonic.net> - 2014-01-23 21:28 -0800
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-23 16:32 -0500
Re: Any quick, easy way to compare two images? Don Bruder <dakidd@sonic.net> - 2014-01-23 16:22 -0800
Re: Any quick, easy way to compare two images? Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-01-23 19:48 -0500
Re: Any quick, easy way to compare two images? Don Bruder <dakidd@sonic.net> - 2014-01-23 23:54 -0800
Re: Any quick, easy way to compare two images? Doug Anderson <ethelthelogremovethis@gmail.com> - 2014-01-24 08:09 -0800
Re: Any quick, easy way to compare two images? Don Bruder <dakidd@sonic.net> - 2014-01-24 08:44 -0800
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-23 22:06 -0500
Re: Any quick, easy way to compare two images? Don Bruder <dakidd@sonic.net> - 2014-01-23 23:37 -0800
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-23 20:46 +0000
Re: Any quick, easy way to compare two images? Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-01-23 23:19 +0000
Re: Any quick, easy way to compare two images? Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-01-23 18:38 -0500
Re: Any quick, easy way to compare two images? Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-01-24 00:49 +0000
Re: Any quick, easy way to compare two images? Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-01-23 19:59 -0500
Re: Any quick, easy way to compare two images? Doug Anderson <ethelthelogremovethis@gmail.com> - 2014-01-23 15:25 -0800
Re: Any quick, easy way to compare two images? Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-01-23 18:37 -0500
Re: Any quick, easy way to compare two images? Doug Anderson <ethelthelogremovethis@gmail.com> - 2014-01-23 16:05 -0800
Re: Any quick, easy way to compare two images? Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-01-23 19:47 -0500
Re: Any quick, easy way to compare two images? Doug Anderson <ethelthelogremovethis@gmail.com> - 2014-01-23 17:10 -0800
Re: Any quick, easy way to compare two images? Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-01-24 17:42 -0500
Re: Any quick, easy way to compare two images? Doug Anderson <ethelthelogremovethis@gmail.com> - 2014-01-24 16:42 -0800
Re: Any quick, easy way to compare two images? Don Bruder <dakidd@sonic.net> - 2014-01-24 20:08 -0800
Re: Any quick, easy way to compare two images? Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-01-25 10:54 -0500
Re: Any quick, easy way to compare two images? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-01-25 15:31 -0500
Re: Any quick, easy way to compare two images? Don Bruder <dakidd@sonic.net> - 2014-01-25 17:31 -0800
Re: Any quick, easy way to compare two images? Michael Vilain <vilain@NOspamcop.net> - 2014-01-25 17:57 -0800
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 03:09 +0000
Re: Any quick, easy way to compare two images? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-01-25 23:02 -0500
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 05:04 +0000
Re: Any quick, easy way to compare two images? Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-01-25 10:58 -0500
Re: Any quick, easy way to compare two images? Doug Anderson <ethelthelogremovethis@gmail.com> - 2014-01-25 10:29 -0800
Re: Any quick, easy way to compare two images? Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-01-25 13:39 -0500
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-25 13:45 -0500
Re: Any quick, easy way to compare two images? Doug Anderson <ethelthelogremovethis@gmail.com> - 2014-01-25 13:27 -0800
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-25 16:30 -0500
Re: Any quick, easy way to compare two images? Doug Anderson <ethelthelogremovethis@gmail.com> - 2014-01-25 13:33 -0800
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-25 16:52 -0500
Re: Any quick, easy way to compare two images? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-01-25 17:31 -0500
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-25 22:35 +0000
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-25 17:49 -0500
Re: Any quick, easy way to compare two images? Tom Stiller <clusterfux.upmon@gmail.com> - 2014-01-25 22:55 +0000
Re: Any quick, easy way to compare two images? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-01-25 18:33 -0500
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-25 19:42 -0500
Re: Any quick, easy way to compare two images? Don Bruder <dakidd@sonic.net> - 2014-01-25 17:38 -0800
Re: Any quick, easy way to compare two images? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-01-25 22:50 -0500
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 02:49 +0000
Re: Any quick, easy way to compare two images? Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-01-26 14:21 +0000
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 15:17 +0000
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-26 14:04 -0500
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 00:17 +0000
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-25 19:42 -0500
Re: Any quick, easy way to compare two images? dorayme <do_ray_me@bigpond.com> - 2014-01-26 12:23 +1100
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 02:54 +0000
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 02:52 +0000
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-25 22:10 -0500
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 03:32 +0000
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-25 22:55 -0500
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 05:02 +0000
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-26 14:04 -0500
Re: Any quick, easy way to compare two images? Doug Anderson <ethelthelogremovethis@gmail.com> - 2014-01-25 18:03 -0800
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-25 22:10 -0500
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-25 17:49 -0500
Re: Any quick, easy way to compare two images? Savageduck <savageduck1@{REMOVESPAM}me.com> - 2014-01-25 15:59 -0800
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 00:24 +0000
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-25 19:42 -0500
Re: Any quick, easy way to compare two images? Savageduck <savageduck1@{REMOVESPAM}me.com> - 2014-01-25 17:30 -0800
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 02:57 +0000
Re: Any quick, easy way to compare two images? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-01-25 22:46 -0500
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 03:49 +0000
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-25 22:55 -0500
Re: Any quick, easy way to compare two images? dorayme <do_ray_me@bigpond.com> - 2014-01-26 12:08 +1100
Re: Any quick, easy way to compare two images? Savageduck <savageduck1@{REMOVESPAM}me.com> - 2014-01-25 17:31 -0800
Re: Any quick, easy way to compare two images? dorayme <do_ray_me@bigpond.com> - 2014-01-26 13:00 +1100
Re: Any quick, easy way to compare two images? Don Bruder <dakidd@sonic.net> - 2014-01-25 20:13 -0800
Re: Any quick, easy way to compare two images? dorayme <do_ray_me@bigpond.com> - 2014-01-26 16:15 +1100
Re: Any quick, easy way to compare two images? Doug Anderson <ethelthelogremovethis@gmail.com> - 2014-01-25 18:07 -0800
Re: Any quick, easy way to compare two images? Savageduck <savageduck1@{REMOVESPAM}me.com> - 2014-01-25 18:24 -0800
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 02:58 +0000
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-25 22:10 -0500
Re: Any quick, easy way to compare two images? Don Bruder <dakidd@sonic.net> - 2014-01-25 17:36 -0800
Re: Any quick, easy way to compare two images? Savageduck <savageduck1@{REMOVESPAM}me.com> - 2014-01-25 17:51 -0800
Re: Any quick, easy way to compare two images? Don Bruder <dakidd@sonic.net> - 2014-01-26 00:39 -0800
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 15:43 +0000
Re: Any quick, easy way to compare two images? Doug Anderson <ethelthelogremovethis@gmail.com> - 2014-01-26 08:19 -0800
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 16:31 +0000
Re: Any quick, easy way to compare two images? Doug Anderson <ethelthelogremovethis@gmail.com> - 2014-01-26 09:54 -0800
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 18:14 +0000
Re: Any quick, easy way to compare two images? Doug Anderson <ethelthelogremovethis@gmail.com> - 2014-01-26 10:44 -0800
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 19:10 +0000
Re: Any quick, easy way to compare two images? dorayme <do_ray_me@bigpond.com> - 2014-01-27 11:14 +1100
Re: Any quick, easy way to compare two images? Doug Anderson <ethelthelogremovethis@gmail.com> - 2014-01-26 16:22 -0800
Re: Any quick, easy way to compare two images? dorayme <do_ray_me@bigpond.com> - 2014-01-27 11:44 +1100
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-27 13:06 -0500
Re: Any quick, easy way to compare two images? Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-01-27 12:48 +0000
Re: Any quick, easy way to compare two images? Doug Anderson <ethelthelogremovethis@gmail.com> - 2014-01-27 05:49 -0800
Re: Any quick, easy way to compare two images? Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-01-26 12:05 -0500
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 17:08 +0000
Re: Any quick, easy way to compare two images? Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-01-26 12:27 -0500
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 17:37 +0000
Re: Any quick, easy way to compare two images? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-01-26 15:36 -0500
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 21:46 +0000
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-26 14:04 -0500
Re: Any quick, easy way to compare two images? Doug Anderson <ethelthelogremovethis@gmail.com> - 2014-01-26 12:16 -0800
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 21:47 +0000
Re: Any quick, easy way to compare two images? Doug Anderson <ethelthelogremovethis@gmail.com> - 2014-01-26 16:21 -0800
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-27 01:57 +0000
Re: Any quick, easy way to compare two images? Don Bruder <dakidd@sonic.net> - 2014-01-26 10:32 -0800
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 18:54 +0000
Re: Any quick, easy way to compare two images? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-01-26 15:40 -0500
Re: Any quick, easy way to compare two images? Savageduck <savageduck1@{REMOVESPAM}me.com> - 2014-01-26 13:30 -0800
Re: Any quick, easy way to compare two images? Don Bruder <dakidd@sonic.net> - 2014-01-26 15:06 -0800
Re: Any quick, easy way to compare two images? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-01-26 18:20 -0500
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 23:35 +0000
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-27 13:06 -0500
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-27 19:14 +0000
Re: Any quick, easy way to compare two images? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-01-27 23:18 -0500
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-28 04:27 +0000
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-29 14:01 -0500
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-29 14:01 -0500
Re: Any quick, easy way to compare two images? john hevelin <bwotte@panix.com> - 2014-01-27 01:19 +0000
Re: Any quick, easy way to compare two images? Don Bruder <dakidd@sonic.net> - 2014-01-26 18:28 -0800
Re: Any quick, easy way to compare two images? john hevelin <bwotte@panix.com> - 2014-01-28 02:26 +0000
Re: Any quick, easy way to compare two images? Don Bruder <dakidd@sonic.net> - 2014-01-28 06:35 -0800
Re: Any quick, easy way to compare two images? dorayme <do_ray_me@bigpond.com> - 2014-01-27 10:55 +1100
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-25 22:10 -0500
Re: Any quick, easy way to compare two images? Doug Anderson <ethelthelogremovethis@gmail.com> - 2014-01-25 21:41 -0800
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-26 14:04 -0500
Re: Any quick, easy way to compare two images? Jolly Roger <jollyroger@pobox.com> - 2014-01-26 03:13 +0000
Re: Any quick, easy way to compare two images? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-01-25 17:30 -0500
Re: Any quick, easy way to compare two images? john hevelin <bwotte@panix.com> - 2014-01-25 18:51 +0000
Re: Any quick, easy way to compare two images? Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-01-25 19:06 +0000
Re: Any quick, easy way to compare two images? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-01-25 15:37 -0500
Re: Any quick, easy way to compare two images? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-01-25 15:35 -0500
Re: Any quick, easy way to compare two images? nospam <nospam@nospam.invalid> - 2014-01-23 22:06 -0500
Page 2 of 8 — ← Prev page 1 [2] 3 4 5 6 7 8 Next page →
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2014-01-23 20:46 +0000 |
| Message-ID | <bkddcuFqs2hU1@mid.individual.net> |
| In reply to | #55220 |
On 2014-01-23, Don Bruder <dakidd@sonic.net> wrote: > > Long story short, I'm messing with an app to assemble a stream of webcam > images into a crude stop-motion movie. > > Since the images may arrive at irregular intervals, I'd like to be able > to do something similar to this: > [snip] > > Where "MAGIC" needs to be a routine that returns a YES/NO to the > question "Is NewImage the same as PreviousImage"? I use motiontrack for this type of "motion detection" in my hand-built home security system with various network cameras. It's quite handy: <http://motiontrack.sourceforge.net> -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR
[toc] | [prev] | [next] | [standalone]
| From | Lewis <g.kreme@gmail.com.dontsendmecopies> |
|---|---|
| Date | 2014-01-23 23:19 +0000 |
| Message-ID | <slrnle38sp.1qmp.g.kreme@amelia.local> |
| In reply to | #55220 |
In message <lbrnpr$q5o$1@dont-email.me> Don Bruder <dakidd@sonic.net> wrote: > Long story short, I'm messing with an app to assemble a stream of webcam > images into a crude stop-motion movie. Since you only care if the images are actually the same image, a simple CRC, XOR, or md5 hash of the files would probably be easiest. > if (MAGIC) if (md5(image1) != md5(iamge2) Heck, if the images are compressed (jpegs), you can probably be safe 99% of the time just by checking the files size. -- The fact that Bob and John are married does nothing to diminish anyone else's marriage any more than a black woman marrying a white man, a Jew marrying a Catholic, or an ugly Lyle marrying a Pretty Woman
[toc] | [prev] | [next] | [standalone]
| From | Alan Browne <alan.browne@FreelunchVideotron.ca> |
|---|---|
| Date | 2014-01-23 18:38 -0500 |
| Message-ID | <2ridnduo-M1jOnzPnZ2dnUVZ8kmdnZ2d@giganews.com> |
| In reply to | #55233 |
On 2014.01.23, 18:19 , Lewis wrote:
> In message <lbrnpr$q5o$1@dont-email.me>
> Don Bruder <dakidd@sonic.net> wrote:
>
>> Long story short, I'm messing with an app to assemble a stream of webcam
>> images into a crude stop-motion movie.
>
> Since you only care if the images are actually the same image, a simple
> CRC, XOR, or md5 hash of the files would probably be easiest.
>
>> if (MAGIC)
>
> if (md5(image1) != md5(iamge2)
No. See my reply to Doug.
>
> Heck, if the images are compressed (jpegs), you can probably be safe 99%
> of the time just by checking the files size.
No. As above.
--
“Everybody has a plan until they get punched in the face.”
- Mike Tyson
[toc] | [prev] | [next] | [standalone]
| From | Lewis <g.kreme@gmail.com.dontsendmecopies> |
|---|---|
| Date | 2014-01-24 00:49 +0000 |
| Message-ID | <slrnle3e4m.1tpe.g.kreme@amelia.local> |
| In reply to | #55238 |
In message <2ridnduo-M1jOnzPnZ2dnUVZ8kmdnZ2d@giganews.com> Alan Browne <alan.browne@FreelunchVideotron.ca> wrote: > On 2014.01.23, 18:19 , Lewis wrote: >> In message <lbrnpr$q5o$1@dont-email.me> >> Don Bruder <dakidd@sonic.net> wrote: >> >>> Long story short, I'm messing with an app to assemble a stream of webcam >>> images into a crude stop-motion movie. >> >> Since you only care if the images are actually the same image, a simple >> CRC, XOR, or md5 hash of the files would probably be easiest. >> >>> if (MAGIC) >> >> if (md5(image1) != md5(iamge2) > No. See my reply to Doug. I read what Doug wants, not what you assumed he wanted. -- Spontaneity has its time and place.
[toc] | [prev] | [next] | [standalone]
| From | Alan Browne <alan.browne@FreelunchVideotron.ca> |
|---|---|
| Date | 2014-01-23 19:59 -0500 |
| Message-ID | <rqGdnQNr_N5qJ3zPnZ2dnUVZ8umdnZ2d@giganews.com> |
| In reply to | #55248 |
On 2014.01.23, 19:49 , Lewis wrote:
> In message <2ridnduo-M1jOnzPnZ2dnUVZ8kmdnZ2d@giganews.com>
> Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:
>> On 2014.01.23, 18:19 , Lewis wrote:
>>> In message <lbrnpr$q5o$1@dont-email.me>
>>> Don Bruder <dakidd@sonic.net> wrote:
>>>
>>>> Long story short, I'm messing with an app to assemble a stream of webcam
>>>> images into a crude stop-motion movie.
>>>
>>> Since you only care if the images are actually the same image, a simple
>>> CRC, XOR, or md5 hash of the files would probably be easiest.
>>>
>>>> if (MAGIC)
>>>
>>> if (md5(image1) != md5(iamge2)
>
>> No. See my reply to Doug.
>
> I read what Doug wants, not what you assumed he wanted.
If I'm wrong then for 10000 frames in he'll get 10000 frames out.
--
“Everybody has a plan until they get punched in the face.”
- Mike Tyson
[toc] | [prev] | [next] | [standalone]
| From | Doug Anderson <ethelthelogremovethis@gmail.com> |
|---|---|
| Date | 2014-01-23 15:25 -0800 |
| Message-ID | <xwlhy6jn6u.fsf@ethel.the.log> |
| In reply to | #55220 |
Don Bruder <dakidd@sonic.net> writes:
> Long story short, I'm messing with an app to assemble a stream of webcam
> images into a crude stop-motion movie.
>
> Since the images may arrive at irregular intervals, I'd like to be able
> to do something similar to this:
>
> NSImage *PreviousImage; // Global to the class
>
> -(NSImage *)getNewImage:(NSString *)ImageSourceURL
> {
> NSImage *NewImage = [self grabImageFrom:ImageSourceURL];
> if (MAGIC)
> {
> // Yes, it's a new image
> if (PreviousImage)
> [PreviousImage release]; // Dump the old one, if any
> PreviousImage = [NewImage copy]; // replace with new one
> return NewImage; // and send the new one back to caller
> }
> else
> // Nope, image hasn't changed.
> return nil;
> }
>
> Where "MAGIC" needs to be a routine that returns a YES/NO to the
> question "Is NewImage the same as PreviousImage"?
>
> Is there a reasonably painless cocoa/core foundation way to do this, or
> am I stuck going right down onto the metal and doing a pixel-by-pixel
> comparison "by hand"?
>
> From what I've managed to find in the various cocoa docs, it *LOOKS* as
> though the "compare" type methods I can spot decide on equality by
> saying "Is this *POINTER* to an NSImage the same as this *OTHER POINTER*
> to an NSImage?", without actually looking at the images themselves -
> only the pointers to them. Which makes it look as though, should I
> assign two identical images to two different NSImages, they'll compare
> "not the same", despite the fact that they're identical. Or am I
> mis-reading things?
The shell command "diff" can be harnessed to do what you want.
diff <file 1> <file 2>
will return nothing if the files are identical (as binary files) and
will return a message telling you they differ (if they differ).
[toc] | [prev] | [next] | [standalone]
| From | Alan Browne <alan.browne@FreelunchVideotron.ca> |
|---|---|
| Date | 2014-01-23 18:37 -0500 |
| Message-ID | <2ridndio-M0kOnzPnZ2dnUVZ8kmdnZ2d@giganews.com> |
| In reply to | #55234 |
On 2014.01.23, 18:25 , Doug Anderson wrote:
> diff <file 1> <file 2>
>
> will return nothing if the files are identical (as binary files) and
> will return a message telling you they differ (if they differ).
Useless for sequential (or series of) frames that are "identical" from a
human vision POV as there will be differences due to noise or hardly
visible illumination changes/variance.
--
“Everybody has a plan until they get punched in the face.”
- Mike Tyson
[toc] | [prev] | [next] | [standalone]
| From | Doug Anderson <ethelthelogremovethis@gmail.com> |
|---|---|
| Date | 2014-01-23 16:05 -0800 |
| Message-ID | <2fd2jijlbb.fsf@ethel.the.log> |
| In reply to | #55237 |
Alan Browne <alan.browne@FreelunchVideotron.ca> writes: > On 2014.01.23, 18:25 , Doug Anderson wrote: > > > diff <file 1> <file 2> > > > > will return nothing if the files are identical (as binary files) and > > will return a message telling you they differ (if they differ). > > Useless for sequential (or series of) frames that are "identical" from > a human vision POV as there will be differences due to noise or hardly > visible illumination changes/variance. Correct. But useful for what I understand the poster to be asking for (a way to determine if the _files_ were identical, not to determine whether the images would be identical to the casual observer).
[toc] | [prev] | [next] | [standalone]
| From | Alan Browne <alan.browne@FreelunchVideotron.ca> |
|---|---|
| Date | 2014-01-23 19:47 -0500 |
| Message-ID | <Lcudnbvj4oa5JXzPnZ2dnUVZ8oOdnZ2d@giganews.com> |
| In reply to | #55241 |
On 2014.01.23, 19:05 , Doug Anderson wrote:
> Alan Browne <alan.browne@FreelunchVideotron.ca> writes:
>
>> On 2014.01.23, 18:25 , Doug Anderson wrote:
>>
>>> diff <file 1> <file 2>
>>>
>>> will return nothing if the files are identical (as binary files) and
>>> will return a message telling you they differ (if they differ).
>>
>> Useless for sequential (or series of) frames that are "identical" from
>> a human vision POV as there will be differences due to noise or hardly
>> visible illumination changes/variance.
>
> Correct.
>
> But useful for what I understand the poster to be asking for (a way to
> determine if the _files_ were identical, not to determine whether the
> images would be identical to the casual observer).
My understanding is he wants to make a sequence of meaningfully
different (to observers) images.
--
“Everybody has a plan until they get punched in the face.”
- Mike Tyson
[toc] | [prev] | [next] | [standalone]
| From | Doug Anderson <ethelthelogremovethis@gmail.com> |
|---|---|
| Date | 2014-01-23 17:10 -0800 |
| Message-ID | <161tzyjibp.fsf@ethel.the.log> |
| In reply to | #55246 |
Alan Browne <alan.browne@FreelunchVideotron.ca> writes: > On 2014.01.23, 19:05 , Doug Anderson wrote: > > Alan Browne <alan.browne@FreelunchVideotron.ca> writes: > > > >> On 2014.01.23, 18:25 , Doug Anderson wrote: > >> > >>> diff <file 1> <file 2> > >>> > >>> will return nothing if the files are identical (as binary files) and > >>> will return a message telling you they differ (if they differ). > >> > >> Useless for sequential (or series of) frames that are "identical" from > >> a human vision POV as there will be differences due to noise or hardly > >> visible illumination changes/variance. > > > > Correct. > > > > But useful for what I understand the poster to be asking for (a way to > > determine if the _files_ were identical, not to determine whether the > > images would be identical to the casual observer). > > My understanding is he wants to make a sequence of meaningfully > different (to observers) images. No. He wants to check to see if he's been sent the same image file as he got previously, so he can throw it out in that case. At least that is what he says he wants, so I'll choose to believe him.
[toc] | [prev] | [next] | [standalone]
| From | Alan Browne <alan.browne@FreelunchVideotron.ca> |
|---|---|
| Date | 2014-01-24 17:42 -0500 |
| Message-ID | <5cKdnS2-vfr0cX_PnZ2dnUVZ_oSdnZ2d@giganews.com> |
| In reply to | #55251 |
On 2014.01.23, 20:10 , Doug Anderson wrote:
> Alan Browne <alan.browne@FreelunchVideotron.ca> writes:
>
>> On 2014.01.23, 19:05 , Doug Anderson wrote:
>>> Alan Browne <alan.browne@FreelunchVideotron.ca> writes:
>>>
>>>> On 2014.01.23, 18:25 , Doug Anderson wrote:
>>>>
>>>>> diff <file 1> <file 2>
>>>>>
>>>>> will return nothing if the files are identical (as binary files) and
>>>>> will return a message telling you they differ (if they differ).
>>>>
>>>> Useless for sequential (or series of) frames that are "identical" from
>>>> a human vision POV as there will be differences due to noise or hardly
>>>> visible illumination changes/variance.
>>>
>>> Correct.
>>>
>>> But useful for what I understand the poster to be asking for (a way to
>>> determine if the _files_ were identical, not to determine whether the
>>> images would be identical to the casual observer).
>>
>> My understanding is he wants to make a sequence of meaningfully
>> different (to observers) images.
>
> No. He wants to check to see if he's been sent the same image file as
> he got previously, so he can throw it out in that case.
>
> At least that is what he says he wants, so I'll choose to believe him.
Here are the key statements from the OP in the OP.
1) ... I'm messing with an app to assemble a stream of webcam
images into a crude stop-motion movie.
NOTE: _images_ are frames. 1 frame per file (like a JPG) or 10000
like a video clip.
2) Where "MAGIC" needs to be a routine that returns a YES/NO to the
question "Is NewImage the same as PreviousImage"?
See NOTE above.
Since all images contain random dynamic range noise regardless of how
static the scene, the function Magic will return true ("different")
every time since the files cannot be anything but different in content.
--
“Everybody has a plan until they get punched in the face.”
- Mike Tyson
[toc] | [prev] | [next] | [standalone]
| From | Doug Anderson <ethelthelogremovethis@gmail.com> |
|---|---|
| Date | 2014-01-24 16:42 -0800 |
| Message-ID | <ecfvocdh8s.fsf@ethel.the.log> |
| In reply to | #55292 |
Alan Browne <alan.browne@FreelunchVideotron.ca> writes:
> On 2014.01.23, 20:10 , Doug Anderson wrote:
> > Alan Browne <alan.browne@FreelunchVideotron.ca> writes:
> >
> >> On 2014.01.23, 19:05 , Doug Anderson wrote:
> >>> Alan Browne <alan.browne@FreelunchVideotron.ca> writes:
> >>>
> >>>> On 2014.01.23, 18:25 , Doug Anderson wrote:
> >>>>
> >>>>> diff <file 1> <file 2>
> >>>>>
> >>>>> will return nothing if the files are identical (as binary files) and
> >>>>> will return a message telling you they differ (if they differ).
> >>>>
> >>>> Useless for sequential (or series of) frames that are "identical" from
> >>>> a human vision POV as there will be differences due to noise or hardly
> >>>> visible illumination changes/variance.
> >>>
> >>> Correct.
> >>>
> >>> But useful for what I understand the poster to be asking for (a way to
> >>> determine if the _files_ were identical, not to determine whether the
> >>> images would be identical to the casual observer).
> >>
> >> My understanding is he wants to make a sequence of meaningfully
> >> different (to observers) images.
> >
> > No. He wants to check to see if he's been sent the same image file as
> > he got previously, so he can throw it out in that case.
> >
> > At least that is what he says he wants, so I'll choose to believe him.
>
> Here are the key statements from the OP in the OP.
>
> 1) ... I'm messing with an app to assemble a stream of webcam
> images into a crude stop-motion movie.
>
> NOTE: _images_ are frames. 1 frame per file (like a JPG) or 10000
> like a video clip.
>
> 2) Where "MAGIC" needs to be a routine that returns a YES/NO to the
> question "Is NewImage the same as PreviousImage"?
>
> See NOTE above.
>
> Since all images contain random dynamic range noise regardless of how
> static the scene, the function Magic will return true ("different")
> every time since the files cannot be anything but different in
> content.
I can't tell if you are willfully misunderstanding the poster, or if
you honestly don't understand him.
He has a situation where an image file gets sent regularly to his
computer. Due to the algorithm that sends that file to his computer,
sometimes the _same file_ is getting sent more than once.
He wants to identify this situation so as not to use the same data
multiple times.
I agree that he _could_ want to do what you thought he wanted to do,
but that isn't what he wants.
[toc] | [prev] | [next] | [standalone]
| From | Don Bruder <dakidd@sonic.net> |
|---|---|
| Date | 2014-01-24 20:08 -0800 |
| Message-ID | <lbvdbf$p2f$1@dont-email.me> |
| In reply to | #55303 |
In article <ecfvocdh8s.fsf@ethel.the.log>,
Doug Anderson <ethelthelogremovethis@gmail.com> wrote:
> Alan Browne <alan.browne@FreelunchVideotron.ca> writes:
>
> > On 2014.01.23, 20:10 , Doug Anderson wrote:
> > > Alan Browne <alan.browne@FreelunchVideotron.ca> writes:
> > >
> > >> On 2014.01.23, 19:05 , Doug Anderson wrote:
> > >>> Alan Browne <alan.browne@FreelunchVideotron.ca> writes:
> > >>>
> > >>>> On 2014.01.23, 18:25 , Doug Anderson wrote:
> > >>>>
> > >>>>> diff <file 1> <file 2>
> > >>>>>
> > >>>>> will return nothing if the files are identical (as binary files) and
> > >>>>> will return a message telling you they differ (if they differ).
> > >>>>
> > >>>> Useless for sequential (or series of) frames that are "identical" from
> > >>>> a human vision POV as there will be differences due to noise or hardly
> > >>>> visible illumination changes/variance.
> > >>>
> > >>> Correct.
> > >>>
> > >>> But useful for what I understand the poster to be asking for (a way to
> > >>> determine if the _files_ were identical, not to determine whether the
> > >>> images would be identical to the casual observer).
> > >>
> > >> My understanding is he wants to make a sequence of meaningfully
> > >> different (to observers) images.
> > >
> > > No. He wants to check to see if he's been sent the same image file as
> > > he got previously, so he can throw it out in that case.
> > >
> > > At least that is what he says he wants, so I'll choose to believe him.
> >
> > Here are the key statements from the OP in the OP.
> >
> > 1) ... I'm messing with an app to assemble a stream of webcam
> > images into a crude stop-motion movie.
> >
> > NOTE: _images_ are frames. 1 frame per file (like a JPG) or 10000
> > like a video clip.
> >
> > 2) Where "MAGIC" needs to be a routine that returns a YES/NO to the
> > question "Is NewImage the same as PreviousImage"?
> >
> > See NOTE above.
> >
> > Since all images contain random dynamic range noise regardless of how
> > static the scene, the function Magic will return true ("different")
> > every time since the files cannot be anything but different in
> > content.
>
> I can't tell if you are willfully misunderstanding the poster, or if
> you honestly don't understand him.
>
> He has a situation where an image file gets sent regularly to his
> computer. Due to the algorithm that sends that file to his computer,
> sometimes the _same file_ is getting sent more than once.
>
> He wants to identify this situation so as not to use the same data
> multiple times.
>
> I agree that he _could_ want to do what you thought he wanted to do,
> but that isn't what he wants.
Thank you, Doug. You were much kinder than I was about to be.
--
Security provided by Mssrs Smith and/or Wesson. Brought to you by the letter Q
[toc] | [prev] | [next] | [standalone]
| From | Alan Browne <alan.browne@FreelunchVideotron.ca> |
|---|---|
| Date | 2014-01-25 10:54 -0500 |
| Message-ID | <r_WdnVC3yP22Q37PnZ2dnUVZ_uydnZ2d@giganews.com> |
| In reply to | #55309 |
On 2014.01.24, 23:08 , Don Bruder wrote:
> In article <ecfvocdh8s.fsf@ethel.the.log>,
> Doug Anderson <ethelthelogremovethis@gmail.com> wrote:
>
>> Alan Browne <alan.browne@FreelunchVideotron.ca> writes:
>>
>>> On 2014.01.23, 20:10 , Doug Anderson wrote:
>>>> Alan Browne <alan.browne@FreelunchVideotron.ca> writes:
>>>>
>>>>> On 2014.01.23, 19:05 , Doug Anderson wrote:
>>>>>> Alan Browne <alan.browne@FreelunchVideotron.ca> writes:
>>>>>>
>>>>>>> On 2014.01.23, 18:25 , Doug Anderson wrote:
>>>>>>>
>>>>>>>> diff <file 1> <file 2>
>>>>>>>>
>>>>>>>> will return nothing if the files are identical (as binary files) and
>>>>>>>> will return a message telling you they differ (if they differ).
>>>>>>>
>>>>>>> Useless for sequential (or series of) frames that are "identical" from
>>>>>>> a human vision POV as there will be differences due to noise or hardly
>>>>>>> visible illumination changes/variance.
>>>>>>
>>>>>> Correct.
>>>>>>
>>>>>> But useful for what I understand the poster to be asking for (a way to
>>>>>> determine if the _files_ were identical, not to determine whether the
>>>>>> images would be identical to the casual observer).
>>>>>
>>>>> My understanding is he wants to make a sequence of meaningfully
>>>>> different (to observers) images.
>>>>
>>>> No. He wants to check to see if he's been sent the same image file as
>>>> he got previously, so he can throw it out in that case.
>>>>
>>>> At least that is what he says he wants, so I'll choose to believe him.
>>>
>>> Here are the key statements from the OP in the OP.
>>>
>>> 1) ... I'm messing with an app to assemble a stream of webcam
>>> images into a crude stop-motion movie.
>>>
>>> NOTE: _images_ are frames. 1 frame per file (like a JPG) or 10000
>>> like a video clip.
>>>
>>> 2) Where "MAGIC" needs to be a routine that returns a YES/NO to the
>>> question "Is NewImage the same as PreviousImage"?
>>>
>>> See NOTE above.
>>>
>>> Since all images contain random dynamic range noise regardless of how
>>> static the scene, the function Magic will return true ("different")
>>> every time since the files cannot be anything but different in
>>> content.
>>
>> I can't tell if you are willfully misunderstanding the poster, or if
>> you honestly don't understand him.
>>
>> He has a situation where an image file gets sent regularly to his
>> computer. Due to the algorithm that sends that file to his computer,
>> sometimes the _same file_ is getting sent more than once.
>>
>> He wants to identify this situation so as not to use the same data
>> multiple times.
>>
>> I agree that he _could_ want to do what you thought he wanted to do,
>> but that isn't what he wants.
>
> Thank you, Doug. You were much kinder than I was about to be.
Next time state your problem more clearly.
An "image" (photography or video) is not a "file".
A "stream of webcam images" (your first sentence, OP) is not a "file".
--
“Everybody has a plan until they get punched in the face.”
- Mike Tyson
[toc] | [prev] | [next] | [standalone]
| From | JF Mezei <jfmezei.spamnot@vaxination.ca> |
|---|---|
| Date | 2014-01-25 15:31 -0500 |
| Message-ID | <52e41f3b$0$7129$c3e8da3$76a7c58f@news.astraweb.com> |
| In reply to | #55328 |
After reading some of the posts and discarding the usual insults: If the goal is to build a movie from all individual images procuded by the camera, then a raw comparison of bytes in the image file will be sufficient (although perhaps not the most efficient). Since every image produced will have some bit differences even in scenes that remain unchanged, then you can rely on raw comparision of data to determine that a new image has been generated. If the goal is to eliminate all static frames (for instance, make a movie of only when there is movement in the image and shorten/eliminate all times when there is none), then you need more complex algorythm to determine image changes not at the byte level but at the shape levels. If this is for security purposes, consider aslo the Hollywood scenarios where the thiefs hack into the camera and feed a static image to your server while they rob the premises.
[toc] | [prev] | [next] | [standalone]
| From | Don Bruder <dakidd@sonic.net> |
|---|---|
| Date | 2014-01-25 17:31 -0800 |
| Message-ID | <lc1ogb$h1d$1@dont-email.me> |
| In reply to | #55345 |
In article <52e41f3b$0$7129$c3e8da3$76a7c58f@news.astraweb.com>, JF Mezei <jfmezei.spamnot@vaxination.ca> wrote: > After reading some of the posts and discarding the usual insults: > > > If the goal is to build a movie from all individual images procuded by > the camera, then a raw comparison of bytes in the image file will be > sufficient (although perhaps not the most efficient). > > Since every image produced will have some bit differences even in scenes > that remain unchanged, then you can rely on raw comparision of data to > determine that a new image has been generated. Basically, yes, this is the whole point. The "final question" I wanted an answer to was "Is there something built into Cocoa that I can use for this, or do I have to roll my own?" If nothing in Cocoa, I'm quite capable of putting something together to handle it, but I was hoping that there was a built-in so I wouldn't have to. It looks like there isn't. My "hand-rolled" is right on the edge of being ready to test. I'll be tinkering with it tomorrow, most likely. > > > If the goal is to eliminate all static frames (for instance, make a > movie of only when there is movement in the image and shorten/eliminate > all times when there is none), then you need more complex algorythm to > determine image changes not at the byte level but at the shape levels. Such might be desirable, but for this project, it's simply not worth any extra effort. > > If this is for security purposes, consider aslo the Hollywood scenarios > where the thiefs hack into the camera and feed a static image to your > server while they rob the premises. Totally irrelevant for this project. -- Security provided by Mssrs Smith and/or Wesson. Brought to you by the letter Q
[toc] | [prev] | [next] | [standalone]
| From | Michael Vilain <vilain@NOspamcop.net> |
|---|---|
| Date | 2014-01-25 17:57 -0800 |
| Message-ID | <vilain-41D381.17575125012014@news.individual.net> |
| In reply to | #55379 |
In article <lc1ogb$h1d$1@dont-email.me>, Don Bruder <dakidd@sonic.net> wrote: > In article <52e41f3b$0$7129$c3e8da3$76a7c58f@news.astraweb.com>, > JF Mezei <jfmezei.spamnot@vaxination.ca> wrote: > > > After reading some of the posts and discarding the usual insults: > > > > > > If the goal is to build a movie from all individual images procuded by > > the camera, then a raw comparison of bytes in the image file will be > > sufficient (although perhaps not the most efficient). > > > > Since every image produced will have some bit differences even in scenes > > that remain unchanged, then you can rely on raw comparision of data to > > determine that a new image has been generated. > > Basically, yes, this is the whole point. The "final question" I wanted > an answer to was "Is there something built into Cocoa that I can use for > this, or do I have to roll my own?" > > If nothing in Cocoa, I'm quite capable of putting something together to > handle it, but I was hoping that there was a built-in so I wouldn't have > to. It looks like there isn't. My "hand-rolled" is right on the edge of > being ready to test. I'll be tinkering with it tomorrow, most likely. > > > > > > > If the goal is to eliminate all static frames (for instance, make a > > movie of only when there is movement in the image and shorten/eliminate > > all times when there is none), then you need more complex algorythm to > > determine image changes not at the byte level but at the shape levels. > > Such might be desirable, but for this project, it's simply not worth any > extra effort. > > > > > If this is for security purposes, consider aslo the Hollywood scenarios > > where the thiefs hack into the camera and feed a static image to your > > server while they rob the premises. > > Totally irrelevant for this project. Years and years ago, I worked for a company that did real-time image processing in hardware. Think of that satellite analysis hardware in the CIA from PATRIOT GAMES. With the camera fixed and frames coming in at regular intervals, it's not hard to do an XOR of the pixels. A certain percentage will change due to noise. You set the threshold on how much that is and everything over it is a keeper. And AFAIK, MacOS or any of it's core service like Quartz don't provide an image-compare service or framework. You've already got something ready to test, so I guess this topic is closed. [I plonked JF back in 2010. What took y'all so long?] -- DeeDee, don't press that button! DeeDee! NO! Dee... [I filter all Goggle Groups posts, so any reply may be automatically ignored]
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2014-01-26 03:09 +0000 |
| Message-ID | <bkjck6F3qa4U7@mid.individual.net> |
| In reply to | #55379 |
On 2014-01-26, Don Bruder <dakidd@sonic.net> wrote: > In article <52e41f3b$0$7129$c3e8da3$76a7c58f@news.astraweb.com>, > JF Mezei <jfmezei.spamnot@vaxination.ca> wrote: > >> After reading some of the posts and discarding the usual insults: >> >> If the goal is to build a movie from all individual images procuded by >> the camera, then a raw comparison of bytes in the image file will be >> sufficient (although perhaps not the most efficient). >> >> Since every image produced will have some bit differences even in scenes >> that remain unchanged, then you can rely on raw comparision of data to >> determine that a new image has been generated. > > Basically, yes, this is the whole point. The "final question" I wanted > an answer to was "Is there something built into Cocoa that I can use for > this, or do I have to roll my own?" > > If nothing in Cocoa, I'm quite capable of putting something together to > handle it, but I was hoping that there was a built-in so I wouldn't have > to. It looks like there isn't. My "hand-rolled" is right on the edge of > being ready to test. I'll be tinkering with it tomorrow, most likely. You would do yourself and everyone else a favor by better describing whether these so-called "duplicate images" are *exact* duplicates of the same image capture, or are distinct captures of the same scene. This distinction matters when considering comparisons. The motiontrack solution I mentioned in a previous reply is very useful for comparing two very similar yet distinctly different images to tell you how much of the image is different so that you can judge for yourself whether the image is different *enough* to take action. >> If the goal is to eliminate all static frames (for instance, make a >> movie of only when there is movement in the image and shorten/eliminate >> all times when there is none), then you need more complex algorythm to >> determine image changes not at the byte level but at the shape levels. > > Such might be desirable, but for this project, it's simply not worth any > extra effort. The motiontrack solution I mentioned makes it brain-dead easy to do. -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR
[toc] | [prev] | [next] | [standalone]
| From | JF Mezei <jfmezei.spamnot@vaxination.ca> |
|---|---|
| Date | 2014-01-25 23:02 -0500 |
| Message-ID | <52e488c6$0$46172$c3e8da3$3a1a2348@news.astraweb.com> |
| In reply to | #55400 |
On 14-01-25 22:09, Jolly Roger wrote: > You would do yourself and everyone else a favor by better describing > whether these so-called "duplicate images" are *exact* duplicates of the > same image capture, or are distinct captures of the same scene. This > distinction matters when considering comparisons. I understood his problem fine. Application accesses 1 image over and over again. But it doesn't know when the image was last updated. Consider an application that checks the file every 30 seconds, but camera updates image at random intervals. You want to know if a new image was created when you last checked. If the camera recreates the file on an Mac/OS-X system, there may be something you could do with fsevendsd (file system event deamon) which can notify an application when a file was created in a directory. Another way would be to rename a file (or delete it) after you have accessed it, and then check to see when the file is next created (indicating a new image). But this depends on hw image files are created on your system or whether your app gos out to fetch it on a remote system.
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2014-01-26 05:04 +0000 |
| Message-ID | <bkjjb0F55lbU2@mid.individual.net> |
| In reply to | #55412 |
On 2014-01-26, JF Mezei <jfmezei.spamnot@vaxination.ca> wrote: > On 14-01-25 22:09, Jolly Roger wrote: > >> You would do yourself and everyone else a favor by better describing >> whether these so-called "duplicate images" are *exact* duplicates of the >> same image capture, or are distinct captures of the same scene. This >> distinction matters when considering comparisons. > > I understood his problem fine. There was a distinct lack of information in the original post which led to a lot of discussion about said lack of information. Are you actually going to try to dispute what happened did happen now? -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR
[toc] | [prev] | [next] | [standalone]
Page 2 of 8 — ← Prev page 1 [2] 3 4 5 6 7 8 Next page →
Back to top | Article view | comp.sys.mac.system
csiph-web