Messages

did u run the scripts prepare.ubuntu.sh  and summon-arm

If no luck, I think it has something to do with the new version of UBUNTU, just get the 12.04 version and all should be fine if you run the scripts, I think theres an error during the summon-arm script with newer UBUNTU versions, it doesnt ever finish.

but now I am getting a werid error like file not found, this is my terminal output:

Set toolchain up so folders are like this. Notice the directory these are in at top.


Create a Makefile.user file and add these line to it and make sure lines 3 to 6 are in yours, adjust other lines as you need for your setup. Don't touch Makefile.user.default file.

If you did everything else correctly, this should get it going.

I have used the prebuilt VM and it is great, only advantage of setting up your own seems to be you can choose a bigger hard drive size which you will need if you are experimenting alot like I was, you can resize it later on, but if done wrong, you will lose all your work. Also, another advantage is newest version of UBUNTU, but I dont notice any differ with newer versions.

I am using my own built version now just cause I wanted to start fresh when I got going again and saved my old VM just in case, but I dont see any differences, just more time setting it up then prebuilt, as a beginner, maybe best to start with prebuilt, but maybe not, cause it helps you learn your way around a bit.

On 700D MLV Format
14bit 820 ms 38 MiB/s
12bit 825 ms 32 MiB/s
10bit 739 ms 30 MiB/s

speed seems to jump around alot on all bits, gets faster after 2nd mlv is taken, usually by 100ms on each.

DNG Format
14bit 2970 ms 10 MiB/s
12bit 2169 ms 12 MiB/s
10bit 1960 ms 11 MiB/s

Got same result on 550D, no freeze, but scrambled image for 10 and 12, unless its not even suppose to work on this cam anyway, but tried anyway.

Code Select Expand

NSTUB(0xFF353274, ProcessPathForFurikake)
NSTUB(0xFF37FBE8, PACK16_Setup)

Update!!, Works on 550D, had to do a Make Clean first, Ill try on 700D now.

Works on 700D as well! Just needed a make clean.

Nope, it just says None.

Is this only for testing on the big cams like 5d3 and 60d, I went to get the stubs, tried it, I get smaller file sizes for the 12 and 10 bit, but there scrambled and cam goes to black and freezes after done taking picture when I do 12 and 10 bit, 14 is fine?

Code Select Expand

//** Image processing paths */
NSTUB(0xFF420AE4, ProcessPathForFurikake)
NSTUB(0xFF5EF23C, PACK16_Setup)             // PACK16_MODE:%#lx and others
not 100% there right, especially the PACK16.





Or is the problem this part that is only for 5D3?

Code Select Expand

+    /* hook to override the bit depth in PACK16 setup function */
    patch_hook_function(
        (uintptr_t)&PACK16_Setup,
        0xE92D4010,
        PACK16_Setup_hook,
        "PACK16: raw bit depth override"
    );

Thanks nikfreak!

Sorry guys, mothers day had to come first, but after all the times alex helped me, I will return favor when I can.

700D

Code Select Expand

  run_test:ff225c48:80:16:
  run_test:ff225c64:80:16: --- Common Top ----
  run_test:ff225c80:80:16: [TOP1]                  0x40D3C000
  run_test:ff225ca4:80:16: SSS_DEVELOP_WORK        0x40D3C000 0x00038000 229376
  run_test:ff225ccc:80:16: SDS_DEVELOP_WORK        0x40D74000 0x00038000 229376
  run_test:ff225cf4:80:16: DARKCUR_COMP_WORK       0x40DAC000 0x00020000 131072
  run_test:ff225d1c:80:16: FENCING_WORK            0x40DCC000 0x00010000 65536
  run_test:ff225d44:80:16: DCFNO                   0x40DDC000 0x00004000 16384
  run_test:ff225d6c:80:16: LVMARGE_P_DEF_DATA_1    0x40DE0000 0x0000A000 40960
  run_test:ff225d94:80:16: LVMARGE_P_DEF_DATA_2    0x40DEA000 0x0000A000 40960
  run_test:ff225db4:80:16: LVMARGE_P_DEF_DATA_3    0x41FD0000 0x0000A000 40960
  run_test:ff225ddc:80:16: LVMARGE_P_DEF_DATA_ZOOM 0x40DF4000 0x0000C000 49152
  run_test:ff225e04:80:16: FILE_HEADER             0x40E00000 0x00280000 2621440
  run_test:ff225e2c:80:16: CAPTURE_WORK1           0x41080000 0x00280000 2621440
  run_test:ff225e58:80:16: BMPVRAM1                0x41300000 0x00080000 524288
  run_test:ff225e84:80:16: BMPVRAM2                0x41380000 0x00080000 524288
  run_test:ff225eb0:80:16: ENGINE_MIRROR           0x41400000 0x00044000 278528
  run_test:ff225edc:80:16: VSHADING_COMP_WORK      0x41444000 0x000DC000 901120
  run_test:ff225efc:80:16: STILL SCAR              0x41520000 0x00075B00 482048
  run_test:ff225f1c:80:16: SAF WORK                0x41595B00 0x00100000 1048576
  run_test:ff226258:80:16: SAF RAW                 0x41695B00 0x0035D540 3528000
  run_test:ff226278:80:16: LVMARGE_P_DEF_DATA_CROP 0x419F3040 0x0000C000 49152
  run_test:ff226298:80:16: EEKO                    0x41E00000 0x001C0000 1835008
  run_test:ff2262b8:80:16: SHOOTING_CREATIVEFILTER 0x41FC0000 0x00010000 65536
  run_test:ff2262d8:80:16: TUNEDATA                0x42000000 0x00030D40 200000
  run_test:ff2262e8:80:16: --- Usually Mode ----
  run_test:ff226304:80:16: ONLY MEM1 1             0x0 0x00000000 0
  run_test:ff226320:80:16: ONLY MEM1 2             0x0 0x00000000 0
  run_test:ff226344:80:16: EXMEM3_AREA_2           0x42200000 0x01E00000 31457280
  run_test:ff226364:80:16: MEMORY_MGR              0x44000000 0x06000000 100663296
  run_test:ff226384:80:16: EXMEM3_AREA_1           0x4A000000 0x019C0000 27000832
  run_test:ff2263a4:80:16: SS_DEVELOP1             0x4B9C0000 0x02000000 33554432
  run_test:ff2263c4:80:16: IMGVRAM1                0x4B9D0000 0x00410000 4259840
  run_test:ff2263e8:80:16: IMGVRAM2                0x4BDE0000 0x00410000 4259840
  run_test:ff22640c:80:16: IMGVRAM3                0x4C1F0000 0x00410000 4259840
  run_test:ff226430:80:16: IMGPLAY_WORK            0x4C600000 0x00A00000 10485760
  run_test:ff226450:80:16: IMGPLAY_WORK2           0x4D000000 0x00400000 4194304
  run_test:ff226470:80:16: SS_DEVELOP_OTHER_WORK   0x4D9C0000 0x00400000 4194304
  run_test:ff226494:80:16: EXMEM3_AREA_3           0x4DDC0000 0x0222C000 35831808
  run_test:ff2264b4:80:16: AVERAGE_WORK_TOP        0x4DDC0000 0x01116000 17915904
  run_test:ff2264d0:80:16: AVERAGE_WORK_BOTTOM     0x4EED6000 0x01116000 17915904
  run_test:ff2264e0:80:16: ---   GIS Mode   ----
  run_test:ff226500:80:16: TEMPMEM1                0x48200000 0x02000000 33554432
  run_test:ff2268c4:80:16: SLIDE_SHOW_WORK         0x48200000 0x00800000 8388608
  run_test:ff2268e4:80:16: MOVIE_PLAY_WORK         0x4A600000 0x00126000 1204224
  run_test:ff226904:80:16: IMGVRAM1                0x4B9D0000 0x00410000 4259840
  run_test:ff226924:80:16: IMGVRAM2                0x4BDE0000 0x00410000 4259840
  run_test:ff226944:80:16: IMGVRAM3                0x4C1F0000 0x00410000 4259840
  run_test:ff226964:80:16: IMGPLAY_WORK            0x4C600000 0x00A00000 10485760
  run_test:ff226984:80:16: IMGPLAY_WORK2           0x4D000000 0x00400000 4194304
  run_test:ff2269a8:80:16: MOVIE_REC_WORK          0x4D800000 0x01400000 20971520
  run_test:ff2269cc:80:16: MOVIE_STREAM            0x4EC00000 0x01400000 20971520
  run_test:ff2269ec:80:16: WORK                    0x4A200000 0x05E00000 98566144
   CtrlSrv:ff52d698:83:01: DlgLiveView.c LOCAL_OLC_BLINK
   CtrlSrv:ff52b784:83:01: StartOlcBlinkTimer
  run_test:ff226a08:80:16: EXMEM3_1_AREA           0x0 0x00000000 0
  run_test:ff226a28:80:16: EXMEM3_2_AREA           0x42200000 0x06000000 100663296
  run_test:ff226a38:80:16: ---   HDR Mode   ----
  run_test:ff226a58:80:16: TEMPMEM1                0x48200000 0x02000000 33554432
  run_test:ff226a78:80:16: SLIDE_SHOW_WORK         0x48200000 0x00800000 8388608
  run_test:ff226a98:80:16: MOVIE_PLAY_WORK         0x4A600000 0x00126000 1204224
  run_test:ff226ab8:80:16: IMGVRAM1                0x4B9D0000 0x00410000 4259840
  run_test:ff226ad8:80:16: IMGVRAM2                0x4BDE0000 0x00410000 4259840
  run_test:ff226af8:80:16: IMGVRAM3                0x4C1F0000 0x00410000 4259840
  run_test:ff226b18:80:16: IMGPLAY_WORK            0x4C600000 0x00A00000 10485760
  run_test:ff226b38:80:16: IMGPLAY_WORK2           0x4D000000 0x00400000 4194304
  run_test:ff226b58:80:16: MOVIE_REC_WORK          0x4D800000 0x01400000 20971520
  run_test:ff226b78:80:16: MOVIE_STREAM            0x4EC00000 0x01400000 20971520
  run_test:ff226b98:80:16: WORK                    0x48200000 0x07E00000 132120576
  run_test:ff226bb4:80:16: EXMEM3_1_AREA           0x0 0x00000000 0
  run_test:ff226bd4:80:16: EXMEM3_2_AREA           0x42200000 0x06000000 100663296
  run_test:ff226be4:80:16: ---    NR Mode   ----
  run_test:ff226c04:80:16: NR_MEMORY_MGR           0x44000000 0x08000000 134217728
  run_test:ff226c20:80:16: COMPOSITION_WORK_TOP    0x0 0x00000000 0
  run_test:ff226c3c:80:16: COMPOSITION_WORK_BOTTOM 0x0 0x00000000 0
  run_test:ff226c4c:80:16: ---    DP Mode   ----
  run_test:ff226e4c:80:16: DP_MULTI                0x47E00000 0x02E00000 48234496
  run_test:ff226e6c:80:16: DP_SINGLE               0x42200000 0x05C00000 96468992
  run_test:ff226e7c:80:16: --- Indev Mode ----
  run_test:ff226e90:80:16: [INDVMGR]               0x0
  run_test:ff226eac:80:16: YUV                     0x4DDC0000 0x0222C000 35831808
  run_test:ff226ec8:80:16: YUV_OUT                 0x42200000 0x0222C000 35831808
  run_test:ff226ee4:80:16: INDV_WORK               0x0 0x00000000 0

No, you did fine on help file, I was to anxious to try it, I didn't even know there was help text, lol. 

Yours makes perfect sense though.

You got to be kidding me!!!! Very cool, will have to try this out for sure! Thanks! 

Update: pre-record works nicely, I like how it shows the amount of seconds capable of pre record, so if u pick 10 seconds,  it will show you while recording if its possible,  and if not, it will show how much you can get for the fps and resolution camera is set for.

I see its pre record time amount doubles pretty much with srm on, then if turned off, so that's obviously working good too.

At first I was confused cause when I started recording, I waited a bit, saw up top the pre record amount in seconds,  then I pressed shutter to save, but it started writing, then kept recording until I pressed shutter. I was thinking it was going to stop capturing and save all frames from pre buffer up to where I pressed shutter, eventually I figured out how u set it up and got use to it.

Pretty cool you got it coded so quickly.

I was using 700d for testing by the way.

Cool, sounds interesting, I will check it out and see how it works from how I remember it working or compare to old end trigger before I copy new one over, just need to hope my VBOX still works and I remember how to do all the stuff I use to mess with to compile. 

As for preview, I would prefer no preview at all, just record buffer and wait for next shot, but wondering if it needs time to write anyway before you can record next shot, so maybe the preview is a must to slow the user down?

Am anxious to see if I get more frames with your new update though, Thanks!

Update: On 700D for silent pictures End Trigger, it went from 25 frames in buffer to 41! Nice update!

Oh yes, the frames limitation, I remember that, and every camera model would be different from what I remember.

And yeah, might help out with lightning trigger if I had a way to remote trigger, lol, good thing about lightning one, is I can hide in car when big bolts get close and the detection code will do the unsafe triggering for me. 

But with all these cell phone apps having these type of features, this addition to the DSLR camera would be great since there quality is way way better then a cell phone sensor.

Hopefully the frame limitation does not keep it from progressing if you decide to try to implement it, but I do understand that part.

And yes, very similar to End Trigger, only bad thing with End Trigger feature is you have to wait it out as each frame writes and goes through the previews and it doesn't include the camera settings in the file if I remember correctly, its been awhile since I was in testing mode, maybe I missed an update?

Thanks for the interest and reply! 

I was trying to film dogs catching Frizbee the other day, and was thinking, I wonder if there's a way to add a buffer record to Raw_Rec module, like have it record to buffer but not to file for the certain amount of frames the user chooses as a buffer, then when the action you want happens, you press the shutter and it records the buffer to video file? Might be a neat option to add to this module for wildlife or sports, especially if it will probably now save the camera settings you use in the video file as well. Or is this to much clutter for the module, maybe a separate module might be needed? I have been away from ML community for awhile and my coding skills are way to rusty to even know if this is possible or not. Thanks

600D

Model ID: 0x286 600D
Boot flags: FIR=0 BOOT=-1 RAM=-1 UPD=-1
ROMBASEADDR: 0XFF010000
Dumping ROM0...

nothing on card no led

Yeah, no same 

Only can try with 1 card though, don't have any extra cards at this time. 

700D works and gives Files, But ROM1.MD5 checksum changes each time, ROM0.MD5 stays the same.

I used winmd5free, I ran 1 test, got the checksum from ROM0.MD5 and copy and pasted it in the Original text box, then ran test again and loaded new ROM0.MD5 and checksum was same as first.

Did same steps for ROM1.MD5, but checksum was differ.

Did I even do it correctly or were you wanting something else?

Hi, was curious on your tweak to the code in fixing this live view freeze issue on the 700D, can you share what you found? I am the one who ported this model so am curious on any fixes found of course? Thanks!

No other then when tweaks are made to the nightly in the future, you will need 114 to have them available on your camera. But 113 and 114 work the same, nothing any better or worse about it.

Well, I just did a fresh install of latest nightly and am not having any crash issues recording mlv even at 1280x720 using all default settings of ML and MLV module, I have Canon video settings set to 1920x1080 @ 24fps to get continuous and also tried at 30fps and still no crash.

So can't reproduce, maybe something is not setup right on your camera?

Try turning small hack off from within the mlv menu, the address might be wrong,  I dont have that issue,  but I still use the build I originally ported, not the nightly,  so maybe the change did not take affect,  I will try to check it later today,  but for now,  just turn small hacks off.

To save you the trouble,  I have already tried that when porting to 113, this feature does not work,  the  firmware is differ then other cams in that area,  was never ever to get it to work for that or for trap focus.

No problem, glad to share until its accepted in the nightly.

I already ported the 114 version which is being used already by other users that messaged me for the build since it is not in the nightly yet.  If anyone needs 114 I am glad to send you link until it's in the nightly.

Anyone know what this HDMI USB thing is, I don't see this on the 550D or 700D when I play with them, this loops so much and makes it super slow to work the menus?

I can PM it to you, since I am not sure the devs prefer it in the threads.

Yeah, even canon is still posting the 113 firmware, but I just don't know if it is ok to Downgrade to 113 if your camera came with 114 already on it, you will have to ask maybe Alex if that is safe. It is def ok to upgrade to 114 then downgrade to 113 because I just did that fine and so have others with other models.

If it is safe for you to downgrade to 113 with a cam that shipped with 114 then you can downgrade to 113 first, install ML on it with the 113 FIR file since there is not one made for 114 yet since the port is not added yet to the public list, then once it is installed, then you can upgrade back to 114 firmware and use the new 114 port I just did, it is working just fine, just as good as 113 is working.

I can also provide a compiled version for anyone who wants to upgrade to 114 and test it, because it will probably never be updated in the nightly without testers to show it is ok as the 113 is.