Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Topics - gotar

#1
Feature Requests / Fetch settings from a photo
April 04, 2014, 09:44:19 AM
I wonder whether this would be possible to use any picture's taken EXIF data as a template to the camera? I mean the ISO value, WB settings (temperature, offsets), expo etc. (maybe with image format/size too).

I see two usecases:

1. easy coming back from experimenting/changed conditions to user's favourite/casual settings (or after lending device to someone else or making any change by mistake),

2. adjusting settings for current scene - I sometimes find myself shoting a few photos with different settings just to choose the best one (mainly alternating WB as the 500D's auto isn't too good).

I realize these scenarios are not what pros do (like lending the camera or shoting blindly to find best values - especially for WB settings that don't matter in raw), but maybe this would be useful.

This is a copy from https://bitbucket.org/hudson/magic-lantern/issue/1905/fetch-settings-from-a-photo since that tracker isn't used for feature requests in ML.
#2
Having non writable card (either full or r/o) issues fullscreen warning and makes LV unusable. One might think it doesn't matter as shutter button doesn't work either, but when tethering it is reenabled and I can take remote shots (at least with my 500D) directly into my Linux box. However, with no advanced ML functions - the basic draws including histogram, waveform and vectoroscope are available by some trick: enter into ML menu (trash button) and make it transparent (zoom in button). This would be more convinient to get rid of the original Canon's warning (just highlight it in place, where available photo count usually resides) and try to fully operate, with no artificial restrains (at least when PC is connected, but some LV image analysis even without r/w possibility might be a support for taking pictures with another, less-featured camera).

Of course one might say 'put writable card', but in case of tethering it does nothing except wearing the card, power usage and some slowdown, as pictures are eventually removed from the card anyway. The card is needed only for running ML and might be small and slow.
#3
When in movie mode one can apply 4 effects that are applied on recording only - but cannot take for example negative photo. Is this some sort of hw limitation, or was intentionally differentiated? Shoting negatives is a low cost of 'scanning' analog films. While converting dozens of positive photos (of negatives) to negative (to make them positive) is rather a simply task, negative preview in M mode is something worth having. With custom WB it would allow direct negative 'scanning' with minimum postprocessing.
#4
Feature Requests / LCD brightness: auto
September 06, 2013, 02:27:59 PM
Dealing with hardware, which - well, do things with light, I really miss the feature of automatic adjustment of LCD backlight. Of course the lens can be closed, one might meter the light of some deep cave in shiny bright day, but many situations are perfectly suited for this to happen; being outdoor we need bright LCD to be seen in full sun, or dimmed when it's night. I often find myself blindly increasing backlight barely seeing the display.
#5
Feature Requests / Thermal throttling profile
September 06, 2013, 02:20:39 PM
Today morning after a few hours spend playing with ML (no real photo) I got the high temperature warning. It would be nice if the most power hungry features could turn themself off automatically in such conditions (I'm not sure which one, but probably waveform, vectoroscope, zebras other than fast, maybe entire LV, dimming LCD etc.) It would be even better, when implemented as low-power profile that comes with some rational presets (made by people who know what drains power - I do not) and could be entered manually (or automatically on low battery condition).
#6
Hello everyone,

at the beginning - I am aware that this request might look like breaking "don't do anything that can't be done in postprocessing" rule, but this feature would have at least one real-life usage: freeing storage space when one runs out of it being out of civilisation. It already happened to me that I had to choose either to delete some of the already taken photos, or won't shoot any new. In such position many would happily sacrifice raw possibilities of some photos if only they could be preserved in JPEGs.

I've searched forum and bug tracker for similar request and found only off-line raw movie compression, unfortunately not possible. I hope in this case it is possible to feed raw data from storage directly into the DIGIC to perform hardware (i.e. fast) JPEG compression. Once again, I don't wish that option to be some introduction of in-camera fancy photo editor, but solely to give users comfort of shooting raws without worrying much about their size, as some of them could be shrinked afterwards (probably when there's more time to review).

Best regards and thanks to all the contributors and developers!