Messages

  sorry,

unexpected impediments prevent me from using the camera for weeks now ..(bad focusing, unreliable color balancing, dim display(!?), slow pc  and so forth and I 'm so bored of all that.

Well, I hope this come true.  Talking about memory:  better more than less..

Here is the updated code: https://gist.github.com/pigeonhill/7efb6b13e34e366d2651ba574125a5fa

So, is this new script to be used now?

P.S. I 've got to install and run the  previous version of the script, but I had no chances to test it enough to report  you about it.. (I will)

The models that would benefit even from this - small - extra memory are 1100D and 600D.

This is the only part I understand in this topic, so my question is : how much is for 600D? (it is not mentioned) in wich these benefits would consist?

@IDA_ML   Braketing is more suitable for static subjects, while Dual ISO allow more DR in scenes with moving subjects. I would say that these are complimentary techniques for HDR shooters.

Thanks for the instructions and for the various suggestions (it seems to me everything is clear!).

I will test in the next days, I will report my impressions.

Thanks for the availability and congratulations for your photos on 500px, I'm following you now.

I'm not a technician, what I'm passionate about ML( despite my difficulty in understanding most of the ML stuff, especially lately, is the hope of being able to obtain final images of good quality, that represent my personal taste.

I just read an article while I was trying to learn about the LUT technology (http://tinyurl.com/y79pafab), which provided me with an interesting element to clarify the nature of a certain sense of frustration and dissatisfaction, which I'm feel against the level of skill I aspected to have achieved, after all this time spent studying and experimenting with my camera.

The part of the article to which I refer says:

"Having a great looking image during your shoot makes all the difference in the world.
It can help you feel more connected to the subject you are shooting."

This is exactly what I need at this point, to get out of the condition of expressive stalemate in which I find myself (perhaps I'm not the only one).

I have not yet well understood these LUAs, I also downloaded a free version of a SW (3DLUTCreatorDemo http://3dlutcreator.ru/, because it support MLV app. for those interested) but at first sight it seem rather cryptic.

However, I wondered if there is a way to implement this technology in ML instead of using an external monitor, as is described in the above mentioned article. (Just only for a preview in LV before shooting would suffice)


Forgive me  if I took the speech a little far and if I said nonsense.

Hi @garry23,

...in order to run the script, I just need to save it as .LUA (notepad or specific editor?) and then drop it into the ML's script folder?

Does it will work on 600D?

(forgive my ignorance,  I am only recently aware of the existence of LUAs ...)

Thanks

@garry23  interesting  ...which script?

@ToniX:
I also think it is a Windows font setting. If Windows overrides our font settings, the fonts may be to big for the GUI. We had the same problem on Linux. If fonts are system standard all should be fine.

@masc,  I saw your comment just now. Pardon
It is certainly a problem caused by windows, known and annoying ..The default settings are too small, so I switched to "BIG" (or Large),  while sizes of specific items (menu, icons, etc) are set  between 9-11 ....

Wild guess: Item/font size off.

Run

Code Select Expand

control /name Microsoft.Display

Hi @Walter Schulz 

I restricted the characters to the minimum size, actually allowing  the view of the parts of the panel that were missing. Unfortunately, this client side solution involves making the rest of the PC unusable, as the texts are for the most part illegible.

Perhaps solving at level of  programming, would be more logical and functional.

Thanks anyway, at least so I will get to test the app  (which looks to be very cool!)

@ToniX: I had the same problem. Text in the right panel appeared truncated. I have solved using this way: mlvapp.exe -> Properties > compatibility -> check "override high dpi scaling behavior -> select "system", OK.
I hope this helps you.
EDIT: I use windows 10 x64. In windows 8.1 the procedure may be slightly different.

PS:Sorry for my very bad english.

Grazie @GianlucaM83 - I've tried, it would have been a preferable solution but it does not work for me.

@dfort
   

Hi 600D users.

I uploaded a build named find-SRM_BUFFER_SIZE.2018Feb15.600D102 to my Bitbucket downloads page. Simply go to the Debug menu and select Free Memory.

Thanks!

hyi, I just wish to inform you that such file is not present at the provided url.

I have a problem with MLV GUI that severely limits the usability of the program, either with MLV.App.v0.13 /0.14.alpha.Win64.static.

The "edit area" panel is not displayed correctly.

In fact, all the commands on the extreme right of the panel are not completely visible and therefore are not accessible.

I tried different screen resolutions without solving.

I use win 8.1 x64 and I wonder if anyone else has the same issue.

Any solution? (detachable panel, a drop menu, more extended stretching ...)

@Walter Schulz    Thanks. I will add few second more, over the 5s as recommended by the UG.

@ a1ex

@ToniX: it's  a build system issue, the crop_rec module shouldn't have been included in the first place.

Cannot reproduce the "need 2 trials before the module is deactivated" part (not even sure what exactly you mean by that).

While testing a lot of different builds I have noted that in some of them (couldn't tell exactly which ones) it requires more than one camera on/off cycle for the modules to be activated/deactivated.

To be explicit: when enabling a module and restarting the camera, the module is not being loaded indeed, and the "ON-Will load" text is still there.

Two,  sometime three camera restarts, are needed to have it enbled. Same at reverse.

This is a confusing and time consuming issue, but I thougtht it was marginal afterall, given all the ML benefits.

@dfort   

crop_rec and lossless compression aren't yet available on the 600D. It might be possible though there is very little memory on that camera to work with. Back on topic--how is the manual lens lua script working on the 600D?

Thank you for the confirmation.

As for the script I can only tell you what happens in the camera:

1) After activating the module, go to the> Script screen.
2) select the Manual Lens Information item in a sub menu Run> Run
3) I follow the instructions and go to the menu> Prefs> Lens Info Prefs
4) In the subMenu -> Manual lens there are 4 items:

Lens: shows the type of lens (EF-S18-55 .... ISII)
Focal length: 0
Openings: 5.6
Autoload lens: on

At the bottom of the screen, an orange text says "Chipped Lens Detected" (in fact, this lens has AF that does not focus well).

The camera need 2 trials before the module is deactivated
The module does not automatically reload, it must be reactivated each time after turning off the camera.
I noted that enabling LUA it use an amount  of memory: from 254K+1001k to 242K +720K

I hope I was helpful. In case you need anything else, please ask.

I have installed the build "magiclantern-manual_lens_info.2018Feb02.600D102" on my 600D.

I've found there the crop_rec. mod, which  I was very curious to test but couldn't find anywhere else.

Unfortunatly, enabling the Crop-rec. module result in error and any other active module is being disabled as well.

( Instead, Lua script seem to work fine here, but I didn't tested extensively)

Is it this a known issue of the 600D or  is it there  some specific procedure to follow in order to make it work?

@a1ex

You could merge both branches and compile from source. Copying modules over won't work, as lua_fix contains many backend changes that break binary compatibility.

Unfortunately this is out of my Hw/SW/time/skills, reach.

For a while I will play with magiclantern-raw_video_10bit_12bit.2017Dec18.600D102 wich should be the most updated build available.. can you please confirm?

Thanks

@a1ex...    Thanks!

Thanks for the tip @Walter Schulz!  (Is it there an html version of the guide available?)

-Unfortunately I do not read german

Furthermore I've found this

The helpfiles from old version. Unrar and just copy to SD card.

I have copied the files from Doc folder of an old ML2.3 to the Doc folder of my NB.
They are not seen by ML.
I've tried to open the files from the "File manager" but it doesn't work.

File extension is .bmh.. I don't know to what Sf it is associated with. 

Any thougth?

Many times I terribly need to read the ML user guide from the camera.

I know that Nightly builds do not come with user guide (I run a latest).

The good outdated guide would be a good reference anyway for me, especially for experimenting with functions I'm new to.

How can I do it ?

@a1ex            Thanks a1ex for taking my post into consideration.

Your observations are correct and I totally agree with you on all the line..

I own a 600D which is notoriously limited in terms of filming in 14Bit RAW.

Then the 10/12 bit RAW as well as the LUA implementation appeared and this reignited my interest in ML .


The NB .2017Dec07.600D102 does not offer 10-12 RAW bits and the LUA module completely blocks the machine if activated and therefore is useless.

The other builds (LUA fix and laters) are updates of the latter (RAW video only at 14Bit) and  running LUA I still had errors, if I remember correctly.

Is there a way to test both 10/12 Bit RAw and LUA in a single build?
If yes, how should I do?

(I tried to copy the 10/12 modules over the builds with LUA fix and vice versa but, without success).

P:S I've read your call for tester, I hope I can participate-

All the best 

Use https://bitbucket.org/daniel_fort/magic-lantern/downloads/ until this problem is solved.

I can't find any version for 600D  listed on your page ...where is it? (the only available file for 600D is "firmware for tester") Should I choose a build for a different model,which one in case?

I hope to find a solution to my issue with that, because....

...In the last days I have installed (and reinstalled) several times, the following packages, but no luck: each one of them it caused some serious issue ( camera hangs, modules won't load, module errors, memory errors, script errors,unusable video preview...), so that I  had to give up using those latest ML 600D N.B.

magiclantern-raw_video_10bit_12bit.2017Dec18.600D102
magiclantern-Nightly.2017Dec07.600D102
magiclantern-lua_fix.2017Dec23.600D102
enGlPb+uLUA_FIX)
d62nh6VR*
tniyhfWA* 
(* Those last two are just the names of the zips when downloaded, following a thread in some ML forum board).

I used ML from 2013 especially for photo (and then left it for more than 1 year, and now I'm back to experiment with video) and I never had so many issues have it running, I'm now quite confused: is it there a more stable Build somewhere that I've missed, or a more reliable build is coming out soon so would be better to wait?

solution or not I'am amazed anyway for the genius technicians and coders behind the ML project, I'am learning so much.

I came across this article (http://www.chrisjonesblog.com/2012/06/how-to-make-a-dcp-digital-cinema-package-on-your-own-computer.html)and I think it could be useful for some of the filmakers here to know, since the technique described in here, is not so far from the ML raw video workflow....

I am just curious . Apart to play games on the camera display, what benefits would have running Freedos or linux on camera?
Maybe more programmability for certain automated tasks, or more deeper control of the camera core? Don't know...

Recently I discovered Kolibri ,that's a very lightwight OS just 1.4 Mb , entirely compiled in c++, complete with GUId and it is very fast.
It requires only a few megabyte disk space and 8MB of RAM to run. Kolibri features a rich set of applications that include word processor, image viewer, graphical editor, web browser and well over 30 exciting games. Full FAT12/16/32 support is implemented, as well as read-only support for NTFS, ISO9660 and Ext2/3/4. Drivers are written for popular sound, network and graphics cards.

http://kolibrios.org/en/index

Could be useful to know?