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 3 of 8 — ← Prev page 1 2 [3] 4 5 6 7 8 Next page →
| From | Alan Browne <alan.browne@FreelunchVideotron.ca> |
|---|---|
| Date | 2014-01-25 10:58 -0500 |
| Message-ID | <r_WdnVO3yP2VQn7PnZ2dnUVZ_uydnZ2d@giganews.com> |
| In reply to | #55303 |
On 2014.01.24, 19:42 , Doug Anderson 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.
I'm just going by his original post where he asks about: "a stream of
images".
A stream of images is NOT individual files.
I'm very willing to say, "Yes, I misunderstood him."
But that's because his case was badly stated so pretty impossible to
know that he meant a hot fudge sundae and not a steak with mushrooms.
--
“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-25 10:29 -0800 |
| Message-ID | <6jy523synp.fsf@ethel.the.log> |
| In reply to | #55329 |
Alan Browne <alan.browne@FreelunchVideotron.ca> writes:
> On 2014.01.24, 19:42 , Doug Anderson 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.
>
> I'm just going by his original post where he asks about: "a stream of
> images".
>
> A stream of images is NOT individual files.
>
> I'm very willing to say, "Yes, I misunderstood him."
>
> But that's because his case was badly stated so pretty impossible to
> know that he meant a hot fudge sundae and not a steak with
> mushrooms.
If you say so. I understood him, and he had clarified the situation
several times before your post above.
Don't know if that was what you were intending, but to me it felt like
you were more interested in arguing with me than in reading what the
original poster had to say and offering assistance.
[toc] | [prev] | [next] | [standalone]
| From | Alan Browne <alan.browne@FreelunchVideotron.ca> |
|---|---|
| Date | 2014-01-25 13:39 -0500 |
| Message-ID | <k9CdnbH9-Zh_mXnPnZ2dnUVZ_rmdnZ2d@giganews.com> |
| In reply to | #55334 |
On 2014.01.25, 13:29 , Doug Anderson wrote:
> Alan Browne <alan.browne@FreelunchVideotron.ca> writes:
>
>> On 2014.01.24, 19:42 , Doug Anderson 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.
>>
>> I'm just going by his original post where he asks about: "a stream of
>> images".
>>
>> A stream of images is NOT individual files.
>>
>> I'm very willing to say, "Yes, I misunderstood him."
>>
>> But that's because his case was badly stated so pretty impossible to
>> know that he meant a hot fudge sundae and not a steak with
>> mushrooms.
>
> If you say so. I understood him, and he had clarified the situation
> several times before your post above.
>
> Don't know if that was what you were intending, but to me it felt like
> you were more interested in arguing with me than in reading what the
> original poster had to say and offering assistance.
Not at all.
--
“Everybody has a plan until they get punched in the face.”
- Mike Tyson
[toc] | [prev] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2014-01-25 13:45 -0500 |
| Message-ID | <250120141345247892%nospam@nospam.invalid> |
| In reply to | #55334 |
In article <6jy523synp.fsf@ethel.the.log>, Doug Anderson
<ethelthelogremovethis@gmail.com> wrote:
> > >> 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.
> >
> > I'm just going by his original post where he asks about: "a stream of
> > images".
> >
> > A stream of images is NOT individual files.
> >
> > I'm very willing to say, "Yes, I misunderstood him."
> >
> > But that's because his case was badly stated so pretty impossible to
> > know that he meant a hot fudge sundae and not a steak with
> > mushrooms.
>
> If you say so. I understood him, and he had clarified the situation
> several times before your post above.
>
> Don't know if that was what you were intending, but to me it felt like
> you were more interested in arguing with me than in reading what the
> original poster had to say and offering assistance.
he did not clearly state what he wanted. several people assumed he
meant content, not file.
if he wants to know it's a different *file*, all that needs to be done
is compare the creation date. there's no reason to bother with
comparing pixels.
since he said he wanted to compare the pixels, it could only have meant
he was interested in the *content*.
then he says he doesn't want that at all.
[toc] | [prev] | [next] | [standalone]
| From | Doug Anderson <ethelthelogremovethis@gmail.com> |
|---|---|
| Date | 2014-01-25 13:27 -0800 |
| Message-ID | <vey523eopt.fsf@ethel.the.log> |
| In reply to | #55336 |
nospam <nospam@nospam.invalid> writes:
> In article <6jy523synp.fsf@ethel.the.log>, Doug Anderson
> <ethelthelogremovethis@gmail.com> wrote:
>
> > > >> 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.
> > >
> > > I'm just going by his original post where he asks about: "a stream of
> > > images".
> > >
> > > A stream of images is NOT individual files.
> > >
> > > I'm very willing to say, "Yes, I misunderstood him."
> > >
> > > But that's because his case was badly stated so pretty impossible to
> > > know that he meant a hot fudge sundae and not a steak with
> > > mushrooms.
> >
> > If you say so. I understood him, and he had clarified the situation
> > several times before your post above.
> >
> > Don't know if that was what you were intending, but to me it felt like
> > you were more interested in arguing with me than in reading what the
> > original poster had to say and offering assistance.
>
> he did not clearly state what he wanted. several people assumed he
> meant content, not file.
>
> if he wants to know it's a different *file*, all that needs to be done
> is compare the creation date. there's no reason to bother with
> comparing pixels.
That might work, but it might not. Depending on the protocal by which
the file was tranmitted to his computer, the creation dates could be
different even though the contents of the files are identical.
[toc] | [prev] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2014-01-25 16:30 -0500 |
| Message-ID | <250120141630000472%nospam@nospam.invalid> |
| In reply to | #55356 |
In article <vey523eopt.fsf@ethel.the.log>, Doug Anderson <ethelthelogremovethis@gmail.com> wrote: > > if he wants to know it's a different *file*, all that needs to be done > > is compare the creation date. there's no reason to bother with > > comparing pixels. > > That might work, but it might not. Depending on the protocal by which > the file was tranmitted to his computer, the creation dates could be > different even though the contents of the files are identical. if the creation date was changed (or any other attribute or metadata), then it's not an exact copy.
[toc] | [prev] | [next] | [standalone]
| From | Doug Anderson <ethelthelogremovethis@gmail.com> |
|---|---|
| Date | 2014-01-25 13:33 -0800 |
| Message-ID | <yxmwijeogq.fsf@ethel.the.log> |
| In reply to | #55357 |
nospam <nospam@nospam.invalid> writes: > In article <vey523eopt.fsf@ethel.the.log>, Doug Anderson > <ethelthelogremovethis@gmail.com> wrote: > > > > if he wants to know it's a different *file*, all that needs to be done > > > is compare the creation date. there's no reason to bother with > > > comparing pixels. > > > > That might work, but it might not. Depending on the protocal by which > > the file was tranmitted to his computer, the creation dates could be > > different even though the contents of the files are identical. > > if the creation date was changed (or any other attribute or metadata), > then it's not an exact copy. You want to add anything else to opinions you express that betray you know nothing about what you are talking about? If I have a file I made yesterday (call it file1), I can make a copy today and call it file2. The creation date of file1 will be yesterday and of file2 will be today. But if I do a diff or a cmp on file1 and file2, they will be shown to be identical as they contaion the _same_ data on a byte-by-byte basis. Just try it if you don't believe me - don't waste 30 posts saying black is white.
[toc] | [prev] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2014-01-25 16:52 -0500 |
| Message-ID | <250120141652210942%nospam@nospam.invalid> |
| In reply to | #55358 |
In article <yxmwijeogq.fsf@ethel.the.log>, Doug Anderson <ethelthelogremovethis@gmail.com> wrote: > > > > if he wants to know it's a different *file*, all that needs to be done > > > > is compare the creation date. there's no reason to bother with > > > > comparing pixels. > > > > > > That might work, but it might not. Depending on the protocal by which > > > the file was tranmitted to his computer, the creation dates could be > > > different even though the contents of the files are identical. > > > > if the creation date was changed (or any other attribute or metadata), > > then it's not an exact copy. > > You want to add anything else to opinions you express that betray you > know nothing about what you are talking about? > > If I have a file I made yesterday (call it file1), I can make a copy > today and call it file2. The creation date of file1 will be yesterday > and of file2 will be today. no it won't. it is unchanged. > But if I do a diff or a cmp on file1 and file2, they will be shown to > be identical as they contaion the _same_ data on a byte-by-byte basis. > > Just try it if you don't believe me - don't waste 30 posts saying black > is white. i did and you're once again, wrong. tested on snow leopard and mountain lion: select a file or folder (doesn't matter), command-d, and everything is the same, including create/mod dates.
[toc] | [prev] | [next] | [standalone]
| From | JF Mezei <jfmezei.spamnot@vaxination.ca> |
|---|---|
| Date | 2014-01-25 17:31 -0500 |
| Message-ID | <52e43b57$0$12701$c3e8da3$69010069@news.astraweb.com> |
| In reply to | #55360 |
On 14-01-25 16:52, nospam wrote: > tested on snow leopard and mountain lion: select a file or folder > (doesn't matter), command-d, and everything is the same, including > create/mod dates. cat original.dat > copy.dat Copy.dat will have identical data, but different metadate such as creation date.
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2014-01-25 22:35 +0000 |
| Message-ID | <bkishmF11p0U1@mid.individual.net> |
| In reply to | #55362 |
On 2014-01-25, JF Mezei <jfmezei.spamnot@vaxination.ca> wrote: > On 14-01-25 16:52, nospam wrote: > >> tested on snow leopard and mountain lion: select a file or folder >> (doesn't matter), command-d, and everything is the same, including >> create/mod dates. > > cat original.dat > copy.dat > > Copy.dat will have identical data, but different metadate such as > creation date. mr.know-it-all's got to be one of THE most thick-headed individuals I think I've ever seen. What a fucking dolt. -- 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 | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2014-01-25 17:49 -0500 |
| Message-ID | <250120141749568218%nospam@nospam.invalid> |
| In reply to | #55363 |
In article <bkishmF11p0U1@mid.individual.net>, Jolly Roger <jollyroger@pobox.com> wrote: > >> tested on snow leopard and mountain lion: select a file or folder > >> (doesn't matter), command-d, and everything is the same, including > >> create/mod dates. > > > > cat original.dat > copy.dat > > > > Copy.dat will have identical data, but different metadate such as > > creation date. > > mr.know-it-all's got to be one of THE most thick-headed individuals I > think I've ever seen. What a fucking dolt. once again, you prove yourself to be an idiot. i just proved that a copy of a file has the same create date.
[toc] | [prev] | [next] | [standalone]
| From | Tom Stiller <clusterfux.upmon@gmail.com> |
|---|---|
| Date | 2014-01-25 22:55 +0000 |
| Message-ID | <bkitmlF199bU1@mid.individual.net> |
| In reply to | #55365 |
On 2014-01-25, nospam <nospam@nospam.invalid> wrote: > In article <bkishmF11p0U1@mid.individual.net>, Jolly Roger ><jollyroger@pobox.com> wrote: > >> >> tested on snow leopard and mountain lion: select a file or folder >> >> (doesn't matter), command-d, and everything is the same, including >> >> create/mod dates. >> > >> > cat original.dat > copy.dat >> > >> > Copy.dat will have identical data, but different metadate such as >> > creation date. >> >> mr.know-it-all's got to be one of THE most thick-headed individuals I >> think I've ever seen. What a fucking dolt. > > once again, you prove yourself to be an idiot. > > i just proved that a copy of a file has the same create date. Nospam,my ass; seems like all spam to me.
[toc] | [prev] | [next] | [standalone]
| From | JF Mezei <jfmezei.spamnot@vaxination.ca> |
|---|---|
| Date | 2014-01-25 18:33 -0500 |
| Message-ID | <52e449dc$0$51479$c3e8da3$eb767761@news.astraweb.com> |
| In reply to | #55365 |
On 14-01-25 17:49, nospam wrote: > i just proved that a copy of a file has the same create date. Not all copies are created equal. You can't state that unless you know how the copy is being made. I provided 2 examples where this is not the case.
[toc] | [prev] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2014-01-25 19:42 -0500 |
| Message-ID | <250120141942323554%nospam@nospam.invalid> |
| In reply to | #55367 |
In article <52e449dc$0$51479$c3e8da3$eb767761@news.astraweb.com>, JF Mezei <jfmezei.spamnot@vaxination.ca> wrote: > > i just proved that a copy of a file has the same create date. > > Not all copies are created equal. > > You can't state that unless you know how the copy is being made. I > provided 2 examples where this is not the case. you didn't make a copy, you cat'ted the output of one file into a new file. the contents may be the same (for text, anyway, it won't work so well for binary), but the metadata is not, therefore it's not a copy. you could re-save a jpeg in photoshop and call it a copy, but jpeg is lossy and the copy will not be the same as the original. when someone makes a copy of something, they expect it to be identical. duplicating a file on the mac will be.
[toc] | [prev] | [next] | [standalone]
| From | Don Bruder <dakidd@sonic.net> |
|---|---|
| Date | 2014-01-25 17:38 -0800 |
| Message-ID | <lc1otu$h1d$3@dont-email.me> |
| In reply to | #55371 |
In article <250120141942323554%nospam@nospam.invalid>, nospam <nospam@nospam.invalid> wrote: > In article <52e449dc$0$51479$c3e8da3$eb767761@news.astraweb.com>, JF > Mezei <jfmezei.spamnot@vaxination.ca> wrote: > > > > i just proved that a copy of a file has the same create date. > > > > Not all copies are created equal. > > > > You can't state that unless you know how the copy is being made. I > > provided 2 examples where this is not the case. > > you didn't make a copy, you cat'ted the output of one file into a new > file. the contents may be the same (for text, anyway, it won't work so > well for binary), but the metadata is not, therefore it's not a copy. > > you could re-save a jpeg in photoshop and call it a copy, but jpeg is > lossy and the copy will not be the same as the original. > > when someone makes a copy of something, they expect it to be identical. > duplicating a file on the mac will be. You really are arguing just for the sake of arguing, aren't you? There's no other explanation for your attempting to nit-pick things to death when it's been stated QUITE clearly what I'm interested in multiple times, in multiple ways. Time to dump you into the bozo-bin - you've demonstrated amply that's where you belong. Buh-bye... -- Security provided by Mssrs Smith and/or Wesson. Brought to you by the letter Q
[toc] | [prev] | [next] | [standalone]
| From | JF Mezei <jfmezei.spamnot@vaxination.ca> |
|---|---|
| Date | 2014-01-25 22:50 -0500 |
| Message-ID | <52e4861b$0$45923$c3e8da3$88b277c5@news.astraweb.com> |
| In reply to | #55382 |
To the OP: The information that is missing from your question is how the image files are tranmitted/received to the disk that your application is reading. or does your app go out and grab the data from the remote camera at regular intervals ? If so, what protocol is used ? Also, what triggers the camera to capture an image (and at what sort of intervals, 1 per minute ? 1 per second ? multiple per second ? )
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2014-01-26 02:49 +0000 |
| Message-ID | <bkjbdsF3qa4U2@mid.individual.net> |
| In reply to | #55371 |
On 2014-01-26, nospam <nospam@nospam.invalid> wrote: > In article <52e449dc$0$51479$c3e8da3$eb767761@news.astraweb.com>, JF > Mezei <jfmezei.spamnot@vaxination.ca> wrote: > >> > i just proved that a copy of a file has the same create date. >> >> Not all copies are created equal. >> >> You can't state that unless you know how the copy is being made. I >> provided 2 examples where this is not the case. > > you didn't make a copy, you cat'ted the output of one file into a new > file. the contents may be the same (for text, anyway, it won't work so > well for binary), but the metadata is not, therefore it's not a copy. > > you could re-save a jpeg in photoshop and call it a copy, but jpeg is > lossy and the copy will not be the same as the original. > > when someone makes a copy of something, they expect it to be identical. > duplicating a file on the mac will be. One might be fooled into thinking you are that naive to think that all copies are the same in the real world, but experience tells us that you are just being moronically disingenuous in a futile attempt to defend the utterly indefensible position you've taken. You are, in a word, lame, Betty. -- 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-26 14:21 +0000 |
| Message-ID | <slrnlea6fk.4tm.g.kreme@amelia.local> |
| In reply to | #55395 |
In message <bkjbdsF3qa4U2@mid.individual.net> Jolly Roger <jollyroger@pobox.com> wrote: > On 2014-01-26, nospam <nospam@nospam.invalid> wrote: >> In article <52e449dc$0$51479$c3e8da3$eb767761@news.astraweb.com>, JF >> Mezei <jfmezei.spamnot@vaxination.ca> wrote: >> >>> > i just proved that a copy of a file has the same create date. >>> >>> Not all copies are created equal. >>> >>> You can't state that unless you know how the copy is being made. I >>> provided 2 examples where this is not the case. >> >> you didn't make a copy, you cat'ted the output of one file into a new >> file. the contents may be the same (for text, anyway, it won't work so >> well for binary), but the metadata is not, therefore it's not a copy. >> >> you could re-save a jpeg in photoshop and call it a copy, but jpeg is >> lossy and the copy will not be the same as the original. >> >> when someone makes a copy of something, they expect it to be identical. >> duplicating a file on the mac will be. > One might be fooled into thinking you are that naive to think that all > copies are the same in the real world, but experience tells us that you > are just being moronically disingenuous in a futile attempt to defend > the utterly indefensible position you've taken. It's a new low, and that's saying something. Here's a very common example for me, using rsync to copy files to a Windows machine does not preserve the date and time. In fact, often making network copies does not preserve the date and time. Also, from reading more of the OP's posts, it seemed like he was actually getting something like an NSImage glob of data than an actual file. > You are, in a word, lame, Betty. He's a fucking idiot is what he is. -- I WAS NOT TOUCHED "THERE" BY AN ANGEL Bart chalkboard Ep. BABF14
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2014-01-26 15:17 +0000 |
| Message-ID | <bkkn8cFccv0U2@mid.individual.net> |
| In reply to | #55424 |
On 2014-01-26, Lewis <g.kreme@gmail.com.dontsendmecopies> wrote: > In message <bkjbdsF3qa4U2@mid.individual.net> > Jolly Roger <jollyroger@pobox.com> wrote: >> On 2014-01-26, nospam <nospam@nospam.invalid> wrote: >>> In article <52e449dc$0$51479$c3e8da3$eb767761@news.astraweb.com>, JF >>> Mezei <jfmezei.spamnot@vaxination.ca> wrote: >>> >>>> > i just proved that a copy of a file has the same create date. >>>> >>>> Not all copies are created equal. >>>> >>>> You can't state that unless you know how the copy is being made. I >>>> provided 2 examples where this is not the case. >>> >>> you didn't make a copy, you cat'ted the output of one file into a new >>> file. the contents may be the same (for text, anyway, it won't work so >>> well for binary), but the metadata is not, therefore it's not a copy. >>> >>> you could re-save a jpeg in photoshop and call it a copy, but jpeg is >>> lossy and the copy will not be the same as the original. >>> >>> when someone makes a copy of something, they expect it to be identical. >>> duplicating a file on the mac will be. > >> One might be fooled into thinking you are that naive to think that all >> copies are the same in the real world, but experience tells us that you >> are just being moronically disingenuous in a futile attempt to defend >> the utterly indefensible position you've taken. > > It's a new low, and that's saying something. > > Here's a very common example for me, using rsync to copy files to a > Windows machine does not preserve the date and time. In fact, often > making network copies does not preserve the date and time. Right. Anyone worth their salt who has used / programmed computers for any length of time in the real world will tell you file system metatadata (dates in particular) are often not a reliable method to determine file integrity. mr.know-it-all probably knows this as well - either that or he's really, really dumb. > Also, from reading more of the OP's posts, it seemed like he was > actually getting something like an NSImage glob of data than an actual > file. Perhaps. My take was that was just one potential avenue he was investigating. With so much uncertainty, it's no wonder we are having these conversations. It certainly doesn't help that mr.know-it-all-never-wrong is doing his best to throw stink bombs into the conversation and detract from its helpfulness at very turn. >> You are, in a word, lame, Betty. > > He's a fucking idiot is what he is. If he is to be judged by his actions, certainly. -- 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 | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2014-01-26 14:04 -0500 |
| Message-ID | <260120141404391164%nospam@nospam.invalid> |
| In reply to | #55426 |
In article <bkkn8cFccv0U2@mid.individual.net>, Jolly Roger <jollyroger@pobox.com> wrote: > > Here's a very common example for me, using rsync to copy files to a > > Windows machine does not preserve the date and time. In fact, often > > making network copies does not preserve the date and time. > > Right. Anyone worth their salt who has used / programmed computers for > any length of time in the real world will tell you file system > metatadata (dates in particular) are often not a reliable method to > determine file integrity. mr.know-it-all probably knows this as well - > either that or he's really, really dumb. i never said it was a way to determine file integrity. when you lie about what i say, it's clear you are just bashing. the create date is a very easy and convenient way to tell if one file is the same as another. obviously you have to use a proper copy method for it to work. if you use a copy method that does alter the create date, then either choose another way to compare files or fix the copy method. it's very simple, but apparently it's well over your head.
[toc] | [prev] | [next] | [standalone]
Page 3 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