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 - surami

#26
General Help Q&A / Re: Compiling in the Cloud
April 12, 2015, 09:01:05 PM
@garry23:
Delete your old Codio project and make a new one, after that:

1. Tools -> Install software -> Install the ZIP
2. Tools -> Terminal (copy the following code):
cd
curl -OL https://launchpad.net/gcc-arm-embedded/4.8/4.8-2013-q4-major/+download/gcc-arm-none-eabi-4_8-2013q4-20131204-linux.tar.bz2
bzip2 -d gcc-arm-none-eabi-4_8-2013q4-20131204-linux.tar.bz2
tar -x -f gcc-arm-none-eabi-4_8-2013q4-20131204-linux.tar
curl -OL http://prdownloads.sourceforge.net/docutils/docutils-0.12.tar.gz
gzip -d docutils-0.12.tar.gz
tar -x -f docutils-0.12.tar
cd docutils-0.12
python setup.py install --prefix=~/.local
cd
export PATH="$HOME/.local/bin:$PATH"
echo "export PATH=\"\$HOME/.local/bin:\$PATH\"" >> .bash_profile
cp .local/bin/rst2html.py .local/bin/rst2html
cd workspace
hg clone -r unified https://bitbucket.org/hudson/magic-lantern
cd magic-lantern/platform/5D3.113/
make zip

3. Hit enter at the end.

If you want make some modifications in your files before you compile, then leave the last 2 lines out. After the modification you have to be at the "xy@z:~workspace $" and you have to run the last 2 line.

You will not have the following modules: raw_rec, dual_iso and dot_tune, because of the gcc 32bit issue.

4. Project -> Export as ZIP.
#27
@garry23: Make a new project and if you are at install software step, where you have to install zip, install the python3 too.

Somebody knows, how to solve the gcc 32bit issue? (dual_iso, dot_tune, etc. modules couldn't be compiled)
#28
I wanted to compile today a fresh unified build on the Codio, but I got the same errors as garry23 wrote, eg.:
Building module mlv_rec...                                                                                                                                                                                                                 
Updated HGVERSION                                                                                                                                                                                                                         
[ README   ]   module_strings.h                                                                                                                                                                                                           
cat README.rst | grep -v -E "^:([^:])+:.+$" | rst2html --no-xml-declaration | python ../html2text.py -b 700                                                     
                                                                                                                                                                                                                                           
/bin/sh: 1: rst2html: not found                                                                                                                                                                                                           
grep: write error: Broken pipe                                                                                                                                                                                                             
                                                                                                                                                                                                                                           
(<type 'exceptions.SystemExit'>, SystemExit(1,), <traceback object at 0x2b27e9af0f38>)                                                                                                                                                     
make[4]: *** [module_strings.h] Error 1                                                                                                                                                                                                   
                                                                                                                                                                                                                                           
********************************************************                                                                                                                                                                                   
WARNING: module mlv_rec failed to build, deleting                                                                                                                                                                                         
********************************************************


I used the same line from the OP:
wget -q -O - http://pastebin.com/raw.php?i=jfVXzw1a | sed "s/\r//g" | bash
cd magic-lantern/platform/550D.109/
make zip
#29
If you are not a coder, it's better to wait for the right person. I compiled my first build on this week, so I'm not a pro in this.

Ask for help here.
#30
Which ML build version?
#32
Problem solved! I think my Pixel TF-321 hot shoe PC sync adapter didn't transfer the right signal to the MX2, so I bought another simple hot shoe PC sync adapter and now the triggering happens right after as shutter is closing (independently from shutter time length), perfect! :)

If you combine the intervalometer + the advanced intervalometer module (eg. with AV ramping) + the ETTR module (Always ON) + LUA scripting module (with this "Force Delay" script) you can get a nice day to night/night to day timelapse sequence with some motion. ;) I will test this soon.
#33
Custom test build from branch LUA scripting (ffcf212) for 550D:

Compiled with Codio:
1. hg clone -r ffcf212 https://bitbucket.org/hudson/magic-lantern
2. "Makefile.modules.default" changes in folder modules:
MODULE_CFLAGS += -I../../src/
ML_MODULES_STATIC ?=
ML_MODULES_DYNAMIC ?= file_man pic_view ettr silent deflick mlv_play mlv_rec mlv_snd lua

3. cd magic-lantern/platform/550D.109
4. make clean && make zip

Additional changes after compiling and downloading the zip:
- all files deleted in scripts folder
- added "forced_delay.lua" script file in the scripts folder (thanks dmilligan!):
menu =
{
parent = "Intervalometer",
name = "Force Delay",
help = "Add an extra delay to each interval",
min = 0,
max = 300,
unit = UNIT.TIME,
}

events =
{
intervalometer = function() msleep(menu.value * 1000) return true end
}

- custom cropmarks: hd.bmp + cinema.bmp
- copied "dual_iso.mo" from latest nightly build (because gcc 32bit isn't working on Codio cloud service and it couldn't be compiled, it's a 64bit system)
- so modules folder: adv_int.mo, deflick.mo, dual_iso.mo, ettr.mo, file_man.mo, lua.mo, mlv_play.mo, mlv_rec.mo, mlv_snd.mo, pic_view.mo, silent.mo

!!!Read the OP here!!!

// Outdated build removed.  Audionut.
#34
Scripting Corner / Re: LUA Scripting (lua.mo)
April 07, 2015, 09:45:24 PM
Thanks for the links. I could compile a build + LUA scripting module for my camera with Codio. It was my first try to compile something and it took some hours to figure everything out, but it seems so, that the "Force Delay" script works perfectly. I hadn't tested yet in the field outside with AutoETTR always ON or with Advanced Intervalometer module, but as I have more time I will make it and report back again.

OFF topic: Now I'm waiting for this Flash Hot Shoe Sync Adapter, I would like to use this as triggering the MX2 controller by DP. If it works, we can make nice day -> night/night -> day timelapses with some motion. (The Pixel TF-321 hot shoe sync adapter didn't worked for me, don't know what was the problem.) In theory there will be enough time (independently from interval time) during the shooting between the exposures for calculating the right ETTR picture and trigger the MX2 to move the cart on the slider and move the Merlin head.

Update: I got my simple hot shoe PC sync adapter and it works perfectly, solved.
#35
Scripting Corner / Re: LUA Scripting (lua.mo)
April 07, 2015, 03:01:14 PM
Thanks for the example David. Could you please send me a LUA.mo download link in private for testing purpose or should I wait for a more stable version?
#36
Scripting Corner / Re: LUA Scripting (lua.mo)
April 05, 2015, 03:09:23 PM
I would like to run a script, which would be enabled when the picture is taken with the intervalometer and the AutoETTR module (+advanced intervalometer module) are also in use. The idea is to force a delay (4 seconds) between the shots independently from interval time.

I'm not familiar with LUA scripting and compiling the LUA module, but as I read on the API page, I should use the event "intervalometer" and the global function "msleep". The modules wouldn't do any confusion? I would like to learn and understand, that how I could do this.
#37
Scripting Corner / Re: LUA Scripting (lua.mo)
March 30, 2015, 04:17:02 PM
Is that correct, that this will be the replacement of the old script.mo?
#38
I like this, it's great!
#39
@Pelican: It's very good idea, but I couldn't setup things in the menu Flash control/External flash func. settings earlier because as I entered into the menu, this was what i saw: "This menu cannot be displayed. Incompatible flash or flash's power is turned off."

@ansius: Thanks for the advice, I will clean the socket.

Yesterday evening I disassamled that TF-321 hot shoe stuff, because I thought there is too much connections (5 in the middle and 1 on sides) to the camera's hot shoe mount and the connections should be reduced, maybe this could cause signal lost or I don't know. I thought this because that Hama stuff has only 1 connection in the middle and 1 on the sides. (topside, bottomside)

Now my Pixel TF-321 is dead, because I operated on the stuff too much... I'm amateur and curious. :D

We will see what happans on the next week or as soon I can get a Hama hot shoe stuff. I hope a simpler hot shoe stuff will do the job.

@ML developers: Is it possible to implement a delay option into the Auto ETTR mechanism? Maybe that 2 sec delayed exposure is too weak for saving the picture, calculate the ETTR things and for the motion.
#40
OK, then let's forget this USB trigger thing. Yes, I don't know what's possible and what's not through USB port. I just asked, because my camera + hotshoe mounted PC sync cable + MX2 I/O port chain isn't working properly. I set up everything as MX2 guys told (there is an option what you wrote, invert I/O, it's needed), but sadly the triggering isn't happening in the right time, it works the same way as the I/O port wouldn't be inverted.

I tested (as Jay suggested from Dynamic Percepton) the PC sync cable connected to the MX2 controller's EXT1 port (I/O 2 external invertvalometer + inverted I/O setting) with shorting the sleeve and tip, so I could simulate long exposure with holding the circuit closed. As I opened the motion triggered imediatly, the cable is ok. So wether that Pixel TF-321 stuff or my camera isn't working properly. I will order next week this kind of Hama hotshoe PC cable stuff.
#41
I think I have to explain, why I would like to use this kind of function.

I would like to give motion to my day to night sequence. It's not problem if I only use the ML's ETTR function (always on) with slowest shutter 8 sec + MX2 interval time to 10 sec. (Shoot -> Move -> Shoot). But this settings aren't enough for a really cool day to night (many stars) sequence, a 25 sec exposure should be needed at max ISO 3200, F2.8 (the 550D has not a world champion sensor, so this ISO is also too much for it, but anyway) and the motion shouldn't happen in that time when the shutter is open.

In theory the right way would be to use the ML's intervalometer (eg. 10 sec) + ETTR always on (slowest shutter 25 sec) + 2 sec. delayed exposure (Canon setting) + MX2 with external intervalometer setting. Why this settings? Because:
- 10 sec interval is quite good for a sunset + the ETTR will expand this time as needed for a proper ETTR picture at night
- 2 sec delayed exposure is needed to save the picture, set up automaticaly the new ETTR settings and give enough time for motion before the next circle
- ML should send a signal to the MX2, that the motion should happen right after the shutter closes
#42
Is it possible to send a "T" character through the camera's USB port with a proper USB cable to trigger the MX2 controller?

Please take a look at the TimeScapes forum, I'm not at home at this kind of engineering things.

I ask this because I would like to trigger the MX2 as the shutter closes, but my camera's hotshoe + Pixel TF-321 + PC sync cable isn't working well, the triggering happens as the shutter opens.
#43
I know it's an old topic, but anyway...

Could somebody explain, that how could I trigger the MX2 to move the Dynamic Perception Stage One Dolly + Merlin head. I would like to use the Auto ETTR function + the intervalometer in ML, so during a day to night/night to day shooting the interval could be different (forced way) and I could give some motion to my timelapse.

I have this Pixel TF-321 hotshoe stuff on my camera and it's connected to the MX2's I/O port (EXT1). If I start the intervalometer in ML, it seems so that the MX2 doesn't get any signal as the shutter closes. Earlier this function worked as I remember.

I found this information on DP's facebook page and on Vimeo too (please read Vimeo description + comments).
#44
@dmilligan: is your deflickering script works too with the older ACR process version (2010)? I would like to get back shadows and recover highlights detail in my timelapse (sunny, cloudy, sunny, cloudy) with the fill light and recovery sliders. I read somewhere that it doesn't produces so kind of flickering troubles as the touching of the shadows, highlights, blacks, whites, etc. sliders in the new ACR process version (2012).

... or somebody knows a workflow for getting back shadows and recover highlights without additional flickering?
#45
@Frank7D

Thanks for your time to check the MLVs.

This mentioned trick isn't working for me. Another converter like raw2cdng produces good DNG sequence, what I can import into AE, but it would be better not to store unnecessarily the files.
Ayshih, please come back for an update :) or where lies the rub?

#46
@Frank7D

Yes, I'm using Pismo File Mount + the latest mlvfs.dll (by ayshih). As I remember the old MLV was created with a nightly build from previous year, somewhere in april and the new MLV is created with a build from this year, january. Are you using Pismo too? If yes, could you try the files.

I get this error in AE "the file format module could not parse the file" 45::35, when i try to import the new MLV's DNG sequence. I can adjust the settings in ACR, but after click on OK, the error window comes into my face.

In theory the mlv_rec modul should be the problematic thing or not? I think this because everything works perfectly with the old MLV.
#47
Any news for a Windows update? I can't import new MLVs (DNG sequences) into AE... the interesting things is, that old MLVs (DNG sequences) are working properly. Is this because of the version differenc of MLs? What can cause this thing?
#48
@classicbs: The idea of using the visionlog raw camera profile came from the post #260, they spoke about flat images... ;)
#49
@classicbs: Maybe this workflow will help for you. I could get the best results till now:
1. Delete your old XMP-s (or save them somewhere as backup).
2a. In LR read in the metadatas for your sequence. Select all files on the library tab (ctrl + a) -> right click metadata -> read metadata.
2b. In LR set custom whitebalance for your files + crop for 16:9. Select all files on develope tab -> switch on autosync -> basic settings: wb custom + crop overlay: aspect 16:9. -> save metadatas (ctrl + s)
2c. In LR set 1 star for your keyframes + adjust the settings for them. Rightclick on the selected images -> set rating: 1 star (switch off autosync!) + filter for 1 star -> adjust the settings for the keyframe as you wish (don't touch the shadows, highlights, blacks, whites) -> save metadatas again.
3a. In BR select all files and right click -> purge cache for selections. Now you will see the settings, what you did in LR.
3b. In BR select all files and run David's awesome ramp multiple script (check all), wait till the process ends.
4a. Before you deflicker the sequence I suggest you to download the visionlog raw camera profile (read the installation guide) and apply it. This will help the deflicker script to work more properly.
5. In LR setup the visionlog raw profile for you sequence. Read in the metadatas for your full sequence (filters off) on the develope tab -> switch on autosync -> camera calibration, profile: visionlog -> save metadatas.
6a. In BR select all files and right click -> purge cache for selections. Now you will see very flat images.
6b. Run deflicker.
7. In LR read metadatas for your sequence and swicth back your camera profile to adobe standard -> save metadatas.
8. In BR select all files and right click -> purge cache for selections. Now you will see everywhere the final multi ramped deflickered sequence.

Maybe it's too long to read and every settings could be done in BR + ACR, but I like the LR's layout.
#50
It looks something like osiris.