Messages

Not sure if this has been mentioned but the latest version of PFMAP-171-win works fine in W8.1 (64bit) for .mlv files.  It doesn't/can't? successfully mount any .M00, M01 etc files.

All the files that I've tested with didn't have any embedded sound so I don't know if it works with an MLV with Audio file. Something to try another day and report the outcome.

Happy Birthday Chmee. Hope your party rocks/ed

You didn't inadvertantly have encryption enabled on the morning of the first day?

Image links are not working.

Thanks Walter.  Correction made to the post.

Correction to card format... I checked my cards and they are FAT32 not ExFat.  Thanks Walter for the correction.

Just realised how old the post I responded to was - feel free to ignore  .

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Which version of EOSCard were you using? How many cards 128gb cards do you have?

When you say that you can't get it to work what does this mean exactly e.g.: ML won't load or it loads but won't run etc.

I have recently purchased 3 x 128gb 1000x Komputerbay cards and all have successfully been made them bootable with EOScard v1.40.

The process that successfully worked for me on all three cards follows:

   
•     I formatted my cards on the PC first (ExFat FAT32) using the default cluster size, then
•     Format again in the camera. This ensures that the card is formatted the way the camera likes it and creates the required DCIM and MISC folders. Then,
•     Insert the card into a compatible card reader.
•     Launch EOScard, click on refresh and verify that the card is being detected.
•     Click on the ML logo. In the "Strings" section, EOS_Develop and Bootdisk check boxes should now be checked. If they are not, check them on yourself.
•     Given that you have a have a 5d mark II check the "unified stable v2.3 and select your model camera from the drop down list.
•     Click on SAVE. this will make the card bootable, Install the autoexe.bin file and the stable version of ML onto the card.
      (note that I have a 7D, for me this step did not create the DCIM and MISC folders - so step 2 above is important or you will need to create them manually).
•     Via file manager, check that the autoexec.bin, the ML folder (and its sub-folders) the DCIM and MISC folders are all present.
•     Download the latest nightly build for you camera from the ML forum website.
•     Expand the nightly build ZIP file on the PC, delete the autoexec.bin and ML folder off the CF card and then copy the latest autoexec,bin and ML folder from the
      nightly build to the root of the CF card.
•     Repeat step 8. If all OK, make sure that you eject the CF card before removing it from the card reader.
•     Try it in the camera.

I don't own a Mac so all of the above is done using a windows PC.

Note that it is important to always eject usb devices from the computer correctly or corruption can and from 1st hand experience, does occur.

Also you might want to try a different card reader. If the one that you are using is a bit old then there may be some compatibility issues with it.



link to EOScard v1.40         http://pel.hu/eoscard/

I appreciate that you may have tried any or all of the above but sometimes the sequence of events can mean the difference between success or not.

It can't hurt to give the above process a try, if it works, fantastic, if not then you may have a dud card.

Cheers

Nice video and a great charitable concept.

Agree with dmilligan. Try setting ML back to its defaults and see if the issue still exists. Check your camera mode as well, may that has been changed to something that would result in excessive overexposure.

[The Set-up]

I've been using ML since it was released for the 7D and the developers have all done a fantastic job in bringing extended functionality to the supported Canon DSLRs. Such an array of functionality that interacts not only with the Canon firmware but also a multitude of individual ML options does, for this black duck anyway, make for an interesting exercise when setting up for a shoot. ML and the contributions from the members here has given me the drive to step way out of my comfort zone.
Enough of that. I decided to get my head around the focus stacking workflow from set-up through to post processing. After much reading of the forum and viewing of the odd YouTube video I thought that I would give it a go. The following is a sharing of my experience.


The Set-up

   
• Canon EOS 7D
• EFS 18-55 IS lens
• Komputerbay 128gb 1000x CF card
• Latest official ML build.
• A good sturdy tripod – mandatory.
• A macro LED ring light that was hand held off the camera to provide some side light and augment the standard room lighting.
• A glass bowl full of coffee capsules and a couple of metal cups with stirrers.
• Stone bench top in the kitchen.

Post Processing Software:

   
• W8.1 Professional
• Lightroom
• Photoshop
• CombineZP (Freeware) – alternative to lightroom and Photoshop
• BarracudaGUI for Dual_ISO processing

Camera set-up
Nothing clever or sophisticated here.

   
• Auto power-off disabled in the Canon menu.
• Live view enabled
• Initial trials:            ISO 100, f5 (for a deliberate shallow DOF), Av priority, output jpeg, Adobe RGB
• Subsequent trial:    ISO 100, f5(for a deliberate shallow DOF), Av priority, output RAW, Adobe RGB
                                  I thought that I had set ML back to its defaults before starting this exercise but I had
                                  inadvertently left Dual_ISO enabled. So I have one sequence with Dual_ISO files and
                                  another with straight RAW.
• Camera was mounted on the tripod as close to the subject as possible while still being able to obtain an easy auto focus lock.

For this process to work, the camera absolutely has to be static as does the specific subject that you are focusing on. I'm not sure what the outcome would look like if there was any background movement whilst the sequence was being taken. (Something to try on another day).

The Focus Stack Process

In the ML menu enable follow focus. You need this to drive the lens focusing mechanism whilst setting your start and end points.



Set the focus start and end points of the focus stack. This is a two step process and setting them is a little confusing as you set both via the one parameter. (It would be great if ML was modified to split them into separate parameters). The screen shots below depict examples of the start (0 steps and end points (-8 steps).
If I'm understanding the process correctly, in this example the focus range for the stack will be 8 focus steps behind the start location The actual distance of each step may vary depending on your lens.


   



Having set the start and end points, executing the rack focus will drive the lens through the stack range from start to end. Executing it again will drive it from end to start. I found this useful to see if I had set my range correctly.





Lastly, set the actual parameters that the will be used to run the focus stack. Note that the number of pics taken is automatically calculated.




If the start and end points have been perfectly set you can probably leave the Num of pics and in front and behind set to zero. I chose to add a few additional frames just in case and discarded those not required when post processing.

I wanted as many slices as possible for my focus stacks and as such set the focus steps/picture to 1. If you are using a higher f stop with a greater natural DOF you can increase this and reduce the number of pictures taken.

To capture your stack, just highlight Run focus stack and press set. Sit back and let the magic happen.



Post Processing
From a post processing perspective all that I was trying to achieve was to merge the stack and produce an image that was in focus from front to back of the subject. Other than a little cropping the outputs are in line with the applications out of the box default settings.


Light Room/Photoshop
Light Room was used to export the images for editing directly into Photoshop as layers. If you know you way around Photoshop you can dispense with Light Room. Then it's a matter of aligning followed by merging the layers.
One would think that the Align layers and Merge Layers function would be under the Layers menu in Photoshop. They are actually under the Edit Menu (really intuitive – NOT).
Depending on the number of layers and the horsepower of your PC, the above can take some time. At the end you are rewarded with a photo that is in focus across its entire depth. There will be some fuzzy edges that you will want to crop away and there may be some minor out of focus spots in the photo. Manually correcting these when working with layers is beyond my skill level at present.
Pro's – Handles anything that you can throw at it.
Con's – Expensive.

CombineZP
I picked up on this application in an old thread in the ML forum. It is Windows only and can be downloaded via the following link:
http://www.hadleyweb.pwp.blueyonder.co.uk/
If you are running a current version of Windows e.g.: w8.1 you need both the msi and the zip file. It's functionally very powerful and produced excellent results.
The simple process is to import the files and run a batch job that aligns and merges them ready for outputting in a supported format.
Pro's – It free, fast, lot's of user feedback whilst executing various steps and the output was comparable to Photoshop.
Con's - It's not a PhotoShop alternative (it's not meant to be), It's not very intuitive and I needed to read the available help and experiment a fair bit before I was
            comfortable enough with the functionality that I wanted to use.
           Also it doesn't support RAW or DNG format files and TIFF output was broken.


I'm sure that there are other products available that will do the job. Someone else might be able to provide some feedback on those.

Example Photos
This example had 10 slices, input were large jpg files. The first image is from Photoshop and the second from CombineZP





The following example had 10 slices and used processed Dual_ISO DNG files in Photoshop. CombineZP didn't recognise the DNG files so there is no comparison.




My final example had 10 slices, input were RAW files in Photoshop. CombineZP didn't recognise the RAW files so there is no comparison.




Cheers, I hope you found this useful.

Links to buf_raw and buf_bolt appear to be broken.

I still keep one CF card with TL installed on it so it would be nice to be able compare this to bolt_raw.

No it didn't.

Today I decided to reset ML back to default settings and try again in case I had some conflicting setting enabled.

This seems to have resolved the issue. I aso changed the order that I established the intervalometer and advance intervalometer settings.

In this attempt I:
- set the key frames first,
- then enabled the adv_Int function
- then set the intervalometer parameters
- lastly enabled the intervalometer
- Turned on liveview.

In my original attempt the workflow was in the reverse order (I'll try his again and see if it was the issue, I expect not)

So I guess all good. Thanks for your efforts in developing and supporting this module.

Time to get more adventurous.

Cheers.... Otto

From dmilligan

here's an example, to ramp Av from f/22 to f/4 in 20 frames do this:

   
• set the Av to f/22 in canon
• go into ML menu
• A > New Keyframe...
• Select "Aperture" menu item and turn it ON (this means this parameter will be included in the keyframe)
• Select "Create Keyframe"
• go back to canon and change the Av to f/4
• go into ML menu
• A > New Keyframe...
• Change "Keyframe Time" to 20
• "Aperture" should still be "ON"
• Select "Create Keyframe"
• Go back up one level and select "List Keyframes", you should see two, T=1 and T=20

You can set keyframes based on time of day as well, just turn "Use Global Time" on, then in the "New Keyframe" menu under keyframe time, you sill see a time (hh:mm:ss) rather than frame # (and on the right side is the current camera time)

To change a keyframe you already created, you can set the keyframe time to the time of the keyframe you wish to edit (if you do this you will see a warning that you will be overwriting an existing keyframe).

I have installed the adv_int module on my 7D today and tried the above example. I have tried it both in manual and AV mode without any apparent success. Whilst the intervalometer takes a photo at the defined time intervals there is no change in the aperture. Each photo is taken using whatever aperture happens to be dialed in on the Canon at the time. Esssentially every photo is exactly the same bar any movements due to the time differences.

Have I overlooked some critical preparation step/s not detailed in the example? or does it not actually work on the 7D?

Any thoughts?  Thanks in advance for any suggestions.

Whilst I don't use all of the features of ML, for those that I do, I've found it to be very stable.

Cheers... Otto

Try the following link for an up to date list of supported features on the cameras supported by ML.


http://nanomad.magiclantern.fm/jenkins/features.html

Hi,
The most recent nightly build appears to be Aug 8. Is something broken?

Cheers... Otto

Hi,

On my W8 pc running v0.3.5.0 of BarracudaGUI, the application hangs (no error messages).

Original content of this post deleted as I found out what the problem was. i.e.: the input file path cannot have spaces or the exiftools background processes hang.

Can the script be changed to pass the file paths wrapped in quotes?  This should eliminate the problem.


Cheers... Otto

Thanks. Do we know what modules it interacts with or visa versa?

Sorry, I may be missing something here. What is the purpose of this module?

Thanks to Pelican for his hard work and to Pileot for well documented guide.

3 x CF cards built and working perfectly with my 7D.

Time to experiment...... Cheers - Otto

If everyone keep asking for stuff, and the developers (g3gg0,?) keep trying to oblige then Alpha3 will be a loooooong wait.

Also, if you have friends with a 7d and or you haven't downloaded Alpha2 then get behind the product, download and try it. 7D Alpha1 - 25534 downloads, Alpha #2 - 213....... Not much incentive to devote a lot of time and energy.

Playing with alpha2 and patiently waiting for Alpha3

hi,

there is nothing new regarding to 7D-specific issues like:
- cpu load with HDMI monitor attached
- flush rate hacks with audio enabled
- fps override not available

all the other changes happening in main repository also work on 7D.
as the menu changes seem to have settled, i can check whats missing on 7D before making the next alpha.

Great news G3gg0.  Hope a solution to the fps will ultimately be found.

Looking forward to the next release.

Cheers.... Otto

Almost as if the battery overheated or something even though that's impossible with no sensors. Strange.

Lithium Ion batteries go feral when they overheat - I haven't had a problem with my camera but  have experienced the same thing with my notebook battery. Unplug it and let it cool for a while and all is good again.

A question on the nightly builds.

Can they be applied to the 7D alpha and if so how?

Hi just wondering when the fps override will be available for the 7D.  I had a play with the intervalometer for timelapse and it worked fine but it gave the shutter mechanism a workout. Looking to try the same experiment using fps override.

Cheers.... Otto

Thanks g3gg0.

It just took a while me to have an Ah Ha moment and connect the dots to the behaviour that I was experiencing with the camera.

There are new scars on my forhead after banging it on a brick after I realised my mistake.

Lots o ffun things to experiment with. thanks for a great app

Cheers.... Otto