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 - Floont

Pages: [1]
1
Camera-specific Development / Re: Canon 1100D / T3
« on: July 29, 2018, 11:36:47 PM »
After numerous Err 70s that seem to be related to a quirky SD card, I got the following (using 1100D_qemu-frsp_test):



(please excuse the crud-laden screen protector)

2
That's odd... here's what I see when I click the link in my previous post:





...and clicking the "Create this page" button does seem to create a new page (although I haven't actually saved one, since I don't have anything useful to add.)
Perhaps there's some interference from an ad blocker or privacy plug-in?

3
I'm not sure what wiki software you guys are using, but it seems to work like Dokuwiki - just type in the URL of the page you want to create (e.g. https://wiki.magiclantern.fm/testing123), then you'll get a "This topic doesn't exist yet" page with a "Create this page" button at the bottom.  Once it's created, you can link to it from other pages.  I'm not sure if that's the best way to create a page, but it works...

(Edit: duh, it is Dokuwiki...)

4
Camera-specific Development / Re: Canon 1100D / T3
« on: February 27, 2018, 06:20:21 PM »
The four photos I posted were taken with my iPhone SE.  I dug out my old A590 and S30, both of which have macro features, but neither one got an image sharper or higher-resolution than the iPhone pic I already posted.  Hopefully, someone with a better second camera/lens will chime in.

I need to leave for a while, will look at the 2018Feb24 version again another time - I'll try a completely clean install to see if it clears up any of the issues I'm seeing.

5
Camera-specific Development / Re: Canon 1100D / T3
« on: February 27, 2018, 05:37:40 PM »
Can you try a few more different screens? In particular, raw histogram has some fine details (the vertical bars). A large console should also help. Also, a large zoom on fine print, please (even if it's just a small part of the screen in the picture).
As I said, this new version doesn't play well with my camera.  I can't get the histogram to display - menu item is on, but grayed out.  It works in the 2017Aug07 version, if that's helpful (not sure if you're looking for something new or just how the 1100D display looks in general).

Fine print from magiclantern-lua_fix.2018Feb24.1100D105 version:





Histogram from magiclantern-Nightly.2017Aug07.1100D105 version:



6
Camera-specific Development / Re: Canon 1100D / T3
« on: February 27, 2018, 02:04:58 PM »
Also looking for a high-res photo of the camera display (large enough to see the individual pixels), showing ML menu with any recent build.

If it's hard to get the entire screen in focus, just focus on some problem areas (e.g. some icon or fine print that doesn't look well).

I've been using magiclantern-Nightly.2017Aug07.1100D105, but per a1ex's request, I loaded magiclantern-lua_fix.2018Feb24.1100D105 and took the two attached photos.  (This version is effectively non-functional for me - it displays a large number of error messages at launch, most of the menus are just black pages with an icon at the top, and I can't navigate within the menus themselves, but that's not what the question was about (so I'll return to  magiclantern-Nightly.2017Aug07.1100D105 for now)).
Hopefully these  images are close to what you're looking for.  I can try other things if it's helpful.
(Please note that I have a scratch-guard coating on my display, so there might be some artifacts from that - if so, such artifacts should be consistent between the two photos.)








7
Camera-specific Development / Re: Canon 1100D / T3
« on: December 18, 2016, 03:16:29 PM »
I thought the 1100D development was dead, too.  I missed the earlier request from a1ex;  here are my results:

(magiclantern-Nightly.2015May03.1100D105, clean fresh install)

First, 5x zoom had no effect on the timer values I observed.

In photo mode: after a fresh boot, timers were 0 (-1), 0 (-1).  Switching to photo mode after being in video mode, timers remained as they were in the video mode.

FPS override off:
1280x720@30: 960 (+0), 1112 (+0)
1280x720@25: 1000 (+0), 1280 (+0)

FPS override @35:
1280x720@30: 872 (-88), 1050 (-62)
1280x720@25: 872 (x0.87), 1050 (x0.82) <- this was the only setting that showed 'x' instead of '+' or '-'; also the only one with decimals

Let me know if there are other tests to be run, and I'll try to help.  I'd love to see a new version.

8
Camera-specific Development / Re: Canon 1100D / T3
« on: November 21, 2013, 08:38:13 PM »
I've just found time to start using my 1100D again, so I came here looking for the latest and greatest.  The last build that didn't fail seems to be on 20oct13 - is that (relatively) safe to use, or do I need to go farther back?  Is there a list somewhere of which features the 1100D port currently supports (or tries to)?  Does a month of failed builds suggest that the 1100D port is currently sidelined or abandoned?

9
General Development / Re: Development stupid questions
« on: December 29, 2012, 11:10:11 PM »
I've tried to print the auto iso range with this line:
bmp_printf(fnt, 455, 92, "%d-%d", raw2iso(auto_iso_range >> 8 ) , raw2iso(auto_iso_range % 0xff));
and I've got strange value for the max.
After I check the raw values I found this
if auto_iso_range is 0x4860
then  auto_iso_range >>8 is 0x48 (good) but auto_iso_range % 0xff is 0xa8 ! (wrong) which is exactly 0x48 + 0x60
I'm not really a hardcore C programmer so I couldn't figure out what circumstances causes this result.
It happens with other values too (between 0x4858 and 0x4878)

Any idea?
The % sign in C is the modulus operator.  Your code is calculating 0x4860 (18528 decimal) mod 0xff (255 decimal), which is 0xa8 (168 decimal).  What you actually want is the low byte of auto_iso_range, which can be retrieved either by changing 0xff to 0x100 in your existing code or simply using the & operator instead of the "%" operator (my preference), i.e. raw2iso(auto_iso_range & 0xff).

Pages: [1]