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

Messages - RenatoPhoto

#1326
Share Your Photos / Re: Astrophotography
January 29, 2013, 06:11:35 PM
Nice photos.

What lens did you use for Orion Nebula?  Or did you use a telescope.
#1327
General Development / Re: ML UI rationalization
January 29, 2013, 02:19:47 PM
Thumbs up!
#1328
Quote from: hjfilmspeed on January 28, 2013, 08:00:17 PM
I LOVE YOU ML! but i strongly dislike canon (coming from a 5d3 owner)

Me too!
#1329
Quote from: g3gg0 on January 27, 2013, 03:53:25 PM
as we are currently in alpha state, that is limited to FIR booting ("Firmware Upgrade" functinality), releases can just be made by us.
you cannot compile it on your own yet.

Could you please release a dev kit so I can compile the newer Bulb Ramping function from unified?  I am using it with 5D3 and work fairly good, but on 7D I have problems as noted here: http://www.magiclantern.fm/forum/index.php?topic=4259.0
#1330
General Help Q&A / Re: Bulb ramping Trouble Shooting
January 26, 2013, 08:32:25 PM
Quote from: a1ex on January 25, 2013, 12:48:36 AM
From the moment when ML issues a shutter command, until Canon code actually processes it, there is some delay (there are lots of tasks processing this request, it goes through some message queues and it ends up in the MPU, probably the real-time CPU). There is no exact control over this timing; I have only measured the repeatability of the process. Each camera may require a different bias though.

Maybe the script should give the camera the closest shutter time that is actually used by the system.  For example instead of 0.1815 it should send 1/5 which is the closest camera acceptable shutter.  By doing this maybe it is possible to avoid some of these camera interpretation errors?

Again this does not seem to be a problem in the bulb mode but it is more pronounced below the 1 sec shutter speed.

Just and idea..
#1331
General Help Q&A / Re: Bulb ramping Trouble Shooting
January 25, 2013, 12:35:26 AM
One more question.

If the log file says that the shutter should be 0.2192 why does the camera shoot the photo at 0.33 shutter speed instead of say 0.2?  This is the thing I call an error and I dont understand.

And thank for all of your replies.  I really appreciate the help.

Renato
#1332
General Help Q&A / Re: Bulb ramping Trouble Shooting
January 24, 2013, 11:15:20 PM
Ok, I have not been able to use the raw deflickering software you provided for 5D3 and the new RawDeflickering package will not install in my Windows machine. 

But..  The main question I have is if the camera can do 1ms repeatability then this would represent a 1% error on a shutter speed of 1/10.  I am measuring error of more that 20% between the raw image and the log file data.  That is what I am pointing out as an error that I don't understand.  I am guessing that there is something fishy in the code that produces these large error when we go below 1 second shutter speed.  A 20% error at 1 ms would be on a 1/200 sec shutter speed but we are getting 20% and even 30% errors between speeds of 1/3 to 1/10.

Remember that what I call error is the difference between the log shutter and the Raw Image shutter.  Also this is something I don't really understand since I though the camera was just taking the photo based on what the software calculates so if the script calculates a 0.2196 seconds shutter speed why is the Raw image come up with 0.33 instead of say 0.2 which would be much closer.  This happens between image 4541 and 4542.  Now considering that 4541 had an error of +26%, then next image with an error of -34% gives a total difference of 50% in apparent brightness change which is very noticeable.  Again this only happens in this range of shutter speeds.

Would it be possible to add a 5 point moving average to the correction as we close to the shutter range below 1s to try to smooth out these errors?  I was watching the camera at this specific point and following the changes manually in my 7D and I could not see why the shutter speed was jumping so much, so what I am saying is that if I was doing this manually I would have just done things slower to prevent the shutter speed jump between images 4540-443.

To illustrate the jumps I put this table:

Image N   Log Shutter    Actual Shutter @ Image N +1
4540          0.2529             0.20
4541          0.2192             0.33
4542          0.1815             0.20

In this particular case the shutter could have remained at 0.2 so why did the camera interpret the 0.2192 as 0.33.  So was there error in the interpretation of the camera or was it the code that interpreted the instruction incorrectly?
#1333
General Help Q&A / Re: Bulb ramping Trouble Shooting
January 24, 2013, 08:06:57 PM
Upon further analysis of the data and comparing the Log with the Photos I have discovered unusual high errors on the shutter speed.  This always happens just after the camera goes from 1 second exposure to the  fraction exposures.  I say that the errors are unusually high because the shutter speed tends to jump in this area more that I would expect.

All of the analysis is based on the Excel Sheet :  http://www.pululahuahostal.com/ML/BRAMP_GRAPH-5D3.xlsx
And the log: http://www.pululahuahostal.com/ML/BRAMP34.LOG

What I have done is obtained the shutter speed from the photos themselves and compare them with the shutter speeds on the Log file.  I noticed that the log has a photo number x but it appears that this information really applies to the (real) photo number x+1.  Also I am assuming that the Photoshop Raw plug in is interpreting the image shutter speed as close as possible since the logs have a different shutter speed.  Again the closest match between the actual picture and the log is by using the photo =log photo number + 1

Assuming that this is correct I am presenting a graph of shutter error which I interpret as the log shutter and what actually shows on the Raw plugin.

The first image is error versus photo number:  http://www.pululahuahostal.com/ML/Shutter_Speed_Error-Vs-PhotoNumber.jpg

As the photo number goes to where the shutter is below 1 s the errors just shoot above 20%

The second image shows the error vs shutter:  http://www.pululahuahostal.com/ML/Shutter-Error-Vs-Shutter_Speed.jpg

I have also noted that the error continues a bit high as the shutter speed gets shorter but definately there are huge errors between shutter speeds of 1/10 to 1/3 .  These errors show significant flickering which only appear in this section of the Timelapse.

I have read MANY places to keep the Timelapse with bulb mode to reduce flicker.  This is absolutely true and these graphs prove this but...

I have done other timelapses in manual mode where the shutter speed in this range does not cause the amount of flicker that the BulbRamp Timelase with ML produces.  This leads me to conclude that there must be an error in the ML calculations as the system moves from bulb exposure to fractional exposures.

Also by reviewing the actual photos I can see this unusual fluctuations on the shutter speed as we move through this specific point.

The Timelapse produced by the unified ML is excellent until you reach this bulb/fraction point, then flickering begins for a  period and then it seems to settle down again.

I use MSU deflicker and get good results but the errors pointed here cannot be removed by deflickering software.

I dont know enough C code to decipher inner working of shoot.c so I hope that someone with this knowlege can take a look at this area where I think (in my opinion) that the script could be modified to reduce the flicker (shutter) errors.

Renato

#1334
General Help Q&A / Re: Bulb ramping Trouble Shooting
January 22, 2013, 04:09:20 PM
As offered, I have created two excel sheets to produce graphs for the BRAMP.LOG

One sheet for 7D (Alpha2)  http://www.pululahuahostal.com/ML/BRAMP_GRAPH-7D.xlsx

One sheet for 5D3 (Unified compile) http://www.pululahuahostal.com/ML/BRAMP_GRAPH-5D3.xlsx

NOTE THAT MY FORMULAS ARE IS SPANISH SO YOU WILL HAVE TO REPLACE THESE FORMULAS FOR THE ENGLISH VERSION.  I HAVE PROVIDED A LIST OF THE TRANSLATIONS IN SHEET 1.  If you make the changes of the formulas then it would be nice if you posted the English version in this thread also.

The reason why they are different is that the 7D log provides a shutter speed in seconds multiplied by 1000 therefore 20 seconds would show up as 20000.  On the 5D3 log it would show as 20 so the calculations are slightly different.

One more trick is required for the 5D3 or unified sheet to work.  In the BRAMP.LOG the shutter speed is in the format xx.xx and my excel program wants a coma instead of a period so you must do a search and replace the entire column of the shutter info.  Search for . (period) and replace with , (comma)  Check your version to see if it accepts commas or periods for the decimals and change the data accordingly if necessary.

1. To open the BRAMP.LOG in excel you need to select all file types (*.*) since excel will not recognize the .log extension. 
2. The import assistance will open and you should click on the "delimited" option, then click on Next, then click on the "space" tick-box, and click on Finish.
3. In most situations the import will be fairly clean but, sometimes I have to fix column C and D because the log does not have a space between the Luma= and its value so it moves all the columns to the left.  Since this is not repeatable you will have to fix this yourself.
4. If using the unified compile you will have to replace the period for a coma in the shutter column.
5. Copy the data from the BRAMP.LOG file to the BRAMP_GRAPH-5D3.xlsx  and pasted it at the first TAB named "BRAMP_Data".  The calculations are done at the "APEX_Calculations" TAB and the graphs are displayed at the next TAB "GRAPHS"

Since this is not an Excel Help blog I will not provide much help so I expect you to know enough about excel to use this sheet.   If you dont know how to use formulas, graphs, etc in Excel then do not even download these files.

If you are good with Python then use the py script provided above by Alex.
#1335
General Help Q&A / Re: Bulb ramping Trouble Shooting
January 19, 2013, 01:25:55 AM
Ok, I made the following corrections:

EV=ABS(-LOG(shutter*ISO/100;2)+K .. this formula agrees pretty well (graphically) to the py graph, but I cannot confirm that it is exact since I cant run the py script.  I am using k=4 to get aprox results but dont know if that is the exact number to use.

I assume that this EV is the "Bulb Exposure" from your graph.

Meassured Scene Brightnes = EV + Y/100 ..  Looks pretty similar (graphically) to the py graph., but I cannot confirm that this is the exact equation.  I understand how EV is obtained from the image but I do not undertand where does the Y value come from.  Is this a value calculated by the camera when you half press the shutter??

I assume that "Meassured Scene Brightnes" is the "Estimated scene exposure level" in your graph.

Any help in understanding this is much appreciated.

Thanks
Renato
#1336
General Help Q&A / Re: Bulb ramping Trouble Shooting
January 18, 2013, 05:43:29 PM
Thanks, that was very nice.  I enjoyed the reading too!  I am an engineer and appreciate the formulas and a deeper understanding.

I managed to get the EV formula to work and used a constant of 10.5 to get values similar to yours.

Now I am stuck on calculating the measured  brightness.  If I add y to EV I get much larger numbers..
for example on the photo number 1872 y = -103 and EV is -10.6. How to add them?
Thanks
#1337
General Help Q&A / Re: Bulb ramping Trouble Shooting
January 18, 2013, 01:06:00 PM
Can you please provide the formulas to calculate the EV graph?  I will put these formulas in Excel for those who not use python. 

I opened the py script but was not able to fully understand the formulas used.

I also ran py under cygwin but it seems that I need to install pylab. I dont want to do this now in case I screw up the installation and later I will not be able to compile autoexec.bin

Thanks for your support
Renato
#1338
General Help Q&A / Re: Bulb ramping Trouble Shooting
January 18, 2013, 05:03:36 AM
Thanks Alex.  That was really great information.

I am not sure how to open py script.  I created and excel file and printed the information on a graph.  There must be some additional formulas in py to get the graph that you displayed.

So Timelapse flicker heavily at some point.  Some transitions are very good but not all of it.

Cam is 7D, intervalometer at 35sec, AutoExpoRamp = Sunset, Max RampSpeed=0.2 EV/shot

Here is Log http://www.pululahuahostal.com/ML/BRAMP24.LOG

Here is my Chart of information in BRAMP23.log:  http://www.pululahuahostal.com/ML/7D-Auto-35-sec-interval.jpg

Here is the excel sheet with BRAMP24.log:  http://www.pululahuahostal.com/ML/Jan-17th-7D-Auto.xls

Any suggestions on what is needed to improve the TL by reducing flicker.

I hate to use your valuable time but I cannot find the answers.  This is just one of many many tries and I am just not getting rid of the flicker.

Thanks in advance for your help!
#1339
General Help Q&A / Re: Bulb ramping Trouble Shooting
January 17, 2013, 04:42:24 PM
The second thing I need help is which values from above are used to make a graph as in link

http://a1ex.magiclantern.fm/bramp/rramirez125-BRAMP01.png
#1340
General Help Q&A / Bulb ramping Trouble Shooting
January 17, 2013, 04:33:30 PM
I am new to this technique and would like to learn and analyze the results of the BRAMP.LOG file.

I have imported the LOGS into excel using fixed width as separators of the fields.

Could someone help me explanain of the following items:

1.  Luma curve: cached: 11,16,25,43,78,128,184,226,248,254,254
     (I assume that is the set of points used in the internal calibration S curve, in which case it only represents the x-value but no y-value is given in this curve.  I assume y value is stored somewhere.)

2.  Reference level: 69 at 65-th percentile  (I assume this is the percentile I selected from the 1st image I took and to be used for the future analysis)

3. Now there is a set of parameters for each image taken that need clarification:

First Column:   Image Number
Luma = xxx  (Luma calculated from new image, how is this calculated)
rounderr= xx (Dont know)
y= xx (Dont know)
r= xx (Donk know)
e=-xx (Dont know)
==> harsh/soft
f= xx
e= -xx (Same as above)
u=- xx
shutter= xx (Image Shutter speed value)
iso= xx (image ISO value)

Thanks
Renato
#1341
General Help Q&A / Re: Magic Lantern - Is it legal?
January 17, 2013, 01:49:29 AM
You guys are awesome, your differences duplicate your strength.  Each one provides what the other lacks, that is the power of independent thinking and open source code!
#1342
General Help Q&A / Re: Magic Lantern - Is it legal?
January 16, 2013, 10:50:36 PM
I am a new user of ML and I am totally blown away by what this software can do.  So I think that once again, the model of open source works, just like in Linux.   I am learning a bit of C and hope that someday I can contribute...

I think that Canon is benefiting from what you guys do and I don't see any reciprocity in this (non-existent) relation.  So what I am insinuating is that it would make your development better and easier if Canon released the code so that your products are even better.

Case in point:  I am dying to have 3X video digital crop in my 7D and 5D.  I think that this is the kind of product that will allow me to make better videos without having to carry heavy lenses; incidentally I could not carry one of those 600mm lenses all day due to my age and size.  So why do ML do not provide this feature?  Because...

1. The development time to reverse engineer this would be huge.  Alex said 0.001% possibility to develop this tool.
2. The FEAR that you (DEVS) may piss Cannon off and that Canon might lock you out on future cameras.  Porting the feature of one camera to another is viewed as a risky process.

So now you have to walk on eggs without getting the real recognition for your work, blocking your development, and blocking the freedom and ingenuity that has gotten you where ML is today.  A great product.

I certainly don't think this is fair for MLs!  Maybe Canon should put forth some type of an agreement to make your hard work count or maybe Nikon should do it.  I just hate to see Canon take advantage of this unfair (non-existent) relation.
#1343
General Help Q&A / Re: Magic Lantern - the best ever
January 16, 2013, 08:40:19 PM
Well, if Canon released the code then this would allow Magic Lantern to become a product that can be sold and you guys could make some money doing  what you like to do.   I would think that ML would then become a successful NASDAQ traded stock.
#1344
General Help Q&A / Re: Magic Lantern - Is it legal?
January 16, 2013, 08:06:04 PM
But to me any Canon issues with hacking should be turned into profit rather that debate.   Lets look at iPhone or any of the successful smart phones.  These platforms allow the hacking and sell you the tools so that you can do a better job.  Who can write a good program for a photographic application?  I think a photographer that uses that app and knows programming will be much more capable of producing a piece of software that is useful.

I think that Magic Lantern answers the need that Canon has failed to address and should be rewarded rather than punished.  I think Canon knows this, and agrees with this statement, and that is the reason why they still allow us to install Magic Lantern in our cams.  It would be really SMART if Canon released the code so that the users can better make use of their cameras.  If Nikon is smarter then maybe they will do it first... 

Renato
#1345
I use Intervalometer to take the stacking picutres in RAW format.  It sure frees up my finger for other more important things like scratching...  ;D  Thanks to ML!

#1346
General Help Q&A / Re: Selft Portrait
January 12, 2013, 12:12:16 AM
Quote from: natasha_r on January 11, 2013, 02:44:09 AM
Any other ways ?

Use Canon Utility Software and conect via USB
#1347
Hola Leandro,

Soy del Ecuador y espero que algun dia pueda presentar algo tan bueno como lo tuyo.  Es admirable!  Felicitaciones.

Renato
#1348
General Chat / Re: SURPRISING !
January 09, 2013, 02:34:33 PM
Obviously they are just promoting Nikon and ML makes Canon better then Nikon.  Therefore they do not want you to present this special advantage.  Except for Video Crop mode where Nikon offers it  in some of their cameras and Canon on only two.
#1349
General Development / Re: Gettings started as developer
January 08, 2013, 05:42:03 PM
Ok, here is a summary of process:

1. Copied ML folder from Alpha 3
2. Copied autoexec.bin from Cygwin/home/PH/magic-lantern/platform/5D3.113  after compiling
3. Downloaded new 5D3-113-bootflag.fir" form Alex post on 5D3 + Dev Kit

With the card (SD 32GB) in card reader

Used EOScard.exe to make boot card.
Run EOScard.exe
Check EOS_DEVELOP checkbox
Check BOOTDISK checkbox
Click on Save

Inserted card into 5D3 and now camera boots normally and ML is enabled.  Hurray!

I will try not to damage the new cam.  I am aware of the dangers.

Thanks for your help.

Renato
#1350
General Development / Re: Gettings started as developer
January 08, 2013, 04:57:52 PM
Thanks for your reply.

I did all of it, updated the firmware and the camera boots to firmaware update.  When I press trash button there is no ML menue.

In Canon Firmware Menue it appears that has loaded...  But still there is something wrong.

Thanks