Jump to content

Recommended Posts

Advertisement (gone after registration)

are you referring to the focus peaking?

If so, Im not suggesting this be eliminated...after all it can be turned off. The implementation in the M is drastically different from the SL or any previous Leica. Unless my camera has an issue (which I doubt), the M focus peaking is adding too many highlights on the image and many appear random. I need to test it further.

That's how focus peaking works on every other camera that has it. The M240s peaking was just not very good.

Link to post
Share on other sites

Two more issues id like to see fixed:

 

-Auto review-hold issue

When "HOLD" is selected in Auto Review the image remains until you touch the shutter a second time. On the M240 and M9, this functioned correctly and the image remained only while "holding" the shutter release down. The implementation on the M requires a 2nd step. Is there a reason for this change? I much prefer the hold and release concept for this new function, the added step is unnecessary and slows down shooting.

-White Balance/Greycard

An extra step was added on the M10. You must shoot the grey card, then select the grey with picker, then save. Again, on the M240 there were less steps required. Is there a reason for this?

 

I'd say this makes sense.

If you have a grey card but can't shoot it to fill the screen - then now you can pinpoint the area you want to WB for. Or if perhaps there is a scene you want to white balance and there's something specific to white balance to in that scene the picker allows you to select an accurate colour patch.

Link to post
Share on other sites

If not already in place (I don't have an M10 yet)

 

- menu option to switch OFF optical finder display of ISO and Exp. comp. This drove me crazy using an M240 briefly. I want to see only: shutter speed if in A, or metering indicators if in M. Don't waste my time with the other stuff (but do make it a user-defined option - I do understand that others find those reminders useful.)

 

- regarding compressed/uncompressed .DNGs. Options and choices are always good.

 

I don't doubt that the compressed quality is fine ( use that option on the M9), but, again, for the brief time I had an M240, I found that Adobe products (ACR) struggled a bit opening compressed 24 Mpixel DNGs - a second or so longer to open them (spinning ball) than with uncompressed images, even though they are smaller files. Probably due to interpreting the Leica compression.

 

And the .DNG file will be compressed by Adobe on the computer anyway, once it has been opened and saved from LR or ACR. So the file-space savings only really apply to: on-card space (and SD cards are cheap - you can't even get anything smaller than 8G most places); or pictures never opened on the computer (which suggests they are not high-value pictures - "delete" will save even more space ;) ).

The DNG compression on the M9 was not the same as the M240. The M240 is lossless compression. The M9 was lossy. There was a valid argument for the M9 and using full size DNGs but this was mooted for the M240.

  • Like 1
Link to post
Share on other sites

I understand how the hotshoe could provide power, but without a mic port how does it transmit sound information? Wouldn't the camera need some sort of port for sound in? I don't see how that could be done through the hot shoe.

 

Edit: looking into this further the question is whether the Leica microphone adapter for the M240 hotshoe will work with the M10, if it does then that would add a mic port that can then be used by any microphone. The question is whether the M10 is set up internally to work with that adapter. I am less than sure that it is.

The m240 adapter was a rebranded Olympus as was the EVF. The physical connection on the M10 I think is different so the mic adapter would not work.

 

Even without the mic adapter the 240 had a small in built mic. Even if one was to record sound separately the built in mic was needed to get the sync of the recorded sound to match the external audio source. Of course it could be done just visually but with a 'scratch' audio track it's much easier.

Link to post
Share on other sites

There's no heat issue when recording video. Full stop. How do I say that with such confidence? Live view.

 

The camera works fine when you're using live view, right? What's going on with the camera when it's doing LV? Oh, right -- it's reading the full contents of the sensor, transforming it, doing some calculations for focus peaking, and shuffling the data off to either the visoflex or the rear display.

 

And when you press the shutter button, it manages to take a wonderful picture regardless of all of the "heat" that's been generated.

 

:rolleyes:

 

Recording video is now a hardware solution that's baked into the Maestro II processor. The same processor in the SL chugs along recording 4K without bursting into flames.

 

They took it away to appease people who hate the fact it can take video.

 

Either using LV can make the camera burst into flames (it doesn't) or you can take video if you wanted to and it was an option.

 

The only technical argument I can buy is the microphone took up too much volume or it's too hard to weather seal the microphone holes. As was pointed out above, that could be solved with a hot-shoe-mounted mic.

This depends on how the camera is built and how well the heat generated by the sensor and nearby circuitry is transported away. The very first generation of Sony NEX cameras were so densely packed that they could shut themselves down after some time of continous video recording because of sensor overheating. I have one of these and it has happened to me a couple of times when shooting video, but never in LV. The M10 might be built differently from the M240 when it comes to sensor cooling.

Link to post
Share on other sites

[bUG FIX]

v 1.3.4.0

 

Shooting with the Visoflex 020, Drive mode is set to Continuous, Image Review set to off. After exposing a burst of images, camera crashes and requires a battery reset.

 

more info here:

http://www.l-camera-forum.com/topic/269358-camera-crash-with-visoflex-continuous-mode/?do=findComment&comment=3212371

 

NOTE: Some cameras report this issue, while other don't.

Edited by digitalfx
Link to post
Share on other sites

<snip>

Finally, recording: when you have something implemented in hardware, as is done with the Maestro II, it takes a surprisingly little amount of power to do video encoding now. We're only looking at 1080 for the M10 (though, in all honesty 4K should be almost as easy) and the number of devices that record 4K video now serves to provide an upper bound on the power dissipation for recording in a modern setting. Take, for instance, the Sony FDR X3000. (Amazing action cam if you're in the market!) With a 4.5 Wh battery, it can record around 50 minutes of 100mbps 4K video. And this is while it's also doing GPS and image stabilization and it's in a plastic enclosure that's fully sealed. It's inconceivable that Leica can't do something similar or better with only 1080 video. (The Sony lasts 125 minutes if it's recording 1080 in case you're curious) It's amazing what you can do with custom hardware!

 

I can see a marketing meeting at Leica debating if the M10 should be allowed to take video... the argument against isn't a technical one, it's one of product differentiation.

 

I don't think the average person was looking to use the M10 to do serious cinematography where you have everything rigged up and are outputting to an external recorder -- 10-bit HDMI in log format. It's for people (reporters?) who need to make a 20-second clip or a quick minute or two interview for some production. No one is arguing for exposing HDMI and stuff.

 

Full disclosure: I have an M10 and don't care it doesn't have video. I'm coming at this from a hardware engineering point of view.

 

-George

 

From a hardware engineering point of view I only have one disagreement with you: microphones and a speaker for playback. I kind of think that part of the improved water sealing may be that they got rid of 4 buttons, the microphones, and the speaker. Not that those were ever really weaknesses for the M240 but they were case penetrations.

 

I think that from a SW point of view doing video well ends up being a rather tall order and probably greatly adds to the size and complexity of the firmware. Having the video people dedicated to the SL and addressing the needs of real videographers there allows them to focus their resources. They can let the versions of the software run independently without complaints like "you added this feature or capability to the SL now add it to the M".

 

Part of leica's DNA is also the "doing it well" and I think that the SL was a big learning curve for them on video and they found out what it takes from both a software and a hardware point of view to do video well and they didn't want to spend effort on a feature that few people used wasn't implemented well. I remember the reviews of the M240 where the reviewers either criticized it or made the excuse that the M240 was never intended for video.

 

Furthermore embedded CPUs are often specified by the size of memory and firmware space they have. It may be that the particular Maestro II variant that they chose has less space for firmware. It is possible that knowing that the M10's firmware didn't need to do a lot of things, the got a trimmer chip in a smaller package which took up less board space.

  • Like 1
Link to post
Share on other sites

[bUG]

FW- 1.3.4.0

 

When images are imported into LR 6.8 or iPhoto, they are randomly imported with incorrect orientation. Horizontal Images import upside down and must be manually flipped.

Discussion:

http://www.l-camera-forum.com/topic/269582-incorrectly-rotated-m10-photos-following-lightroom-cc-import/

Ok, Rao on his own might face this problem for some reason but it is no bug.

 

 

Gesendet von iPhone mit Tapatalk Pro

Link to post
Share on other sites

Ok, Rao on his own might face this problem for some reason but it is no bug.

 

 

Gesendet von iPhone mit Tapatalk Pro

Multiple people have reported this issue in several apps, so why do you feel it's not a bug?

 

I've also experienced some degree of this on import

 

 

Sent from my iPhone using Tapatalk Pro

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...