Nightly Builds - try the very latest stuff here

Started by a1ex, October 11, 2012, 01:55:31 PM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

Towndown

For ten days they add new features, then for the rest of the month they fix things. ... Be sure to read the following pages before trying these out: ... You could expect breakage when running which can be downloaded from here. Nightly Builds. Nightly Builds are made on a daily basis and contain the most recent changes.
juicy velour fsession

Fashion theme

a1ex


Doyle4

No breakages... just bugs :) stop scaring people  8)

albert-e

Quote from: Towndown on February 05, 2014, 07:14:13 PM
For ten days they add new features, then for the rest of the month they fix things. ... Be sure to read the following pages before trying these out: ... You could expect breakage when running which can be downloaded from here. Nightly Builds. Nightly Builds are made on a daily basis and contain the most recent changes.

I forgive you; you're new to ML. Hang in there, in time you'll see how great ML is!

Stedda

This guy is spazzzzzing out on random threads....
5D Mark III -- 7D   SOLD -- EOS M 22mm 18-55mm STM -- Fuji X-T1 18-55 F2.8-F4 & 35 F1.4
Canon Glass   100L F2.8 IS -- 70-200L F4 -- 135L F2 -- 85 F1.8 -- 17-40L --  40 F2.8 -- 35 F2 IS  Sigma Glass  120-300 F2.8 OS -- 50 F1.4 -- 85 F1.4  Tamron Glass   24-70 2.8 VC   600EX-RT X3

dmilligan


kopir

Hello,

Just tried 3 different nightly builds (Feb 8, 2014; Dec 16, 2013; Nov 16, 2013) for 700D camera.
I don't see Auto ETTR option on Expo page. Is it no longer supported or is it 700D-specific problem or am I doing something wrong?
I was originally looking for Bulb ramping feature but found that you depricated it in favor of AutoETTR. I don't see ether in latest builds.
I am trying to use your software for a first time so it could be that I am doing something wrong.
Please advise.

Audionut

Provided you have copied all of the files from the zip to the card, you need to enable the module from the module tab.

kopir


RogueFive

last 2 builds for the 600d are broken for me, reverted back to magiclantern-v2.3.NEXT.2014Feb10.600D102
no error message, just blinking light on startup, black screen

(sorry, lost my account info, starting over)

MrComputerRevo

Quote from: RogueFive on February 12, 2014, 03:31:09 AM
last 2 builds for the 600d are broken for me, reverted back to magiclantern-v2.3.NEXT.2014Feb10.600D102
no error message, just blinking light on startup, black screen

Same for me on 600D. It gives 2 long and 3 short blinks (if that makes any sense) and just does that over and over again. Latestbuild that works is from 10th of February.

beemanpl

Quote from: MrComputerRevo on February 12, 2014, 11:03:46 AM
Same for me on 600D. It gives 2 long and 3 short blinks (if that makes any sense) and just does that over and over again. Latestbuild that works is from 10th of February.

I have the same problem...
600D, 18-55 kit

dmilligan

looks like some changes pushed the binary size over it's limit

from http://builds.magiclantern.fm/jenkins/job/600D.102/199/consoleText

Program Headers:
  Type           Offset   VirtAddr   PhysAddr   FileSiz MemSiz  Flg Align
  EXIDX          0x06f0e4 0x00cef0e4 0x00cef0e4 0x00008 0x00008 R   0x4
  LOAD           0x000100 0x00c80100 0x00c80100 0x6efec 0x8093c RWE 0x100


MemSiz needs to be less than 0x80000 (we have the same problem on 1100D)

a1ex

Solved. Didn't disable anything, just cleaned up some unused stuff.

RP9

Hey guys,

first time on this forum, so hey everybody :D
I already gained some experience with ML as I previously used the Beta on my 5Dc  a lot (worked like a charm). Having bought myself a new toy last week, a brand new 5D Mark II, and using the stable ML 2.3 since then, I'm now willing to give the ML 'Nightly Builds' a shot.

Most of the features seem to work pretty well and the new design is also a big improvement. However, there seems to be a huge bug within the latest NB. Whenever I want to switch off the camera (or manually choose the automatic "Sensor cleaning") the camera crashes while showing the sensor cleaning screen for ages. I have to remove the battery to continue.

If I can help with log-files or similar just let me know!

Best.
RP9



 

a1ex

Are you sure the bug is present in the latest nightly?

RogueFive

Quote from: a1ex on February 12, 2014, 02:06:43 PM
Solved. Didn't disable anything, just cleaned up some unused stuff.
:D works like a charm, thank you for the fast service!

federico.albertini

600d now is working perfectly again (2014Feb13.600D102)
Thank you guys!
:D

Arthur Rambo

Hello beautiful people !
I have been shooting 4 days in a row ( in a raw ^^)  with those nightly builds : 06_02_2014 * 07_02_2014 * 08_02_2014
Everything went smooth, except one thing. For no apparent reasons, the frame rates skipped randomely from 25 fps to 29.776. I'd say one clip went wrong every 8 "good" 25 fps clips. I only noticed that when I converted my MLV to DNG sequences (thanks to Tony and his great mlv converter : http://www.magiclantern.fm/forum/index.php?topic=10198.0 )

I'm on a 5D Mark III
Global Draw : On all modes
Cropmarks : On
Raw video (MLV) : 1920x818 (2.35:1), Global draw : Allow

Is it a known bug ?
Thank you a lot !
Samuel

Jason Montalvo

Quote from: Arthur Rambo on February 13, 2014, 01:18:35 PM
Hello beautiful people !
I have been shooting 4 days in a row ( in a raw ^^)  with those nightly builds : 06_02_2014 * 07_02_2014 * 08_02_2014
Everything went smooth, except one thing. For no apparent reasons, the frame rates skipped randomely from 25 fps to 29.776. I'd say one clip went wrong every 8 "good" 25 fps clips. I only noticed that when I converted my MLV to DNG sequences (thanks to Tony and his great mlv converter : http://www.magiclantern.fm/forum/index.php?topic=10198.0 )

I'm on a 5D Mark III
Global Draw : On all modes
Cropmarks : On
Raw video (MLV) : 1920x818 (2.35:1), Global draw : Allow

Is it a known bug ?
Thank you a lot !
Samuel

Are you shooting in crop mode? Whether you are or not enable FPS Override in the movie menu of ML and select your desired frame rate, then select exact fps as the mode.

That should do the trick.

Arthur Rambo

Hi Jason,
Yes, I shot in crop mode to reduce the amount of data.
Thanks a lot for the trick, I wasn't aware of this solution !
Samuel

Jason Montalvo


RP9

Quote from: a1ex on February 12, 2014, 11:21:09 PM
Are you sure the bug is present in the latest nightly?

Nope, just tried out the Feb13 NightlyBuild. The camera now switches off correctly after showing the sensor cleaning screen for some seconds.

But now the sensor cleaning screen comes up directly after I switch the camera back on and stays there until I press a button.

As in the previous build, when I manually trigger the "automatic sensor cleaning" out of the Canon menu, the camera only shows the screen (and also stays there until I press a button), but it doesn't seem to do the full procedure as there is absolutely no sign/sound of mirror movement.

a1ex


a1ex

Just updated nightly builds; the most interesting stuff IMO is:

- memory backend updates (this one is huge, I expect massive improvements in overall stability)
- pink frame fix for 5D3 (I've only tried on 123, let me know if it works on 113)
- partial pink frame fix for 60D (seems OK in crop mode at 2.5K, but still got pink frames at 60fps)
- for 5D2, another attempt at sensor cleaning fix

From ayshih:
- [50D] TL backport: display filters (ML grayscale preview, anamorphic, etc.) work now
- [ALL] mlv_rec: global draw is restored after finishing a recording

From mk11174:
- audio remote shot on 650D/700D

Some more notable updates from the past few days (already old news for many of you, but maybe not for all):

- from dmilligan: multi-level submenus
- from mofig: more slit-scan modes, including a finish-line camera mode
- from viniciusatique: movie restart on 5D3
- from Marsu42: tweaked warnings on bad settings
- from nanomad and dmilligan: photo raw and dual ISO on 1100D (old news already)
- from escho: cold pixel fix in raw2dng (also old news, work in progress for mlv)

Note: there are some failed builds that lack a stub for memory backend. Just find that stub and these builds will be resumed.