Messages

I mean, the Mac has a reputation of being easy to use, right? I get all sorts of animated popups, OK, maybe that's what users like, but... for pretty much every single basic thing (like moving a file, or going to the Home directory in the GUI, or... typing the ~ character) I need to google how to do it. And it's not the first time I've used a Mac.

Win10 has its own share of quirks (e.g. the WSL home directory is hidden quite deep in the host filesystem), but not nearly as many.

Good news - precompiled toolchain 7-2018-q2-update appears to work fine! The installation script now defaults to that on both Mac and WSL.

It's easy for who never used a PC before

I've tried to use CONFIG_INT for saving and restoring camera settings instead of writing a specific file for the module but came into some issue.

At first try settings were saved only if in ML menu, but not from the GUIMODE where C modes are shown.
Another problem I got is that before by saving each value to a file I didn't had any defaults and they were alway saved all.
Now I've set 0 as default for each value but if the setting we are saving is actually 0 it will not be saved to the module configs file. This broke how I was setting Kelvin or WB previously (kelvin was saved only if it was set so if missing in the file it was not restored, now there is always a value for it).

To make it easier to review I've moved c-modes code out from "Rebel GUI" module and made one specific "C-Modes" module.

Problem is that they should share some variables and I don't know how to handle it, so I've removed that part in C-modes and made it a little more hardcoded than before just to have a working module for now.

But..

Both modules are looking for button press in same GUIMODE_PICTURE_STYLE and that cause them to hang buttons when camera starts, If loaded one by one they work good.

So after a couple of days of insuccess I'm thinking that I should keep one module only approach like before?
I think one module only is ok because both Rebel GUI additions and C-Modes are features missing only on Rebel cameras, so ideally this module should be included only on supported models.

EDIT: found out how to avoid setting a default value with NULL instead of null as I was doing at first)

you can see histogram for RGB channels also without ML, in canon preview only.
Using INFO button to change what is shown when in play mode on 600D (others models may use differen names like DISP for the button)

I know of this comparing various cameras: https://docs.google.com/spreadsheets/d/16cgnRivbUv7nA9PUlCLmLdir3gXdIN3pqzCNAAybepc

To be sure. I've made (in qemu branch):

Code Select Expand


hg pull
cd contrib/qemu/
./install.sh


I'm on OsX 10.13.6 and seems to work ok with clang
GCC: gcc-arm-none-eabi-7-2017-q4-major

As far as I understand the ARM CPU emulation is the smallest problem since it is provided by Qemu. All the custom or very specific chips around it are the difficult ones. You'd have to emulate them on the RaspPi as well. And then you'd have to do it in hardware or catch the hardware accesses which is at least as difficult as it is in Qemu.

E. g. the buttons are not directly connected to a GPIO of the main CPU but to the MPU as far as I understand.

For sure it would be a fun project, e g. with a cheap camera module to "simulate" a real camera. But I don't see value for the actual reverse engineering.

yes the idea dosen't have any pratical use, just for fun.

After plaing all day with qemu, was thinking about it and got one curiousity,

canon dev's have some sort of emulator too?

Or better

usually when a firmware is done how it is developed? they test it on real hardware or they use an emulator, or both? Also i think they have special dev boards maybe?


Another silly idea that came into my mind was if, at least in theory, could be possible to use qemu on (don't know, maybe a rasperry) to simuate canon software and use a module for the camera and a keyboard (maybe modded with just the needed buttons) to control it? For some camera qemu can take pic? Is it right?

EDIT: Last... (for now)
What about this: https://github.com/limboemu/limbo a port of qemu for android if I understood right. Anybody have already tried it for ML?

Is there a knack/shortcut to turning the top wheel x hundred times to adjust each register in adtg_gui.mo? 

E.g Change ADTG2 [8882]  to 0x13b (five minutes of turning!)

can't you select each char in the number with arrows? On the module I use it works

this?

[Edit]

Very interesting. Seems they have done the same thing as me for the initial Slideshow presets. It's unclear how to use the Video presets though. Based on the read me it sounds like once they are dropped in Lr's Video Presets folder they should show up as an option in Slideshow > Export Video, but they do not. Perhaps this worked with older versions of LR or I'm misinterpreting something.

Edit: Found this. Seems they may have removed the ability to use Video Presets for exporting. Shitty. https://forums.adobe.com/thread/1234089

Being an old LR user too, I hate where adobe is going with CC and so on, that is just another bad choices from them.
Recently I've sarted to learn and change my workflow to opensource apps for that reason and also because I'm interested in getting a POWER9 IBM processor machine like the Talos or Blackbird

So far only thing that kept me away from linux is LR and PS both are app that I've used since they were in beta so is really hard to change but not always is easy to get thing better, so far I found really nice how LightZone works for example, instead of Darktable that is less intuitive for me at the moment.

ok seems I've managed to make a full diff now and moved files around ok.
attaching it here

I can look into it, but... maybe near the end of the week, if you remind me.

I've added current_task_addr: in qemu and it started once (not the GUI)
But then I've srewed up somehow the qemu install it's now giving me this error:

qga/commands.c:13:10: fatal error: 'glib.h' file not found

Now I have a little problem with hg
I am in the vxworks_dm_spy branch and have all the changes I made to the 5DC uncommited because didn't know how to tell hg that the files relative to 5D are moved from unmaintained and not new.
Now I think I should update to qemu branch and reload the install script to fix my qemu installation and also update it (since I saw you added something for 5DC after I had installed mine)
Maybe I'll save another patch with my changes and then make "hg update -C qemu" install qemu and then go back to vxworks_dm_spy and restore the patch.
But probally there is a more cleaner way with hg commands...
That will not work because the patch file got from "hg diff -g" (like the others I've shared so far) are incomplete since they don't include those 5DC files I've moved out from unmaintained and edited after.

However, the task structure is not the same as DryOS. It looks the same as on other EOS models though. From my notes (to be double-checked):

I don't understand this; you mean that the structure is same as other EOS model with vxWorks and different from the EOS models with DryOs?

I used some presets for making timelapses with LR years ago and they were working ok but can't remember where I got them.
just found this that maybe you can use to compare with yours

[A]

More precise version (got these timer numbers using g3gg0's EOSTimerGen):
- Enable FPS override
- Select 24.000, optimized for "Exact FPS"
- Change FPS timer A to 600 and FPS timer B to 2000
- Fine-tuning to +0.17ms

This gives 1/47.999 shutter speed on 600D.

From 1/45 shutter just tried and got 1/44.659 (+9 units) with +0,17 in fine tuning and fps as you suggested.
to get something around 1/48 I have to set finetuning to -1,23 (-65 units) to have 1/47,999

So if understood right:
with fps 24 is better 1/48
with fps 23,976 is better 1/47,952
is this correct?

If that's the case on 600D for 23,976 fps (got them in fps override with: timer A 616, timer B 1950 ) I have to set -1,51 and result is 1/47,941

to sum up:

	24fps	23,976fps
timerA:	600	616
timerB:	2000	1950
finetuning:	-1,23	-1,51
RESULTS:	1/47,999	1/47,941

Found the culprit of the Moire in LR on those pillows. It was sharpening.

I tried RT -> .tif and found that LR was causing the Moire there too. The moire was not present in RT or in Preview (I'm on a Mac), only in LR. A quick google (and filtering through all the 'how to fix moire' posts) I found this thread which attributed it to Sharpening and some other adjustments. https://forums.adobe.com/thread/1312516

If I either

A) Keep the sharpening below 20 (the LR default is 40, even for tifs)
B) Increase the Masking slider to 50-60+

... it seems to completely avoid the moire, for this particular case. Of course that also reduces the overall sharpness quite a bit compared to what I wanted but I'm sure with more playing I can get a reasonable compromise for these cases.

I don't do video but for photo I usually used masking a lot in LR with sharpening to avoid oversharpened images

Sorry, couldn't resist to post this link in this topic
https://youtu.be/8ThDAmTm5Ws

I know the 180 degrees shutter rule and use it too, but if the number is nearby I'm happy.
In low light I don't hesitate to use 360 degree shutter value.
But do these tiny difference mentioned here really make a difference ?
Can only imagine that it makes a difference whith artificial light on main power supply at 50/60 Hz.
But with natural outdoor light, is there really a difference visible

Video is funny but I saw differences 

[1/47,995]

If I try on 600D can't set shutter to 1/45 only 1/42 or 1/50, but by using 1/42 and in fine tuning -3.22 i got 1/47,908
and with 1/50 and Fine tuning +0,85 i got 1/47,995

Just for reporting my results

With recents updates on bleading edge versions flexinfo works ok without problems.
I've fixed some positions and cleaned up some parts.

If there is someone interested in testing it:
DOWNLOAD (don't load rebelgui module included, it's here for mistake and not working)
(based on unified branch)
SOURCE CODE
PULL REQUEST


EDIT: added screenshot of trapfocus written with another font

[2018.Oct.10]

friend ... i can not understand.
my current version on Canon 5dmk3 -2018.Oct.10




but now is available - 2019.Mar.24


where on this link i can see difference between current and new versions ?

Alex already answered, there are small changes only for other models, but if you look on the linked pages you should see that last commit (or last changes) is 26 september 2018  and since you version is older it already has all the commits, none new so nothing changed in the code

So far, I've chosen to stay away from the smartphone world, mostly for "comfort zone" reasons. I've actually played with an Android phone for a few weeks, installed LineageOS & stuff, even was halfway successful in running a kernel exploit, and... went back to my old Nokia with over a week of battery life

My impression is that Android market is quite saturated, and a lot more fragmented than the EOS ecosystem (so many different models to consider), but... I'm an outsider there. No idea at all about iOS. I'm not totally opposing this idea - I actually wanted to check the camera internals of smartphones before (curiosity), but didn't do any step in this direction.

Yes, I'm living under a rock; how else do you think I could achieve all of that with ML?

You are totally right, android is oversaturated and camera users knows only gcam is best. They don't even know how to compare two images from two different camera apps, also if you use Android camera api quality is same across all app basically only post process work can give some differences because the basic files that controls the "microsensors" of those ridiculous camera.

And about diversity and models the communities in android word are changing faster because they are almost all device specific, you don't follow a lot works and feat. of other phones than yours and people change phone more frequently than dslr (supposing) and to make money (like Franco) you have to develop for the biggest userbase of that moment, and usually the bigger the user base the worst the community is

went back to my old Nokia with over a week of battery life

plus smaller and toughter, I went back to my old Nokia 1208 after playing around with some xiaomi

Attached the camera lens and sensor package from my broke up smartphone

I didn't noticed this module, seems interesting but there is only the code for the module, what is different in the 550D version? I suppose icons should be in ML code

[2019-03-24]

Hello friends
I see that its available new verision on 10/12 bit ML RAW for Canon 5dmk2 and Canon 5dmk3
Latest Build (2019-03-24 09:58)

But where i can watch differencess with previous version ?
thank

after the links to download for each camera there is a link to the bitbucket commits, just check the date to see what's new from the previous version you are using

I don't know! What is badcaffe? 

I don't know either 

I got it set to all value after a fresh boot:

Code Select Expand


Canon EOS 600D 1.0.2
00f00000:       0 (was badcaffe) ISO=100 Tv=30 Av=45 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=ShootCapture pc=ff1c3910 addr=4069464c Analog ISO (most cameras)
00f00001:     423 (was badcaffe) ISO=100 Tv=30 Av=45 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=ShootCapture pc=ff1c3910 addr=4069464e Vertical offset
00f00002:      18 (was badcaffe) ISO=100 Tv=30 Av=45 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=ShootCapture pc=ff1c3138 addr=40694636 Horizontal offset / column skipping
00f00003:     1d0 (was badcaffe) ISO=100 Tv=30 Av=45 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=ShootCapture pc=ff1c3138 addr=40694638 Analog ISO on 6D
00f00007:       1 (was badcaffe) ISO=100 Tv=30 Av=45 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=ShootCapture pc=ff1c3910 addr=40694650 5D3: image fading out; 6D, 700D: vertical offset
000200c7:    3201 (was badcaffe) ISO=100 Tv=30 Av=45 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=ShootCapture pc=ff1c2e9c addr=40694288
00020002:       1 (was badcaffe) ISO=100 Tv=30 Av=45 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=ShootCapture pc=ff1c2e9c addr=4069428c
00020006:       1 (was badcaffe) ISO=100 Tv=30 Av=45 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=ShootCapture pc=ff1c2e9c addr=40694290
00020007:       0 (was badcaffe) ISO=100 Tv=30 Av=45 lv=0 zoom=1 mv=0 res=-1 crop=-1 task=ShootCapture pc=ff1c2e9c addr=40694294 ADTG preamp (4 2-bit column gains; clean image at 00, 55, AA and FF)
...


I suppose is a magic code like deadbeef, waiting the answer of the experts

from wikipedia:
"("bad cafe") is used by Libumem to indicate uninitialized memory area. "

so could be same here I suppose

by the way... what is:
badcaffe

@scrax Just seen your post! Looks like you have loaded different ISO Research modules to mine? 

I've got the iso research branch 2019mar23 for 600D and I didn't added the module from Danne because iso-regs works only for 5D if I understand right, so I'm using adtg_gui and not iso_reg as module to edit adtg that's why you have different stuff in your module