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.

Messages - nikfreak

Pages: [1] 2 3 ... 40
Camera-specific discussion / Re: Canon 70D (Beta-4a / 26th Oct)
« on: September 18, 2017, 07:38:03 PM »
The value of the SRM_BUFFER_SIZE for the 70D is *not yet* known...

a1ex has meanwhile "extended" my initial pull request and you can say that my PR and the one in ML's repo don'T match exactly. I've reintroduce fps override btw in my PR. Still if you follow the source linked in 1st post:

you will find SRM_BUFFER_SIZE

true then either some other brand (so forgot what he/she used) or still the 5D3 with some magic post workflow

probably was lent a 5dIII and thought it is a 5DS

Raw Video / Re: Canon 100D raw potential.
« on: September 06, 2017, 11:21:55 AM »

we already got "h264 vs raw" topics. Just search for it. 100D is same generation as 650D/700D/EOSM in terms of sensor / write speed and quality. Also there are lots of comparison videos on YT.

100D doesn't have ALL-I option for recording FHD H264. Here the bitrate modifications (after installing ML) come in handy and push your recordings a lil' bit. If that suits your needs then take and be happy with it combined with picture styles. With 10/12bit I would personally go RAW always just for the colors in post production. The amount of quality difference regarding details etc may not be significant after upscaling - still I would go RAW. But that's me. You could even extend the resolution if you don't need continuous. In the end you will have to find the answer yourself. It's like photos JPG vs RAW vs additional workflow/time.

5Ds + g3gg0  :-*
crossing the fingers. Congrats.

Camera-specific discussion / Re: Canon 70D (Beta-4a / 26th Oct)
« on: August 31, 2017, 06:31:01 PM »
upgrade your firmware to 1.1.2

Share Your Videos / Re: Stephen King under a Magic Lantern :)
« on: August 31, 2017, 02:47:50 PM »
finally watched it.
Congrats. Amazing work.

Nightly Builds / Re: Nightly Builds - try the very latest stuff here
« on: August 27, 2017, 11:57:19 AM »
Maybe it could be possible to not damage the camera with some caveats. You would have to lock the mirror if your magically adapter needs to be fitted between body and lens. You then wouldn't be able to focus to infinity at all besides having to focus manually anyways etc.

Rather read and consider this about fisheye / ultrawide lenses


Probably mystic. Try one of the alternatives mentioned in the linked post:

why just consider and not try yourself? 5k even at 60fps no problem because the 1st post does exactly contain that info.  :P

* 4096x2560 @ 12.5p (1:1 crop) - continuous*) at 8 FPS

24p should be a second - maybe!?

You are post #1339
reading #1314 should answer your question regarding 7D

April 1st, 2018, for sure!

Camera-specific discussion / Re: Canon 70D (Beta-4a / 26th Oct)
« on: August 21, 2017, 04:16:17 PM »
Despite playback the recordings worked also in test releases:

@a1ex: as TimerA works for modifying FPS -> what do you think about bringing it back for the public on 70D

Probably got a freaky request but care to share a working for 7D or is it impossible?

May I just chime in and sum it up?

  • read this, this, check this etc. as well as all included links in that posts.
  • Initially Greg succeeded and got results by doing it like described here and a1ex replicated it successfully on Digic5 and first got it only working with freezing preview or grayscale.
  • I'm a little bit unsure but for me it looks like you might need to get edmac_raw_slurp first running/enabled on 5D2 (more see below raw.c) but a1ex might correct me on this
  • raw.c: Check this commit. It's used in conjuction with edmac_raw_slurp and is meanwhile part of unified branch with even updated code parts  8).
  • try it with adtg_gui like a1ex did by simply overriding/changing one or both registers C0F06084 / C0F06088 like Greg did initially. You probably simply need to activate zoom/crop and find an example value for 2.8k/3k or whatever and afterwards hope you get the overriden resolution been shown in mlv_rec...

So frozen preview or not. i would say 1st goal would be to replicate what Greg/a1ex did AND be carefully with whatever you are trying out above this post  :o

Camera-specific discussion / Re: Canon 100D / SL1 (Beta-4b)
« on: July 28, 2017, 09:33:46 AM »
Hey, Gianluca I will just commit a fix for moving the spot box in manual focus. Without your report I wouldn't have noticed that we need it.

For the rest of your probems: please disable "Small Hacks" in advanced optionsof the mlv_rec/lite module. I wasn't able though to reproduce the crash you described.

@a1ex: we really should disallow/hide "Small hacks" for the cameras with a touchscreen (CONFIG_TOUCHSCREEN).

Camera-specific discussion / Re: ML on EOS-M2
« on: July 27, 2017, 10:13:40 PM »
sounds like you need to triple-check the FIO stubs cause _find_ml_card() is part of fio-ml and most of the code is FIO related.

Camera-specific discussion / Re: ML on EOS-M2
« on: July 27, 2017, 07:15:54 PM »
a1ex always told me to use the blink code (led blinking) whenever I got stuck while porting to 70D/100D.
That way it was rather easy to determine at which part of the code we got stuck. Mostly the symptom for becoming stuck was a continuous LED light and not a blinking one.
In your case I would start here in boot-hack.c:

Code: [Select]
/* This runs ML initialization routines and starts user tasks.
 * Unlike init_task, from here we can do file I/O and others.
static void my_big_init_task()

and place some strings/printf's/debugmsg (OK1/2/3...) before or in between to see if you reach that part of the code in qemu. Afterwards continue or revert until you reach a code part where you don't get stuck. As last time I used QEMU with ML is years ago i can't tell you really what code exactly to use for the blinking LED alternative. You need something you will see in qemu console...

will this work on El Capitan (hackintosh)??

Duplicate Questions / Re: Error latest nightly build 7D
« on: July 26, 2017, 01:59:50 PM »
Yep, confirmed.

How do I fix this?

Either you provide the fix and hope it gets merged or you wait for a dev to do it.

Camera-specific discussion / Re: ML on EOS-M2
« on: July 22, 2017, 07:23:33 PM »

TODO: I'd like to update 100D to use the "classic" boot process as well.

as discussed here I failed to use AllocateMemory pool but:

Quote from: nikfreak
...I am able to load 100d into malloc but the interesting part I can only bring up ML menu with the task related changes from this PR in addition with a fixed task_dispatch_hook and undefining hijack_task_addr as instructed earlier. Otherwise ML menu wouldn't come up.

I'm ready If you want to give it another go.

General Chat / Re: Apertus Axiom Beta
« on: July 20, 2017, 12:29:56 PM »
If all goes wrong you can use Canon sensors together with a1ex's qemu work and a raspbi and call it A1EXIOM  :P

Camera-specific discussion / Re: Canon 100D / SL1 (Beta-4b)
« on: July 19, 2017, 12:21:20 PM »
Back then in January I released a test build for the community to enjoy 10/12bit recording and kept it disabled @bitbucket. I recorded myself just a few frames and found it to be working fine. I guess it is fine as it is requested now again and also has been mentioned to work at:

I can enable and push it to bitbucket if you like.

Camera-specific discussion / Re: Canon 100D / SL1 (Beta-4b)
« on: July 19, 2017, 09:55:40 AM »
sounds like CONFIG_EDMAC_RAW_SLURP isn't defined on the experimental builds.
The January build you are referring to had it enabled (only on that build!!!).
For the moment you just have to wait or switch back though I don't recommend to switch back as you won't have the latest fixes included.

Note: Don't mix up builds / modules. It will only cause confusions.

Pages: [1] 2 3 ... 40