 |  |  |  |  |  |
| Couples' oh No moment! by mythshri from Seated Couples | PA020047.Bald Eagle Approach.2 by Hornsbee from BIF | The king of the mountain by Dan Paris from Landscape with Wildlife | Big eyes by Minas_Eye from Eye - macro/close-up | Bon appetit! by valenttin from Van een mug een olifant maken | THREE BOWLER HATS by FINEART4YPvK from Men Wearing Hats |
So Dpreview, how about testing and reporting on this camera's timekeeping performance? I've had two of the RX100s and their clock accuracy is atrocious, mine both lose about a minute a month.
If you use an external GPS for geo-tagging (which is orders of magnitude more accurate than any built-in GPS that I have seen) you are totally dependent on the accuracy of the time-stamp, the application matches that with the similarly time-stamped location in the GPX file.
Yes, there are workarounds, setting the clock regularly or (more simply) photographing the time displayed on your GPS receiver's screen after each outing and adjusting all time-stamps accordingly - but clocks should keep accurate time.
Unless mentioned in reviews, there is no pressure to improve this ...
FLruckas: "Seagate say the driver"
Huh?
Typo or two there?
How did they fit so many 2TB Samsung SSDs into that 3.5 inch form factor?
Just kidding.
I still have a few IBM micro drives laying around.
This is the future of hard drives.
(The same thing that happened to the Microdrive)
We'll all be using tablets to access the data on this SSD HDD in the cloud.
Welcome to the future.
Almost.
... but of course it should then have been "Seagate launch 60TB SSD", shouldn't it? :-)
FLruckas: "Seagate say the driver"
Huh?
Typo or two there?
How did they fit so many 2TB Samsung SSDs into that 3.5 inch form factor?
Just kidding.
I still have a few IBM micro drives laying around.
This is the future of hard drives.
(The same thing that happened to the Microdrive)
We'll all be using tablets to access the data on this SSD HDD in the cloud.
Welcome to the future.
Almost.
No typo - just British usage:
http://blog.dictionary.com/collective-nouns/
Lloyd709: I bet all those stuck in the mud staying with CS6 are starting to feel just a little bit jealous now!!!! Anyone guess what waterfall that is?
The waterfall is Skógafoss - Adobe seem to love Iceland :-)
Given that many cell phones are of sufficient length to mimic the distance between our eyes I am suprised nobody has come out with a 3D arrangement - lenses at opposite ends. Most TVs are 3D by now (at least the high-end ones) so this might be a "killer app" .... and might also give those TVs a raison d'etre!
KW Phua: Waiting for mirrorless lens. Mirror lens are too big to fit with mirrorless camera.
I think the OP wants lenses to shrink with the body size regardless of aperture and sensor size. If anyone can rewrite the laws of physics then that's probably Sony - but still ... :-)
Here's a strange problem. I changed the video format to PAL. On restarting, the camera posted "Running on PAL" - apparently a gentle reminder to format the memory card, fine. However, after formatting it KEPT posting this warning. The only way to get rid of it was to switch back to NTSC and do a format to get rid of the (single) "Running on NTSC" warning.
Is this normal or do I have a dud? Having to acknowledge that I am using PAL every time I turn on the camera is not acceptable ...
I've got an RX100m2 which I love - except for two very irritating flaws.
First off, the clock gains about 30 seconds per month - I haven't seen such poor timekeeping in the last 20 years. When using time to synchronise with an external GPS this matters, when moving, 30 seconds can translate to quite a distance. Yes, I can photograph the GPS time readout and correct for the error - but still :-)
The other flaw is the excessive time it takes for the camera to turn itself off (i.e. retract the lens) - I find myself waiting for it to do so when out hiking and wanting to stow it. Turning off the review doesn't help much.
I wonder whether these flaws have been fixed (unless of course they are specific to my copy).
Mammolo02: I have been using it for a month now. If you limit your prints to A4 size the image quality is acceptable. I would not use it for A3 prints. If you never print anything ... then it's very good :-)
The article keeps going back to the issue of using a RAW editor, but does not mention any. I use RawTherapee, but TG-4 RAW support on major software packages is still lacking.
I'm not sure I'd agree LR 6 does a really good job - it offers three profiles (muted, normal and vivid if memory serves) and in 70% of the cases the JPEGs which the camera insists on also storing come out better than anything I can do in LR without a major effort. I will concede that in the remaining 30% of cases ORFs really do help.
It is interesting that LR automatically ignores the JPEGs on import (at least using "synchronize folder" - I use Downloader Pro for the actual import), seemingly regarding them as thumbnails. Picasa is where you can most easily compare JPEG and ORF.
Just as with the RX100 (and perhaps other recent compact cameras) LR automatically corrects for image distortion, it doesn't even give you the option of omitting that step. Fine for most shots I guess - but sometimes you'd rather live with the barrel distortion to retain that important detail in the corner ...
Fellwalker: Shame there's no GPS.
I recently got my first GPS-equipped camera (Olympus TG-4) and gave it a try. I also used my normal method - Garmin eTrex 30 in my pocket recording GPS positions at 5 second intervals (and batteries last all day!).
After confirming that the camera's location information was useless (even with background tracking activated) I went back to using GeoSetter to write the location information from the eTrex to my photos ....
Google+ Photos allows me to set captions and tag faces - I can find neither feature in Google Photos. Are they hidden somewhere or have they been removed?
Luckily the same albums can currently be accessed three ways (Picasa Web, Google+ and Google Photos) but I imagine that is only temporary ...
I put this where the photo of Kirkjufell was originally posted - guess I might as well put it here as well.
The photo appears to be taken from the vicinity of the village of Grundarfjörður looking north-west towards Kirkjufell (which I have climbed, it's a great adventure!). Where you would expect to see the Big Dipper and the Little Dipper (along with Polaris to mark North) the photo has a bright mass of stars running vertically through it which appears to be the Milky Way (not a prominent feature of the Icelandic night sky I'm afraid!).
For this to happen the Earth's axis would have to slant by a number QUITE a bit larger than the current 23.5° (my crude maths tell me that the ecliptic cannot rise higher than (90°-64° = 26°) + 23.5% = 49.5% and should of course be seen to the south, not the north (and presumably running west-east, not north-south).
The photo appears to be taken from the vicinity of the village of Grundarfjörður looking north-west towards Kirkjufell (which I have climbed, it's a great adventure!). Where you would expect to see the Big Dipper and the Little Dipper (along with Polaris to mark North) the photo has a bright mass of stars running vertically through it which appears to be the Milky Way (not a prominent feature of the Icelandic night sky I'm afraid!).
For this to happen the Earth's axis would have to slant by a number QUITE a bit larger than the current 23.5° (my crude maths tell me that the ecliptic cannot rise higher than (90°-64° = 26°) + 23.5% = 49.5% and should of course be seen to the south, not the north (and presumably running west-east, not north-south).
What gives?
I recently discovered that my RX100 II clock runs fast, it gains a whole minute per month! This is a huge problem for me (especially before I discovered it) because I geocode my pictures after the fact by means of GPX files from my GPS - everything hinges on the camera being set to the right time - and keeping accurate time.
Has anybody else seen this?
Leifur