Messages

IPV6 aren't supported in 2.0.x and won't be. This is an error fixed for 2.1, but it won't be fixed for 2.0.x.

http://www.simplemachines.org/community/index.php?topic=543919.msg3862603#msg3862603
http://www.simplemachines.org/community/index.php?topic=548191.msg3888245#msg3888245

if it is so and ipv6 is not supported by forum, you should disable ipv6 on server and/or remove aaaa from dns.

With IPv6 enabled, I get only error

Code Select Expand

Data too long for column 'ip' at row 1

is it good new for ML development? I suppose, it's not compatible with current ML?

Load raw_diag (first post), enable "Dump RAW Buffer" and "Optical Black Zones", disable all other analysis options, then take a picture. Once you found a picture that triggers the error, upload the DNG and the screenshot.

how to use this module? If I enable "RAW diagnostic" and take picture or execute XXX Bracket, I get only standard photo and "raw error" and nothing else.

[10th Mar.: Alpha4]

10th Mar.: Alpha4 in red color asked everybody to do but no one cared about. Might not help but give some hints perhaps.

In simpler English please. Is still required some test? What to do? I don't see raw diagnostic included in beta-3b as it is written in alpha4.

randomly this variants
1. Trap focus -> continuous -> set -> HlfShutter -> led permanently shines -> {trap focus ok}
2. Trap focus -> continuous -> set -> HlfShutter -> short led blink -> {no trap focus} -> HlfShutter -> led permanently shines -> {trap focus ok}
and then
{trap focus ok} -> shutter halfway (http://wiki.magiclantern.fm/userguide#trap_focus) -> {nothing, trap focus continues}

randomly problem with photos taking on focus:
{trap focus / both variants) -> (slow focus changing or object position changing)-> {focus taken - beep} -> {nothing, no photo}

edit:
problem with camera start with active trap focus
1. (camera on with trap focus continuous) -> (longer waiting) -> press trash button -> {nothing, only blink} -> menu button -> {nothing, only blink} -> menu button -> canon menu
2. (camera on with trap focus continuous) -> (longer waiting) -> press trash button -> {nothing, only blink} -> menu button -> {nothing, only blink} -> longer waiting -> menu button -> {nothing, only blink} -> menu button -> canon menu

.. canon menu -> trash button -> nothing -> menu button -> canon menu left -> trash button -> ML menu

Trap focus
noLV
- Hold AF button - mostly OK *)
- continuous - mostly OK *) , impossible to unlock with 2 seconds shutter halfway, I have use switch off camera. Sometimes this mode is not started immediately, but after second shutter use

*) sometimes, if I move object through focus distance, camera indicates focus (beep), but photo is not taken.

LV
- I don't know, how to use it. No focus and photo is taken, continuous freezes buttons like noLV

ok can you please check again "Exposure presets / Press SET". Seems to work for me. I can toggle via INFO and SET button.Maybe I understood it wrong.

I found what is problem. Exposure presets /Press SET works only If I disable  Canon settings for this button (C.Fn III -> Custom controls). But Auto ETTR /Press SET overrides this Canon settings. I don't know what is feature and what is bug, but it's inconsistent.

	C.Fn III SET:Off	C.Fn III SET: flash...
Exposure presets	SET -> change preset	SET -> flash...
AETTR	SET -> AETTR	SET -> AETTR(edit: precisely, shows flash exposure compensation, but immediately starts LV with AETTR)

Some of the reported bugs are hard to read and understand but I am keeping m best on trying to reproduce

What bugs from me are hard to read and understand? (sorry, I don't speak English, but I can try to rewrite it)

@DeafEyeJedi: Alpha6b (magiclantern-Nightly.2015Jul13.70D111B.zip)

some tests
shot feastures
- advaced bracket
- default params (auto and constant frames) - ok
- default + iso shifting (auto frames) - ok
- default + DOF + constant frames - ok
- default + flash + (auto/constant) frames - ok
- intervalometer
- interval 2s -> real interval for 5 pictures: 3, 1, 3, 1
- trigger - all ok


image review
  - play mode
  exposure adjust - ok
  timelapse play - ok both directions
  compare - ok
  trigger key - all ok
  - image review - ok
  - quick zoom
    single press -> 100% - ok
    fast - ok
    full zoom on AF - error (zoom on center)
    f zoom on last pos - ok
   
Auto ETTR
- in Av sometimes only changes ISO and time with constant exposure (400, 50 ) -> (100, 13), or (400, 50) -> (12800, ?)
trigger mode
   - set - ok
   - halfS dbl - mostly not triggered
   - auto snap - sometimes takes more pictures (3 pictures with different exposure or 4 pictures with identical exposure)
   


edit 14.7. 20:29
Expo lock
  - Off/Tv,ISO/Tv,Av - ok
  - off/ISO,Tv/Tv,Av - ok
  - off/Tv,ISO/Av,Tv - ok
  - iso,Av/Tv,ISO/Av,Tv - ok
  - iso,Av/off/Av,Tv - ok

Dual ISO
  - 200/800 - ok
  - 200/+2EV - ok
  - alternate frames - ok
  - custom file prefix - ok
  - I have some problem with conversion to dng (link to correct cr2hdr, cr2hdr20bit?)

Expo presets
  - Press Info - OK
  - Press Set - Error (canon action, but if i use set for ettr, it works)
  - white balance only in K mode
 
Overlay (all in photo mode)
  - zebras
     under, over - ok
     color space - imo all ok

focus peak
  - greyscale - ok
  - other parameters - it does something, but I can't see exactly difference in result

edit 14.7. 20:38
arcanoid
  - problems with background - after camera start some noise, in other cases last image (LV, from play mode)


edit 15.7. 19:55
crop marks
- show in photo mode - ok
- show in play mode - photo topleft+metadata -> cropmark on whole display

ghost image
- play with photo topleft+metadata -> overlay photo only on topleft in LV

spotmetter
- spotmeter unit - imo ok (but i can't verify right values)
- spot position - ok

LV with ML overlay
- randomly hide focus box

false color
- original image on spotmeter position
- banding detection - BW noisy image in LV (I don't know what is right result)
- green screen - only BW image without something green (I don't know what is right result)

waveform
- all modes do something, I can't verify result

vektorscope
- ok

edit 15.7. 20:22
histogram
- all choises does what I expect (I can't exactly verify displayed histogram)

level indicator
- freezes after I left magiclantern overlay LV page

DOF settings
- ok,  small difference between displayed and real distance (distances to 1 meter)

edit 16.7. 10:25
DotTune AFMA
Scan type - auto
scan passes - 2 and 10, probably ok (display is off during scan (bug or feature?))
AFMA mode - wide and tele on zoom, prime on prime - results looks ok

Hint: There's also a Burn-in test called "Quick test (around 15 min)" in debug menu which you can run!!!

What should be result of Quick test?
Last message was :) and camera is not in initial state (different WB, bulb in AV)

what exactly means "No sound support yet "? Because if I enable mlv_snd and mlv_raw, I get mlv with sound.

MLV format has a lot of metadata that plain RAW does not. This metadata is also added to DNGs produced from the MLV file. The extra metadata appears to be causing problems for Lr.

You can try other converters including mlv_dump or MLVFS. If the problem persists please upload a MLV file and/or DNGs produced from the various converters.

I try mlv_dump.
mlv_dump and mlvrawviewer generate different outputs. mlv_dump dng has thumbnail readable from lightroom. Both dngs have errors in metadata (exposure time)
generated dng: https://mega.nz/#!xURVgATD!HDu84i1AzCMmOdOzvfsPY0uFYS3d-qd-5vbBuo2kDQ4

edit: mlvfs (on win) generates problem in LR too

mlrawviewer 1.3.3 generates wav + many dng files. Problem is with import dng file into lightroom. But DNG profile editor (from adobe too) opens this file.

If i use
mlv_rec -> mlrawviewer 1.3.3 -> dng -> lightroom 6 -> import -> error (preview unavailable)
raw_rec -> mlrawviewer 1.3.3 -> dng -> lightroom 6 -> import -> OK
is it bug or feature?

        6400 -0x40453ae value (0xdb) */

6400 - 0x404535ae

edit:
if I have LV in photo mode, I have in cmos[0]
100 - 40453666 value 0x27
next values are different too
what is wrong?

2015Apr23.70D111B
problem in LV with level indicator in left upper corner on ML screen
start 70D -> LV -> ML screen, level indicator is changing -> [info] -> ... ->[info] ->ML screen, level indicator is static

edit: level indicator in corner (optionaly in center) works only if LV starts on ML screen.

stubs-api log: https://mega.nz/#!UdZEgC5T!V8wiKDQ2ERISyWJWJq8Mp8MBCOcJNnYQaaz8eQXgt8U
interface ok

[70D_111B]

Ok here is a new download for 70D_111B. better now? can you redo "Burn-in test - > Stubs api" and post the file here?

https://drive.google.com/file/d/0B9Mu66yg5QzRWVlWM0hCSzllbGM/view?usp=sharing

https://mega.co.nz/#!BUhx0JCA!fGJprVd0bNAzNXTc4lG5dSOkqoP0lsov4CuEuA1inMM
edit: https://mega.co.nz/#!1RB1zZJY!hnKLzFsj7iYLEagbxVdFRbNZcLmdBwvNF0MWI2iaNrk

Your bug with canon interface pic2 looks interesting. How to reproduce exactly? I guess it happens due to:

Code Select Expand


[FAIL] MEM(dialog->type) => 0x414944

I have problem with canon interface too.
start 70D(B) -> start LV -> [info] -> canon screen (ok)-> [info] -> canon screen with histogram (ok)-> [info] -> screen with level indicator (ok)-> [info] -> screen with missing elements

Someone post stubs api logfile for 70D_111B plz

If I run stubs api test, it crashes

ASSERT: IsSuiteSignature( hSuite )
at ./PackMemory/PackMem.c:1115, task run_test
lv:0 mode:2

edit: my next test was without error
https://mega.co.nz/#!BUhx0JCA!fGJprVd0bNAzNXTc4lG5dSOkqoP0lsov4CuEuA1inMM

... He / She has bought the 70D in 2014...

Why in 2014? Is there some difference between 70D from 2013, 2014, 2015?