
Fratello hands on.
The photos in that review show that it's legible when it needs to be, but the hands can also disappear at certain angles... whether that's a "feature" or accidental, it's not a bad trick for something like this. In reality, like the Bel Canto, this is not a watch that's about telling the time, but more art and elegance I thinkOllyW wrote: ↑Thu Oct 26, 2023 11:43 am Seems that legibility wasn’t a priority.![]()
IMG_5743.jpeg
Fratello hands on.
Maybe it's just me 'cos the BC also didn't do anything for me.
I think this is my conclusion having seen the new moonphase. I find the C1 Moonglow more appealing in looks and functionality, that is the one I might buy.strapline wrote: ↑Thu Oct 26, 2023 10:42 am It's a gorgeous objet d'art, but as a timepiece it's a one trick pony. It really is captivating from a curio point of view, but I like a watch to clearly display the time. In the same manner that most of the focus of the Bel Canto is on its ability to go 'ding', time telling duties seem to have come second...by a long way. Personally I'd take the Moonglow; the party trick is there but so is an interesting date feature, as well as the ability to tell the time.
Des
Hmm, make room for me on the fence there please.
I agree with proposing a case swap. I find that I often need to try and dress down my Moonglow, I’d love the consort bracelet for it if was an option.ajax87 wrote:What’s interesting to me is that the new Moonphase dial is much dressier than the Moonglow, but they dressed down the case and made it more toolish. It looks a lot like a C63 case. The Moonglow case is quite dressy. Pictures below.
I think the Moonglow would look better with the new Moonphase’s case, and vice versa.
I do like both but have no desire to replace my moonglow or add another moonphase. Well done CW!
I almost always wear mine dressed down. It pretty much lives on an Ericka's MN style strap. But you're right, the consort would be great! Probably wouldn't work even if it did fit, with the top of the lugs being polished on the Moonglow. I'm getting a consort bracelet with the FLE, so I'll throw it on and double check. You never know!MistaFroggyG wrote: ↑Thu Oct 26, 2023 2:17 pmI agree with proposing a case swap. I find that I often need to try and dress down my Moonglow, I’d love the consort bracelet for it if was an option.ajax87 wrote:What’s interesting to me is that the new Moonphase dial is much dressier than the Moonglow, but they dressed down the case and made it more toolish. It looks a lot like a C63 case. The Moonglow case is quite dressy. Pictures below.
I think the Moonglow would look better with the new Moonphase’s case, and vice versa.
I do like both but have no desire to replace my moonglow or add another moonphase. Well done CW!
I used to own an Omega moonphase watch and the moon would move sligtly once per day. So hacking the seconds or setting the time would not affect tha accuracty of the moon phase. It's still going to make the jump at a set time. I think my Omega used to move at noon.mvlow wrote: ↑Thu Oct 26, 2023 2:46 pm According to the moon phase chart there is a full hunter's moon on October 28th at 1:24pm. If I were to buy this watch I could see myself sitting there with my iPhone at 1:23 and 45 seconds concentrating on pushing the crown in at exactly 1:24pm to make sure the moon phase is accurate. Then rushing online to buy a watch winder, as I wouldn't want to be looking up the moon phase chart every few days if the watch stopped![]()
Serious question for the uninformed as I've never owned a moon phase watch. When you pull the crown out all the way to hack the seconds hand and set the time does it hack the moon phase as well, so that the moon phase is no longer perfectly accurate. If that is the case, you would have to hack the watch at the exact time of the moon phase you want and set the time at the same time I think?
Personally I wouldn't care if the moon phase was a few minutes off as it's probably not noticeable, but we all know there are some WIS that would stress over this every time they set the watch![]()