Speed cameras are never film. Its is not 1972 anymore.
The speed with which the CCD can write to memory is far faster than the computer can process, there simply isn't time to open the image from memory, stuff in a time and rewrite the image in real time.
Even video equipment only captures frame numbers from one shot to the next, and actual (estimated) time is added later.
I made no such claim. Stop putting words in my mouth.
The prosecution presented radar evidence that the vehicle was speeding. The defense presented faulty evidence from a source that was not capable of measuring speed.
The judge bought into the faulty evidence.
I have no idea what the hell you are whining about, since the guy got off.
Agreed. The time stamp may be added to the RAW as it sits in memory, before encoding. It would make more sense.
Doesn't matter for our purpose here. The processors are simply not fast enough to do all of this work in parallel on two shot bursts. Nothing changes between two shot bursts as far as camera settings. The only difference is the post processing treatment of the photo data.
Admittedly they should have simply time stamped it to the minute and nothing more, and/or provided only one image. The photo what to prove presence, NOT speed. Speed was captured by radar 50 feet from the camera.
But again, this data does not come from the CCD. It is merely added as the images are stored. Do you seriously believe your CCD knows your lens model, and authoring information?
All of this stuff is added AFTER the image is in the camera computer's memory and documents the data at the time the file is written.
If it were EXIF the defendant would never see it, because he simply got prints.
These speeds were superimposed by the camera upon the jpeg at processing time. The EXIF information is also created at that time. (It does not come from the CCD, CCDs don't have clocks).
Processing time can be quite different than actual CCD dump (photo capture) times and almost ALWAYS are when using two-shot bursts, unless your budget is as big as NASA.
You don't add a time stamp to a JPEG picture. You add a time stamp to raw pixels.
Nice theory, but unfortunately things don't work that way unless you are NASA and arrange to have a clock running in each shot.
Cameras do not write to the CCD. CCDs do not impose time stamps. CCDs dump images to into shared working memory. The Computer then process from Working memory as fast as it can, but this processing is always slower that the rate at which the CCD can deliver images.
Lots of 100 dollar cameras can do a three shot burst. The interval of the burst does not include the storage time. But its the storage time (actually the conversion from RAW to JPG time) that gets time stamped.
OCCAM suggests that the photo time stamps measure the interval betweens processing and storing of the photos and nothing at all to do with when the photos are actually snapped.
He has to prove the radar was wrong. The photos are just to prove his vehicle was on that road AT the time the radar clocked it. The law does not require that the picture be taken PRECISELY to a hundredth of a millisecond at the exact time the radar clocked the car.
All it has to prove is that this car was there, and no other car was there at that time. That is all the photos are evidence of. The photos are not evidence of speed. Simply presence.
That's all.
He is not contesting that his car was there. He is trying to use the pictures as evidence to refute the radar, and the judge let him get away with it because the judge accepts junk science in his courtroom.
which almost certainly means that it is generated at the same time the picture is generated
No. That's exactly my point. The time stamps are generated AFTER the picture is taken.
In order for the time stamps to measure EXACT time the picture is taken you need a realtime clock running in the focal plane. NASA does this.
Off the shelf CCDs do not have this.
The time stamp is inserted at processing time. Its not in the raw image.
If you take any reasonable camera that offers time stamping AND a three-shot mode, you can replicate this yourself. Put it in three shot mode, and select RAW image. That image is exactly how it comes from the CCD. Offload that image to computer and it will not contain a time stamp (because its raw).
The time stamp is taken from the compute clock when they are converted to JPG.
The interval between first conversion and second conversion was.363 seconds. That is ALL you can deduce from the time stamps. In that time period, the first picture is written to disk, (card) the second is converted and processed to the point of time stamp insertion, (but not yet written to disk).
The.363 measures the amount of time it takes to write the First picture to disk, Convert the SECOND to jpeg and insert time. The second write to disk is not measured.
The pictures could have been snapped back to back just as fast as the CCD can dump to main memory. The CCD does not impose a clock image on the photos. Its the processing that does that.
The photos are taken 50 feet from the sensor according to the company.
But he is using time stamps which are placed in the image as they are being written to disk, (probably microsd card) NOT as they are being taken. Pictures taken are held in memory until they are processed (converted from raw to jpeg). At the time they are processed the timestamp in inserted into the image.
It took.363 seconds to process, timestamp, and write out the first image. That's is ALL that time stamp measures.
So upon a technical review, this guy should have lost this case.
While true for some essential apps, your comment is not germane to Skype. Once killed, it stays killed. Other than that, I agree with you, get rid of offending apps.
But be sure they are REALLY offending. Skype goes dormant when you log out of skype (not the easiest option to find in the Android version). It will drop all data connections when you do this. But it still leaves about 29meg in memory. That too will be paged out as memory need demands. So it really does not need to be killed, you just need to log out. They should make this easier to find.
Far too many people try to micro-manage Android's memory usage. Far too many cell companies install task killers. Android is not windows. It knows how to manage memory far better than the user does, and far better than task killers. There is absolutely no reason to run a task killer on Android.
If you have a misbehaving app, get rid of it. Don't add more troublesome software to compensate.
Sign out, then you can 'back' out of the app without it running in the background.
If you log out, the process is like every other android process, it goes to sleep and will be paged out as memory demand requires. It no longer hold any connections open. But there should still be an option to completely quit.
Logging out is not obvious, (see status setting tab).
The app is a huge memory hog. I couldn't even install it till the version that allowed installation to the MicroSD card (app2SD). I only use it for international calls to a small group of people, because it is just too resource intensive. I have them text me on google talk (which every android phone has) and then I will switch to voice over Skype.
But lately I've been using SIP for that, using CSipSimple, which connects faster, sounds better, and is very resource friendly. With a free SIP account at both ends from any number of sip providers (such as iptel.org, sip2sip.info, etc) its far easier than Skype. The only advantage skype holds is name recognition.
Slashdot Mirror
Speed cameras are never film. Its is not 1972 anymore.
The speed with which the CCD can write to memory is far faster than the computer can process, there simply isn't time to open the image from memory, stuff in a time and rewrite the image in real time.
Even video equipment only captures frame numbers from one shot to the next, and actual (estimated) time is added later.
He has proven no such thing.
His speed was clocked by radar. He presented no evidence that refutes the radar evidence.
Photos were to prove presence, not speed.
The fact that the vehicle in question was there at the time is not disputed by the defendant.
You are up the wrong tree barking.
I made no such claim. Stop putting words in my mouth.
The prosecution presented radar evidence that the vehicle was speeding.
The defense presented faulty evidence from a source that was not capable of measuring speed.
The judge bought into the faulty evidence.
I have no idea what the hell you are whining about, since the guy got off.
Well, the prosecution presented their evidence already, didn't they?
He's trying to refute that evidence.
Can you describe a system where ANY crime could be proven if the prosecution was not allowed to submit evidence?
True, but not germane to this discussion.
Once the camera is installed you've already lost that battle.
Agreed. The time stamp may be added to the RAW as it sits in memory, before encoding. It would make more sense.
Doesn't matter for our purpose here. The processors are simply not fast enough to do all of this work in parallel on two shot bursts.
Nothing changes between two shot bursts as far as camera settings. The only difference is the post processing treatment of
the photo data.
Admittedly they should have simply time stamped it to the minute and nothing more, and/or provided only one image.
The photo what to prove presence, NOT speed.
Speed was captured by radar 50 feet from the camera.
All I'm saying is the evidence the defense provided does not prove him NOT Guilty.
The radar evidence was not in the article, so I can't judge that.
He used junk science, and he got away with it.
But again, this data does not come from the CCD. It is merely added as the images are stored.
Do you seriously believe your CCD knows your lens model, and authoring information?
All of this stuff is added AFTER the image is in the camera computer's memory and documents the data at the time the file is written.
Faulty logic may be basic logic, but its still faulty.
If it were EXIF the defendant would never see it, because he simply got prints.
These speeds were superimposed by the camera upon the jpeg at processing time.
The EXIF information is also created at that time. (It does not come from the CCD, CCDs don't have clocks).
Processing time can be quite different than actual CCD dump (photo capture) times and almost ALWAYS are when using two-shot bursts, unless
your budget is as big as NASA.
The pictures ARE inadmissible as evidence of speed. The judge is just too stupid to realize this.
Speed is evidenced by RADAR.
Presence is evidenced by photos.
Why is this so hard for you to understand?
You don't add a time stamp to a JPEG picture. You add a time stamp to raw pixels.
Nice theory, but unfortunately things don't work that way unless you are NASA and arrange to have a clock running in each shot.
Cameras do not write to the CCD.
CCDs do not impose time stamps.
CCDs dump images to into shared working memory.
The Computer then process from Working memory as fast as it can, but this processing is always slower that the rate at which the CCD can deliver images.
Lots of 100 dollar cameras can do a three shot burst. The interval of the burst does not include the storage time.
But its the storage time (actually the conversion from RAW to JPG time) that gets time stamped.
OCCAM suggests that the photo time stamps measure the interval betweens processing and storing of the photos and nothing at all to do with when the photos are actually snapped.
Speed is measured by radar, not photo evidence.
Look: Speed is measured by radar, not photos.
He has to prove the radar was wrong. The photos are just to prove his vehicle was on that road AT the time the radar clocked it.
The law does not require that the picture be taken PRECISELY to a hundredth of a millisecond at the exact time the radar clocked the car.
All it has to prove is that this car was there, and no other car was there at that time. That is all the photos are evidence of.
The photos are not evidence of speed. Simply presence.
That's all.
He is not contesting that his car was there. He is trying to use the pictures as evidence to refute the radar, and the judge let him get away with it because the judge accepts junk science in his courtroom.
Define false.
How much accuracy does the law demand on a time stamp?
They guy is not contending that he was NOT there on that day.
Stop being a putz.
which almost certainly means that it is generated at the same time the picture is generated
No. That's exactly my point. The time stamps are generated AFTER the picture is taken.
In order for the time stamps to measure EXACT time the picture is taken you need a realtime clock running in the focal plane.
NASA does this.
Off the shelf CCDs do not have this.
The time stamp is inserted at processing time. Its not in the raw image.
If you take any reasonable camera that offers time stamping AND a three-shot mode, you can replicate this yourself.
Put it in three shot mode, and select RAW image. That image is exactly how it comes from the CCD. Offload that
image to computer and it will not contain a time stamp (because its raw).
The pictures are intended to show the car at that place.
They are not designed to show car speed.
All the measure is picture conversion and storage speed.
Look, any 100 dollar camera can take back to back shots. Some can take 3 of 4 back to back.
They just dump the raw image from the CCD to memory, and process ALL of them to jpg (and insert time stamp) AFTER all of them are shot.
The time stamp is not the time the pictures were taken. Its the time the pictures were processed.
No its not valid.
The time stamp is NOT on the picture when taken.
The time stamp is taken from the compute clock when they are converted to JPG.
The interval between first conversion and second conversion was .363 seconds. That is ALL you can deduce from the time stamps.
In that time period, the first picture is written to disk, (card) the second is converted and processed to the point of time stamp insertion, (but not yet written to disk).
The .363 measures the amount of time it takes to write the First picture to disk, Convert the SECOND to jpeg and insert time.
The second write to disk is not measured.
The pictures could have been snapped back to back just as fast as the CCD can dump to main memory. The CCD does not impose a
clock image on the photos. Its the processing that does that.
The photos are taken 50 feet from the sensor according to the company.
But he is using time stamps which are placed in the image as they are being written to disk, (probably microsd card) NOT as they are being taken.
Pictures taken are held in memory until they are processed (converted from raw to jpeg). At the time they are processed the timestamp in inserted into the image.
It took .363 seconds to process, timestamp, and write out the first image. That's is ALL that time stamp measures.
So upon a technical review, this guy should have lost this case.
No they saying he was able to DECELERATE 15mph in .363 seconds. RTFA.
Tired of roasting my knees. Hate laptops on the lap.
Are you sure you are replying to the right person?
I mentioned nothing about SD.
While true for some essential apps, your comment is not germane to Skype. Once killed, it stays killed.
Other than that, I agree with you, get rid of offending apps.
But be sure they are REALLY offending.
Skype goes dormant when you log out of skype (not the easiest option to find in the Android version).
It will drop all data connections when you do this.
But it still leaves about 29meg in memory.
That too will be paged out as memory need demands. So it really does not need to be killed, you just need to log out. They should make this easier to find.
Far too many people try to micro-manage Android's memory usage. Far too many cell companies install task killers. Android is not windows. It knows how to manage memory far better than the user does, and far better than task killers.
There is absolutely no reason to run a task killer on Android.
If you have a misbehaving app, get rid of it. Don't add more troublesome software to compensate.
Sign out, then you can 'back' out of the app without it running in the background.
If you log out, the process is like every other android process, it goes to sleep and will be paged out as memory demand requires.
It no longer hold any connections open. But there should still be an option to completely quit.
Logging out is not obvious, (see status setting tab).
The app is a huge memory hog. I couldn't even install it till the version that allowed installation to the MicroSD card (app2SD).
I only use it for international calls to a small group of people, because it is just too resource intensive. I have them text me on google talk (which every android phone has) and then I will switch to voice over Skype.
But lately I've been using SIP for that, using CSipSimple, which connects faster, sounds better, and is very resource friendly. With a free SIP account at both ends from any number of sip providers (such as iptel.org, sip2sip.info, etc) its far easier than Skype. The only advantage skype holds is name recognition.