Messages

No! This module only works for cams which have af fine tuning by factory (besides 60D).

...
14 to 12 conversion can be done in post too 

Dunno if you guys are talking bout raw but corect me if i am wrong (we had a long thread which is closed now):
12 is less data so needs less time to write to ram/sdcard.

Please have a look at this example sub / stub. Looks like I understood myself what I can achieve with dm-spy-experiments but plz at least give me a hint if that would be ok:



Now I take /src/dm-spy-extra.c and in there I would add like this:

Code Select Expand


#ifdef CONFIG_6D
    { 0xyzblabla, "StateTransition", 4 , state_transition_log },
    { 0xFF78D814, "SDCheckStatus", WhatToPutHere??? }
#endif

Would that work for startup / "debug (don't click me?) and log some stuff related to SDCheckStatus or doesn't this make any sense to identify what's going on for other stubs?

which resolution is set? Do you get skipped frames? Please run a benchmark test (not in photo mode)  for your card in debug menu and post results so we can see your write speeds. If you are using an additional sdcard in sd slot plz remove and retest.

could this be useful for dualiso preview / processing ? 

so we are using 0.9.26 TCC.
Do you see some usefulness of implementing the "mob" branch / tree of TCC into ML? Looks like some devs are still working on TCC code:

http://repo.or.cz/w/tinycc.git

I hope for raw addition (FA_SubtractTestImage, EekoAddRaw), and I bet a lot of people hope for 12-bit.

Sounds like you are doing some experiments  12-bit raw would be so awesome.

...
a1ex, I am asking you, g3ggl, and the community for guidance from you on a potential solution to GPL issues in the context of RawMagic.  I already asked you guys to bury the hatchet with the man but now people are getting dug into their extreme positions and not offering up solutions.  What extreme positions?  Threats to complain to the apple store, threats to remove access to the forum, measures taken.  That's not nice.
...

Hmm ofc best solution would be if a1ex and Thomas Worth would find a way to clear things up and solve all issues outside the forum. Dunno but we need to find a way so a1ex may agree to pick up  development again.

[FYI, ML development is stopped because of this issue.]

...

FYI, ML development is stopped because of this issue.

I suggest at a first action to delete questionable threads and also ban users which won't agre to comply with ML/GPL rules. I still can't seem to understand why ths didn't happen. On one side there are issues but on the other side there's nothing done by forum admins/mods. It just looks like ML team support such behaviour. I mean the RAWmagic thread is still available and what are we hoping to achieve? That from time to time Mr Thomas Worth will appear here to answer some comments? It's like ping pong. We say he didn't follow GPL, he says no this isn't the case now...

And because of that development is stopped. This is sad.

...
I will do these changes myself after the GPL issues from the forum will be fixed.

The GPL issues make me feel

Here's your link: http://www.apple.com/legal/internet-services/itunes/appstorenotices/

did someone already fill out this form?

....for example, only log those messages from CSMgrTask.

Can someone give me a detailed instruction based on dm-spy-experiments on how to log only "CSMgrTask" + "SdioDrv" +"SdioTsk". I bought a faster Sandisk card which is rated 60MB/s in write speed (before this I had panasonic Gold with a rating of max 45MB/s.). I wanna compare the logs I get from both cards and yes I am still trying to find a way where buss speed modes are set. Googling around I found this here which contains stuff like

Code Select Expand


#define MMC_CAP_UHS_SDR12       (1 << 15)       /* Host supports UHS SDR12 mode */

        #define MMC_CAP_UHS_SDR25       (1 << 16)       /* Host supports UHS SDR25 mode */

        #define MMC_CAP_UHS_SDR50       (1 << 17)       /* Host supports UHS SDR50 mode */

        #define MMC_CAP_UHS_SDR104      (1 << 18)       /* Host supports UHS SDR104 mode */

        #define MMC_CAP_UHS_DDR50       (1 << 19)       /* Host supports UHS DDR50 mode */


and maybe SdioDrv can show what's going on in 6D logs. So some hints where i can define what is going to be logged would be helpful.

Ok need definitely help from one of you ML dev gurus on this. I spent again some hours to read through all official SD specification PDFs from V1.10 til 4.X and I can say CMD6 is all that is needed to set bus speed modes (SDR50 SDR104 DDR50 ...). There's one CMD6 SwitchCommand available in my 6D rom so it may be worth a try. Ofc this only works for UHS-I cards. I also simply guess that 5D3 is set to SDR25. a1ex tried once (see 1st page) but if something is done wrong then sd spec says that afterwards settings are defaulted and that's then SDR12. 

As simple as it sounds: tried another card?

Wow the posted results above are really a noteworthy performance boost. Congrats.

Hi,

I wanted to define CONFIG_EDMAC_RAW_SLURP in internals.h but looks like I need to find DEFAULT_RAW_BUFFER for my 6D. In raw.c there's some hints how to find it and there's also

Code Select Expand


#else

/* with Canon lv_save_raw, just read it from EDMAC */
#define DEFAULT_RAW_BUFFER shamem_read(RAW_LV_EDMAC)

#endif

Shouldn't above code define it automatically or is it obsolete?

no you cannot use 280MB/s at full speed.

6d is rated maximum 45MB/s it cannot do more.
5d3 sd slot is about 20MB/s as i remember and it cannot do more. 5d3 you need to use CF card.

Please use the search function next time. This has been discussed several times in different threads.

Time to push out a final nightly (call it 2.4 or whatever) and at the same time an announcement of raw video stuff being thrown out of ML in future nightlies releases. Code will be cleaned up on bitbucket to get focus on photo stuff. Maybe that would be also the time to announce unsupporting some old cams or cams with less contributors. All video'ers might use that final nightly and others will shoot fullres-silent pics up to 1/8000 in future releases incorporating much more photo stuff which gets contributed. Something like that should do the trick to get the internet's eye on ML. Afterwards we will see what happens and who pops up here to help and get all back into development branch - if that will be ever needed.

and btw that's no joke.

..Without your efforts and open source philosophy magic lantern would be nothing...

Without his efforts one of the next cams appearing with armv6/7 processor and 4k raw video possibility will be nothing cause all his brain will be needed to get it working asap. Others may do the work too but until they get it done 8K will be available 

I'm actually thinking to move away from the video side of ML, and let those actually interested in video do the hard work instead. I'd rather focus on the still photo stuff, which is what I actually use.

+1 on this.
Lots of forum questions regarding video. With the upcoming 4K hype I think time will tell what happens to ML video but the focus should definitely be on photo stuff.

welcome to the forum.
EOS-M contributors are very welcome.

Works for me. We already had such discussions. You should have been using search.

Anyways use another browser or simply deactivate your adblockers or whatever addins you are using.

ofc camera will load less stuff into memory if it's not enabled. I would suggest that you try out yourself. Regarding performance I didn't notice much of a change when enabling several modules but turning off global draw for e.g. can boost performance a lil' bit - at least regarding write performance to card.

You can check out yourself in debug menu. Free ram etc. and also there's some benchmarks. So just enable whatever modules you want and then do benchmarks. I don't expect you to see much of a difference but your report will be welcome...

Ahh ok, that explains it!

@SKID: This one should work

Ok then I can't help you atm. I can suggest you to retry by starting from scratch and deleting configs. If still no luck than report the bug on bitbucket to fullres-silent-pics branch

Yes it is a bug already known. Have a look here:
https://bitbucket.org/hudson/magic-lantern/issue/1974/6d-in-live-view-mode-ml-menu-times-out